DETECTING A PROBE REQUEST IN METHOD AND SYSTEM FOR CONTROLLING AN ELEVATOR CAR

Abstract

An elevator system with an elevator car includes a controller for the elevator car, at least one processor, and a wireless network access point. According to a method of controlling the elevator car, a portable device transmits a probe request, the portable device is carried by a passenger of the elevator system. The probe request contains at least a first probe request data set, the first probe request data set is of a first type. The wireless network access point detects the probe request. The at least one processor accesses data storage. In the data storage there is stored a plurality of passenger profiles. Each passenger profile of the plurality of passenger profiles contains a first profile data set of the first type and a second profile data set representing at least one destination floor.

Claims

1. A method of controlling an elevator car (203; 203A; 203B) in an elevator system (201, 501, 601), wherein the elevator system (201, 501, 601) comprises a controller (207; 207A; 207B) for the elevator car (203; 203A; 203B), at least one processor (211; 211A, 211B, 609), and a wireless network access point (215; 215A; 215B; 607); the method comprising: a portable device (231; 521, 523) transmitting a probe request (233; 517, 519), wherein the portable device (231; 521, 523) is carried by a passenger (229; 511, 513) of the elevator system (201, 501, 601), and wherein the probe request (233; 517, 519) contains at least a first probe request data set (235), wherein the first probe request data set (235) is of a first type; the wireless network access point (215; 215A; 215B; 607) detecting the probe request (233; 517, 519); the at least one processor (211; 211A, 211B, 609) accessing data storage (213; 213A, 213B, 611) having stored therein a plurality of passenger profiles (217; 217A, 217B, 613) wherein each passenger profile (241) of the plurality of passenger profiles (217; 217A, 217B, 613) contains a first profile data set (243) of the first type and a second profile data set (247) representing at least one destination floor; the at least one processor (211; 211A, 211B, 609) identifying a matching passenger profile (249; 525; 527; 615; 617) of the plurality of passenger profiles (217; 217A, 217B, 613), wherein the first profile data set (243) of the matching passenger profile (249; 525; 527; 615; 617) matches the first probe request data set (235); the at least one processor (211; 211A, 211B, 609) determining an anticipated destination floor based on the second profile data set (247) of the matching passenger profile (249; 525; 527; 615; 617); and the at least one processor (211; 211A, 211B, 609) instructing the controller (207; 207A; 207B) to move the elevator car (203; 203A; 203B) to the anticipated destination floor.

2. The method of claim 1, wherein the first probe request data set (235) comprises a list of one or more Service Set Identifiers (237).

3. The method of claim 1, wherein the elevator system (501, 601) comprises one or more further wireless network access points (215A; 215B, 607).

4. The method of claim 1, wherein the wireless network access point (215; 215A; 215B) is located in or on the elevator car (203; 203A; 203B).

5. The method of claim 1, wherein the wireless network access point (215A; 215B) is located in or on the elevator car (203A, 203B) and the elevator system (601) comprises a further wireless network access point (607) in a respective elevator hall (605) on each floor served by the elevator system (601).

6. The method of claim 1, wherein the wireless network access point (607) is located in an elevator hall (605) on a floor served by the elevator system (601).

7. The method of claim 1, wherein the portable device (231; 521, 523) transmits a plurality of probe requests, wherein the probe request (233; 517, 519) is one of said plurality of probe requests.

8. The method of claim 1, further comprising detecting at least one further probe request transmitted by the portable device (231; 521, 523).

9. The method of claim 1, further comprising detecting, by a further wireless access point (215A, 215B, 607) or by one of the one or more further wireless access points (215A, 215B, 607), at least one further probe request transmitted by the portable device (231; 521, 523).

10. The method of claim 1, further comprising: the at least one processor (211; 211A, 211B, 609) determining that a subsequent probe request has not been detected; in response to the at least one processor (211; 211A, 211B, 609) determining that the subsequent probe request has not been detected, the at least one processor (211; 211A, 211B, 609) determining that the passenger (229; 511, 513) has exited the elevator car (203; 203A; 203B); and the at least one processor (211; 211A, 211B, 609) determining a floor on which the passenger (229; 511, 513) exited the elevator car (203; 203A; 203B).

