Patent Description:
Elevator systems may generally preset a load capacity setting for elevator cars, which defines a maximum load that each elevator car may receive. The load capacity setting may be preset by a manufacturer of the elevator system or a user of the elevator system. In such systems, an elevator car having a current load that exceeds the preset load capacity may be ignored from consideration for calls from prospective passengers. However, prospective passengers may commonly forgot entering an elevator car that has a current load below the present load capacity for various reasons. For example, prospective passengers may prefer to enter elevator cars having a certain number of occupants that is less than the load capacity of the elevator car. As a result, an elevator car having a current load below the preset load capacity may be dispatched to a location of a prospective passenger but not occupied by the prospective passenger, thereby resulting in decreased traffic flow and greater wait times for prospective passengers who request another elevator car to be dispatched. Providing a system capable of dynamically adjusting a load capacity setting may result in dispatching elevator cars with a greater likelihood of receiving passengers, thereby increasing traffic flow and decreasing wait times for prospective passengers. <CIT> discloses an automated arrangement that selects one of a plurality of load weight bypass thresholds for an elevator car. The selection depends, for example, upon the car direction and the time of day. Alternative embodiments of the arrangement utilize in the selection either actual or estimated elevator car floor space. Fuzzy logic is used to estimate available floor space.

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various exemplary embodiments and together with the description, serve to explain the principles of the disclosure.

Aspects of the disclosure may be implemented in connection with embodiments illustrated in the attached drawings. These drawings show different aspects of the present disclosure and, where appropriate, reference numerals illustrating like structures, components, materials and/or elements in different figures are labeled similarly.

According to an example, a method of adjusting a load setting of an elevator car includes receiving one or more load measurements associated with the elevator car and determining a maximum load of the elevator car from the one or more load measurements. The method further includes generating a modified load setting for the elevator car based on the maximum load and replacing the load setting of the elevator car with the modified load setting for a predefined period.

According to another example, a method of operating a plurality of elevator cars includes measuring a load of each of the plurality of elevator cars during a predefined period and determining a maximum load of each of the plurality of elevator cars from the load measurements. The method further includes generating a modified load setting for each of the plurality of elevator cars based on the respective maximum load of each of the plurality of elevator cars, and applying the modified load setting of each of the plurality of elevator cars in place of a load setting during the predefined period. The modified load setting defines an adjusted capacity of each of the plurality of elevator cars relative to the load setting.

According to a further example, a method for positioning an elevator car includes determining an occupancy of each of a plurality of locations by determining a first load measurement of the elevator car upon arriving at each of the plurality of locations, determining a second load measurement of the elevator car upon departing from each of the plurality of locations, and determining a difference between the first load measurement and the second load measurement. The method further includes moving the elevator car to a first location with a total occupancy that is greater than the occupancy at each respective location of the plurality of locations when the elevator car is in an inactive state.

The dispatch system of the present disclosure may be in the form of varying embodiments, some of which are depicted by the figures and further described below.

Both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the features, as claimed. As used herein, the terms "comprises," "comprising," or other variations thereof, are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such a process, method, article, or apparatus. Additionally, the term "exemplary" is used herein in the sense of "example," rather than "ideal. " It should be noted that all numeric values disclosed or claimed herein (including all disclosed values, limits, and ranges) may have a variation of +/- <NUM>% (unless a different variation is specified) from the disclosed numeric value. Moreover, in the claims, values, limits, and/or ranges mean the value, limit, and/or range +/-<NUM>%.

<FIG> shows an exemplary dispatch system <NUM> that may include motion controller <NUM>, call device <NUM>, input device <NUM>, sensing device <NUM>, and dispatch controller <NUM>. The one or more devices of dispatch system <NUM> may communicate with one another across a network <NUM> and in any arrangement. For example, the devices of dispatch system <NUM> may be communicatively coupled to one another via a wired connection, a wireless connection, or the like. In some embodiments, network <NUM> may be a wide area network ("WAN"), a local area network ("LAN"), personal area network ("PAN"), etc. Network <NUM> may further include the Internet such that information and/or data provided between the devices of dispatch system <NUM> may occur online (e.g., from a location remote from other devices or networks coupled to the Internet). In other embodiments, network <NUM> may utilize Bluetooth® technology and/or radio waves frequencies.

Motion controller <NUM> may be operably coupled to a transportation unit and configured to detect and transmit motion data of the transportation unit to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. For example, motion controller <NUM> may measure and record one or more parameters (e.g., motion data) of the transportation unit, including, but not limited to, a current location, a travel direction, a travel speed, a door location, a status (e.g., active, inactive, moving, parked, idle, etc.), and more. Motion controller <NUM> may include a computing device having one or more hardware components (e.g., a processor, a memory, a sensor, a communications module, etc.) for generating, storing, and transmitting the motion data. As described in further detail herein, motion controller <NUM> may be operably coupled to an elevator car located within a building, and dispatch system <NUM> may include at least one motion controller <NUM> for each elevator car.

Still referring to <FIG>, call device <NUM> may be positioned outside the transportation unit and configured to receive a user input from one or more prospective occupants for accessing the transportation unit. For example, the user input may be indicative of a call requesting transportation from the transportation unit. Call device <NUM> may be configured to transmit the call request to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. Call device <NUM> may include a keypad, a touchscreen display, a microphone, a button, a switch, etc. Call device <NUM> may be further configured to receive a user input indicative of a current location of the call request (e.g., a first location) and/or a destination location (e.g., a second location) from a plurality of locations.

