Patent Description:
Existing elevator systems allow a user to submit an elevator call (e.g., a hall call or a destination call) using their own mobile device (e.g., a smartphone).

<CIT> discloses a method for developing a routing plan for elevator passengers. Personalised data for each passenger such as social medial connections and job titles may be used to assign a plurality of users to a plurality of elevators such that certain passengers travel together, when their personalised data indicates a link between them. Users may input a destination and/or a "friend" request. Other methods for allocating elevators to passenger groups are known, for example from <CIT> and <CIT>.

According to a first aspect of the present invention, a method of operating an elevator call control system is provided. The method including: receiving a first elevator call from a first individual carrying a first mobile device, the first elevator call including a destination request to travel from a first boarding floor to a first destination floor; determining that the first individual carrying the first mobile device is traveling with a second individual, wherein the second individual is traveling to a second destination floor, wherein the determining that the first individual carrying the first mobile device is traveling with a second individual comprises: detecting a location of a second mobile device carried by the second individual; detecting a location of the first mobile device; and determining that the second mobile device is within a selected range of the first mobile device; assigning an elevator car to the first elevator call; and scheduling the elevator car to transport the first individual carrying the first mobile device and the second individual together to at least one of a first destination floor and the second destination floor.

Further embodiments may include: determining that the second individual is located on a second boarding floor different than the first boarding floor.

Further embodiments may include that determining that the second individual is located on a second boarding floor different than the first boarding floor further includes: receiving a selection input from the mobile device indicating that the second individual is located on a second boarding floor different than the first boarding floor.

Further embodiments may include that determining that the second individual is located on a second boarding floor different than the first boarding floor further includes: detecting a location of a second mobile device carried by the second individual.

Further embodiments may include that the second mobile device is determined to be within the selected range of the first mobile device when the first elevator call is received.

Further embodiments may include that the second mobile device is determined to be within the selected range of the first mobile device when the elevator car arrives at the first boarding floor.

Further embodiments may include that determining that the first individual carrying the first mobile device is traveling with a second individual further includes: quarrying at least one of a social media network and a hotel visitor guest database to determine whether the second individual is traveling with the first individual.

Further embodiments may include that the first destination floor and the second destination floor are the same.

Further embodiments may include that the first destination floor and the second destination floor are different.

Further embodiments may include: determining the first destination floor and the second destination floor.

Further embodiments may include that determining the first destination floor and the second destination floor further includes: receiving a selection input from the first mobile device indicating the first destination floor and the second destination floor.

Further embodiments may include that determining the first destination floor and the second destination floor further includes: quarrying at least one of a social media network and a hotel visitor guest database to determine the first destination floor and the second destination floor.

Further embodiments may include that detecting a location of the second mobile device further includes: connecting, using a building sensor, to the second mobile device via at least one of Wi-Fi and Bluetooth; and determining a distance between the building sensor and the second mobile device.

Further embodiments may include that detecting a location of the second mobile device further includes: detecting, using a building sensor, a wireless signal of the second mobile device, wherein the building sensor does not connect to the wireless signal; and determining a distance between the building sensor and the second mobile device.

Further embodiments may include that detecting a location of the second mobile device further includes: detecting a beacon transmitted by a building sensor using the second mobile device; and determining a distance between the building sensor and the second mobile device in response to a strength of the beacon.

According to another aspect of the present invention, an elevator system is provided in accordance with claim <NUM>.

Technical effects of embodiments of the present disclosure include determining how many other individuals piggy back on a single elevator call by tracking the location of mobile devices.

<FIG> depicts an elevator call control system <NUM> in an example embodiment. The elevator call control system <NUM> includes one or more elevator system <NUM> installed at a building <NUM>. In some embodiments, the building <NUM> may be a building or a collection of buildings that may or may not be physically located near each other. The building <NUM> may include any number of floors. Persons entering the building <NUM> may enter at a lobby floor, or any other floor, and may go to a destination floor via one or more conveyance devices, such as the elevator system <NUM>.

