EP3728094A1 - Route planning on the basis of expected passenger number - Google Patents
Route planning on the basis of expected passenger numberInfo
- Publication number
- EP3728094A1 EP3728094A1 EP18814970.2A EP18814970A EP3728094A1 EP 3728094 A1 EP3728094 A1 EP 3728094A1 EP 18814970 A EP18814970 A EP 18814970A EP 3728094 A1 EP3728094 A1 EP 3728094A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- call
- destination
- passengers
- floor
- destination call
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 claims description 22
- 238000005516 engineering process Methods 0.000 description 14
- 230000006854 communication Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 6
- 238000011156 evaluation Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 241000599985 Beijerinckia mobilis Species 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000007728 cost analysis Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 230000036962 time dependent Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- 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
- 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/2416—For single car elevator systems
-
- 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
- B66B1/3461—Data transmission or communication within the control system between the elevator control system and remote or mobile stations
-
- 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/46—Adaptations of switches or switchgear
- B66B1/468—Call registering systems
-
- 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/0012—Devices monitoring the users of the elevator 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
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B2201/00—Aspects of control systems of elevators
- B66B2201/10—Details with respect to the type of call input
- B66B2201/103—Destination call input before entering the elevator car
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B2201/00—Aspects of control systems of elevators
- B66B2201/20—Details of the evaluation method for the allocation of a call to an elevator car
- B66B2201/222—Taking into account the number of passengers present in the elevator car to be allocated
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B2201/00—Aspects of control systems of elevators
- B66B2201/20—Details of the evaluation method for the allocation of a call to an elevator car
- B66B2201/23—Other aspects of the evaluation method
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B2201/00—Aspects of control systems of elevators
- B66B2201/40—Details of the change of control mode
- B66B2201/46—Switches or switchgear
- B66B2201/4607—Call registering systems
- B66B2201/4615—Wherein the destination is registered before boarding
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B66—HOISTING; LIFTING; HAULING
- B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
- B66B2201/00—Aspects of control systems of elevators
- B66B2201/40—Details of the change of control mode
- B66B2201/46—Switches or switchgear
- B66B2201/4607—Call registering systems
- B66B2201/463—Wherein the call is registered through physical contact with the elevator system
Definitions
- the technology described here relates generally to an elevator system having a
- Embodiments of the technology also relate to a method for operating such an elevator system.
- elevator systems In order for a passenger to call an elevator, elevator systems are known which either have a floor terminal for entering the desired direction of travel (eg, "up” and “down” buttons) or a floor terminal for entering the desired destination floor. The latter allow elevator systems with a destination call control, which allocates an elevator car of a passenger an elevator car to transport the passenger to a desired destination floor.
- An embodiment of an elevator system with a destination call control is disclosed in document EP 0 443 188 B1; the
- Destination call control allocates elevator calls based on calculated service costs and variable bonus / penalty factors. Such allocation procedures are based on the assumption that each passenger has one
- EP 1 522 518 Bl and US 2016/0297642 A1 describe the measured load in the elevator car.
- the bypass function can not be activated when the floor is the destination of a passenger in the cabin.
- the solutions mentioned with the bypass function u. Avoiding an already full elevator car stops on a floor on which no passengers can get on, it leads to a possibly significantly increased waiting time for the waiting passengers. In a destination call control, said elevator car must return to this floor because it has been allocated to the passengers; it is not easy to choose another elevator car, which could possibly serve the passengers earlier.
- the bypass function can therefore lead to a large delay in the journey, which can frustrate the passengers; the waiting passengers may therefore be able to enter new elevator calls, possibly also to destinations that do not correspond to their actual destination, just to finally board an elevator car. This can cause further disadvantages for other passengers.
- One aspect of such an improved technology relates to a method of operating an elevator system in a building, the elevator system having a
- Destination call control device and an elevator car which is movable between floors of the building and has a fixed passenger capacity contains.
- a first destination call entered on a floor by a first passenger at a first time is evaluated in order to determine a first call information from the first destination call.
- the first call information contains information about a call input floor and / or a destination floor.
- the first call information it is determined whether the number of additional passengers is to be assigned to the first destination call, whereby an additional space requirement results in the number of additional passengers in an elevator car serving the first destination call.
- Information on the additional space requirement is generated if the first destination call has a Number of additional passengers. If a number of additional passengers are to be assigned to the first destination call, the first destination call is subordinated by means of an allocation algorithm
- the elevator system comprises an elevator car which is movable between floors of the building and has a fixed passenger capacity.
- a destination call control device is configured, in order to evaluate a first destination call entered on a floor by a first passenger at a first time in order to obtain a first destination call from the first destination call
- Destination call control device is also designed to be by means of the first
- Passengers is assigned, resulting in the number of additional passengers an additional space in a first destination call serving elevator car.
- the destination call controller is further configured to provide information about
- the first destination call by means of a
- the destination call controller makes an assumption about a number of additional passengers who want to be transported together with a calling passenger without themselves inputting a destination call and have a corresponding space requirement in the elevator car. Based on data stored in a database on the passenger behavior on the floors, the technology differs from the usual approach that for each destination call a space requirement for a
- the data stored in the database can be organized in different ways.
- the database is in one
- Each record has a predefined description of a call situation Data fields, where a first data field indicates the call input floor, a second data field a time window, a third data field the destination floor and a fourth data field the number of additional passengers for the call situation described in the data record.
- the technology described here determines whether a number of additional passengers are to be assigned to the first destination call.
- the database is accessed and determined as to whether the first destination call corresponds to a call situation stored in the database. If this is the case, this results for the call situation given by the first destination call
- the elevator system includes a
- a sensor system coupled to the destination call controller and the storage device.
- the sensor system determines information about a number of passengers boarding the elevator car on a floor.
- the sensor system can, for.
- the sensor system may be used to determine the number of additional passengers indicated in the fourth data field.
- the sensor system includes sensors located on the floors that communicate with the person via a line
- a sensor of the sensor system comprises in one embodiment a camera, and the
- the destination call control device is further configured to adapt the information generated for additional space requirements by means of the information ascertained by the sensor system to the number of passengers entering and to provide the information adapted to the operation of passengers to use additional space.
- the planning of the operating order of passengers can be improved because, for. B. the (assumed) additional space requirements can be increased or decreased by means of the number of actually boarding passengers.
- the space requirement of the first passenger is increased by the space requirement of the additional passengers for the allocation of the first destination call.
- the resulting total space requirement is fed to the allocation algorithm.
- the allocation algorithm does not have to be extended or otherwise changed in comparison with known methods since the modification of the space requirement takes place independently of the allocation algorithm.
- the additional space information is kept separate from the first destination call; both are fed separately to the allocation algorithm. It is an advantage that the
- Typical planning steps are calculating the space requirements for passengers waiting on a floor, or calculating the space requirements for passengers, which could be transported together in the elevator car at the same time.
- the individual normal and the individual additional space requirements can be taken into account for each of the passengers considered , For example, if a number of destination calls are entered from different passengers at the first time, the space allocated for the destination calls is based on the space required, for one passenger per destination call, from the number of destination calls and a maximum number of additional passengers , In this case, a number of additional passengers is determined for each destination call and decimal destination call to which the maximum number of additional passengers is assigned. This allows the maximum number of additional passengers to be determined.
- the maximum number of additional passengers is equal to three. This has the advantage that at too few calls with more space is expected, but with enough many calls no unnecessary additional space requirement is more into account.
- Destination calls are based on a space requirement which, with one passenger per destination call, per destination floor results from the number of destination calls and a maximum number of additional passengers. In this case, a number of additional passengers is determined for each destination call and each destination floor and determines a maximum value of the additional space required per destination floor; the resulting maximum values are added.
- This has the advantage that no unnecessary additional space is scheduled for passengers with the same destination with multiple calls, but is expected for passengers with different destinations each with additional passengers traveling and thus enough space is scheduled.
- FIG. 1 is a schematic representation of an embodiment of an elevator system in a building
- Fig. 2 is an exemplary illustration of an embodiment of a
- FIG. 3 shows an exemplary representation of an exemplary embodiment of a method for allocating a destination call on the basis of a schematic flowchart.
- Fig. 1 shows a schematic representation of an embodiment of a
- Elevator system 1 in a building 2 can be any type of multi-storey building (eg residential building, hotel, office building, sports station, etc.) or a ship
- the building 2 shown in Fig. 1 has a plurality of floors L1, L2, L3, which are served by the elevator system 1, that is, a passenger 4 can from the elevator system 1 from a boarding floor on a Destination floor.
- the boarding floor is also called
- the elevator system 1 has an elevator car 10 which can be moved in an elevator shaft 18 and is connected to a drive unit (DR) 14 via a suspension element 16 (cables or belts) and is suspended from this drive unit 14. It may be a traction elevator, with further details, such as a counterweight and guide rails in Fig. 1 are not shown.
- the elevator control (EC) 12 is connected to the drive unit 14 and controls the drive unit 14 to move the elevator car 10 in the shaft 18.
- the function of a traction elevator, its components and the tasks of an elevator control 12 are well known to those skilled in the art.
- the elevator system 1 may comprise a hydraulic elevator.
- the elevator system 1 may comprise multiple cabins, or one or more groups of elevators.
- the elevator system 1 shown in FIG. 1 is equipped with a destination call control device whose function is implemented in the control device (CTRL) 8 in the embodiment shown.
- CTRL control device
- the control device 8 is also referred to as
- Destination call control 8 or destination call control device 8 denotes.
- Controller 8 may in one embodiment be fully or partially implemented in elevator controller 12. If the elevator system 1 comprises one or more groups of elevators, the destination call controller 8 or its function can be implemented in an elevator group controller. The destination call controller 8 informs a destination call of a passenger 4 inputted to a terminal 5 of the floor of one of u. U. several elevator cars 10 and communicates the corresponding
- Elevator system the load, the location and the operating status of an elevator car, the Operating status of a drive knows and additional information over the past
- the described destination call allocation algorithm divides newly entered destination calls in the sense of predetermined criteria as optimally as possible to the elevators. These criteria are essentially functional requirements for the call operation.
- the basis of the destination call allocation are calculations of the
- Fig. 2 shows an exemplary representation of an embodiment of a
- Destination call control device 8 more functional units, eg. Legs
- Call allocation unit 36 a storage device 34 with a database 28 and a processor 30 which controls the destination call control unit 8.
- the processor 30 has an output 32 which is connected to the communication bus 24.
- the technology described here is advantageously applicable to operate the elevator system 1 with the highest possible efficiency and best possible comfort for the passengers 4 (especially with respect to the waiting time).
- the operation of the elevator system 1 is as follows: If a passenger 4 ("calling passenger 4") calls an elevator car 10 on a floor L1, L2, L3 by entering a destination call, the destination call controller 8 makes an assumption a number of passengers 4 who want to be transported together with the calling passenger 4 and have a corresponding space requirement in the elevator car 10. This assumption is based on stored
- the data can be obtained from observations of the behavior of the passengers 4 (empirical values) or with the help of a self-learning system and z.
- the destination call controller 8 makes such an assumption for each further destination call which is entered on another floor L1, L2, L3 and u. U. together with the previously entered destination call can be operated. Since each elevator car 10 can only accommodate a limited number of passengers 4, the destination call controller uses the assumptions made for the call allocation and the planning of a journey.
- the assumptions may, for example, lead the planning to rule out an elevator car 10 that is cheap with regard to the operating costs, although it might still have room for a few passengers 4, and allocates instead an elevator car 10 from the outset, which is unfavorable in terms of costs but has more space for the expected passengers 4.
- the destination call control uses assumptions that are in one
- Embodiment based on stored data. These data are stored in the database 28 of the memory device 34 shown in FIG.
- the database 28 stores a plurality of records, each record being predefined, one
- FIG. 2 shows, by way of example, four data fields, the number of which may be larger or smaller in other exemplary embodiments.
- a first data field specifies the call input floor, a second data field
- Time window a third data field, the destination floor and a fourth data field, the number of additional passengers (4) for the call situation described in the record.
- Data contained in database 28 may be organized, for example, according to the exemplary structure shown in the following table (Table 1).
- Table 1 The table can be called a look-up table.
- the information in the table and its organizational structure are to be understood as exemplary.
- Passengers 4 should be present at their workplaces between 7:00 and 7:30.
- the destination call control can allocate the destination call to an elevator car 10 in a known manner (eg, after a cost analysis)
- Floor Ll on the floor L3 performs.
- z there is another (second) destination call, z.
- the destination call controller may initiate the call arbitration from the basic assumption (one passenger per destination call) , Is it in this
- the destination call controller 8 may allocate the destination call of that passenger 4 to the elevator car 10 allocated for the transportation of the six passengers 4 (first destination call) to the floor L3. On the floor Ll rise thus seven passengers 4 in the elevator car 10 a.
- Destination call (six passengers 4) assigned elevator car 10 with a capacity of eight people can no longer accommodate the waiting on the floor L2 five passenger 4 (third destination call).
- the destination call controller 8 may allocate the first and third destination calls to the same elevator car 10 and schedule the trips so that the elevator car 10 is first moved from floor Ll to floor L3 to the first destination call and then from floor L3 to floor L2 to serve the third destination call.
- the sequence of serviced floors in this case may be the same as for systems with the above-mentioned bypass function, the method and its effect are different: the bypass function may only operate under certain circumstances (for example, if no passengers Floor Ll drive to floor L2) prevent the cabin stops on floor L2, where there is not enough space for boarding passengers waiting there, and will also lead to markedly longer waiting times for the passengers waiting on floor L2.
- Table 1 also shows a situation (line 4) that may arise in an office building around lunchtime.
- line 4 For a destination call entered on floor L3 in a time window between 11: 30-12: 30 on floor Ll becomes
- the call situations indicated in Table 1 can be determined from observations of the behavior of the passengers 4 within a specified period of time.
- the fixed period may be, for example, one or two months (or longer), the observations z.
- At intervals of one week i.e., 7 days observation, 7 days interruption).
- the observations may, for example, be recorded by one or more persons documenting the passenger behavior per floor L1, L2, L3 as a function of the time of day and the day of the week.
- Observations may u. U. supplemented by surveys of passengers 4. With the help of these observations, the time windows can be set and the number of times additional passengers 4 (eg, by means of determining the average) are determined. Such observations can be documented for all floors L1, L2, L3 or only for selected floors L1, L2, L3. As a result, it is possible to determine time-dependent behavior patterns with regard to elevator usage for each floor L1, L2, L3. If the complete table 1 is present, the elevator system 1 can be configured accordingly. Those skilled in the art will recognize that Table 1 may be updated as the use of Building 2 and thus the patterns of behavior change, e.g. B. if a previously unused floor Ll, L2, L3 is used by a company with a large number of people.
- the passenger behavior can be determined by means of a sensor system.
- the sensor system is representatively represented by sensors 6, wherein on each floor Ll, L2, L3 a sensor 6 is arranged, which is connected to a line 22.
- the sensor system can supplement or replace the observations mentioned by persons (it can be used as self-learning
- the sensor system includes, for. B. a counter that determines the on a floor Ll, L2, L3 entering the elevator car 10 passengers 4.
- the counting device may comprise a camera (eg for image recordings in the visible optical spectrum or in the infrared range) in conjunction with an image processing device which determines the number of passengers 4 from the image recordings.
- the counting device may use a load measuring device of the elevator car 10 to determine the number of passengers 4 going to the floor Ll, L2, L3 in question. In addition to this information provided by the counter, the
- the sensor system is communicatively connected to the destination call controller 8.
- the destination call controller 8 may use the information acquired by the sensor system to determine the destination call Planning to improve the operation further, z. B. by the additional space required by currently waiting or transported in an elevator passengers increased or decreased.
- the destination call control according to Table 1 initially makes the assumption that in the case of a (first) destination call on the floor Ll between 7:00 and 7:30 on the destination floor L3 with five additional passengers 4, so a total of six passengers.
- the destination call control can reduce the additional space requirement of five to an additional passenger and re-assess the situation, eg. B. plan for a stop on floor L2, if there is enough space for passengers to get there.
- Sensor system and the destination call control 8 separately acquired information can be later brought together and examined, for. B. in a use for it
- Table 1 may be updated by the sensor system, for example, as needed or according to a predetermined schedule.
- FIG. 3 shows an example
- the method according to FIG. 3 starts in a step S1 and ends in a step S8.
- the method initially waits to receive a destination call (steps S2 and S3). If a passenger 4 at a floor terminal 5 inputs a destination call, this is received by the destination call evaluation unit 26 of the destination call controller 8.
- the destination call evaluation unit 26 can receive several destination calls simultaneously or within a short period of time.
- the received destination call is evaluated to determine call information. In the case of multiple destination calls, each destination call is evaluated.
- Criteria for the evaluation are, for example, the call input floor, the destination floor or the time of the destination call, or combinations thereof. Point of time the destination call is z. B. recorded as time and calendar date.
- the call information comprises, for example, the call input floor and / or the destination floor.
- an additional space requirement in the elevator car 10 is determined by means of the call information. This determination of the additional space requirement uses the data stored in the database 28, which are organized in an embodiment according to Table 1.
- the processor 30 checks whether the received destination call (or its criteria) corresponds to a call situation documented in Table 1. If this is the case, the additional space required results from the number of additional passengers 4 indicated in Table 1 for this call situation.
- the information of the destination call is modified with the additional space requirement determined in step S5 (variant A). From each destination call results implicitly or explicitly information about what space is required in the elevator car 10 for the relevant destination call.
- the "normal" space requirement is z. B. per destination call space for a passenger.
- step S6 the information of the destination call is supplemented with the additional space requirement determined in step S5 (variant B).
- the information about the normal space requirement of the input destination call and the information determined for additional space requirements are kept separate and passed both for the call allocation (step S7).
- step S7 the method determines the allocation of the destination call.
- the method performs an allocation algorithm for this; such allocation algorithms are known in the art, s. for example, the above-mentioned document EP 0 443 188 B1 or the above-mentioned book by G. C. Bamey et al. According to variant A, the
- Variant B differs in the call allocation of variant A in that the
- Call allocation is not simply based on the space required in the elevator car 10, which results from adding up the normal space requirements and additional space requirements. This difference arises, for example, when a destination call of a passenger 4 is to be allocated on a floor L1, L2, L3, on which one or more other passengers 4 have already been allocated to the elevator car 10.
- variant B is in
- Step S7 does not simply add up the normal and additional space requirements of the calling passengers 4, but handles them separately.
- the normal space requirement may be added up (eg, four destination calls will give a normal footprint for four passengers 4), but the additional footprint of the passengers may be limited to the maximum additional footprint of a single passenger.
- Typical planning steps are calculating the space requirement for passengers 4 waiting on a floor L1, L2, L3, or calculating the space requirement for passengers which could be transported together in the elevator car 10 simultaneously.
- the individual normal and the individual additional space requirements are taken into account in the example already mentioned above, the space requirement of all considered passengers was determined so that the sum of the normal space requirement of the passengers and the maximum of the additional space requirement of the passengers are added together.
- the maximum of the additional space requirement could first be determined per destination and these values could be added together across all destinations; This has the advantage that for passengers with the same destination with multiple calls no unnecessary additional space is scheduled, but for passengers with different destinations in each case with additional passengers traveling is expected and thus enough space is scheduled.
- Floor terminals 5 are z. B. in the vicinity of elevator doors 6 and communicatively connected to the control device 8 via the line 22.
- the building 2 has three floors L1, L2, L3 and on each floor there is a floor terminal 5. But there may also be only two or more than three floors; it is also possible that on one floor
- the destination call control device 8 is communicatively connected to the elevator controller 12 and the floor terminals 5 as described above.
- communicative connection is meant in this specification a direct or indirect connection that allows unidirectional or bidirectional communication between two entities.
- data signals and / or control signals are transmitted in a manner known per se.
- Such a connection may be through an electrical line system (either as a point-to-point connection system or as a bus system where the units connected to the bus system are addressable)
- the communicative connection is exemplified by lines 20, 22, wherein the line 20 between the communication bus 24 and the car 10 and the line 22 connects the floor terminals 5 with the control device 8.
- the conduit 22 may be a
- the line 20 may be a communication bus system.
- At least one floor terminal 5 may be communicatively connected to the destination call control device 8 via a radio system.
- a mobile electronic device eg, mobile phone, smartphone, smartwatch, tablet PC
- the mobile device may also display a message (eg, "Elevator A") about the elevator assigned to this destination call.
- the mobile electronic device has a radio module, for example a Bluetooth, an RFID and / or an NFC module.
- the destination call control device 8 or its functionality can also be part of the elevator control 12 or of a floor terminal 5. In such a case, for example, the separate representation of the control device 8 in Fig. 1 could be omitted. If the destination call control device 8 or its functionality is integrated into the elevator control 12, the elevator control 12 represents the control device. Depending on the configuration, therefore, the implementation of the communicative connections also changes.
- Fig. 1 is thus to be understood as a schematic representation of an embodiment of the elevator system 1.
- a floor terminal 5 is arranged on each floor L1, L2, L3, for example in the area of access to an elevator car 10.
- the floor terminal 5 comprises a keyboard or a touch-sensitive screen (touchscreen) such that a passenger 4 enters
- the floor terminal 5 comprises a device for recognizing a destination call.
- this device is a reader for a carried by a passenger 4 information carrier. If the passenger 4 presents the information carrier to the reading device, the reading device reads information from the information carrier, which serves, for example, to recognize an operating authorization. Only when the passenger 4 is authorized to operate the input terminal 5 can the passenger 4 make an entry. Depending on the configuration, a destination call can also be triggered with the information read without further intervention by the passenger 4.
- the information carrier is designed to be similar to a card, for example in the form of a credit card or an employee card.
- an externally contactable memory chip, an RFID transponder in conjunction with a is located in or on the information carrier
- Memory chip or external (optically) readable code eg. As alphanumeric characters, a QR code or a bar code (barcode).
- a QR code e.g. As alphanumeric characters, a QR code or a bar code (barcode).
- Color pattern codes are displayed. Such devices also allow one
- Radio connection with other electronic devices for example via known wireless technologies such as Bluetooth, WLAN / WiFi or NFC.
- wireless technologies such as Bluetooth, WLAN / WiFi or NFC.
- Floor Terminals 5 is compatible with the technology used
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PL18814970T PL3728094T3 (en) | 2017-12-21 | 2018-12-13 | Trip planning due to expected passenger number |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17209784 | 2017-12-21 | ||
PCT/EP2018/084784 WO2019121329A1 (en) | 2017-12-21 | 2018-12-13 | Route planning on the basis of expected passenger number |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3728094A1 true EP3728094A1 (en) | 2020-10-28 |
EP3728094B1 EP3728094B1 (en) | 2022-03-09 |
Family
ID=60781963
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18814970.2A Active EP3728094B1 (en) | 2017-12-21 | 2018-12-13 | Trip planning due to expected passenger number |
Country Status (7)
Country | Link |
---|---|
US (1) | US20210047144A1 (en) |
EP (1) | EP3728094B1 (en) |
CN (1) | CN111386236B (en) |
AU (1) | AU2018389637B2 (en) |
ES (1) | ES2915498T3 (en) |
PL (1) | PL3728094T3 (en) |
WO (1) | WO2019121329A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3365630B1 (en) * | 2015-10-19 | 2024-01-24 | KONE Corporation | Smartwatch and elevator and guide system |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3973649A (en) * | 1974-01-30 | 1976-08-10 | Hitachi, Ltd. | Elevator control apparatus |
US4149613A (en) * | 1975-11-04 | 1979-04-17 | Hitachi, Ltd. | Elevator control system |
DE59004802D1 (en) | 1990-02-22 | 1994-04-07 | Inventio Ag | Method and device for the immediate assignment of destination calls to elevator groups, based on operating costs and variable bonus / malus factors. |
GB2266602B (en) * | 1992-04-16 | 1995-09-27 | Inventio Ag | Artificially intelligent traffic modelling and prediction system |
FI98720C (en) * | 1992-05-07 | 1997-08-11 | Kone Oy | Procedure for controlling an elevator group |
JP2003221169A (en) * | 2002-01-29 | 2003-08-05 | Mitsubishi Electric Corp | Elevator control device |
WO2005009879A1 (en) * | 2003-06-23 | 2005-02-03 | Otis Elevator Company | Elevator dispatching with balanced passenger perception of waiting |
EP1522518B1 (en) | 2003-10-10 | 2013-06-19 | Inventio AG | Elevator system and method for controlling an elevator system |
JP4388546B2 (en) * | 2006-12-28 | 2009-12-24 | 株式会社日立製作所 | Elevator group management system and service elevator guidance display method |
FI119686B (en) * | 2007-10-11 | 2009-02-13 | Kone Corp | Lift system |
WO2009078834A1 (en) * | 2007-12-17 | 2009-06-25 | Otis Elevator Company | Elevator system traffic profile generator |
ES2578524T3 (en) * | 2008-01-17 | 2016-07-27 | Inventio Ag | Procedure for assigning calls from an elevator installation, and elevator installation with a call assignment according to this procedure |
JP5461522B2 (en) * | 2008-03-31 | 2014-04-02 | オーチス エレベータ カンパニー | Elevator car allocation control strategy |
JP5218556B2 (en) * | 2008-05-21 | 2013-06-26 | 三菱電機株式会社 | Elevator group management system |
JP5504060B2 (en) * | 2010-06-08 | 2014-05-28 | 株式会社日立製作所 | Destination floor reservation group management elevator controller |
US8950555B2 (en) * | 2011-04-21 | 2015-02-10 | Mitsubishi Electric Research Laboratories, Inc. | Method for scheduling cars in elevator systems to minimize round-trip times |
WO2014111127A1 (en) * | 2013-01-15 | 2014-07-24 | Kone Corporation | Elevator group |
JP2014189338A (en) * | 2013-03-26 | 2014-10-06 | Hitachi Ltd | Elevator system |
WO2016038242A1 (en) * | 2014-09-12 | 2016-03-17 | Kone Corporation | Call allocation in an elevator system |
US10239728B2 (en) | 2015-04-09 | 2019-03-26 | Carrier Corporation | Intelligent building system for providing elevator occupancy information with anonymity |
JP6445401B2 (en) * | 2015-07-03 | 2018-12-26 | 株式会社日立製作所 | Elevator group management system |
CN107176511B (en) * | 2016-03-09 | 2021-03-16 | 奥的斯电梯公司 | Call control device, call control system and call control method thereof |
-
2018
- 2018-12-13 PL PL18814970T patent/PL3728094T3/en unknown
- 2018-12-13 EP EP18814970.2A patent/EP3728094B1/en active Active
- 2018-12-13 US US16/955,327 patent/US20210047144A1/en active Pending
- 2018-12-13 ES ES18814970T patent/ES2915498T3/en active Active
- 2018-12-13 WO PCT/EP2018/084784 patent/WO2019121329A1/en unknown
- 2018-12-13 AU AU2018389637A patent/AU2018389637B2/en active Active
- 2018-12-13 CN CN201880076128.2A patent/CN111386236B/en active Active
Also Published As
Publication number | Publication date |
---|---|
AU2018389637A1 (en) | 2020-05-07 |
WO2019121329A1 (en) | 2019-06-27 |
CN111386236B (en) | 2022-04-22 |
ES2915498T3 (en) | 2022-06-22 |
AU2018389637B2 (en) | 2021-11-04 |
PL3728094T3 (en) | 2022-06-27 |
CN111386236A (en) | 2020-07-07 |
US20210047144A1 (en) | 2021-02-18 |
EP3728094B1 (en) | 2022-03-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE112009002258B4 (en) | Elevator group management system | |
DE112016001246T5 (en) | System and control for allocating space in elevator cabins | |
EP2421782B1 (en) | Method for location-specific person management in a building | |
EP1041032B1 (en) | Procedure of communicating with a transportation system | |
DE102017109164A1 (en) | Personal security and privacy features for passengers of an autonomous vehicle based transport system | |
EP3261973A1 (en) | Elevator system with adaptive door control | |
DE112012006589T5 (en) | Demand vehicle operation management device, demand vehicle operation management method and demand vehicle operation management system | |
EP1970342A1 (en) | Display device and communication method for a lift system | |
DE102018129072A1 (en) | SYSTEMS AND METHOD FOR DYNAMIC MANAGEMENT OF A SHUTTLE LOAD | |
DE102017011694B4 (en) | Transport system and method for operating a transport system | |
WO2020212061A1 (en) | Method for predicting a traffic situation for a vehicle | |
DE102014209552A1 (en) | Procedure for checking a person authorization | |
DE112016004137T5 (en) | lift system | |
EP3728094B1 (en) | Trip planning due to expected passenger number | |
DE112021003100T5 (en) | Method for managing distribution of a vehicle traveling to the arrival point, management server used therefor, and recording medium on which program for executing the method is recorded | |
WO2016128091A1 (en) | Data acquisition system for determining passenger numbers in public means of transport | |
WO2017016878A1 (en) | Elevator system having a multi-deck-cab elevator | |
DE19539477A1 (en) | Process for automated, optimal redundancy design of measurements for control technology in power plants | |
DE102018208701A1 (en) | Apparatus and method for assisting a customer in requesting a service mobile | |
DE102019208752B4 (en) | Method for operating a vehicle and vehicle | |
DE102013210027B4 (en) | OCCUPANCY DETECTION SYSTEM FOR VEHICLES, END CUSTOMER INFORMATION DEVICE, PROCEDURE AND VEHICLE | |
WO2021121819A1 (en) | Method for allocating seats in a land vehicle | |
WO2022159995A1 (en) | Transfer system for transferring objects in a temporally decoupled manner | |
DE102016214414A1 (en) | METHOD AND SYSTEM FOR PROVIDING A MOTOR VEHICLE | |
DE102006053391A1 (en) | Processing time point allocating arrangement for airport enterprise, has system server and server of instances, where allocation is made by server of instances, using information of instances and information provided to server of instance |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
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: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20200403 |
|
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 |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
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: 20211022 |
|
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: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 1474006 Country of ref document: AT Kind code of ref document: T Effective date: 20220315 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 502018009062 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2915498 Country of ref document: ES Kind code of ref document: T3 Effective date: 20220622 |
|
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: 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: 20220309 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: 20220609 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: 20220309 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: 20220309 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: 20220609 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20220309 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: 20220610 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: 20220309 |
|
RAP4 | Party data changed (patent owner data changed or rights of a patent transferred) |
Owner name: INVENTIO AG |
|
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: 20220309 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: 20220309 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: 20220309 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: 20220711 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: 20220309 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: 20220309 |
|
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: 20220709 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: 20220309 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 502018009062 Country of ref document: DE |
|
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 |
|
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: 20220309 |
|
26N | No opposition filed |
Effective date: 20221212 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI 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: 20220309 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: PL Payment date: 20221201 Year of fee payment: 5 Ref country code: BE Payment date: 20221226 Year of fee payment: 5 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20230118 Year of fee payment: 5 Ref country code: CH Payment date: 20221228 Year of fee payment: 5 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20221227 Year of fee payment: 5 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230521 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20221213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20221213 |
|
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: 20221213 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20221213 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: SE Payment date: 20231222 Year of fee payment: 6 Ref country code: NL Payment date: 20231226 Year of fee payment: 6 Ref country code: IT Payment date: 20231221 Year of fee payment: 6 Ref country code: FR Payment date: 20231226 Year of fee payment: 6 Ref country code: AT Payment date: 20231219 Year of fee payment: 6 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: PL Payment date: 20231201 Year of fee payment: 6 Ref country code: BE Payment date: 20231226 Year of fee payment: 6 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20240118 Year of fee payment: 6 |