As described in further detail herein, call device <NUM> may be located within a building, and dispatch system <NUM> may include at least one call device <NUM> for each floor of the building. Call device <NUM> may be configured to transmit a message from one or more devices of dispatch system <NUM> (e.g., dispatch controller <NUM>) identifying an elevator car designated to arrive at the floor of the building to answer the call request. The message may be communicated by call device <NUM> via various suitable formats, including, for example, in a written form, an audible form, a graphic form, and more.

Input device <NUM> may be positioned inside the transportation unit and configured to receive a user input from one or more occupants of the transportation unit. For example, the user input may be indicative of a command requesting redirection of the transportation unit. Input device <NUM> may be configured to transmit the command to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. Input device <NUM> may include a keypad, a touchscreen display, a microphone, a button, a switch, etc. As described in detail herein, input device <NUM> may be located within an elevator car, and dispatch system <NUM> may include at least one input device <NUM> for each elevator car in a building. In other embodiments, input device <NUM> may be omitted entirely from dispatch system <NUM>.

Still referring to <FIG>, sensing device <NUM> may be positioned inside or outside the transportation unit, and configured to detect and transmit sensor data associated with the transportation unit to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. For example, sensing device <NUM> may measure and record a current load of the transportation unit, including, but not limited to, a weight measurement, a voltage direct current, and more. Sensing device <NUM> may include a load weighing device, such as, for example, a crosshead deflection device, a rope tension device, a platform movement device, a load sensor or cell (e.g., force transducer), etc. As described in further detail herein, sensing device <NUM> may be coupled to an elevator car that is located within a building, and dispatch system <NUM> may include at least one sensing device <NUM> for each elevator car of the building.

Dispatch controller <NUM> may be positioned outside the transportation unit and configured to receive data (e.g., motion data, a call request, a redirection command, sensor data, etc.) from one or more devices of dispatch system <NUM>. Dispatch controller <NUM> may be configured to determine at least one transportation unit of a plurality of transportation units to dispatch to a location of a call request received from a prospective occupant seeking transportation. Dispatch controller <NUM> may be further configured to determine a current load of a transportation unit based on the data received from the one or more devices of dispatch system <NUM>. Dispatch controller <NUM> may include a computing device (see <FIG>) operable to perform one or more processes (see <FIG>) for dynamically adjusting a load setting of transportation units and rendering said transportation units inoperable to receive a call request when a current load exceeds the load setting. Dispatch controller <NUM> may be further operable to perform one or more processes (see <FIG>) for moving transportation units in an inactive state to a location with a total occupancy that is greater than an occupancy at a plurality of other locations. As described in further detail herein, dispatch controller <NUM> may be operably coupled to a plurality of elevator cars located within a building, and dispatch system <NUM> may include at least one dispatch controller <NUM> for each building.

Referring now to <FIG>, dispatch system <NUM> may be utilized in a working environment <NUM>, such as a building (e.g., a facility, a factory, a store, a school, a house, an office, and various other structures). In the example, the transportation unit may include one or more elevator cars within the building. It should be appreciated that working environment <NUM> is merely illustrative such that dispatch system <NUM> may be utilized in various other suitable environments than those shown and described herein without departing from a scope of this disclosure. For example, the working environment may include a mass transit system such that the transportation unit(s) may include a bus, a train, a subway car, a metro car, a vehicle, etc. In the present example, working environment <NUM> may include a plurality of floors defining a plurality of locations within the building, such as first floor 204A, second floor 204B, third floor 204C, and fourth floor 204D. It should be appreciated that, in other embodiments, the building of working environment <NUM> may include additional and/or fewer floors.

Working environment <NUM> may further include one or more elevator shafts with at least one elevator car positioned within each elevator shaft. In the example, working environment <NUM> includes a first elevator shaft <NUM> with at a first elevator car <NUM> and a second elevator shaft <NUM> with a second elevator car <NUM>. Although not shown, it should be appreciated that working environment <NUM> may include additional (e.g., a plurality) elevator shafts and/or elevator cars. Each elevator car <NUM>, <NUM> may be coupled to a pulley system <NUM> configured to move elevator cars <NUM>, <NUM> within elevator shafts <NUM>, <NUM> and relative to floors 204A- 204D. It should be understood that pulley system <NUM> may include various mechanical and/or electrical mechanisms for moving elevator cars <NUM>, <NUM> within elevator shafts <NUM>, <NUM>, including but not limited to, a motor, a cable, a counterweight, a sheave, etc..

Still referring to <FIG>, each elevator car <NUM>, <NUM> may include at least one motion controller <NUM> operably coupled to pulley system <NUM>, such as, for example, via a wireless connection and/or a wired connection <NUM>. Motion controller <NUM> may be configured to measure motion data (e.g., a status) from elevator cars <NUM>, <NUM> by detecting a relative movement of pulley system <NUM>. Each elevator car <NUM>, <NUM> may further include at least one input device <NUM> positioned within a cabin of elevator car <NUM>, <NUM> for receiving a user input from one or more occupants <NUM> located within the cabin.

Each floor 204A-204D may include one or more call devices <NUM> and access doors <NUM> providing accessibility to elevator cars <NUM>, <NUM> when an elevator door <NUM> of elevator car <NUM>, <NUM> is aligned with the respective floor 204A-204D. Call device <NUM> may be configured to receive a user input from one or more prospective occupants <NUM> located at one of the plurality of floors 204A-204D. For example, call device <NUM> may be configured to receive a user input indicative of a call requesting transportation via at least one of elevator cars <NUM>, <NUM>. Call device <NUM> may be configured to transmit the call request to dispatch controller <NUM>, which may include data indicative of a current location within working environment <NUM> from which the call request originated from. The call request may further include data indicative of a destination location within working environment <NUM> to which the prospective passenger is seeking transportation to.

