License management apparatus and license management system

Abstract

To provide a license management apparatus and a license management system that facilitate the management of licenses applied to printing devices.SOLUTION: According to an embodiment, a license management apparatus has a first communication interface, a second communication interface, a memory, and a processor. The first communication interface communicates with a management server. The second communication interface communicates with a printing device having a specific function whose usage restrictions are lifted by a license issued by the management server. The memory stores a license management table that stores licenses issued by the management server obtained via the first communication interface. The processor grants the licenses stored in the license management table to the printing device in response to a request from the printing device communicating via the second communication interface.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] FIELD An embodiment of the present invention relates to a license management device and a license management system. [Background technology]

[0002] Conventionally, some printers (printing devices), such as label printers, allow specific functions to be used by purchasing a license. For example, some thermal printers used in label printers are compatible with thermal heads with different dot resolutions. In this case, the thermal printer can be operated with a high-resolution printing function enabled by purchasing a license. In addition, printers may impose usage restrictions on resolution conversion, and the restrictions on resolution conversion can be lifted by purchasing a license.

[0003] However, the problem with such printers is that each user must purchase a license to use a specific function, which means that it is difficult to easily change the licensed functions of conventional printers, and as a result, users are often hesitant to purchase a license. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-25616 Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a license management device and a license management system that facilitates the management of licenses applied to printing devices. [Means for solving the problem]

[0006] According to an embodiment, the license management device has a first communication interface, a second communication interface, a memory, and a processor. The first communication interface communicates with a management server. The second communication interface communicates with a printing device having a specific function whose usage restrictions are lifted by a license issued by the management server. The memory stores a license management table that stores licenses issued by the management server obtained via the first communication interface. The processor grants the license stored in the license management table to the printing device in response to a request from the printing device communicating via the second communication interface. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of an image forming system as a license management system having a digital multifunction peripheral as an image forming apparatus including a license management device according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of a digital multifunction peripheral as an image forming apparatus including a license management device according to an embodiment. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of a label printer as a printing device in an image forming system as a license management system according to an embodiment. [Figure 4] FIG. 4 is a block diagram showing an example of the configuration of a management server in an image forming system as a license management system according to an embodiment. [Figure 5] FIG. 5 is a flowchart for explaining an example of the operation of a license issuing process by a management server in an image forming system serving as a license management system according to an embodiment. [Figure 6] FIG. 6 is a flowchart for explaining an example of the operation of a license acquisition process performed by a digital multifunction peripheral as a license management device according to the embodiment. [Figure 7]FIG. 7 is a flowchart illustrating an example of the operation of a license management process performed by a digital multifunction peripheral as a license management device according to the embodiment. [Figure 8] FIG. 8 is a flowchart for explaining an example of the operation of a label printer as a printing device in an image forming system as a license management system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, this embodiment will be described with reference to the drawings. First, a description will be given of the configuration of an image forming system 1 as a license management system having a digital multifunction peripheral 3 as an image forming apparatus including a license management device according to an embodiment. FIG. 1 is a diagram showing an example of the configuration of an image forming system 1 as a license management system according to an embodiment. The image forming system (license management system) 1 includes a digital multi-functional peripheral (MFP) 3, label printers 5 (5A, 5B, 5C) as printing devices, a management server 7, and an accounting server 8.

[0009] The digital multifunction peripheral 3 is an example of an image forming apparatus that includes a license management device. The digital multifunction peripheral 3 as a license management device manages licenses that can be applied to a label printer 5 as a printing device. The digital multifunction peripheral 3 as an image forming apparatus that includes a license management device is installed in, for example, a work area.

[0010] The digital multifunction peripheral 3 has, for example, a system control unit 21, an operation panel 22, a printer 23, and a scanner 24 (see FIG. 2). In the digital multifunction peripheral 3 configured as above, the system control unit 21 operates as a license management device. The digital multifunction peripheral 3 as a license management device has a function to communicate with each label printer 5 (5A, 5B, 5C) as a printing device and a function to communicate with the management server 7 via the network.

[0011] The digital multifunction peripheral 3, which serves as a license management device, acquires licenses issued by the management server 7 and provides the licenses acquired from the management server 7 to the label printer 5. For example, the digital multifunction peripheral 3 requests the management server 7 to issue a license applicable to the label printer, and acquires the license issued by the management server 7 in response to the request. The digital multifunction peripheral 3 holds (manages) the licenses issued by the management server 7 and provides the held licenses in response to usage requests from the label printer 5.

