[go: up one dir, main page]

EP3392191B1 - Système de commande d'ascenseur - Google Patents

Système de commande d'ascenseur Download PDF

Info

Publication number
EP3392191B1
EP3392191B1 EP17167610.9A EP17167610A EP3392191B1 EP 3392191 B1 EP3392191 B1 EP 3392191B1 EP 17167610 A EP17167610 A EP 17167610A EP 3392191 B1 EP3392191 B1 EP 3392191B1
Authority
EP
European Patent Office
Prior art keywords
elevator
communication device
data
escalator
core
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
Application number
EP17167610.9A
Other languages
German (de)
English (en)
Other versions
EP3392191A1 (fr
Inventor
Adrian Bünter
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inventio AG
Original Assignee
Inventio AG
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=58606142&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP3392191(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Inventio AG filed Critical Inventio AG
Priority to EP17167610.9A priority Critical patent/EP3392191B1/fr
Priority to EP21180578.3A priority patent/EP3904268B1/fr
Publication of EP3392191A1 publication Critical patent/EP3392191A1/fr
Application granted granted Critical
Publication of EP3392191B1 publication Critical patent/EP3392191B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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 172 714 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.
  • An embodiment of the disclosure 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 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.
  • An embodiment of the disclosure 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)

Claims (12)

  1. Procédé comprenant les étapes consistant à :
    recevoir, par un dispositif de communication (1, 11, 12) lié à au moins un dispositif de commande principal (21, 22, 23, 24) associé à un dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36) à partir d'un serveur infonuagique (6), des données chiffrées qui, lorsqu'elles sont déchiffrées par le dispositif de communication et exécutées sur le dispositif de communication, sont configurées pour commander des opérations principales associées à l'au moins un dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36), déchiffrer les données avec un cryptoprocesseur (102) sur le dispositif de communication (1, 11, 12) ; et
    transmettre les données déchiffrées du dispositif de communication (1, 11, 12) à l'au moins un dispositif de commande central (21, 22, 23, 24) associé au dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36).
  2. Procédé selon la revendication 1, comprenant en outre l'étape consistant à :
    recevoir, par le serveur infonuagique (6), les données chiffrées d'un ordinateur d'arrière-plan (4).
  3. Procédé selon la revendication 1, dans lequel le dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36) est inclus dans un groupe de dispositifs d'ascenseur ou d'escalier mécanique (31, 32, ..., 36).
  4. Procédé selon la revendication 3, dans lequel le dispositif de commande principal (21, 22, 23, 24) commande chacun des dispositifs d'ascenseur ou d'escalier mécanique (31, 32, ..., 36) en fonction des données.
  5. Dispositif de communication (1, 11, 12) doté d'au moins un microprocesseur ;
    d'au moins un cryptoprocesseur (102) ; et d'une mémoire ; caractérisé par la mémoire sur laquelle sont stockées des instructions qui, lorsqu'elles sont exécutées par l'au moins un microprocesseur et l'au moins un cryptoprocesseur (102), amènent le dispositif de communication (1, 11, 12) à :
    recevoir d'un serveur infonuagique (6) ou d'un ordinateur d'arrière-plan (4) des données chiffrées qui sont configurées pour au moins commander les opérations principales associées à un dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36),
    déchiffrer les données, et
    distribuer les données sur au moins une connexion de données entre le dispositif de communication (1, 11, 12) et au moins un dispositif de commande principal (21, 22, 23, 24) associé à un dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36) audit au moins un dispositif de commande principal (21, 22, 23, 24) à utiliser par ledit dispositif de commande pour commander les opérations principales associées audit dispositif d'ascenseur ou d'escalier mécanique (31, 32, ..., 36), ou
    recevoir les données de retour de commande sur au moins une connexion de données entre le dispositif de communication (1, 11, 12) et au moins un dispositif de commande principal (21, 22, 23, 24) associé à un dispositif d'ascenseur ou d'escalier mécanique (31, 32, ...,36) audit au moins un dispositif de commande principal (21, 22, 23, 24),
    chiffrer les données et
    envoyer les données chiffrées à un serveur infonuagique (6) ou à un ordinateur d'arrière-plan (4).
  6. Appareil de communication comprenant un dispositif de communication (1, 11, 12) selon la revendication 5, dans lequel l'appareil comprend en outre un serveur infonuagique (6).
  7. Appareil de communication selon la revendication 6, dans lequel les données sont mises en œuvre sous la forme d'un programme logiciel, et dans lequel l'appareil reçoit le programme logiciel d'un ordinateur d'arrière-plan (4).
  8. Appareil de communication selon la revendication 7, dans lequel le programme logiciel est utilisé pour modifier les instructions stockées dans la mémoire du dispositif de communication (1, 11, 12).
  9. Appareil de communication comprenant un dispositif de communication (1, 11, 12) selon la revendication 5, dans lequel la connexion de données pour distribuer les données au dispositif de commande principal est :
    une connexion téléphonique analogique, et/ou une connexion de communication cellulaire numérique, et/ou une connexion Wi-Fi, et/ou une connexion Ethernet, et/ou une connexion satellite et/ou une connexion de communication par câble.
  10. Système comprenant :
    une première pluralité de dispositifs d'ascenseur ou d'escalier mécanique (31, 32,..., 36) ;
    au moins un dispositif de commande principal (21, 22, 23, 24) configuré pour commander les opérations associées à la première pluralité de dispositifs d'ascenseur ou d'escalier mécanique (31, 32,..., 36) ;
    un serveur infonuagique (6) ; et
    un premier dispositif de communication (1, 11, 12) selon la revendication 5 lié à l'au moins un premier dispositif de commande principal (21, 22, 23, 24).
  11. Système selon la revendication 10, comprenant en outre :
    une seconde pluralité de dispositifs d'ascenseur ou d'escalier mécanique (31, 32, ..., 36) situés à distance de la première pluralité de dispositifs d'ascenseur ou d'escalier mécanique (31, 32, ..., 36) ; et
    un second dispositif de communication (1, 11, 12) selon la revendication 5 lié à au moins un second dispositif de commande principal configuré pour commander au moins les opérations principales associées à la seconde pluralité de dispositifs d'ascenseur ou d'escalier mécanique (31, 32, ..., 36).
  12. Système selon la revendication 11, dans lequel le serveur infonuagique (6) est configuré pour distribuer des données chiffrées au second dispositif de communication (1, 11, 12) sensiblement au même moment où le serveur infonuagique (6) distribue les données chiffrées au premier dispositif de communication (1, 11, 12).