The elevator system <NUM> may be operably connected to one or more computing devices, such as a system controller <NUM>. The system controller <NUM> may be configured to control dispatching operations for one or more elevator cars <NUM> associated with one or more elevator systems <NUM>. It is understood that the elevator system <NUM> may utilize more than one system controller <NUM>. Although three elevator systems <NUM> are shown in <FIG>, it is understood that any number of elevator systems <NUM> may be utilized. Additional, although each elevator system <NUM> is illustrated as having one elevator car <NUM>, it is understood that any number of elevators cars <NUM> may be used each elevator system <NUM>. The elevator cars <NUM> of <FIG> may be referred to also as a first elevator car 103a, a second elevator car 103b, and a third elevator car 103c. It is understood that other components of the elevator system <NUM> (e.g., drive, counterweight, safeties, etc.) are not depicted for ease of illustration in <FIG>.

The system controller <NUM> may include a processor <NUM>, memory <NUM> and communication module <NUM>, as shown in <FIG>. The processor <NUM> can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory <NUM> is an example of a non-transitory computer readable storage medium tangibly embodied in the system controller <NUM> including executable instructions stored therein, for instance, as firmware. The communication module <NUM> may implement one or more communication protocols as described in further detail herein.

The system controller <NUM> may include and/or be in electronic communication with a passenger database <NUM>. The passenger database <NUM> may be local and/or remote to the system controller <NUM>. Although, only shown as a single database, the passenger database <NUM> may comprise multiple individual databases that are each either local or remote. The system controller <NUM> may be connected to the passenger database <NUM> through a cloud computing network or any other desired communication system. The passenger database <NUM> may container information regarding relationships among passengers that may take an elevator car <NUM> of the elevator call control system <NUM>. For example, the passenger database <NUM> may contain information indicating whether two or more passengers may desire to travel together within a single elevator car <NUM>. For example, the two passengers may be family, teammates, friends, coworkers, partners, or the passengers may have any other relationship status that may indicate that they would like to share an elevator car <NUM>. In one embodiment, the passenger database <NUM> is a meeting calendar/schedule that may know when one or more passengers intend to travel together to the same meeting or away from the same meeting. In one embodiment, the passenger database <NUM> is a social media network. In one embodiment, the passenger database <NUM> is a hotel visitor guest database or an employer database. For example, when checking in to a hotel or creating a hotel account, an individual may identify other individuals that they will be traveling with during their stay at the hotel. In another example, the passenger database <NUM> may also include employment information, such as, for example, where the passenger works, what group the passenger works in, what is the passenger's employment rank in the business. The passenger database <NUM> also may include the floors (i.e., landings) where potential passengers of the elevator car <NUM> may be staying in at hotel or floors where potential passengers will working on in an office building.

Also shown in <FIG> is a mobile device <NUM>. The mobile device <NUM> may be a mobile computing device that is typically carried by a person, such as, for example a smart phone, PDA, smart watch, tablet, laptop, etc. The mobile device <NUM> may include a touch screen (not shown). The mobile device <NUM> may include a processor <NUM>, memory <NUM> and communication module <NUM> as shown in <FIG>. The processor <NUM> can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory <NUM> is an example of a non-transitory computer readable storage medium tangibly embodied in the mobile device <NUM> including executable instructions stored therein, for instance, as firmware. The communication module <NUM> may implement one or more communication protocols as described in further detail herein. The mobile device <NUM> belongs to a resident or employee of the building <NUM> who currently has access to the elevator system <NUM>.

Each mobile device <NUM> may transmit an elevator call <NUM> to the system controller <NUM> and the system controller <NUM> will move an elevator car <NUM> in response to the elevator call <NUM>. The elevator call <NUM> may also be transmitted from an elevator call fixture <NUM>. The elevator call fixture <NUM> may be located in an elevator lobby proximate the elevator system <NUM>. The elevator call fixture <NUM> may be stationary. Multiple different individuals may submit an elevator call <NUM> via the elevator call fixture <NUM>.

