JP2012234525A - Information processing apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To effectively perform resource management so as to easily move an installed software license to another device without giving unexpected disadvantage to a user.SOLUTION: The information processing apparatus includes: installation means for downloading and installing software corresponding to a predetermined function from the outside; license file acquisition means for acquiring a license file from the outside; license existence management means for managing the existence of a license for function regardless of the existence of a license file; use protection management means for, when the upper limit number of use of a function is defined with a license file, managing the number of use protection which prohibits the use of the function on another device within the range of the available number of use calculated by subtracting the actual number of use from the upper limit number of use; license moving means for moving a license between devices and updating the existence of the license for a relevant function; and function control means for controlling use of the function by the upper limit number of use and the number of use protection.

Description

  The present invention relates to a technique for managing a license (usage right) of software used in an information processing apparatus.

  In recent image processing devices called MFPs (Multi Function Printers, Multi Function Peripherals) equipped with various functions such as copy, scanner, and fax, as well as PCs (Personal Computers) As a result of improvements, lower prices for large-capacity memory, and progress in networking, it is not necessary to pre-pack applications for sale (box sales), but to purchase applications as needed and download them via the network to the equipment. It came to add the function by installing.

  When an application is installed on a device, a license is confirmed for the purpose of preventing unauthorized use. For example, you can enter the license key that you know at the time of the official purchase of the application to install it on the device, and when you use the application after installation, you can access the license server and authenticate the license. There are types to be judged.

  In license management based on these license forms, an authentication target is often specified only by a device (for example, a serial code unique to the device) into which an application is introduced.

  Further, as a license form different from these, there is a technique such as a floating license. By managing the number of licenses, if the upper limit of the number of licenses is not exceeded, the function introduction can be used without being limited to a specific device.

  When the license form is the above-described floating license, the use of the application is not limited to a specific device, so that the license of the application installed in a certain device can be transferred to another device. Moving the license does not change the number of licenses.

  When transferring a license from a licensed device to another device, there are roughly two types of conventional license management systems.

  In the first type, when transferring a license from a licensed device to another device, the license is returned from the licensed device and the software is installed again (installation, license acquisition) on the other device. Is to do.

  In the second type, when the license is acquired from another device (B) without returning the license from the licensed device (A), the license of the original device (A) is invalidated in the license management system. A license is given to another device (B).

  In Patent Document 1, there is a license that has been issued to another device in a system that manages the license of the software installed in the device for the purpose of transferring the license information of the software while preventing unauthorized use of the software. When a request for permission to install the software is input from another device, the software is permitted to be installed (license issuance), and at the same time, the use of the corresponding software is prohibited for devices that already have a license issued. Thus, a technique for transferring license information to a new device is disclosed.

  When the above-described license management system is used, it is necessary for the user to input a license key of about 10 or more alphanumeric characters in order to determine whether or not the user is valid, including prevention of unauthorized use, at the time of license acquisition.

  Therefore, when transferring a license from a licensed device to another device, the license key is known (remembered or has license key information at hand) in both the first and second types. ) Is necessary. Since the license key was used at the time of previous license acquisition, it is often managed by the administrator of the licensed device, but it may have been forgotten. Need to get. Even when the license key is known, if the license-acquired device and the license transfer destination device are separated from each other, both devices must be operated, which is complicated. In this case, it is possible to request an operation from a third party in the vicinity of each device, but it is necessary to convey the license key information, which is complicated.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to easily transfer a license of installed software to another device, and to further limit the upper limit number of use, etc. It is an object of the present invention to provide an information processing apparatus that can perform efficient resource management without causing any unexpected disadvantage to the user even when the license is defined.

  In order to solve the above problems, in the disclosed form, an installation unit that downloads and installs software installation data corresponding to a predetermined function from the outside, and a license file from the outside to activate the function In addition to the license file acquisition unit to be acquired, the license presence / absence management unit for managing the presence / absence of the license of the function, and the upper limit number of usage that can use the function in the license file, separately from the presence / absence of the license file The usage protection management means for managing the number of usage protections that cannot be used by other devices within the range of the number of available usages obtained by subtracting the actual number of usages from the upper limit number of usage, and the license transfer between the devices, License transfer means for updating the presence / absence of a license for the corresponding function , And a function control means for controlling the use of the function from the available maximum number and the use protection count.

  In the information processing apparatus of the present invention, the license of the installed software can be easily transferred to another device, and even if the license has a specified upper limit number of use, the license is transferred to the user. Efficient resource management can be performed without incurring unexpected disadvantages.

1 is a diagram illustrating a configuration example of an image forming apparatus according to an embodiment of the present invention. It is a figure which shows the example of the information which a license movement management part has. It is a flowchart which shows the example of a process at the time of new installation / activation. It is a figure which shows the example of a process until it selects the function / license used as a transfer object from the movement destination apparatus (request origin) of a license to a movement origin apparatus (request destination). It is a flowchart which shows the process example in the transfer destination apparatus (request origin) at the time of license transfer execution. It is a flowchart which shows the process example in the movement origin apparatus (request destination) at the time of license movement execution. It is FIG. (1) which shows the example of a specific process of a license transfer. It is FIG. (2) which shows the specific example of a process of a license transfer. FIG. 10 is a third diagram illustrating a specific process example of license transfer. It is a figure which shows the example of a license form. It is a figure which shows the example of the state at the time of performing license transfer. It is a figure which shows the example which sets up use protection for the own apparatus before a license transfer (when a use protection setting possible apparatus and a use protection setting level are not introduce | transduced into license transfer management information). It is a figure which shows the example which sets up use protection for an own apparatus and another apparatus before license transfer (when a use protection setting possible apparatus and a use protection setting level are not introduce | transduced into license movement management information). It is a figure which shows the example which sets a use protection for the own apparatus in a transfer destination after a license transfer (when a use protection setting possible apparatus and a use protection setting level are not introduce | transduced into license transfer management information). It is a figure which shows the example which cannot set use protection. It is a figure which shows the example of the difference in the use protection setting by a use protection setting possible apparatus. It is a figure which shows the example of the difference in the use protection setting by a use protection setting level. It is a flowchart which shows the example of a process of a use protection setting. It is a figure which shows the example which sets notification in a transfer destination after a license transfer. It is a figure which shows the example which sets notification with a license head apparatus. It is a flowchart which shows the example of a process at the time of the license transfer in the license transfer destination apparatus (request source). It is a flowchart which shows the example of a process of license movement availability judgment. It is a flowchart which shows the example of a process at the time of the license transfer in the transfer origin apparatus (request destination) of a license. It is a flowchart which shows the example of a process of license movement availability judgment. It is a figure which shows the example of the display of consumption of the frequency | count of use, and the remaining available number. It is explanatory drawing of the problem by the function deletion corresponding to a license. It is explanatory drawing of the problem by a license return and a license transfer. It is a figure which shows the example of a setting screen of a surplus distribution setting. It is a figure which shows the example of a setting screen of surplus distribution destination setting. It is a flowchart (the 1) which shows the example of a process of a license update. FIG. 10 is a diagram (part 1) illustrating an example when license transfer and function deletion are performed; FIG. 11 is a diagram (part 2) illustrating an example when license transfer and function deletion are performed; FIG. 11 is a diagram (No. 3) illustrating an example when license transfer and function deletion are performed; It is a flowchart (the 2) which shows the example of a process of a license update. It is a figure which shows the example of a confirmation screen at the time of trying to delete the function corresponding to a license, or to return a license. It is a figure which shows the example of systematization which makes a server share a part of process.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 1 is a diagram illustrating a configuration example of an image forming apparatus 1 according to an embodiment of the present invention.

  In FIG. 1, an image forming apparatus 1 includes a system control unit 102, a display unit 103, an operation unit 104, an external communication unit 105, a job management unit 106, a reading device unit 107, and an image memory connected via a system bus 101. A unit 108, an image processing unit 109, a printing unit 110, an installation management unit 111, a license file management unit 112, and a license migration management unit 113.

  The system bus 101 is a path connecting a plurality of devices (units) constituting the image forming apparatus 1.

  The system control unit 102 is configured by a CPU (Central Processing Unit) or the like, expands a program stored in a nonvolatile memory in a work area (RAM or the like), and controls each unit according to the program.

  The display unit 103 performs various displays on the screen based on display data instructed from the system control unit 102.

  The operation unit 104 includes a keyboard having various function keys and the like, and transmits a pressed signal of a pressed key to the system control unit 102.

  The external communication unit 105 communicates with a license management system (server) provided outside. The external includes a component server and a memory device (such as an SD card) in addition to the license management system.

  The job management unit 106 schedules jobs such as print jobs. Further, the job management unit 106 suppresses the use when the remaining usable number obtained from the upper limit number of use specified by the license of the application and the actual number of use becomes 0.

  The reading device unit 107 scans a document set on the image forming apparatus 1 and acquires image data.

  The image memory unit 108 stores image data, print data, and the like.

  The image processing unit 109 performs image processing such as enlargement / reduction and rotation on the input image data, and outputs the processed image data to the printing unit 110.

  The printing unit 110 includes a photosensitive drum, toner, a paper feed unit, a paper discharge unit, and the like. In accordance with a printing instruction from the system control unit 102, the printing unit 110 conveys printing paper from the paper feeding unit, causes an image corresponding to the image data input from the image processing unit 109 to be exposed to a photosensitive drum, and developed with toner. Then, the toner is transferred and fixed from the photosensitive drum to the printing paper, and the printing paper is discharged from the paper discharge unit.

  The installation management unit 111 manages configuration information of software installed in the image forming apparatus 1.

  The license file management unit 112 manages the license file downloaded from the license management system using the external communication unit 105, and performs determinations such as license update and automatic license return using the license file information.

  The license migration management unit 113 manages information associated with the migration of the license file, performs a response according to the settings of usage protection and usage status notification, and implements a response associated with the license operation in conjunction with other devices. As the license operation, a function / license inquiry from another device is performed, and the function / license transfer (transfer) is controlled. In addition, it controls the deactivation / activation (regardless of automatic / manual) of other devices (target devices on the license movement path).

  FIG. 2 is a diagram illustrating an example of information (license migration management information) held by the license migration management unit 113. The function identifier (product ID), the corresponding license identifier (license ID), the license original device, the license duplicating device, and the license Includes holdings. The license home device, license copy device, and license holding are new information that does not exist in the existing device.

  Further, the license migration management information includes an expiration date, a usage upper limit number, a usable number, a usage protection count, a usage protection target device, a notification threshold, a notification target, a protection setting notification, and a periodic information notification. Since the expiration date and the upper limit number of use are included in the license information file, they can be omitted when referring to the license information file whenever necessary. The usable number, the use protection number, and the use protection target device are basic information, but the notification threshold, the notification target, the protection setting notification, and the periodic information notification can be omitted if the corresponding function is not used.

  In addition, the license migration management information includes devices that can be used for protection setting and usage protection setting levels.

  Further, the license movement management information includes a surplus distribution setting and a surplus distribution destination setting.

  Hereinafter, each information will be described.

-Applicable function identifier (product ID)
This information identifies the function (software) to be installed in the device. When transferring a license from one device to another, there is a user at the device that is the destination (operation source), but the user does not always know the desired function / license. When acquiring a function list, it is possible to notify a movable function / license by referring to this information.

-Applicable license identifier (license ID)
The license file is acquired from the license management system when the function is introduced. The license file management unit 112 holds the license file entity, and information on whether or not there is a license (right) separately from the presence or absence of the license file. Is information for associating the license file with the license file.