11. The method of claim 1, further comprising: receiving input from the passenger (229; 511, 513) to override the anticipated destination floor or to add a destination floor.

12. The method of claim 1, further comprising updating the matching passenger profile (249; 525; 527; 615; 617) based on the input received to override the anticipated destination floor or to add a destination floor and/or in response to determining the passenger (229; 511, 513) has exited the elevator car (203; 203A; 203B) at a different floor from the anticipated destination floor.

13. The method of claim 1, further comprising: the wireless network access point (215; 215A; 215B; 607) detecting a new probe request from a further portable device carried by a further passenger, wherein the new probe request contains at least a first new probe request data set and wherein the first new probe request data set is of the first type; the at least one processor (211; 211A, 211B, 609) determining that no matching passenger profile exists for which the first passenger profile data set matches the first new probe request data set; and the at least one processor (211; 211A, 211B, 609) creating a new passenger profile in the data storage, wherein the new passenger profile includes a first new passenger profile data set which comprises the first new probe request data set.

14. The method of claim 1, wherein the elevator system (501; 601) comprises more than one elevator car (203A; 203B).

15. An elevator system (201, 501, 601), comprising: an elevator car (203; 203A; 203B); a controller (207; 207A; 207B) for controlling the elevator car (203; 203A; 203B); a wireless network access point (215; 215A; 215B; 607) configured to detect a probe request (233; 517, 519) transmitted by a portable device (231; 521, 523) carried by a passenger (229; 511, 513) of the elevator system (201, 501, 601), wherein the probe request (233; 517, 519) contains at least a first probe request data set (235), wherein the first probe request data set (235) is of a first type; at least one processor (211; 211A, 211B, 609); and a computer-readable medium (213; 213A, 213B) having stored therein instructions which, when executed by the at least one processor (211; 211A, 211B, 609), cause the at least one processor (211; 211A, 211B, 609) to carry out the following method steps: accessing data storage (213; 213A, 213B, 611), the data storage having stored therein a plurality of passenger profiles (217; 217A, 217B, 613) wherein each passenger profile (241) of the plurality of passenger profiles (217; 217A, 217B, 613) contains a first profile data set (243) of the first type and a second profile data set (247) representing at least one destination floor; identifying a matching passenger profile (249; 525; 527; 615; 617) of the plurality of passenger profiles (217; 217A, 217B, 613), wherein the first profile data set (243) of the matching passenger profile (249; 525; 527; 615; 617) matches the first probe request data set (235); determining an anticipated destination floor based on the second profile data set (247) of the matching passenger profile (249; 525; 527; 615; 617); and instructing the controller (207; 207A; 207B) to move the elevator car (203; 203A; 203B) to the anticipated destination floor.

Description

DRAWING DESCRIPTION

[0083] Certain preferred examples of this disclosure will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0084] FIG. 1 shows a schematic illustration of an elevator system that may be used in various examples in accordance with the present disclosure;

[0085] FIG. 2 shows a schematic illustration of a first example of an elevator system in accordance with the present disclosure;

[0086] FIG. 3 shows an illustration representing a probe request that may be employed in methods and elevator systems in accordance with the present disclosure;

[0087] FIG. 4 shows an illustration representing an example passenger profile that may be employed in methods and elevator systems in accordance with the present disclosure;

[0088] FIG. 5 shows a schematic illustration of a second example of an elevator system in accordance with the present disclosure;

[0089] FIG. 6 shows a schematic illustration of a third example of an elevator system in accordance with the present disclosure; and

[0090] FIG. 7 shows a flowchart illustrating a method in accordance with the present disclosure.

DETAILED DESCRIPTION

[0091] FIG. 1 is a perspective view of an elevator system 101 including an elevator car 103, a counterweight 105, a tension member 107, a guide rail 109, a machine 111, a position reference system 113, and a controller 115. The elevator car 103 and counterweight 105 are connected to each other by the tension member 107. The tension member 107 may include or be configured as, for example, ropes, steel cables, and/or coated-steel belts. The counterweight 105 is configured to balance a load of the elevator car 103 and is configured to facilitate movement of the elevator car 103 concurrently and in an opposite direction with respect to the counterweight 105 within an elevator hoistway 117 and along the guide rail 109.

