JP2013047900A - Information processor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily move a license of introduced software to the other apparatus without requiring any license key, and to automatically return the license to a desired apparatus after the movement of the license between apparatuses each of which has the license of software managed by a license management system.SOLUTION: The information processor includes: means for acquiring a license file from the outside in order to activate a function of downloaded software; means for managing the presence/absence of the license of the function regardless of the presence/absence of the license file; means for moving the license between apparatuses, and for updating the presence/absence of the license of the function; means for returning the moved license to a predetermined apparatus in accordance with set automatic return conditions; and means for determining license configuration to be restored from a plurality of license configuration management information set by a user, and for moving the license between the apparatuses.

Description

  The present invention relates to a technology for managing software licenses (use rights) used in various devices (information processing apparatuses) such as PCs (Personal Computers) and copiers.

  Conventionally, a license management system is used when software is installed in various devices including not only a PC but also a copying machine. As a server, the license management system is accessed from each device when installing software or obtaining a license after installation, and issues a license in exchange for information unique to the device to be installed. As a result, each device can use the software, and the license management system can prevent unauthorized use of the software other than the device to be installed.

  Incidentally, there are cases where it is desired to transfer a license from a licensed device to another device. There are 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 to the license management system, and the software is installed again on the other device. (Installation, license acquisition).

  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.

  Patent Document 2 discloses a configuration for transferring a license of a certain device to another device via a license management server.

  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 license key information at hand) in both the first and second types described above. 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 one of the devices, but it is necessary to convey the license key information, which is complicated.

  Even if the license can be transferred, there are many requests that the license be transferred (returned) to the original device or another device after using the function at the transfer destination. This is not always a long-term move of licenses and functions between devices. For example, when you are in a different department, you can use licenses and functions on a "temporary (short term)" basis. This is because there is a case of moving. However, in such a case, the license must be moved again by a user operation, which is complicated.

  Further, there is a demand for building a device in a license configuration desired by a user at a predetermined timing, not focusing on the transfer of licenses by function. In this case, it is not possible to cope with license transfer in units of functions, and it is necessary for the user to manually acquire a license for a required function.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to introduce a software license that has already been installed between each device whose software license is managed by a license management system. It is possible to easily move to another device without requiring a license key without giving a load to the user, and after the license is transferred, the license is automatically returned to the desired device, and the license desired by the user An object of the present invention is to provide an information processing apparatus capable of easily restoring the configuration.

  In order to solve the above problem, in the disclosed form, a software installation data corresponding to a predetermined function is downloaded from outside and installed, and a license file is acquired from outside to activate the function. Apart from the presence or absence of the license file, the means for managing the presence or absence of the license for the function, the means for moving the license between devices, and the means for updating the presence or absence of the license for the corresponding function A means for returning a license to a predetermined device in accordance with a set automatic return condition, and a license for holding a plurality of desired license configuration management information of the own device set by a user and restoring from the set license configuration management information Means for determining a configuration and transferring a license between devices.

  In the information processing apparatus of the present invention, it is possible to give a load to a user without requiring a license key for an installed software license between devices whose software licenses are managed by a license management system. In addition, the license can be easily transferred to another device after the license is transferred, and the license can be automatically returned to the desired device, and the license configuration desired by the user can be easily restored.

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. FIG. 6 is a diagram (part 1) illustrating an example of information held by a license configuration management unit. FIG. 10 is a second diagram illustrating an example of information held by the license configuration management unit. 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 a figure which shows the process example of the setting of a license automatic return. It is a flowchart which shows the process example of a license automatic return. It is a flowchart which shows the process example of the apparatus which received the license automatic return request | requirement. It is a figure which shows the process example of a job management part. It is a figure which shows the process example of the license automatic return according to the information of each apparatus. It is a figure which shows the example of the license ownership state of the head family in each apparatus. It is a figure which shows the example of the setting screen of license structure management information. FIG. 10 is a diagram (part 1) illustrating an example of a common management information setting screen. FIG. 10B is a diagram illustrating an example of a setting screen for common management information (part 2); It is a flowchart which shows the process example of a license structure decompression | restoration. It is a flowchart which shows the example of a specific process of the license required for the restoration | recovery when the period which wants to restore | restore any license structure management information is entered. It is a figure which shows the example of determination of a priority. It is a flowchart which shows the example of a specific process of the license required for the restoration | restoration when the period which wants to restore | restore any license structure management information has passed. It is a flowchart which shows the specific process example of the license required for the restoration | restoration when it returns from the state which did not use an apparatus for a long time. It is a flowchart which shows the specific process example of the license required for a restoration | recovery when there exists a restore instruction | indication from a user. It is a flowchart which shows the specific process example of the license required for the restoration | recovery when a user logs in. It is a figure which shows the example of determination of a priority. It is a flowchart which shows the specific process example of the license required for the restoration | recovery when a user logs out. It is a flowchart which shows the example of a process of acquisition of the license required for decompression | restoration. It is a sequence diagram showing an example of processing when a license necessary for restoration is being used. It is a flowchart which shows the example of a process of discharge | release of the license unnecessary for a restoration | restoration. It is a figure which shows the example of the information referred when inquiring to the apparatus management part of another apparatus. FIG. 10 is a diagram (part 1) illustrating an example of license configuration restoration based on license configuration management information; FIG. 10 is a second diagram illustrating an example of license configuration restoration based on license configuration management information. FIG. 10 is a third diagram illustrating an example of license configuration restoration based on license configuration management information. FIG. 10 is a fourth diagram illustrating an example of license configuration restoration based on license configuration management information; FIG. 10 is a diagram (No. 5) illustrating an example of license configuration restoration based on license configuration management information. It is a figure which shows the example of export to the external medium of license structure management information.

  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, an image memory unit 107, and an image processing connected via a system bus 101. A unit 108, a printing unit 109, an installation management unit 110, a license file management unit 111, a license migration management unit 112, a device management unit 113, and a license configuration management unit 114.

  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 other image processing apparatuses and license management systems (servers) provided outside. The external includes a component server and a memory device (such as an SD card) in addition to other image processing apparatuses and license management systems.

  The job management unit 106 schedules jobs such as print jobs. In addition, if the setting for automatically returning the license after the license transfer from another device is “after function use (after job completion)”, the job management unit 106 moves the license after the job of the corresponding function is completed. Notification to the management unit 112 is performed. The license return management unit 112 performs the automatic license return process. Similarly, if the corresponding function is being used when the license is transferred at the time of restoring the license configuration, the job management unit 106 notifies the license configuration management unit 114 after the job of the corresponding function is completed. The license migration management unit 112 performs the license migration process under the control of the license configuration management unit 114.

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

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

  The printing unit 109 includes a photosensitive drum, toner, a paper feed unit, a paper discharge unit, and the like. In accordance with a print instruction from the system control unit 102, the printing unit 109 conveys printing paper from the paper feeding unit, causes the image corresponding to the image data input from the image processing unit 108 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 110 manages configuration information of software installed in the image forming apparatus 1.

  The license file management unit 111 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 112 manages information on whether or not there is a license separately from the license file management unit 111, and further information on the path of the license migration, in accordance with the license migration between devices. That is, information associated with the movement of the license file is managed, and a response associated with the license operation is performed in conjunction with another device. 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). In addition, the license migration management unit 112 manages information on automatic license return after license migration based on a user operation, and controls automatic license return.

  In order to respond to an inquiry from another device, the device management unit 113 holds information on whether or not a predetermined device (reading device, printing device, FAX board, or the like) is provided and performance. This is used to determine whether or not the corresponding function can be used in the device in order to determine another device to which a license unnecessary for the restoration is transferred when restoring the license configuration.

  The license configuration management unit 114 holds the license configuration information (license configuration management information) of the device set by the user, and restores the license configuration according to the license configuration management information. There are two ways to move the license in restoring the license configuration: when moving directly between devices, and when using the machine (server or device) that manages the entire device as an intermediary. It may be realized.

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

