JP5701151B2 - Device, control method, and program. - Google Patents

Description

  The present invention relates to an apparatus for managing a license history, a control method, and a program.

  There are devices connected to the network that can install licensed applications. When the application is installed, the license history is stored in a plurality of nonvolatile areas such as a ferroelectric memory (FRAM = Ferroelectric Random Access Memory) and a hard disk drive / flash memory. In this way, by managing the license history twice, even if information is deleted from one memory, it is possible to restore the information from the other memory. For example, when the hard disk needs to be replaced due to a failure of the hard disk drive, the license history can be written back to the hard disk from the license history stored in the FRAM. This makes it possible to manage the license using the correct license history, and to prevent the use of a license without a legitimate authority. Hereinafter, the process of writing back the license history is referred to as a license history return process. An apparatus for executing such a backup method is disclosed in Patent Document 1. In a file system that has a configuration in which the management area and the actual data area are physically separated and arranged, if one of them is replaced due to a failure, etc., an apparatus intended to prevent inconsistencies in the file system It is.

JP 2006-222581 A

In the case of Patent Document 1, the management area of the file system is arranged on a high-speed nonvolatile memory device, and the actual data is stored in the storage device. It is intended only to prevent inconsistencies on the file system, and does not assume a data restoration process corresponding to actual data such as a license history. Therefore, there is a high possibility that an appropriate license cannot be used because the license history is inappropriate.
An object of the present invention is to provide an apparatus that performs a license history restoration process for maintaining the consistency of license histories.

  An apparatus according to an embodiment of the present invention is an apparatus that can hold an application that can be used by using a license, and when the application can be used by using a license, the license is A first memory holding a license ID for identification, a second memory holding the license ID for backing up the license ID held in the first memory, and a second memory If the held device ID for identifying the device matches the device ID assigned to the device, the license ID held in the first memory is held in the second memory and does not match In this case, after erasing the license ID already held in the second memory, the license ID held in the first memory is changed to And controlling so as to hold the serial second memory.

  The present invention is an invention assuming restoration processing of data corresponding to actual data such as license history. By executing the license history restoration processing for maintaining the consistency of the license history, an appropriate license cannot be used. It becomes possible to prevent.

1 is a diagram illustrating an overall configuration of an image forming system in the present invention. 1 is a diagram illustrating an overall configuration of an image forming apparatus according to the present invention. It is a figure which shows the software and hardware constitutions in license management. It is a figure which shows the flow of the license installation process in license management. It is a block diagram which shows returning a license log | history from flash memory to FRAM. It is a block diagram which shows returning a license log | history from FRAM to flash memory. It is a figure which shows the flow of the license log | history return process in license management. It is a block diagram which shows returning a license history when a used board comes. It is a block diagram which shows returning a license history when a used board comes. It is a figure which shows the flow of the license log | history return process supposing that a used board comes. It is a figure which shows the case where a serial number can be acquired with a special number. It is a figure which shows the flow of the license log | history return process in consideration of the case where the special serial number in FIG. 11 was able to be acquired.

  Conventional license history restoration processing assumes replacement with a new one due to a failure of a hard disk or the like. This is because hard disks are usually encrypted for security, and it is difficult to think of attaching a used hard disk that has been used by another device to another device. Because. However, in the case of an inexpensive model such as a printer (SFP), a hardware configuration using a nonvolatile memory such as a flash memory on the main body board instead of the hard disk may be used. At this time, as a service by a service person, when a problem occurs in the printer at the user's site, a used main body board that has been used once at another site is incorporated into the printer in order to confirm the phenomenon. Then, there are cases where a test is performed on a used board and a countermeasure for returning the printer to a normal state is considered.

