Abstract
An elevator system (20) includes a controller (36) that uses one of
a plurality of fuzzy logic algorithms for assigning an elevator car
(22-28) to service a passenger request. A disclosed example uses a
passenger's desired destination as indicated by the passenger service
request prior to the passenger entering an elevator car. A disclosed
example includes multiple fuzzy logic algorithms, each corresponding
to a particular relationship between an elevator car's current assignments,
a passenger's desired destination, a source landing of the passenger's
request, or a combination of them.
Claims
1. A method of controlling an elevator system, comprising: assigning
an elevator car to respond to a passenger request that indicates an
intended destination before the passenger enters an elevator car based
upon the intended destination and a fuzzy logic car assignment algorithm.
2. The method of claim 1, including determining whether a candidate
elevator car is currently assigned to travel to the intended destination
and using one of a plurality of fuzzy logic car assignment algorithms
based upon the determination.
3. The method of claim 2, including using a coincident destination
call fuzzy logic algorithm if the candidate elevator car is currently
assigned to travel to the intended destination.
4. The method of claim 2, including determining whether the candidate
elevator car is assigned to travel to a source landing of the passenger
request from which the passenger will board an elevator car to be
carried to the intended destination; determining a type of call
the candidate elevator car is assigned to respond to when traveling
to the source landing; and selecting a corresponding one of a plurality
of fuzzy logic algorithms responsive to the determined type of call.
5. The method of claim 4, including selecting one of a coincident
hall call at the source landing and coincident destination call
fuzzy logic algorithm, a coincident hall call at the source landing
fuzzy logic algorithm, a coincident car call at the source landing
and a coincident destination call fuzzy logic algorithm, a coincident
car call at the source landing fuzzy logic algorithm or a coincident
destination call fuzzy logic algorithm.
6. The method of claim 1, including determining whether a candidate
elevator car is assigned to travel to the intended destination or
a source landing of the passenger request from which the passenger
will board an elevator to be carried to the intended destination
and using a no coincident call fuzzy logic algorithm when the candidate
elevator car is not assigned to travel to the intended destination
or the source landing.
7. The method of claim 1, including preferring to assign an elevator
car that is already assigned to carry at least one other passenger
from a source landing of the passenger request to the intended destination
over at least one other elevator car that is traveling to the source
landing without at least one other passenger assigned to board the
other elevator car.
8. The method of claim 1, including determining whether a candidate
elevator car will have capacity to accommodate the passenger for
responding to the passenger request.
9. The method of claim 8, including determining a capacity of the
candidate elevator car to accommodate the passenger based upon a
number of passengers currently on the candidate elevator car, a
number of passengers expected to leave the candidate elevator car
when or before the candidate elevator car reaches a source landing
of the passenger request and a number of passengers expected to
board the candidate elevator car when or before the candidate elevator
car reaches the source landing.
10. The method of claim 9, including determining a number of passengers
on the candidate elevator car with the passenger on the candidate
car as the candidate car departs the source landing; assigning the
candidate elevator car to respond to the request if the determined
number is less than a maximum capacity of the candidate elevator
car.
11. A method of controlling an elevator system, comprising: determining
whether an elevator car has enough capacity to respond to a passenger
request that indicates an intended destination before the passenger
enters an elevator car based upon the intended destination and a
destination of any other passenger assigned to the elevator car
or currently on the elevator car.
12. The method of claim 11, determining a capacity of the elevator
car to accommodate the passenger based upon a number of passengers
currently on the elevator car, a number of passengers expected to
leave the elevator car when or before the elevator car reaches a
source landing of the passenger request and a number of passengers
expected to board the elevator car when or before the elevator car
reaches the source landing.
13. The method of claim 12, including determining a number of passengers
on the elevator car with the passenger on the elevator car as the
elevator car departs the source landing; assigning the elevator
car to respond to the request if the determined number is less than
a maximum capacity of the elevator car.
14. The method of claim 11, including assigning the elevator car
to respond to the passenger request based upon the intended destination
and a fuzzy logic car assignment algorithm if the elevator car has
enough capacity to respond to the request.
15. The method of claim 14, including determining whether the elevator
car is currently assigned to travel to the intended destination
and using one of a plurality of fuzzy logic car assignment algorithms
based upon the determination.
16. The method of claim 15, including determining whether the elevator
car is assigned to travel to a source landing of the passenger request
from which the passenger will board an elevator car to be carried
to the intended destination; determining a type of call the elevator
car is assigned to respond to when traveling to the source landing;
and selecting a corresponding one of a plurality of fuzzy logic
algorithms responsive to the determined type of call.
17. An elevator system, comprising: a plurality of elevator cars;
and a controller that assigns one of the elevator cars to respond
to a passenger request that indicates an intended destination before
the passenger enters an elevator car based upon the intended destination
and a fuzzy logic car assignment algorithm.
18. The system of claim 17, wherein the controller determines whether
a candidate elevator car is currently assigned to travel to the
intended destination and uses one of a plurality of fuzzy logic
car assignment algorithms based upon the determination.
19. The system of claim 18, wherein the controller determines whether
the candidate elevator car is assigned to travel to a source landing
of the passenger request from which the passenger will board an
elevator car to be carried to the intended destination; determines
a type of call the candidate elevator car is assigned to respond
to when traveling to the source landing; and selects a corresponding
one of a plurality of fuzzy logic algorithms responsive to the determined
type of call.
20. The system of claim 19, wherein the plurality of fuzzy logic
algorithms includes: a coincident hall call at the source landing
and coincident destination call fuzzy logic algorithm, a coincident
hall call at the source landing fuzzy logic algorithm, a coincident
car call at the source landing and a coincident destination call
fuzzy logic algorithm, a coincident car call at the source landing
fuzzy logic algorithm; and a coincident destination call fuzzy logic
algorithm.
21. The system of claim 17, wherein the controller determines whether
a candidate elevator car is assigned to travel to the intended destination
or a source landing of the passenger request from which the passenger
will board an elevator to be carried to the intended destination
and the controller uses a no coincident call fuzzy logic algorithm
when the candidate elevator car is not assigned to travel to the
intended destination or the source landing.
22. The system of claim 17, wherein the controller prefers to assign
an elevator car that is already assigned to carry at least one other
passenger from a source landing of the passenger request to the
intended destination over another elevator car that is traveling
to the source landing as a destination for at least one other passenger.
23. The system of claim 17, wherein the controller determines whether
a candidate elevator car will have capacity to receive the passenger
for responding to the passenger request.
24. The system of claim 23, wherein the controller determines a
capacity of the candidate elevator car to accommodate the passenger
based upon a number of passengers currently on the candidate elevator
car, a number of passengers expected to leave the candidate elevator
car when or before the candidate elevator car reaches a source landing
of the passenger request and a number of passengers expected to
board the candidate elevator car when or before the candidate elevator
car reaches the source landing.
25. The system of claim 24, wherein the controller determines a
number of passengers on the candidate elevator car with the passenger
on the candidate car as the candidate car departs the source landing
and assigns the candidate elevator car to respond to the request
if the determined number is less than a maximum capacity of the
candidate elevator car.
Description
FIELD OF THE INVENTION
[0001] This invention generally relates to elevator systems. More
particularly, this invention relates to assigning elevator cars
to respond to passenger requests.
DESCRIPTION OF THE RELATED ART
[0002] Elevator systems have been in use for many years. Traditional
elevator systems include hall call buttons located near an entrance
to an elevator shaft. Passengers use hall call buttons to indicate
a desire to travel up or down from their current location. Upon
entering the elevator car, the passenger utilizes a car operating
panel to indicate the destination they intend to reach. The elevator
car then travels to the appropriate destination where the passenger
can exit the elevator.
[0003] Various control schemes have been proposed for assigning
elevator cars to respond to passenger requests. In some buildings,
it is desirable to use particular control algorithms to manage elevator
traffic to handle particular traffic conditions. For example, some
elevator systems are designed to assign elevator cars in a way that
minimizes wait time for passengers at a lobby level, for example.
[0004] One known dispatching technique includes using fuzzy logic
for assigning elevator cars to respond to passenger requests placed
using hall call buttons. U.S. Pat. No. 5,668,356 describes such
an arrangement. For such systems, the elevator dispatcher does not
know the destination of passengers until the passengers board the
elevator and enter their destinations with the car operating panel
buttons. Such systems are not able to discern how many passengers
are waiting behind a hall call or how many passengers are associated
with each destination call or car call because the hall call buttons
and the car operating panel buttons do not provide an indication
of how many individuals correspond to each request. For example,
four people may enter an elevator all intending to travel to the
same destination but the destination button on the car operating
panel is only pressed once, typically.
[0005] Although it has been possible to estimate how many passengers
were waiting behind a hall call based on past observed traffic patterns
or sensors located at a lobby level, for example, those approaches
have been adopted in a way that has only limited usefulness within
elevator dispatching control schemes. For example, hardware crowd
sensors typically add cost and there are challenges associated with
installing and locating them in a manner that makes it acceptable
to building owners and architects, for example. Further, the number
of floors at which such sensors can be installed for a group of
elevators is limited and can only provide limited information.
[0006] Another elevator car dispatching technique is associated
with the so-called destination entry systems. A typical destination
entry system includes a device that allows a passenger to request
elevator service and to indicate the passenger's intended destination
before the passenger enters an elevator car. Such systems provide
an advantage in that an elevator car dispatching algorithm can take
into account the passenger's intended destination as part of the
car assignment technique. Various proposals in this regard have
been made.
[0007] Those skilled in the art are always striving to make improvements.
It would be useful to enhance the capability of known elevator car
assignment techniques to improve passenger service. This invention
addresses that need.
SUMMARY OF THE INVENTION
[0008] An exemplary disclosed method of controlling an elevator
system includes assigning an elevator car to respond to a passenger
request based upon the desired destination of the passenger and
a fuzzy logic car assignment algorithm. In a disclosed example the
passenger request indicates the passenger's desired destination
before the passenger enters an elevator car. One example includes
determining whether a candidate elevator car is currently assigned
to travel to the desired destination and using one of a plurality
of fuzzy logic car assignment algorithms based upon that determination.
[0009] One disclosed example includes determining whether a candidate
elevator car is assigned to travel to a source landing of the passenger
request from which the passenger will board an elevator car to be
carried to the desired destination. One example includes determining
a type of call that the candidate elevator car is assigned to respond
to when traveling to the source landing. A corresponding one of
a plurality of fuzzy logic algorithms is selected responsive to
the determined type of call.
[0010] A disclosed example includes providing more than one fuzzy
logic algorithm depending on the relationship between an elevator
car's current assignments and the passenger request including the
source landing of the request and the passenger's desired destination.
[0011] One disclosed example includes determining whether a candidate
elevator car will have enough capacity to receive the passenger
at the source landing. One example includes using passenger destination
information to determine an estimate of how many passengers will
be on the elevator car or will board the elevator car at the source
landing as part of determining whether a candidate elevator car
has enough capacity to service the passenger request.
[0012] The various features and advantages of this invention will
become apparent to those skilled in the art from the following detailed
description. The drawings that accompany the detailed description
can be briefly described as follows.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] FIG. 1 schematically shows selected portions of an elevator
system designed according to an embodiment of this invention.
[0014] FIG. 2 is a flowchart diagram summarizing one example approach
for assigning an elevator car to respond to a passenger request.
[0015] FIG. 3 is a flowchart diagram summarizing one example approach
for making a determination regarding an elevator car's capacity
to respond to a passenger request.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
[0016] Disclosed example embodiments of this invention provide
elevator car dispatching techniques that include using passenger
destination information and a fuzzy logic car assignment algorithm.
[0017] FIG. 1 schematically shows selected portions of an elevator
system 20. A plurality of elevator cars 22, 24, 26 and 28 are arranged
in a known manner to carry passengers 30 between various levels
within a building, for example. The illustrated example includes
a destination entry device 32 that allows a passenger 30 to provide
an indication of the passenger's desired destination before the
passenger 30 enters one of the elevator cars 22-28. The example
destination entry device 32 includes a passenger interface 34 that
allows the passenger to use a known technique for placing a service
request indicating the desired destination. A controller 36 receives
the passenger service requests and assigns particular cars 22-28
to carry passengers to their desired destinations. The controller
36 in one example controls the passenger interface 34 to notify
the passenger which car has been assigned to their request.
[0018] A single controller 36 is schematically shown in the example
of FIG. 1 for discussion purposes. Those skilled in the art who
have the benefit of this description will realize how many processors
or controllers and what combination of software, hardware or firmware
will best meet the needs of their particular situation for performing
the functions of the example controller 36.
[0019] In one example, the controller 36 uses various dispatching
algorithms for assigning elevator cars to desired passenger destinations.
One example includes using fuzzy logic assignment algorithms based
upon decision-making techniques similar to those described in U.S.
Pat. No. 5,668,356. The teachings of that document are incorporated
into this description by reference.
[0020] One example includes selecting one of a plurality of fuzzy
logic algorithms for determining whether a particular one of the
elevator cars should be assigned to service a particular passenger
service request. In one example, the selection of the fuzzy logic
algorithm depends on a relationship between the passenger request
and the current assignments for a candidate elevator car. One example
includes using the passenger's desired destination, which is known
before the passenger enters an elevator car, as a factor in deciding
which fuzzy logic algorithm to use before deciding whether to assign
a particular elevator car to service the passenger's request. Another
factor used in a disclosed example is the source landing of the
passenger request from which the passenger will board an elevator
car to be carried to the desired destination.
[0021] FIG. 2 includes a flowchart diagram 40 that summarizes one
example approach for determining which fuzzy logic algorithm to
use when making an elevator car assignment. The example of FIG.
2 begins at 42 where a determination is made whether an elevator
car under consideration (i.e., a candidate elevator car) has a hall
call at the source landing of the passenger request. A hall call
in this context includes a request for passenger service from the
same landing as the source landing of the passenger request under
consideration. In other words, a determination is made at 42 whether
a candidate elevator car is already assigned to travel to the source
landing of the passenger request to board a passenger. If so, a
determination is made at 44 whether the same elevator car already
has a call at the passenger's desired destination. In other words,
the determination at 44 includes determining whether the elevator
car under consideration is already assigned to travel to the same
destination indicated by the passenger's request.
[0022] When the determinations at 42 and 44 are both positive,
the example of FIG. 2 continues at 46 and a coincident hall call
at the source landing and a coincident destination call fuzzy logic
algorithm is applied for determining whether to assign that elevator
car to that passenger request. If the determination at 42 is positive
but the determination at 44 is negative, then another fuzzy logic
algorithm is selected at 48, which is referred to as a coincident
hall call at the source landing fuzzy logic algorithm in this example.
[0023] Assuming that the candidate elevator car does not have a
hall call at the passenger source landing, a determination is made
at 52 whether the elevator car has a car call at the passenger source
landing. A car call in this context is used to refer to an assignment
for that elevator car to travel to the source landing of the passenger
request under consideration for purposes of dropping off a passenger,
who is already on the elevator car, at the source landing. If so,
a determination is made at 54 whether that elevator car has a call
at the passenger's desired destination. This is the same determination
made at 44, for example.
[0024] When the determinations at 52 and 54 in the example of FIG.
2 are both positive, a corresponding fuzzy logic algorithm is selected
at 56, which is referred to as a coincident car call at the source
landing and coincident destination call fuzzy logic algorithm. If
the car under consideration has a car call at the source landing
for the passenger request but does not have a coincident destination
call, then a fuzzy logic algorithm referred to as a coincident car
call at the source landing is selected at 58.
[0025] For situations where a candidate elevator car does not have
a hall call or a car call at the source landing of the passenger
request, a determination is made at 60 whether the candidate elevator
car has a call at the passenger's intended destination. In other
words, a determination is made at 60 whether the passenger's desired
destination indicated in the request under consideration is the
same as a destination to which that the elevator car is already
assigned to travel. If so, a coincident destination call fuzzy logic
algorithm is used at 62 for determining whether to assign that car
to service that passenger request.
[0026] In the example of FIG. 2, when the determinations made at
42, 52 and 60 are all negative, a fuzzy logic algorithm referred
to as a no incident call algorithm is used at 64 for determining
whether the candidate elevator car can be used to service the passenger
request under consideration.
[0027] As can be appreciated from the example of FIG. 2, a plurality
of possible fuzzy logic algorithms may be used depending on the
relationship between the passenger's request and the current assignment
for an elevator car. In particular, whether there is a coincident
stop (e.g., another call including the same floor as the source
or destination) within the elevator car's current assignments and
the passenger's desired destination is used as a factor for deciding
which fuzzy logic algorithm to apply when assigning an elevator
car.
[0028] The fuzzy logic algorithms mentioned in this description
can take a variety of forms. Those skilled in the art who have the
benefit of this description and information regarding known fuzzy
logic car assignment algorithms will be able to develop an algorithm
that meets the particular needs of an elevator system for a given
situation.
[0029] Another feature of an example embodiment is determining
whether a candidate elevator car will have enough capacity to receive
a passenger when it arrives at the source landing of the passenger's
request, allows any existing passengers to exit the car and boards
all other passengers assigned to that car from that source landing.
One example approach is summarized in the flowchart 70 of FIG. 3.
This example begins at 72 where an estimated number of passengers
in the elevator car is set to a current number value. One example
utilizes information regarding current assignments and elevator
car position and travel direction to determine the current number
of passengers. At 74, the example of FIG. 3 begins at a current
floor where a candidate elevator car is located. At 76, a determination
is made whether the current assignments for that elevator car at
all floors between the current floor and the floor of the source
landing of the passenger request have been taken into consideration
for purposes of determining the available capacity of the elevator
car for the passenger under consideration. At 78, a determination
is made whether the elevator car has a car call at each floor in
route to the source landing. Assuming that there is a car call at
a particular floor, the estimated number of passengers in the car
is decreased at 80 by subtracting the number of service requests
having that floor as the desired destination where a corresponding
number of passengers can be assumed to exit the elevator car.
[0030] At 82, a determination is made whether the car has been
assigned to pick up any passengers at a particular floor. In the
event that such an assignment has been made, the number of estimated
passengers in the car is increased at 84 according to the number
of requests made and assigned to that car. The next floor along
the direction of travel toward the source landing is selected at
86 and the process between the steps 76 through 84 repeats as necessary.
[0031] Once all appropriate floors have been considered, the estimated
number of passengers in the car is compared to the elevator car
capacity at 88. In the event that there is enough capacity remaining,
that car is considered for possible assignment to service the passenger
request at 90. If the estimated number of passengers in that car
is at least equal to the car's capacity, that car is not considered
for assignment as indicated at 92.
[0032] One example includes considering how many passengers have
already been assigned to a particular car that will board the car
at the same source landing as the passenger request under consideration.
This allows for determining whether the elevator will become overcrowded
at the source landing before a particular passenger may have an
opportunity to board that elevator car.
[0033] At the same time, considering what passengers have been
assigned to an elevator car allows for one example controller 36
to give a higher priority to one elevator car compared to another.
For example, where two elevator cars will both arrive at a source
landing at approximately the same time, it is desirable to assign
a passenger to an elevator car that already has passengers boarding
that elevator car from the source landing. This creates a more natural
passenger flow for the individuals boarding an elevator car compared
to, for example, assigning several individuals to one elevator car
and one individual to another elevator car that will arrive at the
source landing and currently is assigned only to drop off individuals
at that source landing. People tend to follow other people onto
elevator cars rather than boarding a car by themself. One example
controller is designed to prioritize elevator car assignments accordingly.
[0034] The disclosed example approaches take advantage of information
such as that available from destination entry systems. By utilizing
a passenger's desired destination in combination with a fuzzy logic
assignment algorithm enhances elevator system performance and provides
better passenger service. For example, identifying coincident stops
for the elevator car (i.e., coincident destinations for assigned
passengers), the number of stops an elevator must make to service
passengers can be reduced. Further, the disclosed example considers
the type of coincident stop for selecting an appropriate fuzzy logic
algorithm to apply to achieve the best possible elevator service
for a passenger request. The disclosed example effectively replaces
the single coincident call fuzzy rule that is used in known elevator
systems with a plurality of fuzzy logic algorithms that can be selected
based upon the relationship between a passenger request and the
current assignments for an elevator car.
[0035] Another advantage of the disclosed example is that it estimates
whether an elevator car will have enough capacity to receive a particular
passenger. This reduces the chance that an elevator car will be
too full to serve a request. Therefore, the disclosed example avoids
the difficulties and drawbacks associated with arrangements that
require a passenger or several passengers to reenter their service
request after a car that had been previously assigned to them arrives
at the source landing.
[0036] The preceding description is exemplary rather than limiting
in nature. Variations and modifications to the disclosed examples
may become apparent to those skilled in the art that do not necessarily
depart from the essence of this invention. The scope of legal protection
given to this invention can only be determined by studying the following
claims. |