JP2007293618A - License management system for medical apparatus, medical apparatus, and license management method for it - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a medical apparatus license management system for issuing a license for use of software and the like and managing it as to a set of a plurality of medical apparatuses. <P>SOLUTION: A scan console 10 working as a main console makes a duplicate of a license for use of the software and the like and adds a file name including a host name for specifying itself to the duplicates. A review console 20 working as an auxiliary console registers the duplicate, and based on the host name included in the file name, determines validity of the license for use by checking whether there is a console making the duplicate or not. When there is the console making the duplicate, it is determined that the license for use registered in the review console 20 is valid, and execution of the software and the like is allowed. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to management of software used for medical devices and medical systems and licenses for licenses of services provided.

  As a technique for managing licenses for use such as software, product activation used in general commercial operating systems is known. The license management procedure by this product activation will be described. First, an installation ID composed of a software product key and hardware configuration information is notified to a license issuer (license management center). The license issuer issues a confirmation ID based on the installation ID. Then, the confirmation ID is input to the device in which the software is installed. The operating system of the device confirms the validity of the license of the software based on the installation ID and the confirmation ID, and if it is determined that the installation is illegal, it prevents login. Thereby, it is possible to prevent the use of illegally installed software.

For the installation ID, for example, hardware configuration information shown in the following (1) to (10) is used.
(1) Display adapter, (2) SCSI adapter, (3) IDE adapter (IDE controller), (4) MAC address of LAN adapter, (5) Size of main memory, (6) CPU type, (7) CPU Serial number, (8) HDD type, (9) HDD serial number, and (10) CD-ROM / CD-R / DVD-ROM type.

  The above-described product activation technique is used to prevent software provided with one license license from being installed and used on a plurality of computers.

  As described above, the license management technology according to the prior art is used to identify the identification information for identifying the computer and the software in order to prevent the software from being illegally installed and used on a plurality of computers. Is stored as a license ID, and when the software is executed, the validity of the license ID is verified.

  By the way, the medical image diagnostic apparatus and the medical system include a scan console for performing imaging, and a review console for performing post-processing such as image processing, image analysis, or filming. Configured. The review console is sometimes referred to as a second console or an image processing workstation.

  The scan console and review console are independent computer systems, but are basically designed to run the same software. As software, for example, an application for calculating a distance or an area in a medical image is applicable. Then, image data captured by the scan console is automatically transferred to the review console, and setting changes in the scan console and review console are automatically reflected in the other console. The review console functions as an integrated system. Each console may be provided with the same service. For example, a virus definition update service corresponds to the service.

  Here, an X-ray CT apparatus will be described with reference to FIG. 19 as an example of a medical image diagnostic apparatus. FIG. 19 is a diagram showing an X-ray CT apparatus as an example of a medical image diagnostic apparatus. The X-ray CT apparatus includes a bed 301, a gantry 302, a scan console 303, and a review console 304. In this example, a plurality of review consoles 304 are installed.

  The scan console 303 controls the operations of the X-ray tube and the X-ray detector disposed on the bed 301 and the gantry 302, and further performs computer processing based on data detected by the X-ray detector, thereby Generate a tomographic image of the specimen.

  Based on the data detected by the X-ray detector, the review console 304 generates a tomographic image of the subject again under new conditions, generates a three-dimensional image, prints the image on a film, Or transfer images to a storage system.

  The bed 301, the gantry 302, the scan console 303, and the review console 304 are connected by a communication cable to transfer data. The communication cable may be directly connected between computers as in serial communication or may use a network such as TCP / IP. The scan console 303 and the review console 304 are connected to other systems in a medical institution and a network for accessing a medical device from a remote location.

  The scan console 303 and the review console 304 are basically equipped with the same software, and can be operated with the same look and field except for the shooting function.

  An engineer or doctor who operates the X-ray CT apparatus can use the scan console 303 and the review console 304 in parallel, and confirms the image obtained by the imaging with the review console 304 while performing the imaging with the scan console 303. Or create a new 3D image, print it on film, or transfer it to an image storage system.

  According to the conventional license management method, it is necessary to issue licenses for use of software and services for each independent computer system and to manage the license for each individual computer system. For this reason, it is necessary to issue and manage licenses for medical image diagnosis apparatuses and medical systems configured by a plurality of computer systems individually for each computer system. For example, it is necessary to manage the scan console and the review console by separately issuing licenses for the individual consoles.

  As described above, the scan console and review console function as an integrated system, and the software and services are provided for a complete set of devices (systems), but individual scan consoles and review consoles are individually provided. It is necessary to issue and manage a use license license, and the use license license is not issued and managed for the system set (for example, Patent Document 1).

  Moreover, unlike a general personal computer, a medical image diagnostic apparatus and a medical system need to function as a whole. However, since the licenses are managed for each individual computer system, if the hardware of each computer system is replaced due to a failure, etc., the license license is reissued and registered for that computer system. There is a need to. As in the product activation described above, device license information for identifying hardware is included in the license, or the license and device identification information are managed in association with each other. Because. In this case, only the software installed in the computer system other than the computer system operates until the reissue and registration is completed, so that there is a problem that the system as a whole becomes unsteady. is there.

  Furthermore, since medical image diagnostic apparatuses and medical systems are apparatuses related to human life, it is required to minimize the time during which the apparatus cannot be used. As in the conventional license management method, in the above example, if the licensed license is managed for each individual console in the above example, it is necessary to register the licensed license by the number of computer systems. Accordingly, time is required, and there is a possibility that the time during which the apparatus cannot be used increases.

  In re-issuance of the license, the new device identification information and the license type are notified to the license issuer (license management center) by telephone, fax, e-mail, etc., and the license issuer issues a new license. It is received by telephone, fax, e-mail, etc., and completed by inputting into the device or installing a license file. As described above, since the reissue of the license for use is time-consuming and takes time, there is a possibility that the time during which the apparatus cannot be used increases.

  Furthermore, since it is necessary to manage licensed licenses for a plurality of computer systems, human error may be induced. For example, there is a possibility that incorrect device identification information is notified to the license issuer (license management center) or device license information is erroneously registered for the device identification information that is the basis for issuing the license agreement. In particular, when reissuing the license, it is necessary to notify the license issuer of the device identification information by telephone or the like, and in this process, incorrect information may be notified to the license issuer. In such a case, the authentication of the license for use is delayed, and there is a possibility that the time during which the apparatus cannot be used becomes long.

  As described above, according to the license management method according to the prior art, even if the parts of the computer system constituting the medical image diagnostic apparatus or the medical system are replaced and repairs are completed, the license agreement is accompanied by the replacement of the parts. Therefore, the medical image diagnostic apparatus and the medical system cannot be used immediately, and there is a problem that takes time to use.

JP 2006-18402 A

  The present invention solves the above-described problems, and issues a license for software and services to a set of medical systems composed of a plurality of medical devices, and manages the license An object is to provide a medical device license management system, a medical device, and a medical device license management method.

  The invention according to claim 1 executes a first medical device including a first execution unit that executes a function tool represented by predetermined software or a predetermined service, and executes the same function tool as the function tool. A second medical device having a second execution unit is a license management system for a medical device connected via a network, and the first medical device is permitted to execute the functional tool. Each time the first execution unit executes the functional tool, the first management unit includes device identification information for identifying the medical device, and manages a license for executing the functional tool. Based on the device identification information for identifying the first medical device and the device identification information of the license license managed by the first management means, the license agreement is set. A first license validity determination unit that permits the first execution unit to execute the functional tool, and a license for use licensed that is managed by the first management unit. License copying means for adding specific information for specifying the first medical device on the network to the license, and the second medical device manages the copied license license Each time the second management unit and the second execution unit execute the functional tool, based on the specific information added to the duplicated license license managed by the second management unit The second license that confirms the presence or absence of the first medical device on the network and, if present, permits the second execution means to execute the function tool. And validity determination means, a license management system of the medical device, characterized in that it comprises a.

  The invention according to claim 2 comprises a medical image diagnostic apparatus for acquiring a medical image of a subject and first execution means for executing a function tool represented by predetermined software or a predetermined service, and the medical image A first medical device for controlling the diagnostic device; and second execution means for executing the same functional tool as the functional tool. The first medical device performs image processing on the medical image acquired by the medical image diagnostic device. A medical device license management system that provides and manages a license for executing the functional tool with respect to a medical system that is connected via a network and functions as a set; The first medical device includes device identification information for identifying a medical device that is permitted to execute the functional tool, and includes a license agreement for executing the functional tool. A first management unit for managing senses, device identification information for identifying the first medical device each time the first execution unit executes the functional tool, and the first management unit First license validity determining means for permitting the first execution means to execute the functional tool targeted by the license for licensing based on the device identification information of the licensed license being managed; A license duplication unit that duplicates the license license managed by the one management unit, and adds identification information for identifying the first medical device on the network to the duplicated license license; The second medical device has a second management unit that manages the copied license, and each time the second execution unit executes the functional tool, The presence or absence of the first medical device on the network is confirmed based on the specific information added to the duplicated license license managed by the second execution means. A license management system for medical equipment, comprising: second license validity determination means for permitting the second execution means to execute the function tool.

  The invention according to claim 11 is a medical device that is connected to another medical device via a network and includes execution means for executing a function tool represented by predetermined software or a predetermined service. Each time the execution means executes the functional tool, the management means for managing the license for executing the functional tool, to which specific information for specifying the medical device on the network is added, Based on the specific information added to the license agreement, the presence or absence of the other medical device on the network is confirmed, and if it exists, the execution of the functional tool is permitted to the execution means. A medical device characterized by having sex determining means.

  The invention according to claim 12 executes a first medical device having a first execution means for executing a function tool represented by predetermined software or a predetermined service, and executes the same function tool as the function tool. A medical device license management method for a system connected to a second medical device having a second execution means via a network, wherein the execution of the functional tool is permitted in the first medical device. A first registration step for registering a license for use in executing the functional tool in the first medical device, including device identification information for identifying the medical device that has been recorded, and the first execution means Each time the functional tool is executed, based on the device identification information for identifying the first medical device and the device identification information of the registered license license, A first license validity determining step for permitting the first execution means to execute the functional tool targeted by the license, and copying the registered license, and the copied license And a license duplication step of adding identification information for identifying the first medical device on the network, and the second medical device uses the duplicated license license for the second medical device. A second registration step of registering with a medical device; and each time the second execution unit executes the functional tool, based on the specific information added to the copied license, the network on the network The presence / absence of the first medical device is confirmed. If the first medical device is present, the second execution means is allowed to execute the function tool. A license validity determining step, a license management method for a medical instrument and performing.

  According to the present invention, a license for one set of a plurality of medical devices is created by making a copy of the license license on one medical device and registering the copied license license on the other medical device. Can be issued and managed. In addition, the validity of the license can be confirmed by confirming the existence of the medical device that created the copy in the medical device in which the copied license is registered. It becomes possible to prevent unauthorized use.