At this time, the above-mentioned used main body board may be used in a customer environment different from the above-mentioned printer, and the flash memory attached to the used main body board was used in the printer of the different customer environment. There is a possibility that the license history of the application remains. In such a case, in the license history recovery process, the license history that was left on the used main body board is treated like regular license information, and as a result, there is a possibility that unused licenses will remain in the license history. The license history information that can be left in the FRAM in terms of capacity has an upper limit, and the license history information that is not used by the user consumes license history wastefully. become.

  Further, depending on the number of license histories, there is a possibility that the license history restoration process from the FRAM is not performed even if it is necessary to operate. In this state, if the license history information on the FRAM is cleared for some reason, the license history originally used by the user does not remain.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing the overall configuration of a printing system including an image forming apparatus according to an embodiment of the present invention. In the embodiment of the present invention, it is assumed that a copier, a printer, a multifunction peripheral, or the like having a function specifically described below is used as the image forming apparatus.

  As shown in FIG. 1, the image forming apparatus 110 is connected to a LAN 140 including Ethernet (registered trademark) together with a client computer 120 and a server computer 130. However, in the printing system of the present invention, the number of devices connected to the system is not limited to the number of connections.

  The image forming apparatus 110 has a copy function, a facsimile function, and an e-mail transmission function, and also has a data transmission function for reading a document image and transmitting image data obtained by the reading to each apparatus on the LAN 140. The image forming apparatus 110 stores an image read by the scanner unit 112 described later and data designated by a computer connected to the LAN 140 in a hard disk in the image forming apparatus 110 or a specific area of the flash memory 204. Is possible. It is also possible to read a document image and save it as a digital image in the hard disk / flash memory 204. It is also possible to print a digital image stored in the hard disk area.

  The image forming apparatus 110 includes a scanner unit 112 that is an image input device, a printer unit 113 that is an image output device, a controller 200 that controls operation of the entire image forming apparatus 110, and the like.

  The scanner unit 112 converts the image information into an electric signal by inputting reflected light obtained by exposing and scanning the image on the document to the CCD. Further, the electrical signal is converted into a luminance signal composed of R, G, and B colors, and the luminance signal is output to the controller 200 as image data. The document is set in the document feeder. When the user gives an instruction to start reading from the operation unit 111, a document reading instruction is given from the controller 200 to the scanner unit 112. Upon receiving this instruction, the scanner unit 112 feeds documents one by one from the document feeder and performs a document reading operation. The document reading method is not an automatic feeding method using a document feeder, but may be a method of scanning the document by placing the document on a glass surface (not shown) and moving the exposure unit. The scanner unit 112 corresponds to a scan unit.

  The printer unit 113 is an image forming device that forms image data received from the controller 200 on a sheet. The printer unit 113 corresponds to a print unit. The image forming apparatus according to the first exemplary embodiment includes both the scanner unit 112 and the printer unit 113. However, the image forming apparatus may include only one of the scanner unit 112 and the printer unit 113. That is, the present invention can be applied to an apparatus having the scanner unit 112 and / or the printer unit 113.

  In the server computer 130, an operating system (hereinafter referred to as OS) and various application service programs are executed by the CPU, and various data processing is performed by executing application services under the management of the OS. The same applies to the client computer 120.

  FIG. 2 is a block diagram for explaining the configuration of the controller 200 of the image forming apparatus 110. The controller 200 is electrically connected to the scanner unit 112 and the printer unit 113, and on the other hand, is connected to the client computer 120 and the server computer 130 via the LAN 140. As a result, image data and device information can be input and output.

  The CPU 201 comprehensively controls access to various connected devices based on a control program or the like stored in the ROM 202, and also comprehensively controls various processes performed in the controller. Note that the various units to which the image forming apparatus 110 is attached can be exchanged.

  A ROM 202 stores a boot program for the apparatus. A RAM 203 is a system work memory for the operation of the CPU 201 and also a memory for temporarily storing image data. The RAM 203 is configured by an FRAM or SRAM that retains stored contents even after the power is turned off, a DRAM that erases the stored contents after the power is turned off, and the like.

  The HDD 204 can hold system software and image data temporarily or semipermanently. This can be replaced with a flash memory or the like. The operation unit I / F 205 is an interface unit for connecting the system bus 212 and the operation unit 111. The operation unit I / F 205 receives image data to be displayed on the operation unit 111 from the system bus 212 to the operation unit 111 and outputs information input from the operation unit 111 to the system bus 212.

  A network I / F 206 is connected to the LAN 140 and the system bus 212 to input / output information. A scanner I / F 208 corrects, processes, and edits image data received from the scanner unit 112. The scanner I / F 208 determines whether the received image data is a color document or a monochrome document, a character document, or a photo document. Then, the determination result is attached to the image data. Such accompanying information is referred to as attribute data.

  The image forming unit 209 performs image data direction conversion, image compression, decompression, and the like. The printer I / F 210 receives the image data sent from the image forming unit 209, and forms an image on the image data while referring to attribute data attached to the image data. The image data after the image formation is output to the printer unit 113. The FAX I / F 211 transmits the image data sent from the image forming unit 209 to the designated transmission destination via the FAX transmission unit 114 and the LAN 140 (or WAN 250).

  The e-mail I / F 207 transmits the image data sent from the image forming unit 209 to the designated transmission destination through the mail sending unit 115 and the LAN 140 (or WAN 250). The user instruction to the image forming apparatus 110 and information presentation to the user may be performed via the operation unit 111 or the client computer 120 connected via the LAN 140, for example. Also good.

  FIG. 3 describes a software / hardware configuration and a license management method related to the license management system. Here, the license is for activating an application preinstalled in the device or a later application. The application can be used only after activation. A SoftID board 350 holds a device ID for uniquely identifying a device such as the image forming apparatus 110, that is, an identification number (for example, a serial number). The SoftID board 350 is realized by hardware. Is done. In the first embodiment, the identification number is a serial number, and FIG. 3 shows that the serial number is AAAA1234567.

  The FRAM 300 stores a license history 310 in a storage holding area. This is used at the time of license installation described later. The content of the history is a history of a license ID that uniquely identifies the license. The main body board 320 includes a non-volatile flash memory 330, and the same content as the license history 310 held in the FRAM 300 is held as a license file 340.

  Here, the FRAM 300 corresponds to the RAM 203 as the first memory, and the flash memory 330 corresponds to the HDD / flash memory 204 as the second memory. The license file 340 also holds a device identification number when the license file is created. In this way, by holding the same contents in the FRAM and the flash memory, when each part described later is exchanged, each of them backs up the information held by each other. 110 is provided. The license installation processing unit 360 is a module that executes the license installation and license history registration processing shown in FIG. The license history management unit 370 is a module that executes the license history return process shown in FIG. The license installation processing unit 360 and the license history management unit 370 are held in the HDD / flash memory 204 in FIG. 2, and the processing is expanded and executed in the memory.

  FIG. 4 shows a flow when the license installation processing unit 360 installs a licensed application. In S400, installation of an application and a license starts. Next, in S410, a duplicate check is performed to determine whether the license ID exists in the license history. The license ID is a number uniquely assigned to the license. The license history refers to a history of license IDs that are registered successfully when the installation of the application and the license is successful. The same contents are held in the FRAM 300 and the flash memory 320.

  In the check in S410, that the license ID is duplicated indicates that there is a track record of installing the same license in the past. In order to prevent unauthorized use, it is generally desirable that one license can be installed only once on one device. Therefore, if there is an overlap in this check, the process proceeds to S440, and the application / license installation fails. If there is no duplication, the process proceeds to S420 to install an application / license. After installation, the license ID is registered. Then, the installation is completed in S450.

