EP3728094B1 - Trip planning due to expected passenger number - Google Patents

Description

The technology described here generally relates to an elevator system with a destination call controller, in particular its design for call allocation and journey planning. Embodiments of the technology also relate to a method for operating such an elevator system.

So that a passenger can call an elevator, elevator systems are known which have either a floor terminal for entering the desired direction of travel (e.g. "up" and "down" buttons) or a floor terminal for entering the desired destination floor. The latter enable elevator systems with a destination call controller that allocates an elevator car to a passenger's elevator call in order to transport the passenger to a desired destination floor. An embodiment of an elevator system with a destination call controller is in the document EP 0 443 188 B1 disclosed; the destination call controller allocates elevator calls based on calculated service costs and variable bonus/penalty factors.

Such allocation methods are based on the assumption that each passenger makes an elevator call. As in EP 1 522 518 B1 stated, such disciplined behavior is not always encountered in real situations; in a group of people with the same destination floor, one person may call the elevator and everyone will board the assigned elevator car. Depending on the size of the group, there may then only be relatively little space left in the elevator car, possibly so little that a passenger who is already scheduled to travel with this elevator car on another floor can no longer get on (or does not want to, because they is too full). In such a case it is known, e.g. e.g EP 1 522 518 B1 or U.S. 2016/0297642 A1 to skip the stop provided for at the floor and to pass the floor; this is referred to there as a bypass. Describe as a criterion for activating the bypass function EP 1 522 518 B1 and U.S. 2016/0297642 A1 , the measured load in the elevator car. However, the bypass function cannot be activated if the floor is the destination of a passenger in the cabin.

U.S. 2017/158459 A1 discloses a method for allocating an elevator in which a passenger batch size distribution is determined for each pair of floors in a building based on passenger batch trips, each passenger batch trip containing at least the boarding and destination floors of the trip, the number of passengers relative to the trip, and the time included in the journey. The number of passengers waiting behind an elevator call is estimated based on passenger batch size distributions. The elevator call is assigned to an elevator capable of serving the estimated number of passengers.

U.S. 2010/326773 A1 discloses an elevator group control system for good operational efficiency even when an elevator is used by a group of people. The number of people in the group is previously stored in a number of people storage section. An elevator is assigned based on the number of people stored in the number of people memory area.

WO 2014/111127 A1 describes an elevator allocation system in which at least one passenger detector is provided on at least one floor, the passenger detector being configured to detect the number of passengers in the lobby. A computing device uses the signals from the passenger detector to determine a passenger number signal, which is fed to the call assignment system.

Although the solutions mentioned with the bypass function possibly avoid that an elevator car that is already full stops on a floor on which no more passengers can board, it leads to a potentially significantly increased waiting time for the waiting passengers. In the case of a destination call control, the named elevator car must return to this floor because it has been assigned to the passengers; it is not simply possible to select another elevator car which could possibly serve the passengers earlier. The bypass function can therefore cause a large delay in travel, which can frustrate passengers; the waiting passengers may therefore enter new elevator calls, possibly also to destinations that do not correspond to their actual travel destination, just to finally be able to board an elevator car. This can result in further disadvantages for other passengers. There is therefore a need for a technology that will serve elevator calls in an improved manner and improve the efficiency of the elevator system.

One aspect of such improved technology relates to a method of operating an elevator system in a building according to claim 1.

Another aspect relates to an elevator system in a building according to claim 6.

In the exemplary embodiments of the technology described here, account is taken of the above-described situations in which, after a passenger has called a destination, additional, unplanned passengers may board with the same travel destination. According to the technology, the destination call controller makes an assumption during call allocation about a number of additional passengers who would like to be transported together with a calling passenger without having entered a destination call themselves and who have a corresponding space requirement in the elevator car. Based on data stored in a database about passenger behavior on the floors, the technology deviates from the usual approach of planning a space requirement for a passenger for each destination call. This allows more realistic assumptions to be made about the actual space requirements, which e.g. results in the elevator system being able to operate with improved efficiency, which also enables optimization of waiting times for passengers.

The database is stored in a storage device, with a large number of data records being stored in the database. Each record has predefined ones describing a call situation

Data fields, a first data field indicating 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 set.