[0012] The label printer 5 (5A, 5B, 5C) is an example of a printing device that has a specific function whose usage restrictions are lifted by a license. The label printer 5 (5A, 5B, 5C) allows the specific function to be used by lifting the usage restrictions of the specific function by a license. In this embodiment, the label printer 5, which is an example of a printing device, has a printing mechanism that thermally prints (prints) an image on a label as a medium. Many label printers 5 have a simple configuration to reduce manufacturing costs, etc. The label printer 5 is an example of a printing device for which it is difficult to provide a configuration for the management server 7 to issue a license in response to user operation.

[0013] However, printing devices with specific functions whose usage restrictions are lifted by a license are not limited to label printers or thermal printers. For example, printing devices may have a printing mechanism that uses an image formation method other than thermal, such as an inkjet method. The printing device in the image forming system 1 as a license management system may be any device that is configured to receive a license from the digital multifunction peripheral 3.

[0014] The management server 7 and billing server 8 are provided in a cloud service 9 that provides services such as issuing licenses to the digital multifunction peripheral 3 and label printer 5. In the cloud service 9, the management server 7 has a function for communicating with the digital multifunction peripheral 3 via a network. The management server 7 issues licenses to be used by the label printer 5 in response to requests from the digital multifunction peripheral 3. The billing server 8 also performs billing processing associated with the issuance of the licenses.

[0015] Next, the configuration of the digital multifunction peripheral 3 as an image forming apparatus including the license management device according to the embodiment will be described. FIG. 2 is a block diagram showing an example of the configuration of a digital multifunction peripheral 3 as an image forming apparatus including a license management device according to an embodiment. As shown in FIG. 2, the digital multifunction peripheral 3 includes a system control unit (system controller) 21, an operation panel 22, a printer 23, and a scanner 24.

[0016] The system control unit 21 controls the entire digital multifunction peripheral 3. The system control unit 21 includes a processor 31, a ROM 32, a RAM 33, a data memory 34, a communication interface (I / F) 35, an NW (network) interface (I / F) 36, and the like.

[0017] The processor 31 executes programs to realize various processing functions. The processor 31 is, for example, a CPU. The processor 31 is connected to the processor 41 of the operation panel 22, the printer 23, the scanner 24, and the like via an internal interface.

[0018] The ROM 32 functions as a program memory that stores programs. The ROM 32 is a non-volatile memory that cannot be rewritten. The RAM 33 functions as a working memory or a buffer memory. The processor 31 performs various processes by using the RAM 33 to execute programs stored in the ROM 32 or the data memory 34.

[0019] The data memory 34 is a rewritable nonvolatile memory. For example, the data memory 34 is configured with a storage device such as an HDD (hard disk drive) or an SSD (solid state drive). The data memory 34 stores various types of data such as control data, application programs (hereinafter also referred to as applications), control data, setting information, and image data.

[0020] In this embodiment, the data memory 34 stores a license management table 341 and a printer management table 342. The license management table 341 stores management data for licenses that can be granted to the label printer 5. The license management table 341 stores information indicating the licenses issued by the management server 7. The license management table 341 stores information indicating the status of each license issued by the management server 7 being granted to the label printer 5. For example, the license management table 341 stores information indicating the type of license that can be granted to the label printer 5, the number of licenses held, the number currently being granted (number of licenses in use), etc.

[0021] The printer management table 342 stores printer management information for each label printer 5. The printer management table 342 stores printer management information relating to each individual label printer 5. For example, the printer management table 342 stores printer management information including information indicating specific functions that can be used by license. The printer management table 342 also stores, as printer management information, an encryption key (key code) for each label printer 5. Here, the encryption key for each label printer 5 is key information that corresponds to key information (decryption key) held by each label printer 5.

[0022] The communication interface 35 is a communication interface (first communication interface) for performing data communication with each label printer 5 (5A, 5B, 5C) that is subject to functional restrictions imposed by the license. The communication interface 35 may include an interface for communicating with each label printer 5 used within the work area, for example, by wireless or wired communication.

[0023] The NW interface 36 is a communication interface (second communication interface) for communicating with each device connected to the network. In the image forming system 1 according to this embodiment, the NW interface 36 may include an interface for communicating with the management server 7 via the network.