Applicable function identifier (product ID):
This information identifies the function (software) to be installed in the device. When a license is transferred between devices, 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 111 holds the actual license file, 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, but depending on the license type after the transfer, automatic license renewal, automatic deactivation (license return), or manual deactivation / subsequent activation may be considered. Communication with the management system will occur. 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 duplication equipment:
Functions / licenses are transferred between devices without going through the license management system, but there are cases where it is necessary to update / delete license files such as automatic license update and automatic deactivation (license return) after transfer To do. 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 holding:
When transferring a function / license, the license file is copied and provided to the transfer destination. If the function / license is transferred, it is illegally used (increase in the number of licenses issued by the server) where the license management system does not know. 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”.

Automatic return:
In the case of license transfer, not only when moving for a long period of time, but also in the sense of temporary rental, you may want to use the function only once or use the function only for 1 hour (hours). It is necessary to return the license automatically after use or after a predetermined time. Therefore, the “automatic return” information is used as information on whether or not to return the license to another device according to the setting after the license is transferred.

Return timing:
When it is handled that it is automatically returned by "automatic return" information, information such as when to return is necessary. As options such as when to return, it can be considered based on a job such as “after completion of use of the corresponding function” or a time axis such as “after 2 hours or at night”. Information on these “when” returns is managed as “return timing”.

Return to:
When it is handled that it is automatically returned by the “automatic return” information, information such as where to return is necessary. The choice of where to return is not limited to the “source device” or “licensed device”, but is also based on information in the device such as a device with a large number of users and a device with a high frequency of use of the function. It is also conceivable to return to the device that is set as the device that is the transfer source or the license head (that is, the same floor of the transfer source). Information such as where to return these is managed as a “return destination”.

  FIG. 3 is a diagram showing an example of information held by the license configuration management unit 114, and an arbitrary number of license configuration management information and one common management information are provided in principle for each device. The license configuration management information includes the license you want to restore (pointer to the license migration management information), automatic restoration, the period you want to restore (restoration timing), the device that is currently using the restoration target license function, and you want to restore Includes handling when restoring a license. The common management information includes a restoration policy and acquisition of a license included in the license configuration management information when used.

  Each item of the license configuration management information will be described.

License to be restored (pointer to license transfer management information):
This is information for specifying the license function to be included in the license configuration desired by the user, and is a pointer to the license migration management information. By linking the license migration management information to the license configuration management information, the license information included in the license configuration to be restored is managed. The items of the license movement management information are as described in FIG.

Auto restore:
This information is used as information on whether the trigger for restoring the license configuration is automatically restored at the time and timing designated by the user (Yes) or whether the restoration is triggered directly by the user (No).

Period to restore (restoration timing):
This is information about when to trigger the restoration in the case of automatic restoration. A trigger is activated when the current time enters a period and when the period ends. The timing of when to restore is based on the day of the week and time such as “23:00”, and the case of considering the user's operation such as “at start-up” (when the device is turned on). There is. Information on when to start restoration is managed here.

Response when the function of the license for the original device is being restored:
If the license to be restored is a license of the device itself, the license is basically returned from the device that uses the license. However, if the corresponding function is being used on the corresponding device, it cannot be returned immediately. At this time, information on whether to give up the corresponding license until the job is completed and returned or whether to use the license of another device until the job is returned is managed here.

Handling when restoring other than the license you want to restore:
When restoring the license configuration, there may be a case where a license that is not included in the license configuration stored as the license configuration management information in the device is held. In such a case, two types of correspondences are conceivable: a license unnecessary for restoring the license configuration is held in its own device as it is or moved to another device. Information on how to handle this unnecessary license is managed here.

  Each item of the common management information will be described.

Restore policy:
When restoration is performed based on the license configuration management information, the license configuration management information registered in the device is used to determine whether to merge licenses to be restored. In principle, merging is performed for license configuration management information included in the period for which the current time is to be restored, but the licenses to be restored for all license configuration management information are merged without considering the period to be restored. You may do it. When merge is not specified as a restoration policy, license configuration management information used for restoration is determined according to a priority described later.

Acquisition of license included in license configuration management information when using:
This is used to determine whether or not to restore a license based on the license configuration management information when the device is used from a state where the device has not been used for a long time, such as returning from the standby state. Even if the license configuration is automatically restored at a certain timing, the license may be taken for use by other devices before the device is used for a while, so it is automatically recovered when used By doing so, you can use the configuration you want to use.

  FIG. 4 is a diagram showing another example of information held by the license configuration management unit 114, in which the license configuration management information is linked to the user. Compared with FIG. 3, the item of the user who created the information is added to the license configuration management information, and the item of the target range for checking the merge / priority is added to the common management information.

User who created the information:
This is identification information of the user who created the license configuration management information. When the license configuration management information is created while the user is logged in to the device, it can be automatically acquired and set. In consideration of creation by a person having a role such as a device administrator, license configuration management information not associated with a specific user can also be created. When the license configuration management information is associated with the user, restoration based on the license configuration management information of the logged-in user can be performed.

Range to check for merge / priority:
When the user who created the information is set, it is used to determine the range of license configuration management information to be merged or the range of license configuration management information for determining the priority. The target range for checking merge / priority is:
・ Target all license configuration management information ・ Target only license configuration management information associated with a specific user ・ Select only target license configuration management information not associated with a specific user it can.

<Operation / License transfer>
FIG. 5 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 migration management unit 112 manages the information on the license acquisition and the function 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. 6 is a diagram showing an example of processing until the function / license to be transferred 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. 7 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 112 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 112 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. 8 is a flowchart showing an example of processing in the source device (request destination) at the time of license transfer execution.

  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 112 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 112 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 own device is not the license owner, in step S407, the license migration management unit 112 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 112.

  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.

