EP3904268B1 - Elevator control system - Google Patents
Elevator control system Download PDFInfo
- Publication number
- EP3904268B1 EP3904268B1 EP21180578.3A EP21180578A EP3904268B1 EP 3904268 B1 EP3904268 B1 EP 3904268B1 EP 21180578 A EP21180578 A EP 21180578A EP 3904268 B1 EP3904268 B1 EP 3904268B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- elevator
- communication device
- escalator
- cloud server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000004891 communication Methods 0.000 claims description 89
- 238000000034 method Methods 0.000 claims description 15
- 238000001914 filtration Methods 0.000 claims 2
- 230000010267 cellular communication Effects 0.000 claims 1
- 230000006870 function Effects 0.000 description 14
- 230000001413 cellular effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B1/00—Control systems of elevators in general
- B66B1/34—Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
- B66B1/3415—Control system configuration and the data transmission or communication within the control system
- B66B1/3423—Control system configuration, i.e. lay-out
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B1/00—Control systems of elevators in general
- B66B1/34—Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
- B66B1/3415—Control system configuration and the data transmission or communication within the control system
- B66B1/3446—Data transmission or communication within the control system
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B25/00—Control of escalators or moving walkways
Definitions
- the present invention relates to the field of elevator and escalator devices. More specifically, it relates to a communication device, a method and a system for communicating between a core controller associated with an elevator or escalator device and a cloud server.
- control software is stored and operated locally on a control board at each instance or installation. Adding or modifying functionality requires service personnel to manually update the software on the control board or download the software to a local unit via a remote connection.
- a software upgrade may require a corresponding processor and memory upgrade.
- Controller software might not be automatically upgraded unless manually executed at a user's request. Future functionality may someday reach the memory and computing power resource limitations in the existing control boards. At that point, a user may have to elect to forego incorporating additional functionality or otherwise incur large expenses upgrading a supporting hardware platform.
- US 9067760 B2 describes a method for communication between an elevator system and a remote control center, that includes establishing a communication connection in a communication network.
- a first signal of the elevator system is received by a communication device of the elevator system through a signal network, and a second signal is transmitted by the communication device in the communication network to a computing apparatus of the remote control center.
- the communication connection is permanently maintained.
- JP 2014 172714 A discloses an elevator system with certain control functionalities that are implemented in a cloud computing system.
- Such improvements shall in particular concern integrity of the systems communication devices as well as security of data that is communicated between the different communication entities of the system.
- the invention is directed to a method according to claim 1.
- the invention is directed to a communication device with at least one microprocessor; at least one cryptoprocessor; and memory having instructions stored thereon that, when executed by the at least one microprocessor and the at least one cryptoprocessor, cause the communication device to at least one of: receive from a cloud server or a backend computer encrypted data that is configured to at least control core operations associated with an elevator or escalator device, decrypt the data, and distribute the data over at least one data connection between the communication device and at least one core controller associated with an elevator or escalator device to said at least one core controller to be used by said controller to control core operations associated with said elevator or escalator device, or receive control feedback data over at least one data connection between the communication device and at least one core controller associated with an elevator or escalator device to said at least one core controller, encrypt the data, and send the encrypted data to a cloud server or a backend computer.
- a third aspect of the invention is directed to a system comprising: a first plurality of elevator or escalator devices; at least one core controller configured to control operations associated with the first plurality of elevator or escalator devices; a cloud server; and a first communication device linked to the at least one first core controller.
- Encrypting the data which is communicated between the communication devices allows to maintain the security level obtained with conventionally controlled elevator and escalator devices even when control over non-core functionalities are moved or relocated to remote devices or into the cloud in general.
- connections are set forth between elements in the following description and in the drawings (the contents of which are included in this disclosure by way of reference). It is noted that these connections in general and, unless specified otherwise, may be direct or indirect and that this specification is not intended to be limiting in this respect. In this respect, a coupling between entities may refer to either a direct or an indirect connection. Some connections are marked with an open or closed lock symbol, exemplarily indicating that information and data transported over these connections is encrypted (locked) or unencrypted (open).
- Exemplary embodiments of apparatuses, systems, and methods are described for maintaining, updating/modifying, and upgrading an elevator system.
- functionality typically associated with an elevator controller may be located in another device or entity, such as a smart communication gateway or on a cloud server.
- the elevator controller may communicate with the smart communication gateway and the cloud server to support selected control functions.
- cloud or cloud computing shall in this specification have the meaning of internet-based computing that provides shared computer processing resources and data to computers and other devices on demand.
- a cloud server is a computer device (server) that is connected to and can be contacted over the internet or any other comparable dedicated or open communication network.
- Fig 1 shows an exemplary elevator system comprising several elevators 31 through 36 grouped in two exemplary groups of elevators.
- a first group of elevators comprises an exemplary number of three elevators 31, 32 and 33, with dedicated core controllers 21, 22, 23.
- Each core controller controls at least core functionalities of the elevator that it is connected to.
- the three core controllers 21, 22 and 23 are connected to a first smart communication gateway, which is a communication device 11 with a memory, at least one microprocessor and interfaces to connect to input/ output (I/O) devices and/ or a cloud 5 and at least one remote cloud server 6 or at least one backend computer device 4.
- I/O input/ output
- a second group of elevators comprises again an exemplary number of three elevators 34, 35 and 36, with one common core controller 24.
- the common core controller controls at least core functionalities of the three elevators.
- the common core controller 24 is connected to a second smart communication gateway, which again is a communication device 12 with a memory, at least one microprocessor and interfaces to connect to I/O devices and/ or a cloud 5 and at least one remote cloud server 6 or at least one backend computer device 4.
- the elevator system as shown if Fig. 1 is illustrative. In some embodiments, one or more of the entities may be optional. In some embodiments, additional entities not shown may be included. For example, in some embodiments the elevator system may be associated with one or more networks, such as one or more computer or telephone networks. In some embodiments, the entities may be arranged or organized in a manner different from what is shown in FIG. 2 .
- the system may include one or more elevators, such as elevators 31 to 36.
- the elevators 31, 32 and 33 may be included in a first elevator group 3.
- the elevators 34, 35 and 36 may be included in a second elevator group.
- the first elevator group may include some or all of the elevators at a particular location, such as a building and the second elevator group may include some or all of the elevators at another particular location, such as another building.
- an elevator group may include more or less than three elevators.
- the elevator group may include one or more core controllers, such as dedicated core controllers 21, 22 and 23 for the first elevator group and a common core controller 24 for the second elevator group.
- core controller 21 may be associated with elevator 31
- core controller 22 may be associated with elevator 32
- core controller 23 may be associated with elevator 33.
- core controllers are combined, such that a common core controller 24 may be associated with all of the three elevators 34, 35 and 36.
- a controller may have been responsible for the operation of an elevator or a group of elevators.
- a controller includes all the hardware and software needed to implement control functionality with respect to elevators that were overseen or regulated by the controller.
- selected controller functionality may be moved or relocated from a controller to another entity, such as a communication device or a cloud server.
- another entity such as a communication device or a cloud server.
- controller design may be simplified, which may result in a more reliable core controller.
- Changes in functionality may also be made at one central location, the cloud server, resulting in a consistent implementation across multiple controllers and/or elevator groups simultaneously and without requiring manual intervention at a local site, at the elevator or the elevator group.
- elevator groups may be remotely located from one another, for example in different buildings.
- the core controllers of the elevators or the elevator groups may communicate with the cloud server via a communication device (smart communication gateway) over one or more connections, channels, or links.
- a communication device such connections may adhere to one or more communication protocols, standards, or the like.
- the connections may adhere to landline telephone, cellular (GSM, UMTS, LTE or any future mobile cellular system standard), wireless local area networking (Wi-Fi), Ethernet (local (LAN), metropolitan (MAN) or wide (WAN) area network), satellite, or cable communications.
- the connections may be constant or persistent.
- the communication device 1, 11, 12 may take over some of the functionality of the controller known from the conventional systems and thereby become part of the controller itself.
- the communication device may receive encrypted data from the cloud or a cloud server, which data is, when decrypted by the communication device and executed on the communication, configured to control core operations associated with an elevator or an elevator group. Therefore, and in accordance with an embodiment of this disclosure, control data is forwarded to the at least one core controller by the communication device.
- Controller functionality other than core controller functionality may be executed on a cloud server.
- Such functionality may include non-core functions for an elevator or a group of elevators, operational mode determinations, diagnostic functions, special contract features, etc.
- non-core functions in some embodiments a user request for service received at, e.g., a hall box located on a particular floor of a building may be communicated to the cloud server and the cloud server may transmit a command to the core controller that eventually directs a specified elevator car to relocate to that particular floor to fulfill the service request.
- a local core controller associated with an elevator or a group of elevators may maintain some functionality, and as such, may include hardware and computing resources to support such functionality, especially core functionality like accelerating, decelerating, braking, resulting in movement at specific speeds in upward or downward directions, other core functionality like opening and closing doors and, in particular, safety relevant functionality.
- a core controller may include hardware and/or software to communicate with a cloud server via a communication device (smart communication gateway). For example, a core controller may exchange data and commands with the cloud server to perform control functions.
- the cloud server may store contract setup parameters for select functions. In some embodiments, the contract setup parameters may be stored in the core controller. In some embodiments, there may be a simplified failover functionality located in the core controller in the event that there is a connection loss between the core controller and the communication device and/ or the communication device and the cloud server.
- operational metrics from elevators may be collected at a cloud server across a portfolio of multiple units, sites, or groups.
- the metrics may be filtered at a communication device linked to the core controller of an elevator or a group of elevators, encrypted for secure communication by the communication device, forwarded to, decrypted and analyzed by cloud services or a backend computer to provide a broad view of the portfolio.
- Metrics may be used to create insights that can be turned into actions that provide real business outcomes. For example, the analysis may indicate trends and may be used to respond to needs. The analysis may also be used to facilitate diagnostic or troubleshooting capabilities. Metrics may be used to trigger or enhance the accuracy of sales proposals. Metrics may be used to provide or schedule maintenance activities, such as preventative maintenance activities.
- interface protocols for, e.g., new devices may be stored in a cloud server and used by a communication device and/ or a local core controller.
- functional upgrades for diagnostics, prognostics, and remote repair/rescue functions can be deployed to customers as they are released and deployed into a cloud server.
- Functionality may be developed at the backend computer and deployed to the cloud server.
- One or more tests may be executed to ensure that the functionality satisfies operational or safety requirements.
- a modernization of cloud supported core controllers may be provided.
- Core controllers may utilize a cloud or cloud server to enable new features or support new devices/equipment.
- the communication device linked to the core controller may receive updates via the cloud to support interface protocols to new equipment and/or add new functions/capabilities. For example, if a new fixture is added requiring a new interface, a core controller may enable the new functionality from the cloud once the new fixture has been integrated into the system without requiring an upgrade of software on the core controller.
- a new core algorithm may be implemented from the cloud to optimize traffic during the modernization phase of the project.
- Fig 2 shows an exemplary communication system which includes a communication device 1, above also referred to as smart communication gateway.
- the communication device 1 comprises memory 103 for storing executable instructions and data.
- the executable instructions may be stored or organized in any manner and at any level of abstraction, such as in connection with one or more processes, routines, procedures, methods, functions, etc.
- the instructions stored in the memory 103 may be executed by one or more microprocessors, such as a main processor unit 101.
- the processor may be coupled to one or more I/O devices 15 by means of exemplary first communication interface 106.
- the I/O device(s) 15 may include one or more of a keyboard or keypad, a touchscreen or touch panel, a display screen, a microphone, a speaker, a mouse, a button, a remote control, a joystick, a printer, a telephone or mobile device (e.g., a smartphone), etc.
- the I/O device(s) 15 may be configured to provide an interface to allow a user to interact with the communication device 1.
- the device has several communication interfaces 105 to 107.
- An exemplary second communication interface 105 connects the communication device to the cloud.
- Exemplary third communication interface 107 connect the communication device to the at least one core controller of an associated elevator or group of elevators.
- the communication device 1 further comprises a cryptoprocessor 102, which is a dedicated microcontroller designed to secure the hardware of the communication device 1 by integrating cryptographic keys into the device.
- a cryptoprocessor is commonly known as Trusted Platform Module.
- the cryptoprocessor has the primary scope to assure integrity of the communication device within an elevator communication system comprising several components in remote locations, such as elevators, groups of elevators, core controllers of elevators, core controllers of groups of elevators, communication devices (smart communication gateways), cloud servers, backend computers, etc.
- Communication to and from the elevator core controller(s) through the communication device 1 is encrypted/ decrypted using the cryptoprocessor 102.
- Communication content integrity and security, as well as system components identity authentication can be further improved with the use of cryptoprocessors.
- integrated means "behave as intended”.
- secure cryptoprocessors, or dedicated microcontroller designed to secure hardware by integrating cryptographic keys into devices in general access to the communication system is less prone to "dictionary attacks" compared to pure software implemented authentication mechanisms.
- a dictionary attack prevention mechanism is created, which effectively protects against guessing or automated dictionary attacks. Without this level of protection, only passwords with high complexity would provide sufficient protection.
- Embodiments of the disclosure may be used to reduce local controller hardware and/or software.
- functionality may be at least partially supported by one or more servers, such as one or more cloud servers.
- Increased or upgraded functionality may be provided without impacting local controller memory or processing requirements/capacities.
- Embodiments of the disclosure may have high-level control functionality implemented remote from an elevator. Functionality may be modified off-line. Functionality may be pushed from a cloud server to one or more elevators once the functionality is available. In some embodiments, an elevator may be configured to request functionality via, e.g., a pull-model.
- Embodiments of the disclosure may be tied to one or more particular machines.
- a controller may be configured to communicate with a cloud server.
- the cloud server may store data that may be used to control one or more functions associated with an environment or application.
- the data may be communicated from the cloud server to the controller to support operations within the environment or application.
- various functions or acts may take place at a given location and/or in connection with the operation of one or more apparatuses, systems, or devices. For example, in some embodiments, a portion of a given function or act may be performed at a first device or location, and the remainder of the function or act may be performed at one or more additional devices or locations.
- an apparatus or system may include one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus or system to perform one or more methodological acts as described herein.
- Various mechanical components known to those of skill in the art may be used in some embodiments.
- Embodiments may be implemented as one or more apparatuses, systems, and/or methods.
- instructions may be stored on one or more computer program products or computer-readable media, such as a transitory and/or non-transitory computer-readable medium.
- the instructions when executed, may cause an entity (e.g., an apparatus or system) to perform one or more methodological acts as described herein.
Landscapes
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Computer Networks & Wireless Communication (AREA)
- Indicating And Signalling Devices For Elevators (AREA)
Description
- The present invention relates to the field of elevator and escalator devices. More specifically, it relates to a communication device, a method and a system for communicating between a core controller associated with an elevator or escalator device and a cloud server.
- In conventional elevator or escalator systems, control software is stored and operated locally on a control board at each instance or installation. Adding or modifying functionality requires service personnel to manually update the software on the control board or download the software to a local unit via a remote connection. A software upgrade may require a corresponding processor and memory upgrade.
- Functions and capabilities continue to be added to elevator controllers. Controller software might not be automatically upgraded unless manually executed at a user's request. Future functionality may someday reach the memory and computing power resource limitations in the existing control boards. At that point, a user may have to elect to forego incorporating additional functionality or otherwise incur large expenses upgrading a supporting hardware platform.
-
US 9067760 B2 -
JP 2014 172714 A - It is an object of the invention to improve an elevator or escalator system with a controller that comprises a core controller for core functionalities and has non-core functionalities moved or relocated from the core controller to another entity. Such improvements shall in particular concern integrity of the systems communication devices as well as security of data that is communicated between the different communication entities of the system.
- According to a first aspect, the invention is directed to a method according to
claim 1. - According to a second aspect, the invention is directed to a communication device with at least one microprocessor; at least one cryptoprocessor; and memory having instructions stored thereon that, when executed by the at least one microprocessor and the at least one cryptoprocessor, cause the communication device to at least one of: receive from a cloud server or a backend computer encrypted data that is configured to at least control core operations associated with an elevator or escalator device, decrypt the data, and distribute the data over at least one data connection between the communication device and at least one core controller associated with an elevator or escalator device to said at least one core controller to be used by said controller to control core operations associated with said elevator or escalator device, or receive control feedback data over at least one data connection between the communication device and at least one core controller associated with an elevator or escalator device to said at least one core controller, encrypt the data, and send the encrypted data to a cloud server or a backend computer.
- A third aspect of the invention is directed to a system comprising: a first plurality of elevator or escalator devices; at least one core controller configured to control operations associated with the first plurality of elevator or escalator devices; a cloud server; and a first communication device linked to the at least one first core controller.
- Encrypting the data which is communicated between the communication devices allows to maintain the security level obtained with conventionally controlled elevator and escalator devices even when control over non-core functionalities are moved or relocated to remote devices or into the cloud in general.
- Additional embodiments are described below.
- Exemplary embodiments of the disclosed technologies are explained in detail with reference to the figures, in which:
-
FIG. 1 schematically shows a view of a portion of an elevator system which communicates with a cloud server and/ or a backend computer connected to the cloud; and -
FIG. 2 schematically shows a view of a portion of a communication device in an elevator system as shown inFig. 1 . - It is noted that various connections are set forth between elements in the following description and in the drawings (the contents of which are included in this disclosure by way of reference). It is noted that these connections in general and, unless specified otherwise, may be direct or indirect and that this specification is not intended to be limiting in this respect. In this respect, a coupling between entities may refer to either a direct or an indirect connection. Some connections are marked with an open or closed lock symbol, exemplarily indicating that information and data transported over these connections is encrypted (locked) or unencrypted (open).
- Exemplary embodiments of apparatuses, systems, and methods are described for maintaining, updating/modifying, and upgrading an elevator system. In some embodiments, functionality typically associated with an elevator controller may be located in another device or entity, such as a smart communication gateway or on a cloud server. The elevator controller may communicate with the smart communication gateway and the cloud server to support selected control functions.
- The term cloud or cloud computing shall in this specification have the meaning of internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. A cloud server is a computer device (server) that is connected to and can be contacted over the internet or any other comparable dedicated or open communication network.
-
Fig 1 shows an exemplary elevator system comprisingseveral elevators 31 through 36 grouped in two exemplary groups of elevators. - On the left side of the drawing, a first group of elevators comprises an exemplary number of three
elevators dedicated core controllers core controllers communication device 11 with a memory, at least one microprocessor and interfaces to connect to input/ output (I/O) devices and/ or acloud 5 and at least oneremote cloud server 6 or at least onebackend computer device 4. - On the right side of the drawing, a second group of elevators comprises again an exemplary number of three
elevators common core controller 24. - The common core controller controls at least core functionalities of the three elevators. The
common core controller 24 is connected to a second smart communication gateway, which again is acommunication device 12 with a memory, at least one microprocessor and interfaces to connect to I/O devices and/ or acloud 5 and at least oneremote cloud server 6 or at least onebackend computer device 4. - The elevator system as shown if
Fig. 1 is illustrative. In some embodiments, one or more of the entities may be optional. In some embodiments, additional entities not shown may be included. For example, in some embodiments the elevator system may be associated with one or more networks, such as one or more computer or telephone networks. In some embodiments, the entities may be arranged or organized in a manner different from what is shown inFIG. 2 . - The system may include one or more elevators, such as
elevators 31 to 36. Theelevators first elevator group 3. Theelevators - While three
elevators FIG. 1 in respective groups, an elevator group may include more or less than three elevators. - The elevator group may include one or more core controllers, such as
dedicated core controllers common core controller 24 for the second elevator group. In the first elevator group,core controller 21 may be associated withelevator 31,core controller 22 may be associated withelevator 32 andcore controller 23 may be associated withelevator 33. In the second group of elevators, core controllers are combined, such that acommon core controller 24 may be associated with all of the threeelevators - In conventional systems, a controller may have been responsible for the operation of an elevator or a group of elevators. In this respect, in conventional systems a controller includes all the hardware and software needed to implement control functionality with respect to elevators that were overseen or regulated by the controller.
- In accordance with one or more embodiments of this disclosure, selected controller functionality, especially non-core functionality or not security relevant functionality, may be moved or relocated from a controller to another entity, such as a communication device or a cloud server. By moving non-core functionality to another entity, a reduction in hardware within the controller included in an elevator or an elevator group may be realized. In this respect, controller design may be simplified, which may result in a more reliable core controller. Changes in functionality may also be made at one central location, the cloud server, resulting in a consistent implementation across multiple controllers and/or elevator groups simultaneously and without requiring manual intervention at a local site, at the elevator or the elevator group. In some embodiments, elevator groups may be remotely located from one another, for example in different buildings.
- The core controllers of the elevators or the elevator groups may communicate with the cloud server via a communication device (smart communication gateway) over one or more connections, channels, or links. Such connections may adhere to one or more communication protocols, standards, or the like. For example, the connections may adhere to landline telephone, cellular (GSM, UMTS, LTE or any future mobile cellular system standard), wireless local area networking (Wi-Fi), Ethernet (local (LAN), metropolitan (MAN) or wide (WAN) area network), satellite, or cable communications. In some embodiments, the connections may be constant or persistent.
- In accordance with one or more embodiments of this disclosure, the
communication device - Controller functionality other than core controller functionality may be executed on a cloud server. Such functionality may include non-core functions for an elevator or a group of elevators, operational mode determinations, diagnostic functions, special contract features, etc. Regarding non-core functions, in some embodiments a user request for service received at, e.g., a hall box located on a particular floor of a building may be communicated to the cloud server and the cloud server may transmit a command to the core controller that eventually directs a specified elevator car to relocate to that particular floor to fulfill the service request.
- A local core controller associated with an elevator or a group of elevators may maintain some functionality, and as such, may include hardware and computing resources to support such functionality, especially core functionality like accelerating, decelerating, braking, resulting in movement at specific speeds in upward or downward directions, other core functionality like opening and closing doors and, in particular, safety relevant functionality.
- A core controller may include hardware and/or software to communicate with a cloud server via a communication device (smart communication gateway). For example, a core controller may exchange data and commands with the cloud server to perform control functions. The cloud server may store contract setup parameters for select functions. In some embodiments, the contract setup parameters may be stored in the core controller. In some embodiments, there may be a simplified failover functionality located in the core controller in the event that there is a connection loss between the core controller and the communication device and/ or the communication device and the cloud server.
- In some embodiments, operational metrics from elevators may be collected at a cloud server across a portfolio of multiple units, sites, or groups. The metrics may be filtered at a communication device linked to the core controller of an elevator or a group of elevators, encrypted for secure communication by the communication device, forwarded to, decrypted and analyzed by cloud services or a backend computer to provide a broad view of the portfolio. Metrics may be used to create insights that can be turned into actions that provide real business outcomes. For example, the analysis may indicate trends and may be used to respond to needs. The analysis may also be used to facilitate diagnostic or troubleshooting capabilities. Metrics may be used to trigger or enhance the accuracy of sales proposals. Metrics may be used to provide or schedule maintenance activities, such as preventative maintenance activities.
- In some embodiments, interface protocols for, e.g., new devices may be stored in a cloud server and used by a communication device and/ or a local core controller.
- In some embodiments, functional upgrades for diagnostics, prognostics, and remote repair/rescue functions can be deployed to customers as they are released and deployed into a cloud server. Functionality may be developed at the backend computer and deployed to the cloud server. One or more tests may be executed to ensure that the functionality satisfies operational or safety requirements.
- In some embodiments, a modernization of cloud supported core controllers may be provided. Core controllers may utilize a cloud or cloud server to enable new features or support new devices/equipment. Before or during the modernization, the communication device linked to the core controller may receive updates via the cloud to support interface protocols to new equipment and/or add new functions/capabilities. For example, if a new fixture is added requiring a new interface, a core controller may enable the new functionality from the cloud once the new fixture has been integrated into the system without requiring an upgrade of software on the core controller. As yet another example, a new core algorithm may be implemented from the cloud to optimize traffic during the modernization phase of the project.
-
Fig 2 shows an exemplary communication system which includes acommunication device 1, above also referred to as smart communication gateway. Thecommunication device 1 comprisesmemory 103 for storing executable instructions and data. The executable instructions may be stored or organized in any manner and at any level of abstraction, such as in connection with one or more processes, routines, procedures, methods, functions, etc. - The instructions stored in the
memory 103 may be executed by one or more microprocessors, such as amain processor unit 101. The processor may be coupled to one or more I/O devices 15 by means of exemplaryfirst communication interface 106. In some embodiments, the I/O device(s) 15 may include one or more of a keyboard or keypad, a touchscreen or touch panel, a display screen, a microphone, a speaker, a mouse, a button, a remote control, a joystick, a printer, a telephone or mobile device (e.g., a smartphone), etc. The I/O device(s) 15 may be configured to provide an interface to allow a user to interact with thecommunication device 1. - To allow communication to and through the
communication device 1 the device hasseveral communication interfaces 105 to 107. An exemplarysecond communication interface 105 connects the communication device to the cloud. Exemplarythird communication interface 107 connect the communication device to the at least one core controller of an associated elevator or group of elevators. - The
communication device 1 further comprises acryptoprocessor 102, which is a dedicated microcontroller designed to secure the hardware of thecommunication device 1 by integrating cryptographic keys into the device. Such a cryptoprocessor is commonly known as Trusted Platform Module. The cryptoprocessor has the primary scope to assure integrity of the communication device within an elevator communication system comprising several components in remote locations, such as elevators, groups of elevators, core controllers of elevators, core controllers of groups of elevators, communication devices (smart communication gateways), cloud servers, backend computers, etc. - Communication to and from the elevator core controller(s) through the
communication device 1 is encrypted/ decrypted using thecryptoprocessor 102. Communication content integrity and security, as well as system components identity authentication can be further improved with the use of cryptoprocessors. In this context "integrity" means "behave as intended". Also, with the use of secure cryptoprocessors, or dedicated microcontroller designed to secure hardware by integrating cryptographic keys into devices in general, access to the communication system is less prone to "dictionary attacks" compared to pure software implemented authentication mechanisms. With the implementation of cryptograpfic keys in a dedicated hardware module, a dictionary attack prevention mechanism is created, which effectively protects against guessing or automated dictionary attacks. Without this level of protection, only passwords with high complexity would provide sufficient protection. - While some of the examples described herein related to elevators, aspects of this disclosure may be applied in connection with other types of conveyor devices, such as an escalator, a moving sidewalk, a wheelchair lift, or groups of such conveyor devices, etc.
- Embodiments of the disclosure may be used to reduce local controller hardware and/or software. For example, functionality may be at least partially supported by one or more servers, such as one or more cloud servers. Increased or upgraded functionality may be provided without impacting local controller memory or processing requirements/capacities.
- Embodiments of the disclosure may have high-level control functionality implemented remote from an elevator. Functionality may be modified off-line. Functionality may be pushed from a cloud server to one or more elevators once the functionality is available. In some embodiments, an elevator may be configured to request functionality via, e.g., a pull-model.
- Embodiments of the disclosure may be tied to one or more particular machines. For example, a controller may be configured to communicate with a cloud server. The cloud server may store data that may be used to control one or more functions associated with an environment or application. The data may be communicated from the cloud server to the controller to support operations within the environment or application.
- As described herein, in some embodiments various functions or acts may take place at a given location and/or in connection with the operation of one or more apparatuses, systems, or devices. For example, in some embodiments, a portion of a given function or act may be performed at a first device or location, and the remainder of the function or act may be performed at one or more additional devices or locations.
- Embodiments may be implemented using one or more technologies. In some embodiments, an apparatus or system may include one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus or system to perform one or more methodological acts as described herein. Various mechanical components known to those of skill in the art may be used in some embodiments.
- Embodiments may be implemented as one or more apparatuses, systems, and/or methods. In some embodiments, instructions may be stored on one or more computer program products or computer-readable media, such as a transitory and/or non-transitory computer-readable medium. The instructions, when executed, may cause an entity (e.g., an apparatus or system) to perform one or more methodological acts as described herein.
Claims (15)
- A method comprising the steps of:receiving, by a communication device (1, 11, 12) linked to at least one core controller (21, 22, 23, 24) associated with an elevator or escalator device (31, 32, ..., 36) from a cloud server (6), encrypted data that is configured to control operations associated with the at least one elevator or escalator device (31, 32, ..., 36,),decrypting the data with a cryptoprocessor (102) on the communication device (1, 11, 12); andforwarding the decrypted data from the communication device (1, 11, 12) to the at least one core controller (21, 22, 23, 24) associated with the elevator or escalator device (31, 32, ..., 36).
- The method of claim 1, further comprising the step of:
receiving, by the cloud server (6), the encrypted data from a backend computer (4). - The method of claim 1, wherein the elevator or escalator device (31, 32, ..., 36) is included in a group of elevator or escalator devices (31, 32, ..., 36).
- The method of claim 3, wherein the core controller (21, 22, 23, 24) controls each of the elevator or escalator devices (31, 32, ..., 36) in accordance with the data.
- The method of claim 1, further comprising the steps of:obtaining, by the communication device (1, 11, 12), second data regarding a status of an implementation of the data and/ or second data regarding the use of the data from the core controller (21, 22, 23, 24);encrypting the second data with a cryptoprocessor (102) on the communication device (1, 11, 12); andforwarding the decrypted second data from the communication device (1, 11, 12) to a cloud server (6) and/ or a backend computer (4).
- The method of claim 1, further comprising the step of:
manipulating and/ or analyzing and/ or filtering the second data. - The method of claim 6, wherein manipulating and/ or analyzing and/ or filtering the second data is done by the communication device (1, 11, 12) and/ or the cloud server (6).
- Communication device (1, 11, 12) with at least one microprocessor and memory characterized by at least one cryptoprocessor (102) and in that the memory having instructions stored thereon that, when executed by the at least one microprocessor and the at least one cryptoprocessor (102), cause the communication device (1, 11, 12) to at least one of:receive from a cloud server (6) or a backend computer (4) encrypted data that is configured to at least control core operations associated with an elevator or escalator device (31, 32, ..., 36),decrypt the data, anddistribute the data over at least one data connection between the communication device (1, 11, 12) and at least one core controller (21, 22, 23, 24) associated with an elevator or escalator device (31, 32, ..., 36) to said at least one core controller (21, 22, 23, 24) to be used by said controller to control core operations associated with said elevator or escalator device (31, 32, ..., 36), orreceive control feedback data over at least one data connection between the communication device (1, 11, 12) and at least one core controller (21, 22, 23, 24) associated with an elevator or escalator device (31, 32, ..., 36) to said at least one core controller (21, 22, 23, 24),encrypt the data, andsend the encrypted data to a cloud server (6) or a backend computer (4).
- Communication apparatus comprising a communication device (1, 11, 12) of claim 8, wherein the apparatus further comprises a cloud server (6).
- Communication apparatus of claim 9, wherein the data is implemented as a software program, and wherein the apparatus receives the software program from a backend computer (4).
- Communication apparatus of claim 10, wherein the software program is used to alter the instructions stored in the memory of the communication device (1, 11, 12).
- Communication apparatus comprising a communication device (1, 11, 12) of claim 8, wherein the data connection to distribute the data to the core controller is at least one of an analogue phone connection, a digital cellular communications connection, a Wi-Fi connection, an Ethernet connection, a satellite connection, and a cable communications connection.
- A system comprising:a first plurality of elevator or escalator devices (31, 32, ..., 36);at least one core controller (21, 22, 23, 24) configured to control operations associated with the first plurality of elevator or escalator devices (31, 32, ..., 36);a cloud server (6); anda first communication device (1, 11, 12) of claim 8 linked to the at least one first core controller (21, 22, 23, 24).
- The system of claim 13, further comprising:a second plurality of elevator or escalator devices (31, 32, ..., 36) remotely located from the first plurality of elevator or escalator device (31, 32, ..., 36); anda second communication device (1, 11, 12) linked to at least one second core controller configured to control at least core operations associated with the second plurality of elevator or escalator devices (31, 32, ..., 36).
- The system of claim 14, wherein the cloud server (6) is configured to distribute encrypted data to the second communication device (1, 11, 12) substantially the same time that the cloud server (6) distributes the encrypted data to the first communication device (1, 11, 12).
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP21180578.3A EP3904268B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17167610.9A EP3392191B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
EP21180578.3A EP3904268B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17167610.9A Division EP3392191B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3904268A1 EP3904268A1 (en) | 2021-11-03 |
EP3904268B1 true EP3904268B1 (en) | 2023-08-23 |
Family
ID=58606142
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17167610.9A Active EP3392191B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
EP21180578.3A Active EP3904268B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17167610.9A Active EP3392191B1 (en) | 2017-04-21 | 2017-04-21 | Elevator control system |
Country Status (1)
Country | Link |
---|---|
EP (2) | EP3392191B1 (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110844724A (en) | 2018-08-21 | 2020-02-28 | 奥的斯电梯公司 | Elevator data communication system |
CN109823952B (en) * | 2019-03-20 | 2023-12-05 | 杭州地铁运营有限公司 | Station escalator guide control panel |
EP3976518B1 (en) | 2019-05-29 | 2024-06-26 | Inventio Ag | Elevator system with a multipurpose edge-gateway and method for data communication |
EP3915912A1 (en) * | 2020-05-29 | 2021-12-01 | KONE Corporation | A people conveyor system and a method for updating software of a people conveyor component in a people conveyor system |
JP7151941B2 (en) | 2020-06-19 | 2022-10-12 | 三菱電機ビルソリューションズ株式会社 | Elevator control device, elevator monitoring system and elevator monitoring method |
CN112623918B (en) * | 2020-12-09 | 2023-06-02 | 中铁第四勘察设计院集团有限公司 | Intelligent escalator decision-making method and system based on IPFS |
US11912532B2 (en) * | 2021-01-04 | 2024-02-27 | Beltways Inc. | System and methods for variable speed modular moving walkways |
CN112960494B (en) * | 2021-02-08 | 2023-02-10 | 深圳市旺龙智能科技有限公司 | Elevator taking control device additionally arranged on elevator and shared elevator cloud charging system |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060260880A1 (en) | 2004-05-21 | 2006-11-23 | Mitsubishi Denki Kabushiki Kaisha | Remote supervisory control system for elevating machine |
US8770350B2 (en) | 2008-12-18 | 2014-07-08 | Otis Elevator Company | Access control system and access control method for a people conveyor control system |
JP2014172714A (en) | 2013-03-08 | 2014-09-22 | Hitachi Ltd | Elevator system |
CN104495553A (en) | 2014-12-05 | 2015-04-08 | 安徽中程智能科技有限公司 | Intelligent elevator monitoring and managing platform |
CN104986634A (en) | 2015-07-08 | 2015-10-21 | 广州广日电梯工业有限公司 | System and method for cloud group control of elevator |
US9596078B2 (en) | 2013-09-10 | 2017-03-14 | M2M And Iot Technologies, Llc | Set of servers for “machine-to-machine” communications using public key infrastructure |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2243738A1 (en) | 2009-04-24 | 2010-10-27 | Inventio AG | Method for communicating with a lift assembly |
-
2017
- 2017-04-21 EP EP17167610.9A patent/EP3392191B1/en active Active
- 2017-04-21 EP EP21180578.3A patent/EP3904268B1/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060260880A1 (en) | 2004-05-21 | 2006-11-23 | Mitsubishi Denki Kabushiki Kaisha | Remote supervisory control system for elevating machine |
US8770350B2 (en) | 2008-12-18 | 2014-07-08 | Otis Elevator Company | Access control system and access control method for a people conveyor control system |
JP2014172714A (en) | 2013-03-08 | 2014-09-22 | Hitachi Ltd | Elevator system |
US9596078B2 (en) | 2013-09-10 | 2017-03-14 | M2M And Iot Technologies, Llc | Set of servers for “machine-to-machine” communications using public key infrastructure |
CN104495553A (en) | 2014-12-05 | 2015-04-08 | 安徽中程智能科技有限公司 | Intelligent elevator monitoring and managing platform |
CN104986634A (en) | 2015-07-08 | 2015-10-21 | 广州广日电梯工业有限公司 | System and method for cloud group control of elevator |
Also Published As
Publication number | Publication date |
---|---|
EP3392191B1 (en) | 2021-06-23 |
EP3904268A1 (en) | 2021-11-03 |
EP3392191A1 (en) | 2018-10-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3904268B1 (en) | Elevator control system | |
EP3203703B1 (en) | Beacon-based industrial automation access authorization | |
US20160134686A1 (en) | Cloud management | |
US20160107861A1 (en) | Cloud server based control | |
JP6700688B2 (en) | Device safety for process control systems | |
CA2943250C (en) | Method and system for ensuring an application conforms with security and regulatory controls prior to deployment | |
CN100535808C (en) | System and method for secure remote access | |
CN104247486B (en) | The method and computing device of connection are established between the enterprise security circumference of equipment and enterprise | |
EP3618353B1 (en) | Dynamic, endpoint configuration-based deployment of network infrastructure | |
US10551809B2 (en) | Identification of industrial equipment using micro-location services | |
EP3530602B1 (en) | Safety circuit for an elevator system, device and method of updating such a safety circuit | |
CN111212805A (en) | Safety system for people mover of building | |
JP2010049331A (en) | Management device, method, and program for network equipment | |
KR101599213B1 (en) | Method and system for providing service detection rule in network security | |
US20180314512A1 (en) | Software updating device | |
US20190109825A1 (en) | Method for the management and maintenance of an aircraft comprising a zone with a high degree of security | |
CN112468316A (en) | Edge computing gateway device and implementation method thereof | |
US20130139147A1 (en) | System for performing remote services for a technical installation | |
US11134399B1 (en) | Connectivity apparatus for remote cell tower integration | |
US20020133634A1 (en) | Thin client solutions with HMI systems | |
CN111343263B (en) | Operation and maintenance system and operation and maintenance method for batch private cloud | |
CN111371746B (en) | Operation and maintenance system and operation and maintenance method for batch private cloud | |
EP3947231B1 (en) | Method and system for commissioning of a communication gateway | |
CN113614016B (en) | Safety device for personnel handling equipment incorporated in a building | |
CN105807740A (en) | Bulk cargo loading and unloading equipment remote service system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 3392191 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
B565 | Issuance of search results under rule 164(2) epc |
Effective date: 20210908 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20220425 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: INVENTIO AG |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20230411 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 3392191 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602017073305 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20230823 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1602405 Country of ref document: AT Kind code of ref document: T Effective date: 20230823 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231124 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231223 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231226 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231123 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231223 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231124 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R026 Ref document number: 602017073305 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230823 |
|
PLBI | Opposition filed |
Free format text: ORIGINAL CODE: 0009260 |
|
PLAX | Notice of opposition and request to file observation + time limit sent |
Free format text: ORIGINAL CODE: EPIDOSNOBS2 |
|
26 | Opposition filed |
Opponent name: OTIS ELEVATOR COMPANY Effective date: 20240523 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240423 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240429 Year of fee payment: 8 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Free format text: CASE NUMBER: APP_34688/2024 Effective date: 20240610 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20240501 Year of fee payment: 8 |