[0024] The operation panel 22 is a user interface. The operation panel 22 has a processor 41, a display device 42, a touch panel (operation device) 43, and operation buttons (operation device) 44. The display device 42 is a display that displays operation guides and the like. The touch panel 43 is provided on the display screen of the display device 42. The touch panel 43 detects a location on the display screen of the display device 42 that is touched by the user. The operation buttons 44 are buttons for inputting predetermined instructions.

[0025] The processor 41 of the operation panel 22 controls the operation panel 22. The processor 41 performs various processes by executing programs stored in an internal memory or an external memory. The processor 41 is connected to the processor 31 of the system control unit 21, and controls the operation panel 22 in accordance with instructions from the processor 31 of the system control unit 21. For example, the processor 41 controls the display content to be displayed on the display device 42 in accordance with instructions from the processor 31 of the system control unit 21. The processor 41 also detects inputs to the touch panel 43 and the operation buttons 44, and supplies information indicating the input content to the processor 31 of the system control unit 21.

[0026] The printer 23 is an image forming unit provided in the digital multifunction peripheral 3 itself. The printer 23 forms an image on a medium (image forming medium) such as paper. The printer 23 prints an image to be printed supplied from the system control unit 21 onto paper taken out of a paper feed cassette, for example. The printer 23 may form an image using any image forming method. For example, the printer 23 may print an image on a medium using an electrophotographic method, or may print an image on a medium using an inkjet method.

[0027] The scanner 24 is a device that reads an image of a document. The scanner 24 is installed, for example, on the top of the main body of the digital multifunction peripheral 3. The scanner 24 optically reads the image of a document set on a document glass or a document set in an automatic document feeder (ADF). The scanner 24 outputs image data of the document as a result of reading the image of the document.

[0028] Next, the configuration of the label printer 5 as the printing device in the image forming system 1 according to the embodiment will be described. FIG. 3 is a block diagram showing an example of the configuration of a label printer 5 as a printing device in the image forming system 1 according to the embodiment. As shown in FIG. 3, the label printer 5 includes a processor (second processor) 51, a memory 52, a communication interface (I / F) 53, a display unit 54, an operation unit 55, and a printing mechanism (printing mechanism) 56.

[0029] The processor 51 executes programs for carrying out various processes. The processor 51 is, for example, a CPU. The processor 51 is connected to each unit within the label printer 5 via an internal interface. The processor 51 executes programs stored in the memory 52 to carry out various processes.

[0030] The memory 52 includes, for example, a ROM, a RAM, and a data memory. The ROM of the memory 52 is a non-volatile memory that cannot be rewritten and stores preset programs, control data, and the like. The RAM of the memory 52 functions as a working memory or a buffer memory. The data memory of the memory 52 is a non-volatile memory that can be rewritten and stores programs, control data, setting information, and other data. The data memory of the memory 52 also includes a storage area that securely stores key information for decrypting data encrypted by the digital multifunction peripheral 3.

[0031] The communication interface 53 is a communication interface (third communication interface) for communicating with the digital multifunction peripheral 3. The communication interface 53 may include an interface of a communication method corresponding to the communication interface provided in the digital multifunction peripheral 3.

[0032] The display unit 54 is a display that displays operation guides and the like. For example, the display unit 54 is configured with a liquid crystal display device or an organic EL display. The operation unit 55 accepts operations by the user. For example, the operation unit 55 is configured with a group of buttons that are pressed by the user. Alternatively, the operation unit 55 may be configured with a touch panel provided on the display screen of the display unit 54.

[0033] Printing mechanism 56 prints an image on a medium. In the configuration example shown in FIG. 3, printing mechanism 56 is a thermal printing unit having paper feed mechanism 57, sensor 58, thermal head 59, etc. In printing mechanism 56, paper feed mechanism 57 feeds paper (medium) as labels. Sensor 58 detects the paper (medium) fed by paper feed mechanism 57 at a predetermined position (for example, at the printing position or just before the printing position). Thermal head 59 is driven and controlled according to the image to be printed, and prints the image on the paper fed by paper feed mechanism 57. Printing mechanism 56 may also be provided with sensors that detect various malfunctions, such as paper jams.

[0034] In this embodiment, the printing mechanism 56 has a specific function whose usage restrictions are lifted by a license granted by the digital multifunction device 3. For example, the printing mechanism 56 is configured to be able to print at a specific resolution (specific function) with a license, but is unable to print at the specific resolution without a license. As a specific example, if the printing mechanism 56 is configured to be able to print at 200 dpi or 300 dpi, the label printer 5 is enabled to print at 300 dpi with a license.