EP17167610.9A 2017-04-21 2017-04-21 Système de commande d'ascenseur Active EP3392191B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17167610.9A EP3392191B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur
EP21180578.3A EP3904268B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP17167610.9A EP3392191B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP21180578.3A Division EP3904268B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur

Publications (2)

Publication Number Publication Date
EP3392191A1 EP3392191A1 (fr) 2018-10-24
EP3392191B1 true EP3392191B1 (fr) 2021-06-23

Family

ID=58606142

Family Applications (2)

Application Number Title Priority Date Filing Date
EP21180578.3A Active EP3904268B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur
EP17167610.9A Active EP3392191B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP21180578.3A Active EP3904268B1 (fr) 2017-04-21 2017-04-21 Système de commande d'ascenseur

Country Status (1)

Country Link
EP (2) EP3904268B1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110844724A (zh) 2018-08-21 2020-02-28 奥的斯电梯公司 电梯数据通信系统
CN109823952B (zh) * 2019-03-20 2023-12-05 杭州地铁运营有限公司 一种车站电扶梯导向控制板
AU2020281743B2 (en) 2019-05-29 2024-06-06 Inventio Ag Elevator system with a multipurpose edge-gateway and method for data communication
AU2021220228A1 (en) 2020-02-13 2022-09-01 Inventio Ag Method of operating a computer-controlled device for establishing a secure data communication in a distributed control system of a passenger transportation arrangement
EP3915912A1 (fr) * 2020-05-29 2021-12-01 KONE Corporation Système de transport de personnes et procédé de mise à jour de logiciel d'un composant de transport de personnes dans un système de transport de personnes
KR102497834B1 (ko) 2020-06-19 2023-02-08 미쓰비시 덴키 빌딩 솔루션즈 가부시키가이샤 엘리베이터 제어 장치, 엘리베이터 감시 시스템 및 엘리베이터 감시 방법
CN112623918B (zh) * 2020-12-09 2023-06-02 中铁第四勘察设计院集团有限公司 一种基于ipfs的自动扶梯智能决策方法及系统
US11912532B2 (en) * 2021-01-04 2024-02-27 Beltways Inc. System and methods for variable speed modular moving walkways
CN112960494B (zh) * 2021-02-08 2023-02-10 深圳市旺龙智能科技有限公司 用于加装在电梯上的乘梯控制装置及共享电梯云收费系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4607109B2 (ja) 2004-05-21 2011-01-05 三菱電機株式会社 昇降機の遠隔監視制御システム
KR101425464B1 (ko) 2008-12-18 2014-08-01 오티스 엘리베이터 컴파니 승객 수송장치 제어 시스템에 대한 접근 제어 시스템 및 접근 제어 방법
EP2243738A1 (fr) 2009-04-24 2010-10-27 Inventio AG Procédé destiné à la communication à l'aide d'une installation d'ascenseur
JP2014172714A (ja) 2013-03-08 2014-09-22 Hitachi Ltd エレベータシステム
US9350550B2 (en) 2013-09-10 2016-05-24 M2M And Iot Technologies, Llc Power management and security for wireless modules in “machine-to-machine” communications
CN104495553A (zh) 2014-12-05 2015-04-08 安徽中程智能科技有限公司 智能电梯监测管理平台
CN104986634B (zh) * 2015-07-08 2017-03-08 广州广日电梯工业有限公司 一种电梯云群控系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP3392191A1 (fr) 2018-10-24
EP3904268A1 (fr) 2021-11-03
EP3904268B1 (fr) 2023-08-23