Still referring to <FIG>, each elevator car <NUM>, <NUM> may further include at least one sensing device <NUM>. Sensing device <NUM> may be coupled to elevator car <NUM>, <NUM> and configured to detect a load (e.g., weight) of elevator car <NUM>, <NUM>. With elevator car <NUM>, <NUM> including one or more occupants <NUM> within a cabin of elevator car <NUM>, <NUM>, sensing device <NUM> may be operable to correlate the detected load measurement to a number of occupants <NUM> within elevator car <NUM>, <NUM>. In some embodiments, sensing device <NUM> may be positioned on elevator car <NUM>, <NUM> (e.g., within the cabin). In other embodiments, sensing device <NUM> may be positioned external to elevator car <NUM>, <NUM> and coupled to pulley system <NUM>. For example, sensing device <NUM> may include one or more connections <NUM> coupled to one or more components of pulley system <NUM> (e.g., a crosshead, a beam, a hitch, a rope, a platform, etc.).

As seen in <FIG>, sensing device <NUM> may be configured to measure a total load of elevator cars <NUM>, <NUM>, including any items present within the cabin, and occupying a capacity, of elevator cars <NUM>, <NUM> (e.g., occupants <NUM>, ancillary objects <NUM>, etc.). In some embodiments, sensing device <NUM> may detect a total load of elevator cars <NUM>, <NUM>, including a weight of elevator car <NUM>, <NUM> and the one or more components of elevator car <NUM>, <NUM> (e.g., rails <NUM>, input device <NUM>, doors <NUM>, etc.). In other embodiments, sensing device <NUM> may detect a current load of elevator cars <NUM>, <NUM> in exclusion of any items within the cabin that may not occupy a capacity of elevator cars <NUM>, <NUM> (e.g., rails <NUM>, input device <NUM>, doors <NUM>, etc.). Sensing device <NUM> may detect one or more load measurements of elevator cars <NUM>, <NUM> and record such measurements as sensor data. As discussed further herein, sensing device <NUM> may be configured to transmit the sensor data for each elevator car <NUM>, <NUM> to dispatch controller <NUM> via network <NUM> for determining an availability of the elevator car <NUM>, <NUM> to receive prospective passengers <NUM> from one or more floors 204A-204D.

Referring now to <FIG>, dispatch controller <NUM> may include a computing device incorporating a plurality of hardware components that allow dispatch controller <NUM> to receive data (e.g., motion data, call requests, commands, sensor data, etc.), process information (e.g., current load measurements, load settings, etc.), and/or execute one or more processes (see <FIG>). Illustrative hardware components of dispatch controller <NUM> may include at least one processor <NUM>, at least one communications module <NUM>, a user interface <NUM>, and at least one memory <NUM>. In some embodiments, dispatch controller <NUM> may include a computer, a mobile user device, a remote station, a server, a cloud storage, and the like. In the illustrated embodiment, dispatch controller <NUM> is shown and described herein as a separate device from the other devices of dispatch system <NUM>, while in other embodiments, one or more aspects of dispatch controller <NUM> may be integrated with one or more of the other devices of dispatch system <NUM>. Stated differently, the illustrative hardware components of dispatch controller <NUM> shown and described herein may be integral with one or more of motion controller <NUM>, call device <NUM>, input device <NUM>, and/or sensing device <NUM>.

Processor <NUM> may include any computing device capable of executing machine-readable instructions, which may be stored on a non-transitory computer-readable medium, such as, for example, memory <NUM>. By way of example, processor <NUM> may include a controller, an integrated circuit, a microchip, a computer, and/or any other computer processing unit operable to perform calculations and logic operations required to execute a program. As described in detail herein, processor <NUM> is configured to perform one or more operations in accordance with the instructions stored on memory <NUM>, such as, for example, dispatch logic <NUM>, zoning logic <NUM>, and the like. Communications module <NUM> may facilitate communication between dispatch controller <NUM> and the one or more other devices of dispatch system <NUM>, such as, for example, via network <NUM>. User interface <NUM> may include one or more input and output devices, including one or more input ports and one or more output ports. User interface <NUM> may include, for example, a keyboard, a mouse, a touchscreen, etc., as input ports. User interface <NUM> may further include, for example, a monitor, a display, a printer, etc. as output ports. User interface <NUM> may be configured to receive a user input indicative of various commands, including, but not limited to, a command to execute one or more processes (<FIG>), a command defining a predefined period, a command to apply an automatic adjustment of a load setting, and more.

Still referring to <FIG>, memory <NUM> may include various programming algorithms and data that support an operation of dispatch system <NUM>. Memory <NUM> may include any type of computer readable medium suitable for storing data and algorithms, such as, for example, random access memory (RAM), read only memory (ROM), a flash memory, a hard drive, and/or any device capable of storing machine-readable instructions. Memory <NUM> may include one or more data sets, including, but not limited to, motion data received from motion controller <NUM>, a load setting <NUM> for each of the plurality of elevator cars <NUM>, <NUM>, sensor data <NUM> captured from each sensing device <NUM>, a modified load setting <NUM> for each of the plurality of elevator cars <NUM>, <NUM>, local load data <NUM>, and the like.