[First Embodiment]
(Constitution)
The configuration of the medical device license management system according to the first embodiment of the present invention will be described with reference to FIG. FIG. 1 is a functional block diagram showing a schematic configuration of a license management system for a medical device according to the first embodiment of the present invention.

  A medical image diagnostic apparatus and a medical system are composed of a plurality of computer systems. In this embodiment, a license management system for a medical device in which the scan console 10 and the review console 20 are connected via a network will be described by taking the scan console 10 and the review console 20 as examples. For example, an X-ray CT apparatus, an MRI apparatus, or an X-ray imaging apparatus is used as the medical image diagnostic apparatus.

  In the license management system for a medical device according to the first embodiment, the scan console 10 is a main (master) console, and the review console 20 is a subordinate (slave) console. The scan console 10 and the review console 20 are basically installed with the same software and are supplied with the same service. In the scan console 10 and the review console 20, a license for use of software and services is registered. In the scan console 10 which is the main console, the original licensed license issued by the license issuer (license management center) is registered. On the other hand, in the review console 20 that is the slave console, a copy of the license license registered in the scan console 10 that is the main console is registered. That is, the original license license is registered in the main console, and a copy of the license license is registered in the slave console.

  In this embodiment, the main console determines the validity of the license for use according to whether or not its own console is the same as the console that is permitted to use software and services. On the other hand, the subordinate console determines the validity of the license for use depending on whether or not the console for which the license for license is copied actually exists. The scan console 10 corresponds to the “first medical device” of the present invention, and the review console 20 corresponds to the “second medical device” of the present invention.

  The software corresponds to various programs used in medical equipment such as a program for measuring a length and an area. The service corresponds to a virus definition update service. The use license is a license for using these software and services. If the use license is valid, the software can be executed on the scan console 10 or the review console 20, and the service is provided. Can receive. On the other hand, if the license is invalid, the software cannot be executed and the service cannot be provided. Software and services correspond to “functional tools” of the present invention.

  In this embodiment, the scan console 10 which is the main console creates a copy of the license agreement and registers the copy in the review console 20 to collectively manage the license agreement. Then, the review console 20 confirms the existence of the console that has made a copy of the license agreement, and if the existence is confirmed, the copy of the license agreement is determined to be valid, and the existence is not confirmed. In this case, it is possible to prevent unauthorized use of software and services by determining that the copy of the license agreement is invalid. In the following, first, the configuration of the scan console 10 will be described, and then the configuration of the review console 20 will be described.

<Configuration of Scan Console 10>
(Register licensed license)
First, a configuration related to registration and management of a license agreement will be described. The license registration unit 11 of the scan console 10 installs a license for use of software and services issued by a license issuer (license management center) in the scan console 10. The original licensed license is installed in the scan console 10.

  For example, when the license agreement is stored in an external recording medium such as a CD-R, DVD-R, or HDD, the license registration unit 11 reads the license agreement from the recording medium, and scan console 10 to install. If the external server storing the license and the scan console are connected via a network, the license registration unit 11 reads the license from the external server, and the scan console 10 You may install it on

  Further, a license license registration screen may be displayed on a display device (not shown), and license license information may be input on the registration screen. In this case, the license information is obtained from the license issuer by a method such as telephone or e-mail. An example of this registration screen is shown in FIG. In the example shown in FIG. 5, the license key corresponds to licensed license information, and the operator inputs the license key obtained from the license issuer on the registration screen.

  Here, the configuration of the license agreement will be described with reference to FIG. FIG. 2 is a diagram showing an example of the configuration of the license for use.

  As shown in FIG. 2, the license agreement includes an area for storing target identification information and an area for storing apparatus identification information. The target identification information is information for identifying software or services that are subject to use permission. The device identification information is information for identifying a console (device) that is licensed. Furthermore, the license agreement verifies that the version license format format information storage area, the encoding (encoding) information storage area information, and the license agreement have not been tampered with. An area for storing a checksum may be provided. Hereinafter, each piece of information constituting the license agreement will be described.

  The version information is represented by, for example, a 2-digit value, the upper digit represents the major version number, and the lower digit represents the minor version number. For example, the version information is updated when new information is added to the license for use. Since the version information is information necessary for identifying a plurality of license license formats, it is not always necessary when only a single format is supported.

  The information indicating the encoding method is represented by, for example, a one-digit value (method number), and is information for identifying what encoding method is used. The information indicating the encoding method is also added in consideration of the case where the encoding method is changed, and is not necessarily required when only a single encoding method is supported. FIG. 3 shows an example of the encoding method and the method number assigned to the encoding method. In the example illustrated in FIG. 3, encoding methods having method numbers (codes) 1 to 9 and A to F are illustrated. The used encoding method is identified by this method number (code).

  The object identification information includes a product classification code (1 digit), an object identification code (8 digits), and a master / slave identification code (1 digit) as a character string.

  The product classification code is information for specifying the type of product for which a license is issued, assuming that licenses are issued for various product groups such as an X-ray CT apparatus and an MRI apparatus. is there. When issuing a license for use only for a single product, the product classification code need not be included in the target identification information.

  The target identification code is information for identifying software or services that are subject to use permission. It may be a character string for identifying software or service, or may be a code for identifying software or service. Further, not only a single software or service may be identified, but a combination of a plurality of licenses may be identified. For example, the presence / absence of permission for use of one software or service can be expressed by 1 bit, and the licensed software or service can be expressed by the number of bits.

  FIG. 4 shows an example of bit representation of the object identification information. In the table of FIG. 4, combinations of licenses for 16 types of software and services can be expressed using 16 bits. In the example of the figure, when the value is “0”, the use license is “none”, and when the value is “1”, the use license is “present”.

  The master-slave identification code is information for identifying whether the license for use is an original or a copy. For example, the master-slave identification code “0” represents the original, and the others represent the number of times of duplication (duplication number). For example, the replication number is expressed as a hexadecimal number or a 32 digit number with one digit. That is, if the master-slave identification code is “0”, it means that this license is an original, and if it is not “0”, this means that this license is a duplicate. Furthermore, the number of times of copying (replication number) is represented by the numerical value.

  Since the original licensed license issued by the license issuer (license management center) is registered in the scan console 10, the master-slave identification code of the licensed license registered in the scan console 10 is “0”. ing. On the other hand, since a copy of the license agreement is registered in the review console 20, the master-slave identification code of the license agreement registered in the review console 20 is other than “0”.

  The device identification information is information for identifying a licensed console (device), for example. This apparatus identification information is configured with information (hereinafter, also referred to as “device information”) for specifying a device installed in a console (apparatus) for which use is permitted. In the example shown in FIG. 2, the device identification information is composed of a combination of an IP address, a MAC address of the LAN adapter, and a volume number of the HDD. For example, if the scan console 10 is a licensed console, the device identification information of the license license is composed of information for identifying the scan console 10.

  It should be noted that information other than the IP address, MAC address, and HDD volume number may be combined to form device identification information, and one piece of information may be used as device identification information. Further, in the case of a device equipped with a plurality of LAN adapters and HDDs, the device identification information may be obtained by using all the information, and the device identification information may be obtained by using the identification information of the LAN adapter or HDD designated in advance. It is also good.

  The checksum information is information for confirming whether the license agreement has been tampered with. Detects whether the license agreement has been tampered with by comparing the checksum value calculated in advance based on the license agreement with the newly calculated checksum value based on the license agreement To do. The checksum calculation method includes various encoding methods as shown in FIG. 3. In this embodiment, the checksum is calculated by CRC-16 as an example.

  The supplementary information is a comment indicating the product model of the product subject to the license, the name of the software or service, and the like. Note that the supplementary information is not essential information, and thus the supplementary information may not be included in the license agreement.

  The license management unit 12 of the scan console 10 stores and manages the installed license. The license agreement may be managed as a file or may be managed by a database management system. The license management unit 12 also installs the licensed license (registration date / time), duplicates the licensed date / time (duplication date / time), identification information (duplicate device identification information) of the copied console (device), Manages management information such as replication number (number of replications). For this management, a management file may be provided to manage management information, or a management table may be provided in the database management system for management. The license management means 12 corresponds to the “first management means” of the present invention.