[0035] Next, the configuration of the management server 7 in the image forming system 1 according to the embodiment will be described. FIG. 4 is a block diagram showing an example of the configuration of the management server 7 in the image forming system 1 according to the embodiment. As shown in FIG. 4, the management server 7 includes a processor 61, a ROM 62, a RAM 63, a data memory 64, a NW interface (I / F) 65, an interface 66, and the like.

[0036] The processor 61 executes programs for carrying out various processes. The processor 61 is, for example, a CPU. The processor 61 is connected to each unit in the management server 7 via an internal interface. The processor 61 executes programs stored in the ROM 62 or the data memory 64 using the RAM 63 to carry out various processes.

[0037] The ROM 62 is a non-volatile memory that cannot be rewritten and stores preset programs, control data, etc. The RAM 63 functions as a working memory or a buffer memory.

[0038] The data memory 64 is a rewritable non-volatile memory. The data memory 64 stores various types of data including programs, control data, and setting information. In this embodiment, the data memory 64 stores information obtained from the digital multifunction peripheral 3. The data memory 64 saves, as information obtained from the digital multifunction peripheral 3, maintenance information for the digital multifunction peripheral itself and maintenance information for each label printer 5 connected to the digital multifunction peripheral 3. For example, the data memory 64 stores each piece of maintenance information in association with identification information that identifies the digital multifunction peripheral 3 and each label printer 5.

[0039] The NW interface 65 is a communication interface for performing communication via a network. In the image forming system 1, the management server 7 communicates with the digital multifunction peripheral 3 via the network using the NW interface 65.

[0040] The interface 66 is an interface for communicating with the billing server 8. For example, the interface 66 may be a communication interface for locally connecting to the billing server 8. Furthermore, when the management server 7 and the billing server 8 are configured to communicate with each other via a network, the interface 66 may be included in the NW interface 65.

[0041] Next, a process in which the management server 7 issues a license in response to a request from the digital multifunction peripheral 3 including the license management device according to the embodiment will be described. FIG. 5 is a flowchart for explaining a process in which the management server 7 issues a license in response to a request from the digital multifunction peripheral 3 including the license management device according to the embodiment. The management server 7 of the cloud service 9 communicates with the digital multifunction peripheral 3 over the network via the NW interface 65. The processor 61 of the management server 7 receives a request for issuing a license to be granted to the label printer 5 from the digital multifunction peripheral 3 with which it communicates via the NW interface 65 (ACT21).

[0042] When the processor 61 of the management server 7 receives a license issuance request from the digital multifunction peripheral 3 (ACT21, YES), it determines whether the requested license can be issued (ACT22). For example, the issuance request from the digital multifunction peripheral 3 includes information for identifying the license to be issued. The processor 61 identifies the license to be issued from the issuance request, and determines whether the identified license can be issued to the digital multifunction peripheral 3. If the requested license cannot be issued (ACT22, NO), the processor 61 notifies the digital multifunction peripheral 3 that made the issuance request that the license cannot be issued, and ends the process.

[0043] If the requested license can be issued (ACT22, YES), the processor 61 of the management server 7 transmits a license packet including information indicating the license that can be issued to the digital multifunction peripheral 3 (ACT23). Here, the processor 61 may also transmit fee information for issuing the license to the digital multifunction peripheral 3 as a license packet.

[0044] After transmitting the license packet, the processor 61 of the management server 7 monitors whether the license packet has been accepted by the destination digital multifunction peripheral 3 (ACT24). If the processor 61 of the management server 7 cannot confirm that the digital multifunction peripheral 3 has accepted the license packet (ACT24, NO), it determines whether the permitted acceptance time has expired (ACT25). If the time elapsed since the license packet was transmitted is within the permitted acceptance time (ACT25, NO), the processor 61 continues to permit acceptance (ACT26) and returns to ACT24. If the permitted acceptance time has expired without the license being accepted (ACT25, YES), the processor 61 invalidates the license provided by the transmitted license packet and terminates the process.

[0045] When the processor 61 of the management server 7 confirms that the digital multifunction peripheral 3 has received the license packet (ACT24, YES), it executes accounting processing to issue (validate) the license (ACT27). The processor 61 executes, via the accounting server 8, a payment process by the specific user for the fee for issuing the license. For example, the processor 61 acquires payment information for payment by the specific user from the digital multifunction peripheral 3, and executes, via the accounting server 8, a payment process for the fee based on the acquired payment information.