[0092] The tension member 107 engages the machine 111, which is part of an overhead structure of the elevator system 101. The machine 111 is configured to control movement between the elevator car 103 and the counterweight 105. The position reference system 113 may be mounted on a fixed part at the top of the elevator hoistway 117, such as on a support or guide rail, and may be configured to provide position signals related to a position of the elevator car 103 within the elevator hoistway 117. In other examples, the position reference system 113 may be directly mounted to a moving component of the machine 111, or may be located in other positions and/or configurations as known in the art. The position reference system 113 can be any device or mechanism for monitoring a position of an elevator car and/or counterweight, as known in the art. For example, without limitation, the position reference system 113 can be an encoder, sensor, or other system and can include velocity sensing, absolute position sensing, etc., as will be appreciated by those of skill in the art.

[0093] The controller 115 is located, as shown, in a controller room 121 of the elevator hoistway 117 and is configured to control the operation of the elevator system 101, and particularly the elevator car 103. For example, the controller 115 may provide drive signals to the machine 111 to control the acceleration, deceleration, leveling, stopping, etc. of the elevator car 103. The controller 115 may also be configured to receive position signals from the position reference system 113 or any other desired position reference device. When moving up or down within the elevator hoistway 117 along guide rail 109, the elevator car 103 may stop at one or more landings 125 as controlled by the controller 115. Although shown in a controller room 121, those of skill in the art will appreciate that the controller 115 can be located and/or configured in other locations or positions within the elevator system 101.

[0094] The machine 111 may include a motor or similar driving mechanism. In accordance with examples of the disclosure, the machine 111 is configured to include an electrically driven motor. The power supply for the motor may be any power source, including a power grid, which, in combination with other components, is supplied to the motor. The machine 111 may include a traction sheave that imparts force to tension member 107 to move the elevator car 103 within elevator hoistway 117.

[0095] Although shown and described with a roping system including a tension member 107, elevator systems that employ other methods and mechanisms of moving an elevator car within an elevator hoistway may employ examples of the present disclosure. For example, examples may be employed in ropeless elevator systems using a linear motor to impart motion to an elevator car. Examples may also be employed in ropeless elevator systems using a hydraulic lift to impart motion to an elevator car. FIG. 1 is merely a non-limiting example presented for illustrative and explanatory purposes.

[0096] FIG. 2 shows a schematic illustration of a first example of an elevator system 201 in accordance with the present disclosure. The elevator system 201 may for example incorporate the structure of the elevator system 101 depicted in FIG. 1, although this is not essential.

[0097] The elevator system 201 comprises an elevator car 203 operating within a vertical elevator hoistway 205 between floors in a building. The elevator car 203 is controlled by a controller 207 that is positioned in a control room (omitted for clarity) adjacent to the elevator hoistway 205.

[0098] The elevator car 203 comprises a communications control board 209. The communications control board 209 comprises a processor 211, a memory 213 that is accessible by the processor 211, and a wireless network access point 215 in communication with the processor 211. In this example, the wireless network access point 215 is a Wi-Fi access point (hereafter Wi-fi AP). Stored in the memory 213 is a plurality of passenger profiles 217. Although in this example, the plurality of passenger profiles 217 is stored in the memory 213 that is part of the elevator system 201, in other examples and in variations on this example, the plurality of passenger profiles 217 may be stored in a memory that is not part of the elevator system 201, e.g. on a remote server or in the cloud.

[0099] The elevator car 203 also comprises a floor-selection panel 219 in communication with the processor 211. The floor-selection panel 219 comprises a number of buttons 221 corresponding to floors served by the elevator system 201, which a passenger can press to select a floor for the elevator car 203 to travel to.

[0100] The elevator car 203 is accessible via an elevator hall 223. In the elevator hall 223 there is an elevator-calling panel 225 comprising a button 227 for summoning an elevator car 203. The elevator-calling panel 225 is in communication with the controller 207.

[0101] A passenger 229 in the elevator hall 223 wishing to use the elevator system 201 can summon an elevator car 203 by pressing the button 227. When the passenger 229 pushes the button 227, the elevator-calling panel 225 communicates with the controller 207, which controls the elevator car 203 to move it to the floor where elevator-calling panel 225 is located. When the elevator car 203 arrives at the floor, the passenger 229 enters the elevator car 203.