(Copy of license)
Next, a configuration related to duplication of the license for use will be described. The license copying unit 13 creates a copy of the license for use for the software or service selected by the operator. For example, as in the example of the duplication screen shown in FIG. 6, the names of software and services registered in the scan console 10 are displayed on a display device (not shown), are in a selectable state, and are displayed. The operator selects the name of the software or service for which the license agreement is desired to be copied.

  When a software or service is selected and a copy instruction is given, the license acquisition unit 14 uses the license and the license management information (registration) based on the target identification code of the software or service target identification information. Information such as date / time, duplication date / time, duplication device identification information, duplication number, etc.) is acquired from the license management means 12. When the licensed license is managed by the database management system, the license acquisition unit 14 acquires the licensed license and management information by performing a search on the database.

  The license copying unit 13 receives the license and management information output from the license acquisition unit 14 and creates a copy of the licensed license. In order to distinguish between the original licensed copy and the copy, the license copy means 13 increments (increases) the copy number (number of copies) at that time, and uses the increased value as the master-slave identification of the copied license license. The code value. If the license is an original license, the master-slave identification code is “0”, and if it is a copy, the copy number (number of times of copying) is the value of the master-slave identification code. Therefore, it is possible to distinguish between the original license and the copy of the license.

  Further, the license duplicating unit 13 calculates a checksum of the license license and uses the value as checksum information. Then, the license copying unit 13 registers the copy of the license license for use in the license management unit 12 and outputs it to the license output unit 15.

  When the license output unit 15 receives the license license copy from the license copy unit 13, the license output unit 15 assigns a file name to the copy of the license license according to a predetermined file name naming rule and stores it in the designated recording device. To do. As an example of the file name naming rule, for example, “(License) + (host name of the console that performed the replication) + (generation date (yyyymmddhmmmss)). Dat”. In this way, the file name was copied by referring to the file name by including information (in this case, the host name) for identifying the copied console on the network. It becomes possible to specify the console. In this embodiment, since the console (device) that performed the duplication is the scan console 10, the host name of the scan console 10 is included in the file name.

  Note that, as shown in FIG. 7, the license output means 15 may save the copy of the license agreement and the original license license together in a designated recording device as one license license file. good. Accordingly, it is possible to confirm whether or not the license for use has been tampered with by comparing the original and the copy.

  Note that if a license agreement with the same file name is stored in the specified recording device, a confirmation dialog is displayed on the display device (not shown) and an overwrite save command is issued. Thereafter, the license output unit 15 overwrites and saves the license for use.

(Determination of validity of licensed license)
Next, a configuration relating to the determination of the validity of the license agreement will be described. The device identification information acquisition unit 17 acquires device identification information for identifying a console (device) from the console itself, and outputs the acquired device identification information to the license validity determination unit 16. In this embodiment, the device identification information acquisition unit 17 acquires device identification information from the scan console 10 itself. In this embodiment, as shown in FIG. 2, since the IP address, the MAC address of the LAN adapter, and the volume number of the HDD are used as the device identification information, the device identification information acquisition unit 17 uses the IP address of the scan console 10. MAC address and HDD serial number are acquired. For example, device identification information can be acquired by using a function provided by the operating system of the scan console 10 (a function such as a library provided by the platform SDK).

  In addition, when the scan console 10 is equipped with a plurality of IP addresses, LAN adapters, and HDDs, information used as device identification information is designated as configuration information, whereby the designated information is identified as device identification. It may be used as information, or information obtained by combining all information may be used as device identification information.

  Each time the software or service is executed, the license validity determination unit 16 receives the target identification information of the software or service operating on the scan console 10 and determines the validity of the license for use of the software or service. For example, the control unit 18 that executes the software or service outputs target identification information of the software or service to the license validity determination unit 16 together with the validity verification request for the license. The license validity determination unit 16 receives the validity verification request and the target identification information, and determines the validity of the license for use of the software or service. When it is determined that the license for use is valid, the control unit 18 executes the software or service. When it is determined that the license is invalid, the execution is prohibited. The license validity determination means 16 corresponds to the “first license validity determination means” of the present invention, and the control means 18 corresponds to the “first execution means” of the present invention.

  First, the license validity determination unit 16 specifies a system configuration that specifies whether the scan console 10 operates as a “main” console (device) or a “secondary” console when the scan console 10 is activated. Are read from the internal storage device. In this embodiment, the scan console 10 has a “main” console setting. As a result, the scan console 10 determines the validity of the license for use depending on whether or not the console of the scan console 10 is the same as the console permitted to use the software or service.

  Next, the license validity determination unit 16 receives the target identification information from the software or service running on the scan console 10 and outputs the target identification information to the license acquisition unit 14. Alternatively, the license validity determination unit 16 may convert the target identification information into an internal code and output the internal code to the license acquisition unit 14. The license acquisition unit 14 acquires the corresponding license license from the license management unit 12 using the target identification information or the internal code as a search condition, and outputs the license to the license validity determination unit 16.

  The license validity determination unit 16 calculates a checksum based on the version information and the encoding method included in the acquired license agreement. Then, the license validity determination unit 16 compares the calculated value with the value stored in the checksum area of the license agreement, and determines whether or not the values match. If the checksum values match, the license agreement has not been tampered with. On the other hand, if the checksum values do not match, the license agreement has been tampered with. If it is determined that the license agreement has been tampered with, the license validity determination unit 16 outputs information indicating that the license has been tampered to the control unit 18. When the control means 18 receives a notification that it has been tampered with, it stops the activation of the software or service.

  Next, the license validity determination unit 16 confirms that the master-slave identification code of the license agreement indicates “0” and that the license license is the original. For example, when the license acquisition unit 14 acquires the license for use with the master-slave identification code “0” from the license management unit 12, the license validity determination unit 16 outputs the original licensed license, and the license is valid. The sex determination means 16 confirms that it is an original. Further, the license validity determination unit 16 determines the validity of the license using the licensed license whose master-slave identification code is “0” among the licensed licenses acquired by the license acquiring unit 14.

  Next, the license validity determination unit 16 compares the device identification information included in the license for use with the device identification information of the scan console 10 acquired by the device identification information acquisition unit 17, and the same for the console (device). Determine gender. For example, if the device information constituting the device identification information matches, the license validity determination unit 16 determines that there is console identity. In the example of the license agreement shown in FIG. 2, since the device identification information is composed of the IP address, the MAC address, and the HDD volume number, these values coincide with the device identification information acquired from the scan console 10. If so, it is determined that the consoles are identical.

  In addition, when the device identification information is configured by a plurality of device information, the console is used when the same number or the same ratio among the plurality of device information is equal to or more than a predetermined number or ratio. It may be determined that there is identity. In the example shown in FIG. 2, if two or more values out of the IP address, MAC address, and HDD volume number, for example, match the value of the device identification information acquired from the scan console 10, the console identity It is determined that there is. As a result, even if some devices of the scan console 10 are replaced, it is determined that they are the same as the console. In this way, by making the console identity determination redundant, even if some devices are replaced, there is no need to issue a new license, and the license license that has been used up to now can be used. It can be used continuously.

  When it is determined that they are the same console (device), the license validity determination unit 16 makes a reply to the control unit 18 that the license for use is valid, and determines that they are different devices (console). If so, a reply that the license is invalid is made.

  Upon receiving an answer that the license is valid, the control unit 18 executes the software or service that is the target of the license. On the other hand, when receiving a reply that the license for use is invalid, the control means 18 stops execution of the target software or service.

  Note that the license validity determination unit 16 performs a tampering check and an original confirmation for the licensed license registered in the license management unit 12 in advance, and holds the licensed license on a memory (not shown). Alternatively, the validity may be determined when the validity verification request for the license agreement is received from the control means 18.

  Also, for example, a checksum is calculated using information other than the device identification information and the device identification information acquired by the device identification information acquisition means 17, and the calculated value is stored in the checksum area of the license agreement. The validity of the license may be determined by comparing with the value that has been set.

  As described above, the scan console 10 operating as the main console (device) determines the validity of the license to be used by determining the identity of the console (device) based on the device identification information.

  In addition, the reply means 19 returns a response of presence confirmation to the review console 20 from the review console 20 in response to the presence confirmation request of the console (apparatus) for which the license agreement has been copied. For example, when data is transmitted from the review console 20 as an ICMP ECHO command according to the ECHO protocol based on the host name of the console (scan console 10) that performed the duplication, the response means 19 transmits as an ICMP ECHO REPLY command. The sent data is returned to the review console 20 as it is. The review console 20 can check whether or not there is a console to which the license agreement has been copied, depending on whether or not a response is returned. Further, a response expected for a communication request may be returned using a communication protocol such as RPC (Remote Procedure Call).

<Configuration of Review Console 20>
(Register licensed license)
First, a configuration related to registration and management of a license agreement will be described. The license registration unit 21 of the review console 20 installs the license for use copied in the scan console 10 in the review console 20. For example, when the copied license license is stored in an external recording medium such as a CD-R, DVD-R, or HDD, the license registration unit 21 copies the license license copied from the recording medium. Is installed in the review console 20. Further, a license for use may be installed from an external server via a network. In addition, as shown in FIG. 5, a registration screen may be displayed on the display means 27, and the operator may input the license key of the copied license license on the registration screen.

  The license management means 22 of the review console 20 stores and manages the installed licenses. The license agreement may be managed as a file or may be managed by a database management system. The license management means 22 also installs the licensed license (registration date / time), copies the licensed date / time (duplication date / time), duplicates console identification information (duplication device identification information), duplicate number ( Management information such as the number of copies). For this management, management information may be managed by providing a management file, or a management table may be provided and managed in the database management system. The license management means 22 corresponds to the “second management means” of the present invention.