The technology described here uses such a database to determine whether a number of additional passengers can be assigned to the first destination call. For this purpose, the database is accessed and it is determined whether the first destination call corresponds to a call situation stored in the database. If this is the case, this results in the number of additional passengers for this call situation given by the first destination call. Generating additional space requirement information therefore includes reading the fourth data field to determine the number of additional passengers.

The data stored in the database can be determined in different ways. In one embodiment, the elevator system includes a sensor system coupled to the destination call control device and the memory device. The sensor system determines information on a number of passengers boarding the elevator car on a floor. The sensor system can e.g. B. be used to determine the number of additional passengers that are specified in the fourth data field. In one exemplary embodiment, the sensor system comprises sensors arranged on the floors, which are coupled to the destination call control device and the memory device via a line. In one exemplary embodiment, a sensor of the sensor system includes a camera, and the sensor system is designed to determine the number of passengers from images recorded by the camera. As an alternative to such a self-learning system, people can observe and record the behavior of the passengers depending on the time of day and the day of the week in order to obtain the data for the database.

In one exemplary embodiment, the destination call control device is also designed to adapt the generated information about the additional space requirement using the information determined by the sensor system about the number of boarding passengers and to use the adapted information about the number of passengers to serve passengers to use additional space. As a result, the planning of the operating sequence of passengers can be improved because z. B. the (assumed) additional space requirement can be increased or decreased by means of the number of passengers actually boarding.

In one embodiment, 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. It is an advantage here that the allocation algorithm does not have to be expanded or otherwise changed compared to known methods, since the space requirement is modified independently of the allocation algorithm.

According to the invention, for allocating the first destination call, the additional space requirement information is kept separate from the first destination call; both are fed separately to the allocation algorithm. It is an advantage here that the allocation algorithm can be supplemented or modified with simpler or more complicated rules in order to take into account the additional space requirement in different planning steps. Typical planning steps are the calculation of the space requirement for passengers waiting on a floor, or the calculation of the space requirement for passengers who could be transported together in the elevator car at the same time. In both cases, the individual normal and the individual additional space requirements can be taken into account for each of the passengers under consideration.

For example, if a number of destination calls from different passengers is entered essentially at the first time, a space requirement is assumed for allocating the destination calls, which, with one passenger per destination call, 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, from this, that destination call to which the maximum number of additional passengers is assigned. This allows the maximum number of additional passengers to be determined. For example, if there are three destination calls, with two of these destination calls being assigned an additional passenger and one of the destination calls being assigned three additional passengers, the maximum number of additional passengers is three. This has the advantage that at if too few calls require more space, but if there are enough calls, no unnecessary additional space is taken into account.

In another example, if a number of destination calls from different passengers are entered essentially at the first time, a space requirement is assumed for allocating the destination calls, which, with one passenger per destination call, per destination floor, consists of the number of destination calls and a maximum number of additional passengers. A number of additional passengers is determined for each destination call and each destination floor, and a maximum value of the additional space requirement is determined therefrom for each destination floor; the resulting maximum values are added. This has the advantage that no unnecessary additional space requirement is planned for passengers with the same travel destination in the case of several calls, but additional passengers traveling with them are expected for passengers with different destinations, and sufficient space is therefore planned.

Fig. 1

eine schematische Darstellung eines Ausführungsbeispiels eines Aufzugsystems in einem Gebäude,

Fig. 2

eine beispielhafte Darstellung eines Ausführungsbeispiels einer Zielrufsteuerungseinrichtung, und

Fig. 3

eine beispielhafte Darstellung eines Ausführungsbeispiels eines Verfahrens zum Zuteilen eines Zielrufs anhand eines schematischen Ablaufdiagramms.

Various aspects of the improved technology are explained in more detail below using exemplary embodiments in conjunction with the figures. In the figures, the same elements have the same reference numbers. Show it:

1

a schematic representation of an embodiment of an elevator system in a building,

2

an exemplary representation of an embodiment of a destination call control device, and

3

an exemplary representation of an embodiment of a method for allocating a destination call using a schematic flow chart.