[0046] When the payment of the fee for the license issuance is completed, the processor 61 of the management server 7 performs the license issuing process (ACT28). For example, the processor 61 of the management server 7 issues (validates) the license in the license packet sent to the digital multifunction peripheral 3 by managing the license as having been issued. The processor 61 of the management server 7 also notifies the digital multifunction peripheral 3 of the completion of the license issuance and payment, and permits the digital multifunction peripheral 3 to use the license.

[0047] As described above, the management server of the image forming system as a license management system can issue licenses that can be granted to label printers in response to issuance requests from digital multifunction peripherals. The management server can also work with a billing server to settle fees associated with the issuance of licenses in response to requests from digital multifunction peripherals.

[0048] Next, the operation of the digital multifunction peripheral 3 as the image forming apparatus including the license management device in the image forming system 1 as the license management system according to the embodiment will be described. The digital multifunction peripheral 3 has a configuration as an image forming device, and also functions as a license management device that manages licenses granted to each label printer 5. Here, it is assumed that an application program for license management (license management program) is installed in the system control unit 21 of the digital multifunction peripheral 3.

[0049] The system control unit 21 of the digital multifunction peripheral 3 operates as a license management device by executing a license management program. For example, the license management program is installed in the data memory 34 and executed by the processor 31. The processor 31 of the digital multifunction peripheral 3 manages licenses granted to each label printer 5 connected to the digital multifunction peripheral 3 by executing a license management application.

[0050] First, a process will be described in which the digital multifunction peripheral 3 including the license management device according to the embodiment acquires a license issued by the management server 7 that can be granted to the label printer 5. FIG. 6 is a flowchart for explaining an example of the operation of a process in which the digital multifunction peripheral 3 including the license management device according to the embodiment acquires a license issued by the management server 7. Here, it is assumed that a specific user, such as an administrator, who has administrative authority over the label printer 5, requests the issuance of a license that can be granted to the label printer 5. The processor 31 of the system control unit 21 of the digital multifunction peripheral 3 receives an input from the specific user requesting the issuance of a license that can be granted to the label printer 5 (ACT31).

[0051] For example, the processor 31 of the digital multifunction peripheral 3 logs in to the management server 7 as a specific user through user authentication using authentication information input by the user via the operation device 43 or the like. When the specific user has successfully logged in to the management server 7, the processor 31 of the digital multifunction peripheral 3 accepts input of a license issuance instruction from the specific user. Here, the specific user uses the operation device 43 or the like to input information specifying the license to be issued and inputs an instruction to issue the license.

[0052] When a license issuance instruction is input, the processor 31 of the digital multifunction peripheral 3 transmits a license issuance request to the management server 7 in response to the issuance instruction (ACT32). After transmitting the license issuance request, the processor 31 of the digital multifunction peripheral 3 waits for a response from the management server 7. If the processor 31 cannot acquire a license packet in response to the issuance request from the management server 7 (ACT33, NO), it determines that the license cannot be issued and ends the process.

[0053] When the processor 31 of the digital multifunction peripheral 3 receives a license packet as a response to the issuance request (ACT33, YES), it accepts input of issuance confirmation of the license indicated by the license packet (ACT34). The processor 31 also accepts input of payment information for the specific user to pay the fee required for license issuance along with the issuance confirmation. When the specific user inputs the issuance confirmation and payment information using the operation device 43 or the like, the processor 31 transmits the input issuance confirmation and payment information to the management server 7 (ACT35). As a result, the management server 7 performs the charging process and license issuance process using the payment information through the operations described above.

[0054] If the processor 31 of the digital multifunction peripheral 3 does not receive a notification of license issuance completion from the management server 7 (ACT36, NO), it determines that the license cannot be issued and ends the process. For example, if the billing process at the billing server 8 based on the payment information fails, the processor 31 receives a notification from the management server 7 that the license cannot be issued due to billing failure. In this case, the processor 31 displays, for example, on the display device 42, that the license cannot be issued due to billing failure, and ends the process.

[0055] When the processor 31 of the digital multifunction peripheral 3 receives a notification from the management server 7 that the license issuance has been completed (ACT36, YES), the processor 31 of the digital multifunction peripheral 3 enables the license issued by the management server 7 to be granted to the label printer 5 (ACT37). In other words, the processor 31 of the digital multifunction peripheral 3 stores the license issued by the management server 7 in the license management table 341, enabling the license to be granted to the label printer 5.