<Operation / Automatic license return after license transfer>
FIG. 9 is a diagram showing an example of processing for setting automatic license return.

  In FIG. 9A, a function license transfer request is made from, for example, the device D to the device A in step S501. When the license transfer is completed from the device A to the device D in step S502, the license transfer request side is displayed in step S503. In the device D, the license transfer management unit 112 displays the automatic return setting screen as a pop-up screen. Although an example of prompting input on the pop-up setting screen immediately after the license transfer will be described, the present invention is not particularly limited to this example. By making it possible to input at any time, it is possible to correct what has been set once.

  Next, in FIG. 9B, first, since there is an automatic return setting depending on whether it is a long-term license transfer or a short-term license transfer for which a function is to be used temporarily, “no return plan” Or whether to perform "automatic return setting". When “no return plan” is selected as in step S511, “No” (not to be automatically returned) for “automatic return” information in the license migration management information of the license migration management unit 112 as in step S512. Meaning) is set. This is the end of the update of the license movement management information.

  In the case where “automatic return setting” is selected as in step S513, it is an input for two axes indicating when to return “when” and “where”.

  With regard to “when”, since there is a possibility that it may be returned upon completion of the use of the function because it is desired to use the function on a temporary basis, it is possible to make a selection conscious of the job “after job completion”. Automatic return processing may be performed immediately after the job for the corresponding function is completed, but it is possible to submit several jobs in succession. There may be a follow-up such as “If you want to continue submitting a job, please press N if you submit the job (return after completion)”.

  In addition, it is possible to specify how many hours later or when to return using the concept of “time” instead of the concept of “job”. It is also possible to make detailed designations, but in order to reduce the user load, it is easy to prepare by default also “Today at night (22:00)”, “1 day later”, “1 week later”, etc. It is also possible to set it.

  After “when” is selected in step S514, “where” is set as the return destination, but this is “movement” indicating the license owner ascertained in the license movement management information of the license movement management unit 112. By adding information such as “target device (license head)” and “target device from which to move” to the license transfer management information, “transfer source (device whose license has been moved)” separately from the license head You can also choose.

  That is, the license migration management unit 112 identifies and holds the license family device in the license migration management information. For this reason, when “Move source device” is selected in the automatic license return setting, the license is returned to the licensed home device. In addition, the “movement source device” is not limited to the device that becomes the license head, but can be regarded as the movement source immediately preceding the movement of the device as a movement route. In this case, by newly adding information such as “source device” to the license migration management information, it is possible to realize migration to the device to which the license has been migrated. The “license duplicating device” information also holds the information on the movement path, but the information is only held by the license owner, so a “movement source device” is newly added. This is for the purpose of grasping the device that has become the movement route because the headquarters needs to trigger processing such as automatic license renewal, and it is used for information exchange only between the moved device and the license headquarters. is there.

  In addition to the return target using the license transfer management information of the license transfer management unit 112, the return destination can be selected after referring to the information of each device. It is also possible to “return to a proper device”. As a specific example of “according to the function usage frequency”, the determination may be made based on “the number of registered users of the device”, “the usage frequency of the corresponding function”, or “the corresponding device installation location”.

  In “Number of registered users”, it is expected that the larger the number of users, the more the device will be used, and the corresponding function will be used more frequently. Become an idea. The “frequency of use of the corresponding function” is merely an assumption for the number of registered users of the device, so it has no meaning if the number of registered users is not used, even if the number of registered users is not large. The idea is to return the device to a device with a high usage frequency, that is, a high counter value of the corresponding function. Regarding the “installation location”, it is necessary to make it possible to input “installation location” supplementary information in the initial setting of the device, etc., unlike the above-described one. If this information is used as a return source, the source may have already regained the license for the same function from another device. Assume that you move to equipment. The same can be said for the frequency of use of the corresponding function, but it is based on the assumption that the corresponding function will be used in the same way in the vicinity of the device that is used / moved (same floor). .

  When “where” is selected in step S515, the license migration management information is set as in step S516. When “after job completion” is selected as “when”, the license migration management unit 112 notifies the job management unit 106, and the job management unit 106 monitors the completion of the corresponding job. Details will be described later.

  If the device that is the return destination is not the device that is known by the license owner, the device that is the destination of transfer can be transmitted to the device that becomes the license owner. In other words, the source of movement (the side from which the license is taken) provides the information of the moved device to the license owner in order to grasp the movement route (license duplication destination device) including automatic license renewal, but the automatic return destination Depending on the setting, there is a possibility of becoming a device that the license owner does not know. Whether this is the return destination or the return source, it does not matter. This is because the information of the license owner is transferred as information of the license movement management unit 112 regardless of whether the return source or the return destination. Therefore, since it is necessary to know whether or not the device for which automatic license return is set is known in the “license duplicate device” information known at the head of the house, after deciding whether this is the return source or return destination Just do it.

  FIG. 10 is a flowchart showing an example of the automatic license return process.

  In FIG. 10, when the automatic return setting is completed and the process is started in step S601, it is determined in step S602 that the automatic return process is executed according to the automatic return setting (when). That is, if the automatic return setting is “after job completion”, the job management unit 106 notifies the license migration management unit 112 when it recognizes the completion of the corresponding job, and the license migration management unit 112 executes automatic return processing. to decide. When the automatic return setting is “time setting”, the license migration management unit 112 determines that the automatic return process is to be executed when the current time is matched with the current time.

  In step S603, it is determined whether or not the license (function) can be transferred. Although it is necessary to perform the license invalidation process (step S604) before returning the license, since the license may not be executed if it is being executed, a prior determination is performed.

  When the corresponding license (function) cannot be moved, as error processing in step S610, when the corresponding function is being executed, the function execution completion is waited or the license (function) invalidation processing is retried according to the set number of times. For example, a pattern for maintaining the normal route or a pattern for ending as an error in step S611 without performing the retry process.

  If the corresponding license (function) can be moved, in step S604, the corresponding function is invalidated as advance preparation for the return process. Skip if already disabled.

  In step S605, a return request is made to the return destination according to the automatic return setting (where). A return request is made to check the device status of the return destination, and if the function of the return destination has already been deleted, the license file, installation data, and license transfer management unit information (license home, expiration date) are transferred.

  In the subsequent step S606, when the return destination is power OFF, communication NG, etc., retry processing is performed according to the set number of times as error processing in step S610, but when communication cannot be secured, it is handled as an automatic movement error.