Load settings <NUM> may include data indicative of a preset maximum load capacity for each of the plurality of elevator cars <NUM>, <NUM>. That is, load settings <NUM> may define a maximum weight that each elevator car <NUM>, <NUM> may receive during use. It should be appreciated that the load settings <NUM> for each of the plurality of elevator cars <NUM>, <NUM> may be the same, or vary, relative to one another. Load settings <NUM> may be predefined by, for example, a user of dispatch system <NUM> (e.g., via user interface <NUM>). In some embodiments, load settings <NUM> may be modified by the user. Sensor data <NUM> may include a real-time load measurement of each elevator car <NUM>, <NUM>, indicative of a number of occupants <NUM> (and/or ancillary objects <NUM>) located within a cabin of elevator cars <NUM>, <NUM>. In some embodiments, the sensor data <NUM> stored in memory <NUM> may include a maximum load measurement of a respective elevator car <NUM>, <NUM> detected by sensing device <NUM>. As described in detail herein, modified load settings <NUM> may include an updated load setting (e.g., maximum load capacity) for each of the plurality of elevator cars <NUM>, <NUM> based on data received from the one or more devices of dispatch system <NUM> (e.g., sensing device <NUM>). Dispatch controller <NUM> may be configured to dynamically generate the modified load settings <NUM> based on one or more load measurements received from sensing devices <NUM> of elevator cars <NUM>, <NUM>.

Still referring to <FIG>, the modified load settings <NUM> may further include a predefined period during which the modified load settings <NUM> may be applied by dispatch controller <NUM>. Dispatch controller <NUM> may be configured to replace the load settings <NUM> with the modified load settings <NUM> during the predefined period. In some embodiments, dispatch controller <NUM> may be configured to autonomously determine the predefined period, while in other embodiments a user of dispatch system <NUM> may manually select the predefined period (e.g., via user interface <NUM>).

Local load data <NUM> may include a load balance measurement at each of the plurality of locations within working environment <NUM>, and may be indicative of a number of occupants <NUM> located at each of the plurality of floors 204A-204D. Dispatch controller <NUM> may be configured to compute the local load data <NUM>, which may correspond to a load of items (e.g., occupants <NUM>, ancillary objects <NUM>, etc.) transported to and from each of the plurality of floors 204A-204D by at least one of the plurality of elevator cars <NUM>, <NUM>. Dispatch controller <NUM> may be further configured to store the local load data <NUM> in memory <NUM> and associate the load with a number of occupants located at a particular location within working environment <NUM> (e.g., floors 204A-204D). For example, dispatch controller <NUM> may receive and correlate the motion data received from motion controller <NUM> with the sensor data <NUM> received from sensing device <NUM> to determine the local load data <NUM>.

In some embodiments, dispatch controller <NUM> may be configured to periodically (e.g., hourly, daily, weekly, monthly, yearly, etc.) update the modified load settings <NUM> for each of the plurality of elevator cars <NUM>, <NUM> based on receiving additional load measurements (e.g., sensor data <NUM>) from sensing devices <NUM>. In further embodiments, dispatch controller <NUM> may be further configured to periodically update the local load data <NUM> upon determining one or more elevator cars <NUM>, <NUM> have traveled to and/or from floors 204A-204D to transport at least one occupant <NUM>. That is, dispatch controller <NUM> may continuously modify the local load data <NUM> to include a current load balance measurement at each floor 204A-204D based on determining a number of occupants <NUM> arriving to, or leaving from, each floor 204A-204D (e.g., as detected by sensing device <NUM>).

Still referring to <FIG>, memory <NUM> may include a non-transitory computer readable medium that stores machine-readable instructions thereon, such as, dispatch logic <NUM> and zoning logic <NUM>. In one example, dispatch logic <NUM> may include executable instructions that allow dispatch system <NUM> to determine an occupant capacity of each elevator car <NUM>, <NUM> based on a current load measurement of each elevator car <NUM>, <NUM> (e.g., sensor data <NUM>). As described in detail herein, dispatch system <NUM> may be configured to determine whether a current load of each elevator car <NUM>, <NUM> (indicative of a number of occupants present within the cabin) exceeds a maximum load capacity of the respective elevator car <NUM>, <NUM> (e.g., load setting <NUM>, modified load setting <NUM>). When the maximum load capacity of at least one elevator car <NUM>, <NUM> is exceeded, dispatch system <NUM> may render the particular elevator car inoperable to answer additional call requests from prospective occupants <NUM> seeking transportation. That is, dispatch system <NUM> disregards the elevator car from further consideration when determining which of the plurality of elevator cars <NUM>, <NUM> to dispatch to a new call request(s) until the current load of the elevator car no longer exceeds the maximum load capacity.

In another example, zoning logic <NUM> may include executable instructions that allow dispatch system <NUM> to determine when one or more of the plurality of elevator cars <NUM>, <NUM> is in an inactive state, and which location (e.g., a first location) to park elevator cars at while in the inactive state. The executable instructions of zoning logic <NUM> may further allow dispatch system <NUM> to determine an amount of load transferred by elevator cars <NUM>, <NUM> to a plurality of locations (e.g., floors 204A-204D) to identify a first location having a greater load balance than the remaining plurality of locations.

Referring now to <FIG>, an example method <NUM> of using dispatch system <NUM> to dynamically adjust a load setting of an elevator car, and to render the elevator car inoperable for receiving calls when a current load exceeds the load setting, is depicted. It should be understood that the steps shown and described herein, and the sequence in which they are presented, are merely illustrative such that additional and/or fewer steps may be included in various arrangements without departing from a scope of this disclosure.

At step <NUM>, dispatch system <NUM> may receive a call at a location of a plurality of locations within working environment <NUM>. The call may be initiated in response to a prospective occupant <NUM> actuating call device <NUM> at the location (e.g., a first location). Call device <NUM> may transmit the call to dispatch controller <NUM> via network <NUM>, and the call may include data indicative of the first location (e.g., fourth floor 204D) from which the call originated from. The call may further include data indicative of a destination (e.g., a second location) within working environment <NUM> to which the prospective occupant <NUM> seeks to travel, such as first floor 204A.