[0102] The passenger 229 is carrying a portable device 231 which is Wi-fi-enabled, i.e. it is capable of connecting to a Wi-Fi network. The portable device 231 continually transmits probe requests 233 for the purpose of network discovery, e.g. in accordance with the IEEE 802.11 WLAN protocol.

[0103] When the passenger 229 is in the elevator car 203, the Wi-Fi AP 215 detects a probe request 233 transmitted by the portable device 231. The content of the probe request 233 is represented schematically in FIG. 3. The probe request 233 comprises a first probe request data set 235, which comprises a list of Service Set Identifiers (SSIDs) 237 corresponding to Wi-Fi networks known to the portable device 231 (e.g. to which the portable device 231 has previously connected). The probe request 233 may comprise other data 239, e.g. which may be intended for use in establishing a network connection.

[0104] The Wi-Fi AP 215 communicates the list of SSIDs 237 to the processor 211. The processor 211 accesses the plurality of passenger profiles 217 in the memory 213. The content of an example passenger profile 241 is represented schematically in FIG. 4. The example passenger profile 241 comprises first passenger profile data 243 which comprises an SSID list 245 that was previously received via a probe request from a corresponding portable device carried by a passenger. The passenger profile is thereby associated with the passenger carrying the corresponding portable device. The example passenger profile 241 also comprises second passenger profile data 247 representing at least one destination floor. For example, the second passenger profile data 247 may include a list of destination floors with frequency data indicating how frequently the passenger visits each floor. As another example, the second passenger profile data 247 may include a list of days and times, with an indication of the most frequently visited destination floor for the corresponding day and time. These are just two non-limiting examples of data that may be included in the second passenger profile data 247 and other examples are possible.

[0105] The processor 211 compares the list of SSIDs 237 from the probe request 233 with the SSID lists 245 of the plurality of passenger profiles 217 in the memory 213 and identifies a matching passenger profile 249 which contains the same SSIDs as the list of SSIDs 237 from the probe request 233. The processor 211 determines from the second passenger profile data 247 that the passenger with whom the passenger profile is associated most frequently visits the 7th floor. The processor 211 then instructs the controller 207 to move the elevator car 203 to the 7th floor. As another example, the processor 211 may determine that the current day and time is Wednesday at 2:30 pm. The processor 211 may determine from the second passenger profile data 247 that on Wednesdays between 2 pm and 3 pm, the passenger's most frequently visited floor is the 4th floor. This situation might arise, for example, if the passenger 229 usually works on the 7th floor but has a regular appointment (e.g. a team meeting) on Wednesdays at 2:30 pm on the 4th floor. Other examples are possible for how a passenger's anticipated destination floor may be determined based on the second passenger profile data 247.

[0106] In an alternative scenario in accordance with the method of the present disclosure, the passenger 229 might not intend to go to the 4th floor, even though it is Wednesday at 2:30 pm. For example, they may have joined a different team with a regular meeting on the 3rd floor instead. When the processor 211 determines that the anticipated floor is the 4th floor, the processor 211 may cause the floor-selection panel 219 in the elevator car 203 to indicate the anticipated destination floor, e.g. by illuminating the button 251 corresponding to the 4th floor.

[0107] The passenger 229 may see that the button 251 for the 4th floor is illuminated and recognise that the anticipated destination floor needs to be corrected. The passenger 229 may press the button 253 for the 3rd floor to add the 3rd floor as a destination floor. The 4th floor may be automatically cancelled as a destination floor in response to the passenger 229 selecting the 3rd floor, or the passenger 229 might press the button 251 for the 4th floor to cancel it as a destination floor. The elevator car 203 then travels to the 3rd floor.

[0108] The processor 211 may update the matching passenger profile 249 to reflect the passenger's input to override the determination of the 4th floor as the anticipated destination floor. For example, the matching passenger profile 249 may be updated to record a change in the frequency of visiting the 4th floor and the 3rd floor during the day and time interval of 2 pm to 3 pm on Wednesdays. If the passenger 229 corrects the destination floor from the 4th floor to the 3rd floor a threshold number of times, the matching passenger profile 249 may be updated so that the 4th floor is indicated to be the anticipated destination floor for the day and time interval of 2 pm to 3 pm on Wednesdays.