When an automatic return destination is set, an attempt is made to automatically return according to the settings, but if the device to be returned already has a license to be returned (purchased or moved from another device) or returned When the target is turned off or has a communication error, the movement target can be changed according to the default priority order. Because the automatic return setting has been made, the license was moved when it was desired to retain the license for a short period of time, and it was not possible to return to the selected return destination, so it is appropriate without continuing to retain the license This applies the concept of giving priority to returning to a proper device. As an example of the default priority for return in this case,
(1) User settings (settings selected by the user)
(2) License headquarters (3) Source of movement (4) Installation location (5) Frequency of function use (6) Number of device registration users is considered. The set priority order can be changed later.

  If automatic return cannot be performed for all devices based on priority (such as when a license is acquired through purchase, power is turned off, or the device itself has been removed, etc.) Re-activate your license.

  In addition, when the automatic return setting timing is set, if the machine is turned off before automatic return according to the setting and automatic return cannot be executed at the automatic return timing, it will be automatically set according to the setting after restart Return it. That is, in the case of time designation, it is performed after restarting. In addition, regarding the job, it is impossible to determine whether all the user jobs have been submitted before the power is turned off, so it is necessary to wait for job submission again and receive a report of job submission completion (other movement availability).

  In addition, before executing the automatic return process at the automatic return setting timing, if the function job is being accepted and the function cannot be invalidated, the submitted job is prioritized and completed. Or the automatic return process is executed by retrying a predetermined number of times, but there is a time designation job as a job type. In this case, if a time earlier than the time specified as the automatic return timing is specified, it is set as NG, and a license (function) to be returned after a certain period of time is set regardless of the return timing. Therefore, it is possible to prevent the corresponding job from being NG as a result.

  In step S607, data necessary for automatic return processing to the return destination is transferred (provided data changes as described in step S605 depending on the device status of the return destination).

  In step S608, the license migration management information of the license migration management unit 112 is updated when communication with the return destination is completed. As the update target, change the “license possession” information from yes to no, and initialize the automatic return setting that has been set when the return is completed.

  FIG. 11 is a flowchart illustrating a processing example of a device that has received an automatic license return request.

  In FIG. 11, in step S701, a license automatic return request is received and processing is started. Since the data type exchanged differs depending on the device configuration (license status to be returned), the request source is notified of the device configuration. If the corresponding function has already been deleted on the own machine, the request source is notified that the corresponding function data has been deleted, and the license file, installation data, and license transfer management information are transferred from the other party, and the installation (function enabled) It is necessary to carry out processing.

  In step S702, only necessary data is transferred according to the device configuration, and the data is received.

  In step S703, the corresponding license (function) is validated based on the received data.

  In step S704, the license migration management information is updated. That is, processing such as updating “license holding” information from non-> existing is performed. Thereafter, the process ends.

  The detailed processing (including the error system) in FIG. 11 is the same as that shown in FIGS.

  FIG. 12 is a diagram illustrating a processing example of the job management unit 106 when “after job completion” is selected as the automatic return setting (when).

  In FIG. 12A, when “after job completion” is selected by the user in step S801 (after step S514 in FIG. 9), the license migration management unit 112 that has accepted the setting in the device D transfers to the job management unit 106. In response to the request, “notify the license migration management unit when the job is completed” is requested, and the job management unit 106 uses the automatic license return flag “○” for the corresponding job unit of the corresponding functional unit as license automatic return management information. "Is set. Here, a state in which the automatic license return flag “◯” is set in the job unit “C marking” corresponding to the functional unit (package) “marking” is shown.

  The job management unit 106 notifies the license migration management unit 112 when the corresponding job for which the automatic license return flag is set is completed. In order to recognize that the job is completed, the license migration management unit 112 recognizes from the other device. The function that transferred the license (sales package in terms of distribution unit) and the job are associated with the automatic license return management information. In addition, even if the job management unit 106 does not manage the device configuration uniquely, the part that manages the device configuration, for example, information on functions installed in the device in advance in the installation management unit 110 or information on a sales package introduced by the user is used as the installation information. If managed, it can also be realized by the job management unit 106 referring to it.

  On the other hand, FIG. 12B shows job scheduling information when a job has not been submitted to the device D.

  Here, in FIG. 12C, when a job “C marking” is input from the user in step S <b> 802, it is confirmed on the screen whether the job input is completed. In step S803, when “job submission completion” is selected by the user (when job submission is completed, the job submission completion is pressed), the job is submitted and the job “job submission information” is displayed in the job scheduling information. "C marking" is added. Since the input job “C marking” is set with the automatic license return flag “O” in the automatic license return management information of FIG. 12A and needs to be returned after the job is completed, the automatic license return flag in the job scheduling information Is also valid.

  Thereafter, the input job “C marking” is executed, and when the execution is completed, when the job management unit 106 recognizes the completion of the job execution, it is necessary to complete the job to the license migration management unit 112 and automatically return the license. Tell the license (sales package) that corresponds to the job. In addition, it is possible to identify a user who has been set for automatic license return and not automatically return a job other than the user for which automatic license return has been set. This can also be realized by notifying only the completion of the job and allowing the license migration management unit 112 to determine the association between the job and the function (sales package). In response to this, the license migration management unit 112 performs an automatic license return process.

  In FIG. 12D, when a job “C marking” is input from the user in step S804, the job is continuously input because the job is continuously input or the job is scheduled to be input again after some time. If it is necessary, job submission has not been completed, and in step S805, “continue job submission required” is pressed. At this time, since it is not necessary to return the job after completion, the automatic license return information flag is not valid. Therefore, when the job management unit 106 recognizes the completion of job execution, it is not necessary to notify the license migration management unit 112 that the job is completed and it is necessary to return the license automatically.

  If a mechanism for setting a predetermined period is provided and the job is not submitted even after the period has elapsed, automatic return processing can be performed according to the automatic return setting. This is to keep waiting for completion of the job and prevent it from being returned for a long time unless the job is received.

  In addition, after completion of a job in which all the jobs are submitted, if cancellation of the job is accepted when the automatic license return flag is set, automatic movement can be prevented. A license automatic return flag is set in the job management unit 106 by grasping the completion of job input from the user operation, but the flag is ignored and not moved when canceling the job. This is because there is a case where it is not always the job submitting user that has been canceled.

  Furthermore, since the example of selecting “after job completion” has been described, the job is captured in units, but when the license transferred from another device (sales package as a distribution unit) itself is used, it is automatically returned. It is also possible. In other words, it is possible to make a determination after using the function without limiting to “job (part of the function provided by the sales package)”.

  FIG. 13 is a diagram illustrating a processing example of automatic license return according to information on each device. In FIG. 13, device A purchases a function from the license management system (server) and becomes the license head, device B receives the transfer of the function from device A, and device C transfers the function from device B. It is supposed to be received.

  As an automatic license return destination, it is possible to select not only a license transfer route but also a device that seems to be optimal after extracting information on devices connected to the network. In this case, after step S514 in FIG. 9, a return destination based on device information reference such as “return to an appropriate device according to the frequency of device use” is set instead of the license transfer route.

  In FIG. 13, the installation location, the function usage frequency (counter value), the number of registered users, the automatic license transfer setting, etc. are shown for each device as information for determining the license return destination. Note that the information for determining the license return destination is not limited to these.

  As for the installation location, when returning the device C to the device A (setting to return to the license family), while the license is being transferred to the device C, the device A has moved or newly transferred the license for the same function from the other device. In some cases, they are purchased from outside. That is, when the license is returned to the device A, the device A that is the return destination may already be unnecessary. Therefore, in such a case, it can be considered that it is desirable to return to the same floor of the device C, so the installation location can also be selected. The installation location can be acquired by making it possible to input it as an initial setting item of the device.

  In FIG. 13, when the return destination of the automatic license return setting is “apparatus information reference type and installation location”, for example, if the destination is “9F”, it is returned to the apparatus B.

  The applicable function usage frequency (counter value) is selectable because it can be considered that the license should be returned to a device with high usage frequency. Since the counter value of each function is often managed by the device, information can be acquired.

  In FIG. 13, when the return destination of the automatic license return setting is “apparatus information reference type and applicable function usage frequency”, the license is returned to the device B having the highest applicable function usage frequency (counter value).

  The number of registered users can be selected because it can be considered that the frequency of use of each function increases (should increase) as the number of users increases. The number of registered users in each device is often held in the form of an address book, and information can be acquired.

  In FIG. 13, when the return destination of the automatic license return setting is “apparatus information reference type and the number of registered users”, it is moved to the apparatus A having the largest number of registered users.

  In FIG. 13, an automatic license return setting is provided as information for determining the license return destination. With regard to this automatic license return setting, the license may be transferred from another device. However, there are cases where the license cannot be transferred or there is a case where it is desired to avoid the license transfer using the setting information of each license holding device. Since it is not known when these licenses can be acquired (moved), depending on the timing, the license may be transferred between other devices, and automatic license return setting (data reference type) may be performed. It is possible to set as a type to make a reservation for wanting to move. In this case, information can be acquired by making it possible to input as an automatic transfer reservation function as a setting item of initial setting or license transfer management information.

  In FIG. 13, if the license transferred between devices is the “marking function” and the return destination of the automatic license return setting is “apparatus information reference type and automatic license return request”, the corresponding preference is set. It will be returned to device B.

  The return processing based on the automatic license return setting has been described above. However, if a license transfer request is received from another device before the automatic license return timing, the request source is given priority to the license transfer request from the other device. You can move the license to On the other hand, when a license transfer request is received from another device before the timing of automatic license return, it is possible to cancel the license transfer request from another device with priority on the automatic return setting of the own device. It is also possible to select and set in advance whether to give priority to the license transfer request from another device or to give priority to the automatic return setting of the own device.