・ License home device Functions / licenses are transferred between devices without going through the license management system. Depending on the license form, automatic license renewal, automatic deactivation (license return), or manual deactivation / subsequent activation etc. As a result, communication with the license management system occurs. However, in many cases, the license management system acquires information (for example, serial number) for specifying a device when communicating with the corresponding device when the corresponding license is issued, and manages the information in association with the issued license. For this reason, as described above, it is not desirable that access is made from a device other than the device associated with the license managed by the license management system when accessing from all the devices whose licenses have been transferred. In a license management system that manages licenses and devices in association with each other, the NG process is performed. However, if the licenses are not associated, the license operation of the device accessed first is reflected, and each device (license transfer path) and It can happen. Therefore, in order to avoid these problems, and in order not to require the license management system to deal with license migration in particular, the device that accesses the license management system is the device that acquired the license first (this is called the head family). Only. Therefore, there is no contradiction between the server management license and the device identification information as much as the head family accesses.

  This information indicates that only the device for which the license is initially acquired becomes the license head, and all the devices along which the license has been transferred do not become the head. Here, it is not the license head or not (Yes or No), but indicates which device the head is. This is because when a license is manually acquired for a device on a route that has been moved (already licensed by another device), it is not the head family, so the operation is NG. Not only because it is moved and not owned, but also to teach the license management system and the devices that can be accessed.

・ License replication device Functions / licenses are transferred between devices without going through the license management system. However, depending on the license type after the transfer, it is necessary to update / delete license files such as automatic license update and automatic deactivation (license return). There is a case. In this case, as described in the section “License home device”, only the head home communicates with the license management system. It is necessary to manage the response such as license update / deletion. For this reason, this information is used because it is necessary to grasp all the devices that have become license transfer paths (holding the license copy).

・ License possession When a function / license is moved, the license file is copied and provided to the transfer destination. However, if the license management system does not know the license management system, it will be illegally used (increased number of licenses issued by the server). Therefore, when the function / license is moved by copying the license, the device that is the transfer source does not have the license, that is, it is illegal to use the information such as “No” regarding whether the license is transferred or not. To prevent. The license possession is indicated by “Yes”.

-Expiration date The expiration date specified in the license information file for the applicable application. There are cases where a date is designated, and cases where the date is designated from a date such as a license grant date.

-Maximum number of usages This is the number of applicable applications specified in the license information file. According to the contract, it is specified by the number of printable sheets or the number of times the function can be executed. The expiration date and the upper limit number of usage may be defined exclusively or in combination.

-Usable number This is the number obtained by subtracting the number of usages (cumulative value of the number actually used) and the number of usage protections (or 0 if no usage protection number is set) from the maximum usage number. The maximum value that can be used by devices that are not subject to usage protection is the number that can be used. The maximum value that can be used by a device that is subject to use protection is obtained by adding the number of use protections for that device to the number of usable devices.

-Number of usage protections This is the number of usage protection (secured) for a specific device when usage protection is set. Other devices cannot use as much as they are included in the number of usage protections even if the license is transferred.

-Equipment subject to use protection Information that identifies equipment subject to use protection.

Notification threshold A value for determining the notification timing when a license usage status notification is set for a specific device.

-Notification target Information for identifying a device to which a user (registered user) to be notified of usage status belongs.

・ Protection setting notification As a notification of the usage status for the licensed home device, when the usage protection is set on each device after the license transfer, the ratio of the newly set usage protection to the usage protection number and the usage limit number, etc. This is information indicating validity / invalidity (ON / OFF) of notification of information that can be calculated from the license movement management information.

Periodic information notification As a notification of the usage status for the license home device, the consumption of the usable number with respect to the upper limit number of usage reaches a predetermined value (for example, 20% for the near end, 0% for the end) or in predetermined increments (for example, 10%) This is information indicating the validity / invalidity (ON / OFF) of the notification when it reaches the (step).

・ Devices that can be set for use protection Information that identifies devices that can be set for use protection. The licensed home device that first introduced the license is set as a device that can be used for protection setting at the time of introduction, or it is set as a device that can be used for protection setting even if it is not set as a device that can be used for protection protection. It is treated in the same way as By operating with the license home device, it is possible to set other devices as devices that can be used and protected.

-Usage protection setting level This is information indicating the priority of the usage protection setting for each device that is set as a usage protection configurable device. In order to avoid a situation in which the number of available protections is insufficient due to the usage protection settings already made and it becomes impossible to set new usage protection settings, it is allowed to take away the number of usage protections that have already been set. Since it cannot be said that the use is protected if it is stolen, the use protection setting level defines the criteria for depriving / stolen. If the usage protection setting level of a device is lower than the usage protection setting level of a device to which new protection is to be set, the usage protection can be set because the usable number is less than the required usage protection number. However, if the usage protection can be set by depriving the number of usage protections set for other devices, the number of usage protections may be deprived. The device having the highest use protection setting level does not lose the use protection number.

・ Surplus distribution setting When a license or a corresponding function is deleted, a license is returned, or a license is transferred in response to a license transfer request from another device, usage protection is set for that device. This is information indicating a surplus distribution method of the usage protection number so that the usage protection number is not wasted when the usage protection number has a surplus when the usage protection is canceled. The surplus distribution setting includes “return to available number”, “return to other device”, and the like.

-Surplus distribution destination setting Information for specifying or selecting another device when the surplus distribution setting is “Return to other device”. The surplus distribution destination setting includes “master device (home device)”, “maximum use protection setting device”, and the like.

<License transfer without operation / use protection>
FIG. 3 is a flowchart showing an example of processing at the time of new installation / activation, which is a license acquisition after normal software installation, that is, processing at the time of activation. It should be noted that the function does not become effective just by installing software that realizes a predetermined function, but becomes effective when activated. It can also be deactivated after being activated.

  In step S101, when the user inputs a license key on the screen and starts executing the activation in order to obtain a license for using the corresponding function, in step S102, the license management system is connected, and the license key is validated in the license management system. Check sex.

  In step S103, the process branches depending on whether an error determination such as a connection error or an invalid license key has occurred. If an error determination is made, error processing is performed in step S108, and activation is completed by an abnormal system in step S109.

  If no error determination is made, the validity of the license key is confirmed, and in step S104, a license file is acquired from the license management system. The license file stores a license type, a use time limit, and the like.

  In step S105, processing for making the function available using the acquired license file is performed. The function can be used according to the expiration date included in the license file.

  In step S106, the license movement management unit 113 manages the information that the license is acquired and the function is available in this flow. Therefore, the ID indicating the corresponding function, the ID indicating the license file, and the information of the own device are set in the license headquarters information, and information indicating that the license is acquired is also set for the license holding. Nothing is set for license duplication at the time of this flow. This is because it is updated when the license for the function is transferred to another device. As a result, the function can be used in step S107 and the activation is completed.

  FIG. 4 is a diagram showing an example of processing until the function / license to be moved from the license destination device (request source) to the source device (request destination) is selected.

  First, in step S201, a function list is inquired from the requesting device D to the devices (A, B, C,...) Connected to the network.

  Each device that receives the inquiry returns information about the functions installed in the device itself to the device D, and the device D acquires this in step S202. Of course, it is not necessary to return the inquiry results for devices that are not subject to insertion / removal, such as firmware and installation / uninstallation, and functions that do not assume license transfer.

  In response to the inquiry result from each device, device D performs screen display in step S203. When a function that the user is interested in or necessary is selected in step S204, a detailed screen is displayed. In the detailed screen, not only information indicating each function (name, function overview, etc.) but also “device location”, “frequency of function usage”, “comment in the free description column” (“do not move” etc.) are set It is also possible to use information that can be used to determine which device to move from.

  From these detailed information, in step S205, the user selects from which device the function / license file and the license are to be transferred, and an instruction to execute the transfer is issued.

  FIG. 5 is a flowchart showing an example of processing in the transfer destination device (request source) at the time of license transfer execution.

  When the function / license transfer target is selected in step S301 and the process starts, in step S302, the state of the own device is confirmed before the function / license transfer is transmitted to the request destination. This is because when a function / license transfer is requested to the source device, there are a case where the corresponding function is installed on the own device and there is no license, and a case where the function itself does not exist.

  If the function itself does not exist, in step S303, when the function / license transfer request is made to the transfer source, if the corresponding function is not installed or there is a difference in version and installation data is required, the install data is also requested. .

  In step S304, transfer of the function / license is requested, but if installation data is required in step S303, the installation data is also requested.

  In step S305, transfer data based on the license of the corresponding function is received.

  In step S306, it is determined whether there is an error in receiving the transfer data. If there is no error, in step S307, it is determined whether the corresponding function is not installed.

  If the corresponding function is not installed (if the corresponding function is also requested to be transferred), in step S308, installation processing is executed using the received installation data. Of course, when installation data is required due to a version difference, an update process is performed internally. If no error at the time of installation is determined in step S309, the process merges with the case where the installation is not performed.

  In step S310, as an activation process, the corresponding function is made available using a license file. In addition, unlike the normal activation process, the function / license is transferred between devices as in the case of the transfer source, and communication with the license management system is not performed.

  In step S311, it is determined whether or not the own device is the license head. If the own device is not the license head, the license movement management unit 113 updates the corresponding information in step S312. That is, the “license possession” information is in a licensed state, and the “license original device” information describes information indicating which device is the original. Also, the “license duplicating device” information is blank because it is not used except by the licensee.

  If your machine is the license owner, you have activated the function based on the external system as the license owner and you are in a function-usable state. This corresponds to the case where after the license is invalidated and the license is transferred to another device, the own device regains the license from the device having the license for the current function.

  If the own device is the license owner, the license migration management unit 113 updates the corresponding information in step S313. That is, the “license possession” information is in a licensed state, and the “license original device” information is not updated because the own device is known as the original device. In addition, regarding the “license duplicating device” information, since it is not necessary to describe the license family as a duplicated route, the update process is not performed. Thereby, in step S314, the function / license transfer is completed.

  If there is an error in the transfer data reception or analysis after the reception (or installation, etc.), it is conceivable that the data transfer is requested again or the license transfer fails in the error processing in step S315. Also, if there is no deficiency in the transfer data and there is an error during the installation process and the activation process, the recovery process is performed because it is closed by the own machine. However, if an error occurs even after recovery, the function cannot be used even if the license is transferred. Therefore, the information that is handled by the license transfer management unit between the devices, such as by returning the license to the transfer source. Roll back so that there is no.

  In this flow, installation data and license file data are received as necessary. However, if a function usage license is transferred between devices many times, it is installed on each device and the license file is retained. Can be. In this case, it can be realized by requesting only the license for function use to be transferred to the request destination. The received data includes only information necessary for management for license transfer (“license original device”, “expiration date” (effective expiration date in the original home, not the expiration date of the license file)).

  Note that the “license duplicating device” information is not necessary as received data of the license transfer request destination because it is transmitted to the home device when moving from a device other than the home device to another device. Further, the “license possession” information does not need to be provided as information because the license is retained when the license is moved. However, it is also necessary to inform as information when matching with each device such as rollback.

  FIG. 6 is a flowchart showing an example of processing in the source device (request destination) when executing license transfer.

  When the function / license transfer request is made in step S401 and the process starts, in step S402, it is first determined whether the license transfer request can be accepted. This may be after the license file already exists and the license was previously transferred but the license has already been transferred to another device.In this case, the license cannot be transferred, so it is possible to accept the request. Become.

  If the license transfer request can be accepted, it is determined in step S403 whether the function / license transfer can be executed. This is because the function / license cannot be transferred when the function based on the requested license is being executed or waiting for execution (including reservation).

  If the license transfer can be executed, in step S404, the function cannot be used as a deactivation process of the corresponding function. In the normal deactivation process, the license is returned to the license management system. However, in the case of a function / license transfer request, the license / system is not returned to the license management system in order to realize the function / license transfer between devices. In this case, the function associated with the license is invalidated as a deactivation process without returning the license.

  In step S405, it is confirmed from the information of the license migration management unit 113 whether or not the own device is the license owner.

  If the own device is the license head, in step S406, the license migration management unit 113 adds information on the migration destination device to the “license duplicate device” information. Also, the “license possession” information is updated to information that no license is possessed.

  If the device itself is not the license owner, in step S407, the license migration management unit 113 updates the information that the “license possession” information is not retained. Since it is not the head family, “license duplicating device” information is not handled.

  In step S408, information indicating that the license has been transferred to another device is notified to the device serving as the license head. Upon receiving this notification, the license head device adds the notified device information to the “license duplicate device” information in its own license migration management unit 113.

  In step S409, it is determined whether only the license file is required for the transfer or whether the installation data of the function itself is necessary. Which pattern is included in the first request of this flow.

  If the installation data is also the transfer target, in step S410, the installation data indicating the corresponding function, that is, the data of the sales package (PKG) in the release form is copied.

  In step S411, the copied installation data is transferred to the requesting device. If no error is determined in step S412, the process merges with the case of only the license.

  In step S413, the license file associated with the function is copied.

  In step S414, the copied license file is transferred to the requesting device. Regarding license file duplication / transfer, limit the duplication / transfer limit value (for example, up to 10 times) or limit to only devices on the same floor (requires floor installation information). be able to.

  If no error is determined in step S415, the function / license transfer request response is completed in step S416.

  In the error processing of step S417, at the request reception stage (before execution) such as step S402 / 403, only the request source is informed that the request cannot be executed. Since the information has been updated, roll back to the state before the update. After the error process, the function / license transfer request response is completed as an NG process in step S418.

  It should be noted that the request source is notified of the fact that it has rolled back by itself in case of an error during data transfer, etc., and the request source is urged to roll back in order to prevent inconsistencies between the devices.

  If it is not possible to connect to the request source due to a line disconnection, etc., retry processing is performed several times. However, if notification about the alignment processing cannot be made in one direction, there is a possibility that the alignment may not be achieved. It is also possible to temporarily disable. In this case, the user is informed of the reason for temporarily invalidating the license by using means such as screen display or e-mail notification, and urges recovery. After that, notification for matching with the request source can be made, and if there is no problem with matching, the invalidation is canceled, and each device can roll back to the state before the request. In the rollback of the request source, partially received data that has not been completed is discarded.

  Note that in this flow, installation data and license file data are copied and transferred as necessary. However, if a function usage license is transferred between devices many times, it is installed on each device and the license file is retained. It can become a state. In this case, it can be realized by providing only the license for function use to the request source. The transfer data includes only information necessary for management for license transfer ("license original", "expiration date" (effective expiration date in the actual original data, not the expiration date of the license file)). If the expiration date of the license file (for example, +3 months), the expiration date of the device increases with each move, and it is necessary to follow the expiration date that the headquarters first activated. Applicable expiration date).

  The “license duplicating device” information is transmitted to the home device when moving from a device other than the home device to another device, so there is no need to notify the providing destination when providing the license. Also, with regard to license holding, it is not necessary to provide information as it does not hold the license when the license is moved. However, it is also necessary to inform as information when matching with each device such as rollback.

  7 to 9 are diagrams showing specific processing examples of license migration, and are diagrams showing the status of license migration management information when license migration is performed by a plurality of devices (three).

  FIG. 7 shows an initial state, in which device A is the device in which the function Z is first introduced as the home, device B has the function Z installed through the memory device but has not been activated, and device C has no plug-in. Assume devices that have not been added. The plug-in with the product ID “123” is called function Z for the sake of explanation. The devices for which the license file is valid are enclosed in bold lines.

  FIG. 8 shows a state when the license is transferred from the device A as the license head to the device B, and FIG. 9 shows a state where the license is transferred from the device B to the device C.