[0109] In another alternative scenario in accordance with the method of the present disclosure, the passenger 229 may board the elevator car 203 and the processor 211 may determine the 4th floor to be the anticipated destination floor. However, the passenger 229 may board the elevator car 203 with a second passenger who is another, long-standing member of the new team. Following the method of the present disclosure for the second passenger, the processor 211 may determine the 3rd floor to be the anticipated destination floor for the second passenger. The processor 211 may cause the buttons 251, 253 for both the 3rd floor and the 4th floor to be illuminated. The passenger 229 may note that two buttons 251, 253 are illuminated, but may not provide any input via the buttons 221 because their actual intended destination floor (the 3rd floor) is already indicated. Both passengers may exit for their meeting on the 3rd floor.

[0110] The passenger's portable device 231 continually transmits probe requests 233 as part of its network discovery protocol. The Wi-Fi AP 215 in the elevator car 203 therefore continues to detect probe requests 233 from the portable device 231 while the portable device 231 is in the elevator car 203. However, when the passenger 229 exits the elevator car 203 on the 3rd floor with the second passenger, the Wi-Fi AP 215 ceases to receive further probe requests from the portable device 231. The processor 211 determines from the Wi-Fi AP 215 that the Wi-Fi AP 215 stopped receiving probe requests when the elevator car 203 was on the 3rd floor. The processor 211 determines that the passenger 229 exited the elevator car 203 on the 3rd floor instead of on the anticipated destination floor which was the 4th floor. The processor 211 may update the matching passenger profile 249 to reflect the determination that the passenger 229 exited on the 3rd floor instead of the anticipated floor.

[0111] FIG. 5 shows a schematic illustration of a second example of an elevator system 501 in accordance with the present disclosure. The elevator system 501 may for example incorporate the structure of the elevator system 101 depicted in FIG. 1, although this is not essential.

[0112] The elevator system 501 comprises first and second elevator cars 203A, 203B operating within respective vertical elevator hoistways 205A, 205B between floors in a building. Each elevator car 203A, 203B is controlled by a respective controller 207A, 207B that is positioned in the respective elevator hoistway 205A, 205B.

[0113] Each elevator car 203A, 203B has the same structure and features as the elevator car 203 described with respect to FIG. 2, although this is not essential and variations are possible. Corresponding features of the elevator cars 203A, 203B are labelled with the same reference numerals as in FIG. 2 except that a suffix A or B is added to distinguish between features of the first and second elevator cars 203A, 203B.

[0114] One controller 207A is designated a group controller or master controller, and is used to coordinate movement of the elevator cars 203A, 203B, for example in response to an elevator call summoning one of the elevator cars 203A, 203B for use by a passenger.

[0115] One memory 213A is designated the master memory, and contains a definitive version of the plurality of passenger profiles 217A. The other memory 213B is synchronized to the master memory 213A, i.e. to bring the content of the other memory 213B into conformity with the content of the master memory 213A (e.g. periodically or in response to a change in the content of the master memory 213A). Although in this example one memory 213A of the memories 213A, 213B is designated the master memory, in other examples and in variations on this example, a different memory (e.g. on a remote server or in the cloud) may serve as a master memory. It is to be understood that in this example, the memories 213A, 213B in the elevator cars 203A, 203B together constitute data storage as discussed above.

[0116] The elevator system 501 is accessible via an elevator hall 503. In the elevator hall 503, there is an elevator-calling panel 505. However, in this example, the elevator-calling panel 505 comprises a go up button 507 and a go down button 509. Passengers 511, 513 in the elevator hall wishing to use the elevator system 501 can summon one of the elevator cars 203A, 203B by pressing the go up button 507 or the go down button 509, depending on whether they wish to travel up or down relative to their current floor. Providing a go up button 507 and a go down button 509 instead of a single button for summoning one of the elevator cars 203A, 203B may help the group controller 207A to coordinate the movement of the elevator cars 203A, 203B, e.g. sending only one car if multiple passengers wish to travel in the same direction and sending two cars if the passengers wish to travel in different directions.