Dispatch controller <NUM>, in accordance with dispatch logic <NUM>, may retrieve motion data of each elevator car <NUM>, <NUM>, from a corresponding motion controller <NUM>, to determine movement parameters of elevator cars <NUM>, <NUM>. For example, dispatch controller <NUM> may receive data including a current location, a travel direction, a travel speed, etc., of each elevator car <NUM>, <NUM>. Dispatch controller <NUM> may further retrieve a load measurement (e.g., sensor data <NUM>) of each elevator car <NUM>, <NUM>, from a corresponding sensing device <NUM>, at step <NUM>. Dispatch controller <NUM> may be configured to determine a current load of each of elevator cars <NUM>, <NUM> based on the sensor data <NUM>.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may compare the current load measurement of each elevator car <NUM>, <NUM> to a respective load setting <NUM> to determine whether the current load exceeds a maximum load capacity (e.g., the load setting <NUM>) of the elevator car <NUM>, <NUM>. Load setting <NUM> may include various suitable capacities, including, but not limited to, a range of about <NUM>,<NUM> pounds to about <NUM>,<NUM> pounds. In the present example, the load setting <NUM> of first elevator car <NUM> may be about <NUM>,<NUM> pounds, and the lead setting <NUM> of second elevator car <NUM> may be about <NUM>,<NUM> pounds. Dispatch controller <NUM> may be configured to analyze the motion data and the sensor data <NUM> of the plurality of elevator cars <NUM>, <NUM> to determine which elevator car <NUM>, <NUM> to dispatch to the first location, at step <NUM>.

For example, in response to determining the current load does not exceed the load setting <NUM>, dispatch controller <NUM> may be configured to render the elevator car <NUM>, <NUM> operable to receive the call. That is, dispatch controller <NUM> may determine the elevator car <NUM>, <NUM> is available for consideration when determining which of the plurality of elevator cars <NUM>, <NUM> to dispatch to the call request. In response to determining the current load exceeds the load setting <NUM>, dispatch controller <NUM> may be configured to render the elevator car <NUM>, <NUM> inoperable to receive the call. In this instance, dispatch controller <NUM> may determine the elevator car <NUM>, <NUM> is unavailable such that the elevator car <NUM>, <NUM> is omitted from consideration when determining which of the plurality of elevator cars <NUM>, <NUM> to dispatch to the call.

In the present example, first elevator car <NUM> may include a current load of about <NUM> pounds and second elevator car <NUM> may include a current load of about <NUM> pounds. Additionally, first elevator car <NUM> may be positioned further from the first location (e.g., fourth floor 204D) than second elevator car <NUM> when the call is received at step <NUM>. Accordingly, second elevator car <NUM> may be determined as an optimal elevator car from the plurality of elevator cars <NUM>, <NUM> to dispatch to fourth floor 204D. In some embodiments, dispatch controller <NUM> may be configured to communicate with call device <NUM> to transmit a message to the prospective occupant <NUM> at the first location. For example, dispatch controller <NUM> may communicate an identification of the second elevator car <NUM> assigned to answer the call. In other embodiments, dispatch controller <NUM> may identify second elevator shaft <NUM> from which second elevator car <NUM> may arrive. The message may be transmitted via call device <NUM> in various suitable formats, including, for example, via a display (e.g., a written form, a graphic form, etc.), a speaker (e.g., an audible form), and more.

Dispatch controller <NUM> may be configured to store the sensor data <NUM> of each of the plurality of elevator cars <NUM>, <NUM> in memory <NUM>. It should be appreciated that dispatch controller <NUM> may continuously store sensor data <NUM> of elevator cars <NUM>, <NUM> in response to the repeated use of dispatch system <NUM> when receiving calls (step <NUM>) and obtaining sensor data <NUM> (step <NUM>) to determine which of the plurality of elevator cars <NUM>, <NUM> to dispatch to the call (step <NUM>). Accordingly, memory <NUM> may provide a database of load measurements for each of the plurality of elevator cars <NUM>, <NUM>. Further, dispatch controller <NUM> may determine a timing of when each load measurement is received by dispatch controller <NUM> such that the sensor data <NUM> stored in memory <NUM> may be associated with a corresponding time interval. It should be appreciated that the sensor data <NUM> may be accessible for review by a user of dispatch system <NUM> via user interface <NUM>.

At step <NUM>, dispatch controller <NUM> may be configured to determine a maximum load of each elevator car <NUM>, <NUM> from the one or more load measurements received from sensing devices <NUM> during one or more predefined periods. The predefined period may include various time intervals during which sensor data <NUM> is received from the plurality of elevator cars <NUM>, <NUM>. For example, the predefined period may include, but is not limited to, one or more hours of a day, one or more days of a week, one or more weeks of a month, one or more months of a year, etc. Accordingly, dispatch controller <NUM> may determine the maximum load measurement of each elevator car <NUM>, <NUM> for a particular predefined period. It should be appreciated that memory <NUM> may include corresponding load measurements (e.g., sensor data <NUM>) for a plurality of predefined periods.