(Determination of validity of licensed license)
Next, a configuration relating to the determination of the validity of the license agreement will be described. Each time the software or service is executed, the license validity determining unit 24 receives the target identification information of the software or service operating on the review console 20 and determines the validity of the license for use of the software or service. For example, the control unit 25 that executes the software or service outputs the software or service target identification information to the license validity determination unit 24 together with the validity verification request for the license. The license validity determination unit 24 receives the validity verification request and the target identification information, and determines the validity of the license for use of the software or service. The license validity determination unit 24 corresponds to the “second license validity determination unit” of the present invention, and the control unit 25 corresponds to the “second execution unit” of the present invention.

  First, the license validity determination unit 24 specifies a system configuration that specifies whether the review console 20 operates as a “main” console (device) or a “subordinate” console when the review console 20 is activated. Are read from the internal storage device. In this embodiment, the review console 20 is set to a “secondary” console. As a result, the review console 20 determines the validity of the license agreement depending on whether or not the console that has copied the license license actually exists.

  Next, the license validity determination unit 24 receives the target identification information of the software or service operating on the review console 20 and outputs the target identification information to the license acquisition unit 23. Alternatively, the license validity determination unit 24 may convert the target identification information into an internal code and output the internal code to the license acquisition unit 23. The license acquisition unit 23 acquires the corresponding license license from the license management unit 22 using the target identification information or the internal code as a search condition, and outputs it to the license validity determination unit 24.

  The license validity determination unit 24 calculates a checksum based on the version information and the encoding method included in the acquired license agreement. Then, the license validity determination unit 24 compares the calculated value with the value stored in the checksum area of the license agreement, and determines whether or not the values match. If the checksum values match, the license agreement has not been tampered with. On the other hand, if the checksum values do not match, the license agreement has been tampered with. If it is determined that the license agreement has been tampered with, the license validity determination unit 24 outputs information indicating that the license has been tampered to the control unit 25. When the control means 25 receives the information indicating that it has been tampered with, it stops the activation of the software or service.

  Next, the license validity determination unit 24 confirms that the master-slave identification code of the license agreement is other than “0” and that the license license is a copy.

  Then, the license validity determining unit 24 determines the validity of the licensed license depending on whether or not there is a console (device) that created a copy of the licensed license. If there is a console for which a copy of the licensed license exists, the license validity determination unit 24 determines that the licensed license copy is valid, and if there is no console for which the duplicated license exists, the license validity determination unit 24 copies the licensed license. Judge as invalid. The duplication device existence confirmation unit 26 confirms the existence of the console to which the license agreement is duplicated.

  The license validity determination unit 24 acquires the host name of the console that created the copy (the host name of the scan console 10) from the file name of the copy of the license agreement, and outputs the host name to the copy device existence confirmation unit 26. To do.

  The duplication device existence confirmation unit 26 confirms whether or not there is a console (device) that has created a duplicate of the license agreement. The duplication device existence confirmation unit 26 transmits an ICMP ECHO command to the scan console 10 according to the ECHO protocol and receives an ICMP ECHO REPLY command based on the host name of the scan console 10 acquired by the license validity determination unit 24, for example. Confirm whether or not there is a console that created the duplicate. When an ECHO response is returned in response to an ECHO request, the duplicating device existence confirmation unit 26 determines that there is a console that has created a copy of the license, and creates a copy if no response is returned. It is determined that there is no console. Further, a response expected for a communication request may be returned using a communication protocol such as RPC (Remote Procedure Call).

  The duplication device existence confirmation unit 26 outputs the determination result to the license validity determination unit 24. The license validity determination unit 24 determines the validity of the license based on the determination result. When the duplication device existence confirmation unit 26 confirms the existence of the console (device) that created the duplication, the license validity judgment unit 24 determines that the duplication of the license license is valid. On the other hand, if the duplication device existence confirmation unit 26 does not confirm the existence of the console that created the duplication, the license validity judgment unit 24 determines that the duplication of the license for use is invalid. In other words, if the existence of the console that created the copy is confirmed, it is determined that the copy of the licensed license is a legitimate license, and if the existence of the console that created the copy is not confirmed, the licensed license It is determined that the copy of is not a regular license but a license copied by an illegal act.

  When the presence of the console that created the copy is confirmed, the license validity determination unit 24 sends a reply to the control unit 25 that the copy of the license license is valid. On the other hand, if the existence of the console that created the copy is not confirmed, the license validity determination unit 24 responds to the control unit 25 that the copy of the license license is invalid.

  When the control means 25 receives an answer that the copy of the license agreement is valid, it executes the software or service that is the subject of the license agreement. On the other hand, when the control means 25 receives a reply that the copy of the license license is invalid, it stops the execution of the target software or service.

  The license validity determination unit 24 performs a tampering check and an original confirmation on the licensed license registered in the license management unit 22 in advance, and holds the licensed license on a memory (not shown). When the validity verification request for the license agreement is received from the control means 25, the validity may be determined.

  As described above, the original license license is registered in the scan console 10 operating as the main console, and the license license duplicated in the scan console 10 is registered in the review console 20 operating as the slave console. This eliminates the need for the license issuer (license management center) to issue a license for each console. As a result, it is possible to collectively issue and manage licenses for use of software and services of medical systems. In addition, it is possible to confirm whether or not duplication has been performed illegally by confirming the existence of the console that has created a duplication of the license license in the subordinate console. As a result, licenses are issued to a set of multiple medical devices, and the licenses are managed in a batch, and the validity of the licenses is checked to prevent unauthorized use of software and services. It is possible to prevent it.

  And since licenses can be issued and managed for a set of multiple medical devices, it is possible to prevent the occurrence of human error during issuance of licenses and registration. It becomes possible to reduce the unavailable time.

  Note that the license registration unit 11, the license duplication unit 13, the license acquisition unit 14, the license output unit 15, the license validity determination unit 16, and the device identification information acquisition unit 17 may be configured by hardware, software It may consist of. For example, the scan console 10 includes a CPU and a storage device (not shown), and the CPU executes a program stored in the storage device, thereby executing the functions of each unit such as the license registration unit 11.

  Further, the license registration unit 21, the license acquisition unit 23, the license validity determination unit 24, and the duplication device existence confirmation unit 26 may be configured by hardware or software. For example, the review console 20 includes a CPU and a storage device (not shown), and the CPU executes a program stored in the storage device, thereby executing the functions of each unit such as the license registration unit 21.

  In this embodiment, the case where the scan console 10 operates as a main console and the review console 20 operates as a slave console has been described. However, even if the relationship between the master and the slave is reversed, the embodiment The same actions and effects can be achieved. For example, when the review console 20 operates as the main console, the review console 20 determines the validity of the license according to whether or not its own console is the same as the console that is permitted to use software and services. judge. Further, the review console 20 creates a copy of the license license. On the other hand, when the scan console 10 operates as a slave console, the scan console 10 determines the validity of the license agreement depending on whether or not the console that has duplicated the license license actually exists.

  Further, the same operations and effects can be achieved even for devices other than the scan console 10 and the review console 20.

(Operation)
Next, a series of operations (license management method) performed by the medical device license management system according to the first embodiment of the present invention will be described with reference to FIGS. 8 to 10 are flowcharts showing a series of operations by the security management system for the medical device according to the first embodiment of the present invention. First, the operation of the scan console 10 that operates as a main console will be described with reference to FIGS. 8 and 9, and the operation of the review console 20 that operates as a slave console will be described with reference to FIG.

  First, referring to FIG. 8, registration and duplication of a license for use in the scan console 10 will be described.

(Step S01)
First, the license registration unit 11 of the scan console 10 installs the license for use (original) issued by the license issuer (license management center) in the scan console 10. For example, the license registration unit 11 installs a use license from a recording medium or installs it via a network. Further, a registration screen shown in FIG. 5 may be displayed on a display device (not shown), and an operator may input a license key on the registration screen. The license management unit 12 stores and manages the installed license.

(Step S02)
Next, the operator selects software or a service for which a license for use license is desired. For example, the copy screen shown in FIG. 6 is displayed on a display device (not shown), and the operator selects the name of the software or service for which the license agreement is desired to be copied from the displayed software or service name. Select.

(Step S03)
When software or service is selected in step S02, the license acquisition unit 14 uses the license and management information (registration date and time, duplication date and time) based on the target identification code of the target identification information of the selected software and service. , Information such as copy device identification information and copy number) is acquired from the license management means 12 and output to the license copy means 13.

(Step S04)
Then, the license copying unit 13 receives the use license and the management information acquired by the license acquisition unit 14 and creates a copy of the use license. Further, the license duplication unit 13 increments (increases) the duplication number (the number of duplications) at that time, and sets the incremented value as the value of the master-slave identification code of the duplicated license. Further, the license duplicating unit 13 calculates a checksum of the license license and uses the value as checksum information. Then, the license copying unit 13 registers the copied license license in the license management unit 12 and outputs it to the license output unit 15.

(Step S05)
The license output means 15 assigns a file name to the copy of the license agreement according to a predetermined file name naming rule, and stores it in the designated recording device. This file name includes the host name of the console that created the copy of the license agreement. In this embodiment, since the scan console 10 creates a copy of the license license, the license output unit 15 includes the host name of the scan console 10 in the file name.

  By performing the above processing, the license agreement is installed in the scan console 10, and a copy of the license agreement is created.

  Next, with reference to FIG. 9, the determination of the validity of the license for use in the scan console 10 will be described.

(Step S06)
First, the license validity determination unit 16 reads the system configuration from the internal storage device when the scan console 10 is activated, and confirms whether the scan console 10 operates as a main console or a secondary console. In this embodiment, the scan console 10 operates as a main console.

(Step S07)
Next, the control means 18 outputs to the license validity determination means 16 the object identification information of the software or service operating on the scan console 10 together with the validity verification request for the license agreement. The license validity determination unit 16 outputs the target identification information or the internal code to the license acquisition unit 14. The license acquisition unit 14 acquires the corresponding license license from the license management unit 12 using the target identification information or the internal code as a search condition, and outputs it to the license validity determination unit 16.

(Step S08)
Next, the license validity determination unit 16 calculates a checksum based on the version information and the encoding method included in the acquired license, and compares it with the value of the checksum area of the license. If the values match, the license validity determination unit 16 determines that the use license has not been tampered with. On the other hand, if the values do not match, the license validity determination unit 16 determines that the license agreement has been tampered with, and outputs the determination result to the control unit 18. When the control means 18 receives a notification that tampering is indicated, the control means 18 stops the activation of the software or service.

(Step S09)
Next, the license validity determination unit 16 confirms that the master-slave identification code of the license agreement indicates “0” and that the license license is the original.

(Step S10)
On the other hand, the device identification information acquisition unit 17 acquires the device identification information of the scan console 10 itself and outputs it to the license validity determination unit 16.

(Steps S11 and S12)
Then, the license validity determination unit 16 compares the device identification information included in the license for use with the device identification information of the scan console 10 acquired by the device identification information acquisition unit 17 to determine console identity. . For example, when the same number or the same ratio among a plurality of device information constituting the device identification information is equal to or greater than a predetermined number or ratio, the license validity determination unit 16 uses the same console. It is judged that.

  When it is determined that the consoles are the same, the license validity determination unit 16 responds to the control unit 18 that the license is valid. Answer that the license is invalid.

(Step S13)
When the control means 18 receives an answer that the license for use is valid (step S12, Yes), the control means 18 operates the software or service that is the subject of the license for use.