The elevator call <NUM> may include a "boarding floor" and a "destination floor. " The "boarding floor" is where the person with the mobile device <NUM> desires to board the elevator car <NUM> and the "destination floor" is where the person with the mobile device <NUM> intends to travel. In one embodiment, the elevator call <NUM> may only include the "destination floor" and the "boarding floor" may be automatically determined by the elevator system <NUM>. Embodiments herein generate a graphical user interface on the mobile device <NUM> through an application <NUM>. The mobile device <NUM> may transmit an elevator call <NUM> through an application <NUM>.

The mobile device <NUM> and the system controller <NUM> communicate with one another. For example, the mobile device <NUM> and the system controller <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The mobile device <NUM> and the system controller <NUM> may communicate over a wireless network, such as <NUM>. 11x (Wi-Fi), short-range radio (Bluetooth), cellular, satellite, etc. In some embodiments, the system controller <NUM> may include, or be associated with (e.g., communicatively coupled to) a networked element, such as kiosk, beacon, hall call fixture, lantern, bridge, router, network node, door lock, elevator control panel, building intercom system, etc. The networked element may communicate with the mobile device <NUM> using one or more communication protocols or standards. For example, the networked element may communicate with the mobile device <NUM> using near field communications (NFC). A connection between the mobile device <NUM> and the system controller <NUM> may be direct between mobile device <NUM> and system controller <NUM> or it may be through a web service. The connection also may include security elements such as VPN or authentication or encryption. The system controller <NUM> establishes connection with a mobile device <NUM> that is inside and/or outside of the building <NUM> in order to detect a location of the mobile device <NUM>. A location of the mobile device may be determined using various technologies including GPS, triangulation, trilateration, signal strength detection, accelerometer detection, gyroscopic detection, or barometric pressure sensing by way of non-limiting example. The triangulation and trilateration may use various wireless technologies including but not limited to Wi-Fi and Bluetooth. In example embodiments, the mobile device <NUM> communicates with the system controller <NUM> over multiple independent wired and/or wireless networks. Embodiments are intended to cover a wide variety of types of communication between the mobile device <NUM> and system controller <NUM>, and embodiments are not limited to the examples provided in this disclosure. Communication between the mobile device <NUM> and the system controller <NUM> will allow the system controller <NUM> to determine the location of the mobile device <NUM> in relation to the elevator system <NUM>. The location of the mobile device <NUM> is communicated to the system controller <NUM> through a plurality of sensors <NUM>, discussed further below.

Each elevator system <NUM> may also include a sensor <NUM> configured to detect whether a mobile device <NUM> has entered the elevator car <NUM>. In an embodiment, the sensor <NUM> may be located on the elevator car <NUM>. The system controller <NUM> is in electronic communication with each sensor <NUM> through a wired connection and/or wireless connection. In an alternative embodiment, each sensor may be in indirect communication with the system controller <NUM> through the mobile device <NUM>. In a non-limiting example, if the sensors <NUM> are a Bluetooth beacon, then the mobile device <NUM> can detect when it is in proximity of the sensor <NUM>, then the mobile device <NUM> can communicate with the system controller <NUM> that it is in the elevator car <NUM>.

Further, although only one sensor <NUM> is shown per elevator car <NUM> for ease of illustration it is understood that each elevator car <NUM> may contain one or more sensors <NUM>. Each sensor <NUM> may also be configured to detect operational data of the elevator car <NUM>, such as for example, elevator door position (e.g. open/closed), elevator car location, speed, voltage, vibration, acceleration, noise, deceleration, jerk, and any other performance parameter of any component of the elevator system <NUM> known to one of skill in the art.

The sensors <NUM> detect the presence of an individual in an elevator car <NUM> and identify the individual using various sensing technology, such as, for example Wi-Fi transceivers, Bluetooth transceivers, radio transceivers, visual recognition cameras, people counters, microphones, etc. to detect persons and/or mobile devices entering and leaving the elevator car. The type and nature of sensors <NUM> within the sensor system <NUM> is not limited to the embodiments disclosed herein. The mobile device <NUM> and the sensors <NUM> communicate with one another. For example, the mobile device <NUM> and the sensors <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The mobile device <NUM> and the sensors <NUM> may communicate over a wireless network, such as <NUM>. 11x (Wi-Fi), ZigBee, Z-Wave and short-range radio (Bluetooth).

