Patent Description:
Commonly, elevator cars are organized into elevator groups serving a range of landings of a building rather than each elevator car serving every floor of a building. Once established, the ranges of landings typically remain unchanged due to physical constraints in the elevator system. In conventional elevator systems, a building may have several groups where the floors served by one group do not overlap with the floors served by any other group except, perhaps, the main lobby or other special floors. <CIT> describes an elevator dispatching system comprising a plurality of zones, in which elevator cars are allocated from one zone to another in response to a maximum estimated wait time being exceeded. <CIT> describes a method for dividing destination calls in an elevator system on the basis of division criteria. <CIT> describes a control method for an elevator system in which elevator cars are divided into serving sectors comprising floors to be served by at least one elevator car, in which elevator cars may be reassigned to different service sectors based on historic car usage data. <CIT> describes a method for distributing service calls in an elevator system within a building, in which floors within the building are divided into zones, and the limits of these zones are dynamically changed based on transportation needs.

According to an embodiment of the invention, a method of operating a building elevator system within a building having a plurality of landings is provided according to claim <NUM>.

Some embodiments may include that the range of landings served by one or more elevator systems of the second elevator group is adjusted to serve one or more landings gravitationally above the second range of landings.

Some embodiments may include that the range of landings served by one or more elevator systems of the second elevator group is adjusted to serve one or more landings gravitationally below the second range of landings.

Some embodiments may include that the range of landings served by one or more elevator systems of the second elevator group is adjusted to serve one or more landings of the first range of landings.

Some embodiments may include that prior to adjusting a range of landings the first range of landings does not include landings within the second range of landings with the exception of an egress landing.

Some embodiments may include that the first range of landings is a lower range of landings and the second range of landings is a higher range of landings located at a higher elevation than the lower range of landings with the exception of an egress landing.

Some embodiments may include: receiving an elevator call for a landing within the first range of landings; and moving an elevator car of the one or more elevator systems of the second elevator group to the landing within the first range of landings.

Some embodiments may include: receiving an elevator call for a landing within the first range of landings; determining an elevator car of the one or more elevator systems of the first elevator group or an elevator car of the one or more elevator systems of the second elevator group to best serve the elevator call in response to a relative amount of traffic with the first range of landings and the second range of landings; and moving the elevator car determined to the landing within the first range of landings.

According to another embodiment of the invention, a building elevator system is provided according to claim <NUM>.

Technical effects of embodiments of the present disclosure include organizing elevator systems into groups serving a range of landings and determining when an elevator car from one elevator group may serve another elevator group in overlapping landings.

Referring now to <FIG> with continued reference to <FIG>. As seen in <FIG>, a building elevator system <NUM> within a building <NUM> may include multiple different individual elevator systems 101a-101j organized in elevator groups 112a-112b. It is understood that while ten elevator systems 101a-101j are utilized for exemplary illustration, embodiments disclosed herein may be applied to building elevator systems <NUM> having two or more elevator systems <NUM>. It is also understood that while twenty-six landings 125a-125z are utilized for exemplary illustration, embodiments disclosed herein may be applied to building elevator systems <NUM> having any number of landings.

Further, the elevator systems 101a-101j illustrated in <FIG> is organized into two elevator groups 112a, 112b for ease of explanation but it is understood that the elevator systems 101a-101j may be organized into one or more elevator groups. Each elevator group 112a-112b may contain one or more elevator systems <NUM>. Elevator cars <NUM> in the same group typically have the characteristic that: the elevator machines are in physical proximity, the hoistways are physically located so that elevator doors on a given landing are served by the same lobby space, the elevator controllers are operably connected in a common communication network, the elevator controllers are assigned elevator calls by a common group controller, and/or share common emergency power components. During normal operation, a first elevator group 112a serves a first range of landings 250a (i.e., a lower range of landing) comprising landings 125a-<NUM>. During normal operation, a second elevator group 112b serves a second range of landings 250b (i.e., a higher range of landings) comprising landings 125n-125z and landing 125a (e.g., egress landing, ground landing, lobby landing, or exit landing). The higher range of landings is located at a higher elevation than the lower range of landings. It is understood that while each elevator group 112a-112b serves only one range of landings <NUM> for exemplary illustration, embodiments disclosed herein may include elevator groups having multiple elevator systems where each elevator system in a single elevator group serves a different range of landings or any number of elevators serve any select group of continuous or noncontinuous landings.