(Step S14)
On the other hand, when receiving a reply that the license for use is invalid (step S12, No), the control means 18 stops the activation of the target software or service.

  As described above, the scan console 10 operating as the main console determines the validity of the license agreement by determining console identity.

  Next, the operation in the review console 20 will be described with reference to FIG.

(Step S20)
First, the license registration means 21 of the review console 20 installs the duplicated license license on the review console 20. For example, the license registration unit 21 installs a license for use from a recording medium or installs it via a network. Further, the registration screen shown in FIG. 5 may be displayed on the display means 27, and the operator may input a license key on the registration screen. The license management means 22 stores and manages the installed license license.

  Next, the license validity determination unit 24 determines the validity of the license for use of software or services operating on the review console 20.

(Step S21)
First, the license validity determination unit 24 reads the system configuration from the internal storage device when the review console 20 is activated, and checks whether the review console 20 operates as a main console or a subordinate console. . In this embodiment, the review console 20 operates as a slave console.

(Step S22)
Next, the control means 25 outputs to the license validity judgment means 24 the target identification information of the software or service operating on the review console 20 together with the validity verification request of the license agreement. The license validity determination unit 24 outputs the target identification information or the internal code to the license acquisition unit 23. The license acquisition unit 23 acquires the corresponding license license from the license management unit 22 using the target identification information or the internal code as a search condition, and outputs it to the license validity determination unit 24.

(Step S23)
Next, the license validity determination unit 24 calculates a checksum based on the version information and the encoding method included in the acquired license, and compares it with the value of the checksum area of the license. If the values match, the license validity determination unit 24 determines that the use license has not been tampered with. On the other hand, if the values do not match, the license validity determination unit 24 determines that the license agreement has been tampered with, and outputs the determination result to the control unit 25. When the control means 25 receives a notification indicating that it has been tampered with, it stops the activation of the software or service.

(Step S24)
Next, the license validity determination unit 24 confirms that the master-slave identification code of the license agreement is other than “0” and that the license license is a copy.

(Step S25)
Next, the license validity determination unit 24 obtains the host name of the console that created the copy from the file name of the copy of the license license, and outputs the host name to the copy apparatus existence confirmation unit 26. In this embodiment, since the scan console 10 creates a copy of the license agreement, the host name of the scan console 10 is attached to the file name.

(Step S26)
Then, based on the host name of the scan console 10, the duplicating device presence confirmation unit 26 transmits an ICMP ECHO command to the scan console 10 according to, for example, the ECHO protocol, and performs duplication depending on whether or not the ICMP ECHO REPLY command is received. Check whether the created console exists. When the data is transmitted as the ICMP ECHO command from the review console 20, the response means 19 of the scan console 10 returns the data transmitted as the ICMP ECHO REPLY command to the review console 20 as it is. If an ECHO response is returned in response to the ECHO request, the duplicating device existence confirmation unit 26 determines that there is a console that has created a copy of the license, and if no response is returned, the duplicating device existence confirmation unit 26 It is determined that the console that created the file does not exist.

(Step S27, Step S28)
If the duplicating device existence confirmation unit 26 determines that there is a console that has produced a copy of the licensed license (Yes in step S27), the license validity determination unit 24 determines that the licensed license copy is valid. (Step S28). That is, it is determined that the copy of the license for use is a legitimate license.

(Step S27, Step S29)
On the other hand, if the duplicating device existence confirmation unit 26 determines that there is no console that has created a copy of the license agreement (No in step S27), the license validity determination unit 24 copies the license agreement license. It determines with it being invalid (step S29). That is, it is determined that the copy of the license license is not a regular license but a license copied by an illegal act.

(Step S30)
If it is determined that the use license is valid, the control unit 25 operates the software or service that is the target of the use license.

(Step S31)
On the other hand, when it is determined that the license for use is invalid, the control unit 25 stops the activation of the target software or service.

  As described above, the review console that operates as a subordinate console determines the validity of the license agreement by confirming the existence of the console to which the license agreement has been copied.

  As described above, by registering the original license license in the main console and registering the duplicate in the slave console, it is not necessary to issue the license license for each individual console. Can be issued and managed. Also, by confirming the existence of the console that has copied the license agreement, it can be determined whether the copy is legitimate or illegal. As a result, it is possible to prevent the unauthorized use of software and services by confirming the validity of the licensed license while managing licensed licenses collectively.

[Second Embodiment]
Next, a medical device license management system according to a second embodiment of the present invention will be described. The license management system for a medical device according to the second embodiment has almost the same configuration as that of the first embodiment, but the information included in the license for use and the function of the license validity determination unit 16 are different. Here, the explanation will focus on the license agreement and the license validity determination means 16.

  As in the first embodiment, the license for use used in the second embodiment is for identifying object identification information for identifying software or services to be licensed, and a console for which use has been licensed. And group information representing a group of software and services to be licensed. This group represents a range of similar software and services, and is determined by, for example, a provider of software or services. By adding group information to software and services, software and services to which the same group information is added are determined to be the same kind of software and services.

  If the group information added to the newly installed software or the newly provided service is the same as the group information included in the license license registered in the license management unit 12, the license validity The determination unit 16 determines that the license for the software or service is valid, and if the group information is different, the determination unit 16 determines that the license for use is invalid. When it is determined that the license for use is valid, the license validity determination unit 16 replies to the control unit 18 that the license is valid. In response to the answer, the control means 18 executes the software or service that is the subject of the license agreement.

  As described above, software that is not currently installed or services that are not provided can be installed or provided in the future by determining whether the license agreement is valid or invalid based on the group information indicating the license application range. In this case, it becomes possible to use new software and services without adding or changing licenses. In other words, when software and services belonging to the same group are added, the new software and services can be used without waiting for the issuance of a new license, reducing the time during which the device cannot be used. It becomes possible to do.

  Although the license validity determining unit 16 of the scan console 10 has been described here, the license validity determining unit 24 of the review console 20 may also determine whether the license for use is valid or invalid based on the group information. .

[Third Embodiment]
Next, a configuration of a license management system for a medical device according to a third embodiment of the present invention will be described with reference to FIG. FIG. 11 is a functional block diagram showing a schematic configuration of a license management system for a medical device according to the third embodiment of the present invention.

  The license management system for a medical device according to the third embodiment includes information indicating the period of use permission in the use license and determines the validity of the use license based on temporal conditions. In this embodiment, as an example, a case where the history management unit 32 and the history search unit 33 are provided in the scan console 30 that operates as a main console will be described. Since the configuration and functions other than the license validity determination unit 31, the history management unit 32, and the history search unit 33 are the same as those in the first embodiment, the description thereof is omitted.

  The license agreement used in the third embodiment is the same as in the first embodiment, in order to identify target identification information for identifying software or services subject to license agreement and the licensed console. Information indicating the period of use permission (hereinafter also referred to as “use permission period information”). This use permission period information includes an issue date and time and an effective period, or an effective date and time.

  Like the license validity determination unit 16 in the first embodiment, the license validity determination unit 31 of the scan console 30 compares the device identification information included in the license for use with the device identification information of the scan console 30. Check the console identity. In this embodiment, the license validity determination unit 31 further confirms that the license for use is within the expiration date.

  For example, when an issuance date / time and an effective period are used as the license agreement period information, the license validity determination unit 31 calculates an expiration date / time based on the issuance date / time and the effective period. Then, the license validity determination unit 31 compares the calculated expiration date with the current date and time (system time) calculated by the timing unit included in the scan console 30, and the current date and time is the expiration date and time. The validity of the license is determined based on whether or not the license is exceeded.

  When an expiration date is used as the license agreement period information, the license validity determination unit 31 determines the date and time of the expiration date and the current date and time (system time) calculated by the timing unit included in the scan console 30. And the validity of the license agreement is determined based on whether or not the current date and time exceeds the date and time of the expiration date.

  If the current date and time exceeds the date and time of the expiration date, the license validity determination unit 31 determines that the license for use is invalid even if it is determined that the consoles are the same. On the other hand, if the current date does not exceed the date of the expiration date and it is determined that the consoles are the same, the license validity determination unit 31 determines that the license for use is valid. When it is determined that the license for use is valid, the license validity determination unit 16 replies to the control unit 18 that the license is valid. In response to the answer, the control means 18 executes the software or service that is the subject of the license agreement.

  Also, when determining the validity of the licensed license using the console system time, it is as if the licensed license is still within the expiration date by temporarily going back to the past. There is a risk that software or services may be used.

  Therefore, in this embodiment, the system time when the validity of the license agreement is determined is recorded, and when the validity is newly determined, the recorded system time is compared with the current system time. If the current system time goes back from the time of the previous determination, the license for use is invalidated assuming that the system time of the console has been tampered with.

  In FIG. 11, each time the license validity determination unit 31 determines the license, the license validity determination unit 31 records the information used for the determination in the history management unit 32 as determination history information. The information used for the determination (determination history information) includes, for example, the system time (time) when the determination is performed. Further, the information used for the determination may include information such as device identification information included in the license, license period information, and device identification information acquired by the device identification information acquisition unit 17. The history management means 32 may manage the history information of the determination as one file, manage the history information by adding new history information, and add the history information using the database management system. Thus, history information may be managed.

  When the license validity determination unit 31 receives the validity verification request for the license agreement, the history search unit 33 acquires the history information of the previous determination from the history management unit 32 and sends it to the license validity determination unit 31. Then, the license validity determination unit 31 compares the current system time of the console acquired this time with the previous system time included in the history information. If the current system time goes back from the previous system time, the system time of the console may be falsified. Even if the consoles are the same, the license validity determination means 31 has an invalid license. Judge that there is.

  On the other hand, if the current system time exceeds the previous system time, it is determined that the console system time has not been tampered with, and if the console is the same and is within the expiration date of the license, the license validity determination The means 31 determines that the license for use is valid.

  As described above, the date and time when the validity of the licensed license was determined is recorded as a history, and the system time is falsified by comparing the system time with the history when a new determination is made However, since it is possible to detect falsification of the system time, it is possible to prevent unauthorized use of software and services.

  In this embodiment, the scan console 30 that operates as a main console has been described. However, the review console 20 that operates as a subordinate console is provided with history management means and history search means, and the expiration date of the license license is determined. Further, it may be confirmed whether or not the system time of the review console 20 is falsified.

  Further, the third embodiment and the second embodiment may be combined. In other words, in the third embodiment, when the same kind of software is installed or the same kind of service is provided by including the group information in the licensed license, the licensed license is used based on the group information. You may determine the effectiveness of.