In an embodiment, the sensors <NUM> may include a Wi-Fi transceiver to connect to a mobile device <NUM> when the mobile device <NUM> enters the elevator car <NUM> in order to identify the mobile device <NUM>. In another embodiment, the sensors <NUM> may include a Bluetooth transceiver to connect to a mobile device <NUM> when the mobile device <NUM> enters the elevator car <NUM> in order to identify the mobile device <NUM>. The sensors <NUM> are configured to detect a distance between the elevator car <NUM> and the mobile device <NUM> to determine whether the mobile device <NUM> is entering and/or leaving the elevator car <NUM>. The sensors <NUM> may be configured to detect a distance between the elevator car <NUM> and the mobile device <NUM> through wireless signal strength detection.

Communication between the mobile device <NUM> and the sensors <NUM> can be one-way or two-way communication. In one example, if Bluetooth is utilized then the mobile device <NUM> may advertise a Bluetooth signal and the sensors <NUM> may receive it. In another example, the sensors <NUM> may advertise a Bluetooth signal and the mobile device <NUM> may receive it. In another example, there may be two-way Bluetooth communication between the sensors <NUM> and the mobile device <NUM>. In another example, a Wi-Fi transceiver (i.e. sensor <NUM>) may be placed in an elevator car and the mobile device may detect the Wi-Fi beacon frame as part of the <NUM>. 11x protocol as well as the received signal strength of that beacon frame to approximate the distance between the Wi-Fi transceiver and the mobile device <NUM> but not connect to the Wi-Fi signal. In another example, the mobile device <NUM> may actively send a probe request looking for Wi-Fi transceivers, then a Wi-Fi transceiver (i.e. sensor <NUM>) located in an elevator car may extract the MAC address of the mobile device <NUM> from the probe request and approximate distance between the Wi-Fi transceiver and the mobile device <NUM> from received signal strength.

In another embodiment, the mobile device <NUM> and the sensors <NUM> may communicate over a non-radio frequency network. In an example the mobile device <NUM> and the sensors <NUM> may communicate through audio transmission, such as, for example a high frequency audio transmission. The mobile device <NUM> may emit a chirp signature between <NUM>-<NUM> that one or more microphones (i.e. sensor <NUM>) can detect and extract a signature to determine which mobile device <NUM> is present. In this example, Audio gain at speaker may be measured to a distance between the microphone and the mobile device <NUM> may be determined in response to the audio gain. Advantageously, more microphones may help better determine distance. Alternatively, the speakers (i.e. sensors <NUM>) may be located in the elevators car <NUM> and may emit the high frequency audit for the mobile device <NUM> to detect. Advantageously, one or more speakers may be help better determine distance.

The elevator call control system <NUM> may also include an indoor positioning system <NUM> comprising one or more building sensors <NUM> in electronic communication with the system controller <NUM>. In an embodiment, the indoor positioning system <NUM> may be configured to determine how many individuals carrying mobile devices <NUM> are waiting for an elevator car <NUM> in an elevator lobby. For example, a single individual may have submitted an elevator call <NUM> but five individuals are planning on boarding the elevator car <NUM> when it arrives to pick up the individuals, which is a process known as piggy backing because the five individuals will be "piggy backing" on the elevator call <NUM> submitted by the single individual.

The building sensors <NUM> may be located throughout the building <NUM>. The building sensors <NUM> may be located proximate an elevator shaft <NUM> of each elevator system <NUM>. Each building sensor <NUM> may be configured to emit and/or detect a wireless signal. The building sensor <NUM> may be configured to emit a wireless signal that may be detected by the mobile device <NUM>. The building sensor <NUM> may be able to detect a wireless signal emitted by mobile device <NUM>. In an embodiment, a building sensor <NUM> may be a door lock that controls access to a room within the building <NUM>. In an embodiment, a building sensor <NUM> may be a wireless access protocol device that provides Wi-Fi access to computing devices throughout the building <NUM>.