<Operation / License configuration restoration>
FIG. 14 is a diagram showing an example of the license ownership status of the home in each device. Device A has a license for each function of copying and FAX, and device B has a license for each function of FAX and document storage. The device C is assumed to have a copy and printer function license.

  FIG. 15 is a diagram showing an example of a license configuration management information setting screen. In this example, the first license configuration management information is set in the device B of FIG.

  First, in FIG. 15A, a function to be restored is selected. The function of the selection candidate can include not only the function (FAX, document storage) in which the device B is the home but also the function (copy, printer) of other devices in the license configuration management information. .

  As for the license of the home of another device, there are a method of selecting a license that has been used even once by its own device, and a method of searching for license information of another device and selecting all licenses There are two types.

  After selecting the function, pressing the “OK” button causes a transition to the screen of FIG.

On this screen,
・ Whether to restore automatically?
・ What is the timing for restoration (period of restoration)?
・ What should I do if I am using the license of the head family?
・ What to do with unnecessary licenses to restore the license structure?
Can be set by the user. Although the designation of the restoration timing is shown on a day of the week basis in addition to the time, designation on a date basis may be used. The set information is held as the license configuration management information shown in FIG.

  FIG. 16 is a diagram showing an example of a common management information setting screen, which corresponds to the case of license configuration management information (FIG. 3) not linked to a user.

  There are two types of restore policies: “Restore by merging information” and “Restore based on the highest priority information”. What is the case for “Restore based on the highest priority information”? It is possible to select whether to set priority for the reference.

  In addition, if the device has not been used for a long time even within the period to be restored, the function may have been taken away by other devices. You can also set whether to get back.

  FIG. 17 is a diagram showing another example of the common management information setting screen, which corresponds to the case of the license configuration management information (FIG. 4) associated with the user.

  In this case, in addition to the case of FIG. 16, when merging license configuration management information or determining license configuration management information with the highest priority, it is possible to set the extent to which the target range is set. If “all information” is set, the target is set regardless of whether the created user has a setting. In the case where “only the one associated with the user” is set, only the license configuration management information in which the user who created the license configuration management information is set is the target. When “only those not associated with the user” is set, only the license configuration management information for which the user who created the license configuration management information is not set is targeted.

  FIG. 18 is a flowchart illustrating an example of a license configuration restoration process.

In FIG. 18, in step S901, processing is started by receiving a restoration trigger. The restoration trigger includes a trigger that the license configuration management unit 114 determines that automatic restoration timing (time, start-up time, etc.) has arrived and notifies the user itself, and a user operation (transmission of a restoration request by the user) There are two types of triggers that are generated and notified to the license configuration management unit 114. As an automatically generated trigger,
・ When it is time to restore any of the license configuration management information ・ When the period when you want to restore any of the license configuration management information is over ・ When returning from a state where the device has not been used for a long time ・ User login There are times when the user logs out. Among these, when the user logs in and when the user logs out, this corresponds to the case of the license configuration management information (FIG. 4) associated with the user.

  In the case of a user operation, the license configuration can be restored at a timing that the user likes.

  In step S902, a license necessary for restoration is specified according to the type of trigger. In this process, if restoration is not necessary, it is also determined. Details will be described later.

  Next, in step S903, the process branches depending on whether restoration is performed from the processing result in step S902. If it is determined in step S903 that no restoration is performed, the process is completed in step S908 without performing restoration.

  If restoration is performed in step S903, a license necessary for restoration is acquired in step S904. That is, it is confirmed whether or not the license necessary for restoration specified in step S902 exists in the own device, and if it does not exist, it is obtained from another device. Details of the processing will be described later.

  In step S905, it is determined whether to release a license. Specifically, for example, when any of the license configuration management information included in the period for which the current time is desired to be restored does not require handling at the time of restoration (FIGS. 3 and 4) other than the license to be restored. Then, the merged license of the license configuration management information included in the period for which the current time is desired to be restored is compared with the license existing in the own device. Then, if an unnecessary license other than the license specified by the license configuration management information exists in the own device, it is released.

  If it is determined in step S905 that the license is not released, the process ends in step S907.

  If it is determined in step S905 that a license is released, in step S906, a license unnecessary for restoration is released. That is, an unnecessary license is moved to another device. Details of the processing will be described later. By releasing a license that is unnecessary for restoration, only the license that the user declares necessary can be left in the device. And a process is complete | finished by step S907.

  FIG. 19 is a flowchart showing a processing example of specifying a license necessary for restoration when one of the license configuration management information is to be restored (step S902 in FIG. 18).

  In FIG. 19, when processing is started in step S911, it is determined in step S912 whether or not the restoration policy is “merge”.

  If the restoration policy is “merge”, in step S913, the licenses in the license configuration management information included in the period in which the current time is desired to be restored are merged to determine a license necessary for restoration. Then, the process ends at step S917.

  If the restoration policy is not “merge”, it is determined in step S914 whether the priority of the license configuration management information that has been the trigger is the highest among the license configuration management information included in the period in which the current time is desired to be restored. To do. Details of the priority determination will be described later.

  If the priority of the license configuration management information serving as the trigger is the highest, in step S915, the license of the license configuration management information serving as the trigger is determined as a license necessary for restoration. Then, the process ends at step S917.

  If the priority of the license configuration management information serving as a trigger is not the highest priority, it is determined in step S916 that restoration is not necessary. Then, the process ends at step S917.

  FIG. 20 is a diagram illustrating an example of priority determination, and is an example in the case where the priority is set to be determined based on the average of the usage amount of functions.

  The device has a counter of how much each function has been used, and the usage amount of each function is determined based on the information.