[Fourth Embodiment]
(Constitution)
Next, a configuration of a license management system for a medical device according to a fourth embodiment of the present invention will be described with reference to FIG. FIG. 12 is a functional block diagram showing a schematic configuration of a license management system for a medical device according to the fourth embodiment of the present invention.

  In the license management system for medical devices according to the fourth embodiment, verification of the identity of a console (device) in a computer system that operates as a slave console has been strengthened. In this embodiment, the subordinate console determines the validity of the licensed license by confirming the existence of the console that has copied the licensed license, and further confirming the identity of the console. For the main console, as in the first embodiment, the validity of the license agreement is determined by confirming the identity of the console.

  In this embodiment, as an example, a case where the scan console 40 is a “main” console (device) and the review console 50 is a “subordinate” console will be described. The differences from the medical device license management system according to the first embodiment are the license duplication unit 41 of the scan console 40, the license validity determination unit 51 of the review console 50, and the device identification information acquisition unit 52. The license duplication unit 41, the license determination unit 51, and the device identification information acquisition unit 52 will be mainly described.

(Acquiring device identification information of secondary console)
The device identification information acquisition unit 52 of the review console 50 acquires device identification information for identifying the review console 50 from the review console 50 itself, and outputs the acquired device identification information to the license validity determination unit 51. As in the first embodiment, since the IP address, the MAC address, and the HDD serial number are used as the device identification information, the device identification information acquisition unit 52 uses the IP address, the MAC address, and the HDD of the review console 50. And the acquired information is output to the license validity determination unit 51 as device identification information.

  Further, the device identification information of the review console 50 acquired by the device identification information acquisition unit 52 is displayed on the display unit 27. A screen displayed on the display means 27 is shown in FIG. As shown in FIG. 13, device identification information (device identification code) is displayed on the display means 27. The operator records the device identification information of the review console 50 displayed on the display means 27. The device identification information of the review console 50 recorded by the operator is used when the license license is copied by the scan console 40.

(Copy of license)
The license copying unit 41 of the scan console 40 creates a copy of the license for use for the software or service selected by the operator. For example, as in the example of the duplication screen shown in FIG. 14, the names of software and services registered in the scan console 40 are displayed on a display device (not shown), are in a selectable state, and are displayed. The operator selects the name of the software or service for which the license agreement is desired to be copied.

  Further, the operator inputs device identification information of a console (device) that is scheduled to install a copy of the license license by an input means (not shown). In this embodiment, the review console 50 is a console (apparatus) scheduled to install a copy of the license agreement. Therefore, the operator inputs the device identification information of the review console 50 using the input means. For example, as in the example of the duplicate screen shown in FIG. 14, an input field for device identification information (device identification code) is provided, and the device identification information of the review console 50 is input to the input field.

  When the software or service is selected and the device identification information of the review console 50 is input, the license acquisition unit 14 sends the license and management information to the license management unit 12 based on the target identification code of the target identification information. Get from.

  The license copying unit 41 receives the license agreement and management information output from the license acquisition unit 14 and creates a copy of the license agreement. At this time, the license copying unit 41 replaces the device identification information included in the copy of the license agreement with the device identification information input previously. That is, the license copying unit 41 replaces the device identification information included in the copy of the license agreement with the device identification information of the console (device) that is scheduled to install the copy of the license agreement. In this embodiment, since the device identification information of the review console 50 is input, the license duplicating unit 41 replaces the device identification information included in the copy of the license license with the device identification information of the review console 50.

  Then, as in the first embodiment, in order to distinguish between the original licensed copy and the copy, the license copy unit 41 increments (increases) the copy number (number of copies) at that time and increases it. The value is the value of the master-slave identification code of the copied license. Further, the license duplicating unit 41 calculates a checksum of the license license and uses the value as checksum information. Then, the license copying unit 41 registers the copy of the license for use license in the license management unit 12 and outputs it to the license output unit 15.

  Similarly to the first embodiment, the license output unit 15 assigns a file name to a copy of the license for license according to a predetermined file name naming rule, and stores it in a designated recording device. For example, the file name is “(License) + (host name of the console that performed the replication) + (generation date (yyyymmddhmmms)). Dat”. In this embodiment, since the console that replicated is the scan console 40, the host name of the scan console 40 constitutes the file name.

(Determining the validity of the license agreement on the secondary console)
Each time the software or service is executed, the license validity determination unit 51 of the review console 50 receives the target identification information of the software or service operating on the review console 50, and the validity of the license for using the software or service is confirmed. Determine. Similarly to the first embodiment, the license validity determination unit 51 confirms the existence of a console (apparatus) that has copied the license for use. Further, the license validity determination unit 51 confirms whether or not the review console 50 is a planned installation destination of a copy of the license license.

  First, as in the first embodiment, the license validity determination unit 51 determines whether the review console 50 operates as a “main” or “subordinate” console (apparatus) when the review console 50 is activated. Confirm. In this embodiment, the review console 50 is set to a “secondary” console. Thereby, the review console 50 determines the validity of the license agreement by confirming the identity of the console and further confirming the existence of the console that has duplicated the license license.

  Next, the license validity determination unit 51 obtains a license for using software or a service operating on the review console 50 from the license management unit 22. Then, as in the first embodiment, the license validity determination unit 51 calculates a checksum, confirms whether or not the licensed license has been tampered with, and the master-slave identification code of the licensed license is other than “0”. Show and confirm that it is a duplicate.

  Further, the duplicating device existence confirmation unit 26 confirms whether or not there is a console (device) to which the license agreement has been duplicated, as in the first embodiment. That is, the license validity determination unit 51 obtains the host name of the copied device (the host name of the scan console 40) from the copied license license file name, and copies the host name to the copy device existence confirmation unit. 26. Similar to the first embodiment, the duplicating apparatus existence confirmation unit 26 confirms whether or not the duplicating console (apparatus) exists based on the host name.

  Furthermore, in this embodiment, the license validity determination unit 51 compares the device identification information included in the license for use with the device identification information of the review console 50 acquired by the device identification information acquisition unit 52, and determines whether the console ( Device).

  Since the copy of the license license includes the device identification information of the installation destination of the copy, the device identification information included in the license license and the device identification information acquired by the device identification information acquisition unit 52 are included. By comparing, it is possible to confirm whether or not a copy of the license agreement is installed on the scheduled console.

  In other words, if the device identification information matches, the review console 50 is the console where the copy is scheduled to be installed, and it means that the copy of the license license has been installed as planned. On the other hand, when the device identification information does not match, the review console 50 means that the copy of the license license is illegally installed, unlike the copy installation planned destination. Therefore, if the device identification information matches, the license validity determination unit 51 determines that the consoles are identical.

  In addition, when the device identification information is configured by a plurality of device information, the console is used when the same number or the same ratio among the plurality of device information is equal to or more than a predetermined number or ratio. It may be determined that there is identity.

  Then, the license validity determination unit 51 confirms that the license (license) is valid when the existence of the console (apparatus) to which the license license is copied and the identity of the console (apparatus) is confirmed. Is determined. On the other hand, if the existence of the console (device) that has copied the license agreement is not confirmed, or the identity of the console (device) is not confirmed, the license validity determination unit 51 determines whether the license agreement is valid. It is determined to be invalid.

  As described above, in the review console 50 that operates as a “slave” console (device), the presence of the duplicated console (device) is confirmed, and further, the identity of the review console 50 is confirmed to be used. It becomes possible to strengthen prevention of unauthorized use of licensed licenses.

  Further, this fourth embodiment may be combined with at least one of the second embodiment or the third embodiment. That is, the validity of the license agreement may be determined using the group information, or the validity of the license agreement may be determined based on the expiration date.

[Fifth Embodiment]
Next, a license management system for a medical device according to a fifth embodiment of the present invention will be described with reference to FIG. FIG. 15 is a functional block diagram showing a schematic configuration of a license management system for a medical device according to the fifth embodiment of the present invention.

  The medical device license management system according to the fifth embodiment updates the license for use when the hardware configuration changes due to component replacement or the like, and the device identification information for identifying the console changes. In this embodiment, as an example, a case where the license update unit 61 is provided in the scan console 60 that operates as a main console will be described. Since the configuration and functions other than the license update unit 61 are the same as those in the first embodiment, description thereof will be omitted.

  The license update unit 61 of the scan console 60 compares the device identification information included in the license agreement with the device identification information acquired by the device identification information acquisition unit 17. If the device information constituting the device identification information is different, the device identification information included in the license is replaced with the device identification information acquired by the device identification information acquisition unit 17. That is, when the hardware configuration changes due to component replacement or the like, the device information changes, so the device information of the device identification information included in the license agreement is replaced with new device information.

  For example, as shown in FIG. 2, if the device identification information includes the volume number of the HDD, the volume number changes when the HDD is replaced. The volume number of the HDD to be configured is replaced with a new volume number. As a result, the device identification information of the license agreement is updated.

  After updating the device identification information, the license update unit 61 calculates the checksum of the license agreement according to the encoding method included in the license agreement, and stores the value in the checksum area. Then, the license update unit 61 registers the updated use license in the license management unit 12.

  In this way, when the device identification information of the license agreement is updated, the validity of the license is subsequently determined based on the updated license license.

  As described above, even when the console device identification information is changed due to console replacement, etc., it is not necessary to issue a new license, and the license can be easily updated. Become. In this way, since the license agreement can be easily updated, the time during which the software or service cannot be used can be reduced.

  Further, the license update unit 61 may update the license for use according to the ratio of the number of devices changed. For example, when the device information constituting the device identification information is changed to a predetermined number or less than a predetermined ratio, the license update unit 61 updates the license for use. On the other hand, if the device information has been changed beyond a predetermined number or a predetermined ratio, the license update unit 61 may wait for a new license to be issued without updating the license license. In other words, if the device information is changed beyond a predetermined number or a predetermined ratio, it is not considered as the same console, and the license is not updated, and a new license is issued. .

  For example, if the device identification information is composed of three pieces of device information, and there is a change in one piece of device information, the license update unit 61 updates the license for use and makes two or more devices. When there is a change in the information, the license update unit 61 does not update the use license. In the example shown in FIG. 2, when one device information is changed among the device identification information composed of three device information of the IP address, the MAC address, and the HDD volume number, the license update unit 61 When the license agreement is updated and two or more pieces of device information are changed, the license update unit 61 waits for a new license agreement without updating the license agreement.

  As described above, if you can consider the same console by updating the license agreement according to the ratio of the number of devices changed, use the software or service without waiting for the license license to be issued. It becomes possible.

  In this embodiment, the scan console 60 that operates as a main console has been described. However, the license update means 61 may be provided in the review console 20 that operates as a subordinate console to update the license agreement. .

  In addition, this fifth embodiment may be combined with at least one of the second to fourth embodiments.