<Replacement with new FRAM / flash memory>
5 and 6, the license history restoration process when the FRAM / flash memory part is replaced with a new one will be described.

  FIG. 5 is a block diagram of return processing when the FRAM is replaced. The device state 550 is the same as the license history state shown in FIG. The serial number of the device is AAA1234567, and the license history 310 and the license file 340 include two license histories, uuid1 and uuid2. Consider a case where the state is changed to a new FRAM from this state (corresponding to the operation of FRAM replacement 500) and the state of the device transits to state 560. At this time, the FRAM 300 is replaced with a new FRAM 510. When the device is activated with the new FRAM 510 replaced, the license history management unit 370 compares the license history 520 held in the FRAM 510 with the license history of the license file 340 held in the flash memory 330. To do.

  As a result of the comparison, the license history management unit 370 has zero license histories 520 in the storage holding area of the FRAM 510 and two license histories in the license file 340 held in the flash memory 330. It can be seen that there are more license histories of the license file 340 to be executed. At this time, a restoration process is executed in which the license history is copied from the memory holding a large amount of license history to the memory holding a small amount of license history. Specifically, in order to copy the license history from the flash memory 330 to the FRAM 510, the above-described return processing 530 is performed. As a result, the state of the device transitions to a state 570, and the license history from the license file 340 is copied to the license history 540 of the FRAM 510. The above is the outline of the license history return processing from the flash memory to the FRAM.

  FIG. 6 is a block diagram of a return process when the flash memory is replaced. The device state 660 is the same as the license history state shown in FIG. The serial number of the device is AAA1234567, and the license history 310 and the license file 340 include two license histories, uuid1 and uuid2.

  Consider a case where a new main body board 320 is replaced from this state (corresponding to the operation of main body board replacement 600), and the device state transitions to state 670. At this time, the board 320 is replaced with a new main body board 610, and the flash memory 330 is replaced with a new flash memory 620. When the device is activated with the new body board 610 replaced, the license history management unit 370 compares the license history 310 held in the FRAM 300 with the license history of the license file 630 held in the flash memory 620. To do. As a result of the comparison, the license management unit 370 has zero license histories in the license file 630 held in the flash memory 620 and two license histories 310 held in one FRAM 300. You can see that there are many.

  At this time, a license restoration process is performed in which the license history is copied from a memory having a large number of license histories to a memory having a small number of license histories. Specifically, in order to copy the license history from the license history 310 of the FRAM 300 to the flash memory 620, the above-described return processing 640 is performed. As a result, the state of the device transitions to the state 680, and the license history is copied from the FRAM 300 to the history of the license file 650. The above is the outline of the license history return processing from the FRAM to the flash memory.

  FIG. 7 shows a flowchart of the license history return process executed by the license history management unit 370 in the cases of FIGS.

  In S700, the device is activated. In step S710, the license history management unit 370 checks the consistency of the license history. In S720, the license history management unit 370 compares the number of license histories held in the FRAM and the flash memory. This comparison of the number of license histories is called license history consistency check. If the numbers match at this time, based on the determination that the consistency between the FRAM and the flash memory is maintained, the process proceeds to S730 without executing any process and the return process ends.

  On the other hand, if the number of license histories in the flash memory is larger than the number of license histories in the FRAM, the process proceeds to S740, and the contents of the license history are restored from the flash memory to the FRAM. Further, the process ends in S730. Conversely, when the number of license histories in the FRAM is larger than the number of license histories in the flash memory, the process proceeds to S750, and the contents of the license history are restored from the FRAM to the flash memory. Further, the process ends in S730.