In the present example, the predefined period may include a two-hour duration (e.g., <NUM>:<NUM> PM to <NUM>:<NUM> PM) during weekdays (e.g., Monday, Tuesday, Wednesday, Thursday, and Friday). In this instance, the maximum load measurement of each elevator car <NUM>, <NUM> may be determined from the one or more load measurements received from elevator cars <NUM>, <NUM> during the two-hour duration of each weekday. At step <NUM>, dispatch controller <NUM> may be configured to generate a modified load setting <NUM> for each elevator car <NUM>, <NUM> based on the maximum load received by each respective elevator car <NUM>, <NUM> during the predefined period. That is, according to the present invention, the modified load setting <NUM> equals the greatest load measurement received by each elevator car <NUM>, <NUM> during the predefined period.

In some embodiments, dispatch controller <NUM> may receive a user input (e.g., via user interface <NUM>), at step <NUM>, with a command to determine the modified load setting <NUM> for one or more of the plurality of elevator cars <NUM>, <NUM>. It should be appreciated that each modified load setting <NUM> may be associated with a particular elevator car <NUM>, <NUM> and a particular predefined period during which the maximum load measurement, from which the modified load setting <NUM> is derived from, was received. It should be understood that the modified load setting <NUM> may be applicable to the predefined period.

In the present example, the maximum load measurement received by first elevator car <NUM> during the predefined period may equal about <NUM>,<NUM> pounds, and the maximum load measurement received by second elevator car <NUM> during the predefined period may equal about <NUM>,<NUM> pounds. Accordingly, dispatch controller <NUM> may adjust the original load setting <NUM> of first elevator car <NUM> from <NUM>,<NUM> pounds to <NUM>,<NUM> pounds (e.g., the modified load setting <NUM>) during the two-hour duration on weekdays. Dispatch controller <NUM> may further adjust the load setting <NUM> of second elevator car <NUM> from <NUM>,<NUM> pounds to <NUM>,<NUM> pounds (e.g., the modified load setting <NUM>) during the two-hour duration on weekdays.

In other embodiments, dispatch controller <NUM> may be configured to automatically generate the modified load setting <NUM> for one or more of the plurality of elevator cars <NUM>, <NUM>. For example, dispatch controller <NUM> may automatically generate the modified load setting <NUM> based on determining the maximum load measurement is less than the load setting <NUM> by a predetermined threshold. The predetermined threshold may be determined by dispatch controller <NUM> or defined by a user of dispatch system <NUM>. In some examples, the predetermined threshold may range from about <NUM>% to about <NUM>%.

In the present example, the predetermined threshold may be set to about <NUM>%. With the maximum load measurement of first elevator car <NUM> (e.g., <NUM>,<NUM> pounds) being less than the load setting <NUM> of first elevator car <NUM> (e.g., <NUM>,<NUM> pounds) by about <NUM>%, dispatch controller <NUM> may automatically generate the modified load setting <NUM> for first elevator car <NUM>. Further, with the maximum load measurement of second elevator car <NUM> (e.g., <NUM>,<NUM> pounds) being less than the load setting <NUM> of second elevator car <NUM> (e.g., <NUM>,<NUM> pounds) by about <NUM>%, dispatch controller <NUM> may forgo generating the modified load setting <NUM> for second elevator car <NUM>. It should be appreciated that dispatch controller <NUM> may be operable to account for small losses in load measurements attributed to various sources, including the sensing device <NUM>, hoist way issues, and more.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may be configured to apply the modified load setting <NUM> in substitute of the load setting <NUM>. It should be understood that the modified load setting <NUM> may be an adjustment to the load setting <NUM>, and applicable in lieu of the original load setting <NUM>, during the predefined period. In this instance, when receiving a new call request (step <NUM>) during the predefined period (e.g., between <NUM>:<NUM> PM to <NUM>:<NUM> PM on weekdays), dispatch controller <NUM> may compare a detected load measurement of the elevator car <NUM>, <NUM> (step <NUM>) to the modified load setting <NUM> (step <NUM>) when determining whether the elevator car <NUM>, <NUM> includes sufficient capacity to receive the call.

Referring now to <FIG>, an example method <NUM> of using dispatch system <NUM> to determine an occupancy at a plurality of locations, and to position inactive elevator cars at the location having a greater occupancy, is depicted. It should be understood that the steps shown and described herein, and the sequence in which they are presented, are merely illustrative such that various embodiments may include additional and/or fewer steps without departing from a scope of this disclosure. Further, it should be appreciated that dispatch system <NUM> may perform example method <NUM> in conjunction with one or more other processes, such as method <NUM> described above.

At step <NUM>, dispatch system <NUM> may receive a call request at a location of a plurality of locations within working environment <NUM>. The call may be initiated in response to a prospective occupant <NUM> actuating call device <NUM> at the location (e.g., one of floors 204A-204D). Call device <NUM> may transmit the call to dispatch controller <NUM> via network <NUM>. In the present example, dispatch controller <NUM> may receive the call from a first location (e.g., second floor 204B) for transportation to a second location (e.g., first floor 204A). Dispatch controller <NUM>, in accordance with zoning logic <NUM>, may receive motion data from a corresponding motion controller <NUM> of each elevator car <NUM>, <NUM> to determine current motion parameters of the plurality of elevator cars <NUM>, <NUM>.

Dispatch controller <NUM> may further receive sensor data <NUM> from a corresponding sensing device <NUM> of each elevator car <NUM>, <NUM> to determine a current load of elevator cars <NUM>, <NUM>. Motion controller <NUM> and sensing device <NUM> may each transmit a signal to dispatch controller <NUM> (via network <NUM>) indicative of the motion data and the sensing data <NUM> of the corresponding elevator car <NUM>, <NUM>, respectively. At step <NUM>, dispatch controller <NUM> may dispatch at least one of the plurality of elevator cars <NUM>, <NUM> having a current load that does not exceed the respective load setting <NUM> (and/or modified load setting <NUM>) of the elevator car <NUM>, <NUM>, such as, for example, in accordance with the steps of method <NUM> described above. In the present example, first elevator car <NUM> may be dispatched to the first location of the call (e.g., second floor 204B) to pick up the prospective occupant <NUM>.