[Sixth Embodiment]
Next, a license management system for a medical device according to a sixth embodiment of the present invention will be described with reference to FIG. FIG. 16 is a functional block diagram showing a schematic configuration of a license management system for a medical device according to the sixth embodiment of the present invention.

  The license management system for a medical device according to the sixth embodiment creates pseudo information for a license for use, and stores the pseudo information and the license for use in a mixed manner. The purpose is to prevent falsification of licenses. In this embodiment, as an example, a case where a pseudo license creating unit 71 is provided in a scan console 70 that operates as a main console will be described. Since the configuration and functions other than the pseudo license creating unit 71 are the same as those in the first embodiment, the description thereof is omitted.

  The pseudo license creation unit 71 of the scan console 70 creates a random value using a random function based on the license license acquired from the license management unit 12 by the license acquisition unit 14. Then, the pseudo license creation unit 71 stores the random value in the license management unit 12 as pseudo information for the license license.

  As described above, by storing the licensed license and the pseudo information in the license management unit 12 for those who intend to illegally analyze the licensed license, the target licensed license is licensed. There is an effect that it is difficult to find from the management means 12. As a result, it is possible to reduce the possibility that the license agreement is tampered with illegally.

  When the license management unit 12 manages the license license as a file, since the license license is managed by the file name, the authorized administrator can use the license license and pseudo information. Can be easily distinguished.

  In this embodiment, the scan console 70 that operates as a main console has been described. However, a pseudo license creation unit is provided in the review console 20 that operates as a slave console, and the license registration unit 21 of the review console 20 includes The license agreement and pseudo information may be mixed and stored.

  Further, this sixth embodiment may be combined with at least one of the second to fifth embodiments.

[Seventh Embodiment]
next. A medical device license management system according to a seventh embodiment of the present invention will be described with reference to FIG. FIG. 17 is a functional block diagram showing a schematic configuration of a license management system for a medical device according to the seventh embodiment of the present invention.

  The license management system for a medical device according to the seventh embodiment uses a license after a certain period of time has elapsed when the hardware configuration changes due to part replacement or the like, and the device identification information for identifying the console changes. Update the device identification information of the license. In this embodiment, as an example, a case will be described in which a scan console 80 operating as a main console is provided with apparatus identity determination means 81, history management means 82, period management means 83, and license update means 84. Since the configuration and functions other than the device identity determination unit 81, the history management unit 82, the period management unit 83, and the license update unit 84 are the same as those in the first embodiment, description thereof will be omitted.

  The device identity determination unit 81 receives the use license from the license acquisition unit 14 and further receives the device identification information of the scan console 80 from the device identification information acquisition unit 17, and the device identification information included in the use license license, The device identification information acquired by the device identification information acquisition means 17 is compared to determine the console identity. If the device information constituting the device identification information matches, it means that the device constituting the scan console 80 has not changed, and if the device information does not match, the device has changed.

  For example, when the device identification information is composed of a plurality of device information, and device information equal to or greater than a predetermined number or a predetermined ratio matches, the device identity determination unit 81 determines that the consoles are the same. judge. For example, when device information of 50% or more matches, the apparatus identity determination unit 81 determines that the consoles are the same. On the other hand, if the percentage of matching device information is less than 50%, the device identity determination unit 81 determines that the consoles are not the same.

  When the device information constituting the device identification information matches a predetermined number or a predetermined proportion of device information, the device identity determination unit 81 determines to update the device identification information of the license license. . This is because the console can be regarded as the same, and the license for use is updated.

  The device identity determination unit 81 records the history of device identity determination in the history management unit 82. This determination history includes the date and time when the device identity was determined and the device information that did not match. Further, when the license for use is updated, the fact that it is updated is included.

  The period management unit 83 refers to the history information recorded in the history management unit 82, and determines that the identity of the device is to be determined when the history information includes an update of the license for use. After a predetermined period of time elapses from that date, an update instruction for the device identification information of the license license is output to the license update means 84. This update command includes device information that did not match. For example, the period management unit 83 outputs an update command to the license update unit 84 60 days after the date of determination of device identity.

  Upon receiving the update command from the period management unit 83, the license update unit 84 replaces the device identification information (device information) included in the license agreement with the replaced device information. Then, the license agreement with the updated device identification information is stored in the license management means 12. As a result, the license agreement is updated.

  Then, the license validity determination unit 16 determines the validity of the license of the software or service based on the updated use license.

  As described above, even if the device is replaced, if the console can be regarded as the same, the device identification information (device information) of the license is replaced with the device information after the replacement, and the license is updated. This makes it possible to use software and services without waiting for the issuance of a license for use.

  Next, a specific example of updating the device identification information will be described with reference to FIG. FIG. 18 is a diagram illustrating the update timing of the device identification information.

  For example, on the 0th day (first), the device A, the device B, the device C, and the device D are installed in the scan console 80, and the device identification information is changed to the devices A, B, C, and D. A case in which the device information is configured will be described. Here, the information indicating the device A is “device information A”, the information indicating the device B is “device information B”, the information indicating the device C is “device information C”, and the information indicating the device D is “device information”. Information D ”.

  On the 0th day, the device identification information acquired by the device identification information acquisition means 17 is composed of device information A, device information B, device information C, and device information D. On the other hand, the device identification information included in the license agreement is also composed of device information A, B, C, and D.

  On the 30th day, when the device A is replaced with the device X and the device B is replaced with the device Y, the device identification information acquired by the device identification information acquisition unit 17 is the device information X, Y, C, and D. It will consist of That is, when the device A and the device B are exchanged, the device identification information of the scan console 80 is changed.

  The device identity determination unit 81 receives the license for license from the license acquisition unit 14 and receives the current (30th day) device identification information acquired by the device identification information acquisition unit 17 and compares the device identification information. By doing so, the identity of the console is determined. In this example, since device A is exchanged for device X and device B is exchanged for device Y, the two pieces of device information are different. In this case, since the device information of 2/4 (50%) matches, the device identity determination unit 81 determines that the consoles are the same, and further determines to update the device identification information of the license license. To do.

  The device identity determination unit 81 records the history of device identity determination in the history management unit 82. This determination history includes the date when the device was replaced (the date when the device identity was determined), the device information that did not match, and the fact that the license agreement was updated. In the example shown in FIG. 12, device information X and Y are included in the history as device information that did not match.

  Then, the period management unit 83 manages the time with reference to the history management unit 82, replaces the device information A with the device information X after a predetermined period from the date when the devices A and B are exchanged, A command (update command) for replacing the information B with the device information Y is output to the license update unit 84. In the example shown in FIG. 18, the update command is output on the 90th day after 60 days.

  In accordance with the update command output from the period management unit 83, the license update unit 84 replaces the device information constituting the device identification information of the license license with the replaced device information. In other words, after a predetermined period of time has passed since the device was replaced, the device identification information of the license for license is replaced with the device information after the replacement. In the example illustrated in FIG. 18, since a predetermined period (60 days) has elapsed since the device X and the device Y are replaced, the device information A and the device information B included in the device identification information of the license for use are changed to the device. Replace with information X and device information Y. Thereby, the device identification information of the updated license license is composed of device information X, Y, C, and D. Then, the license update unit 84 stores the updated use license in the license management unit 12.

  Then, the license validity determination unit 16 of the scan console 80 determines the validity of the software or service license based on the updated license agreement.

  In this example, the device C is replaced with the device Z on the 90th day. In this case, the device identification information acquired by the device identification information acquisition means 17 is composed of device information X, Y, Z, and D. Then, the device identity determination unit 81 compares the device identification information of the updated license and the device identification information acquired by the device identification information acquisition unit 17 to determine console identity. In this case, since the device C is replaced with the device Z, one device information is different. In this case, since the device information of 3/4 (75%) matches, the device identity determination means 81 determines that the consoles are the same, and further updates the device identification information of the license license. To decide.

  The device identity determination unit 81 records the history of device identity determination in the history management unit 82. In the example shown in FIG. 18, device information Z is included in the history as device information that does not match.

  Further, the device D is replaced with the device W on the 120th day after 30 days. In this case, the device identification information acquired by the device identification information acquisition means 17 is composed of device information X, Y, Z, and W. Then, the device identity determination unit 81 includes the device identification information (device information X, Y, C, and D) of the license for use and the device identification information (device information X, Y, Z and W) to determine console identity. In this case, since the device C is replaced with the device Z on the 90th day and the device D is replaced with the device W on the 120th day, the two pieces of device information are different. In this case, since the device information of 2/4 (50%) matches, the device identity determination means 81 determines that the consoles are the same, and further updates the device identification information of the license license. To decide.

  The device identity determination unit 81 records the history of device identity determination in the history management unit 82. In the example shown in FIG. 18, device information W is included in the history as device information that does not match.

  Then, the period management unit 83 manages the time with reference to the history management unit 82, and after the predetermined period has elapsed from the date when the device C is replaced with the device Z (after 60 days), the device information C is stored in the device information C. A command (update command) to be replaced with information Z is output to the license update unit 84.

  The license update unit 84 replaces the device information C included in the device identification information of the license agreement with the device information Z in accordance with the update command output from the period management unit 83. As a result, the device identification information of the updated license license is composed of device information X, Y, Z, and D. Then, the license update unit 84 stores the updated use license in the license management unit 12.

  Then, the license validity determination unit 16 determines the validity of the license of the software or service based on the updated use license.

  Furthermore, after a predetermined period has elapsed from the date when the device D is replaced with the device W (after 60 days have elapsed), the period management unit 83 outputs an update command to the license update unit 84. The license update unit 84 replaces the device information D included in the device identification information of the license agreement with the device information Z. As a result, the device identification information of the updated license license becomes device information X, Y, Z, and W. Then, the license validity determination unit 16 determines the validity of the license of the software or service based on the updated use license.

  As described above, when devices are gradually replaced and the console can be regarded as the same, by updating the license, you can continue to use the software and services without waiting for the license to be issued It becomes possible.

  In this embodiment, the scan console 80 that operates as the main console has been described. However, the device identity determination unit 81, the history management unit 82, the period management unit 83, and the license are added to the review console 20 that operates as the slave console. An update means 84 may be provided to update the use license.

  Further, this seventh embodiment may be combined with at least one of the second to fourth or sixth embodiments.