<Operation / Plug-in operation>
In the following, the behavior at the time of plug-in operation in each state generated in each device based on the license transfer will be described. In the following explanation, “automatic license renewal” means that when the expiration date of the license (the expiration date of the original family at the destination) approaches, it communicates with the license management system according to the license form, acquires a new license, and automatically licenses It is a technology for updating. Apart from the automatic license update, updating the license at any timing of the user is called “manual license update”.

  Further, in the following processing, there is a common logic that first confirms “whether it is the original” and then confirms that the own device is the original.

** For the licensee family **
[Device configuration: No license, no copy (no activation after installation)]
● Operation: Manual license renewal (1) You see “license held” information, but you do not have it. However, even if the "license duplicating device" information is seen, it is determined that there is no duplication destination and that the license has not been moved.
(2) A normal license update via the server is performed to obtain an updated license file.

● Operation: Automatic license update (1) Perform normal license update via the server.
(2) Looking at the “License holding” information, it does not hold, but even if you look at the “License duplicating device” information, it does not mean that the license has been moved. No interlocking operation is required.

● Operation: Deactivate (License Return) (1) When viewing the “License Copy Device” information, it is determined that the license has not been transferred because there is no copy destination. If you look at the “license holding” information, you can see that you do not have a license, that is, you have not activated it after installation.
(2) A message indicating that no operation is required since a license has not been acquired is displayed.

● Operation: Deletion (deletion of function) (1) When viewing the “license duplicating device” information, it is determined that there is no duplication destination and no other license has been moved. If you look at the “license holding” information, you can see that you do not have a license, that is, you have not activated it after installation.
(2) The corresponding function is deleted.
(3) The license movement management information is also deleted.

[Equipment configuration: No license, copy available (License transfer after activation)]
● Operation: Manual license renewal (1) You see “license held” information, but you do not have it. Then, when viewing the “license duplicating device” information, it is determined that the license has been moved because a duplication destination exists.
(Pattern A)
(2) Prompt to execute after moving the license to this machine, and request will be an error.
(Pattern B)
(2) Although there is no license, a normal license update via the server is performed to update the license file. However, since there is no license, of course, it is not activated. Also, the update license file is transferred to each copy destination device to trigger a license update.
(3) Execute until all the duplication destinations in (2) are completed. If there is no connection, repeat the retry process periodically.

● Operation: Automatic license update (1) Perform normal license update via the server.
(2) The "license holding" information shows that the license has not been held, but the "license copying device" information shows that the license has been moved.
(3) Copy the updated license file, transfer the updated license file to each device, and trigger a license update.
(4) Execute until all the duplication destinations in (3) above are completed. If there is no connection, repeat the retry process periodically.

● Operation: Deactivate (License Return) (1) You see "License Holding" information, but you do not have it. Then, when viewing the “license duplicating device” information, it is determined that the license has been moved because a duplication destination exists.
(Pattern A)
(2) Because the license has been transferred to another device on this machine. Prompt to execute after moving the license to this machine, and request will be an error.
(Pattern B)
(2) Identifying the current license holding device from the “license duplicating device” information with the idea of prioritizing user operation (you can identify it yourself, or you can make a license holding inquiry to the duplicating device), and assign the corresponding license yourself Move to (regain license).
(3) When the license is returned to the device in (2) above, the license is returned by communicating with the server. (If (2) cannot be recovered, error processing is performed.)
Since the head family returned the license to the server, at this time there is a license file on all devices, but there is no license anywhere. If the headquarters accepts the deletion in this state, it is determined that the license has been returned to the server if there is no license even if you inquire about the other device as to whether the license is on another device or returned. Is possible.

● Operation: Deletion (deletion of function) (1) Although “License holding” information is viewed, it is not held. Then, when viewing the “license duplicating device” information, it is determined that the license has been moved because a duplication destination exists.
(Pattern A)
(2) Since the license has been transferred to another device on this machine, the license is transferred to this machine, the license is returned to the server (deactivated), and the user is prompted to delete it. An error is assumed.
(Pattern B)
(2) Identifying the current license holding device from the “license duplicating device” information with the idea of prioritizing user operation (you can identify it yourself, or you can make a license holding inquiry to the duplicating device), and assign the corresponding license yourself Move to (regain license).
(3) When the license is returned to the device in (2) above, the license is returned by communicating with the server. (If (2) cannot be recovered, error processing is performed.)
(4) Delete the corresponding function.
(In pattern B, pattern 1 after deletion)
(5) Since there is no license for the license duplication destination, functions in each device cannot be used and resources are wasted, so deletion of the corresponding function / license file is prompted.
(6) Repeatedly until the above (5) is completed.
(7) When the above (6) is completed, the license transfer management unit deletes the corresponding information.
(In pattern B, pattern 2 after deletion)
(4) After that, the license movement management information is also deleted and the flow ends (that is, no deletion request is made to another device).

  In other words, the head family disappears and only the branch house having the license file becomes necessary, and although the home trigger is required such as automatic license renewal, it becomes impossible to cope. This is because it can be determined that the license transfer management information was not found when it was inquired by the branch office, and it can be determined that the information has been sent to the branch house as a result of the inquiry. (Delete function).

[Device configuration: Licensed, no duplication (Activate after installation)]
● Operation: Manual license renewal (1) The license is owned by looking at the “license possession” information. In addition, the “license duplicating device” information is seen, but it is determined that the license has not been moved because there is no duplication destination.
(2) A normal license update via the server is performed to obtain an updated license file.

● Operation: Automatic license update (1) Perform normal license update via the server.
(2) If you look at the license holding, you can see that it is held, and even if you look at the “License Duplicating Device” information, the license has not been moved. No interlocking operation is required.

● Operation: Deactivate (License Return) (1) When viewing the “License Copy Device” information, it is determined that the license has not been transferred because there is no copy destination. When the “license possession” information is seen, it can be seen that the license is possessed, and it can be determined that the case is a normal deactivation process.
(2) Perform a normal deactivation process and return the license to the server.
Since the home has returned the license to the server, if the home accepts the deletion in this state, it can be determined that the license has been returned because the license has not been transferred to another device.

● Operation: Deletion (deletion of function) (1) When viewing the “license duplicating device” information, it is determined that there is no duplication destination and no other license has been moved. The “license possession” information shows that the license is possessed and it can be determined that the normal deactivation process can be executed.
(2) Perform a normal deactivation process and first return the license to the server.
(3) The corresponding function is deleted.

[Equipment configuration: Licensed, duplicated (when the license is moved and activated again after activation)]
● Operation: Manual license renewal (1) The license is owned by looking at the “license possession” information. Further, when viewing the “license duplicating device” information, it is determined that there is a duplication destination, so that the license is moved and another duplication license file is available.
(2) Perform a normal license update via the server and update the license file. Also, the update license file is transferred to each copy destination device to trigger a license update.
(3) Execute until all the duplication destinations in (2) are completed. If there is no connection, repeat the retry process periodically.

● Operation: Automatic license update (1) Perform normal license update via the server.
(2) Looking at the “license holding” information, the license is owned. However, when viewing the “license duplicating device” information, it is determined that the duplication destination exists and the license is moved and other duplicating license files are available.
(3) Copy the updated license file, transfer the updated license file to each device, and trigger a license update.
(4) Execute until all the duplication destinations in (3) above are completed. If there is no connection, repeat the retry process periodically.

● Operation: Deactivation (License return) (1) Looking at the “License holding” information, the license is owned. However, when viewing the “license duplicating device” information, it is determined that the duplication destination exists and the license is moved and other duplicating license files are available.
(2) Perform a normal deactivation process and return the license to the server.

  Since the head family returned the license to the server, at this time there is a license file on all devices, but there is no license anywhere. If the headquarters accepts the deletion in this state, it is determined that the license has been returned to the server if there is no license even if you inquire about the other device as to whether the license is on another device or returned. Is possible.