[0056] As described above, the digital multifunction peripheral as a license management device can request the management server to issue a license to be granted to a label printer in response to an issuance instruction from a user. The digital multifunction peripheral can also acquire the license issued by the management server in response to the issuance request and manage it as a license that can be granted to a label printer. Furthermore, the digital multifunction peripheral can pay the fee for license issuance using the payment information of a specific user, enabling license issuance and fee payment on a per-user basis.

[0057] Next, a license management process performed by the digital multifunction peripheral 3 including the license management device according to the embodiment will be described. FIG. 7 is a flowchart for explaining an example of the operation of license management processing by the digital multifunction peripheral 3 including the license management device according to the embodiment. The processor 31 of the digital multifunction peripheral 3 receives a license use request (a request to remove usage restrictions on specific functions imposed by the license) from a label printer 5 with which communication is possible via the communication interface 35 (ACT41). The license use request from the label printer specifies information indicating the requested license or information indicating specific functions that become available under the license. The use request may also specify the period during which the license is to be used in the label printer 5 (usage period).

[0058] When the processor 31 of the digital multifunction peripheral 3 receives a license use request, it determines whether or not the requested license can be granted to the label printer 5 (ACT42). For example, the processor 31 refers to the license management table 341 to determine whether or not the requested license can be granted to the label printer 5.

[0059] If the processor 31 of the digital multifunction peripheral 3 cannot grant the requested license (ACT42, NO), it notifies the requesting label printer 5 that the license cannot be granted, and ends the processing. For example, the processor 31 may notify the requesting label printer 5 of the reason why the requested license cannot be granted. In this case, the label printer 5 that requested the license may display on the display unit 54 the reason why the license was not granted, based on the notification from the digital multifunction peripheral 3.

[0060] Furthermore, if a license can be granted (ACT42, YES), the processor 31 of the digital multifunction peripheral 3 sets an expiration date for the license to be granted to the requesting label printer 5 (ACT43). For example, the expiration date attached to the license may be a predetermined period, may be set based on the usage period specified in the usage request from the label printer 5, or may be unlimited. Furthermore, the license may not have an expiration date. Once the processor 31 determines the license expiration date, it generates license data (license packet) that attaches expiration date information to the license, which is information for lifting usage restrictions on a specific function.

[0061] When the processor 31 of the digital multifunction peripheral 3 generates the license data, it encrypts the generated license data using the encryption key of the label printer 5 to which the license is to be granted (ACT44). The encryption key used to encrypt the license data needs to be such that only the label printer 5 to which the license is to be granted can decrypt it. In other words, the encryption key used for encryption needs to correspond to the decryption key held by the label printer to which the license is to be granted. For example, the digital multifunction peripheral 3 securely stores the encryption key used for encryption for each label printer 5 in the printer management table 342. This allows only the label printer 5 to which the license is to be granted to decrypt the encrypted license data, and allows only that label printer 5 to obtain the license data.

[0062] After encrypting the license data, the processor 31 of the digital multifunction peripheral 3 sends the encrypted license data to the label printer 5 to which the license is to be granted (the label printer that requested use) (ACT45). After sending the license data, the processor 31 records information indicating that the license has been granted to the label printer 5 in the license management table 341. The processor 31 also monitors the usage status of the license in the label printer 5 to which it sent the license data.

[0063] After transmitting the encrypted license data, the processor 31 of the digital multifunction peripheral 3 accepts the relinquishment of the license from the label printer 5 (ACT46). For example, the label printer 5 may notify the digital multifunction peripheral 3 of the relinquishment of the license when processing using the granted license is completed. When the processor 31 receives the relinquishment of the license from the label printer 5 (ACT46, YES), it invalidates the use of the license in the label printer 5 (ACT49).

[0064] Here, invalidating the use of the license in the label printer 5 means releasing the license that has been granted (assigned) to the label printer 5. By invalidating the use of the license in the label printer 5 (releasing the license that has been granted to the label printer 5), the digital multifunction peripheral 3 can recover the granted license and reassign it.

[0065] If the license has not been abandoned (ACT46, NO), the processor 31 of the digital multifunction peripheral 3 monitors the validity of the license granted to the label printer 5 (ACT47). For example, the processor 31 determines whether the license is valid based on whether the expiration date attached to the license granted to the label printer 5 has passed. In this case, the processor 31 determines the license to be valid if it is within the expiration date (ACT47, YES) and permits continued use of the license (ACT48). The processor 31 also determines that a license that has passed the expiration date is invalid (ACT47, NO) and invalidates use of the license on the label printer 5 (releases the license assigned to the label printer) (ACT48).