The building sensors <NUM> may detect the location of the mobile device <NUM> within a building <NUM> using various sensing technology, such as, for example Wi-Fi transceivers, Bluetooth transceivers, radio transceivers, etc. to detect the presence of mobile devices <NUM> within the building <NUM>. The type and nature of building sensors <NUM> within the sensor system <NUM> is not limited to the embodiments disclosed herein. The mobile device <NUM> and the building sensors <NUM> communicate with one another. For example, the mobile device <NUM> and the building sensors <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The mobile device <NUM> and the building sensors <NUM> may communicate over a wireless network, such as <NUM>. 11x (Wi-Fi), ZigBee, Z-Wave and short-range radio (Bluetooth).

In an embodiment, the building sensors <NUM> may include a Wi-Fi transceiver to connect to a mobile device <NUM> when the mobile device <NUM> is located within a threshold distance in order to determine the location of the mobile device <NUM>. In another embodiment, the building sensors <NUM> may include a Bluetooth transceiver to connect to a mobile device <NUM> when the mobile device <NUM> is located within a threshold distance in order to determine the location of the mobile device <NUM>. The building sensors <NUM> may be configured to detect a distance between each of the building sensor <NUM> and the mobile device <NUM> through wireless signal strength detection. The wireless signal strength detected between the mobile device <NUM> and a single building sensor <NUM> may be enough to approximate a location of the mobile device <NUM> or the indoor positioning system <NUM> may utilize three or more building sensors <NUM> to triangulate the position of the mobile device <NUM> utilizing the wireless signal strength detected between the mobile device <NUM> and each of the three building sensors <NUM>.

Communication between the mobile device <NUM> and the building sensors <NUM> can be one-way or two-way communication. In one example, if Bluetooth is utilized then the mobile device <NUM> may advertise a Bluetooth signal and the building sensors <NUM> may receive it. In another example, the building sensors <NUM> may advertise a Bluetooth signal and the mobile device <NUM> may receive it. In another example, there may be two-way Bluetooth communication between the building sensors <NUM> and the mobile device <NUM>. In another example, a the building sensor <NUM> may be a Wi-Fi transceiver (i.e., a wireless access protocol device) and the mobile device <NUM> may detect the Wi-Fi beacon frame as part of the <NUM>. 11x protocol as well as the received signal strength of that beacon frame to approximate the distance between the Wi-Fi transceiver and the mobile device <NUM> but not connect to the Wi-Fi signal. In another example, the mobile device <NUM> may actively send a probe request looking for Wi-Fi transceivers, then a Wi-Fi transceiver (i.e. building sensor <NUM>) may extract the MAC address of the mobile device <NUM> from the probe request and approximate distance between the Wi-Fi transceiver and the mobile device <NUM> from received signal strength.

In one embodiment, the mobile device <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM> and transmit that distance to the system controller <NUM> to determine the location of the mobile device <NUM>. In another embodiment, the indoor positioning system <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM> and transmit that distance to the system controller <NUM> to determine the location of the mobile device <NUM>. The location of the mobile device <NUM> may be determined by the mobile device <NUM> or by the indoor positioning system <NUM>. In one embodiment, the mobile device <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM>, then the mobile device <NUM> may use that distance to determine the location of the mobile device <NUM> to transmit to the system controller <NUM>. In another embodiment, the indoor positioning system <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM>, then the indoor positioning system <NUM> may use that distance to determine the location of the mobile device <NUM> to transmit to the system controller <NUM>.

Referring now to <FIG> with continued reference to <FIG>. <FIG> shows a flow chart of a method <NUM> of operating an elevator call control system <NUM>. The method <NUM> may be performed by system controller <NUM>. <FIG> illustrates a mobile device <NUM> graphical user interface <NUM> for operating the application <NUM>. <FIG> illustrates a graphical representation of the method <NUM>. The mobile device <NUM> may be a laptop computer, smart phone, tablet computer, smart watch, or any other mobile computing device known to one of skill in the art. In the example shown in <FIG>, the mobile device <NUM> is a touchscreen smart phone. The mobile device <NUM> may include a display screen <NUM> and an input device <NUM>, such as, example, a mouse, a touch screen, a scroll wheel, a scroll ball, a stylus pen, a microphone, a camera, etc. In the example shown in <FIG>, since the mobile device <NUM> is a touchscreen smart phone, then the display screen <NUM> may also function as an input device <NUM>. <FIG> illustrates a graphical user interface <NUM> on the mobile device <NUM>. A user may interact with the graphical user interface <NUM> through a selection input, such as, for example, a "click", "touch", verbal command or any other input to the user interface <NUM>.