Each landing 125a-125z in the building <NUM> of <FIG> may have a destination entry device 89a-89z. The elevator destination entry device 89a-89z sends an elevator call <NUM> to a redirector <NUM> including the source of the elevator call <NUM> and the destination of the elevator call <NUM>. The destination entry device 89a-89z may serve one or more elevator groups 112a-112b. The destination entry device 89a-89z may be a push button and/or a touch screen and may be activated manually or automatically. For example, the elevator call <NUM> may be sent by an individual entering the elevator call <NUM> via the destination entry device 89a-89z. The destination entry device 89a-89z may also be activated to send an elevator call <NUM> by voice recognition or a passenger detection mechanism in the hallway, such as, for example a weight sensing device, a visual recognition device, and a laser detection device. The destination entry device 89a-89z may be activated to send an elevator call <NUM> through an automatic elevator call system that automatically initiates an elevator call <NUM> when an individual is determined to be moving towards the elevator system in order to call an elevator or when an individual is scheduled to activate the destination entry device 89a-89z. The destination entry device 89a-89z may also be a mobile device configured to transmit and elevator call <NUM>. The mobile device may be a smart phone, smart watch, laptop, or any other mobile device known to one of skill in the art. It is understood that while a redirector <NUM> is used for exemplary illustration, embodiments disclosed herein may be applicable to elevator systems <NUM> with different elevator call control methods, such as, for example, a traditional two-button interface with hall call buttons (up/down) at the landings and car call buttons (with destination floors) inside the elevator car <NUM>.

The redirector <NUM> may be in communication with the controller 115a-115j of each elevator system 101a-101j through a dispatcher 210a-210b and a server 212a-212b, as shown in <FIG>. The dispatchers 210a-210b may comprise group control software that is configured to select the best elevator car 103a-103j within the range of landings <NUM> assigned to the dispatcher 210a-210b. The dispatcher 210a-210b may be an electronic controller including a processor and an associated memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform various operations. The processor may be, but is not limited to, a single-processor or multi-processor system of any of a wide array of possible architectures, including field programmable gate array (FPGA), central processing unit (CPU), application specific integrated circuits (ASIC), digital signal processor (DSP) or graphics processing unit (GPU) hardware arranged homogenously or heterogeneously. The memory may be but is not limited to a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable medium. It is understood that while destination entry devices 89a-89z are used for exemplary illustration, embodiments disclosed herein may be applicable to elevator systems <NUM> with different elevator call control architectures.

The servers 212a-212b are similar to a redirector <NUM> being that the servers 212a-212b manages the destination entry devices 89a-89z related to a particular group 112a-112b (e.g., the redirector <NUM> interfaces with destination entry devices 89a-89z that are shared between groups 112a-112b). In an embodiment, the servers 212a-212b may be configured to operate as a pass through between the redirector <NUM> and the dispatcher 210a-210b associated with the server 212a-212b.

The controllers 115a-115j can be combined, local, remote, cloud, etc. The redirector <NUM> is configured to control and coordinate operation of multiple elevator systems 101a-101j. The redirector <NUM> may be an electronic controller including a processor and an associated memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform various operations. The processor may be, but is not limited to, a single-processor or multi-processor system of any of a wide array of possible architectures, including field programmable gate array (FPGA), central processing unit (CPU), application specific integrated circuits (ASIC), digital signal processor (DSP) or graphics processing unit (GPU) hardware arranged homogenously or heterogeneously. The memory may be but is not limited to a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable medium.

The redirector <NUM> is in communication with each of the elevator destination entry devices 89a-89z of the building elevator system <NUM>, which are shared by more than one group 112a-112b. The first range of landings 250a or the second range of landings 250b may be adjusted in response to at least one of a time of day and an intensity of traffic within each of the first range of landings 250a and the second first range of landings 250b. If the redirector <NUM> is monitoring the elevator calls <NUM> coming in from the elevator destination entry devices 89a-89z and determines that the one of the elevator groups 112a-112b needs additional assistances answering the calls then the redirector <NUM> may adjust the range of landings served by one or more elevator systems <NUM>. The redirector may be remote, local, cloud, or any combinations thereof.

As shown in the example of <FIG> at block <NUM>, if the first elevator group 112a is experiencing an increased quantity of elevator calls <NUM> then the range of landings served by one or more elevators systems 101f-<NUM> of the second elevator group 250b may be extended to help serve landings 125a-<NUM> of the first range of landings 250a and the first elevator group 112a. In <FIG>, the range of landings served by elevators systems 101f-<NUM> are extended by two landings <NUM>, <NUM> to help serve increased elevator calls <NUM> to the first elevator group 112a. It is understood that <FIG> is for exemplary purposes and any number of elevator systems of the second elevator group 112b may be extended any number of landings <NUM>.