1 shows a schematic representation of an embodiment of an elevator system 1 in a building 2; In principle, the building 2 can be any type of multi-story building (e.g. residential building, hotel, office building, sports station, etc.) or a ship. Components and functions of the elevator system 1 are explained below insofar as they appear helpful for understanding the technology described here. This in 1 The building 2 shown has several floors L1, L2, L3, which are served by the elevator system 1, ie a passenger 4 can use the elevator system 1 from a boarding floor to a Destination floor are transported. The boarding floor is also referred to as the call input floor.

In the exemplary embodiment shown, the elevator system 1 has an elevator car 10 that 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 . This can be a traction elevator, with further details such as a counterweight and guide rails in 1 are not shown. The elevator controller (EC) 12 is connected to the drive unit 14 and controls the drive unit 14 in order 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. In another embodiment, the elevator system 1 may include a hydraulic elevator. Those skilled in the art will also recognize that elevator system 1 may include multiple cars, or one or more groups of elevators.

This in 1 The elevator system 1 shown is equipped with a destination call control device, the function of which is implemented in the control device (CTRL) 8 in the exemplary embodiment shown. The control device 8 is also referred to below as destination call controller 8 or destination call controller 8 . In one exemplary embodiment, the control device 8 can be implemented in whole or in part in the elevator control 12 . If the elevator system 1 includes 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 allocates one of possibly several elevator cars 10 to a destination call entered at a floor terminal 5 from a passenger 4 and communicates the corresponding allocation information via a communication bus 24 to the elevator controller 12.

The basic function of a destination call controller and the call assignment carried out by it are known, for example from the book by Barney GC et al., Elevator Traffic Analysis Design and Control, Rev. 2nd Ed., 1985, pp. 135-147 , or the patent document referenced above EP 0 443 188 B1 . This patent document describes, for example, that a computer at any time for each elevator in the elevator system, the load, the location and the operating status of an elevator car, the Knows the operating status of a drive and has additional information about the previous traffic volume and currently valid bonus/penalty factors. Based on this information, the destination call allocation algorithm described allocates newly entered destination calls to the elevators as optimally as possible in the sense of predetermined criteria. These criteria are essentially functional requirements for call operation. The basis for destination call allocation are calculations of the service costs. The individually calculated service costs are compared with one another for each call and the elevator with the lowest service costs is determined to serve the destination call. Further details on the structure of the elevator system 1 are given elsewhere in this description.

2 shows an exemplary representation of an exemplary embodiment of a destination call control device 8. In this representation, the destination call control device 8 comprises a number of functional units, e.g. B. a destination call evaluation unit 26, which is connected to the floor terminals 5, a call allocation unit 36, a memory 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 . Those skilled in the art will recognize that the functional units shown may be combined into one unit in another representation.

in the in 1 In the situation shown, the technology described here can be used in an advantageous manner in order to operate the elevator system 1 with the highest possible efficiency and the best possible comfort for the passengers 4 (especially with regard to the waiting time). The operation of the elevator system 1 according to one exemplary embodiment is summarized briefly and by way of example as follows: If a passenger 4 ("calling passenger 4") on a floor L1, L2, L3 calls an elevator car 10 by entering a destination call, the destination call controller 8 makes an assumption a number of passengers 4 who would like to be transported together with the calling passenger 4 and who require a corresponding amount of space in the elevator car 10 . This assumption is based on stored data which indicate for each floor L1, L2, L3 how many passengers 4 are usually to be expected at the time the call is input in addition to the calling passenger 4. The data can be obtained from observations of the behavior of the passengers 4 (empirical values) or using a self-learning system and z. B. for each Storey L1, L2, L3 depending on the time of day and the day of the week. The destination call controller 8 makes such an assumption for each further destination call that is entered on a different floor L1, L2, L3 and can possibly be served together with the previously entered destination call. Since each elevator car 10 can only accommodate a limited number of passengers 4, the destination call controller uses the assumptions made for call assignment and planning a journey. The assumptions can lead, for example, to the planning excluding an elevator car 10 that is favorable in terms of operating costs, although it might still have room for a few passengers 4, and instead allocating an elevator car 10 from the start that is less favorable in terms of costs is, but has more space for the expected passengers 4.