It is a functional block diagram which shows schematic structure of the license management system of the medical device which concerns on 1st Embodiment of this invention. It is a figure which shows an example of the structure of a use permission license. It is a figure which shows one example of an encoding system and a system number. It is an example of the bit representation of object identification information. It is a figure which shows an example of the registration screen of a use permission license. It is a figure which shows an example of the screen at the time of duplicating a use license. It is a figure which shows the original and duplication of a use license. It is a flowchart which shows a series of operation | movement by the license management system of the medical device which concerns on 1st Embodiment of this invention. It is a flowchart which shows a series of operation | movement by the license management system of the medical device which concerns on 1st Embodiment of this invention. It is a flowchart which shows a series of operation | movement by the license management system of the medical device which concerns on 1st Embodiment of this invention. It is a functional block diagram which shows schematic structure of the license management system of the medical device which concerns on 3rd Embodiment of this invention. It is a functional block diagram which shows schematic structure of the license management system of the medical device which concerns on 4th Embodiment of this invention. It is a figure which shows an example of the screen which displays apparatus identification information. It is a figure which shows an example of the screen at the time of duplicating a use license. It is a functional block diagram which shows schematic structure of the license management system of the medical device which concerns on 5th Embodiment of this invention. It is a functional block diagram which shows schematic structure of the license management system of the medical device which concerns on 6th Embodiment of this invention. It is a functional block diagram which shows schematic structure of the license management system of the medical device which concerns on 7th Embodiment of this invention. It is a figure which shows the update timing of apparatus identification information. 1 is a diagram illustrating an X-ray CT apparatus as an example of a medical image diagnostic apparatus.

Explanation of symbols

10, 30, 40, 60, 70, 80 Scan console 11, 21 License registration means 12, 22 License management means 13, 41 License duplication means 14, 23 License acquisition means 15 License output means 16, 24, 31, 51 License valid Sex determination means 17, 52 Device identification information acquisition means 18, 25 Control means 19 Reply means 20, 50 Review console 26 Duplicate device existence confirmation means 27 Display means 32, 82 History management means 33 History search means 61, 84 License update means 71 Pseudo license creation means 81 Device identity determination means 83 Period management means

Claims (12)

A first medical device having a first execution unit for executing a functional tool represented by predetermined software or a predetermined service; and a second execution unit having a second execution unit for executing the same functional tool as the functional tool. 2 is a license management system for medical devices connected via a network,
The first medical device is:
First management means including device identification information for identifying a medical device permitted to execute the functional tool, and managing a license for executing the functional tool;
Each time the first execution unit executes the functional tool, device identification information for identifying the first medical device, and device identification information of a license license managed by the first management unit And a first license validity determination unit that permits the first execution unit to execute the functional tool targeted by the license.
License duplicating means for duplicating a license license managed by the first management means and adding specific information for identifying the first medical device on the network to the duplicated license license. When,
Have
The second medical device is:
A second management means for managing the copied license license;
Each time the second execution means executes the function tool, the second execution means on the network is based on the specific information added to the copied license license managed by the second management means. A second license validity determining unit that checks whether or not one medical device exists and, if present, permits the second execution unit to execute the functional tool;
A license management system for medical equipment, comprising: A medical image diagnostic apparatus for acquiring a medical image of a subject;
A first medical device that includes a first execution unit that executes a function tool represented by predetermined software or a predetermined service, and controls the medical image diagnostic apparatus;
A second execution means for executing the same function tool as the function tool is provided, and is connected via a network to a second medical device that performs image processing on a medical image acquired by the medical image diagnostic apparatus A medical device license management system that provides and manages a license for executing the functional tool for a medical system that functions as a set,
The first medical device is:
First management means including device identification information for identifying a medical device permitted to execute the functional tool, and managing a license for executing the functional tool;
Each time the first execution unit executes the functional tool, device identification information for identifying the first medical device, and device identification information of a license license managed by the first management unit And a first license validity determination unit that permits the first execution unit to execute the functional tool targeted by the license.
License duplicating means for duplicating a license license managed by the first management means and adding specific information for identifying the first medical device on the network to the duplicated license license. When,
Have
The second medical device is:
A second management means for managing the copied license license;
Each time the second execution means executes the functional tool, the second execution means on the network is based on the specific information added to the copied license license managed by the second execution means. A second license validity determining unit that checks whether or not one medical device exists and, if present, permits the second execution unit to execute the functional tool;
A license management system for medical equipment, comprising: The device identification information included in the license agreement includes device information for identifying a device constituting a medical device that is permitted to execute the functional tool,
The device identification information for identifying the first medical device includes device information for identifying a device constituting the first medical device,
Each time the first execution unit executes the functional tool, the first license validity determination unit includes the device information of the license license managed by the first management unit, and the first license unit. The device according to claim 1 or 2, wherein the first execution means is permitted to execute the functional tool targeted by the license for use when the device information of the medical device matches at a predetermined ratio or more. The license management system for medical equipment according to claim 2. The license agreement further includes group information for identifying the type of functional tool,
Each time the first execution unit executes the functional tool, the first license validity determination unit determines that the type of the functional tool is the license license managed by the first management unit. The medical device license according to any one of claims 1 to 3, wherein the first execution means is allowed to execute the function tool when the group information included in the group information matches the type indicated by the group information. Management system. The license agreement further includes license period information indicating a time limit for using the functional tool,
Each time the first execution unit executes the functional tool, the first license validity determination unit determines that the system time of the first medical device exceeds the time limit indicated by the license period information. 5. The medical device license management system according to claim 1, wherein execution of the functional tool is not permitted. The first medical device is:
A history management unit that records the date and time when the first license validity determination unit determines the execution permission of the functional tool as history information;
Each time the first execution unit executes the functional tool, the first license validity determination unit determines that the system time of the first medical device is earlier than the date and time recorded in the history management unit. 6. The medical device license management system according to claim 1, wherein execution of the functional tool is not permitted when the date and time are The license duplicating means duplicates the licensed license, adds specific information for identifying the first medical device to the duplicate, and further introduces the duplicated licensed medical device. Receiving the device identification information for identifying the device identification information, replacing the device identification information included in the copied license agreement with the received device identification information,
Each time the second execution unit executes the functional tool, the second license validity determination unit checks whether or not the first medical device exists, and further determines the second medical device. Based on the device identification information for identification and the device identification information included in the copied license license managed by the second management unit, the second execution unit executes the function tool. The medical device license management system according to any one of claims 1 to 6, wherein the license management system is permitted. The first medical device is:
2. The apparatus according to claim 1, further comprising license update means for replacing the device identification information included in the license for use managed by the first management means with the device identification information of the first medical device. The license management system for a medical device according to claim 7. The first medical device is:
Identity determining means for comparing the device identification information of the license license managed by the first management means with the device identification information of the first medical device to determine the identity of the device identification information. In addition,
If the device identification information is not identical, the license update unit is managed by the first management unit after a predetermined period from when the device identification information of the first medical device is changed. 9. The medical device license management system according to claim 8, wherein the device identification information of the license is replaced with the device identification information of the first medical device after the change. The first medical device is:
Further comprising pseudo license creating means for creating pseudo information based on the license agreement managed by the first management means;
10. The medical device license management system according to claim 1, wherein the first management unit manages the pseudo information together with the license agreement. A medical device that is connected to another medical device via a network and includes execution means for executing a function tool represented by predetermined software or a predetermined service,
Management means for managing a license for executing the functional tool, to which specific information for specifying the other medical device on the network is added;
Each time the execution means executes the functional tool, it checks the presence or absence of the other medical device on the network based on the specific information added to the license, and if it exists, A license validity determination unit that permits the execution unit to execute the function tool;
A medical device characterized by comprising: A first medical device having a first execution unit for executing a functional tool represented by predetermined software or a predetermined service; and a second execution unit having a second execution unit for executing the same functional tool as the functional tool. A medical device license management method for a system connected via a network,
In the first medical device,
A first registration step that includes device identification information for identifying a medical device permitted to execute the functional tool, and registers a license for executing the functional tool in the first medical device;
Each time the first execution means executes the functional tool, based on the device identification information for identifying the first medical device and the device identification information of the registered license, A first license validity determination step for allowing the first execution means to execute the functional tool targeted by the license for use;
A license duplication step of duplicating the registered license, and adding specific information for identifying the first medical device on the network to the duplicated license;
And
In the second medical device,
A second registration step of registering the duplicated license license in the second medical device;
Each time the second execution means executes the functional tool, the presence or absence of the first medical device on the network is confirmed based on the specific information added to the copied license license. A second license validity determination step for allowing the second execution means to execute the function tool, if any,
A license management method for a medical device.