<Replacement with used board>
FIG. 8 shows a block diagram when the return processing is performed according to the flow of FIG. 7 when the used board is replaced. The device status 860 is the same as the status of the license history shown in FIG. The serial number of the device is AAA1234567, and the license history 310 and the license file 340 include two license histories, uuid1 and uuid2. Consider a case where the device is replaced with a used main body board 810 from this state (corresponding to the operation of the board replacement 800), and the device state transitions to state 870.

  The used main body board 810 has a flash memory 820. Further, it is assumed that the used board 810 is used in another apparatus different from the image forming apparatus 110 having the serial number BBBB9999999. Therefore, the used board 810 includes the license history held when the application is activated on another device. The license history file 830 includes three histories of uuid3, uuid4, and uuid5 as license histories, and holds serial number information BBBB9999999. The state 870 is a state in which the main body board 320 is replaced with the used main body board 810. When the device is activated with the main body board 810 replaced, the license history management unit 370 compares the license history 310 held in the FRAM 300 with the license history of the license file 830 held in the flash memory 820. To do.

  As a result of the comparison, since the license history management unit 370 has three license histories in the license file 830 held in the flash memory 820 and two license histories 310 held in one FRAM 300, the license history management unit 370 holds the license held in the flash memory 820. It can be seen that the license history of the file 830 is larger. At this time, the license history restoration process shown in FIG. 7 is performed. More specifically, a return process 840 is performed from the flash memory 820 to the FRAM 300. As a result, the state of the device transitions to the state 880, and the license history of the FRAM 300 becomes the state of the license history 850. As a result, in addition to the original uddi1 and uid2 in the FRAM, license histories of three unrelated devices BBBB9999999, which are udid3, 4, and 5, are held, and the license history of the license file 830 Consistency is not maintained. As a result, the following problems occur.

  Although there is an upper limit on the license history information that can be left in the FRAM in terms of capacity, the license history is wasted due to the license history information that is not used by the user.

  Also, at the next start-up, as a result of checking the number of license histories in the FRAM and the flash memory, the license history held in the FRAM is now larger than the license history held in the flash memory, so the license history restoration process is performed. It will be.

  Further, unlike this embodiment, consider a case where the number of license histories held by the FRAM and the flash memory is the same. In that case, since the number of license histories is the same, the license history restoration processing is not performed. In other words, the license history held by the used board remains on the main board. In this state, if the license history information held by the FRAM is cleared, there is a possibility that the license histories uuid1 and uuid2 used by the user who should be managed are deleted in terms of license management.

  FIG. 9 shows a license history return processing method corresponding to a used board in order to eliminate the situation of FIG. The device status 950 is the same as the license history status shown in FIG. The serial number of the device is AAA1234567, and the license history 310 and the license file 340 include two license histories, uuid1 and uuid2. Consider a case where the main body board 810 is replaced from this state (corresponding to the operation of the board replacement 900), and the device state transitions to the state 870.

  The used main body board 810 has a flash memory 820. Here, this used board 810 is used in a device having the serial number BBBB9999999, and the license history file 830 includes three histories of uid3, uid4, and uid5 as license histories, and includes serial number information BBBB9999999. keeping. A state 960 is a state in which the main body board 320 is replaced with the used main body board 810. When the device is activated with the main board 810 replaced, the license history management unit 370 compares the serial number held in the license file 830 of the flash memory 820 with the serial number of the device.

  If the serial number values are different, the license file 830 is deleted based on the judgment that a used board is attached. This corresponds to erasing by erasing the license ID. In the case of the first embodiment, the license file 830 is deleted in the process 910 because they are different from BBBB9999999 and AAA1234567, respectively. As a result, the status 970 is obtained, and the license file 830 is deleted from the flash memory 820. The license file 930 indicates an empty file having no substance. Further, the license history management unit 370 compares the license history 310 held in the FRAM 300 with the license history held in the license file 930 stored in the flash memory 810.

  As a result of the comparison, the license history management unit 370 has zero license histories in the insubstantial license file 930 of the flash memory 810 and two license histories 310 stored in one FRAM 300. It can be seen that the history 310 is more frequent. If the license history restoration process shown in FIG. 7 is executed at this time, the restoration process 920 is executed from the license history 310 stored in the FRAM 300 to the flash memory 810. As a result, the state of the device transitions to the state 980, and the license history is restored from the FRAM 300 to the history of the license file 940. As a result, unlike the result of FIG. 8, the consistency between the FRAM 310 and the license history file 940 is maintained. That is, by maintaining consistency, the license history will not be cleared even if board replacement or FRAM replacement is performed thereafter, and there is no problem as a license management system.

  FIG. 10 shows a flowchart of the license history return process taking into account used boards executed by the license history management unit 370.

  In S1000, the device is activated. In step S1010, a comparison is made as to whether the serial number of the device matches the serial number of the license history file. If they match, the process advances to step S1020, and the license history management unit 370 checks the consistency of the license history. Here, the license history consistency check means checking the number of license histories in the FRAM and the flash memory. If the serial number values do not match in S1010, the process proceeds to S1030, the license history file is deleted, and then the process proceeds to S1020.

  In S1040, the number of license histories of the FRAM and flash memory is checked. If the numbers at this time match, the process proceeds to S1050 without doing anything, and the license history restoration process ends. On the other hand, when the number of license histories in the flash memory is larger than the number of license histories in the FRAM, the process proceeds to S1060, and the contents of the license history are restored from the flash memory to the FRAM. Further, the process ends in S1050. On the other hand, if the number of license histories in the FRAM is larger than the number of license histories in the flash memory, the process proceeds to S1070, and the contents of the license history are restored from the FRAM to the flash memory. Further, the process ends in S1050.