A first individual 402a making an elevator call <NUM> may identify one or more other individuals traveling with the first individual 402a using the user interface <NUM> of the application <NUM>. Alternatively, the application <NUM> may automatically identify and prepopulate the one or more other individuals traveling with the first individual 402a using the passenger database <NUM> and/or location determination of mobile devices <NUM> belonging to the one or more other individuals then display the one or more individuals on the display screen <NUM>, as seen in <FIG> at <NUM>. Once the first individual 402a and the one or more other individuals are displayed on the display screen <NUM>, the first individual 402a may adjust the one or more other individuals through the graphical user interface <NUM> of the application <NUM>.

Additionally, the first individual 402a making an elevator call <NUM> may identify the boarding floor and destination floor of the first individual 402a and the one or more other individuals traveling with the first individual 402a using the user interface <NUM> of the application <NUM>. Alternatively, the application <NUM> may automatically identify and prepopulate the boarding floor and destination floor of the first individual and the one or more other individuals traveling with the first individual 402a using the passenger database <NUM> and/or location determination of mobile devices <NUM> belonging to the one or more other individuals then display the boarding floors and destination floors are displayed on the display screen <NUM>, as seen in <FIG> at <NUM>. Once the boarding floors and destination floors are displayed on the display screen <NUM>, the first individual 402a may adjust the one or more other individuals through the graphical user interface <NUM> of the application <NUM>.

The application <NUM> may also be configured to display short cut buttons <NUM> through the user interface <NUM> on the display screen <NUM>, as shown at <NUM> in <FIG>. For instance, the short cut buttons <NUM> may include short cuts such as, for example, "RETURN ALL PASSENGERS TRAVELING TOGETHER TO HOTEL ROOM" AND "TRANSPORT ALL PASSENGERS TRAVELING TOGETHER TO HOTEL LOBBY". An individual may select one of the shortcut buttons <NUM> to automatically generate an elevator call <NUM> so that all the passengers identified as travelling together in the passenger database <NUM> may travel within the same elevator car <NUM>.

At block <NUM>, a first elevator call 302a is received from a first individual 402a carrying a first mobile device 208a. The first elevator call 302a includes a destination request to travel from a first boarding floor 125a to a first destination floor. The first mobile device 208a may be determined to be located on the first boarding floor 125a by receiving a selection input from the first mobile device 208a and/or detecting a location of the first mobile device 208a. The location of the first mobile device 208a may be detected utilizing the building sensors <NUM>, the sensor <NUM> of an elevator car <NUM>, and/or a second mobile device 208b. In one example, the location of the first mobile device 208a may be determined by: connecting, using a building sensor <NUM>, to the first mobile device 208a via at least one of Wi-Fi and Bluetooth; and determining a distance between the building sensor <NUM> and the first mobile device 208a. In another example, the location of the first mobile device 208a may be determined by: detecting, using a building sensor <NUM>, a wireless signal of the first mobile device 208a, wherein the building sensor <NUM> does not connect to the wireless signal; and determining a distance between the building sensor <NUM> and the first mobile device 208a. In yet another example, the location of the first mobile device 208a may be determined by: detecting a beacon transmitted by a building sensor <NUM> using the first mobile device 208a; and determining a distance between the building sensor <NUM> and the first mobile device 208a in response to a strength of the beacon.