Still referring to <FIG>, at steps <NUM> to <NUM>, dispatch controller <NUM> may be configured to determine an occupancy at a plurality of locations. For example, at step <NUM>, dispatch controller <NUM> may be configured to determine a first load measurement of first elevator car <NUM> when arriving at the first location (e.g., a load start value). In this instance, sensing device <NUM> may transmit a signal to dispatch controller <NUM> of the first load measurement (e.g., sensor data <NUM>) when the motion parameters received from motion controller <NUM> indicate first elevator car <NUM> has arrived at the first location. In the present example, the first load measurement may include a load indicative of a single occupant <NUM> located within the cabin of first elevator car <NUM> when arriving at second floor 204B.

At step <NUM>, dispatch controller <NUM> may be configured to determine a second load measurement of first elevator car <NUM> when departing from the first location (e.g., a load end value). In this instance, sensing device <NUM> may transmit a signal to dispatch controller <NUM> of the second load measurement (e.g., sensor data <NUM>) when the motion parameters received from motion controller <NUM> indicate first elevator car <NUM> has departed the first location. In the present example, the second load measurement may include a load indicative of a pair of occupants <NUM> located within the cabin of first elevator car <NUM> when departing second floor 204B. At step <NUM>, dispatch controller <NUM> may be configured to determine a difference between the first load measurement (step <NUM>) and the second load measurement (step <NUM>) to compute a resulting occupancy at the first location. Accordingly, to determine a corresponding number of prospective occupants <NUM> received from (and/or transferred to) the first location, dispatch controller <NUM> may compare the first load measurement of first elevator car <NUM> when arriving at second floor 204B to the second load measurement after departing from second floor 204B.

In the present example, first elevator <NUM> may include a first load measurement of about <NUM> pounds to about <NUM> pounds upon arriving to the first location, and about <NUM> pounds to about <NUM> pounds upon departing from the first location to the destination location (e.g., first floor 204A). Accordingly, dispatch controller <NUM> may be configured to determine that about one prospective occupant <NUM> entered first elevator car <NUM> from second floor 204B. It should be appreciated that dispatch controller <NUM> may store a predetermined occupant load in memory <NUM>. In this instance, dispatch controller <NUM> may correlate the one or more load measurements to a number of occupants <NUM> via conversion with the predetermined occupant load. For example, the predetermined occupant load may range from about <NUM> pounds to about <NUM> pounds, such as <NUM> pounds. In other embodiments, the one or more load measurements may be in various other metric forms, including, for example, volts direct current (VDC). In this instance, dispatch controller <NUM> may correlate one volt to a predetermined load variable, such as, for example, a weight ranging from about <NUM> pounds to about <NUM> pounds. It should be appreciated that various other suitable metrics of the load measurements may be implemented by dispatch system <NUM> without departing from a scope of this disclosure.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may determine whether the elevator car <NUM>, <NUM> is in an inactive state. For example, dispatch controller <NUM> may be configured to determine an operating status of first elevator car <NUM>, such as whether first elevator car <NUM> is actively completing a call and/or is assigned to answer an additional call. In the present example, upon receiving the prospective occupant <NUM> from second floor 204B (e.g., the first location), first elevator car <NUM> may be dispatched to a destination of the prospective occupants <NUM> (e.g., a second location) to complete the call request. Accordingly, dispatch controller <NUM> may determine first elevator car <NUM> remains in an active state at step <NUM>, and return to step <NUM> to dispatch first elevator car <NUM> to the second location. Dispatch controller <NUM> may be configured to repeat steps <NUM> to <NUM> to determine an occupancy of the second location (e.g., first floor 204A). Accordingly, dispatch controller <NUM> may measure a first load measurement of first elevator car <NUM> upon arriving to the second location (step <NUM>) and a second load measurement upon departing from the second location (step <NUM>). Dispatch controller <NUM> may determine a difference (i.e., percent load change) between the first and second load measurements (step <NUM>) to compute a resulting occupancy at the second location.

It should be understood that dispatch controller <NUM> may compute a percent load change for each of the plurality of locations when at least one of the plurality of elevator cars <NUM>, <NUM> travels to said location to answer a call (e.g., pick up a prospective occupant <NUM>) and/or to complete a call (e.g., drop off an occupant <NUM>). Dispatch controller <NUM> may generate local load data <NUM> for the first and second locations based on the occupancy computed at step <NUM>, respectively. The local load data <NUM> may include a measurement of a load transferred by first elevator car <NUM> to and/or from the first location (e.g., second floor 204B) and the second location (e.g., first floor 204A). The local load data <NUM> may be indicative of a number of occupants <NUM> located at the location after an arrival and departure of first elevator car <NUM> from said location.

It should be understood that the local load data <NUM> may include a comprehensive measurement that accounts for a cumulative load transported to, and from, the location by the plurality of elevator cars <NUM>, <NUM>. Accordingly, dispatch controller <NUM> may maintain a current occupancy determination for each of the plurality of locations. Dispatch controller <NUM> may be configured to store the local load data <NUM> in memory <NUM>, and continuously update the local load data <NUM> for each of the plurality of floors 204A-204D during continued use of dispatch system <NUM>.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may determine whether the elevator car <NUM>, <NUM> is in an inactive state. Dispatch controller <NUM> may determine that first elevator car <NUM> is in an inactive state when no further calls are assigned to first elevator car <NUM>, and/or first elevator car <NUM> does not include additional destinations from existing calls. In response to determining first elevator car <NUM> is in an inactive state at step <NUM>, dispatch controller <NUM> may be configured to determine at least one location of the plurality of locations that has a maximum occupancy at step <NUM>. That is, dispatch controller <NUM> may be configured to compare the local load data <NUM> of the plurality of locations relative to one another to assess a current occupancy at each location.

