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
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B66—HOISTING; LIFTING; HAULING
  • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
  • B66B1/00—Control systems of elevators in general
  • B66B1/24—Control systems with regulation, i.e. with retroactive action, for influencing travelling speed, acceleration, or deceleration
  • B66B1/2408—Control systems with regulation, i.e. with retroactive action, for influencing travelling speed, acceleration, or deceleration where the allocation of a call to an elevator car is of importance, i.e. by means of a supervisory or group controller
  • B66B1/2458—For elevator systems with multiple shafts and a single car per shaft
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B66—HOISTING; LIFTING; HAULING
  • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
  • B66B5/00—Applications of checking, fault-correcting, or safety devices in elevators
  • B66B5/0006—Monitoring devices or performance analysers
  • B66B5/0018—Devices monitoring the operating condition of the elevator system
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B66—HOISTING; LIFTING; HAULING
  • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
  • B66B2201/00—Aspects of control systems of elevators

Definitions

• the invention relates to an elevator arrangement and particularly to elevator system group controllers for an elevator arrangement.
• elevator system group controllers Optimized and capacity of an elevator group in transporting people. As the buildings grow, elevator groups grow and several groups and even horizontal people flows needs to be managed simultaneously. Therefore, in large elevator groups an amount of data to be processed by the elevator system group controller is also large.
• the large amount of data means that the challenge of optimizing the people flow becomes complex and the demand for computing power is high for solving the optimization task in an acceptable time.
• the complexity of the optimization task may vary in time, for example the time of day, whereby the demand for computing power may have peaks.
• the physical resources in the elevator system group controller should be increased. However, this causes the elevator system group controller to take more space in the building the elevator group is deployed. In addition to the building having sufficient space for the elevator system group controller, the space should also be air-conditioned to keep the temperature within an operational range of the elevator system group controller.
• Some embodiments provide improvements comprising controlling an elevator group by a remote elevator system group controller.
• Some embodiments provide improvements to controlling an elevator group, when a connection to a remote elevator system group controller is down.
• Some embodiments provide improvements to adapting computing power dedicated to optimization of traffic flow.
• Figure 1 illustrates an elevator arrangement according to an embodiment
• Figure 2 illustrates architecture of an elevator arrangement comprising a local elevator system group controller and a remote elevator system group controller, according to an embodiment
• Figure 3 illustrates a method according to an embodiment
• Figure 4 illustrates operation on re-establishment of connection to a remote elevator system group controller.
• FIG. 1 illustrates an elevator arrangement 100 according to an embodiment.
• the elevator arrangement comprises an elevator group that includes a plurality of elevator cars 102, 122 movable between landing zones 104a, 104b, 124a, 124b that communicate traffic, e.g. people, to and from the elevator cars through doorways 110a, 110b, 130a, 130b.
• the elevator cars are supported by ropes in hoistways 112, 132 such that the elevator cars may be moved up or down the hoistways by hoisting machineries 113, 133 connected to the ropes.
• the hoistways may be located in a single shaft or separate shafts. In the illustration the elevator cars are located in separate shafts.
• Sensors 106a, 106b, 108a, 108b, 126a, 126b may be installed to the elevator arrangement for obtaining data on traffic and environment of the elevator arrangement.
• the sensors may be installed to the elevator cars, hoistways, doorways and landing zone for example.
• the sensors 106a, 106b, 126a, 126b are installed to ceilings in the landing zones to monitor traffic that enters the elevator car, leaves the elevator car or is waiting in the landing zone for arrival of the elevator car. Examples of sensors comprise optical sensors, radio frequency sensors, cameras and weight sensors.
• Operating panels 108a, 108b, 128a, 128b on the landing zones or in side elevator cars may also serve as sensors.
• the operating panel may include a user interface, for example one or buttons, a touch screen and/or a display.
• the operating panel provides a user to enter a destination landing zone to the elevator arrangement.
• the sensors may be connected to a Local Elevator System Group Controller (LESGC) 140 such that data from the sensors, for example destination landing zone may be used for traffic flow optimization in the elevator group.
• LESGC Local Elevator System Group Controller
• the connections between the sensors and the LESGC may be wired or wireless connections.
• Wireless connections may be implemented using devices capable of operating according to a Wireless Local Area Network standard defined by the IEEE 802.11 family of standards. Wired connections may be implemented by wiring, for example field buses and Ethernet connections. Both the wireless and wireless communications may be based on the Internet Protocol.
• the elevator car may be driven between the floors on the basis of the destination landing zone received via the operating panel.
• the elevator arrangement may comprise more than one operating panels that each may be used to enter a destination landing zone.
• the landing zone may have an operating panel installed to a wall.
• a typical operating panel in the landing zone is a button for indicating a destination landing zone that is higher or lower than the landing zone of the operating panel.
• Both operating panels in the landing zone and the in the elevator car may be capable of receiving a specific destination landing zone, e.g. defined by a number of the floor the landing zone is located in.
• the LESGC may perform traffic flow optimization in the elevator group on the basis of data from sensors in the elevator arrangement.
• the traffic flow optimization may comprise inputting the data from the sensors to a local operating model to determine actions in the elevator arrangement for traffic flow optimization.
• the actions in the elevator arrangement comprise controlling movement of the elevator cars between the landing zones.
• the LESGC may be connected to the hoisting machineries for issuing control commands to the hoisting machineries for driving the elevator cars between the landing zones.
• a LESGC may be connected to hoisting machinery over a secure connection.
• the security of the connection may be provided by a short distance and/or a dedicated communication path for the communications between the LESGC and the hoisting machinery. In this way the number of intermediate devices such as hosts, bridges and routers may be kept low.
• a landing zone may be located in one floor in a building where the elevator arrangement is installed.
• the landing zone refers to an area of the floor that communicates traffic with the elevator car through the doorway.
• the doorway may comprise a door such that the doorway may be closed, when the elevator car is not at the landing zone, but for example moving between the floors or stopped to another floor.
• FIG 2 illustrates an elevator arrangement 200 controllable by a local elevator system group controller 202 and a Remote Elevator System Group Controller 204 (RESGC), according to an embodiment.
• the LESGC may be installed to the elevator arrangement described in Figure 1 .
• the LESGC may be connected electrically to a memory (M) 206 and a Communications Unit (CU) 208 such that functionalities according to an embodiment may be caused.
• M memory
• CU Communications Unit
• the elevator arrangement In an example of implementation of the elevator arrangement, the
• LESGC, M and CU may be for example installed to the same instrument cabin, where they are connected by a communication bus within the instrument cabin.
• the CU provides transmission and reception of information between the elevator arrangement and the RESGC, and between the LESGC and the units of the elevator arrangement, for example one or more hoisting machineries (HMs) 210 and sensors.
• the connection to the RESGC may be an Internet Protocol connection over Ethernet connection.
• the RESGC may be located in an external network 216, for example the Internet. Connecting RESGC to the elevator arrangement provides that the elevator group in the elevator arrangement may be controller by the RESGC.
• the RESGC may be connected to one or more external data sources 212, 214 that provide information for traffic flow optimization in the elevator arrangement. Examples of the information provided by the external data sources comprise public transportation schedules, real-time data from traffic on the streets, real-time data form traffic on the roads, real-time data from the public transportation.
• the RESGC may be connected to the data sources over IP connections for example in the Internet.
• the external data source may comprise for example databases that may be accessed by the RESGC.
• the RESGC is implemented in a cloud computing system.
• the functionality of the RESGC may be executed by a plurality of computers in the cloud computing system.
• the cloud computing system provides adapting computing power dedicated to optimization of traffic flow. Accordingly resources may be flexibly allocated to the RESGC based on the complexity of traffic flow optimization tasks at hand, which may depend on an amount of traffic or on distribution of traffic to name a few.
• Figure 3 illustrates a method according to an embodiment.
• the method may be performed in an elevator arrangement of Figure 2.
• a LESGC or another control entity in the elevator arrangement may cause execution of the method steps.
• the method may start 302, when the elevator arrangement is deployed and operational.
• the connections illustrated in Figure 2 are configured and functional, thus data may be communicated over the connections.
• the connection between the elevator arrangement and the RESGC may be monitored. Monitoring of the connection facilitates determining when the RESGC can control the elevator group and when the RESGC cannot control the elevator group.
• the RESGC may control the elevator group when data from the sensors of the elevator arrangement can be received by the RESGC and the RESGC can send control commands and/or a new local operating model to the elevator arrangement.
• the monitoring may comprise monitoring an amount of traffic, size of data packets and/or type of data packets for example.
• the monitoring may be used to determine an amount of traffic in one direction or in both directions between the elevator arrangement and the RESGC. If the amount of traffic in either or both directions is below a threshold, it may be determined that the connection may be down. Polling messages, for example ping messages, may be sent in one or both directions to determine whether the connection is down.
• the size of data packets may be monitored to determine whether the connection between the elevator arrangement and the RESGC is down or up. When the size of data packets correspond to a size of data packets that are typical for error messages, it may be determined that the connection towards the sender of the data packets is down.
• the type of data packets may be identified as error messages or negative acknowledgement messages, whereby the connection towards the originator of such messages may be determined as being down.
• the method proceeds to 308, where traffic may be served by the elevator cars on the basis of the local operating model.
• the connection may be down, when traffic cannot be communicated in one or both directions on the connection.
• the connection may be down due to a broken device, cable or wire or due to a restart of a device that forms a part of the connection.
• the local operating model may be formed on the basis of data from the sensors within the elevator arrangement.
• the data may be input to the local elevator system group controller for forming the local operating model.
• the LESGC may be used by the LESGC for serving traffic when the connection to the RGC is down.
• the local operating model used by the LESGC for serving traffic when the connection to the RGC is down may be obtained from the RESGC when the connection to the RESGC is up, i.e. prior to the connection being down.
• connection between the elevator arrangement and the RESGC traffic may be served 310 by the elevator cars as controlled by the RESGC, when the connection is up.
• a connection may be up, when traffic may be communicated in both directions on the connection.
• the RESGC may control the elevator cars on the basis of a remote operating model.
• the controlling may comprise sending control commands to the elevator arrangement.
• the elevator control commands may be direct commands to drive the elevator car or the control commands may be a drive profile file that includes parameters for driving the elevator cars.
• data from the sensors of the elevator arrangement can be received by the RESGC and used to update the remote operating model.
• traffic may be served 308, 310 according to the remote operating mode or the local operating model and monitoring 304 of the connection may be continued.
• the RESGC may obtain data from the sensors in the elevator arrangement and the external data sources, when the connection between the RESGC and the elevator arrangement is up.
• the obtained data are input to the RESGC that may process the data and form a remote operating model.
• the remote operating model may be updated on the basis of the data form the sensors as well as data form the external data sources.
• the RESGC may combine the data from the elevator arrangement and external data sources for updating the remote operating model.
• the remote operating model may be used to determine control commands to the elevator arrangement for controlling the elevator group, e.g. driving the elevator cars.
• the local operating model may be updated on the basis of the remote operating model.
• the RESGC may form a new local operating model on the basis of the remote operating model.
• the new local operating model may be communicated to the elevator arrangement.
• the elevator arrangement may use an operating model that is formed on the basis of data sources from the elevator arrangement as well as external data sources even if connection to the remote elevator arrangement is down.
• the local operating model may require less computational power than the remote operating model.
• the local operating model may have less parameters than the remote operating model. Since the local operating model is formed on the basis of data sources that are internal to the elevator arrangement as well as external data sources, the local operating model may be optimized for the elevator arrangement such that traffic in the elevator arrangement may be served efficiently even if the connection to the RESGC is down.
• Figure 4 illustrates operation on re-establishment of connection to a RESGC.
• the operation may be performed in an elevator arrangement of Figure 1 , for example by the LESGC.
• the re-establishment of connection to the RESGC may start 402 after it has been determined that a connection to the RESGC is down, for example in step 308 in Figure 3.
• data from sensors in the elevator arrangement may be obtained. The data may be buffered for later use.
• the buffered data may be sent 408 to the RESGC.
• the buffered data may be used to update the remote operating model and/or to determine a new local operating model.
• the connection may be determined to be up on the basis of monitoring the connection as described in step 304 in Figure 3.
• connection If 406 the connection is not up, the buffering of data may be continued and the method proceeds to 402.
• the connection may be determined to be down on the basis of monitoring the connection as described in step 304 in Figure 3.
• Implementations of an elevator arrangement, a RESGC or a LESGC may comprise a central processing unit (CPU).
• the CPU may comprise a set of registers, an arithmetic logic unit, and a control unit.
• the control unit is controlled by a sequence of program instructions transferred to the CPU from the memory.
• the control unit may contain a number of microinstructions for basic operations.
• the implementation of micro- instructions may vary, depending on the CPU design.
• the program instructions may be coded by a programming language, which may be a high-level programming language, such as C, Java, etc., or a low-level programming language, such as a machine language, or an assembler.
• the memory may be a volatile or a non-volatile memory, for example EEPROM, ROM, PROM, RAM, DRAM, SRAM, firmware, programmable logic, etc.
• the memory and the controller may be connected by an electrical connection provided e.g. by a printed circuit board, where the memory and the controller are installed.
• the LESGC and the RESGC may include or be connected to a memory that may store an operating model to be used in controlling an elevator group.
• An embodiment provides a computer program embodied on a distribution medium, for example a non-transitory computer readable storage medium, comprising program instructions which, when loaded into an electronic apparatus, cause the controller to perform a method according to an embodiment.
• the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
• Such carriers include a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
• the computer program may be executed in a single electronic digital computer or processor or it may be distributed amongst a number of computers or processors.
• Execution of the computer program or a computer program product for a computer causes execution of a method according to an embodiment.
• an elevator arrangement implementing one or more functions described with an embodiment comprises not only prior art means, but also means for monitoring a connection to the RESGC, and serving traffic by the elevator cars on the basis of the local operating model, when the connection is down, and serving traffic by the elevator cars as controlled by the RESGC, when the connection is up.
• the various means comprise means for implementing functionality of a corresponding elevator arrangement described with an embodiment and it may comprise separate means for each separate function, or means may be configured to perform two or more functions.
• these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof.
• firmware or software implementation can be through modules (e.g., procedures, functions, and so on) that perform the functions described herein.
• the software codes may be stored in any suitable, processor/computer-readable data storage medium(s) or memory unit(s) or article(s) of manufacture and executed by one or more processors/computers.
• the data storage medium or the memory unit may be implemented within the processor/computer or external to the processor/computer, in which case it can be communicatively coupled to the processor/computer via various means as is known in the art.

Landscapes

• Engineering & Computer Science (AREA)
• Automation & Control Theory (AREA)
• Computer Networks & Wireless Communication (AREA)
• Indicating And Signalling Devices For Elevators (AREA)
• Elevator Control (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=55629467

Family Applications (1)

Country Status (4)

Families Citing this family (4)

Family Cites Families (18)

• 2014
  • 2014-10-01 EP EP14903069.4A patent/EP3201115A4/de active Pending
  • 2014-10-01 WO PCT/FI2014/050747 patent/WO2016051011A1/en active Application Filing
  • 2014-10-01 CN CN201480082297.9A patent/CN107074483B/zh active Active
• 2017
  • 2017-03-02 US US15/448,061 patent/US10640327B2/en active Active

Also Published As

Similar Documents

Legal Events