As mentioned above, destination call control uses assumptions based on stored data in one embodiment. This data is in the in 2 shown database 28 of the storage device 34 is stored. The database 28 stores a plurality of records, each record having predefined data fields describing a call situation. In 2 four data fields are shown as an example, the number of which may be greater or smaller in other exemplary embodiments. 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 (4) for the call situation described in the data record. The data contained in the database 28 can be organized, for example, according to the example structure shown in the following table (Table 1). The table may be referred to as a look-up table. The information in the table and its organizational structure are to be understood as examples. Table 1 Floor (1) time slot (2) destination floor (3) number add. passengers (4) 1 L1 7:00 - 7:30 L3 5 2 L1 7:30 - 8:30 L2 2 3 L2 7:00 - 7:30 L3 4 4 L3 11:30 - 12:30 L1 7

Some of the exemplary call situations shown in Table 1 are described below by way of example. According to one of these call situations (line 1 in Table 1). a passenger 4 on floor L1 makes a (first) call to floor L3 between 7:00 and 7:30. According to Table 1, the destination call controller makes the assumption that not only the calling passenger 4 (basic assumption) would like to be transported to floor L3, but also five additional passengers 4. This destination call thus corresponds to a total of six passengers 4. Such a situation can arise, for example. B. arise when these passengers 4 between 7:00 and 7:30 are to be present at their workplaces.

If there is no further target call in the time window between 7:00 and 7:30 a.m. at the time of the (first) target call, the target call controller can assign an elevator car 10 to the target call in a known manner (e.g. after a cost analysis), which takes the journey from Floor L1 runs to floor L3. If, on the other hand, there is another (second) destination call, e.g. B. a destination call entered on the floor L1 to the floor L2, and Table 1 does not contain information on the number of additional passengers (ie the number of additional passengers is zero), the destination call control can proceed from the basic assumption (one passenger per destination call) to carry out the call allocation . If, in this example, it is an elevator car 10 with a person or passenger capacity of eight people, the destination call controller 8 can allocate the destination call of this passenger 4 to the elevator car 10 that is used to transport the six passengers 4 (first destination call) to floor L3 was assigned. Seven passengers 4 thus enter the elevator car 10 on floor L1.

However, a different assignment results if a third destination call to floor L3 is entered at about the time of the first destination call on floor L2 (line 3 in Table 1). According to Table 1, the destination call controller makes the assumption that the calling passenger 4 and four additional passengers 4 would like to be transported. The elevator car 10 with a capacity of eight people assigned to the first destination call (six passengers 4) can no longer accommodate the five passengers 4 (third destination call) waiting on the floor L2. For call allocation, this means that the destination call controller 8 does not allocate the third destination call to the elevator car 10 that is planned to travel from floor L1 to floor L3 because there is not enough space in the car with the additional passengers planned. Instead, the destination call controller 8 can allocate another elevator car 10 to the third destination call. It can thus be avoided that there is not enough space for the passengers waiting there to board due to the additional passengers expected when stopping on floor L2. In addition, can this may result in a minimized waiting time for the passengers 4 waiting on floor L2. Alternatively, if no passengers z. B. drive from floor L1 to floor L2, the destination call controller 8 can allocate the first and the third destination call to the same elevator car 10 and plan the trips so that the elevator car 10 is first moved from floor L1 to floor L3 in order to make the first destination call serve, and then from floor L3 to floor L2 to serve the third destination call. Although the sequence of floors served in this case can be the same as in systems with the bypass function mentioned above, the procedure and its effect are different: The bypass function can only be used under certain circumstances (if no passengers, e.g. from going from floor L1 to floor L2) will prevent the car from stopping at floor L2, where there is not enough space for the passengers waiting there to board, and will also result in significantly increased waiting times for passengers waiting on floor L2. The method described here does not have these disadvantages, since in any case a stop of the already overcrowded car on floor L2 is avoided and the waiting times of the passengers on all floors can already be taken into account and minimized during the planning.

Table 1 also shows a situation (line 4) that can arise in an office building around midday. For a destination call to floor L1 entered on floor L3 in a time window between 11:30 and 12:30, it is assumed that in addition to the calling passenger 4, seven additional passengers 4 would like to travel from floor L3 to floor L1. In this case, the elevator car 10 with a capacity of eight passengers is fully occupied. The destination call controller 8 does not plan any further stops for this trip.