Similar Documents

Publication Publication Date Title
EP3392191B1 (fr) Système de commande d'ascenseur
US20160134686A1 (en) Cloud management
US20160107861A1 (en) Cloud server based control
EP3203703B1 (fr) Autorisation d'accès d'automatisation industrielle par balise
JP6700688B2 (ja) プロセス制御システムに対するデバイスの安全化
EP3099037B1 (fr) Provision d'une mot de passe à utilisation pour escalade temporaire de privilège dans un système de contrôle
CA2943250C (fr) Procede et systeme pour assurer qu'une application est conforme a des controles de securite et de reglementation avant deploiement
AU2018356262C1 (en) Safety system for a building-related passenger transportation system
EP3530602B1 (fr) Circuit de sécurité pour un système d'ascenseur, dispositif et procédé de mise à jour d'un tel circuit de sécurité
EP3947231B1 (fr) Procédé et système pour la mise en service d'une passerelle de communication
JP2010049331A (ja) ネットワーク機器の管理装置、管理方法及び管理プログラム
CN109891845B (zh) 管理和维护包括有高度安全性的区域的飞机的方法和系统
CN104426908A (zh) 用于可信移动通信的系统及方法
WO2017063701A1 (fr) Dispositif de mise à jour de logiciel
US10360355B2 (en) Secondary security authority
US9940116B2 (en) System for performing remote services for a technical installation
CN111343263B (zh) 批量私有云的运维系统和运维方法
CN113614016B (zh) 用于结合于建筑物的人员运送设施的安全装置
US11134399B1 (en) Connectivity apparatus for remote cell tower integration
US20020133634A1 (en) Thin client solutions with HMI systems
US20170220756A1 (en) Method and mobile unit updating the configuration of a medical technology apparatus without an internet connection
JP2009106121A (ja) 監視制御システム
CN105807740A (zh) 散货装卸设备远程服务系统
US11641344B2 (en) Secure remote maintenance devices and method, for remote maintenance of industrial equipment
HK40049110A (en) Method and system for commissioning of a communication gateway

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

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

AX Request for extension of the european patent

Extension state: BA ME

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: 20190423

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

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20200513

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: 20210324

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

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: DE

Ref legal event code: R096

Ref document number: 602017040651

Country of ref document: DE

Ref country code: AT

Ref legal event code: REF

Ref document number: 1404159

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210715

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20210623

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: 20210623

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: 20210623

Ref country code: BG

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: 20210923

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1404159

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20210623

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: 20210623

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: 20210923

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: 20210924

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: 20210623

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20210623

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: 20210623

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: 20210623

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: 20210623

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: 20210623

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: 20210623

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: 20210623

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: 20211025

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: 20210623

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: 20210623

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017040651

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20210623

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20220324

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

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: 20210623

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: 20210623

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

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: 20210623

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220421

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220421

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20170421

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

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: 20210623

Ref country code: CY

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: 20210623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

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: 20210623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

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: 20210623

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20250428

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20250422

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20250424

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: CH

Payment date: 20250501

Year of fee payment: 9