<Example of replacement of SoftID board>
FIG. 11 shows an example in which the serial number may change due to the replacement of the SoftID board. The device status in FIG. 11 is the same as the license history status shown in FIG. The serial number of the device is AAA1234567, and the license history 310 and the license file 340 have two histories, uuid1 and uuid2.

  In this state, the SoftID board may be damaged for some reason (1100), and the serial number of the device may not be acquired (1110). At this time, as a result, the serial number of the device becomes a NULL value.

  Alternatively, when a measure is taken to replace the SoftID board (1120), the serial number may become a special serial number for service parts (1130) as a result.

  In the case of the above example, if the processing shown in the flowchart of FIG. 10 is performed, in S1010, the serial numbers are not necessarily matched, and as a result, the license file is deleted based on the determination of the used board. (S1030). As a result, when there is a problem on the SoftID board side, the license file restoration processing is performed, which is obviously wasteful processing. Therefore, FIG. 12 is a flowchart in consideration of returning such a special serial number. After the device is started in S1200, the device serial number is checked in S1210. At this time, if the serial number is a NULL value or a predetermined number for a service part, the process proceeds to S1260 without performing a specific process so as not to enter the license history recovery process.

  If the serial number is other than the above, the process proceeds to S1220. In S1220, it is compared whether the serial number of the device matches the serial number of the license history file. If they match, the process advances to step S1230, and the license history management unit 370 checks the consistency of the license history.

  Here, the license history consistency check means checking the number of license histories in the FRAM and the flash memory. If the serial number values do not match in S1220, the process advances to S1240 to delete the license history file, and then advances to S1230. In S1250, the number of license histories of the FRAM and flash memory is checked. If the numbers at this time match, the process proceeds to S1260 without doing anything, and the license history recovery process ends.

  On the other hand, if the number of license histories in the flash memory is larger than the number of license histories in the FRAM, the process proceeds to S1270, and the contents of the license history are restored from the flash memory to the FRAM. Further, the processing ends in S1260. Conversely, when the number of license histories in the FRAM is larger than the number of license histories in the flash memory, the process proceeds to S1280, and the contents of the license history are restored from the FRAM to the flash memory. Further, the processing ends in S1260.