[0117] When the passengers 511, 513 have summoned an elevator car using the elevator-calling panel 505, the group controller 207A sends the appropriate number of elevator cars 203A, 203B to the floor where the elevator-calling panel 505 is located. An indicator 515 over each elevator access door (omitted for clarity) may indicate each elevator car's designated direction of travel to help the passengers 511, 513 board the correct elevator car.

[0118] The passengers 51, 513 board the elevator cars 203A, 203B. The Wi-Fi AP 215A, 215B in each elevator car 203A, 203B detects respective probe requests 517, 519 transmitted by portable devices 521, 523 carried by the passengers 511, 513, and determines an anticipated destination floor for each passenger 511, 513 in the same manner as described above with respect to FIG. 2. The controller 207A, 207B for each elevator car 203A, 203B moves the respective elevator car 203A, 203B to each anticipated destination floor of the passengers 511, 513 in said elevator car 203A, 203B in an appropriate order.

[0119] The passengers 511, 513 may override or cancel the anticipated destination floor or add a new destination floor in the same manner as described above with respect to FIG. 2. The processor 211A, 211B in each elevator car 203A, 203B may use the Wi-Fi AP 215A, 215B in the respective elevator car 203A, 203B to determine on which floor each passenger 511, 513 exits the elevator car 203A, 203B in the same manner as described above with respect to FIG. 2. The processors 211A, 211B may determine that the passengers 511, 513 left on their respective anticipated destination floor or on a different floor.

[0120] The processor 211A, 211B in each elevator car 203A, 203B may update the passenger profile 525, 527 for each passenger 511, 513 in the elevator cars 203A, 203B at the master memory 213A, based on any input from the passengers 511, 513 (e.g. overriding or cancelling the anticipated destination floor or adding a destination floor) or based on the respective floor on which each of the passengers 511, 513 exited the elevator cars 203A, 203B. The other memory 213B may be synchronized to the master memory 213A, e.g. in response to the master memory 213A being updated or during a periodic synchronization process.

[0121] FIG. 6 shows a schematic illustration of a third example of an elevator system 601 in accordance with the present disclosure. The elevator system 601 has the same structure and features as the elevator system 501 depicted in FIG. 5, except that in the example of FIG. 6 there is a communications control board 603 in the elevator hall 605 on each floor. The communications control board 603 comprises a Wi-Fi AP 607, a processor 609 and a memory 611. The memory 611 has stored therein a copy 613 of the plurality of passenger profiles 217A, 217B that is also stored in each memory in each elevator car 203A, 203B. It is to be understood that in this example, the memories 213A, 213B in the elevator cars 203A, 203B together with the memory 611 in the elevator hall 605 on each floor constitute the data storage as discussed above.

[0122] Features depicted in FIG. 6 that are the same as corresponding features depicted in FIG. 5 are labelled with the same reference numerals.

[0123] Similarly to the example of FIG. 5, one of the memories 213A, 213B, 611 is designated the master memory (e.g. the memory 611 on an entrance-level floor) and the other memories 213A, 213B are synchronized with the master memory 611 (e.g. periodically or in response to a change in the data stored in the master memory 611). Although in this example, the memory 611 is designated the master memory, in variations on this example and in other examples, a different memory e.g. that is separate from the elevator system (e.g. on a remote server or in the cloud) may serve as a master memory.

[0124] In this example, the Wi-Fi AP 607 in the elevator hall 605 may be used to automatically call one or more elevator cars 203A, 203B for one or more passengers 511, 513 in the elevator hall 605.

[0125] For example, two passengers 511, 513 may arrive in the elevator hall 605, carrying respective portable devices 521, 523. Each portable device 521, 523 continually transmits probe requests 517, 519 according to a network discovery protocol, wherein each probe request 517, 519 contains a list of SSIDs for the respective portable device 521, 523. The Wi-Fi AP 607 detects a probe request 517, 519 from each portable device 521, 523, and in a similar manner to that described above with reference to FIG. 2, the processor 609 in the elevator hall 605 uses the list of SSIDs to identify a respective matching passenger profile 615, 617 for each passenger 511, 513 from the plurality of passenger profiles 613 in the memory 611. The processor 609 determines a respective anticipated destination floor for each passenger 511, 513 based on the respective matching passenger profile 615, 617.