At block <NUM>, it is determined that the first individual 402a carrying the first mobile device 208a is traveling with a second individual 402b. Determining that the first individual 402a carrying the first mobile device 208a is traveling with a second individual 402b comprises: detecting a location of a second mobile device 208b carried by the second individual 402b; detecting a location of the first mobile device 208a; and determining that the second mobile device 208b is within a selected range R1 of the first mobile device 208a. The second mobile device 208b may be determined to be within a selected range R1 of the first mobile device 208a when the first elevator call 302a is received and/or when the elevator car <NUM> arrives at the first boarding floor 125a. It may also be determined that the first individual 402a carrying the first mobile device 208a is traveling with a second individual 402b by: quarrying at least one of a social media network and a hotel visitor guest database to determine whether the second individual 402b is traveling with the first individual 402a.

At block <NUM>, an elevator car <NUM> is assigned to the first elevator call 302a. At block <NUM>, the elevator car <NUM> is scheduled to transport the first individual 402a carrying the first mobile device 208a and the second individual 402b together to at least one of a first destination floor and a second destination floor. In an embodiment, the first destination floor is the second destination floor (e.g., the first destination floor and the second destination floor are a hotel lobby, a ground floor, gym floor, pool floor, or conference room floor). In the example shown in <FIG>, the first destination floor and the second destination floor are a ground floor 125c.

The elevator car <NUM> may be scheduled to pick up the first individual 402a and the second individual 402b on the same floor or scheduled to pick up the first individual 402a and the second individual 402b on different floors, such that the first individual 402a and the second individual 402b travel together within the elevator car <NUM> at some point between their origin and destinations. Further, The elevator car <NUM> may be scheduled to transport the first individual 402a and the second individual 402b to the same floor or scheduled to transport the first individual 402a and the second individual 402b to different floors, such that the first individual 402a and the second individual 402b travel together within the elevator car <NUM> at some point between their origin and destinations.

The method <NUM> may further comprise: determining that the second individual 402b is located on a second boarding floor 125b. The second boarding floor 125b may be different than the first boarding floor 125a as shown in <FIG>. Alternatively, the second boarding floor may also be the same as the first boarding floor (not shown), the first individual 402a and the second individual 402b may board the elevator car on the same boarding floor. It is determined that the second individual 402b is located on a second boarding floor 125b different than the first boarding floor 125a by: detecting a location of a second mobile device 208b carried by the second individual 402b.

The location of the second mobile device 208b may be detected utilizing the building sensors <NUM>, the sensor <NUM> of an elevator car <NUM>, and/or the first mobile device 208a. In one example, the location of the second mobile device 208b may be determined by: connecting, using a building sensor <NUM>, to the second mobile device 208b via at least one of Wi-Fi and Bluetooth; and determining a distance between the building sensor <NUM> and the second mobile device 208b. In another example, the location of the second mobile device 208b may be determined by: detecting, using a building sensor <NUM>, a wireless signal of the second mobile device 208b, wherein the building sensor <NUM> does not connect to the wireless signal; and determining a distance between the building sensor <NUM> and the second mobile device 208b. In yet another example, the location of the second mobile device 208b may be determined by: detecting a beacon transmitted by a building sensor <NUM> using the second mobile device 208b; and determining a distance between the building sensor <NUM> and the second mobile device 208b in response to a strength of the beacon.

Claim 1:
A method of operating an elevator call control system (<NUM>), the method comprising:
receiving a first elevator call from a first individual (402a) carrying a first mobile device (208a), the first elevator call (302a) including a destination request to travel from a first boarding floor (125a) to a first destination floor (125c);
determining that the first individual (402a) carrying the first mobile device (208a) is traveling with a second individual (402b), wherein the second individual (402b) is traveling to a second destination floor (125c);
assigning an elevator car (<NUM>) to the first elevator call (302a); and
scheduling the elevator car (<NUM>) to transport the first individual (402a) carrying the first mobile device (208a) and the second individual (402b) together to at least one of a first destination floor (125c) and the second destination floor (125c);
and characterized in that the determining further comprises:
detecting a location of a second mobile device (208b) carried by the second individual (402b);
detecting a location of the first mobile device (208a); and
determining that the second mobile device (208b) is within a selected range (R1) of the first mobile device (<NUM>).