● Operation: Deletion (deletion of function) (1) Looking at the “license holding” information, the license is owned. However, when viewing the “license duplicating device” information, it is determined that the duplication destination exists and the license is moved and other duplicating license files are available.
(2) Perform normal deactivation processing and return the license to the server.
(3) The corresponding function is deleted.
(Pattern 1 after deletion)
(4) Since there is no license for the license duplication destination, functions in each device cannot be used and resources are wasted, so deletion of the corresponding function / license file is prompted.
(5) Periodically repeat until the above (4) is completed. (6) When the above (5) is completed, the license migration management unit deletes the corresponding information.
(Pattern 2 after deletion)
(3) The license migration management information is also deleted later, and the flow ends (that is, no deletion request is made to another device).

  In other words, the head family disappears and only the branch house having the license file becomes necessary, and although the home trigger is required such as automatic license renewal, it becomes impossible to cope. Since it can be determined that the license transfer management information was not found when it was inquired from the branch, it was handled in the branch's decision logic by using that information as the result of the inquiry. .

** If you are not a licensed family **
[Device configuration: With license file, no license (After moving to own device, re-moving the license to another device)]
● Operation: Manual license renewal (1) Judge whether it is the home or not and know that it is not the home.
(Pattern A)
(2) Since it is not the head family, it is considered as an error. In addition, it is urged to execute it on the original equipment. (Assuming a pattern to be deployed to other devices after manual license renewal at home)
(Pattern B)
(2) The server is not accessed because it is not the principal, so the principal is informed that a license renewal request has been made, and the principal relegates the license renewal. (Assuming a pattern to be deployed to other devices after manual license renewal at home)
(3) An updated license file is transferred from the head family, receives an update request, performs update processing (without accessing the server) based on the received license file, and completes execution by applying a new expiration date.
In the case of NG in (2) (failed at home, unable to access, etc.), error processing is performed.

● Operation: Automatic license renewal (1) It is determined whether or not it is the original family and it is understood that it is not the original family.
(2) Do not perform automatic license renewal (skip). This is because the server is not accessed because it is not the head family.
(3) Wait for completion of automatic update of the head family (pattern to be deployed to other devices after automatic license renewal at the head family).
(4) Since an updated license file and an update request are received from the head family, update processing (without server access) is performed, and execution is completed when a new expiration date is applied.
If there is no response from the home until the expiration date is over, automatic deactivation will occur, but this device configuration will not be licensed and will be skipped.

● Operation: Deactivation (License return) (1) Judgment of whether or not it is the original family, it can be found that it is not the original family.
(2) It is confirmed whether or not there is a license.
(3) A message indicating that no operation is required since no license has been acquired is displayed.

● Operation: Deletion (deletion of function) (1) It is determined whether or not it is a head family and it is understood that it is not the head family.
(2) It is confirmed whether or not there is a license.
(3) Delete is executed.
In addition, in order to delete the home device by itself, the home device is requested to delete the information of the home device from the license copy information of the home device. (Because the license file is also deleted, it is no longer necessary to link with the home)
(Pattern A)
Deletion can be executed after the replication information correction to the head family is completed.
(Pattern B)
After executing the deletion, a copy information correction request is made to the head family after completion. However, since the license transfer management information has already been deleted for both the license file and the corresponding function, this needs to be handled as a background job that is repeated until the request from the owner and the correspondence with the owner are completed. Therefore, it periodically requests the head family until the duplication information correction is completed. In the unlikely event that the owner prompts the user to update the license, etc. by updating the license before the request for copying information is completed, the license transfer management information has already been deleted and is not necessary. Return the result, and request to delete the device from the relevant copy information.

[Device configuration: With license file and license]
● Operation: Manual license renewal Device configuration: License file present, no license (after moving to own device, re-moving to another device) License: Same as manual license renewal.

● Operation: Automatic license renewal Device configuration: License file present, no license (after moving to own device, re-moving to another device) License: Same as automatic license renewal.

● Operation: Deactivation (License return) (1) Judgment of whether or not it is the original family, it can be found that it is not the original family.
(2) Confirm whether or not there is a license, but you can see that you have a license.
(Pattern A)
(3) Display that the license must be returned to the home by communicating with the server (for example, return the license after moving the license to the home) and display the NG result.
(Pattern B)
(3) The function is returned from this machine, but the license is returned to the server by the head family. Therefore, the license is returned from the own machine to the head house instead of the server. Execution). In addition, a message is displayed indicating that the license of this machine has been returned to the headquarters, and it must be deactivated from the headquarters to return it to the server. (Returning to the server requires home operation)
(Pattern C)
(3) Although the function is returned from this machine, it is the original family that returns the license to the server. Therefore, the license is returned from the own machine to the original family instead of the server, and to the server. Tell the customer that there was a request to return the license, and after returning the license to the headquarters, have the headquarters perform the deactivation process.

The device receives a notification of the completion of the deactivation process at the home and informs the server that the license has been returned. (You may request the deactivation process from the headquarters to finish the flow. In this case, the headquarters will only display that you have requested a license return to the server. Even if deactivation is performed at the home and fails due to disconnection, etc., it can be completed by retry processing at the home.)
● Operation: Deletion (deletion of function) (1) It is determined whether or not it is a head family and it is understood that it is not the head family.
(2) Confirm whether or not there is a license, but you can see that you have a license.
(3) Return the license before deletion. (License return pattern when the license is held at the branch house)
(License return pattern A)
(4) A message indicating that the license must be returned before being deleted and that the license must be transferred to the headquarters for returning the license is displayed, and an error occurs.
(License return pattern B)
(4) When the return of the license to the head family is completed, the deletion is executed. Since license migration management information is also included at the time of deletion, the headquarters is requested to delete the information of the own device from the copy information held by the headquarters. Refer to “Description column for deletion with a license file and no license” for information on correcting the copy information to the original family at the time of deletion.
(License return pattern C)
None. In response to a request to delete the corresponding function on the own machine, the requested range is to delete the license after returning the license to the headquarters (the above-mentioned pattern B). Deletion of the function after the license transfer at the branch house only moves the license to the head family, and further returns the license from the head family to the server.

<Problems with licenses that specify the expiration date and the maximum number of usage>
When the expiration date and the upper limit of usage are further defined in the license, there is a possibility that a situation that does not meet the user's expectation in particular regarding the upper limit of usage may be caused.

  FIG. 10 is a diagram illustrating an example of a license form. FIG. 10A illustrates an example in which an expiration date is defined in a license information file indicating license conditions. FIG. 10B illustrates an upper limit number of use in the license information file. 10C is an example in which the expiration date and the upper limit number of use are defined in the license information file. The expiration date may specify the period from the time of license (such as the date of installation or activation) in addition to the case where the expiration date is shown as in the illustrated example. The use upper limit number indicates the number of printable sheets and the number of times the function is used. The expiration date and the upper limit of usage depend on the contents of the contract.

  FIG. 11 is a diagram illustrating an example of a state when a license is transferred. FIG. 11A is an example when an expiration date is defined in the license information file, and FIG. 11B is used in the license information file. This is an example when the upper limit number is defined. If the expiration date and the upper limit number of use are defined in the license information file, both processes are performed together.

  In FIG. 11A, a predetermined application is introduced in the device A, and the movement from the device A to the device X, from the device X to the device Y, from the device Y to the device Z, and from the device Z to the original device A is repeated. Even if the license information file is expired, the expiration date of the license information file does not change from the initial one, so if the device A that first introduced the application retrieves the license before the expiration date, Functions can be used.

  In FIG. 11B, a predetermined application is introduced by the device A, and the movement from the device A to the device X, from the device X to the device Y, from the device Y to the device Z, and from the device Z to the original device A is repeated. In this case, the remaining usable number (the value obtained by subtracting the usage number from the upper limit number of usage) decreases according to the number of usages of the original device A and the devices X, Y, and Z that pass through, and the application was first introduced. When a license is regained for the device A and used, there is almost no remaining usable number, and there may be a situation where sufficient use cannot be performed.

<Operation protection / license transfer management information use protection setting device and use protection setting level when the use protection setting level is not introduced>
First, a description will be given of usage protection settings in a state where the usage protection setting enabled device and the usage protection setting level are not introduced.

  FIG. 12 is a diagram illustrating an example in which usage protection is set for the device itself before the license is transferred.

  In FIG. 12, the app A is introduced by the device A (step S501). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”, and the use protection number and the use protection target device are not set.

  Thereafter, the user of the device A may transfer the license to another device, but if the device A wants to use “30 times” at least, the use protection is set for the device A (step S502). . With this setting, the usage protection number of the license migration management information of the device A is “30”, the usage protection target device is “device A”, and the available number is “70” obtained by subtracting “30” from the previous “100”. "become.

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S503). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, when the user of the device B uses the function of the app A “40 times” (step S504), the available number of license migration management information of the device B becomes “30” obtained by subtracting “40” from “70”. . Note that if the device B tries to use the function of the application A further, the device B cannot be used beyond the available number “30”, and the use is suppressed when the available number becomes “0”.

  Thereafter, in response to a request from the device A, the license of the application A is transferred from the device B to the device A (step S505). At this time, the license migration management information having the same contents as the immediately preceding device B is held in the device A. In the device A, the function of the application A can be used up to “60” which is the sum of the usable number “30” and the utilization protection number “30”.

  FIG. 13 is a diagram showing an example in which usage protection is set for the own device and other devices before the license is transferred.

  In FIG. 13, the app A is introduced by the device A (step S511). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”, and the use protection number and the use protection target device are not set.

  Thereafter, the user of the device A sets the usage protection of the usage protection number “30” for the device A (step S512).

  Thereafter, the user of the device A sets the usage protection of the usage protection number “20” for the device B (step S513). Note that in order to set not only the directly operated device (device A) but also other devices (device B), service search / device search, which is a prerequisite for acquiring the function list shown in step S201 of FIG. Search for other devices using the above mechanism and set them as usage protection settings.

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S514).

  Since the use protection is already set for the device B, the user of the device B does not need to newly set the use protection if there is no problem with the set number of use protections (step S515). ).

  FIG. 14 is a diagram illustrating an example in which usage protection is set for the own device at the transfer destination after the license transfer.

  In FIG. 14, the app A is introduced by the device A (step S521). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”, and the use protection number and the use protection target device are not set.

  Thereafter, the user of the device A sets the usage protection of the usage protection number “30” for the device A (step S522).

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S523).

  After that, the user of the device B sets the usage protection of the usage protection number “20” for the device B (step S524).

  FIG. 15 is a diagram illustrating an example in which usage protection cannot be set.

  In FIG. 15, it is assumed that application A is introduced (step S531), and usage protection with the usage protection number “30” is set for device A without using the function of application A (step S532).

  Thereafter, in response to a request from the device B, the license of the application A is transferred from the device A to the device B (step S533), and the usage protection with the usage protection number “20” is set for the device B (step S534). ).

  Thereafter, in response to a request from the device C, the license of the application A is transferred from the device B to the device C (step S535). Is not allowed (step S536). That is, “30” is already set for the total of “30” for the device A and “20” for the device B, and the total number of usage protection “50” from the upper limit number “100” is set. This is because the usage protection number “60” cannot be newly set since the usable number obtained by subtracting “” is “50”.

  In this way, when setting up usage protection by multiple devices or users, there is a limit to the maximum number of usage, so it may be possible to set up usage protection in advance, but other usage protection settings If you try to set usage protection after a delay, the number of usage protection has already been set for the maximum number of usage, and the desired number of usage protection cannot be secured. The possibility of not being able to occur arises.