810 Used board 820 Flash memory attached to used board 830 License history file of used board 910 License serial number comparison and deletion of license history file 930 Deleted license history file

Claims (7)

A device that can hold applications that can be used by using a license,
A first memory that holds a license ID for identifying the license when the application becomes available by using the license;
A second memory for holding the license ID in order to back up the license ID held in the first memory;
When the device ID for identifying the device held in the second memory matches the device ID assigned to the device, the license ID held in the first memory is changed to the second memory. Control means for controlling to hold the license ID held in the first memory in the second memory after erasing the license ID already held in the second memory if they do not match And a device comprising:   The second memory is a memory mounted in a different device different from the device, and the license ID already held in the second memory is an application that can be used in the different device. The device according to claim 1, wherein the device ID is a device ID of the other device.   When the device ID for identifying the device held in the second memory together with the license ID matches the device ID assigned to the device, the control means erases the second memory. 3. The apparatus according to claim 1, wherein control is performed such that the license ID held in the first memory is held in the second memory without performing processing. 4. The apparatus is an image forming apparatus having a print unit and / or a scan unit,
The apparatus according to any one of claims 1 to 3, wherein the application is an application for operating the print unit or the scan unit.   The process of holding the license ID held in the first memory in the second memory means that the number of license IDs held is larger than the number of license IDs held in the second memory. 5. The license history restoration process for copying from the memory of 1 to the second memory having a smaller number of license IDs than the first memory. 6. The device described in 1. A control method for controlling a device capable of holding an application that can be used by using a license,
The first memory holds a license ID for identifying the license when the application becomes available by using the license,
The second memory retains the license ID in the same manner as the first memory in order to back up the license ID stored in the first memory.
When the device ID for identifying the device held in the second memory matches the device ID assigned to the device, the control means assigns the license ID held in the first memory to the first ID. If the license ID stored in the second memory does not match, the license ID already stored in the second memory is erased, and then the license ID stored in the first memory is controlled to be stored in the second memory. A control method for controlling an apparatus.   A program for causing a computer to execute the control method according to claim 6.

Images