Dispatch controller <NUM> may determine fourth floor 204D includes an occupancy that is greater than the occupancy of the remaining plurality of locations. In the present example, as seen in <FIG>, first floor 204A may include two occupants <NUM> (e.g., recently transported thereto by first elevator car <NUM>), second floor 204B may include one remaining occupant <NUM>, third floor 204C may include two occupants <NUM>, and fourth floor 204D may include three occupants <NUM>. Accordingly, dispatch controller <NUM> may determine that fourth floor 204D includes a current occupancy that is greater than the occupancy of the remaining floors 204A-204C.

At step <NUM>, dispatch controller <NUM> may be configured to move first elevator car <NUM> to fourth floor 204D. First elevator car <NUM> may be positioned at fourth floor 204D while first elevator car <NUM> remains in an inactive state. Stated differently, first elevator car <NUM> may be parked at fourth floor 204D until a call request from one of the plurality of floors 204A-204D (e.g., via call device <NUM>) is assigned to first elevator car <NUM> by dispatch controller <NUM>. It should be appreciated that, with first elevator car <NUM> maintained at fourth floor 204D, and with fourth floor 204D including a greater occupancy than the remaining plurality of floors 204A-204C, a minimum travel distance for answering a future call request with first elevator car <NUM> may be minimized.

It should be appreciated that dispatch controller <NUM> may be configured to periodically reassess the current occupancy (e.g., local load data <NUM>) of each of the plurality of floors 204A-204D. Accordingly, dispatch controller <NUM> may move one or more inactive elevator cars <NUM>, <NUM> to a modified location based on updated local load data <NUM>. For example, in response to determining the first location (identified at step <NUM>) no longer includes a greater occupancy relative to the plurality of other locations, dispatch controller <NUM> may be configured to reposition the inactive elevator car(s) <NUM>, <NUM> to a second location having the greatest occupancy.

In some embodiments, method <NUM> may include further steps for positioning one or more inactive elevators at additional locations when a number of inactive elevator cars <NUM>, <NUM> at the first location (e.g., fourth floor 204D) exceeds a predetermined threshold. In other embodiments, a user of dispatch system <NUM> may identify a number of locations at which the plurality of elevator cars <NUM>, <NUM> may be parked at when in an inactive state. For example, dispatch controller <NUM> may receive a user input (e.g., via user interface <NUM>) indicating three locations for parking inactive elevator cars <NUM>, <NUM>. In this instance, dispatch controller <NUM> may determine which three locations of the plurality of locations have the greatest occupancy relative to the remaining plurality of locations, and direct any inactive elevator cars <NUM>, <NUM> to at least one of the three locations. In some embodiments, dispatch controller <NUM> may be operable to generate a report (e.g., via user interface <NUM>) including information relating to one or more of the load setting <NUM>, the sensor data <NUM>, the modified load setting <NUM>, the local load data <NUM>, and more.

It should be appreciated that the one or more processes of dispatch system <NUM> shown and described herein, such as example methods <NUM>, <NUM>, may be implemented in various other working environments. In one example, dispatch system <NUM> may be configured to apply one or more of example methods <NUM>, <NUM> in a transit system, such as a bus service, a train service, a subway service, a metro service, a ridesharing service, etc. With respect to example method <NUM>, dispatch system <NUM> may render a transportation unit (e.g., a bus, a train, a subway, a metro, a vehicle, etc.) inoperable for receiving additional calls and/or occupants when exceeding its maximum load capacity. In this instance, the transportation unit may bypass the location (e.g., the stop) and/or inhibit receipt of additional load onto the transportation unit (e.g., by not opening doors). In some embodiments, dispatch system <NUM> may be configured to communicate with one or more remote stations to transmit information indicative of a current load.

For example, dispatch system <NUM> may transmit alerts to remote station(s) requesting assistance from additional transportation units (e.g., a bus, a train, a subway, a metro, a vehicle, etc.) at one or more locations when the current load of one or more current transportation units exceed a maximum load capacity. It should be appreciated that dispatch system <NUM> may promote traffic flow by determining a minimum number of transportation units required at one or more locations, or at one or more predefined intervals, to accommodate an expected load based on local load data of various locations. With respect to example method <NUM>, dispatch system <NUM> may determine an occupancy at a plurality of locations (e.g., bus stops, train stops, subway stops, metro stops, etc.) to position inactive transportation unit (e.g., a bus, a train, a subway, a metro, a vehicle, etc.) at the location having a greater occupant count.

Claim 1:
A method (<NUM>) of adjusting a load setting of an elevator car (<NUM>), comprising:
Receiving (<NUM>) one or more load measurements associated with the elevator car (<NUM>) during a predefined period ;
Determining (<NUM>) a maximum load of the elevator car (<NUM>) during the predefined period from the one or more load measurements;
generating (<NUM>) a modified load setting for the elevator car (<NUM>) based on the maximum load, such that the modified load setting equals the greatest load measurement received by the elevator car (<NUM>) during the predefined period; and
replacing (<NUM>) the load setting (<NUM>) of the elevator car (<NUM>) with the modified load setting (<NUM>) during the predefined period.