[0066] Furthermore, the processor 31 of the digital multifunction peripheral 3 may invalidate the use of the license in the label printer 5 if the license is not used within a specified time. In this case, the processor 31 determines whether the license is valid based on whether the license has been used within the specified time. For example, if the license has been used within the specified time, the processor 31 determines that the license is valid (ACT47, YES) and permits continued use of the license (ACT48). Furthermore, if the license has not been used within the specified time (ACT48, NO), the processor 31 invalidates the use of the license in the label printer 5 (ACT48).

[0067] When the processor 31 of the digital multifunction peripheral 3 invalidates the use of the license in the label printer 5, it updates the license management information in the license management table 341 (ACT50). For example, the processor 31 manages the invalidated license in the license management table 341 as a license that can be granted to the label printer 5. This allows the processor 31 to collect the license that has been invalidated for use in a specific label printer and manage it again as a license that can be granted to the label printer.

[0068] Next, the operation of the label printer 5 to which a license is granted from the digital multifunction peripheral 3 including the license management device according to the embodiment will be described. FIG. 8 is a flowchart illustrating an example of the operation of a label printer to which a license is granted from a digital multifunction peripheral 3 including a license management device according to an embodiment. When the label printer 5 executes a specific function that is enabled by a license, the label printer 5 requests the use of the license from the digital multifunction peripheral 3, which serves as the license management device. For example, the processor 51 of the label printer 5 receives an instruction to execute the specific function that is input by the user using the operation unit 55. Upon receiving the instruction to execute the specific function, the processor 51 connects to the digital multifunction peripheral 3, which serves as the license management device, via the communication interface 53. Upon connecting to the digital multifunction peripheral 3, the processor 31 transmits a request to use the license to execute the specific function to the digital multifunction peripheral 3 (ACT61).

[0069] After transmitting a license use request to the digital multifunction peripheral 3, the processor 51 of the label printer 5 waits for a response to the use request from the digital multifunction peripheral 3 (ACT62). If the processor 51 receives a response to the use request indicating that a license cannot be granted, or if the processor 51 cannot receive a response to the use request (ACT62, NO), the processor 51 concludes that a license cannot be obtained and ends the process. For example, the processor 51 displays on the display unit 54 a message that a specific function cannot be executed because a license cannot be obtained, and ends the process.

[0070] When the processor 51 of the label printer 5 receives data in response to the usage request (ACT62, YES), it decrypts the received data using the decryption key information it holds (ACT63). Note that if the data sent from the digital multifunction device 3 to the label printer 5 is not encrypted, the processor 51 can omit the processing of ACT63.

[0071] The processor 51 of the label printer 5 decrypts the data received as a response to the license use request and determines whether the decrypted data includes a license (ACT64). If the decrypted data does not include a license (ACT64, NO), the processor 51 concludes that a license could not be acquired and ends the series of processes. For example, the processor 51 displays on the display unit 54 a message that a specific function cannot be executed because a license could not be acquired, and ends the process.

[0072] Furthermore, if the decrypted data has a license (ACT64, YES), the processor 51 of the label printer 5 acquires the license included in the decrypted data. Upon acquiring the license, the processor 51 releases the usage restrictions using the acquired license, thereby enabling the specific function to be executed (ACT65). With the license enabled, the processor 51 of the label printer 5 executes printing processing using the specific function in response to a user instruction.

[0073] The processor 51 of the label printer 5 permits execution of a specific function with the use restrictions imposed by the license lifted, and monitors the validity of the license (ACT66). For example, if the license has an expiration date, the processor 51 monitors whether the license has been invalidated by determining whether the expiration date has passed. If the license remains valid (ACT66, NO), the processor 51 continues to release the use restrictions imposed by the license on the specific function. If the processor 51 determines that the license has been invalidated (ACT66, YES), it invalidates the use of the license (ACT67). For example, if the expiration date attached to the license has passed, the processor 51 invalidates the license by making it unusable.

[0074] The processor 51 of the label printer 5 may also invalidate a license if it is not used within a specified time. For example, the processor 51 may determine whether a license has been invalidated based on whether the license was used within a specified time. In this case, the processor 51 keeps licenses that have been used within the specified time available for use, and invalidates licenses that have not been used within the specified time.

