WO2020194604A1 - ライセンス移行ツール、プログラム、及びライセンス移行システム - Google Patents
ライセンス移行ツール、プログラム、及びライセンス移行システム Download PDFInfo
- Publication number
- WO2020194604A1 WO2020194604A1 PCT/JP2019/013379 JP2019013379W WO2020194604A1 WO 2020194604 A1 WO2020194604 A1 WO 2020194604A1 JP 2019013379 W JP2019013379 W JP 2019013379W WO 2020194604 A1 WO2020194604 A1 WO 2020194604A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- license
- key
- identifier
- license key
- plc
- Prior art date
Links
- 238000012546 transfer Methods 0.000 title claims abstract description 99
- 230000005012 migration Effects 0.000 claims description 78
- 238000013508 migration Methods 0.000 claims description 78
- 230000005540 biological transmission Effects 0.000 claims description 27
- 230000001172 regenerating effect Effects 0.000 claims description 6
- 238000007726 management method Methods 0.000 description 188
- 238000000034 method Methods 0.000 description 22
- 230000008569 process Effects 0.000 description 22
- 238000004891 communication Methods 0.000 description 21
- 230000006870 function Effects 0.000 description 21
- 238000013500 data storage Methods 0.000 description 17
- 230000008929 regeneration Effects 0.000 description 17
- 238000011069 regeneration method Methods 0.000 description 17
- 230000004044 response Effects 0.000 description 10
- 238000012790 confirmation Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 6
- 230000007704 transition Effects 0.000 description 5
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
Definitions
- the present invention relates to a license transfer tool, a program, and a license transfer system.
- the license management server managed by the application program distributor and the device on which the application program is installed communicate via the network, and the license management server Activation may be performed.
- the application program uninstalled from the device may be installed on another device. In this case, it is necessary to transfer the license of the application program.
- Patent Document 1 describes that the license is transferred as follows.
- the device from which the license is transferred When the application program is uninstalled, the device from which the license is transferred generates an uninstall certification code and sends the uninstall certification code to the license management server.
- the device to which the license is transferred generates the unique identification code and sends the unique identification code to the license management server.
- the license management server determines whether the received uninstall certification code and the unique identification code are valid, and if they are valid, permits license transfer. When permitting the license transfer, the license management server sends an installation permission notification to the device to which the license is transferred.
- the present invention has been made in view of the above circumstances, and an object of the present invention is to transfer a license between stand-alone devices that cannot communicate with a license management server.
- the license transfer tool transfers the license key indicating that the use of the application program is permitted between two or more devices that are not connected to the external network.
- the license key includes an identifier that identifies the device in which the license key is registered.
- the key acquisition means provided in the license transfer tool acquires the license key from the first device which is the device from which the license is transferred.
- the identifier acquisition means included in the license transfer tool acquires a second identifier that identifies the second device from the second device that is the device to which the license is transferred.
- the regeneration means provided by the license transfer tool deletes the first identifier that identifies the first device from the license key obtained from the first device, adds the second identifier of the second device as an identifier, and creates a new license. Generate a key and supply a new license key to the second device.
- the license transfer tool acquires a license key from the first device which is the license transfer source device, and identifies the second device from the second device which is the license transfer destination device. To get.
- the license transfer tool deletes the first identifier that identifies the first device from the license key obtained from the first device, adds the second identifier of the second device as an identifier, and generates a new license key. Supply a new license key to the second device. With such a configuration, licenses can be transferred between stand-alone devices that cannot communicate with the license management server.
- a block diagram showing a functional configuration of a license management system according to an embodiment of the present invention The figure which shows the hardware configuration of the license management system which concerns on embodiment.
- the figure which shows the structure of the program storage part of PLC which concerns on embodiment The figure which shows the structure of the license key storage part of PLC which concerns on embodiment
- the figure which shows the structure of the license key which concerns on embodiment The figure which shows an example of the data stored in the application conformity table which concerns on embodiment.
- the figure which shows an example of the data stored in the license registration table which concerns on embodiment The figure which shows an example of the menu screen of the license management tool which concerns on embodiment Flowchart of license issuance request processing of license management tool according to the embodiment
- the figure which shows an example of the selection screen which selects the target of registration of the license key which concerns on embodiment The figure which shows an example of the registration completion screen of the license key which concerns on embodiment
- the license management system 1 shown in FIG. 1 manages the license of the application program executed by the programmable logic controllers 101 and 102.
- the license management system 1 includes a license management tool 500 that manages license registration of a programmable logic controller used in a production line in a factory, and a license management server 600 that issues a license.
- Programmable logic controllers 101 and 102 are control devices that control mechanical devices (not shown) used in a production line in a factory.
- the programmable logic controllers 101 and 102 may be collectively referred to as a programmable logic controller 100 (PLC100).
- the license management tool 500 for example, a personal computer located in the same factory as the programmable logic controller 100 and having a dedicated program installed is used.
- the license management server 600 is, for example, a server under the control of a manufacturer that develops and sells application programs.
- the PLC100 controls a mechanical device connected via an internal network (not shown) in a factory by executing an application program sold as a product.
- the PLC100 needs to have a license indicating that the use of the application program is licensed.
- the PLC 100 can execute the application program if it has the license key of the application program.
- the license key is a code indicating that the PLC100 has a license.
- the license management server 600 issues a license key.
- the PLC100 is not connected to the external network and cannot communicate with the license management server 600.
- the external network is an open network such as the Internet.
- the license management tool 500 can communicate with the license management server 600 via an external network. Therefore, the license management tool 500 acquires the license key from the license management server 600 instead of the PLC 100, and supplies the acquired license key to the PLC 100.
- the license management tool 500 performs a process related to the transfer of the license key.
- the transfer of the license key is to transfer the license key from the PLC100 which has the license key for one application program to another PLC100.
- the PLC100 that has the license key will be able to execute the application program.
- the PLC100 that no longer has the license key cannot execute the application program.
- the PLC 100 includes a memory 11 for storing various programs and data, an input / output interface 12 for exchanging data between the license management tool 500 via a communication cable 701, and a PLC 100. It has an MPU (Micro Processing Unit) 13 that controls the whole.
- the memory 11 and the input / output interface 12 are connected to the MPU 13 via the bus 19 and communicate with the MPU 13.
- the memory 11 includes a volatile memory and a non-volatile memory.
- the memory 11 stores programs for realizing various functions of the PLC 100.
- the memory 11 stores a license management program 111, which is a program that causes the MPU 13 to execute processes such as storing and retrieving the license key. Further, the memory 11 is used as a work memory of the MPU 13.
- the memory 11 stores an identifier for uniquely identifying the PLC 100.
- the serial code assigned to the PLC 100 at the time of manufacturing the PLC 100 is used as the identifier assigned to the PLC 100.
- the memory 11 stores a user ID which is information for identifying the user.
- the user of the PLC100 is, for example, the administrator of the PLC100.
- the input / output interface 12 includes, for example, a USB controller, converts the data supplied from the MPU 13 into an electric signal, and outputs the converted signal to the license management tool 500 via the communication cable 701.
- the communication cable 701 is, for example, a USB cable. Further, the input / output interface 12 receives the electric signal output by the license management tool 500 via the communication cable 701, restores the received electric signal to data, and outputs the received electric signal to the MPU 13.
- the MPU 13 executes various programs stored in the memory 11 to realize various functions of the PLC 100. For example, by executing the license management program 111, processing such as storing and retrieving the license key is executed.
- the license management tool 500 is licensed via a memory 51 that stores various programs and data, an input / output interface 52 that exchanges data between the PLC 100 and the PLC 100 via a communication cable 701, and a network 702. It has a communication interface 53 that communicates with the management server 600, an input device 54 that detects an input operation of a user, a display device 55 that outputs an image, and a CPU (Central Processing Unit) 56 that controls the entire license management tool 500. ..
- the memory 51, the input / output interface 52, the communication interface 53, the input device 54, and the display device 55 are connected to the CPU 56 via the bus 59, and each communicates with the CPU 56.
- the memory 51 includes a volatile memory and a non-volatile memory.
- the memory 51 stores programs for realizing various functions of the license management tool 500. Specifically, the memory 51 stores the license management program 511. Further, the memory 51 is used as a work memory of the CPU 56.
- the license management program 511 is a program that causes the CPU 56 to execute the license key registration process and the license key transfer process.
- the input / output interface 52 includes, for example, a USB controller, converts data supplied from the CPU 56 into an electric signal, and outputs the converted signal to the PLC 100 via the communication cable 701. Further, the input / output interface 52 receives the electric signal output by the PLC 100 via the communication cable 701, restores the received electric signal to data, and outputs the received electric signal to the CPU 56.
- a USB controller converts data supplied from the CPU 56 into an electric signal, and outputs the converted signal to the PLC 100 via the communication cable 701. Further, the input / output interface 52 receives the electric signal output by the PLC 100 via the communication cable 701, restores the received electric signal to data, and outputs the received electric signal to the CPU 56.
- the communication interface 53 includes a network interface circuit and communicates with the license management server 600 via the network 702 under the control of the CPU 56.
- the network 702 is, for example, the Internet.
- the input device 54 includes a mouse, operation keys, and the like, receives an operation input from the user, and outputs a signal indicating the user's operation input to the CPU 56.
- the display device 55 includes a display and displays an image based on a signal supplied from the CPU 56 on the display.
- the CPU 56 executes various programs stored in the memory 51 to realize various functions of the license management tool 500. Specifically, the CPU 56 registers the license key of the application program in the PLCs 101 and 102 by executing the license management program 511. Further, the CPU 56 transfers the license key possessed by the PLC 101 to the PLC 102 by executing the license management program 511, for example.
- the license management server 600 includes a memory 61 for storing various programs and data, a communication interface 62 for communicating with the license management tool 500 via the network 702, and a CPU 63 for controlling the entire license management server 600.
- the memory 61 and the communication interface 62 are connected to the CPU 63 via the bus 69, and each communicate with the CPU 63.
- the memory 61 includes a volatile memory and a non-volatile memory.
- the memory 61 stores programs for realizing various functions of the license management server 600. Specifically, the memory 61 stores the license management program 611. Further, the memory 51 is used as a work memory of the CPU 56.
- the license management program 611 is a program that causes the CPU 63 to execute a process of issuing a license key and a process of managing information related to license registration.
- the communication interface 62 includes a network interface circuit and communicates with the license management server 600 via the network 702 under the control of the CPU 63.
- the CPU 63 executes various programs stored in the memory 61 to realize various functions of the license management server 600. Specifically, the CPU 63 issues a license key by executing the license management program 611.
- the PLC 100 has a program storage unit 110 that stores an application program, a license key storage unit 120 that stores a license key, an invalidation key storage unit 130 that stores an invalidation key, and a PLC 100 that stores an application program.
- a license confirmation unit 140 that determines whether or not the license key is valid before execution, a license transmission / reception unit 150 that exchanges a license key between the license management tool 500, and a program execution that executes an application program. Includes part 160.
- the program storage unit 110 stores the application program executed by the PLC 100.
- Application programs include programs sold as products. As shown in FIG. 3, it is assumed that the program storage unit 110 stores the application programs 1101 to 1103 purchased by the user.
- the PLC 100 needs to have each application key in order to execute the application programs 1101 to 1103.
- the application programs 1101 to 1103 may be collectively referred to as an application program 1100.
- the function of the program storage unit 110 is realized by the memory 11 shown in FIG.
- the license key storage unit 120 shown in FIG. 1 stores the license key corresponding to each of the application programs 1100 executed by the PLC 100. As shown in FIG. 3, it is assumed that the program storage unit 110 stores the application programs 1101 to 1103. In this case, as shown in FIG. 4, the license key storage unit 120 stores the license keys 1201 to 1203 corresponding to the application programs 1101 to 1103, respectively. Hereinafter, the license keys 1201 to 1203 may be collectively referred to as a license key 1200.
- the license key storage unit 120 is an example of the license key storage means of the present invention.
- the license key 1200 is supplied from the license management tool 500 shown in FIG.
- the license transmission / reception unit 150 which will be described later, stores the license key 1200 supplied from the license management tool 500 in the license key storage unit 120.
- the function of the license key storage unit 120 is realized by the memory 11 shown in FIG. It is desirable that the license key storage unit 120 is provided in an area of the memory 11 that cannot be referred to by the user.
- the license transmission / reception unit 150 is an example of the storage means of the present invention.
- the license key storage unit 120 stores the license key 1200 and the application ID that identifies the application program 1100.
- the license key 1200 includes a license code 1200a, a device ID 1200b, a transition counter 1200c, and an invalidation flag 1200d.
- the license code 1200a is an identification code assigned to each license of the application program 1100. In the embodiment, it is assumed that one PLC100 can execute the application program 1100 with one license.
- the device ID 1200b is an identifier for uniquely identifying the PLC100 in which the application program 1100 is installed. An identifier of PLC100 in which the license key 1200 is registered is set in the device ID 1200b.
- the PLC 100 determines whether or not the device ID 1200b of the license key 1200 matches the identifier of the own machine. When the PLC 100 determines that the device ID 1200b of the license key 1200 matches the identifier of its own machine, the PLC 100 executes the application program 1100. On the other hand, if the PLC 100 determines that the device ID 1200b of the license key 1200 does not match the identifier of the own machine, the PLC 100 does not execute the application program 1100. With such a configuration, it is possible to control the PLC100, which should not execute the application program 1100, so as not to execute the application program 1100.
- the license management server 600 When the license key 1200 is issued for the first time, the license management server 600 generates the license key 1200. Therefore, the license management server 600 is supplied with the identifier of the PLC 100 from the license management tool 500. The license management server 600 sets the identifier of the PLC 100 in the license key 1200 as the device ID 1200b. At the time of migration of the license key 1200, the license management tool 500 regenerates the license key 1200. In this case, the license management tool 500 sets the identifier of the destination PLC100 as the device ID 1200b in the license key 1200.
- the migration counter 1200c stores a value indicating the number of migrations, which is the number of times the license of the application program 1100 has been migrated.
- the value of the migration counter 1200c is an initial value, for example, "0" when the license key 1200 is first generated.
- the value of the transition counter 1200c is added by "1" at the timing when the license key 1200 is regenerated.
- the license management server 600 sets an initial value in the value of the migration counter 1200c when the license key 1200 is generated.
- the license management tool 500 adds the value of the migration counter 1200c of the license key 1200 by a predetermined number, for example, "1".
- the value of the transition counter 1200c is an initial value, for example, “0”.
- the PLC 101 cannot execute the application program 1101 due to some reason such as a malfunction of the PLC 101.
- the administrator of the PLC 100 installs the application program 1101 on the PLC 102 and uses the license management tool 500 to transfer the license key 1200 of the application program 1101 to the PLC 102.
- the value of the transition counter 1200c at this time is a value obtained by adding "1" to the initial value, that is, "1".
- the invalidation flag 1200d has a value indicating whether or not the license key 1200 is an invalidation key.
- the invalidation key is used to prevent unauthorized use of the license key 1200.
- the invalidation key is stored in the source PLC100 when the license key 1200 is transferred to another PLC100.
- the invalidation flag 1200d As a value indicating that the license key 1200 is a valid key, for example, "0" is set in the invalidation flag 1200d.
- the value of the invalidation flag 1200d is, for example, "1", indicating that the key is an invalidation key.
- the license management tool 500 copies the license key 1200 to be migrated, sets the invalidation flag 1200d of the copied key to "1", generates an invalidation key, and generates an invalidation key to generate the migration source. Save the invalidation key in the PLC100 of.
- the PLC100 does not accept the supplied license key 1200 when the license management tool 500 supplies an invalidation key that matches the part excluding the invalidation flag 1200d of the license key 1200.
- the invalidation key storage unit 130 shown in FIG. 1 stores the invalidation key.
- the license management tool 500 issues an invalidation key to the migration source PLC100 when the license key 1200 is migrated. Therefore, the invalidation key storage unit 130 stores the invalidation key only when the invalidation key is supplied from the license management tool 500.
- the function of the invalidation key storage unit 130 is realized by the memory 11 shown in FIG. It is desirable that the invalidation key storage unit 130 is provided in an area of the memory 11 that cannot be referred to by the user.
- the license management server 600 when the license key 1200 is issued for the first time, the license management server 600 generates the license key 1200 including the PLC101 identifier as the device ID 1200b of the license key 1200, and transmits the license key 1200 to the license management tool 500.
- the user or another person copies the license key 1200 for PLC101 stored in the license management tool 500 to a certain area in the memory 51.
- the license key 1200 is registered in the PLC 101
- the user or another person operates the license management tool 500 to transfer the license key 1200 to the PLC 102.
- the user or another person re-registers the copied license key 1200 for the PLC 101 in the PLC 101.
- the license key 1200 for the PLC 101 can be registered in the PLC 101, and the application program 1100 can be executed by the two PLC 100s by purchasing only one license.
- the user or another person operates the license management tool 500 to obtain the license key 1200 acquired from the PLC 101 during the process of migrating the license key 1200 registered in the PLC 101 from the PLC 101 to the PLC 102.
- the copy is made to a certain area in the memory 51.
- the license key 1200 regenerated by the license management tool 500 is registered in the migration destination PLC 102, and then the user or another person registers the copied license key 1200 for the PLC 101 in the PLC 101 again.
- the license key 1200 for the PLC 101 can be registered in the PLC 101, and the application program 1100 can be executed by the two PLC 100s by purchasing only one license.
- the license management tool 500 when migrating the license key 1200, the license management tool 500 generates an invalidation key from the license key 1200 held by the migration source PLC100 and transfers the invalidation key. Register with the original PLC101.
- the license confirmation unit 140 shown in FIG. 1 confirms whether or not the PLC 100 has the license key 1200 necessary for executing the application program 1100.
- the license confirmation unit 140 determines whether or not the license key 1200 corresponding to the application program 1100 exists in the license key storage unit 120 shown in FIG. When the license key 1200 exists in the license key storage unit 120, the license confirmation unit 140 determines whether or not the value of the device ID 1200b of the license key 1200 matches the identifier of the PLC 100 stored in the memory 11. Determine if the license key 1200 is valid. The license confirmation unit 140 notifies the program execution unit 160 whether or not the license key 1200 is valid. The function of the license confirmation unit 140 is realized by the MPU 13 shown in FIG.
- the license transmission / reception unit 150 shown in FIG. 1 receives the license key 1200 from the license management tool 500, and determines whether the license key 1200 can be registered. When the license transmission / reception unit 150 determines that the supplied license key 1200 can be registered, the license key 1200 stores the license key 1200 in the license key storage unit 120.
- the license transmission / reception unit 150 determines whether or not the invalidation key in which the portion of the received license key 1200 excluding the invalidation flag 1200d matches is stored in the invalidation key storage unit 130.
- the license transmission / reception unit 150 stores the license key 1200 in the license key storage unit 120 when the parts other than the invalidation flag 1200d do not have the matching invalidation key.
- the license transmission / reception unit 150 does not store the license key 1200 in the license key storage unit 120 when the parts other than the invalidation flag 1200d have matching invalidation keys.
- the license transmission / reception unit 150 transmits the identifier of the PLC 100 to the license management tool 500.
- the license management server 600 sets the identifier of the PLC 100 in the license key 1200 as the device ID 1200b.
- the license management tool 500 sets the identifier of the PLC 100 in the license key 1200 as the device ID 1200b.
- the license transmission / reception unit 150 is an example of the identifier transmission means of the present invention.
- the license transmission / reception unit 150 displays a list of the values of the license key 1200 stored in the license key storage unit 120 in the license management tool 500. Send to.
- the license transmission / reception unit 150 takes out the designated license key 1200 from the license key storage unit 120 and transfers the license key 1200 to the license management tool 500. Send. Therefore, the extracted license key 1200 is not stored in the license key storage unit 120.
- the license transmission / reception unit 150 stores the invalidation key in the invalidation key storage unit 130.
- the function of the license transmission / reception unit 150 is realized by the MPU 13 shown in FIG. 2 executing the license management program 111.
- the program execution unit 160 shown in FIG. 1 executes the application program 1100. Prior to executing the application program 1100, the program execution unit 160 inquires the license confirmation unit 140 whether or not the license key 1200 corresponding to the application program 1100 is valid. When the program execution unit 160 determines that the license key 1200 is valid based on the response from the license confirmation unit 140, the program execution unit 160 executes the application program 1100 stored in the program storage unit 110. The function of the program execution unit 160 is realized by the MPU 13 shown in FIG.
- the license management tool 500 functionally migrates the purchase data storage unit 510 that stores data related to the purchased application program 1100, the license registration unit 520 that registers a new license key 1200 in the PLC 100, and the license key 1200. Includes the license transfer unit 530.
- the purchase data storage unit 510 stores the application ID and the application name that specify the purchased application program 1100 in order to specify the application program 1100 that the user has purchased.
- the function of the purchase data storage unit 510 is realized by the memory 51 shown in FIG.
- the license registration unit 520 shown in FIG. 1 receives an instruction for issuing a new license key 1200 from the user, it sends an issuance request requesting the issuance of the license key 1200 to the license management server 600.
- the license registration unit 520 transmits the license key 1200 to the PLC 100.
- the license registration unit 520 displays a list of application names of the purchased application program 1100 stored in the purchase data storage unit 510 on the display device 55 shown in FIG.
- the license registration unit 520 requests the identifier from the connected PLC 100 and acquires the identifier from the PLC 100.
- the license registration unit 520 transmits a license issuance request to the license management server 600.
- the license issuance request includes a user ID that identifies the user of the PLC 100, an identifier of the PLC 100 received from the PLC 100, and an application ID that identifies the application program 1100 specified by the user.
- the license registration unit 520 receives the license key 1200 from the license management server 600, the license registration unit 520 transmits the received license key 1200 to the PLC 100.
- the license registration unit 520 when the license registration unit 520 receives a notification from the license management server 600 that the license key 1200 cannot be issued, it notifies the user that the registration of the license key 1200 has failed. For example, the license registration unit 520 displays a message to the effect that the registration of the license key 1200 has failed on the display device 55 shown in FIG.
- the function of the license registration unit 520 is realized by the CPU 56 shown in FIG. 2 executing the license management program 511.
- the license transfer unit 530 shown in FIG. 1 receives an instruction to transfer the license key 1200 from the user, the license transfer unit 530 acquires the license key 1200 from the connected migration source PLC100.
- the license transfer unit 530 acquires an identifier from the migration destination PLC100, regenerates a new license key 1200 including the identifier, and gives a new license key 1200 to the migration destination PLC100.
- the function of the license transfer unit 530 is realized by the CPU 56 shown in FIG. 2 executing the license management program 511.
- the license transfer unit 530 includes a key acquisition unit 531, an identifier acquisition unit 532, a regeneration unit 533, and an invalidation key generation unit 534.
- the key acquisition unit 531 When the user connects the license management tool 500 and the migration source PLC100 and issues an instruction to migrate the license key 1200, the key acquisition unit 531 first obtains information about the license key 1200 held by the migration source PLC100. Request to the migration source PLC100. The key acquisition unit 531 presents to the user information about the license key 1200 received from the migration source PLC. The key acquisition unit 531 requests the migration source PLC100 to take out the license key 1200 specified by the user. When the key acquisition unit 531 acquires the license key 1200 from the migration source PLC100, the key acquisition unit 531 supplies the license key 1200 to the regeneration unit 533.
- the key acquisition unit 531 is an example of the key acquisition means of the present invention.
- the identifier acquisition unit 532 When the user connects the license management tool 500 and the migration destination PLC100, the identifier acquisition unit 532 requests the identifier from the migration destination PLC100. When the identifier acquisition unit 532 acquires the identifier from the migration destination PLC100, the identifier acquisition unit 532 supplies the identifier to the regeneration unit 533.
- the identifier acquisition unit 532 is an example of the identifier acquisition means of the present invention.
- the regeneration unit 533 instructs the invalidation key generation unit 534 to generate the invalidation key before regenerating the license key 1200.
- the regeneration unit 533 regenerates the license key 1200 after the invalidation key generation unit 534 generates the invalidation key.
- the regeneration unit 533 is an example of the regeneration means of the present invention.
- the regeneration unit 533 deletes the identifier of the migration source PLC100 set as the device ID 1200b from the license key 1200 acquired by the key acquisition unit 531 from the migration source PLC100.
- the regeneration unit 533 sets the identifier of the destination PLC100 as the device ID 1200b of the license key 1200. Further, the regeneration unit 533 increments the value of the migration counter 1200c of the license key 1200 by one. In this way, the regeneration unit 533 regenerates the license key 1200.
- the regeneration unit 533 transmits the regenerated license key 1200 to the migration destination PLC100.
- the regeneration unit 533 transmits the transferred license key information to the license management server 600.
- the transferred license key information includes a user ID that identifies the user of the PLC 100, a license key 1200 transmitted to the migration destination PLC 100, and an identifier of the migration destination PLC 100.
- the invalidation key generation unit 534 generates an invalidation key when instructed by the regeneration unit 533.
- the invalidation key generation unit 534 duplicates the migration source license key 1200, sets the invalidation flag 1200d of the duplicated key to "1", and generates an invalidation key.
- the invalidation key generated by the invalidation key generation unit 534 differs only in the value of the invalidation flag 1200d from the license key 1200 held by the migration source PLC100.
- the invalidation key generation unit 534 transmits the invalidation key to the migration source PLC100.
- the invalidation key generation unit 534 is an example of the invalidation key generation means of the present invention.
- the transfer source PLC 101 is an example of the first device of the present invention
- the transfer destination PLC 102 is an example of the second device of the present invention.
- the identifier of the migration source PLC101 is an example of the first identifier of the present invention
- the identifier of the migration destination PLC102 is an example of the second identifier of the present invention.
- the license management server 600 includes an application data storage unit 610 that stores data related to application programs, a license data storage unit 620 that stores data related to licenses, and a license management unit 630 that issues a license key 1200. Including.
- the application data storage unit 610 stores the application compatibility table 610a as shown in FIG.
- the application conformance table 610a stores data indicating whether or not each application program 1100 can be executed for each model of the PLC 100.
- the application compatibility table 610a stores a value indicating whether each application program 1100 can be executed (OK) or cannot be executed (NG) according to the model of the PLC100.
- the PLC100 of "TYPE2" can execute "application 1001" and "application 1004", and cannot execute other application programs 1100.
- an administrator who manages the license management server 600 at a manufacturer that develops and sells an application program stores the application conformity table 610a in the application data storage unit 610.
- the function of the application data storage unit 610 is realized by the memory 61 shown in FIG.
- the license data storage unit 620 shown in FIG. 1 stores the purchase license table 620a as shown in FIG. 7.
- the purchase license table 620a stores data indicating the number of licenses purchased and the number of licenses used for each user.
- the purchase license table 620a shows a user ID that is an identifier that identifies the user, an application ID that identifies the application program 1100, a purchase license that indicates the number of licenses purchased by the user, and a license registered in the PLC 100. Includes usage licenses indicating numbers.
- a user whose user ID is "2009002” has purchased three licenses of "application 1001", but has not used the application program 1100 for all the purchased licenses. Further, this user has purchased one license of "application 1002” and four licenses of "application 1003", and is using the application program 1100 for all the purchased licenses.
- the license data storage unit 620 shown in FIG. 1 stores the license registration table 620b as shown in FIG.
- the license registration table 620b stores data related to the license key 1200 issued to the PLC 100.
- the license registration table 620b stores data for identifying the license key 1200 issued to the PLC 100 for each combination of the user and the application program 1100.
- the license registration table 620b includes a user ID that is an identifier that identifies the user, an application ID that identifies the application program 1100, an issued license key, and an identifier of the PLC100.
- an administrator who manages the license management server 600 at a manufacturer that develops and sells an application program stores the purchase license table 620a and the license registration table 620b in the license data storage unit 620.
- the function of the license data storage unit 620 is realized by the memory 61 shown in FIG.
- the license management unit 630 shown in FIG. 1 When the license management unit 630 shown in FIG. 1 receives a license issuance request from the license management tool 500, it issues a license key 1200.
- the license management unit 630 determines whether or not the license can be issued. Specifically, the license management unit 630 refers to the application conformance table 610a, and the model of the PLC100 specified from the identifier of the PLC100 included in the received license issuance request executes the designated application program 1100. Determine if it can be done. The information indicating the model of the PLC100 is included in the serial code which is the identifier of the PLC100, and the license management unit 630 can identify the model of the PLC100 from this information.
- the license management unit 630 determines whether or not the user having the user ID included in the license issuance request has purchased the license of the specified application program 1100 by referring to the purchase license table 620a. .. If the user has purchased a license, the license management unit 630 determines whether or not there is an unused license.
- the license management unit 630 determines that the license key 1200 can be issued when the user has purchased the license and has an unused license. Therefore, the license management unit 630 generates the license key 1200 as shown in FIG.
- the license management unit 630 generates a random number using the user ID as a seed, and sets a value obtained by adding the application ID to the generated random number in the license code 1200a.
- the license management unit 630 sets the device ID 1200b with the PLC100 identifier included in the license issuance request.
- the license management unit 630 sets an initial value, for example, “0” in the transition counter 1200c.
- the license management unit 630 sets the invalidation flag 1200d to "0" as a value indicating that the license key 1200 is a valid key.
- the license management unit 630 transmits the license key 1200 generated in this manner to the license management tool 500.
- the license management unit 630 registers the user ID, application ID, and PLC100 identifier included in the license issuance request and the issued license key 1200 in the license registration table 620b.
- the license management unit 630 cannot issue the license key 1200 if the model of the PLC100 cannot execute the specified application program 1100, the user has not purchased the license, or there is no unused license. Determine that it is possible. In this case, the license management unit 630 notifies the license management tool 500 that the license key 1200 cannot be issued.
- the function of the license management unit 630 is realized by the CPU 63 shown in FIG. 2 executing the license management program 611.
- the license management unit 630 when the license management unit 630 receives the user ID that identifies the user of the PLC 100, the license key 1200 registered in the migration destination PLC 100, and the identifier of the migration destination PLC 100 from the license management tool 500, the license management unit 630 registers the license. Update table 620b. Specifically, the license management unit 630 updates the data specified by the received license key 1200 and the identifier among the data in the license registration table 620b with the received license key 1200 and the identifier of the PLC 100. After that, the license management unit 630 sends an update completion notification indicating that the update of the license registration table 620b is completed to the license management tool 500.
- the CPU 56 functions as a license registration unit 520 by executing the license management program 511.
- the license registration unit 520 requests an identifier from the PLC 101 (step S11).
- the license transmission / reception unit 150 of the PLC 101 transmits the identifier to the license management tool 500.
- the license registration unit 520 displays the application program selection screen as shown in FIG. 11A.
- the license registration unit 520 displays a screen on which the user can select any of the purchased application programs 1100 stored in the purchase data storage unit 510 shown in FIG.
- the user selects a desired application program and presses the "register" button.
- the license registration unit 520 accepts the selection of the application program (step S13) and transmits the license issuance request to the license management server 600 (step S14).
- the license issuance request includes a user ID of the user of the PLC 100, an identifier of the PLC 100, and an application ID that identifies the application program 1100.
- the license registration unit 520 receives the license key 1200 from the license management server 600, it determines that the license issuance was successful (step S15; Yes).
- the license registration unit 520 transmits the license key 1200 to the PLC 101 (step S16), and displays a registration completion screen as shown in FIG. 11B.
- the license registration unit 520 when the license registration unit 520 receives a notification from the license management server 600 that the license key 1200 cannot be issued, it determines that the license issuance has failed (step S15; No), and for example, as shown in FIG. 11C. A screen is displayed to notify that the license issuance has failed (step S17).
- the processing on the license management server 600 side regarding the issuance of the license key 1200 is as follows.
- the CPU 63 shown in FIG. 2 functions as the license management unit 630 shown in FIG. 1 by executing the license management program 611.
- step S21 when the license management unit 630 receives the license issuance request from the license management tool 500 (step S21; Yes), the PLC 100 refers to the application conformance table 610a, and the PLC 100 selects the designated application program 1100. It is determined whether or not it can be executed (step S22). When the license management unit 630 determines that the PLC 100 can execute the designated application program 1100 (step S22; Yes), the license management unit 630 executes the process of step S23.
- the license management unit 630 determines that the PLC 100 cannot execute the specified application program 1100 (step S22; No), it notifies the license management tool 500 that the license issuance has failed (step S27). ..
- step S23 the license management unit 630 refers to the purchase license table 620a and determines whether or not the user of the PLC 100 has a usable license for the application program 1100 (step S23).
- the license management unit 630 determines that the user of the PLC 100 has a usable license for the application program 1100 (step S23; Yes)
- the license management unit 630 generates a license key 1200 (step S24).
- the license management unit 630 transmits the generated license key 1200 to the license management tool 500 (step S25). After that, the license management unit 630 registers the information of the license key 1200 in the license registration table 620b shown in FIG. 8 (step S26).
- the license management unit 630 issues a license when the user of the PLC100 has not purchased the application program 1100, or has purchased the application program 1100 but is using all the licenses (step S23; No). Notifies the license management tool 500 that the failure has occurred (step S27).
- the above is the processing on the license management server 600 side at the time of initial registration of the license.
- the user operates the input device 54 of the license management tool 500 to open the menu screen.
- the CPU 56 displays a menu screen as shown in FIG. 9 on the display device 55.
- the CPU 56 functions as the license transfer unit 530 shown in FIG. 1 by executing the license management program 511.
- the license transfer unit 530 requests the transfer source PLC101 for information on license registration (step S31).
- the license transmission / reception unit 150 of the PLC 101 transmits a list of values of the license key 1200 stored in the license key storage unit 120 and an identifier of the PLC 101 to the license management tool 500 as license registration information.
- the license transfer unit 530 receives the information about the license registration (step S32)
- the license transfer unit 530 displays a selection screen of the application program to be transferred as shown in FIG. 15A based on the received data.
- the license transfer unit 530 requests the transfer source PLC101 to take out the license key 1200 of the selected application program 1100 (step S34). In response to this, it is assumed that the license transmission / reception unit 150 of the PLC 101 takes out the designated license key 1200 and sends the license key 1200 to the license management tool 500.
- the license transfer unit 530 When the license transfer unit 530 receives the license key 1200 from the transfer source PLC101 (step S35; Yes), the license transfer unit 530 copies the received license key 1200, and sets "1" in the invalidation flag 1200d of the copied license key 1200. To generate an invalidation key. (Step S36).
- the license transfer unit 530 transmits the invalidation key to the transfer source PLC101 (step S37). In response to this, the license transmission / reception unit 150 of the PLC 101 stores the received invalidation key in the invalidation key storage unit 130. After that, the license transfer unit 530 executes the process of step S38.
- the license transfer unit 530 instructs the user to switch the connection (step S38).
- the license transfer unit 530 displays a screen as shown in FIG. 15B and instructs the transfer destination to connect to the PLC 102. It is assumed that the user removes the communication cable 701 from the migration source PLC 101, disconnects the license management tool 500 from the PLC 101, and then connects the communication cable 701 to the migration destination PLC 102. Therefore, the license management tool 500 can communicate with the migration destination PLC102.
- the license transfer unit 530 requests an identifier from the transfer destination PLC 102 (step S39).
- the license transmission / reception unit 150 of the PLC 102 transmits the identifier to the license management tool 500.
- the license transfer unit 530 regenerates a new license key 1200 from the license key 1200 received from the migration source PLC101 (step S41). Specifically, the license transmission / reception unit 150 deletes the identifier of the migration source PLC101 set as the device ID 1200b of the license key 1200 as shown in FIG. 5, and newly obtains the identifier obtained from the migration destination PLC 102. Set the license key 1200 as the device ID 1200b. Further, the license transfer unit 530 increases the value of the transfer counter 1200c of the license key 1200 by one.
- the license transfer unit 530 transmits the regenerated license key 1200 to the transfer destination PLC 102 (step S42).
- the license transmission / reception unit 150 of the PLC 102 stores the received license key 1200 in the license key storage unit 120.
- the license transfer unit 530 transmits the license key information to the license management server 600 (step S51).
- the license key information includes a user ID that identifies the user of the PLC 100, a license key 1200 transmitted to the migration destination PLC 102, and an identifier of the PLC 102.
- the license transfer unit 530 receives the update completion report from the license management server 600 (step S52)
- the license transfer unit 530 displays the transfer completion screen as shown in FIG. 15C.
- the license management unit 630 of the license management server 600 when the license management unit 630 of the license management server 600 receives the license key information from the license management tool 500 (step S61), it updates the data in the license registration table 620b (step S62). Specifically, the license management unit 630 updates the data specified by the received user ID among the data in the license registration table 620b with the received license key 1200 and the identifier. After that, the license management unit 630 transmits an update completion notification indicating that the update of the license registration table 620b is completed to the license management tool 500 (step S63).
- the license management tool 500 transfers the license key 1200 between two or more PLCs 100 that are not connected to the external network.
- the license management tool 500 deletes the PLC101 identifier from the license key 1200 acquired from the migration source PLC101 and sets the migration destination PLC102 identifier in the license key 1200 to regenerate the license key 1200 and create a new one.
- the license key 1200 is supplied to the migration destination PLC102.
- the license management tool 500 can transfer licenses between stand-alone devices that cannot communicate with the license management server.
- the license transmission / reception unit 150 when the license transmission / reception unit 150 stores the invalidation key in the invalidation key storage unit 130 in which the parts other than the invalidation flag 1200d of the received license key 1200 match, the license key 1200 is stored. I explained an example of not accepting. However, it is not limited to this.
- the license management tool 500 may not send the license key 1200 to the PLC 100 when the PLC 100 has the invalidation key.
- the regenerating unit 533 of the license management tool 500 may request the PLC 100 for the invalidation key possessed by the PLC 100 before transmitting the regenerated license key 1200 to the migration destination PLC100. ..
- the PLC 100 shall transmit a list of invalidation key values stored in the invalidation key storage unit 130 to the license management tool 500. If the invalidation key received from the PLC 100 includes an invalidation key that matches the part other than the invalidation flag 1200d of the regenerated license key 1200, the regeneration unit 553 regenerates the license key 1200. May not be transmitted to the migration destination PLC100.
- the license management tool 500 has described an example in which the invalidation key is transmitted to the migration source PLC 100 before supplying the new license key 1200 to the migration destination PLC 100, but the present invention is not limited to this.
- the license management tool 500 acquires the license key 1200 from the migration source PLC100 and copies the license key 1200, or generates an invalidation key from the license key 1200.
- the license management tool 500 generates a new license key 1200 after the connection of the PLC 100 is switched, and sends the new license key 1200 to the migration destination PLC 100.
- the license management tool 500 transmits the invalidation key to the migration source PLC100.
- the invalidation key is provided to the migration source PLC100 after the registration of the license key 1200 to the migration destination PLC100 is completed, if the registration of the new license key 1200 to the migration destination PLC100 fails. It is also possible to return the license key 1200 to the migration source PLC100 again.
- the identifier of the migration source PLC101 is included in the license key 1200 as the first identifier, and when a new license key 1200 is generated, the identifier of the migration source PLC101 is taken out from the license key 1200.
- the identifier of the destination PLC 102 is added to the license key 1200 as the second identifier.
- an identifier other than the identifier of the migration source PLC100 and the identifier of the migration destination PLC100 may be used as the first identifier, or the hash value generated from the identifier of PLC102 may be used as the second identifier.
- the license management tool 500 executes the license information update process shown in FIG. 16A following the transfer process of the license key 1200, but the present invention is not limited to this.
- the license management tool 500 may execute the license information update process separately from the process of migrating the license key 1200.
- the license management tool 500 may not always be connected to the network 702. In such a case, the license management tool 500 may execute the license information update process shown in FIG. 16A when connected to the network 702.
- the license management tool 500 communicates with the PLC 100 via the communication cable 701
- the license management tool 500 and the PLC 100 may perform wireless communication.
- a computer-readable recording medium including a magnetic disk, an optical disk, a magneto-optical disk, a flash memory, a semiconductor memory, and a magnetic tape can be used.
- License management system 11,51,61 memory, 12,52 input / output interface, 13 MPU, 19,59,69 bus, 53,62 communication interface, 54 input device, 55 display device, 56,63 CPU, 101, 102 (100) Programmable logic controller (PLC), 110 Program storage unit, 111,511 License management program, 120 License key storage unit, 130 Invalidation key storage unit, 140 License confirmation unit, 150 License transmission / reception unit, 160 Program execution unit , 500 License management tool, 510 Purchase data storage unit, 511 License management program, 520 License registration unit, 530 License transfer unit, 513 Key acquisition unit, 532 Identifier acquisition unit, 533 Regeneration unit, 534 Invalidation key generation unit, 600 License management server, 610 application data storage unit, 610a application conformance table, 611 license management program, 620 license data storage unit, 620a purchase license table, 620b license registration table, 630 license management unit, 701 communication cable, 702 network, 1101 ⁇ 1103 (1100) application program, 1201-1203 (1200) license key, 1200
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Automation & Control Theory (AREA)
- Programmable Controllers (AREA)
- Storage Device Security (AREA)
Abstract
Description
以下、本発明の実施の形態に係るライセンス管理システムについて、図面を参照しつつ詳細に説明する。
続いて、ライセンスキー1200の初回の登録処理を説明する。まず、ユーザは、通信ケーブル701により、ライセンス管理ツール500とPLC101とを接続する。ユーザは、ライセンス管理ツール500の入力装置54を操作してメニュー画面を開く。ユーザの操作に応答して、CPU56は、表示装置55に図9に示すようなメニュー画面を表示する。ここで、ユーザが「ライセンスキーの登録」を選択したとする。
続いて、ライセンスキー1200の移行処理を説明する。以下の説明においては、PLC101が有するライセンスキー1200をPLC102に移行する例を説明する。ユーザは、通信ケーブル701により、ライセンス管理ツール500と移行元のPLC101とを接続する。なお、ライセンス管理ツール500は、ネットワーク702を介して、ライセンス管理サーバ600に接続されている必要はない。
Claims (10)
- アプリケーションプログラムの使用が許諾されていることを示すライセンスキーを、外部ネットワークに接続されていない2以上の装置の間で移行するライセンス移行ツールであって、
前記ライセンスキーは、前記ライセンスキーが登録されている装置を識別する識別子を含み、
ライセンスの移行元の前記装置である第1装置から、前記ライセンスキーを取得するキー取得手段と、
ライセンスの移行先の前記装置である第2装置から、前記第2装置を識別する第2識別子を取得する識別子取得手段と、
前記第1装置から取得した前記ライセンスキーから、前記第1装置を識別する第1識別子を削除して、前記第2装置の前記第2識別子を前記識別子として追加して、新しい前記ライセンスキーを生成し、前記第2装置に新しい前記ライセンスキーを供給する再生成手段と、
を備えるライセンス移行ツール。 - 前記ライセンスキーは、前記アプリケーションプログラムの1ライセンス毎に割り振られた識別コードと、前記ライセンスキーが登録されている前記装置を識別する前記識別子と、前記ライセンスキーの移行回数を示す情報と、を含む、
請求項1に記載のライセンス移行ツール。 - 前記ライセンスキーを有する前記第2装置は、前記ライセンスキーに含まれる前記識別子が、前記第2装置を識別する前記第2識別子と一致する場合に、前記アプリケーションプログラムを実行する、
請求項1または2に記載のライセンス移行ツール。 - 前記再生成手段が、新しい前記ライセンスキーを前記第2装置に供給した後に、前記第1装置に前記ライセンスキーを再度登録することができないことを示す無効化キーを生成し、前記第1装置に前記無効化キーを供給する無効化キー生成手段、
を備える請求項1または3に記載のライセンス移行ツール。 - 前記無効化キー生成手段は、前記第1装置から取得した前記ライセンスキーを複製し、複製したキーに、そのキーが無効であることを示す値を設定して、前記無効化キーを生成する、
請求項4に記載のライセンス移行ツール。 - 前記第2装置は、前記無効化キーを有している場合、前記無効化キーと対応する前記ライセンスキーを受け付けない、
請求項4または5に記載のライセンス移行ツール。 - 前記再生成手段は、前記第2装置が新しい前記ライセンスキーに対応する前記無効化キーを有している場合、新しい前記ライセンスキーを前記第2装置に供給しない、
請求項4または5に記載のライセンス移行ツール。 - 前記装置は、プログラマブルロジックコントローラである、
請求項1から7のいずれか1項に記載のライセンス移行ツール。 - アプリケーションプログラムの使用が許諾されていることを示すライセンスキーを、外部ネットワークに接続されていない2以上の装置の間で移行するコンピュータに、
ライセンスの移行元の前記装置である第1装置から、前記ライセンスキーを取得させ、
ライセンスの移行先の前記装置である第2装置から、前記第2装置を識別する第2識別子を取得させ、
前記第1装置から取得した前記ライセンスキーから、前記第1装置を識別する第1識別子を削除して、前記第2装置の前記第2識別子を追加して、新しい前記ライセンスキーを生成させ、
前記第2装置に新しい前記ライセンスキーを供給させる、
プログラム。 - アプリケーションプログラムの使用が許諾されていることを示すライセンスキーを移行ツールが第1装置から第2装置へ移行するライセンス移行システムであって、
前記ライセンスキーは、前記ライセンスキーが登録されている装置を識別する識別子を含み、
前記移行ツールは、
ライセンスの移行元の前記第1装置から、前記ライセンスキーを取得するキー取得手段と、
ライセンスの移行先の前記第2装置から、前記第2装置を識別する第2識別子を取得する識別子取得手段と、
前記第1装置から取得した前記ライセンスキーから、前記第1装置を識別する第1識別子を削除して、前記第2装置の前記第2識別子を前記識別子として追加して、新しい前記ライセンスキーを生成し、前記第2装置に新しい前記ライセンスキーを供給する再生成手段と、
を備え、
前記第1装置は、
前記ライセンスキーを記憶するライセンスキー記憶手段と、
前記移行ツールから前記ライセンスキーを要求されると、前記移行ツールに前記ライセンスキー記憶手段が記憶する前記ライセンスキーを送信する送信手段と、
を備え、
前記第2装置は、
前記移行ツールから前記識別子を要求されると、前記移行ツールに前記識別子を送信する識別子送信手段と、
前記移行ツールから供給された前記ライセンスキーを前記第2装置が有する前記ライセンスキー記憶手段に格納する格納手段と、
を備える、
ライセンス移行システム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019568127A JP6701463B1 (ja) | 2019-03-27 | 2019-03-27 | ライセンス移行ツール、プログラム、及びライセンス移行システム |
PCT/JP2019/013379 WO2020194604A1 (ja) | 2019-03-27 | 2019-03-27 | ライセンス移行ツール、プログラム、及びライセンス移行システム |
KR1020217026824A KR102314391B1 (ko) | 2019-03-27 | 2019-03-27 | 라이센스 이행 툴, 기록 매체, 및 라이센스 이행 시스템 |
CN201980094382.XA CN113614716B (zh) | 2019-03-27 | 2019-03-27 | 许可转移工具、记录有程序的计算机可读取记录介质及许可转移系统 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2019/013379 WO2020194604A1 (ja) | 2019-03-27 | 2019-03-27 | ライセンス移行ツール、プログラム、及びライセンス移行システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020194604A1 true WO2020194604A1 (ja) | 2020-10-01 |
Family
ID=70776090
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2019/013379 WO2020194604A1 (ja) | 2019-03-27 | 2019-03-27 | ライセンス移行ツール、プログラム、及びライセンス移行システム |
Country Status (4)
Country | Link |
---|---|
JP (1) | JP6701463B1 (ja) |
KR (1) | KR102314391B1 (ja) |
CN (1) | CN113614716B (ja) |
WO (1) | WO2020194604A1 (ja) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0651975A (ja) * | 1992-07-30 | 1994-02-25 | Fuji Xerox Co Ltd | ソフトウェア管理システム |
JP2005327196A (ja) * | 2004-05-17 | 2005-11-24 | Canon Inc | ライセンス管理装置、その制御方法、プログラムおよび記憶媒体 |
JP2009169782A (ja) * | 2008-01-18 | 2009-07-30 | Hitachi Ltd | 受信装置および配信装置の再生ライセンス管理方式 |
JP2010191691A (ja) * | 2009-02-18 | 2010-09-02 | Konica Minolta Business Technologies Inc | ライセンス管理システム、ライセンス管理コンピュータ、ライセンス管理方法およびライセンス管理プログラム |
JP2015026159A (ja) * | 2013-07-25 | 2015-02-05 | 株式会社バンダイナムコゲームス | サーバシステムおよびサーバシステムによる処理方法 |
JP2018026087A (ja) * | 2016-08-05 | 2018-02-15 | 株式会社リコー | 情報処理システム、アプリケーション導入方法及び情報処理装置 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004302817A (ja) | 2003-03-31 | 2004-10-28 | Matsushita Electric Ind Co Ltd | ライセンス管理システム |
JP4958671B2 (ja) * | 2007-07-24 | 2012-06-20 | キヤノン株式会社 | ライセンス管理装置、ライセンス管理方法、及びコンピュータプログラム |
JP5136161B2 (ja) | 2008-03-31 | 2013-02-06 | 富士通株式会社 | ソフトウェア・ライセンス管理システム、ソフトウェアをインストール可能な端末装置、ライセンス管理装置、およびプログラム |
JP5413078B2 (ja) * | 2009-09-14 | 2014-02-12 | 株式会社リコー | 機器管理システム、機器管理装置、仲介装置、機器管理方法、及び機器管理プログラム |
CN103503365A (zh) * | 2011-04-25 | 2014-01-08 | 松下电器产业株式会社 | 记录介质装置及控制器 |
US9292842B2 (en) * | 2011-10-28 | 2016-03-22 | Anil H. Pereira | Systems and methods for managing software licensing agreements |
US9838460B2 (en) | 2012-05-29 | 2017-12-05 | Google Llc | Tool for sharing applications across client devices |
JP6103169B1 (ja) * | 2015-11-05 | 2017-03-29 | 三菱電機株式会社 | セキュリティ装置、及びセキュリティ方法 |
EP3418833B1 (de) * | 2017-06-20 | 2021-04-07 | Siemens Aktiengesellschaft | Verfahren und anordnung zum zugriff eines ersten computers auf eine virtuelle maschine eines zweiten computers |
-
2019
- 2019-03-27 KR KR1020217026824A patent/KR102314391B1/ko active IP Right Grant
- 2019-03-27 WO PCT/JP2019/013379 patent/WO2020194604A1/ja active Application Filing
- 2019-03-27 CN CN201980094382.XA patent/CN113614716B/zh active Active
- 2019-03-27 JP JP2019568127A patent/JP6701463B1/ja active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0651975A (ja) * | 1992-07-30 | 1994-02-25 | Fuji Xerox Co Ltd | ソフトウェア管理システム |
JP2005327196A (ja) * | 2004-05-17 | 2005-11-24 | Canon Inc | ライセンス管理装置、その制御方法、プログラムおよび記憶媒体 |
JP2009169782A (ja) * | 2008-01-18 | 2009-07-30 | Hitachi Ltd | 受信装置および配信装置の再生ライセンス管理方式 |
JP2010191691A (ja) * | 2009-02-18 | 2010-09-02 | Konica Minolta Business Technologies Inc | ライセンス管理システム、ライセンス管理コンピュータ、ライセンス管理方法およびライセンス管理プログラム |
JP2015026159A (ja) * | 2013-07-25 | 2015-02-05 | 株式会社バンダイナムコゲームス | サーバシステムおよびサーバシステムによる処理方法 |
JP2018026087A (ja) * | 2016-08-05 | 2018-02-15 | 株式会社リコー | 情報処理システム、アプリケーション導入方法及び情報処理装置 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2020194604A1 (ja) | 2021-04-08 |
KR20210109659A (ko) | 2021-09-06 |
CN113614716B (zh) | 2022-09-13 |
CN113614716A (zh) | 2021-11-05 |
KR102314391B1 (ko) | 2021-10-19 |
JP6701463B1 (ja) | 2020-05-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6680022B2 (ja) | 情報処理装置、情報処理システム、情報処理方法及びプログラム | |
JP4827467B2 (ja) | ライセンス転送システム及びライセンス情報発行サーバ | |
US20170186117A1 (en) | License management apparatus, license management method, and license authentication program | |
KR102169947B1 (ko) | 에이전트 디바이스에 대한 신뢰된 신원을 확립하는 방법 | |
US20080027742A1 (en) | Information processing method, information processing apparatus, computer program and storage medium | |
WO2014199464A1 (ja) | 開発環境システム、開発環境装置、開発環境提供方法及びプログラム | |
JP4260759B2 (ja) | 機器制御サービス提供プログラム、機器制御サービス提供システムおよび機器制御サービス提供方法 | |
JP5177804B2 (ja) | フィールド通信システムおよびフィールド通信方法 | |
WO2013011902A1 (ja) | ライセンス管理装置、ライセンス管理システム、ライセンス管理方法、及びプログラム | |
CN107122630A (zh) | 设备授权管理方法和装置 | |
WO2015004706A1 (ja) | ストレージ装置およびストレージ装置の制御方法 | |
WO2020194604A1 (ja) | ライセンス移行ツール、プログラム、及びライセンス移行システム | |
WO2012151973A1 (zh) | 许可管理方法及装置 | |
JP5991740B2 (ja) | ライセンス管理装置、ライセンス管理方法、およびプログラム | |
CN101246533A (zh) | 用于管理数字内容的方法和装置 | |
JP2009098977A (ja) | 周辺機器接続システム | |
WO2015136964A1 (ja) | ライセンス情報管理装置、ライセンス情報管理方法、および、プログラム | |
JP2005284506A (ja) | ダウンロードシステム及びダウンロードシステムを構成する機器、管理局、リムーバブルメディア | |
JP2016173715A (ja) | ライセンス管理システム、プログラム及びライセンス管理方法 | |
WO2014045490A1 (ja) | ライセンス制御システム、ライセンス制御方法、ライセンス適用装置、及びプログラムが格納された非一時的なコンピュータ可読媒体 | |
JP5130126B2 (ja) | ライセンス数管理装置、ライセンス数管理方法及びライセンス数管理プログラム | |
EP2728504A1 (en) | License administration device and license administration method | |
JP6570801B1 (ja) | Cpuユニット、プログラマブルロジックコントローラ、プログラム、及びエンジニアリングツール | |
WO2015194050A1 (ja) | 産業機器生産システム、産業機器生産方法、プログラム、及び情報記憶媒体 | |
JP6492418B2 (ja) | 決済システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2019568127 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19921844 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20217026824 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19921844 Country of ref document: EP Kind code of ref document: A1 |