As shown in the example of <FIG> at block <NUM>, if the second elevator group 112b is experiencing an increased quantity of elevator calls <NUM> then the range of landings served by one or more elevators systems 101d-101e of the first elevator group 112a may be extended to help serve landings 125n-125z of the second range of landings 250b and the second elevator group 112b. In <FIG>, the range of landings served by elevators systems 101d-101e are extended by two landings 125n, 125o to help serve increased elevator calls <NUM> to the second elevator group 112b. It is understood that <FIG> is for exemplary purposes and any number of elevator systems of the first elevator group 112a may be extended any number of landings <NUM>. In one embodiment, both block <NUM> and <NUM> are added. In another embodiment, only block <NUM> is added. In yet another embodiment, only block <NUM> is added.

The redirector <NUM> may also be configured to adjust the range of landings served by one or more elevator systems <NUM> in accordance with a preset schedule by the time of day (i.e., known traffic patterns due to history) or in accordance with the prevailing traffic pattern.

Referring now to <FIG>, while referencing components of <FIG>. <FIG> shows a flow chart of method <NUM> of operating a building elevator system <NUM> within a building <NUM> having a plurality of landings <NUM>, in accordance with an embodiment of the disclosure. In an embodiment, the method <NUM> may be performed by the redirector <NUM>.

At block <NUM>, a first elevator group 112a comprising one or more elevator system 101a-101e is controlled. Each of the one or more elevator systems 101a-101e of the first elevator group 112a comprises an elevator car 103a-103e configured to serve a first range of landings 250a.

At block <NUM>, a second elevator group 112b comprising one or more elevator system 101f-101j is controlled. Each of the one or more elevator systems 101f-101j of the second elevator group 112b comprises an elevator car 103f-103j configured to serve a second range of landings 250b. In an embodiment, the first range of landings 250a does not include landings within the second range of landings 250b with the exception of an egress landing 125a.

In another embodiment, first range of landings 250a is a lower range of landings and the second range of landings 250b is a higher range of landings located at a higher elevation than the lower range of landings with the exception of an egress landing 125a.

At block <NUM>, at least one of the amount of traffic received by the first elevator group 112a relative to the amount of traffic received by the second elevator group 112b, and the amount of traffic within the first range of landings 250a relative to the amount of traffic within the second range of landings 250b is detected.

The predicted passenger response time (e.g., waiting time or time to destination) could be based on the conditions of each elevator system <NUM> within an elevator group 250a-250b at the time of the call. The predicted passenger response time to a new call for given elevator system <NUM> may be calculated so that it is understand the likely waiting time (or time to destination) if an elevator call were to be assigned to the elevator system <NUM>. The general application of a predicted passenger response time calculation is by running that calculation through each of the eligible elevator systems 101a-101j at the time when an elevator call <NUM> is received. Note that a less computationally-intensive predicted passenger response time could be based purely on the time of day by learning the response times from historical data.

For example, the decision on whether or not to consider an elevator car 103f-<NUM> to receive a call involving landing <NUM>-<NUM> might be based on predicting the response time to serve a given elevator call <NUM>. If one of elevator systems 101a-101e can best serve the elevator call <NUM>, then the elevator call <NUM> should be assigned to one of those elevator systems 101a-101e; whereas, if one of the elevator systems 101f-<NUM> can best serve the elevator call <NUM>, the elevator call <NUM> should be assigned accordingly. There may be variations, such as if the predicted passenger response time by service from elevator systems 101a-101e is within an acceptable threshold, then assign to one of those elevator systems 101a-101e but otherwise, consider the predicted passenger response time of elevator systems 101f-<NUM> as well when block <NUM> is enabled.

The amount of traffic may be based on the volume of elevator car <NUM> traffic within a timeframe. For example, the amount of traffic could be the total volume of traffic within the timeframe, the volume of traffic from an origin landing within the time frame, the volume of traffic to a destination floor within the timeframe, the volume of traffic between a subset of landings to another subset of landings within the timeframe. The amount of traffic may also be not just a volume, but also a relative proportion of elevator car <NUM> traffic. In the example of <FIG>, it could consider the relative amount of traffic between the first range of landings 250a and the second range of landings 250b. For example, if there is an unusually high proportion of traffic within the first range of landings 250a, then block <NUM> may be utilized to allow some of the elevators 101f-<NUM> to serve some of the traffic to or from landings <NUM>-<NUM>.