[0075] However, the validity of the license may be monitored by the digital multifunction peripheral 3. In this case, the processor 31 of the label printer 5 determines whether the license has been invalidated based on an instruction from the digital multifunction peripheral 3. In other words, when the processor 31 receives an instruction from the digital multifunction peripheral 3 to invalidate the license, it may restrict the use of a specific function by the license (invalidate the license).

[0076] As described above, the digital multifunction peripheral as a license management device acquires licenses that can be granted to label printers, which are issued by the management server. The digital multifunction peripheral manages the licenses that can be granted to label printers acquired from the management server, and grants licenses as appropriate in response to requests from the label printers.

[0077] This allows the digital multifunction peripheral to issue and manage licenses applied to label printers, eliminating the need for individual label printers to issue and manage licenses. Furthermore, because the digital multifunction peripheral can centrally manage licenses granted to multiple label printers, efficient license management can be implemented for the entire system. Furthermore, as a result of the license management described above, specific functions of the label printer can be used at a low cost, improving user convenience.

[0078] Furthermore, the digital multifunction peripheral, which functions as a license management device, sets an expiration date for the license it grants to the label printer. In this case, the digital multifunction peripheral invalidates the use of the expired license with the label printer and collects the license. This allows the digital multifunction peripheral to manage the use of licenses based on the expiration dates attached to the licenses granted to the label printer. As a result, the digital multifunction peripheral can manage licenses granted to multiple label printers as floating licenses, enabling efficient license management.

[0079] Furthermore, the digital multifunction peripheral, which functions as a license management device, invalidates the use of a license on a label printer if the license has not been used within a specified time. This allows the digital multifunction peripheral to collect the license from a label printer that has not used the license for more than the specified time. As a result, the digital multifunction peripheral can manage licenses according to the actual use of each label printer, achieving efficient license management throughout the system as a whole.

[0080] In the above-described embodiment, the license managed by the digital multifunction peripheral as a license management device is described as lifting restrictions on the use of specific functions. However, the license managed by the digital multifunction peripheral as a license management device is not limited to a license that lifts restrictions on the use of specific functions. For example, the license may be implemented as a license for updating programs and control data executed by the processor 31 of the label printer. In this case, the digital multifunction peripheral as a license management device can also control functions realized by software in each label printer by granting licenses.

[0081] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0082] 1...image forming system (information transmission system), 3...digital multifunction peripheral (license management device, image forming device), 5 (5A, 5B, 5C)...label printer (printing device), 7...management server, 8...billing server, 9...cloud service, 21...system control unit, 22...operation panel, 23...printer, 24...scanner, 31...processor (first processor), 34...data memory, 35...communication interface (first communication interface), 36...NW interface (second communication interface) interface), 41...processor, 42...display device, 43...touch panel (operation device), 44...operation button (operation device), 51...processor (second processor), 52...memory, 53...communication interface (third communication interface), 54...display unit, 55...operation unit, 56...printing mechanism (printing mechanism), 57...paper feed mechanism, 58...sensor, 59...thermal head, 61...processor, 64...data memory, 65...NW interface, 66...interface.

Claims

1. a first communication interface for communicating with a management server; a second communication interface for communicating with a printing device having a specific function whose usage restriction is lifted by a license issued by the management server; a memory that stores a license management table that stores licenses issued by the management server and acquired via the first communication interface; a processor that provides the license stored in the license management table to the printing device in response to a request from the printing device communicating via the second communication interface; A license management device having:

2. the processor transmits to the printing device a license encrypted with an encryption key that can be decrypted by the printing device that sent the request; The license management device according to claim 1 .

3. When a license granted to the printing device becomes invalid, the processor stores the invalid license in the license management table as a license that can be granted. The license management device according to claim 1 or 2.

4. the processor sets an expiration date for the license granted to the printing device; The license management device according to claim 1 or 2.

5. In a license management system having a license management device and a printing device, the license management device, a first communication interface for communicating with a management server; a second communication interface for communicating with the printing device; a memory that stores a license management table that stores licenses issued by the management server and acquired via the first communication interface; a processor that provides the license stored in the license management table to the printing device in response to a request from the printing device communicating via the second communication interface; The printing device includes: a printing mechanism having a specific function for which usage restrictions are set; a third communication interface for communicating with the license management device; a second processor that releases the usage restriction of the specific function in the printing mechanism based on the license issued by the management server, which is acquired from the license management device via the third communication interface; License management system.

Images