The call situations specified in Table 1 can be determined from observations of the behavior of the passengers 4 within a specified period of time. The specified period can be, for example, one or two months (or longer), with the observations e.g. B. at intervals of one week (ie observe 7 days, pause 7 days). The observations can be recorded, for example, by one or more people who document the passenger behavior per floor L1, L2, L3 depending on the time of day and the day of the week. The observations can possibly be supplemented by questioning the passengers 4 . With the help of these observations, the time window can be determined and the number of additional passengers 4 (e.g. by 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, time-dependent behavioral patterns with regard to elevator use can be determined for each floor L1, L2, L3. If Table 1 is complete, the elevator system 1 can be configured accordingly. Those skilled in the art will recognize that Table 1 can be updated as the use of the building 2 and hence behavioral patterns change, e.g. B. when a previously unused floor L1, L2, L3 is used by a company with a large number of people.

In another exemplary embodiment, passenger behavior can be determined using a sensor system. In 1 the sensor system is represented by sensors 6, with a sensor 6 connected to a line 22 being arranged on each floor L1, L2, L3. The sensor system can supplement or replace the observations mentioned by people (it can be designed as a self-learning system). In one embodiment, the sensor system comprises z. B. a counting device that determines the passengers 4 entering the elevator car 10 on a floor L1, L2, L3. The counting device can include a camera (e.g. for recording images in the visible optical spectrum or in the infrared range) in connection with an image processing device that determines the number of passengers 4 from the recorded images. In another embodiment, the counting device can use a load measuring device of the elevator car 10 in order to determine the number of passengers 4 boarding on the relevant floor L1, L2, L3.

In addition to this information provided by the counting device, the sensor system can use information about the destination call or calls entered on the relevant floor L1, L2, L3. In this case, the sensor system is communicatively connected to the destination call controller 8 . In a further refinement, in this case the destination call controller 8 can use the information recorded by the sensor system in order to further improve the planning of operation, e.g. B. by increasing or reducing the additional space required by passengers currently waiting or being transported in an elevator. For example, the destination call control according to Table 1 initially makes the assumption that with a (first) destination call on floor L1 between 7:00 and 7:30 a.m. on destination floor L3 with five additional passengers 4, i.e. a total of six passengers 4 is to be expected; but if, after boarding, a sensor system provides the information that a total of two passengers 4 had actually boarded, the destination call controller can reduce the additional space requirement from five to one additional passenger and reassess the situation, e.g. B. plan an intermediate stop on floor L2 if there is now enough space for passengers boarding there.

Alternatively, there is no connection to the terminator controller 8, but information collected separately from the sensor system and the terminator controller 8 can later be brought together and examined, e.g. B. in a computer system used for this purpose. Analogously to the observations by people, the passenger behavior per floor L1, L2, L3 can be determined by the sensor system during a fixed period of time; with this, the complete table 1 can be determined. In addition, the table 1 can be updated by the sensor system, for example when required or according to a fixed schedule.

With the understanding of associated with 1 and 2 described basic structure of the elevator system 1 and the exemplary call situations shown in Table 1, the following is a description of an embodiment of a method for operating the elevator system 1, in particular a method for allocating a destination call, in conjunction with Figure 3 Figure 3 shows an exemplary flow chart of a method for allocating a destination call to an elevator car 10 of the elevator system 1. The method according to FIG 3 begins in a step S1 and ends in a step S8.

The process initially waits for receipt of a destination call (steps S2 and S3). If a passenger 4 enters a destination call at a floor terminal 5 , this is received by the destination call evaluation unit 26 of the destination call controller 8 . The person skilled in the art recognizes that, depending on the volume of traffic, the destination call evaluation unit 26 can receive several destination calls at the same time or within a short period of time.

In a step S4, the received destination call is evaluated in order to determine call information. In the case of several target calls, each target call is evaluated. Criteria according to which the evaluation takes place are, for example, the call input floor, the destination floor or the time of the destination call, or combinations thereof. Point of time of the destination call is z. B. recorded as time and calendar date. The call information includes, for example, the call input floor and/or the destination floor.

In a step S5, an additional space requirement in the elevator car 10 is determined using the call information. This determination of the additional space requirement uses the data stored in the database 28, which is organized according to Table 1 in one exemplary embodiment. In one exemplary embodiment, 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 requirement results from the number of additional passengers 4 specified in Table 1 for this call situation.

In a step S6, in one exemplary embodiment, the information on the destination call is modified with the additional space requirement determined in step S5 (variant A). Each destination call results in implicit or explicit information about the space required in the elevator car 10 for the destination call in question. The "normal" space requirement is e.g. B. space for one passenger per destination call. The information is z. B. modified in such a way that the normal space requirement is increased by the determined additional space requirement (z. B. + 2 passengers) (space requirement (new): 1 + 2 = 3 passengers). This modified information is passed on to the subsequent call allocation (step S7).

According to another exemplary embodiment, in step S6 the information about the destination call is supplemented with the additional space requirement determined in step S5 (variant B). In this embodiment, the information about the normal space requirement of the input destination call and the determined information about additional space requirement are kept separately and both are passed on for the call allocation (step S7).

In step S7, the method determines the allocation of the destination call. The method runs an allocation algorithm for this; such allocation algorithms are known to those skilled in the art, see for example the document cited above EP 0 443 188 B1 or the book by GC Barney et al. According to variant A, the call allocation is based on the assumption that a destination call has been entered that requires space of z. B. has three passengers, so the space requirement corresponds to the information modified in step S6. This destination call is allocated in a known manner by the implemented allocation algorithm; the allocation algorithm must are not expanded or otherwise changed compared to known methods, since the modification of the space requirement already takes place in the preceding step S6 and is therefore independent of the allocation algorithm.

Variant B differs from Variant A in the call allocation in that the call allocation is not simply based on the space requirement in the elevator car 10, which results from adding the normal space requirement and the additional space requirement. This difference arises, for example, when a destination call is to be assigned to a passenger 4 on a floor L1, L2, L3 on which one or more other passengers 4 have already been assigned to the elevator car 10. According to variant B, the normal and additional space requirements of the calling passengers 4 are not simply added together in step S7, but are treated separately. For example, the normal seating requirements can be added together (e.g., four destination calls equals a normal seating requirement for four passengers 4), but the passenger space requirements can be limited to the maximum additional space requirements of a single passenger. This has the advantage that if there are too few calls, more space is required, but if there are enough calls, no unnecessary additional space is taken into account.

With variant B, the allocation algorithm can be supplemented or modified with simpler or more complicated rules in order to take into account the additional space requirement in various planning steps. Typical planning steps are the calculation of the space requirement for passengers 4 waiting on a floor L1, L2, L3, or the calculation of the space requirement for passengers who could be transported together in the elevator car 10 at the same time. In both cases, the individual normal and the individual additional space requirements can be taken into account for each of the passengers 4 under consideration. In the example given above, the space requirements of all passengers considered were determined in such a way that the sum of the normal space requirements of the passengers and the maximum of the additional space requirements of the passengers are added together. As a further example, instead of the maximum of the additional space requirement of all passengers, the maximum of the additional space requirement could first be determined for each destination and these values could be added together for all destinations; this has the advantage that no unnecessary additional space is planned for passengers with the same destination when there are several calls, but for passengers with different destinations, additional passengers are expected and sufficient space is planned.

To describe further components and functions of the elevator system 1, reference is again made to FIG 1 taken. The floor terminals 5 arranged on the floors L1, L2, L3 are z. B. arranged in the vicinity of elevator doors 6 and communicatively connected to the control device 8 via the line 22 . In the exemplary embodiment shown, the building 2 has three floors L1, L2, L3 and there is a floor terminal 5 on each floor. But there can also be only two or more than three floors; it is also possible that there is more than one floor terminal 5 on a floor L1, L2, L3.

As described above, the destination call control device 8 is communicatively connected to the elevator control 12 and the floor terminals 5 . A communicative connection is to be understood in this description as a direct or indirect connection that enables unidirectional or bidirectional communication between two units. In this case, data signals and/or control signals are transmitted in a manner known per se. Such a connection can be made by an electrical line system (either as a system of point-to-point connections or as a bus system, with the units connected to the bus system being addressable), a radio system or a combination of a radio system and a line system. In 1 the communicative connection is shown by way of example by lines 20, 22, the line 20 existing between the communication bus 24 and the car 10 and the line 22 connecting the floor terminals 5 to the control device 8. In one embodiment, the line 22 can be a communication bus system to which the floor terminals 5 are connected. Correspondingly, the line 20 can also be a communication bus system.

In another exemplary embodiment, at least one floor terminal 5 can be communicatively connected to the destination call control device 8 via a radio system. In a further exemplary embodiment, a mobile electronic device (e.g. mobile phone, smartphone, smartwatch, tablet PC) can be used instead of a floor terminal 5 for entering a destination call. The mobile device can also display a message (e.g. "Elevator A") about the elevator assigned to this destination call. For a wireless For communication with the elevator system 1, the mobile electronic device has a radio module, for example a Bluetooth, an RFID and/or an NFC module.

The person skilled in the art recognizes that the destination call control device 8 or its functionality can also be part of the elevator control 12 or a floor terminal 5 . In such a case, for example, the separate representation of the control device 8 in 1 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. The implementation of the communicative connections therefore also changes depending on the configuration. 1 is thus to be understood as a basic representation of an exemplary embodiment of the elevator system 1 .

In one embodiment, a floor terminal 5 is arranged on each floor L1, L2, L3, for example in the area of access to an elevator car 10. In one embodiment, the floor terminal 5 includes a keyboard or a touch-sensitive screen (touch screen), so that a passenger 4 a Destination floor (ie a destination call) can enter. In another exemplary embodiment, the floor terminal 5 includes a device for recognizing an authorization parameter that is assigned to a passenger 4 . In one exemplary embodiment, this device is a reading device for an information carrier carried by a passenger 4 . If the passenger 4 presents the information carrier to the reading device, the reading device reads information from the information carrier, which is used, for example, to recognize an operating authorization. The passenger 4 can only make an entry if the passenger 4 is authorized to operate the input terminal 5 . Depending on the configuration, a destination call can also be triggered with the information read without any further action on the part of the passenger 4 .

In one embodiment, the information carrier is designed like a card, for example in the form of a credit card or an employee ID card. Depending on the configuration, a memory chip that can be contacted from the outside, an RFID transponder in connection with a memory chip or a code that can be (optically) read from the outside, e.g. B. alphanumeric characters, a QR code or a bar code (barcode). Alternatively, the functionality of the information carrier can also be carried out on a portable electronic device (e.g. B. mobile phone or smartphone) can be realized. For example, alphanumeric characters, QR codes, barcodes or color pattern codes can be shown on the displays of such devices. Such devices also enable a radio connection to other electronic devices, for example via known radio technologies such as Bluetooth, WLAN/WiFi or NFC. The reader of the floor terminal 5 is compatible with the information carrier technology used. Those skilled in the art will also recognize that the reader may be configured for more than one technology.

Claims (11)

1. A method for operating an elevator system (1) in a building (2), wherein the elevator system (1) comprises a destination call control device (8) and an elevator car (10), which can travel between floors (L1, L2, L3) of the building (2) and has a defined passenger capacity, with said method comprising the steps of:

   evaluating a first destination call being input on a floor (L1, L2, L3) by a first passenger (4) at a first point in time in order to determine first call information from the first destination call, wherein the first call information contains data on a call input floor (L1, L2, L3) and/or a destination floor (L1, L2, L3);

   using the first call information for determining if a number of additional passengers (4) are to be assigned to the first destination call, wherein the number of additional passengers (4) results in an additional space requirement in an elevator car (10) handling the first destination call, and wherein said determination comprises

   - accessing a database (28), in which a plurality of datasets can be stored, wherein a dataset has predefined data fields that describe a call situation, and wherein a first data field indicates the call input floor, a second data field indicates a time window, a third data field indicates the destination floor and a fourth data field indicates the number of additional passengers (4) for the call situation described in the dataset, and

   - determining if the first destination call corresponds to a call situation stored in the database (28);

   generating information on the additional space requirement if a number of additional passengers (4) are to be assigned to the first destination call; and,

   if a number of additional passengers (4) are to be assigned to the first destination call, allocating the first destination call with the aid of an allocation algorithm by using information on the additional space requirement in order to transport the first passenger (4) from the call input floor (L1, L2, L3) to the destination floor (L1, L2, L3), wherein the information on the additional space requirement is kept separate of the first destination call and both are fed to the allocation algorithm separately in order to allocate the first destination call.
2. The method according to claim 1, in which the generation of information on the additional space requirement comprises reading the fourth data field in order to determine the number of additional passengers (4).
3. The method according to one of claims 1 to 2, in which the space requirement of the first passenger (4) is increased by the space requirement of the additional passengers (4) and the resulting overall space requirement is fed to the allocation algorithm in order to allocate the first destination call.
4. The method according to claim 3, in which the allocation of destination calls is, if a number of destination calls essentially are input by different passengers (4) at the first point in time, based on a space requirement that, for one passenger (4) per destination call, results from the number of destination calls and a maximum number of additional passengers (4), wherein a number of additional passengers (4) is determined for each destination call and the destination call, to which the maximum number of additional passengers (4) is assigned, is determined thereof.
5. The method according to claim 3, in which the allocation of destination calls is, if a number of destination calls essentially are input by different passengers (4) at the first point in time, based on a space requirement that, for one passenger (4) per destination call, results from the number of destination calls and a maximum number of additional passengers (4), wherein a number of additional passengers (4) is determined for each destination call and each floor and a maximum value of the additional space requirement per floor is determined thereof, and wherein the resulting maximum values are added.
6. An elevator system (1) in a building (2), comprising:

   an elevator car (10), which can travel between floors (L1, L2, L3) of the building (2) and has a defined passenger capacity;

   a storage device (34), in which a database (28) containing a plurality of datasets is stored, wherein each dataset has predefined data fields that describe a call situation, and wherein a first data field indicates the call input floor, a second data field indicates a time window, a third data field indicates the destination floor and a fourth data field indicates the number of additional passengers (4) for the call situation described in the dataset; and

   a destination call control device (8) that is configured for

   evaluating a first destination call being input on a floor (L1, L2, L3) by a first passenger (4) at a first point in time in order to determine first call information from the first destination call, wherein the first call information contains data on a call input floor (L1, L2, L3) and/or a destination floor (L1, L2, L3);

   using the first call information for determining if a number of additional passengers (4) are to be assigned to the first destination call, wherein the number of additional passengers (4) results in an additional space requirement in an elevator car (10) handling the first destination call;

   generating information on the additional space requirement if a number of additional passengers (4) are to be assigned to the first destination call; and,

   if a number of additional passengers (4) are to be assigned to the first destination call, allocating the first destination call with the aid of an allocation algorithm by using information on the additional space requirement in order to transport the first passenger (4) from the call input floor (L1, L2, L3) to the destination floor (L1, L2, L3), wherein the destination call control device (8) furthermore is configured for keeping the information on the additional space requirement separate of the first destination call and for feeding both to the allocation algorithm separately in order to allocate the first destination call.
7. The elevator system (1) according to claim 6, furthermore comprising a sensor system that is linked to the destination call control device (8) and the storage device (34), wherein the sensor system determines information on a number of passengers (4), who board the elevator car (10) on a floor (L1, L2, L3).
8. The elevator system (1) according to claim 7, in which the sensor system comprises sensors (6) that are arranged on the floors (L1, L2, L3) and linked to the destination call control device (8) and the storage device (34) via a line (22).
9. The elevator system (1) according to claim 8, wherein a sensor (6) of the sensor system comprises a camera and the sensor system is configured for determining the number of passengers (4) based on recorded images of the camera.
10. The elevator system (1) according to one of claims 6-9, in which the destination call control device (8) furthermore is configured for adapting the generated information on the additional space requirement by means of the information on the number of boarding passengers (4) determined by the sensor system and for using the adapted information on the additional space requirement for handling the passengers (4).
11. The elevator system (1) according to one of claims 6-10, in which the destination call control device (8) furthermore is configured for increasing the space requirement of the first passenger (4) by the space requirement of the additional passengers (4) and for feeding the resulting overall space requirement to the allocation algorithm in order to allocate the first destination call.

Images