In the case of the example of FIG.
Average usage of functions included in license configuration management information # 1:
(Copy use amount + printer use amount) / 2 = (200 + 500) / 2 = 350
Average usage of functions included in license configuration management information # 2:
(Printer usage + FAX usage) / 2 = (500 + 350) / 2 = 425
Average usage of functions included in license configuration management information # 3:
Usage amount of document accumulation = 400
It becomes. Therefore, the priority is in the order of license configuration management information # 2> license configuration management information # 3> license configuration management information # 1.

  FIG. 21 is a flowchart showing an example of processing for specifying a license (step S902 in FIG. 18) necessary for restoration when the period for restoring any license configuration management information is over.

  In FIG. 21, when processing is started in step S921, it is determined in step S922 whether or not the restoration policy is “merge”.

  If the restoration policy is “merge”, it is determined in step S923 that restoration is not necessary. And a process is complete | finished by step S926.

  If the restoration policy is not “merge”, it is determined in step S924 that the license has been restored based on the license configuration management information that is the trigger, or, for example, the highest priority in a state one minute before the current time. It is determined whether or not it has been restored. The priority determination is performed in the same manner as described with reference to FIG.

  If the license has not been restored based on the license configuration management information that has been a trigger, it is determined in step S923 that restoration is unnecessary. And a process is complete | finished by step S926.

  If the license has been restored based on the license configuration management information that has been a trigger, in step S925, the license configuration management information having the highest priority among the license configuration management information included in the period in which the current time is desired to be restored. To determine the license required for restoration. If there is no other license configuration management information, it is determined that restoration is unnecessary. And a process is complete | finished by step S926.

  FIG. 22 is a flowchart showing a processing example of specifying a license (step S902 in FIG. 18) necessary for restoration when returning from a state where the device has not been used for a long time.

  In FIG. 22, when the process is started in step S931, it is determined in step S932 whether or not the license is set to be acquired when used after being left for a long time.

  If the license is set to be acquired, it is determined in step S933 whether the restoration policy is “merge”.

  If the restoration policy is “merge”, in step S934, the licenses of the license configuration management information included in the period in which the current time is desired to be restored are merged to determine a license necessary for restoration. And a process is complete | finished by step S937.

  If the restoration policy is not “merge”, in step S935, the license of the license configuration management information with the highest priority among the license configuration management information included in the period in which the current time is desired to be restored is changed to a license necessary for restoration. decide. If there is no other license configuration management information, it is determined that restoration is unnecessary. The priority determination is performed in the same manner as described with reference to FIG. And a process is complete | finished by step S937.

  If the license is not set to be acquired, it is determined in step S936 that restoration is unnecessary. And a process is complete | finished by step S937.

  FIG. 23 is a flowchart showing a processing example of specifying a license necessary for restoration (step S902 in FIG. 18) when the user gives a restoration instruction.

  In FIG. 23, when processing is started in step S941, it is determined in step S942 whether or not the restoration policy is “merge”.

  If the restoration policy is “merge”, in step S943, the licenses in the license configuration management information included in the period in which the current time is desired to be restored are merged to determine a license necessary for restoration. And a process is complete | finished by step S947.

  If the restoration policy is not “merge”, it is determined in step S944 whether there is license configuration management information having the highest priority among the license configuration management information included in the period in which the current time is desired to be restored. The priority determination is performed in the same manner as described with reference to FIG.

  If there is license configuration management information with the highest priority, in step S945, the license of the license configuration management information with the highest priority is determined as the license necessary for restoration. And a process is complete | finished by step S947.

  If there is no license configuration management information with the highest priority, it is determined in step S946 that restoration is unnecessary. And a process is complete | finished by step S947.

  When the user designates the license configuration management information and instructs restoration, the restoration may be performed based on the license configuration management information.

  FIG. 24 is a flowchart illustrating a processing example of specifying a license necessary for restoration when the user logs in (step S902 in FIG. 18).

  In FIG. 24, when the process is started in step S951, it is determined in step S952 whether there is license configuration management information included in the period in which the current time is desired to be restored, which is associated with the logged-in user.

  If there is no license configuration management information, it is determined in step S954 that restoration is not necessary. And a process is complete | finished by step S957.

  If the license configuration management information exists, it is determined in step S953 whether the restoration policy is “merge”.

  If the restoration policy is “merge”, it is determined in step S954 that restoration is not necessary. And a process is complete | finished by step S957.

  If the restoration policy is not “merge”, the priority of the license configuration management information associated with the logged-in user is the highest among the license configuration management information included in the period in which the current time is to be restored in step S955. Judge whether it is high. Details of the priority determination will be described later.

  If the priority is highest, it is determined in step S954 that restoration is not necessary. And a process is complete | finished by step S957.

  If the priority is not the highest, in step S956, the licenses in the license configuration management information included in the period for which the current time is desired to be restored, which are associated with the logged-in user, are merged to determine a license necessary for the restoration. And a process is complete | finished by step S957.

  In the above description, only the license configuration management information registered by the logged-in user is restored to the information included in the period that the current time is to be restored. All of the license configuration management information registered by may be restored.

  FIG. 25 is a diagram illustrating an example of priority determination, and is a diagram illustrating how priority is determined when license configuration management information is associated with a user.

  In addition to the method (method # 1) for determining based on how much the function included in the license configuration management information as shown in FIG. 20 is used, how much each user uses the device How much a user who has created license configuration management information by combining the method (method # 2) based on whether it is used (method # 2) uses the functions included in the license configuration management information There is a method (method # 3) for determining based on the information.

In the description of FIG. 20, the description is based on the average of the usage amounts of the included functions, but here, another method is used for determination based on the total usage amount.
For Method # 1:
License configuration management information # 1:
Copy function usage + printer function usage = 300 + 700 = 1000
License configuration management information # 2:
Usage amount of printer function + Usage amount of FAX function = 700 + 500 = 1200
License configuration management information # 3:
Usage amount of document storage function = 800
From the above results, the priority is license configuration management information # 2> license configuration management information # 1> license configuration management information # 3.
For Method # 2:
License configuration management information # 1:
Usage without login = 1000
License configuration management information # 2:
Usage when logged in to user A = 600
License configuration management information # 3:
Usage when logged into user B = 700
From the above results, the priority is license configuration management information # 1> license configuration management information # 3> license configuration management information # 2.
For Method # 3:
License configuration management information # 1:
Usage amount of copy function in unlogged state + printer usage amount in unlogged state = 200 + 400 = 600
License configuration management information # 2:
Usage amount of printer function when logged in to user A + Usage amount of FAX function when logged in to user A = 300 + 200 = 500
License configuration management information # 3:
Usage amount of document storage function when logged in to user B = 700
Based on the above results, the priority is license configuration management information # 3> license configuration management information # 1> license configuration management information # 2. Here, the determination was made based on the total usage amount, but as shown in FIG. A method for obtaining an average of the usage amount may be used.

  FIG. 26 is a flowchart showing a processing example of specifying a license necessary for restoration when the user logs out (step S902 in FIG. 18).

  In FIG. 26, when the process is started in step S961, it is determined in step S962 whether or not there is license configuration management information associated with the logged out user and included in the period for which the current time is desired to be restored.

  If there is no license configuration management information, it is determined in step S964 that restoration is not necessary. And a process is complete | finished by step S967.

  If the license configuration management information exists, it is determined in step S963 whether the restoration policy is “merge”.

  If the restoration policy is “merge”, it is determined in step S964 that restoration is not necessary. And a process is complete | finished by step S967.

  If the restoration policy is not “merge”, in step S965, the license configuration management information associated with the logged out user has the highest priority among the license configuration management information included in the period in which the current time is desired to be restored. Judge whether it is high. The priority determination is performed in the same manner as described with reference to FIG.

  If the priority is highest, it is determined in step S964 that restoration is not necessary. And a process is complete | finished by step S967.

  If the priority is not the highest, in step S966, the licenses in the license configuration management information included in the period in which the current time is desired to be restored, which are associated with the logged out user, are merged to determine a license necessary for the restoration. And a process is complete | finished by step S967.

  FIG. 27 is a flowchart showing a processing example of acquisition of a license necessary for restoration (step S904 in FIG. 18).

  In FIG. 27, when the process starts in step S971, in step S972, one of the restoration target licenses set in the license configuration management information is specified, and the process proceeds to step S973.

  In step S973, it is confirmed whether the restoration target license exists in the own device. If it exists in the own device, the process returns from step S9710 to step S972 to move to the next license process, and if not, the process moves to step S974.

  In step S974, it is confirmed whether or not the license to be restored is a license whose home device is the own device. If the own device is a license of the head family, the process proceeds to step S975. If not, the process proceeds to step S979.

  In step S975, it is confirmed whether the restoration target license currently held by the other device is being used in the other device. If it is in use, the process proceeds to step S977, and if not, the process proceeds to step S976.

  In step S976, the license to be restored is moved to its own device, the process returns from step S9710 to step S972, and the next license process is started. The movement of the license is processed by the license movement management unit 112 in the same manner as described above.

  In step S977, when the use of the currently used license is completed, the corresponding device is requested to return the license, and the process proceeds to step S978.

  In step S978, if there is a license currently being used by another device, whether or not to wait until the use is completed or to obtain from another device is the own device of the license configuration management information (FIGS. 3 and 4). Confirm by the corresponding setting that the license function to be restored is in use. If it is obtained from another device, the process proceeds to step S979. If it is waited until the use is completed, the process returns from step S9710 to step S972 to proceed to the next license process.

  In step S979, a necessary license is acquired from another device, and the process returns from step S9710 to step S972 to move to the next license process. The movement for obtaining a license is processed by the license movement management unit 112 in the same manner as described above.

  If it is determined in step S9710 that all licenses have been processed, the process ends in step S9711.

  FIG. 28 is a sequence diagram showing a processing example when a license necessary for restoration is being used. In addition to the processing overlapping with the processing in FIG. 27, processing not covered in FIG. 27 is included.

  In FIG. 28, device B checks in step S981 whether the license necessary for restoration is used in device D, and if it is answered in step S982 from device D that device B is in use, device B in step S983 Ask D to return the license after the job is completed. In step S984, the device D internally sets the license to be returned after the job is completed.

  Here, when it is set that the function being used is acquired from another device, the device B confirms whether or not the license necessary for restoration is used by the device A in step S985. If there is a reply from the device A that the device A is being used in step S986, the license is not requested by the device B because the device B is not home.

  In addition, in step S987, the device B confirms whether or not the license necessary for the restoration of the device C is being used. If there is a reply from device C that it is empty (not in use) in step S988, device B makes a license transfer request to device C in step S989, and receives a license transfer from device C in step S9810.

  After that, in step S9811, the corresponding job of the device D is completed. When a license is returned from the device D to the device B in step S9812, the device B returns the borrowed license to the device C in step S9813.

  FIG. 29 is a flowchart showing an example of processing for releasing a license unnecessary for restoration (step S906 in FIG. 18).

  In FIG. 29, when the process starts in step S991, in step S992, one of the restoration target licenses set in the license configuration management information is specified, and the process proceeds to step S993.

  In step S993, it is confirmed whether or not a license unnecessary for restoring the license configuration is a license for which the own device is the home. If the own device is a license of the head family, the process proceeds to step S995. If not, the process proceeds to step S994.

  In step S994, the license is returned to the home device of the corresponding license, and the process returns from step S9915 to step S992 to move to the next license process.

  In step S995, an inquiry is made to the license file management unit 111 and the device management unit 113 of the other device in order to know whether the corresponding license can be used in another device, and the process proceeds to step S996. In the inquiry, the license file management unit 111 is inquired whether a license having the same function as the corresponding license is held, and the device management unit 113 is required to use the function of the corresponding license. Inquire whether the device is equipped. Each device holds information indicating what device is necessary to use the function for each function, as shown in FIG. 30 (a). An inquiry is made to the device management unit 113 as to whether the function can be used.

  Returning to FIG. 29, in step S996, it is checked whether there is one available device. If there is one device that can be used, the process proceeds to step S997; otherwise, the process proceeds to step S998.

  In step S997, an available device is set as a license transfer destination, and the process proceeds to step S9914.

  In step S998, it is confirmed whether or not the user is set to manually select a destination from a plurality of devices that can use the corresponding license. If the selection is made manually, the process proceeds to step S999. If not, the process proceeds to step S9911.

  In step S999, in order for the user to select a device to be moved, a list of available devices is presented to the user and selected, and the process proceeds to step S9910.

  In step S9910, the device selected by the user is set as the movement destination, and the process proceeds to step S9914.

  In step S9911, it is confirmed whether or not the setting is made so as to determine the destination device by looking at the value of the function-specific counter of each device. If it is set to make a judgment by looking at the function-specific counter, the process proceeds to step S9912; otherwise, the process proceeds to step S9913.

  In step S9912, the function-specific counter value of each device that can use the license is confirmed, the most used device (counter value is large) is set as the movement destination, and the process proceeds to step S9914.

  In step S9913, the specifications of each device are confirmed, the device with the highest specification is set as the movement destination, and the process proceeds to step S9914. Each device holds information indicating which specification is prioritized for each function as shown in FIG. 30B, and inquires the device management unit 113 of the other device based on the information. I do. The default specification is determined for each function, but the user can change the setting.

  Returning to FIG. 29, in step S9914, the license is transferred to the device set as the transfer destination, and the process returns from step S9915 to step S992 to proceed to the next license process.

  If it is determined in step S9915 that all licenses have been processed, the process ends in step S9916.

  FIG. 31A to FIG. 31E are diagrams showing examples of license configuration restoration based on license configuration management information, and show how licenses move. In FIG. 31C and thereafter, it is assumed that there is no user operation and the license is transferred only by restoration based on the license configuration management information.

  FIG. 31A shows a state in which license configuration management information is created for the device B among the three devices A to C shown in FIG. The license configuration management information can be held by each device, but this time, it is described as being held only by device B for explanation.

  FIG. 31B shows a state in which the license is moved from the device B in order to use the FAX function in the device C and the document storage in the device A, respectively. This time is 8:30 on Monday.

  FIG. 31C shows a state in which the license is moved based on the license configuration management information # 1 and # 3 at 9:00 on Monday.

  FIG. 31D shows a state in which the license has been moved to 11:00 based on the license configuration management information # 2.

  FIG. 31E shows a state where the time is 13:00 and an unnecessary license is moved based on the license configuration management information # 3.

  Note that although the period of the license configuration management information # 1 expires at 12:00, nothing is done because the license configuration management information # 2 is set to hold licenses that are not required for restoration.

  FIG. 32 is a diagram showing an example of exporting license configuration management information to an external medium.

  That is, the license configuration management information can be stored not only in the device but also in an external medium such as a flash memory. In this case, the restoration timing is blank.

  When an external medium storing license configuration management information is inserted into the device, a trigger for restoring the license configuration of the device with the external media inserted into the license configuration indicated by the license configuration management information stored in the external medium Is sent to the license configuration management unit 114, and the license configuration is restored by the same processing as described above. Since the device is not limited to the exported device, the license configuration can be restored by various devices based on the license configuration management information stored in the external medium.

<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. In addition, since the automatic license return function is provided, the license of the installed software can be easily transferred to other devices without requiring a license key and without burdening the user. The license can be automatically returned to a desired device after movement, and the license configuration desired by the user can be easily restored.

  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 Image memory part 108 Image processing part 109 Printing part 110 Installation management part 111 License file management part 112 License movement management part 113 Device management unit 114 License configuration management unit

JP 2006-018402 A Special table 2010-501092 gazette

Claims (16)

Means for downloading and installing software installation data corresponding to a predetermined function from the outside;
Means for obtaining a license file from outside to activate the function;
Apart from the presence or absence of the license file, means for managing the presence or absence of a license for the function;
Means for transferring a license between devices and updating the presence or absence of a license for the corresponding function;
Means for returning the transferred license to a predetermined device in accordance with the set automatic return condition;
Means for holding a plurality of desired license configuration management information of the own device set by the user, determining a license configuration to be restored from the plurality of set license configuration management information, and transferring a license between the devices An information processing apparatus characterized by that. The information processing apparatus according to claim 1,
An information processing apparatus characterized in that when determining a license configuration to be restored, the license configuration is such that the licenses specified by a plurality of set license configuration management information are merged to restore the merged license. The information processing apparatus according to claim 1,
When determining the license configuration to be restored, it is assumed that the license configuration is such that the priority is determined for each of the set license configuration management information, and the license specified by the license configuration management information with the highest priority is restored. An information processing apparatus characterized by that. The information processing apparatus according to claim 3.
An information processing apparatus characterized in that a total use number of functions corresponding to a license specified by license configuration management information is used as a priority. The information processing apparatus according to claim 3.
An information processing apparatus characterized in that an average number of functions used corresponding to a license specified by license configuration management information is used as a priority. The information processing apparatus according to any one of claims 1 to 5,
The license configuration management information includes a setting item indicating a period to be restored. The information processing apparatus according to any one of claims 1 to 6,
An information processing apparatus that restores a license configuration of a device based on a license configuration that is restored at that time when the device is used after the device has not been used for a long time. The information processing apparatus according to any one of claims 1 to 7,
An information processing apparatus that links license configuration management information to a user of a device. The information processing apparatus according to claim 8,
An information processing apparatus that determines license configuration management information to be checked when determining a license configuration to be restored based on a user. The information processing apparatus according to any one of claims 8 and 9,
An information processing apparatus that determines the priority of license configuration management information based on how much a user who has set license configuration management information uses the device. The information processing apparatus according to any one of claims 8 and 9,
An information processing apparatus that determines the priority of license configuration management information based on how much a user who sets the license configuration management information uses a license specified by the license configuration management information. The information processing apparatus according to any one of claims 8 to 11,
An information processing apparatus that restores license configuration management information set by a corresponding user at a timing when a user who has set license configuration management information logs into the device. The information processing apparatus according to claim 12,
An information processing apparatus, wherein when a user who sets license configuration management information logs out from a device, the license configuration is restored to an optimal license configuration at the present time. An information processing system in which a plurality of information processing devices are connected via a network,
The information processing apparatus includes:
Means for downloading and installing software installation data corresponding to a predetermined function from the outside;
Means for obtaining a license file from outside to activate the function;
Apart from the presence or absence of the license file, means for managing the presence or absence of a license for the function;
Means for transferring a license between devices and updating the presence or absence of a license for the corresponding function;
Means for returning the transferred license to a predetermined device in accordance with the set automatic return condition;
Means for holding a plurality of desired license configuration management information of the own device set by the user, determining a license configuration to be restored from the plurality of set license configuration management information, and transferring a license between the devices An information processing system characterized by this. A process in which the control unit downloads and installs software installation data corresponding to a predetermined function from the outside; and
A step of acquiring a license file from outside to activate the function;
A step of managing the presence or absence of a license for the function separately from the presence or absence of the license file;
A step of transferring a license between devices and updating the presence or absence of a license for the corresponding function;
A step in which the control unit returns the transferred license to a predetermined device in accordance with the set automatic return condition;
The control unit holds a plurality of desired license configuration management information of the own device set by the user, determines a license configuration to be restored from the plurality of set license configuration management information, and moves the license between the devices An information processing method comprising:   An information processing program for causing a computer to execute the information processing method according to claim 15.

Images