<Use protection settings when a device and use protection setting level are introduced for operation / license transfer management information>
FIG. 16 is a diagram illustrating an example of a difference in setting of usage protection by a device capable of setting usage protection.

  In FIG. 16, the device A introduces the application A (step S541). In this state, the license migration management information of the device A is that when the upper limit number of use is “100”, the available number is “100”, the use protection number and the use protection target device are not set, and the use protection setting is set. Assume that device A is set as the license head for the possible device, and the usage protection setting level is not set.

  Thereafter, the user of the device A may transfer the license to another device, but if the device A wants to use “30 times” at least, the use protection is set for the device A (step S542). . With this setting, the usage protection number of the license migration management information of the device A is “30”, the usage protection target device is “device A”, and the available number is “70” obtained by subtracting “30” from the previous “100”. "become.

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S543). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, the user of the device B tries to set usage protection for the device B. However, since the device B is not set as a device for which usage protection can be set in the license migration management information, setting of usage protection is not allowed (step) S544).

  On the other hand, when the user of the device A sets the device B as a use-protectable device (step S545) while the license is in the device A (step S545), the user of the device B moves from the device A to the device B (step S546). If the device B tries to set the usage protection for the device B, the device B is set as a device that can be set for use protection in the license migration management information, and thus the usage protection setting is permitted (step S547).

  In this way, by setting (restricting) the devices that can be set for use protection in advance, each device can prevent the depletion of the number of usable items that can be set for use protection, and only the appropriate devices that need to be protected for use. You can allow usage protection settings.

  In addition, although the case where the license home device is automatically set as the use protection setting possible device and the case where any device is set by the license home device have been described, in addition, the license is transferred from the other device to the own device. Devices that have already been managed (devices managed as license transfer routes) and devices that have been determined according to the judgment of the setting information of each device (for example, devices installed on the same floor, devices with the same management department or administrator, the same It is also possible to automatically set a device or the like arranged on the LAN.

  FIG. 17 is a diagram illustrating an example of a difference in usage protection setting depending on the usage protection setting level.

  In FIG. 17, the app A is introduced by the device A (step S551). In this state, the license migration management information of the device A is that when the upper limit number of use is “100”, the available number is “100”, the use protection number and the use protection target device are not set, and the use protection setting is set. Assume that device A is set as the license head for the possible device, and the usage protection setting level is not set.

  Thereafter, the user of the device A may transfer the license to another device. However, if the device A wants to use “50 times” at least, the user A is set for use protection (step S552). ), Setting is made so that the use protection can also be set for the device B (step S553). With this setting, the usage protection number of the license migration management information of the device A is “50”, the usage protection target device is “device A”, and the available number is “50” obtained by subtracting “50” from the previous “100”. ”And the devices that can be used and protected for protection become“ device A, device B ”.

  Thereafter, the license of the app A is transferred from the device A to the device B in response to a request from the device B (step S554). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, the user of the device B tries to set the usage protection of the usage protection number “80” for the device B, but the device B is set as a usage protection setting enabled device, but the usage count is “50”. Since the requested usage protection number “80” is insufficient, setting of usage protection is not allowed (step S555).

  On the other hand, when the user of the device A sets the usage protection setting level of the device A to “medium” and the usage protection setting level of the device B to “high” while the license is in the device A (step S556), the device A changes to the device A. After the movement to B (step S557), if the user of device B tries to set the usage protection of the usage protection number “80” for the device B, the usage number is “50” and the required usage protection is requested. Although the number “80” is not enough, device B has a higher usage protection setting level than device A, and therefore, the usage protection setting is allowed by depriving the shortage “30” from the device A usage protection number. (Step S558). As a result, the usage protection number of the device A is “20”, the usage protection number of the device B is “80”, and the available number is “0”.

  Although the devices that can be set for use protection are limited by the settings, only the previous settings are protected, and if you try to set the use protection after a delay, the number of usable items for the maximum number of use is depleted (insufficient) However, you may not be able to set the desired usage protection, but by setting a usage protection setting level for devices that can be set for usage protection, the usage protection of other devices with a lower usage protection setting level than the device itself If there is a set number, you can set up usage protection by taking away the shortfall.

  Although it has been described that when the usage protection setting level is not set, the already set usage protection number is not deprived, the usage protection setting level that is not set is regarded as a default level (for example, “medium”). It may be determined whether or not it can be taken.

In addition, the usage protection setting level can be set by the user by selecting from the specified items such as “low”, “medium”, “high” or “1” “2” “3” “4” “5”. The usage protection setting level may be automatically set (updated at regular intervals) according to the above. For example,
-A method to increase the usage protection setting level as the number of registered users of the device increases (assuming that the usage frequency of the function whose license has been transferred is high)
-A method of setting the usage protection setting level to a higher level as the device usage frequency (for example, printing usage frequency) is higher (assuming that the usage frequency of the function whose license has been transferred is higher)
-If the usage frequency of the function whose license has been moved is low, there is a method to lower the usage protection setting level. The target device only needs to have a license information file, and the presence or absence of a license can be ignored.

  In addition, various reference values (median values) may be used as the initial value of the use protection setting level at the time of license introduction in the licensed home device.

  FIG. 18 is a flowchart illustrating an example of processing for setting use protection.

  In FIG. 18, when a request for setting usage protection with a device name, product ID (or license ID), number of usage protections, etc. is received and processing is started (step S561), the requesting device protects the license migration management information. It is determined whether it is included in the settable device (step S562).

  If it is determined that the device is included in the protection-configurable device (YES in step S562), then it is possible to secure the number of use protections desired by the request source, that is, the number of use protections desired by the request source is the license migration management information. It is determined whether or not the number is less than or equal to the available number (step S563).

  If it is determined that the request source can secure the desired number of usage protections (YES in step S563), the usage protection is set (the number of available license migration management information, the number of usage protections, and the usage protection target device is updated) (step S563). S564). More specifically, the requested use protection number is subtracted from the available number, the requested use protection number is additionally set, and the request source device is additionally set as the use protection target device. Then, the use protection setting ends normally (step S565).

  If it is determined that the desired number of usage protections cannot be secured by the request source (NO in step S563), whether there is something that can be secured (taken away) from the number of usage protections already set, the number of usage protections, and the usage protection target A determination is made based on the device and the use protection setting level (step S566). More specifically, when the sum of the number of available protections and the sum of the number of available usages for devices with a usage protection setting level lower than the usage protection setting level of the requesting device is greater than or equal to the number of usage protections desired by the requesting device Judge that it can be secured.

  If it is determined that it can be secured (YES in step S566), use protection is set (the number of available license migration management information, the number of use protection, and the update of the device subject to use protection) (step S567). More specifically, if the available number is not 0, the number is updated to 0, the amount that is insufficient in the available number is subtracted from the usage protection number of other devices, the requested usage protection number is additionally set, and the request source Set the additional device as a device subject to use protection. In this case, when the number of usage protections is deprived from a plurality of devices, it is desirable to deprive the devices with a low usage protection setting level with priority. If the usage protection setting level is the same, it is desirable to apportion it.

  Next, it is determined from the protection setting notification (including protection setting notification for any device other than the licensed home device) whether or not notification is necessary for the device whose usage protection number has been deprived (step S568).

  If it is determined that notification is necessary (YES in step S568), the device that requires notification is notified that the usage protection number has been deprived (step S569). Then, the use protection setting ends normally (step S565).

  Further, when it is determined that the device is not included in the protection-configurable device (NO in step S562), or when it is determined that the required number of usage protection cannot be secured even if the number of usage protection is deprived from other devices (in step S566). NO) displays on the operation panel of the device that usage protection cannot be set (the desired number of usage protections cannot be secured), and the process ends (step S570).

  In the above description, the target to be protected for use of a license is “device”. However, the target can be “person (user)” instead of “device”. For example, organizational managers such as managers and department heads are required to protect the use of nearby devices because they use more than a certain number of functions. However, it is not always in the same seat, and functions may be used in different places, so use protection may be required regardless of the device.

  In such a case, it is possible to associate the license with the user, not the device, and identify the user by login / logout, thereby enabling the use protection setting, the use protection setting availability, and the control based on the use protection setting level. it can. In this case, it can be realized by managing a “user” instead of the “device” described above. Note that the license associated with the user is not limited to contracting with an individual, but may be used by a plurality of users, and can therefore be associated with a plurality of user groups. In addition to the above-described management mechanism tied to the device, the management mechanism tied to the user can coexist.

<Notification of operation / usage status>
Since the notification when the number of use protections already set has been taken by another device has already been described in part of FIG. 18, other notifications will be described as an example.

  FIG. 19 is a diagram showing an example in which notification is set at the transfer destination after the license transfer.

  In FIG. 19, the application A is introduced by the device A (step S601). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”, and the use protection number and the use protection target device are not set.

  Thereafter, the user of the device A may transfer the license to another device, but if the device A wants to use “30 times” at least, the user A is set to use protection (step S602). . With this setting, the usage protection number of the license migration management information of the device A is “30”, the usage protection target device is “device A”, and the available number is “70” obtained by subtracting “30” from the previous “100”. "become.

  Thereafter, in response to a request from the device B, the license of the application A is transferred from the device A to the device B (step S603). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, when the user of the device B thinks that the user B is notified when the number of usable devices is halved, the user sets the notification for the device B (step S604). With this setting, “35”, which is half of the available number “70”, is set as the notification threshold value of the license migration management information of device B, and the registered user of device B is set as the notification target. If device B loses its license (when the license is transferred to another device), the notification setting (notification threshold, notification target) is invalidated. Since the notification based on this setting is only for the administrator and the user in the own device, it is invalidated when the license is invalidated.

  Thereafter, when the user of the device B uses the function of the app A “35 times” (step S605), the available number reaches the notification threshold value “35”, and the registered user of the device B to be notified is notified ( Step S606). As the content of the notification, for example, “the remaining usage count of application A has been halved (35 times)”.

  FIG. 20 is a diagram showing an example of setting notification in the license original device.

  In FIG. 20, the app A is introduced by the device A (step S611). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”, and the use protection number and the use protection target device are not set.

  Thereafter, the user of the device A may transfer the license to another device, but if the device A wants to use “30 times” at least, the user A is set to use protection (step S612). . With this setting, the usage protection number of the license migration management information of the device A is “30”, the usage protection target device is “device A”, and the available number is “70” obtained by subtracting “30” from the previous “100”. "become.

  After that, when the user of the device A wants to grasp the status of the number of usable licenses as the usage status even after the license is transferred to another device as the licensed home device that has installed the app A, the device A can be set to notify Is performed (step S613). With this setting, the periodic information notification of the license movement management information of the device A is set to “ON”. When it is desired to grasp the usage protection setting status as the usage status, the protection setting notification of the license migration management information of the device A is set to “ON”. These notifications are inherited even if the license is transferred between the devices, and can be reset ON / OFF from the license home device.

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S614). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, when the user of the device B uses the function of the app A “50 times” (step S615), the usable number becomes “20”, which is 20% of the upper limit number of use “100”. The usage status is notified to the device A (step S616).

  In addition, although the case where the user intentionally sets the notification for the license original device has been described, the notification may be automatically set for the license original device in conjunction with the license transfer.

  In addition, the notification for the licensed home device has been described. However, when similar notification is required for other devices, a similar notification is added to the license movement management information by separately adding an item such as “notification subject equivalent to the home”. This can be done by registering the device group to be used.

