TECHNICAL FIELD
-
Various examples generally relate to the field of elevator systems. In particular, some examples relate to a solution for handling elevator maintenance licenses.
BACKGROUND
-
Elevator maintenance may be performed with an elevator maintenance device that requires a valid maintenance license. Without a valid maintenance license, the elevator maintenance device cannot perform any maintenance operations associated with elevators.
-
A problem may occur, for example, when a technician leaves a company performing elevator maintenance, and if the technician uses a company owned device having a valid maintenance license, the device may not be returned back at all. Such a license or maintenance device can still be misused to carry out maintenance activities, for example, configuration changes to elevators.
SUMMARY
-
The scope of protection sought for various example embodiments of the disclosure is set out by the independent claims. The example embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various example embodiments of the disclosure.
-
According to a first aspect, there is provided an elevator system device. The elevator system device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the elevator system device to at least perform: receiving, from a network device, hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; storing the hash information; receiving a connection request from an elevator maintenance device, the connection request comprising license information; generating license hash information based on the license information in the connection request; comparing the generated license hash information with the stored hash information; and determining whether to accept the connection request based on the comparison.
-
In an implementation form of the first aspect, the at least one memory stores instructions that, when executed by the at least one processor, cause the elevator system device to at least perform: accepting the connection request if the comparison indicates that the license hash information is not found in the hash information associated with the at least one disabled.
-
In an implementation form of the first aspect, the at least one memory stores instructions that, when executed by the at least one processor, cause the elevator system device to at least perform: rejecting the connection request if the comparison indicates that the license hash information is found in the hash information associated with the at least one disabled license.
-
In an implementation form of the first aspect, the at least one memory stores instructions that, when executed by the at least one processor, cause the elevator system device to at least perform: generating log information associated with the rejection; and transmitting the log information to the network device.
-
According to a second aspect, there is provided a network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least perform: storing hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; and transmitting the hash information to one or more elevator sites comprising the elevators.
-
According to a third aspect, there is provided an elevator system comprising an elevator system device according to the first aspect and a network device according to the second aspect.
-
According to a fourth aspect, there is provided a method comprising: receiving, from the network device, hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; storing the hash information; receiving a connection request from an elevator maintenance device, the connection request comprising license information; generating license hash information based on the license information in the connection request; comparing the generated license hash information with the stored hash information;; and determining whether to accept the connection request based on the comparison.
-
In an implementation form of the fourth aspect, the method further comprises accepting the connection request if the comparison indicates that the license hash information is not found in the hash information associated with the at least one disabled.
-
In an implementation form of the fourth aspect, the method further comprises rejecting the connection request if the comparison indicates that the license hash information is found in the hash information associated with the at least one disabled license.
-
In an implementation form of the fourth aspect, the method further comprises generating log information associated with the rejection; and transmitting the log information to the network device.
-
According to a fifth aspect, there is provided a method comprising: storing hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; and transmitting the hash information to one or more elevator sites comprising the elevators.
-
According to a sixth aspect, there is provided a computer program comprising instructions which, when the program is executed by at least one processor, cause the least one processor to perform the method of the fourth or fifth aspect.
-
According to a seventh aspect, there is provided a computer-readable medium comprising a computer program comprising instructions which, when the program is executed by at least one processor, cause the at least one processor to perform the method of the fourth or fifth aspect.
-
According to an eighth aspect, there is provided a network device comprising means for: receiving, from the network device, hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; storing the hash information; receiving a connection request from an elevator maintenance device, the connection request comprising license information; generating license hash information based on the license information in the connection request; comparing the generated license hash information with the stored hash information; and determining whether to accept the connection request based on the comparison.
-
According to a ninth aspect, there is provided a network device comprising means for: storing hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; and transmitting the hash information to one or more elevator sites comprising the elevators.
BRIEF DESCRIPTION OF THE DRAWINGS
-
The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate examples of the invention and together with the description help to explain the principles of the invention. In the drawings:
- FIG. 1 illustrates a flow diagram of a method for handling elevator maintenance licenses according to an example embodiment.
- FIG. 2A illustrates a flow diagram of a method for handling elevator maintenance licenses according to an example embodiment.
- FIG. 2B illustrates a flow diagram of a method for handling elevator maintenance licenses according to an example embodiment.
- FIG. 3 illustrates a block diagram of an elevator system device according to an example embodiment.
- FIG. 4 illustrates a block diagram of a network device according to an example embodiment.
- FIG. 5 illustrates a signaling diagram of a system according to an example embodiment.
DETAILED DESCRIPTION
-
Various examples and embodiments discussed below illustrate a solution which enables the detection of a misuse of an elevator maintenance device even in a case where the elevator maintenance device has a valid license but its user is not allowed to use the elevator maintenance device any more.
-
FIG. 1 illustrates a flow diagram of a method for handling elevator maintenance licenses according to an example embodiment. The method may be implemented by a network node, for example, a cloud node.
-
At 100, hash information associated with at least one disabled license may be stored by a network device. A license allows to carry out one or more maintenance activities associated with elevators with a maintenance device or tool. License information relating to disabled licenses may be received, for example, from a management node that collects data relating to stolen or non-returned maintenance devices or tools or employees who have left a company and who were using a maintenance license. Based on the license information received from the maintenance node, the network device may mark them as disabled. The license information received from the management node may comprise full license information or one or more parts of it, and the hash information may be generated for each disabled license based on the license information. In another example, the license information may comprise the hash information. In another example, the management node may provide identification information that identifies one or more employees who have used elevator maintenance licenses. Based on the identification information, the network device may identify licenses used by the employees and mark them as disabled. In an example embodiment, the hash information may refer to an array of hashes generated based on the license information using known hash generation techniques. Further, the term "hash information" may refer to any piece of information that has been generated based on license information or one or more parts of the license information.
-
At 102, the hash information may be transmitted to one or more elevator sites comprising elevators. Each elevator site may comprise one or more elevators for which maintenance operations may be performed using various maintenance devices or tools. When the elevator sites have updated hash information relating to disabled licenses available, they are able to prohibit the use of stolen or non-returned maintenance devices or tools having disabled licenses or other tools using the disabled licenses.
-
FIG. 2A illustrates a flow diagram of a method for handling elevator maintenance licenses according to an example embodiment. The method may be implemented by an elevator system device, for example, an elevator controller.
-
At 200, hash information associated with at least one disabled license may be received from a network device, for example, a cloud node. A license allows to carry out maintenance activities associated with elevators. In an example embodiment, the hash information may refer to an array of hashes generated based on the license information using known hash generation techniques. Further, the term "hash information" may refer to any piece of information that has been generated based on license information or one or more parts of the license information.
-
At 202, the hash information may be stored, for example, in a memory, for example, a secure non-volatile storage.
-
At 204, a connection request may be received from an elevator maintenance device, the connection request comprising license information.
-
At 206, license hash information may be generated based on the license information in the connection request. The hash generation may be performed using known hash generation techniques.
-
At 208, the generated license hash information may be compared with the stored hash information. The stored hash information may comprise a hash array of disabled licenses, and it is determined whether the hash array includes the generated license hash information.
-
At 210, it may be determined whether to accept the connection request based on the comparison.
-
FIG. 2B illustrates a flow diagram of a method for handling elevator maintenance licenses according to an example embodiment. The method may be implemented by an elevator system device, for example, an elevator controller.
-
At 200, hash information associated with at least one disabled license may be received from a network device, for example, a cloud node. A license allows to carry out maintenance activities associated with elevators. In an example embodiment, the hash information may refer to an array of hashes generated based on the license information using known hash generation techniques. Further, the term "hash information" may refer to any piece of information that has been generated based on license information or one or more parts of the license information.
-
At 202, the hash information may be stored, for example, in a memory, for example, a secure non-volatile storage.
-
At 204, a connection request may be received from an elevator maintenance device, the connection request comprising license information.
-
At 206, license hash information may be generated based on the license information in the connection request. The hash generation may be performed using known hash generation techniques.
-
At 208, the generated license hash information may be compared with the stored hash information. The stored hash information may comprise a hash array of disabled licenses, and it is determined whether the hash array includes the generated license hash information.
-
At 212, it may be determined whether a match is found between the stored hash information and generated license hash information.
-
At 214, if a match is not found, the connection request may be accepted. After allowing the connection request, maintenance operations may be performed using a maintenance device or tool using the license.
-
At 216, if a match is found, the connection request may be rejected. This means that the connection request originated from a maintenance device or tool having a disabled license.
-
At 218, log information associated with the rejection may be generated. The log information may identify, for example, the maintenance device or tool from which the connection request originated, a user using the maintenance device or tool and/or the license.
-
At 220, the log information may be transmitted, for example, to the network device.
-
FIG. 3 illustrates a block diagram of a network device 300 according to an example solution. The network device 300 may comprise, for example, a cloud-based device.
-
The network device 300 comprises one or more processors 302, and one or more memories 304 that comprise computer program code 306, and/or a communication interface 308 for wired and/or wireless communication. Although the network device 300 is depicted to include only one processor 302, the network device 300 may include more than one processor. In an example embodiment, the memory 304 is capable of storing instructions, such as an operating system and/or various applications.
-
Furthermore, the processor 302 is capable of executing the stored instructions. In an example embodiment, the processor 302 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the processor 302 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In an example embodiment, the processor 302 may be configured to execute hard-coded functionality. In an example embodiment, the processor 302 may be embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 302 to perform the algorithms and/or operations described herein when the instructions are executed, for example, the steps discussed relating to any of FIG. 1.
-
The memory 304 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory 304 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).
-
The at least one memory 304 may store program instructions that, when executed by the at least one processor 302, cause the network device 300 to perform the functionality of the various embodiments discussed herein. Further, in an embodiment, at least one of the processor 302 and the memory 304 may constitute means for implementing the discussed functionality. For example, the network device 300 may be configured to store hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators, and transmit the hash information to one or more elevator sites comprising the elevators.
-
A computer program may comprise instructions which, when the program is executed by the at least one processor 302, cause the network device 300 to perform any of the methods described above. Furthermore, a computer-readable medium may comprise the computer program.
-
FIG. 4 illustrates a block diagram of an elevator system device 400 according to an example solution. The elevator system device 400 may comprise, for example, an elevator controller or an elevator group controller.
-
The elevator system device 400 comprises one or more processors 402, and one or more memories 404 that comprise computer program code 406, and/or a communication interface 408 for wired and/or wireless communication. Although the elevator system device 400 is depicted to include only one processor 402, the elevator system device 400 may include more than one processor. In an example embodiment, the memory 404 is capable of storing instructions, such as an operating system and/or various applications.
-
Furthermore, the processor 402 is capable of executing the stored instructions. In an example embodiment, the processor 402 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the processor 402 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In an example embodiment, the processor 402 may be configured to execute hard-coded functionality. In an example embodiment, the processor 402 may be embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 402 to perform the algorithms and/or operations described herein when the instructions are executed, for example, the steps discussed relating to any of FIG. 2A and/or 2B.
-
The memory 404 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory 404 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).
-
The at least one memory 404 may store program instructions that, when executed by the at least one processor 402, cause the elevator system device 400 to perform the functionality of the various embodiments discussed herein. Further, in an embodiment, at least one of the processor 402 and the memory 404 may constitute means for implementing the discussed functionality. For example, the elevator system device 400 may be configured to receive, from a network device, hash information associated with at least one disabled license, a license allowing to carry out one or more maintenance activities associated with elevators; store the hash information; receive a connection request from an elevator maintenance device, the connection request comprising license information; generate license hash information based on the license information in the connection request; compare the generated license hash information with the stored hash information; and determine whether to accept the connection request based on the comparison.
-
A computer program may comprise instructions which, when the program is executed by the at least one processor 402, cause the network device 400 to perform any of the methods described above. Furthermore, a computer-readable medium may comprise the computer program.
-
FIG. 5 illustrates a signaling diagram of a system according to an example embodiment.
-
The system comprises a user device 500, for example, a smart phone, a laptop computer or a tablet computer that is used to perform one or more maintenance operations relating to one or more elevators 502, 504, 506. The system may also comprise a management node 510 that may be configured to maintain data relating to user devices, including the user device 500. The maintained data may comprise, for example, a serial number of the user devices and information identifying maintenance licenses. When an employee leaves a company or when a user device is lost or is not returned back to a company when an employee leaves the company, the user device and/or its associated license can be marked as "disabled" or "blacklisted". The management node 510 may then send identifying information 528 to a cloud node 508. The identifying information 528 may comprise complete license information relating to the disabled licenses or partial information relating to the disabled licenses. In another example, the identifying information 528 may comprise hash information associated with the disabled licenses. In another example, the hash information may refer to an array of hashes generated based on the disabled licenses using known hash generation techniques. In another example embodiment, the management node 510 may send as identifying information 528 information that identifies an employee or employees that left the company.
-
The cloud node 508 may be configured to receive the identifying information 528 from the management node 510. If the identifying information comprises license information and does not yet comprise hashed information, the cloud node 508 may be configured to generate the hash information based on the license information and store the hash information. On the other hand, the identifying information 528 received from the management node 510 may comprise information that identifies an employee or employees that have left the company. The identifying information may comprise, for example, the name of the employee or an employee identifier. The cloud node 508 may store an association between employees and licenses used by the employees. Based on this association the cloud node 508 is able to mark licenses relating to the identified employees as disabled, and generate and store the hash information relating to the disabled licenses.
-
The cloud node 508 may be configured to transmit 512, 514, 516 the hash information to one or more elevator sites comprising the elevators 502, 504, 506. Each elevator site may comprise one or more elevators for which maintenance operations may be performed using various maintenance devices or tools. The elevators 502, 504, 506 or their controllers are configured to store the received information to memory, for example, a secure non-volatile storage.
-
At 518, the user device 500 may be configured to transmit a connection request 518 to the elevator 506 for which maintenance operations are required to be performed. The connection request may comprise license information for performing the maintenance operations. After receiving the license information, the elevator 506 (or the elevator controller) may be configured to generate license hash information based on the license information in the connection request.
-
At 520, the elevator 506 may be configured to determine whether a match is found between generated license hash information and the stored hash information, i.e. to determine whether the license is disabled or not. If a match is not found (i.e., the license is not a disabled license), the connection request may be accepted at 526. After allowing the connection request, maintenance operations may be performed using the maintenance device or tool. However, if a match is found (i.e., the license is a disabled license), the connection request may be rejected at 522. This means that the connection request originates from a user device 500 using a disabled license that is not allowed to perform maintenance operations any more.
-
At 524, log information associated with the rejection may be generated and transmitted to the cloud node 508. The log information may identify, for example, the user device 500 from which the connection request originated and/or the license information.
-
One or more of the examples and example embodiments discussed above may enable a solution for preventing the performance of maintenance operations to target elevators using stolen or lost valid licenses. Further, one or more of the examples and example embodiments discussed above may enable a solution for efficient disabled license handling. As each license may have a limited validity time, for example, two weeks, it is only necessary to maintain hash information relating disabled/blacklisted licenses for at most the validity time, for example, two weeks.
-
The examples discussed above may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The example devices can store information relating to various methods described herein. This information can be stored in one or more memories, such as a hard disk, a solid state drive (SSD), an optical disk, a magneto-optical disk, an R_AM, and the like. One or more databases can store the information used to implement the examples. The databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein. The methods described with respect to the examples can include appropriate data structures for storing data collected and/or generated by the methods of the devices and subsystems of the examples in one or more databases.
-
The components of the examples may include computer readable medium or memories for holding instructions programmed according to the teachings and for holding data structures, tables, records, and/or other data described herein. In an example, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer-readable medium may include a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution. Such a medium can take many forms, including but not limited to, non-volatile media, volatile media, transmission media, and the like.
-
While there have been shown and described and pointed out fundamental novel features as applied to preferred examples thereof, it will be understood that various omissions and substitutions and changes in the form and details of the devices and methods described may be made by those skilled in the art without departing from the spirit of the disclosure. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the disclosure. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or example may be incorporated in any other disclosed or described or suggested form as a general matter of design choice. Furthermore, in the claims means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.
-
The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the present specification as a whole, in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims. The applicant indicates that the disclosed aspects/embodiments may consist of any such individual feature or combination of features. In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the disclosure.