Patent Grant
9481548
1. Field of the Invention
The present invention relates to an elevator system, and particularly to a smart elevator system using wireless sensor networks to acquire data relating to operating an elevator system.
2. Description of the Related Art
The elevator is a type of transport equipment that moves people or goods between floors (levels) of a structure, such as a building, a vessel, or other structures. Elevators are generally powered by electric motors that drive traction cables. Elevators are typically used in office buildings, airports, shopping malls, and other large structures. These devices transport large numbers of persons and equipment between two or more locations in a structure.
Elevators can be used a variety of ways and are widely used throughout the world. Elevators can operate in a variety of forms such as freight elevators, stage lifts, dumbwaiter elevators, and vehicle elevators. Although elevators have been advanced to perform a variety of tasks, a primary use is in transporting passengers throughout a structure, such as a building. A person or passenger awaiting an elevator car may spend numerous minutes waiting on an elevator car for transport. A passenger may also spend numerous minutes waiting inside the elevator car while passengers depart and load.
Current elevators can use technology to make passenger transport faster, easier, and even more energy efficient. These smart elevators can have various technological advancements over its predecessors and are continuing to evolve. For example, some smart elevators can calculate the weight of passengers to prevent too many people from getting on. Other smart elevators are able to route passengers to their requested location based on the number of passengers with a similar request. These smart elevators typically use a standard hardwire connection in transmitting and processing passenger requests.
Wireless Sensor-Actor Networks (WSANs) have attracted much interest in recent years. A typical WSAN consists of a larger set of miniaturized sensor nodes reporting their data to significantly fewer actor (actuator) nodes. Sensors probe their surroundings and report their findings to one or multiple actors, which processes the collected sensor reports and respond to emerging events of interest. The use of WSANs in assisting in the transport of people is expected to make elevators more efficient and decrease elevator traffic delay. Manufacturers and business owners believe the market for smart elevators is expected to grow as elevator manufacturers look for ways to move people around faster and more efficiently.
Elevators incorporating wireless sensor networks in the use for transporting people are known. Elevators of this type include, for example, published PCT patent application WO 2007020907 A1, which teaches a system which calls elevator cars using a wireless network of nodes. A mobile node at an unknown location broadcasts a request packet. The request packet includes an identification of the mobile node and an elevator call command. One or more fixed nodes at known locations measure signal strength of the received request packet and determine a known location of the mobile node based on the signal strength and the known locations of the fixed nodes, and call an elevator car according to the known location of the mobile node and the elevator call command.
Also, for example, the published PCT patent application WO 2011009356 A1, is directed towards a wireless system for detecting identification cards of mobile users within a building. In this system, an elevator automatically responds to detection of a target card in the vicinity of an elevator sensor.
There appears to be a need for an elevator system to incorporate the use of wireless sensor networks in operating elevators by allowing the sensor nodes to receive the approximate location of people and the approximate number of persons in various locations and to provide a method of using that information to determine efficient means to transport persons. Thus, a smart elevator system addressing the aforementioned problems is desired.
Embodiments of apparatuses include a smart elevator system and also include methods for operating the smart elevator system in directing a plurality of elevator cars using a plurality of sensors and computer processors. Various embodiments of the smart elevator system use a wireless sensor network. The wireless sensor network is based on sensor nodes located on each floor of a structure, such as a building, a vessel, or other structures, for example. The sensors can communicate with one another in a multi ad-hoc fashion. The sensors can also communicate with a central processor that receives data regarding elevator requests. Each sensor on a respective floor is aware of the global traffic conditions (for example, a number of persons awaiting elevator service in a downward or upward direction on that respective floor) in order to efficiently decide where the elevator should be directed and stopped. The information gathered through the respective sensors on each floor can be used in a fashion of an ad hoc network to make a determination of the new floor location the elevator should proceed to based on the information received from the sensors. The information gathered may also be transmitted to a central computer processor for determining a single elevator car's next floor location or for determining elevator stops for a multitude of elevator cars in a structure, such as a building, for example.
In various embodiments, sensors are placed in locations near each of the various floor elevator doors. The sensors are capable of detecting a number of persons awaiting the elevator. The sensors are also capable of detecting an approximate number of persons to travel in an upward floor location and an approximate number of people to travel in a downward floor location. In the instance of smart elevators, wireless sensors can also detect a number of people waiting for elevator service, whether an elevator car is empty, and the approximate location of people in a particular area, for example.
An embodiment of a method for controlling the elevator in a smart elevator system is the sensor first detecting the approximate number of persons awaiting elevator service. In one embodiment, the sensors communicate the person or passenger information to a floor controller, which can act as a receiving processor, which is associated to the elevator door. This method of communication by a sensor to the floor controller can be replicated on every floor in a structure, such as a building, for each of the sensor node's respective controller associated to its respective elevator door. The controller then communicates with one or more controllers, e.g., computer processors, on the floors immediately above and immediately below in an ad hoc approach. The elevator has a scheduler, e.g., a computer processor, which is associated to the elevator that receives the traffic information on the floors immediately above and below that floor from that current floor's controller. Based on the information received, the scheduler runs a designated program, such as to implement an algorithm, to select an elevator path, remain on the current floor, or return to a default location.
Also, in an embodiment, the sensors transmit the passenger traffic information to the respective floor controller, e.g., a computer processor, which is associated to the elevator door on a corresponding floor. The individual floor controllers then transmit the traffic information for each individual floor to a central scheduling dispatcher, e.g., a computer processor, which acts as a primary scheduling control device. Based on the information received the central scheduling dispatcher unit processes the information, runs a designated program to select the elevator path, and directs the elevator according to the selection.
In another embodiment, the sensors transmit the passenger traffic information to the respective floor controller that is associated to the elevator door on a corresponding floor. The individual floor controllers then transmit the traffic information for each individual floor to a central scheduling dispatcher, e.g., a computer processor, which acts as a secondary scheduling device. In this embodiment, there can be several central scheduling dispatchers corresponding to a number of elevator cars in a structure, such as a building. Each central scheduling dispatcher transmits passenger traffic information to an overall elevator dispatcher unit, e.g. a computer processor, which acts as a primary scheduling control device, for determining elevator transport paths. Based on the information received from the central scheduling dispatcher units, the overall elevator dispatcher unit processes the information, runs a designated program to select one or more elevator transport paths for one or more elevator cars, and transmits the selected elevator transport paths for the one or more elevator cars to the central scheduling dispatchers corresponding to the one or more elevator cars.
These and other features of the present invention will become readily apparent upon further review of the following specification and drawings.
Unless otherwise indicated, similar reference characters denote corresponding features consistently throughout the attached drawings.
With reference now to the drawings, in particular to
To assist in understanding the various embodiments of the operation of at least one elevator car in a smart elevator system, reference can be made to
Continuing with reference to
The communication among the controllers and scheduler 256 on the various floors of the structure, such as a building, continues in a similar manner through the floor N of the structure, such as a building. On the floor N, the controller 222 associated to floor N elevator door 224 communicates with the scheduler 256 associated to the elevator car 202. The controller 222 also communicates with a controller on a floor X directly below (the floor X in this case represents a floor of a floor elevator door in a structure, such as a building, directly below the floor N).
Referring to the illustration of the elevator waiting area 100 in
In an embodiment of operating an elevator car in a smart elevator system, such as the smart elevator system 200 illustrated in
For example, the traffic information is received by the controller 218, and then the traffic information is transmitted at 250 to the controller 220 on the floor 2 above and also transmitted at 248 to the controller 216 on the floor 1 below. Also, for example, traffic information received by a controller on a floor X and is transmitted at 252 to the controller 220, where the floor X is located above the floor 3. Also, for example, traffic information received by the controller 222 on the floor N is transmitted at 254 to the controller on the floor X where the floor X is located below the floor N.
In
Also, for example, in an embodiment of the smart elevator system 200 the controller 218 can also transmit the information directly and distinctly at 212, separate from the ad-hoc transmission, to the scheduler 256 associated to the elevator car 202. The scheduler 256 associated with the elevator car 202 receives the traffic information at 212 and implements a program or decision algorithm to select a transport path, such as including which direction the elevator should operate. For example, referring to the floor elevator waiting area 100 of
The floor X elevator door controller at 308 determines the passenger information from the traffic information and sends passenger information at 320 to the scheduler at 310, such as the scheduler 256, which is associated to the elevator car, such as the elevator car 202. The scheduler, such as the scheduler 256, e.g., a computer implemented device, that is associated to the elevator car, such as associated to the elevator car 202, at 310, acts as a computer processor and implements a decision program, such as implementing an algorithm, to select the elevator path or transport path, such as for the elevator car 202. The scheduler, such as the scheduler 256, that is associated to the elevator car at 310 transmits the decision and instruction at 322 as to the determined elevator path or transport path to the elevator, such as elevator car 202, at 312, such as to the elevator car's operational controller or processor to move the elevator car to a next floor location, for example.
Referring now to
In
At step 709 the controller 220 sends the passenger information to other controllers, such as controllers 222 and 218, in an ad hoc manner. The controller 220 associated to the floor 3 elevator door 226 also sends the passenger information at 211 directly to the scheduler 256 associated to the elevator car 202 at step 710. The scheduler 256 associated to the elevator car 202 can implement a decision program at step 712 in the program or process to determine the elevator car's 202 transport path.
At step 712, the scheduler 256 associated to the elevator car 202 can compare the number of people (a total of six people in this example) awaiting elevator service in the floor 3 elevator waiting area 242 in the traffic information against a value of at least one person awaiting elevator service, for example. If it is determined at step 712 that there is at least one person awaiting elevator service, the scheduler 256 associated to the elevator car 202 proceeds to step 716 and, if not, the process proceeds to step 714 where the elevator car 202 remains on a current floor or returns to a default floor as the determined transport path. From step 714, the process returns to step 702.
Continuing at step 716 the scheduler 256 determines whether the number of persons awaiting elevator service in the floor 3 elevator waiting area 242 is greater in a downward direction or an upward direction from the floor 3, for example. In this example, since there are four persons requesting downward elevator service, greater than the two persons requesting upward elevator service, from the floor 3, the scheduler 256 associated to the elevator car 202 can proceed to step 720 and instructs, such as to the elevator car's operational controller or processor, the elevator car 202 to move in a transport path, such as a downward path to a downward location, for example. If there are a greater number of persons requesting elevator service in an upward direction from the floor 3, the scheduler 256 associated to the elevator car 202 can proceed to step 718 and instructs, such as to the elevator car's operational controller or processor, the elevator car 202 to move in a transport path, such as an upward path to an upward location, for example. Also, the transport path of the elevator car 202 can be in an upward direction, such as from the floor 2, to take the persons awaiting elevator service at the floor 3 in a downward direction, or can be in a downward direction, such as from the floor N, to take the persons awaiting elevator service at the floor 3, in a upward direction, for example.
Referring to
As shown in
In an embodiment of the smart elevator system 400, the sensors 450, 452, 454, and 456 scan and receive at 423, 416, 414 and 412 traffic information regarding persons awaiting elevator service from the elevator waiting areas on the respective floors 1-N 410, 408, 406 and 404. The sensors 450, 452, 454 and 456 transmit the traffic data in relation to the persons awaiting elevator service at 412, 414, 416, and 423 to the corresponding controllers 460, 462, 464 and 466 associated to the corresponding floor 1-N elevator doors 418, 420, 422 and 440. The passenger traffic information is sent at 424, 426, 428 and 430 by the controllers 460, 462, 464, and 466 to the central scheduling dispatcher 402 which directs at 432 the elevator car 436 to move in a transport path, such as in an upward direction 434, or in a downward direction 438, for example. Also, the sensor 435 can be used to scan and receive traffic information on the inner area 158 inside of an elevator car, such as the elevator car 436, to detect the number of current passengers inside the elevator car, for example, and provide the information at 432 to the central scheduling dispatcher 402.
Referring to the illustration of the elevator waiting area 100 illustrated in
In the smart elevator system 400 of
The floor X elevator door controller, such as controllers 460, 462, 464 and 466, at 508 determines the passenger information based on the traffic information and then sends the passenger information at 520 to the central scheduling dispatcher, such as the central scheduling dispatcher 402, at 510. The central scheduling dispatcher, such as the central scheduling dispatcher 402, at 510 implements a decision program, such as an implementing an algorithm, to select the elevator path or transport path for the elevator car, such as the elevator car 436. The central scheduling dispatcher, such as central scheduling dispatcher 402, transmits the decision and instruction at 522 to the elevator car, such as the elevator car 436, such as to the elevator car's operational processor or controller, at 512 to move to a next floor location, for example.
Referring now to
In
Also, at step 806, the sensor 454 transmits at 416 the passenger information at step 806 to the controller 464 associated to the floor 2 elevator door 420. The controller 464 associated to the floor 2 elevator door 420 receives the information at 416 and determines the passenger information for the upward and downward requests at step 808. The controller 464 associated to the floor 2 elevator door 420 transmits the passenger information at 428 to the central scheduling dispatcher 402 at step 810. The central scheduling dispatcher 402 can implement a decision program at step 812 in the program or process to determine the elevator car's 436 transport path. At step 812, the central scheduling dispatcher 402 can compare the number of people (a total of nine people in this example) awaiting elevator service in the passenger information against a value of at least one person awaiting elevator service, for example. As there has been determined there is at least one person awaiting elevator service at step 812, the central scheduling dispatcher 402 proceeds to step 816. If it has been determined that there is not at least one person awaiting service, the process proceeds to step 814 where the elevator car, such as elevator car 436, remains on a current floor or returns to a default floor as the determined transport path. From step 814, the process returns to step 802.
Continuing at step 816, it is determined whether the number of persons awaiting elevator service is greater in the downward direction 438 or in the upward direction 434, for example. In this example there are five people waiting for elevator service in the upward direction 434 so the central scheduling dispatcher 402 proceeds to step 818 and instructs the elevator car 436, such as to the elevator car's operational controller or processor, to move in an upward path, for example, as the transport path. If there are a greater number of people requesting elevator service in the downward direction 438, the central scheduling dispatcher 402 can proceed to step 820 and instructs the elevator car 436, such as to the elevator car's operational controller or processor, to move to in a downward path, for example, as the transport path. Also, the transport path of the elevator car 436 can be upward, such as from the floor 1, to take the persons awaiting elevator service in a downward direction waiting at the floor 2, or can be downward, such as from the floor N, to take the persons awaiting elevator service at the floor 2, in a upward direction, for example.
The floor controllers 670, 672, 674 and 676 transmit at 630, 632, 634 and 636 the passenger traffic information to the central scheduling dispatcher 1 604. The central scheduling dispatcher 1 604 can organize and determine passengers' downward and upward elevator requests based on the traffic information received at 630, 632, 634 and 636 from the corresponding floor controllers 670, 672, 674 and 676. The central scheduling dispatcher 1 604 then sends the determined passenger information at 650 to the overall elevator dispatcher unit 602. The overall elevator dispatcher unit 602 receives passenger information at 650 from at least the central scheduling dispatcher 1 604, implements a decision program to select at least one transport path for at least one elevator car, such as the elevator car 1 626, and returns the selected transport path at 650 to the central scheduling dispatcher 1 604. The central scheduling dispatcher 1 604 can then transmit at 694 the selected transport path to the corresponding elevator car 1 626, such as to the elevator car's operational controller or processor, for example.
Also, similarly, associated with the central scheduling dispatcher 2 606 are a plurality of floor controllers, floor 1-N elevator doors, a plurality of sensors, and floor 1-N elevator waiting areas and an elevator car 2, similar to those associated with the central scheduling dispatcher 1 604 or the central scheduling dispatcher N in the smart elevator system 600, for example. The sensors associated with the central scheduling dispatcher 2 606 on floors 1-N respectively scan and transmit the passenger traffic information received from corresponding floor 1-N elevator waiting areas to the corresponding floor controllers, e.g., computer processors, which can act as receiving processors. The sensors, such as at least one sensor, can be used to scan and receive traffic information on the inner area 158 inside of an elevator car, such as the elevator car 2 to detect the number of current passengers inside an elevator car, such as the elevator car 2. After the at least one sensor scans the inner area 158 of the elevator car 2, the information from the sensor can be transmitted to a controller or processor, such as the central scheduling dispatcher 2 606, as can act as a receiving processor, for example.
The central scheduling dispatcher N 608, as well as the central scheduling dispatcher 2 606, receives and communicates information analogous to the system described with respect to the central scheduling dispatcher 1 604. However, the central scheduling dispatcher N 608 communicates at 638, 640, 642, and 644 with floor controllers 686, 688, 690 and 692, and sends the selected transport path instruction at 696 to its corresponding elevator car N 628, such as to the elevator car's operational controller or processor. Also, the overall elevator dispatcher unit 602 receives passenger information at 654 from the central scheduling dispatcher N 608, implements a decision program to select at least one transport path for at least one elevator car, such as the elevator car N 628, and returns the selected transport path at 654 to the central scheduling dispatcher N 608. The central scheduling dispatcher N 608 can then transmit at 696 the selected transport path to the corresponding elevator car N 628, such as to the elevator car's operational controller or processor, for example.
Further, the central scheduling dispatcher 2 606 communicates with its associated corresponding floor controllers and sends the selected transport path instruction to a corresponding elevator car 2, for example. Also, the overall elevator dispatcher unit 602 receives passenger information at 652 from the central scheduling dispatcher 2 606, implements a decision program to select at least one transport path for at least one elevator car, such as an elevator car 2 associated with the central scheduling dispatcher 2 606, and returns the selected transport path at 652 to the central scheduling dispatcher 2 606, for example. The central scheduling dispatcher 2 606 can then transmit the selected transport path to the corresponding elevator car 2, such as to the elevator car's operational controller or processor, for example.
In an embodiment of the smart elevator system 600, the overall elevator dispatcher unit 602 can act as the primary scheduling dispatcher unit instead of a central scheduling dispatcher, in contrast to the central scheduling dispatcher 402 being a primary scheduling dispatcher in the smart elevator system 400 of
Also, the overall elevator dispatcher unit 602 in the smart elevator system 600 can send instructions to and receive information from one or more of a plurality of central scheduling dispatchers, the communications can be sent to or received from the one or more central scheduling dispatchers, such as central scheduling dispatchers 604, 606 and 608, simultaneously, at about a same time, at different times or independently of the other central scheduling dispatchers, for example. Also, the instructions sent for the operation of the elevator cars in the smart elevator system 600 can be sent simultaneously, at about a same time, at different times or independently as to operation of or a transport path for each corresponding elevator car, for example.
Referring now to
While in
Also, the embodiment of a method for operating an elevator car in an elevator system described with respect to the smart elevator system 600 and the central scheduling dispatcher 1 604 in
At step 902, at least one sensor, such as sensor 664, scans the elevator waiting area outside of at least one floor elevator door, such as floor 2 elevator waiting area 614, the elevator waiting area 614 being similar to the elevator waiting area 100 of
Also, after the at least one sensor, such as the sensor 664, scans and receives the traffic information of persons awaiting elevator service, such as the number of persons waiting in the downward traffic area or transport zone 112 and the number of persons waiting in the upward traffic area or transport zone 114, the at least one sensor transmits the traffic information to at least one controller, such as controller 674, associated with an elevator car, such as the elevator car 626, at step 906. Once the at least one controller receives the traffic information from the corresponding sensors, the at least one controller can organize the information for upward and downward elevator requests at step 908.
At step 912, it is determined whether there is more than one central scheduling dispatcher. If there is not more than one central scheduling dispatcher at step 912, such as where other of a plurality of central scheduling dispatchers in the smart elevator system 600 are not currently active or where there is only a single central scheduling dispatcher in a structure, such as a building, that is associated with an overall elevator dispatcher unit, for example, the process proceeds to step 940. At step 940, the at least one controller can send the passenger information to the corresponding central scheduling dispatcher, such as central scheduling dispatcher 1 604, at step 940. The process then proceeds to step 942 where the central scheduling dispatcher, such as central scheduling dispatcher 1 604, can compare the number of people awaiting elevator service in the passenger information against a value of at least one person awaiting elevator service, for example. If it is determined at step 942 that there is not at least one person awaiting elevator service, the elevator car remains on the current floor or returns to the default floor at step 952, as the determined transport path, and the process can return to step 902.
However, where it was determined at step 912 that there is not more than one central scheduling dispatcher, if it is determined that there is at least one person awaiting elevator service at step 942, the central scheduling dispatcher, such as the central scheduling dispatcher 1 604, proceeds to step 944 to determine whether the number of people awaiting elevator service is greater in a downward direction or an upward direction, for example. At step 944, if the number of persons awaiting elevator service is greater in an upward direction, the process proceeds to step 946, and the central scheduling dispatcher, such as central scheduling dispatcher 1 604, can direct the elevator car, such as the elevator car 626, such as to the elevator car's operational controller or processor, to proceed on a transport path in an upward direction at step 946, for example.
However, if at step 944 it is determined that the number of persons awaiting elevator service is greater in a downward direction, the process proceeds to step 948, and the central scheduling dispatcher, such as central scheduling dispatcher 1 604, can direct the elevator car, such as the elevator car 626, such as to the elevator car's operational controller or processor, to proceed on a transport path in a downward direction at step 948, for example. Also, the transport path of the elevator car 626 can be upward, such as from the floor 2, to take the persons awaiting elevator service in a downward direction waiting at the floor 3, or can be downward, such as from the floor N, to take the persons awaiting elevator service at the floor 3, in an upward direction, for example.
Continuing with reference to step 912, if it is determined there is more than one central scheduling dispatcher in the smart elevator system 600 at step 912, the process proceeds to step 914. At step 914, the at least one controller, such as the controllers 670, 672, 674 and 676 or the controllers 686, 688, 690 and 692, sends the passenger information to the at least one corresponding central scheduling dispatcher, such as the corresponding central scheduling dispatcher 604, 606 or 608. The process proceeds to step 916, where the passenger information is then passed by the at least one corresponding central scheduling dispatcher to the primary processor, such as a computer implemented device, e.g. the overall elevator dispatcher unit (OEDU) 602.
At step 918, the overall elevator dispatcher unit, such as the overall elevator dispatcher unit 602, receives passenger traffic information from one or more central scheduling dispatchers, such as the central scheduling dispatchers 604, 606 and 608. Upon receipt of all the passenger traffic information, the overall elevator dispatcher unit 602 can compare the number of people awaiting elevator service in the passenger information against a value of at least one person awaiting elevator service, for example, at step 920. If it is determined that there is not at least one person awaiting elevator service at step 920, the process proceeds to step 930 where the corresponding elevator cars remain on the current floors or return to the default floors, as the determined transport path, and the process then proceeds to return to step 902.
If there is at least one person awaiting elevator service at step 920, the process proceeds to step 922 where the overall elevator dispatcher unit, such as the overall elevator dispatcher unit 602, determines the transport path for at least one elevator car of a group of elevator cars and determines from the group of elevator cars, at least one elevator car of a total number of, or of a plurality of, elevator cars to service an elevator floor or floors for the person or persons awaiting elevator service at step 922. Based on the determination, at step 924, the overall elevator dispatcher unit, such as the overall elevator dispatcher unit 602, sends the one or more determined transport paths for the one or more elevator cars of the group of elevator cars to the corresponding central scheduling dispatchers, such as the central scheduling dispatcher 1 604, the central scheduling dispatcher 2 606 through the central scheduling dispatcher N 608, of a group of central scheduling dispatchers.
Based on the received determined one or more transport paths, the process proceeds to step 926 where at least one of the central scheduling dispatchers, such as at least one of the central scheduling dispatchers 1 604 through N 608, sends instructions for a corresponding determined transport path, such as can include an upward transport path, a downward transport path, or a combination thereof, to a corresponding elevator car, such as to the elevator car's operational controller or processor. Also, the transport path of an elevator car can be upward, such as from the floor 2, to take the persons awaiting elevator service in a downward direction waiting at the floor 3, or can be downward, such as from the floor N, to take the persons awaiting elevator service at the floor 3, in an upward direction, for example.
Further, it will be appreciated that embodiments of smart elevator systems and embodiments of methods for operating smart elevator systems can be implemented by one or more computer implemented devices, such as for the various controllers or processors of a smart elevator system, in which the instructions for operating the smart elevator system can be stored in a memory of and implemented by the computer implemented device, such as a processor, computer or computer server, for example. In such embodiments, the one or more computer implemented devices and one or more implementing computer applications includes hardware, such as can include processors and memory, and software for adapting and implementing the operation of embodiments of smart elevator systems and methods for operating smart elevator systems, such as by computer architecture and schematic processes, as described, such as in in relation to the smart elevator systems 200, 400 and 600 of
In
Examples of computer readable media as can be used or included in the memory 1004 can include a non-transitory computer readable storage memory, a magnetic recording apparatus, an optical disk, a magneto-optical disk, and/or a semiconductor memory (for example, RAM, ROM, etc.). Examples of magnetic recording apparatus that may be used in addition to memory 1004, or in place of the memory 1004, include a hard disk device (HDD), a flexible disk (FD), and a magnetic tape (MT). Examples of the optical disk include a DVD (Digital Versatile Disc), a DVD-RAM, a CD-ROM (Compact Disc-Read Only Memory), and a CD-R (Recordable)/RW.
For example, information or data can be transmitted from or received by the interface 1002, such as received sensor data and information as to a number of passengers awaiting transport in a floor elevator waiting area or a number of passengers in an inner area inside an elevator car, and transmitted information or data as to a determined transport path or determined transport paths for a corresponding one or more elevator cars, for example. Such information or data can be organized in the memory 1004 and transmitted to or from the memory 1004, such as a computer readable memory, at 1012 to the controller/processor 1006 or at 1010 to the interface 1002, for example.
Operations are performed by the controller/processor 1006, which can be any suitable type of computer implemented device, such as a computer processor, for example, as discussed. Also, the resulting information, resulting data or resulting determination made by the controller/processor 1006 from the information or data processed by the controller/processor 1006 can be stored in the memory 1004 and can be transmitted through the interface 1002, such as to one or more of the controllers or processors in the smart elevator system, such as to implement a determined transport path or to provide information or data to be displayed to passengers awaiting elevator service or currently being serviced by the at least one elevator car on the display 109, such as a digital display, for example, in an area near an elevator door. The display 109, such as a digital display, can show a number of passengers currently inside the at least one elevator car, whether the at least one elevator car is full, and the estimated time of arrival of the at least one elevator car to the corresponding floor, for example.
Embodiments of smart elevator systems and the methods for operating smart elevator systems, such as can be implemented through the use of one or more sensor apparatuses, memories and processors, for example, can also include for the master or primary processor to transmit the selected elevator path to the elevator car and the selected elevator path as can be displayed on a display associated with the elevator car, such as a computer monitor or digital screen, such as the display 109. Also, embodiments of smart elevator systems and the methods for operating smart elevator systems can also include for the master or primary processor to transmit passenger traffic information as can be displayed on a display associated with the elevator car, such as a computer monitor or digital screen, such as the display 109.
Further, embodiments of smart elevator systems and the methods for operating smart elevator systems can also include for the master or primary processor to transmit the number of passengers inside a corresponding elevator car, to indicate or specify whether the corresponding elevator car is full, and an estimated time of arrival for the corresponding elevator car as can be displayed on a display associated with the elevator car, such as a computer monitor or digital screen, such as the display 109, for example.
A depiction of the digital display can be shown by referencing
In obtaining, processing and displaying information on the display 109, the inner elevator sensor 160 can scan and detect the number of passengers inside the inner area 158 of the at least one elevator car, such as the three passengers being serviced in
The primary processor can receive the determined passenger information from the controller 108, or other processors in the smart elevator system, and include the determined passenger information on the number of passengers currently being serviced by the at least one elevator car in the decision process along with other information for selecting one or more elevator transport paths. After the primary processor has selected at least one elevator transport path, the primary processor can also transmit, for example, a direction of the selected at least one elevator transport path, the number of passengers inside of a corresponding elevator car, whether the corresponding elevator car is empty or full, and the estimated time of arrival of the corresponding elevator car to the display 109, such as a digital display, to the corresponding one or more floors where elevator service is requested or serviced by the at least one elevator car.
The information and operations that are transmitted throughout the various embodiments of a smart elevator system or methods for operating an elevator system can be in the form of electronic data, wireless signals, or a variation thereof. The information and operations that are transmitted throughout the various embodiments can be sent wirelessly, optically, or by any of various types or arrangements of hard wire connections, or combinations thereof, among the various system components, for example.
It is to be understood that the present invention is not limited to the embodiments described above, but encompasses any and all embodiments within the scope of the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4852696 | Fukuda | Aug 1989 | A |
| 4958707 | Yoneda | Sep 1990 | A |
| 5487451 | Hughes | Jan 1996 | A |
| 6202799 | Drop | Mar 2001 | B1 |
| 6257373 | Hikita | Jul 2001 | B1 |
| 6601679 | Crenella et al. | Aug 2003 | B2 |
| 6986408 | Takeuchi | Jan 2006 | B2 |
| 6988071 | Gazdzinski | Jan 2006 | B1 |
| 7552802 | Hirade | Jun 2009 | B2 |
| 7823702 | Hirade | Nov 2010 | B2 |
| 8020672 | Lin | Sep 2011 | B2 |
| 8096388 | Nakamura | Jan 2012 | B2 |
| 8584811 | Kuoppala | Nov 2013 | B2 |
| 8857569 | Friedli | Oct 2014 | B2 |
| 8905195 | Finschi | Dec 2014 | B2 |
| 20070041352 | Frankel et al. | Feb 2007 | A1 |
| 20150034426 | Armistead | Feb 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 101116367 | Jan 2008 | CN |
| 101955094 | Jan 2011 | CN |
| WO 2007020907 | Feb 2007 | WO |
| WO 2009078536 | Jun 2009 | WO |
| WO 2011009356 | Jan 2011 | WO |
| Entry |
|---|
| Seng-Yong Lau et al., “Sensor Networks for Everyday Use: The BL-Live Experience”, IEEE International Conference onSensor Networks, Ubiquitous, and Trustworthy Computing, 2006., Jun. 5-7, 2006, Taichung, Taiwan, 7 pages. |
| Z. Shuai et al., “Traffic Modeling and Prediction Using Camera Sensor Networks”, ICDSC 2010, Aug. 31-Sep. 4, 2010, Atlanta, GA, USA, pp. 49-56. |
| Hamza Ijaz Abbasi et al., “Implementation of Smart Elevator System based on Wireless Multi-hop AdHoc Sensor Networks”, 2011, 2nd IEEE Conference on NESEA, Dec. 8-9, 2011, Perth Australia, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150096843 A1 | Apr 2015 | US |