<License transfer when operation / use protection is set>
FIG. 21 is a flowchart showing an example of processing at the time of license transfer at the license transfer destination device (request source).

  In FIG. 21, the migration source device (request destination) is identified from the license migration destination device, and the license migration process is started (step S701). Regarding the identification of the transfer source device, another device is searched for using the service search / device search mechanism, which is the premise for acquiring the function list shown in step S201 in FIG.

  Next, license information is acquired from the request destination (step S702). The license information includes information such as “available number” for the upper limit number type, and “remaining number of days” for the expiration date type.

  Next, based on the acquired license information, it is determined whether or not the license transfer is actually performed (step S703). Details will be described with reference to FIG.

  Next, when it is determined that the license can be transferred (YES in step S703), an inquiry is made as to whether the request can be immediately executed (step S704).

  If there is a reply that the request can be executed immediately (YES in step S704), the license transfer is executed (step S705). That is, a new installation is performed when the license is moved and the function is not installed in the own machine, and a process such as license activation is performed when only the license is activated after being installed. Thereafter, the license transfer is completed (step S706).

  If it is determined that the license is not transferred (NO in step S703) or if it is determined that the license cannot be transferred (NO in step S704), the license transfer is not performed (step S707). In step S704, since it may happen that the function associated with the requested license is executed by the request destination device by chance, it may be impossible to execute immediately. Therefore, a fixed number of retries are executed every fixed time. It is also possible. However, this is not the case when it is determined that the license transfer is canceled because the number of usable devices required by the own device is less than the determination in step S703.

  FIG. 22 is a flowchart showing an example of processing for determining whether or not a license can be transferred (step S703 in FIG. 21).

  In FIG. 22, when the determination process is started (step S711), it is determined whether or not the license is a type based on the use upper limit number (step S712).

  If it is determined that the type is not the upper limit number (NO in step S712), the license transfer request to the request destination is confirmed (step S715), the determination result (transfer confirmation) is transmitted to the request destination, and the process is terminated. (Step S716). In addition, if it is not the upper limit number type, that is, if it is the expiration date type, it is determined that the movement request is confirmed, but the expiration date is compared with the current date and time, and if there is no more than a certain number of days, the use value is low ( It is also possible to cancel the movement request.

  If it is determined that the number is the upper limit type of use (YES in step S712), it is then determined whether a threshold is set as the minimum number of times of use (step S713). The requesting user has a threshold value such as “I want to use at least this”, so when the setting on the requesting side is simply set (when it is judged to move if it can be used even at least once), the requesting user Can be discouraged. When judging the number of days that can be used from the expiration date and the current date and time, the threshold value may be the number of days.

  If it is determined that the threshold is not set (NO in step S713), the license transfer request to the request destination is confirmed (step S715), the determination result (transfer confirmation) is transmitted to the request destination, and the process is terminated. (Step S716).

  When it is determined that a threshold value is set (YES in step S713), the available number acquired from the request destination (the available number and the used protection number when the usage protection for the destination device is set) It is determined whether or not (sum of) exceeds a threshold that is to be used at least by the own device (step S714).

  If it is determined that the threshold value is exceeded (YES in step S714), the license transfer request to the request destination is confirmed (step S715), the determination result (transfer confirmation) is transmitted to the request destination, and the process ends (step S716). ).

  If it is determined that the threshold value is not exceeded (NO in step S714), it is determined that the desired number of times cannot be used and the movement is not performed (step S717), and the determination result (movement request cancellation) is transmitted to the request destination. The process ends (step S718).

  FIG. 23 is a flowchart showing an example of processing at the time of license transfer at the license transfer source device (request destination).

  In FIG. 23, when the determination process is started (step S721), the license information held by itself is transmitted to the request source in response to the request from the request source (step S722).

  Next, based on the license information held by the own device, it is determined whether or not the license is actually transferred (step S723). Details will be described with reference to FIG.

  Next, when it is determined that the license can be transferred (YES in step S723), available information (for example, the available number after the license is transferred) is transmitted to the request source, and an inquiry is made as to whether or not the license is transferred (step S724). In addition, after accepting the license transfer request from the request source, the request source is informed of the number of available licenses after the license transfer, and the final decision is made. When the call is made, each searched device may transmit available information.

  Next, the final determination at the request source is acquired, and it is determined whether or not the movement is executed (step S725).

  If it is determined that the transfer is to be executed (YES in step S725), it is determined whether the license transfer can be executed immediately (step S726). As license availability information, even if the license can be transferred, when the license is being transferred, the function cannot be moved while it is being used. Check if a reservation has been made.

  If it is determined that the license transfer can be executed immediately (YES in step S726), the license transfer is executed (step S727). That is, the corresponding function is made unusable on the own machine (deactivation or invalidation that makes the corresponding function unusable on the own machine), and the corresponding license information is notified to the request source (duplicate license necessary for transfer). Thereafter, the license transfer is completed (step S728).

  On the other hand, when it is determined that the license transfer is not possible (NO in step S723), when it is determined that the final determination of the request source is not transfer execution (NO in step S725), or when it is determined that the license transfer is not immediately executable (NO in step S726) notifies the request source that the license cannot be transferred and ends the process (step S729).

  FIG. 24 is a flowchart showing an example of processing for determining whether or not a license can be transferred (step S723 in FIG. 23).

  In FIG. 24, when the determination process is started (step S731), it is determined whether or not the license is a type based on the use upper limit number (step S732).

  When it is determined that it is not the use upper limit number type (NO in step S732), information indicating that movement is possible and additional information (such as how many times it can be used from the calculation result) are created (step S734), and movement is performed. The process is terminated after notification of the possibility (step S735). In addition, if it is not the upper limit number type, that is, if it is the expiration date type, it is determined that the movement request is confirmed, but the expiration date is compared with the current date and time, and if there is no more than a certain number of days, the use value is low ( It is also possible to cancel the movement request.

  When it is determined that the type is the upper limit number type (YES in step S732), the available number (the sum of the available number and the used protection number when the use protection for the destination device is set) is obtained. It is determined whether or not a certain number or more (step S733). Here, a certain number can be set. The value judgment is for each person, for example, it is judged to be valuable if it can be used even once.

  If it is determined that the number of usable items is equal to or greater than a certain number (YES in step S733), information indicating that movement is possible and additional information (how many times it can be used from the calculation result) are created. (Step S734), the movement is notified and the process is terminated (Step S735).

  On the other hand, if it is determined that the number of usable items is not equal to or greater than a certain number (NO in step S733), it is determined that no meaningful use is possible even if the license is transferred (step S736), and the process ends. (Step S737).

  If the user sets a threshold value such as “I want to use at least this” at the request source, information on the threshold value is acquired at the request destination, and the number of usable devices (use protection for the destination device) In the case where is set, it may be determined whether or not the sum of the available number and the use protection number) exceeds the threshold.

<License transfer when operation / use protection is set>
FIG. 25 is a diagram showing an example of display of consumption of the number of uses and remaining usable number.

  In FIG. 25, the application X is introduced into the device A, usage protection for the device A is set, and the function of the application X is not used in step S801. In the license migration management information in this state, it is assumed that the usage upper limit number is “100”, the usage protection target device is “device A”, the usage protection number is “30”, and the usable number is “70”.

  Then, considering the case where the function of the application X is used “20 times” in the device A, the usage count “20” is counted so as to be consumed from the available number, or it is consumed from the usage protection number of the device A. There are two ways of counting.

  Step S802 shows a case of counting from the usable number (when the usable number runs out, counting from the number of protected usages), and the usable number is subtracted from the previous “70” by the number of times of use “20”. It is “50”. In this method, since the usage protection number is consumed after the usable number is exhausted, it can be expected that the device A will be fully utilized.

  Step S803 shows a case of counting from the usage protection number of the device A (when the usage protection number is lost, counting from the available number), the usage protection number is changed from “30” to “20”. It is deducted to “10”. In this method, since it is consumed from the number of usage protections, it can be expected to efficiently promote minimum usage.

  There are also some patterns in how to define the number of remaining available numbers to be displayed to the user.

  In step S804, the total number of usage protections and available numbers is displayed as the remaining available number for the license migration management information in step S803. Suitable for telling exactly how much more is actually available.

  In step S805, the number of protected usages is displayed as the remaining usable number for the license migration management information in step S803. By displaying the remaining number of usage protections, it is possible to prevent excessive usage in anticipation of license transfer to other devices, such as resetting usage protection as necessary.

  In step S806, the available number is displayed as the remaining available number for the license migration management information in step S803. By displaying the remaining number of available numbers and not displaying the number of protected usages as a guarantee, it is possible to use the number of protected usages even if the remaining number of available usages appears to be zero. Can be expected to guarantee

<Problems caused by usage protection>
By introducing devices that can be used for protection and usage protection setting levels, even if new usage protection cannot be performed due to the usage protection already performed by other devices, the number of other devices can be protected under the specified conditions. The functions that can be taken are described above.

  However, after setting usage protection on a device, when deleting the corresponding function on the device, returning the corresponding license, or moving the corresponding license in response to a request from another device However, although there is a low possibility that the corresponding license will be used in the future in the device, there is a problem that only the usage protection remains and the number of usage protections that are not used is generated, resulting in inefficiency.

  FIG. 26 is an explanatory diagram of problems caused by the function deletion corresponding to the license.

  In FIG. 26, the app A is introduced by the device A (step S901). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”, and the use protection number and the use protection target device are not set.

  After that, the user of the device A may transfer the license to another device, but if the device A wants to use “50 times” at least and the device B wants to be able to set use protection, The usage protection is set for the device A, and the device B is also set as the usage protection setting device (step S902). With this setting, the usage protection number of the license migration management information of the device A is “50”, the usage protection target device is “device A”, and the available number is “50” obtained by subtracting “50” from the previous “100”. "become. Further, the device that can be set for use protection is “device B”.

  Thereafter, in response to a request from the device B, the license of the application A is transferred from the device A to the device B (step S903). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, the user of the device A determines that the device A will not use the app A in the future and deletes the function (step S904), but the license transfer management information is not changed.

  After that, the user of the device B tries to set the use protection on the device B, but the usable number is “50” because the use protection number of the device A is “50”, and the future use on other devices is Therefore, a sufficient number of usage protections cannot be set, and the usage protection number “10” is set for the device B (step S905). With this setting, the usage protection target device is “device A device B”, the usage protection number is “50 10”, and the available number is “40”.

  In this way, even if it is determined that the device A will not use the app A in the future and the function is deleted, a sufficient number of devices such as the device B and subsequently the license transfer are available due to the use protection set in the device A. There is a possibility that the use protection of can not be performed. Of course, a device with a high use protection setting level can take away the use protection that has already been set, but it is considered that there will be more devices that are not set with a high use protection setting level, and the use protection set by device A will not be used. Without being obscured, it will only interfere with the use of other devices.

  FIG. 27 is an explanatory diagram of problems caused by license return and license transfer.

  In FIG. 27, it is assumed that an application is installed in the device A (step S911), and “30 times” use protection is set for the device A in a state where the function is not used (step S912). If the upper limit number of use is “100”, the use protection target device is “device A”, the use protection number is “30”, and the available number is “70”. Although illustration is omitted, it is assumed that “device B device C” is also set as a device that can be set for use protection.

  After that, the license is transferred from the device A to the device B without using the application on the device A (step S913), and “20 times” use protection is set on the device B (step S914). With this setting, the usage protection target device is “device A device B”, the usage protection number is “30 20”, and the available number is “50”.

  After that, the license is transferred from the device B to the device C without using the app on the device B (step S915), and the device C provides the use protection of “20 times” from the available number “50” to the possible range. It is assumed that it has been set (step S916). With this setting, the use protection target device is “device A device B device C”, the use protection number is “30 20 20”, and the available number is “30”.

  After that, when a license is returned from the device C to the device A that has installed the application (step S917), the license migration management information of the device A is in the same state as the immediately preceding device C.

  In this case, even if the device C that has returned the license or the device B that has transferred the license does not intend to use the app in the future, the user of the device A is restricted by the usage protection set by the devices B and C. This makes it difficult to set additional usage protection.