[0126] The processor 609 communicates with the group controller 207A to indicate the required number of elevator cars 203A, 203B. In this example, the two passengers 511, 513 arrive in the elevator hall 605 on the 3rd floor. The anticipated destination floor for one passenger 511 is the 1st floor and the anticipated destination floor for the other passenger 513 is the 5th floor. The processor 609 communicates to the group controller 207A that an elevator car 203A to go down and an elevator car 203B to go up are required. The group controller 207A coordinates sending elevator cars 203A, 203B accordingly.

[0127] When the elevator cars 203A, 203B arrive, an indicator 515 above each elevator car 203A, 203B indicates the designated direction of travel for each elevator car 203A, 203B and the passengers 511m 513 board the elevator cars 203A, 203B.

[0128] In some variations and alternative scenarios, the processor 609 may communicate the anticipated destinations floors to the respective processors 211A, 211B in each elevator car 203A, 203B. The processor 211A, 211B in each elevator car 203A, 203B may then instruct the respective controller 207A, 207B for each elevator car 203A, 203B to move the elevator car 203A, 203B to the respective anticipated destination floor. This approach may be applicable, for example, when only one elevator car is required (as it may be assumed that the one elevator car should visit all anticipated destination floors). However, in this example involving using two elevator cars 203A, 203B, there is a possibility that a passenger 511, 513 may board the wrong elevator car 203A, 203B. There is also a possibility that a passenger may be detected in the elevator hall 605 who does not intend to travel.

[0129] In this example, to help to ensure that the correct floors are visited, the Wi-Fi AP 215A, 215B in each elevator car 203A, 203B detects a probe request 517, 519 from the portable device 521, 523 of the passenger 511, 513 in the respective elevator car 203A, 203B, and determines an anticipated destination floor for the respective passenger 511, 513 in the same manner as described above with reference to FIG. 2. As the probe requests 517, 519 from any given portable device 521, 523 all contain the same SSID list as each other probe request 517, 519 from the same portable device 521, 523, for each passenger 511, 513, the matching passenger profile 525, 527 identified by the processor 211A, 211B in the elevator car 203A, 203B will be the same as the matching passenger profile 615, 617 identified by the processor 609 in the elevator hall 605. Therefore, for each passenger 511, 513, the respective processor 211A, 211B in the elevator car 203A, 203B will determine the same anticipated destination floor as was determined by the processor 609 in the elevator hall 605. However, by repeating the determination of the anticipated destination floor based on the probe request 517, 519 detected by the Wi-Fi APs 215A, 215B in the elevator cars 203A, 203B, it can be checked which elevator car 203A, 203B contains which passenger 511, 513 and therefore which anticipated destination floor each elevator car 203A, 203B should visit.

[0130] Each passenger 511, 513 may override or cancel the anticipated destination floor or add a new destination floor in the same manner as described above with respect to FIG. 2.

[0131] The processor 211A, 211B in each elevator car 203A, 203B may use the Wi-Fi AP 215A, 215B in the respective elevator car 203A, 203B to determine on which floor each passenger 511, 513 exits the elevator car 203A, 203B in the same manner as described above with respect to FIG. 2. However, as noted above, there is a Wi-Fi AP 607 in the elevator hall 605 of each floor. Therefore, in this example, additionally or alternatively, the Wi-Fi AP 607 in the elevator hall 605 on the floor on which each passenger 511, 513 exits the respective elevator car 203A, 203B may detect a probe request 517, 519 from the respective passenger's portable device 521, 523. The processor 609 in the or each elevator hall 605 may identify the matching passenger profile 615, 617 corresponding to the respective probe request 517, 519. The processor 609 may then make a determination that the passenger 511, 513 exited the elevator car 203A, 203B on the floor where the probe request 517, 519 was detected by the Wi-Fi AP 607. This may confirm or correct the determination of the floor on which each passenger 511, 513 exits the elevator cars 203A, 203B, as determined using the Wi-Fi APs 215A, 215B in the elevator cars 203A, 203B. For example, if there is a relatively long delay between probe requests 517, 519 transmitted by a portable device 521, 523, there may be ambiguity concerning which floor the elevator car 203A, 203B was on when the passenger 511, 513 exited the elevator car 203A, 203B.