At block <NUM>, a range of landings <NUM> (e.g., see block <NUM> in <FIG>) served by one or more elevator systems 1013f-<NUM> of the second elevator group 112b is adjusted in response to at least one of the amount of traffic received by the first elevator group 112a relative to the amount of traffic received by the second elevator group 112b, and the amount of traffic within the first range of landings 250a relative to the amount of traffic within the second range of landings 250b. The method <NUM> may further comprise: receiving an elevator call for a landing <NUM>-<NUM> within the first range of landings 250a; and moving an elevator car 103f-<NUM> of the one or more elevator systems 101f-<NUM> of the second elevator group 112b to the landing <NUM>-<NUM> within the first range of landings 250a. The "receiving an elevator call for a landing <NUM>-<NUM> within the first range of landings 250a" may include both if the origin is within the first range of landings 250a and/or if the destination is within the first range of landings 250a.

The method <NUM> may further comprise: receiving an elevator call for a landing <NUM>-<NUM> within the first range of landings 250a; determining an elevator car 103a-103e of the one or more elevator systems 101a-101e of the first elevator group 112a or an elevator car 103f-<NUM> of the one or more elevator systems 101f-<NUM> of the second elevator group 112b to best serve the elevator call <NUM> in response to a relative amount of traffic with the first range of landings 250a and the second range of landings <NUM>; and moving the elevator car determined to the landing <NUM>-<NUM> within the first range of landings 250a.

In an embodiment, the range of landings served by one or more elevator systems <NUM> of the second elevator group 112b may be adjusted to serve one or more landings gravitationally above the second range of landings 250b and/or gravitationally below the second range of landings 250b. In another embodiment, the range of landings served by one or more elevator systems <NUM> of the second elevator group 112b may be adjusted to serve one or more landings of the first range of landings 250a.

At block <NUM>, at least one of the amount of traffic received by the first elevator group 112a relative to the amount of traffic received by the second elevator group 112b, and the amount of traffic within the first range of landings 250a relative to the amount of traffic within the second range of landings 250b. At block <NUM>, a range of landings <NUM> (e.g., see block <NUM> in <FIG>) served by one or more elevator systems 101d-101e of the first elevator group 112a is adjusted in response to at least one of the amount of traffic received by the first elevator group 112a relative to the amount of traffic received by the second elevator group 112b, and the amount of traffic within the first range of landings 250a relative to the amount of traffic within the second range of landings 250b. The method <NUM> may further comprise: receiving an elevator call for a landing 125n-125o within the second range of landings 250b; and moving an elevator car 103d-103e of the one or more elevator systems 101d-101e of the first elevator group 112a to the landing 125n-125o within the second range of landings 250b. The method <NUM> may further comprise: receiving an elevator call <NUM> for a landing 125n-125o within the second range of landings 250b; determining an elevator car 103d-103e of the one or more elevator systems 101d-101e of the first elevator group 112a or an elevator car 103f-103j of the one or more elevator systems 101f-101j of the second elevator group 112b to best serve the elevator call <NUM> in response to a relative amount of traffic with the first range of landings 250a and the second range of landings 250b; and moving the elevator car determined to the landing 125n-125o within the second range of landings 250b.

In an embodiment, the range of landings served by one or more elevator systems <NUM> of the first elevator group 112a may be adjusted to serve one or more landings gravitationally above the first range of landings 250a and/or gravitationally below the first range of landings 250a. In another embodiment, the range of landings served by one or more elevator systems <NUM> of the first elevator group 112a may be adjusted to serve one or more landings of the second range of landings 250b.

As described above, embodiments can be in the form of processor-implemented processes and devices for practicing those processes, such as processor. Embodiments can also be in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes a device for practicing the embodiments.

Claim 1:
A method of operating a building elevator system (<NUM>) within a building (<NUM>) having a plurality of landings (125a-125z), the method comprising:
controlling a first elevator group (112a) comprising one or more elevator systems (101a-101e), wherein each of the one or more elevator systems (101a-101e) of the first elevator group (112a) comprises an elevator car (103a-103e) configured to serve a first range of landings (250a);
controlling a second elevator group (112b) comprising one or more elevator systems (101f-101j), wherein each of the one or more elevator systems (101f-101j) of the second elevator group (112b) comprise an elevator car (103f-103j) configured to serve a second range of landings (250b); and characterized by:
detecting at least one of the amount of traffic received by the first elevator group (112a) relative to the amount of traffic received by the second elevator group (112b), and the amount of traffic within the first range of landings (250a) relative to the amount of traffic within the second range of landings (250b); and
adjusting a range of landings served by one or more elevator systems (101f-101j) of the second elevator group (112b) in response to at least one of the amount of traffic received by the first elevator group (112a) relative to the amount of traffic received by the second elevator group (112b), and the amount of traffic within the first range of landings (250a) relative to an amount of traffic within the second range of landings (250b).