<Method of solving problems caused by usage protection>
In the license form that manages the presence / absence of licenses with the maximum number (for example, the number of printable sheets) linked to the device or user, protection of use in each device (for example, XX of the maximum number of printable sheets is used only on the A machine. In case of function deletion on the corresponding device, license return, license transfer due to transfer request from other devices, etc., the already set usage protection will be released according to the conditions (period, priority, etc.) I am doing so. Further, the surplus usage protection number is distributed to other devices by canceling the usage protection. Thereby, it is possible to effectively utilize the surplus use protection number (use count) that may not be used, and to realize more efficient resource management without causing any disadvantage to the user.

  Cancel the usage protection settings in the following cases.

・ When deleting a function with a use protection setting (with a license), cancel the use protection setting of the machine that has been set. ・ When returning a license with a use protection setting, Canceling the use protection setting for a function ・ When a function transfer request is received from another device with a function for which use protection is set (licensed), the conditions (such as a certain number or less remaining in the license form including the expiration date) In response, cancel the use protection setting of the device that has already been set. When depriving the use protection number of other devices under the specified conditions according to the above-mentioned use protection setting level, move it from the viewpoint of the user (user) that you want to move to the end. You can set the usage protection for the license you want to move, and if you don't have enough, you can overwrite the usage protection according to the priority from the other set usage protection and get the number of usage protection you want to get. To to have been the subject. The cancellation of the use protection setting is a viewpoint of what is to be done when requested by another device, and what is to be done when deletion / return is carried out by a third party, not limited to itself.

The surplus distribution (distribution pattern, distribution destination)
-With the cancellation of the usage protection setting, it is returned to the number of times that the license is not used for other usage protection, etc. With the cancellation of the usage protection setting, the license is subject to conditions (priority etc.) for other usage protected devices Depending on the corresponding equipment use protection, it will be reduced.

<Surplus distribution setting and surplus distribution destination setting>
FIG. 28 is a diagram illustrating an example of a setting screen for setting surplus distribution.

  In FIG. 28, after the use protection setting, the screen I1 is displayed by pressing the device surplus distribution method setting menu. On this screen I1, a distribution method can be selected by a “Return to Usable Number” button and a “Return to Other Device” button. It can also be set later with the “Cancel” button.

  When the “Return to available count” button is selected, the screen I2 is displayed. In this screen I2, it is notified that the usage protection setting is canceled and the number of times that the device can be used in common with other devices is returned, and the screen is closed by pressing the “Close” button.

  When the “Return to other device” button is selected, the process proceeds to the next surplus distribution destination setting.

  FIG. 29 is a diagram showing an example of a setting screen for setting a surplus distribution destination.

  In FIG. 29, after setting the return to another device in the surplus distribution method setting, the screen I3 is displayed by pressing the surplus distribution destination setting menu of the device. In this screen I3, the “Master device” button, “Active device (holding rights)” button, “Device with maximum protection setting” button, “Device with maximum protection setting level” button, and “Device designation” button are used for distribution destinations. Can be selected. The master device is the original device that first introduced the license. It can also be set later by a “cancel” button.

  When “device designation” is selected, the screen I4 is displayed. In this screen I4, the device candidates that can be set are acquired using the information on the license copy device in the license transfer management information (information indicating the route the license has been copied and moved between devices), and these are selected by the button. It becomes possible. By displaying not only the number of protected usages that are included in the license movement management information and are candidates for determination of the distribution destination, but also information on the device itself (for example, the installation location) is provided, thereby providing the user with more information for determination. . It is also possible to return to the previous screen I3 by the “Return” button.

  If any item other than “device designation” is selected on the screen I3 except “Cancel”, the screen I5 is displayed. This screen I5 exemplifies the case where “maximum use protection setting device” is selected, and displays device information. For other “master device”, “active device (right holding)”, and “device with the maximum protection setting level”, information on the corresponding device is displayed in the same manner. It is also possible to return to the previous screen I3 by the “Return” button.

  When a device is selected on the screen I4 or the “Confirm” button is pressed on the screen I5, the screen I6 is displayed. On this screen I6, the fact that the setting of the distribution destination has been completed, the return destination device, the number of protected use before and after return are displayed. Press the “Close” button to close the screen.

<License renewal processing for cancellation and distribution of usage protection>
FIG. 30 is a flowchart illustrating an example of a license update process when a function corresponding to a license is deleted, when a license is returned, and when a license is transferred in response to a request from another device.

  In FIG. 30, when the process is started (step S921), it is determined whether or not use protection is set in the license of the own device (step S922).

  If it is determined that usage protection is set (Yes in step S922), it is then determined whether there is a surplus in the usage protection setting (step S923).

  If it is determined that there is a surplus (Yes in step S923), the distribution setting (usable number reduction, return pattern to other devices) is referred to and it is determined whether or not other devices are distributed (step S924).

  If it is determined that the distribution setting is not other device distribution (No in step S924), the use protection of the own device is canceled and the surplus is returned to the available number (step S925).

  If it is determined that the distribution setting is other device distribution (Yes in step S924), another device to be a distribution destination is selected (step S926). As a distribution destination selection pattern, “a maximum number of usage protection settings”, “a maximum usage protection setting level”, “master device”, or the like can be considered. Other than the master device, there may be a device with the same value. In that case, the number of registered users of the device is large (the more the device is judged to be used, the more the device is used), the same floor (installation location), etc. It may be possible to make a decision in consideration of the usage frequency and environment.

  Next, the use protection of the own device is canceled, and the surplus is returned to the use protection number of the distribution destination device (step S927).

  If it is determined that usage protection has not been set after the reduction of the surplus (steps S925 and S927) (No in step S922), or if it is determined that there is no surplus (No in step S923), license transfer This is reflected in the management information (step S928), and the process ends (step S929). In addition, the update necessary for the license migration management information is also performed as described above.

As for the synchronization timing with other devices after license update,
・ After the license transfer, the license holding device is updated. ・ After the license transfer, the license holding device uses the function for a certain number of times.
・ After the license transfer, every time the license non-holding device is set is assumed.

  FIG. 31 is a diagram showing an example when license transfer and function deletion are performed.

  In FIG. 31, the app A is introduced by the device A (step S931). In the license migration management information of the device A in this state, when the upper limit number of use is “100”, the available number is “100”. The number of use protections, use protection target devices, use protection settable devices, use protection setting levels, surplus distribution settings, and surplus distribution destination settings are not set.

  After that, the user of the device A may transfer the license to another device, but the device A wants to use “50 times” at a minimum, and the device B can also set use protection and want to increase the priority. Further, when the surplus distribution destination is considered to be the device B, the use protection is set for the device A, the device B is also set as the use protection setting device, the use protection setting level is set high, and the surplus distribution is set. The surplus distribution destination setting is set in the device B with the other device set (step S932). With this setting, the usage protection number of the license migration management information of the device A is “50”, the usage protection target device is “device A”, and the available number is “50” obtained by subtracting “50” from the previous “100”. "become. Further, the use protection setting possible device is “device B”, the use protection setting level is “high”, the surplus distribution setting is “other device”, and the surplus distribution destination setting is “device B”.

  Thereafter, in response to a request from the device B, the license of the application A is transferred from the device A to the device B (step S933). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, the user of the device A determines that the device A will not use the app A in the future, and deletes the function (step S934). At this time, the use protection number of the device A is returned to the device B by the processing described with reference to FIG. In the license migration management information reflected on the device B, the usage protection number is “50” and the usage protection target device is “device B”. Other information remains the same.

  FIG. 32 is a diagram showing an example in the case where license transfer and function deletion are performed. The difference from FIG. 31 is that the license is transferred and the function is deleted after the function is used to some extent.

  In FIG. 32, when the application A is installed in the device A, the upper limit number of license transfer management information is “100” and the available number is “100”, and the user of the device A may transfer the license to another device. Assume that the device A wants to use “50 times” at least, the device B can also set use protection to increase the priority, and further consider the surplus distribution destination as the device B. In this case, the usage protection is set for the device A, the device B is also set as the usage protection setting device, the usage protection setting level is set high, and the surplus distribution setting is set as the other device with the surplus distribution destination setting. Set to device B (step S941). With this setting, the usage protection number of the license migration management information of the device A is “50”, the usage protection target device is “device A”, and the available number is “50”. Further, the use protection setting possible device is “device B”, the use protection setting level is “high”, the surplus distribution setting is “other device”, and the surplus distribution destination setting is “device B”.

  Thereafter, when the function is used only 10 times by the device A (step S942), the usable number becomes “40”.

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S943). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, the user of the device A determines that the device A will not use the app A in the future, and deletes the function (step S944). At this time, the use protection number of the device A is returned to the device B by the processing described with reference to FIG. In the license migration management information reflected on the device B, the usage protection number is “50” and the usage protection target device is “device B”. Other information remains the same.

  FIG. 33 is a diagram showing an example when license transfer and function deletion are performed. FIG. 32 is different from FIG. 32 in that FIG. 32 consumes (subtracts) from the available number by using the function, whereas FIG. 33 consumes (subtracts) from the use protection number.

  In FIG. 33, when the application A is installed in the device A, the upper limit number of use of the license movement management information is “100” and the usable number is “100”, and the user of the device A may transfer the license to another device. Assume that the device A wants to use “50 times” at least, the device B can also set use protection to increase the priority, and further consider the surplus distribution destination as the device B. In this case, the usage protection is set for the device A, the device B is also set as the usage protection setting device, the usage protection setting level is set high, and the surplus distribution setting is set as the other device with the surplus distribution destination setting. Set to device B (step S951). With this setting, the usage protection number of the license migration management information of the device A is “50”, the usage protection target device is “device A”, and the available number is “50”. Further, the use protection setting possible device is “device B”, the use protection setting level is “high”, the surplus distribution setting is “other device”, and the surplus distribution destination setting is “device B”.

  After that, when the function is used only 10 times in the device A (step S952), the number of protected use of the device A becomes “40”. As the number of usage protections, it is desirable to keep the current number of usage protections and the number of usage protections at the time of setting together in order to inform the user of the usage status through screen display. However, you may subtract as it is from the use protection number.

  Thereafter, in response to a request from the device B, the license for the application A is transferred from the device A to the device B (step S953). At this time, the license migration management information having the same content as that of the immediately preceding device A is held in the device B.

  Thereafter, the user of the device A determines that the device A will not use the app A in the future, and deletes the function (step S954). At this time, the use protection number of the device A is returned to the device B by the processing described with reference to FIG. In the license migration management information reflected on the device B, the usage protection number is “40” and the usage protection target device is “device B”. Other information remains the same.