[0132] After the floor on which each passenger 511, 513 exited has been determined, the processor 211A, 211B in the elevator car 203A, 203B may update the matching passenger profile 525, 527 for each passenger 511, 513 in the master memory 611 (e.g. via the processor 609 in the elevator hall 605). The other memories 213A, 213B may then by synchronized with the master memory 611 to reflect the update.

[0133] In an alternative scenario involving the example elevator system of FIG. 6, when the passengers 511, 513 first arrive in the elevator hall 605 to use the elevator system 601, the Wi-Fi AP 607 in the elevator hall 605 may detect a probe request 517 from a passenger's portable device 521, but the processor 609 may determine that no matching passenger profile exists in the plurality of passenger profiles 613 in the memory 611.

[0134] In this situation, the elevator-calling panel 505 may indicate to the passenger 511 that they should use the elevator-calling panel 505 to summon an elevator car 203a, 203B (e.g. by illuminating a light on the elevator-calling panel 505). This may help to avoid unnecessary elevator calls resulting from people passing through the elevator hall 605 that do not typically visit the floors served by the elevator system 601. Alternatively, the processor 609 may instruct the group controller 207A to send an elevator car 203A to the elevator hall 605, e.g. without indicating the direction of travel.

[0135] When an elevator car 203A arrives, the passenger 511 may enter, and the Wi-Fi AP 215A in the elevator car 203A may detect a probe request 517 from the passenger's portable device 521. The processor 211A in the elevator car 203A may use an SSID list from the probe request 517 to try to identify a matching passenger profile but determine that no matching passenger profile exists. The floor-selection panel 219A may indicate to the passenger 511 that they should select a floor (e.g. by illuminating a light on the floor-selection panel 219A). The passenger 511 selects a floor and the controller 207A moves the elevator car 203A to the selected floor.

[0136] The processor 211A in the elevator car 203A may then create a new passenger profile for the passenger 511, including adding the SSID list from the probe request 517 to the new passenger profile and adding information relating to the selected destination floor. The new passenger profile may be updated with each subsequent use of the elevator system 601 by the passenger 511 to build and refine the new passenger profile.

[0137] It will be appreciated that examples involving two elevator cars may be extended to more than two elevators cars.

[0138] FIG. 7 shows a flow chart illustrating an example method 701 in accordance with the present disclosure. The method 701 may be used to control an elevator car in an elevator system. The elevator car may be, for example, any of the elevator cars described above with reference to FIG. 1, FIG. 2, FIG. 5 or FIG. 6 above. However, this is not essential and the method may be used to control any elevator car in accordance with the present disclosure.

[0139] The method 701 of FIG. 7 is a method of controlling an elevator system comprising a controller for the elevator car, at least one processor, and a wireless network access point.

[0140] The method comprises a step 703 of a portable device transmitting a probe request, wherein the portable device is carried by a passenger of the elevator system, and wherein the probe request contains at least a first probe request data set, wherein the first probe request data set is of a first type.

[0141] The method comprises a step 705 of the at least one processor accessing data storage, the data storage having stored therein a plurality of passenger profiles wherein each passenger profile of the plurality of passenger profiles contains a first profile data set of the first type and a second profile data set representing at least one destination floor.

[0142] The method comprises a further step 707 of the wireless network access point detecting the probe request.

[0143] The method comprises a further step 709 of the at least one processor identifying a matching passenger profile of the plurality of passenger profiles, wherein the first profile data set of the matching passenger profile matches the first probe request data set.

[0144] The method comprises a further step 711 of the at least one processor determining an anticipated destination floor based on the second profile data set of the matching passenger profile.

[0145] The method comprises a further step 713 of the at least one processor instructing the controller to move the elevator car to the anticipated destination floor.

[0146] The method may comprise one or more additional steps in addition to the steps depicted in FIG. 7. The additional step(s) may each occur before, after or in between any of the steps depicted in FIG. 7.

[0147] It will be appreciated that although the passengers mentioned in the above examples may be people, the passengers may also be non-human (e.g. animals/pets, robots, objects, etc.), e.g. in variations on these examples and in other examples.

[0148] It will be appreciated by those skilled in the art that the disclosure has been illustrated by describing one or more specific aspects thereof, but is not limited to these aspects; many variations and modifications are possible, within the scope of the accompanying claims.