<License renewal process when transferring license in license form including maximum number of usage and expiration date>
FIG. 30 illustrates an example of license update processing when a function corresponding to a license is deleted, when a license is returned, and when a license is transferred due to a request from another device. It is desirable to use another form of processing when moving. In other words, every time a license transfer request is issued, the process of canceling the use protection according to the logic is advantageous for the license transfer request side, but depending on the frequency of occurrence for the license handing side (request receiving side) This is because the work of setting the use protection again may occur. The advantages and disadvantages differ depending on the position, but of course the license transfer request is executed, and the processing of FIG. 30 may be performed at the time of the license transfer request giving priority to the position of the other device user who wants to use the function. Good.

  FIG. 34 is a processing example corresponding to the case where the license form includes the upper limit number of use and the expiration date as shown in FIG. 10C when the license is transferred in response to a request from another device. By determining not only the upper limit number of use but also the expiration date, it is possible to further improve user convenience.

  For example. If the license expires less than one month and is protected for use, when the user intends to use it within the remaining period, the use protection is canceled when a transfer request is received from another device. Since it is assumed that the user wants to avoid being unusable, there is use protection, and if the remaining period is within a certain number, it is possible to realize a response that a movement request from another device is not accepted. This is only a process for a license transfer request, and after the license is returned by the own device, it is possible to transfer the license as a result in a case where the license securing process is executed by another device.

  In FIG. 34, when processing is started (step S961), it is determined whether usage protection is set in the license of the own device (step S962).

  If it is determined that the usage protection is set (Yes in step S962), it is then determined whether it is a license transfer request and the number of remaining days of the expiration date is equal to or less than a certain number (step S963).

  If it is a license transfer request and it is determined that the number of days remaining in the expiration date is not less than a certain number (No in step S963), the license transfer request is allowed, and then whether there is a surplus in the usage protection setting Judgment is made (step S964).

  If it is determined that there is a surplus (Yes in step S964), the distribution setting (usable number reduction, return pattern to other device) is referred to and it is determined whether or not the other device is distributed (step S965).

  If it is determined that the distribution setting is not other device distribution (No in step S965), the use protection of the own device is canceled and the surplus is returned to the available number (step S966).

  When it is determined that the distribution setting is other device distribution (Yes in step S965), another device as a distribution destination is selected (step S967). As a distribution destination selection pattern, “a maximum number of usage protection settings”, “a maximum usage protection setting level”, “master device”, or the like can be considered. Other than the master device, there may be a device with the same value. In that case, the number of registered users of the device is large (the more the device is judged to be used, the more the device is used), the same floor (installation location), etc. It may be possible to make a decision in consideration of the usage frequency and environment.

  Next, the use protection of the own device is canceled, and the surplus is returned to the use protection number of the distribution destination device (step S968).

  If it is determined that the usage protection is not set after the reduction of the surplus (Steps S966 and S968) (No in Step S962), or if it is determined that there is no surplus (No in Step S964), the license transfer This is reflected in the management information (step S969), and the process ends (step S970). In addition, the update necessary for the license migration management information is also performed as described above.

  If it is a license transfer request and it is determined that the number of remaining days for the expiration date is equal to or less than a predetermined number (Yes in step S963), the license transfer request is rejected (step S971). In this case, the request source is notified, and the request source displays a message such as “Use protection is provided and the expiration date is below a certain number, so the device user is given priority and the license transfer request has been cancelled.” .

  In the processing example of FIG. 34, the license transfer request is rejected if the remaining number of days of expiration date is less than a certain number. However, if the number of days for expiration date is less than a certain number, the condition is changed to allow the license transfer request. May be. In addition, by making it possible to set a certain number, it is possible to provide rules suitable for the user.

  In addition, the behavior as “License including expiration date + upper limit of use” was shown. For example, trial license (free version for a limited time) is more suitable for “license type” such as unconditional release of usage protection for transfer requests. It is also possible to make a behavior (release judgment).

<Confirmation when deleting functions and returning licenses>
In step S924 in FIG. 30 (step S965 in FIG. 34), there may be a case where the distribution destination is not set in the determination of the distribution destination setting when there is usage protection and surplus. In this case, when deleting a function or returning a license in the operation unit of the corresponding device, for example, “Caution: Number of times of printing is protected for use.” Deletion / license of the corresponding function Can you provide a screen that prompts the user to confirm, such as "Do you want to return?" As a result, it is possible to prevent a third party other than the user who introduced the license from the corresponding device from deleting the function without permission.

  When “deletion of function / license return” is executed continuously even after the confirmation screen is displayed, it may be possible to remove the surplus from the protection target as a default process and return it as a usable count.

  The user operating on the device can confirm the cases such as deleting these functions or returning the license, and when there is a move request from another device (when another device is executed with high priority). Can be dealt with in the same way.

  FIG. 35 is a diagram showing an example of a confirmation screen when a function corresponding to a license is deleted or a license is to be returned. When a function deletion or license return is requested in a state where there is a surplus of usage protection, a distribution method is shown. When the distribution destination has been set, the screen I7 is displayed. When the distribution method and the distribution destination are not set, the screen I8 is displayed.

<Notification to related parties>
When a reduction for the use protection setting surplus is executed, it is possible to prompt confirmation of increase / decrease in the number of use protection by notifying the administrator of the device related to the return. As a result, it is possible to notify the situation to a user who does not know that the use protection (surplus) has been reduced.

The notification is assumed to be performed as follows.
-If the excess device is distributed to other devices when the function is deleted or the license is returned on the corresponding device, the relevant device administrator and the device administrator of the return destination are notified.
-If a surplus is distributed to another device when the corresponding device responds to a license transfer request from another device, a notification is sent to the device manager and the device manager of the return destination.
-If the surplus is distributed to the available number of times when responding to a license transfer request from another device, the device administrator is notified (the number of times it can be used) That means that other devices can make further use protection settings.)

  Note that a device that is a notification destination can be acquired by using the license movement route information. It is conceivable that a notification destination (administrator destination) is stored in advance along with the movement route information, or the administrator destination information is acquired after determining the corresponding device.

<Systematization>
Although the above-described processing is assumed to be performed by individual devices, a configuration in which part of the processing performed by the devices is delegated to an external server is also conceivable.

  FIG. 36 is a diagram showing an example of systematization in which a part of the processing is shared by the server. The server side is responsible for whether or not to cancel the use protection setting including the distribution method and the determination of the distribution destination.

  Although it can be a merit for the user to determine the distribution in each device, according to this configuration, it can be easily managed by treating it as a rule that is unified as a system administrator, and can be a merit for the system administrator.

  Also, a combination of the judgment of each device and the rules in the system (for example, by giving priority to each rule, the distribution judgment in the device is compared with the distribution judgment inquired from the server, and the priority distribution rule is followed. Etc.).

  In FIG. 36, when a function is deleted or a license is returned to a device (step S981), if there is a surplus of usage protection, a distribution method and distribution destination inquiry is performed from the device to the server (step S982). ).

  The server determines the distribution method and the distribution destination (step S983), and gives the determined distribution method and distribution destination instructions to the device (step S984). The device cancels and distributes the usage protection settings according to the instructions.

<Summary>
As described above, according to the present embodiment, as a mechanism for transferring functions / licenses between devices, information such as the presence / absence of a new license is managed separately from the presence / absence of a license file provided from the license management system. Therefore, the installed software license can be easily transferred to another device without requiring a license key and without burdening the user. Further, it is possible to prevent the use exceeding the number of licenses issued by the license management system, thereby preventing unauthorized use.

  Further, even with a license for which the upper limit number of use is defined, efficient resource management can be performed without causing any unexpected disadvantage to the user as a result of movement.

  Furthermore, even when a new usage protection cannot be performed due to the previous usage protection by another device, the actual operation can be performed by depriving the usage protection number of the other device under a predetermined condition.

  Furthermore, after setting usage protection on a certain device, when deleting the corresponding function on the device, returning the corresponding license, or returning the corresponding license in response to a request from another device Since it is unlikely that the corresponding license will be used in the future in the device, efficient operation can be performed by canceling the use protection and returning it to the available number or the number of other devices used.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

DESCRIPTION OF SYMBOLS 1 Image forming apparatus 101 System bus 102 System control part 103 Display part 104 Operation part 105 External communication part 106 Job management part 107 Reading device part 108 Image memory part 109 Image processing part 110 Printing part 111 Installation management part 112 License file management part 113 License Transfer Management Department

JP 2006-018402 A

Claims (20)

Installation means for downloading and installing software installation data corresponding to a predetermined function from the outside;
License file acquisition means for acquiring a license file from the outside in order to activate the function;
Separately from the presence or absence of the license file, license presence / absence management means for managing the presence or absence of the license of the function,
When the license file defines the maximum number of usages that can use the function, the number of usage protections that the function cannot be used by other devices within the range of available numbers obtained by subtracting the actual usage number from the maximum usage number Use protection management means for managing
A license transfer means for transferring a license between devices and updating the presence or absence of a license for the corresponding function;
An information processing apparatus comprising: function control means for controlling the use of the function from the upper limit of use and the number of protection of use. The information processing apparatus according to claim 1,
An information processing apparatus comprising means for notifying a usage status of the license at a predetermined timing to a predetermined destination. The information processing apparatus according to claim 1, wherein:
The information processing apparatus, wherein the license transfer unit rejects a license transfer request when the number of functions that can be used after the license transfer is less than a predetermined value. The information processing apparatus according to any one of claims 1 to 3,
The information processing apparatus, wherein the license transfer unit rejects a license transfer request when a period during which the function can be used after the license transfer is less than a predetermined value. The information processing apparatus according to any one of claims 1 to 4,
The function control means is configured to be able to select the consumption of the number due to the use of the function in preference to either the available number or the use protection number set for the own device. A characteristic information processing apparatus. The information processing apparatus according to any one of claims 1 to 5,
The function control means may be any one of the available number, the use protection number set for the own device, or the total number of the available number and the use protection number as the remaining available number to be displayed to the user. An information processing apparatus that can be selected based on one of the two. The information processing apparatus according to any one of claims 1 to 6,
The usage protection management means sets the usage protection number by depriving the usage protection number already set for another device when setting of a new usage protection number exceeding the available number is requested. An information processing apparatus characterized by that. The information processing apparatus according to claim 7,
An information processing apparatus comprising means for setting a use protection setting target device that limits devices that can be set for use protection. The information processing apparatus according to claim 8,
An information processing apparatus comprising: means for setting a usage protection setting level indicating a priority that does not cause the other devices to deprive the usage protection number. The information processing apparatus according to any one of claims 7 to 9,
An information processing apparatus comprising means for notifying a destination associated with a device whose usage protection number has been deprived that the number of usage protections has been deprived. In the information processing apparatus according to any one of claims 1 to 10,
When deleting the function, when returning the license, or when moving the license in response to a request from another device, when there is a license usage protection number corresponding to the information processing apparatus, An information processing apparatus comprising means for canceling the use protection number. The information processing apparatus according to claim 11,
An information processing apparatus comprising: means for reducing the usage protection number to the usable number or the usage protection number of another device according to a user setting when canceling the usage protection number. The information processing apparatus according to claim 12,
As other devices to which the number of usage protections is returned, the device that becomes the head of the corresponding function, the device with the maximum number of usage protections for the corresponding function, the device with the maximum usage protection setting level for the corresponding function, and the license for the corresponding function An information processing apparatus capable of selecting either a currently held device or a user-specified device. The information processing apparatus according to any one of claims 11 to 13,
When the license is transferred in response to a request from another device, the license includes means for determining whether the license can be transferred based on the upper limit number of use and the expiration date when the license includes an expiration date An information processing apparatus characterized by that. The information processing apparatus according to any one of claims 11 to 14,
When deleting the function or returning the license, if there is a license protection number corresponding to the information processing device, how to handle the license protection number corresponding to the information processing device An information processing apparatus comprising means for displaying on the screen of the information processing apparatus. The information processing apparatus according to any one of claims 11 to 15,
An information processing apparatus comprising: means for notifying an administrator of another device of cancellation of the use protection number. The information processing apparatus according to any one of claims 11 to 16,
An information processing apparatus comprising means for inquiring an external server as to whether or not the usage protection number can be canceled. A computer constituting the information processing apparatus;
Installation means for downloading and installing software installation data corresponding to a predetermined function from the outside,
A license file acquisition means for acquiring a license file from the outside in order to activate the function;
Separately from the presence or absence of the license file, license presence / absence management means for managing the presence or absence of a license for the function,
When the license file defines the maximum number of usages that can use the function, the number of usage protections that the function cannot be used by other devices within the range of available numbers obtained by subtracting the actual usage number from the maximum usage number Use protection management means to manage,
A license transfer means for transferring a license between devices and updating the presence or absence of a license for the corresponding function;
An information processing program that functions as a function control unit that controls use of the function from the upper limit number of use and the use protection number. The information processing program according to claim 18,
The usage protection management means sets the usage protection number by depriving the usage protection number already set for another device when setting of a new usage protection number exceeding the available number is requested. Information processing program. The information processing program according to any one of claims 18 and 19,
When the computer deletes the function, returns the license, or moves the license in response to a request from another device, there is a license usage protection number corresponding to the information processing apparatus. And an information processing program that further functions as a means for canceling the number of protected usages.