Patent Description:
Elevator passengers may be resistant to travel with robots, other passengers with pets, and the like. There is a need to provide an elevator system that can enable passengers to travel comfortably in these situations in the elevator car.

<CIT> discloses an elevator device comprising a shaft provided with two landing place side entrances on different side faces at each story, a car elevated and lowered in the shaft and provided with two car side entrances constituted to oppose to the landing place side entrances and a movable bulkhead for dividing an accommodation space so as to face the car side entrances, respectively, when the elevator stops at each story, and a controller for controlling the car and the movable bulkhead in such a way that it moves the movable bulkhead so as to divide the accommodation space in the car and the passengers getting on from different car side entrances are conveyed in the different and divided accommodation spaces.

According to a first aspect of the invention, disclosed is an elevator system as claimed in claim <NUM>.

In addition to one or more of the above disclosed aspects of the system, one of the zones may include a sensor operationally coupled to the controller and other one of the zones may include a video display that is operationally coupled to the controller, and the controller may be configured to control the sensor and display so that, when the divider system is deployed, images or video captured from the one of the zones is displayed in the other one of the zones via the display.

In addition to one or more of the above disclosed aspects of the system, the divider system may include a transparent portion to provide persons in one of the zones with visual access to the other one of the zones when the divider system is deployed.

In addition to one or more of the above disclosed aspects of the system, the cabin may include a first sidewall and a second sidewall; and the divider system may include: a first door operationally coupled to the first sidewall; and a second door operationally coupled to the second sidewall.

In addition to one or more of the above disclosed aspects of the system, the controller may be configured to: transition the divider system to the deployed state from the retracted state upon rendering a determination that a first trigger condition is met; and transition the divider system to the retracted state from the deployed state upon rendering a determination that a second trigger condition is met.

In addition to one or more of the above disclosed aspects of the system, the controller may be configured to determine one or more of: the first trigger condition is met when a pet or robot enters the elevator car; or the second trigger condition is met when one or more of a passenger count, furniture, equipment or personal belongings that are larger than a predetermined size enters the elevator car.

In addition to one or more of the above disclosed aspects of the system, the controller may be configured to receive data from one or more of: a sensor onboard the elevator car or at a landing, operationally connected to the controller; or a wireless network that is communicatively coupled with the controller; and the controller may be configured to: render a determination from the data of whether the first or second trigger conditions are met.

In addition to one or more of the above disclosed aspects of the system, the controller may be configured to: determine from the data received over the wireless network that the first or second trigger conditions will be met at a landing prior to stopping at the landing; and transition the divider system to the deployed state or the retracted state when, or prior to, stopping at the landing, responsive to the determination.

In addition to one or more of the above disclosed aspects of the system, the controller may be operationally coupled to the front and aft doors and may be configured to prevent more than one of the front and aft doors from opening at a landing when the divider system is in the retracted state.

In addition to one or more of the above disclosed aspects of the system, the doors may include seals around their respective perimeters; the front and aft zones of the elevator car may respectively include front and aft balanced ventilation systems that are operationally controlled by the controller, wherein the controller may be configured to operate the front and aft balanced ventilation systems when the divider system is in the deployed state.

According to a second aspect of the invention, further disclosed is a method of operating an elevator system as claimed in claim <NUM>.

In addition to one or more of the above disclosed aspects of the method, controlling the divider system may include controlling a first door operationally coupled to a first sidewall of the cabin, and a second door operationally coupled to a second sidewall of the cabin.

In addition to one or more of the above disclosed aspects of the method, controlling the divider system may include: transitioning the divider system to the deployed state from the retracted state upon rendering a determination that a first trigger condition is met; and transitioning the divider system to the retracted state from the deployed state upon rendering a determination that a second trigger condition is met.

In addition to one or more of the above disclosed aspects of the method, controlling the divider system may include: rendering a determination that the first trigger condition is met when a pet or robot enters the elevator car; and rendering a determination that the second trigger condition is met when one or more of a passenger count, furniture, equipment or personal belongings that are larger than a predetermined size enters the elevator car.

In addition to one or more of the above disclosed aspects of the method, controlling the divider system may include: receiving data, from one or more of: a sensor onboard the elevator car or at a landing that is operational coupled to the controller; a network communicatively coupled to the controller; rendering a determination from the data of whether the first or second trigger conditions are met.

In addition to one or more of the above disclosed aspects of the method, controlling the divider system may include: receiving data transmitted from a mobile device over a network, wherein the data is indicative of, at a landing: a pet; a passenger count; furniture; equipment; or personal belongings; rendering a determination from the data of whether the first or second trigger conditions are met.

In addition to one or more of the above disclosed aspects of the method, the method may include controlling a sensor in one of the zones and a display in another one of the zones so that, when the divider system is deployed, images or video captured from the one of the zones is displayed in the other one of the zones via the display.

In addition to one or more of the above disclosed aspects of the method, the method may include preventing more than one of the front and aft doors from opening at a landing when the divider system is in the retracted state.

In addition to one or more of the above disclosed aspects of the method, the method may include controlling front and aft balanced ventilation systems of the front and aft zones when the divider system is in the deployed state.

<FIG> is a perspective view of an elevator system <NUM> including an elevator car <NUM>, a counterweight <NUM>, a tension member <NUM>, a guide rail (or rail system) <NUM>, a machine (or machine system) <NUM>, a position reference system <NUM>, and an electronic elevator controller (controller) <NUM>. The counterweight <NUM> is configured to balance a load of the elevator car <NUM> and is configured to facilitate movement of the elevator car <NUM> concurrently and in an opposite direction with respect to the counterweight <NUM> within an elevator shaft (or hoistway) <NUM> and along the guide rail <NUM>.

Embodiments may also be employed in ropeless elevator systems using self-propelled elevator cars (e.g., elevator cars equipped with friction wheels, pinch wheels or traction wheels).

Turning to <FIG>, additional aspects of the elevator system <NUM> are shown. The system <NUM> includes the elevator car <NUM> that includes a front end 200A that includes a front doorway 210A. An aft end 200B includes an aft doorway 210B. A cabin 103A extends from the front end 200A to the aft end 200B. A divider system <NUM>, or partition, is operationally coupled to the elevator car <NUM> within the cabin 103A, intermediate the front end 200A and aft end 200B. The divider system <NUM> is operational to transition between two states, including a deployed state and a retracted state. In the retracted state, the cabin 103A is undivided between the front end 200A and aft ends 200B. In the deployed state, the divider system <NUM> divides the cabin 103A into a front zone 230A accessible by the front doorway 210A and an aft zone 230B accessible by the aft doorway 210B. A cabin operating panel 232A is also shown at the front end 200A. An additional panel 232B may be provided in the aft end 200B so that elevator implements may be controlled via either operating panel <NUM> when the divider system <NUM> is in the deployed state.

As shown in <FIG> and <FIG>, in one embodiment the divider system <NUM> is positioned closer to the aft doorway 210B so that the aft zone 230B is smaller than the front zone 230B. For example, size D1 of the front zone 230A may be <NUM> to <NUM> percent of the total front to aft span D2 of the cabin 103A. This may be helpful if the front zone 230A is primarily used for passengers <NUM> and the aft zone is primarily used, e.g., for robots <NUM>, service staff <NUM>, a person with a pet, etc. In one embodiment, the divider system <NUM> is a removable partition wall.

A controller 115A is on board the elevator car <NUM> and operationally coupled to the divider system <NUM>. The controller 115A may be in the front or aft panels 232A, 232B, or in both for redundancy purposes. The controller 115A is configured to control the divider system <NUM> to transition between the deployed state and the retracted state. The controller 115A may be operationally coupled to the front doorway 220A and aft doorway 210B and configured to prevent more than one of the front and aft doorways 210A, 210B from opening at landing <NUM>, e.g., front and aft landings 238A, 238B, when the divider system <NUM> is in the retracted state. This would prevent passengers from exiting on the wrong side of the elevator car <NUM>.

Turing to <FIG> and <FIG>, in one embodiment the divider system <NUM> includes doors <NUM>, which may be pivotal doors, operationally coupled to the controller 115A. That is, the cabin 103A includes a first sidewall 240A and a second sidewall 240B extending from the front end 200A to aft end 200B. The doors <NUM> include a first door 225A operationally coupled to the first sidewall 240A and a second door 225B operationally coupled to the second sidewall 240B. The doors <NUM> may be equipped with automated swing door operators <NUM> which are operationally coupled to the controller 115A.

In one embodiment, the doors <NUM> include gaskets or seals <NUM> around their respective perimeters. The front zone 230A and aft zone 230B of the elevator car <NUM> may respectively include front and aft balanced ventilation systems 270A, 270B that are operationally controlled by the controller 115A. That is, the front zone 230A and aft zone 230B may each include dual fans to draw air into and out of the zones <NUM> when the doors <NUM> are in the deployed state. The controller 115A may be configured to operate the ventilation systems 270A, 270B when the divider system is in the deployed state. Due to the seals <NUM> and ventilation systems 270A, 270B, conditions of air within one of the zones <NUM> may be prevented from affecting the other one of the zones <NUM>. For example, odors, dust and other allergens that may be in one of the zones <NUM> may be prevented from affecting the other one of the zones <NUM>.

As shown in <FIG>, in the elevator cabin 103A, one of the zones <NUM> may be provided with an image sensor <NUM> (or first sensor, which may be a charge-coupled device or CCD used for digital imagery) and the other one of the zones <NUM> may be provided with a video display <NUM>, each of which may be operationally connected to the controller 115A. When the divider system <NUM> is deployed, the controller 115A may control the image sensor <NUM> and display <NUM> so that image information captured by the image sensor <NUM> is displayed on the display <NUM>. For example, the image sensor <NUM> may be in the second zone 230B and the display may be in the first zone 230A. With the divider system <NUM> in the deployed state, passengers in the first zone 230A would be comfortable knowing what is currently occurring, such as who or what is being transported, in the second zone 230B. Of course, both zones <NUM> may be equipped with image sensors and displays to allow passengers in each one of the zones <NUM> see displayed information about what is occurring in the other one of the zones <NUM>. Alternatively, the divider system <NUM> may have a transparent portion, such as a window, to provide a similar effect, to provide persons in one of the zones with visual access to the other one of the zones when the divider system is deployed.

In one embodiment, the controller 115A may be configured to transition the divider system <NUM> to the deployed state from the retracted state when a first trigger condition is met. For example, the controller 115A may be configured to determine that the first trigger condition is met when a pet or robot enters the elevator car <NUM>. The controller 115A may also be configured to transition the divider system <NUM> to the retracted state from the deployed state when a second trigger condition is met. The second trigger condition may be met when any of a passenger count, furniture, equipment or personal belongings that are larger than a predetermined size enters the elevator car <NUM>. Equipment may include a hospital bed, and personal belongings may include, e.g., luggage. In one embodiment, the display <NUM> may indicate that certain equipment, cargo, maintenance crew, and, e.g., passengers with pets, should be located the aft zone 230B during normal elevator usage.

Turning to <FIG> and <FIG>, in one embodiment, a second sensor <NUM> is onboard the elevator car <NUM> or at a landing 238B. The second sensor <NUM> may be operationally connected to the controller 115A. The second sensor <NUM> may be connected to the controller 115A via wireless or wired connections identified below. The controller 115A may be configured to receive sensor data from the second sensor <NUM>. From the sensor data, the controller 115A may be configured to render a determination of whether the first or second trigger conditions are met and transition the divider system <NUM> to the deployed or retracted state responsive to the determination. For example, with the sensor data, the controller 115A may be configured to identify a general size, based on overall geometry, of a passenger count, furniture, equipment, etc., exceeds the size available in a divided cabin 103A when the divider system <NUM> is deployed. For example the sensor <NUM> may utilize LIDAR (light detection and ranging). With this determination the controller 115A may retract the divider system <NUM>. In an embodiment, the sensor <NUM> may be an RFID or similar sensor that the controller 115A may utilize to identify via RF communications that a maintenance robot or hospital stretcher is going to enter the elevator car <NUM>.

Turning back to <FIG>, in one embodiment, the controller 115A may communicate over a wireless network <NUM> (identified below) and receive sensor data if the sensor <NUM> is located at the landing <NUM>. From the sensor data, the controller 115A may determine that the first or second trigger conditions will be met at the landing prior to stopping at the landing. For example, a mobile device <NUM>, such as a mobile phone, of a passenger 231A at the landing may include a software application which allows the passenger 231A to both call the elevator car <NUM> to the landing and indicate that a pet <NUM> is being brought onto the elevator car <NUM>. Alternatively, the mobile device may allow the passenger to enter passenger count or indicate whether furniture or equipment is going to enter the elevator car <NUM> at the landing. Also, a maintenance robot <NUM> may be able to communicate autonomously over the wireless network with the controller 115A to indicate it is entering at the landing 238B. With this information, the controller 115A can transition the divider system <NUM> to the deployed or retracted state when, or prior to, stopping at the landing 238B, responsive to the appropriate determination.

Turning to <FIG>, a flowchart shows method of operating an elevator system <NUM> with a controller 115A operationally connected to an elevator car <NUM>. As shown in block <NUM>, the method includes controlling a divider system <NUM> onboard the elevator car <NUM>, within a cabin 103A of the elevator car <NUM>, located between a front end <NUM> having a front doorway <NUM> and an aft end having an aft doorway <NUM>. Such controlling includes controlling the divider system <NUM> to transition between a deployed state and a retracted state. In the retracted state, the cabin 103A is undivided. In the deployed state, the divider system <NUM> divides the cabin 103A into a front zone <NUM> accessible by the front doorway <NUM> and an aft zone <NUM> accessible by the aft doorway <NUM>.

As shown in block 610A, controlling the divider system <NUM> may include controlling a first door 225A operationally coupled to a first sidewall <NUM> of the cabin 103A, and a second door 225B operationally coupled to a second sidewall <NUM> of the cabin 103A. As shown in block 610B, controlling the divider system <NUM> may include transitioning the divider system <NUM> to the deployed state from the retracted state when a first trigger condition is met. In an example, the controller determines that the first trigger condition is met when a pet or robot enters the elevator car. As further shown in block 620B, this step may include transitioning the divider system to the retracted state from the deployed state when a second trigger condition is met. In an example, the controller determines that the second trigger condition is met when one or more of a passenger count, furniture, equipment or personal belongings that are larger than a predetermined size enters the elevator cabin 103A. As shown in block 610C, controlling the divider system <NUM> may include receiving data, from a sensor <NUM> onboard the elevator car <NUM> or at a landing 238B, that is utilized for determination whether the first or second trigger conditions are met. As shown in block 610D, controlling the divider system <NUM> may include communicating over a wireless network <NUM> and receiving data from a mobile device <NUM> that is utilized for determining that the first or second trigger conditions are met at a landing 238B prior to stopping at the landing 238B.

As shown in bock <NUM>, the method may include controlling an image sensor <NUM> in one of the zones <NUM> and a display <NUM> in another one of the zones <NUM> to display images or video of the one of the zones <NUM> when the divider system <NUM> is deployed. As shown in block <NUM>, the method may include preventing more than one of the front doorway 210A and aft doorway 210B from opening at a landing <NUM> when the divider system <NUM> is in the retracted state. As shown in block <NUM>, the method may include controlling the ventilation systems 270A, 270B of the front zone 230A and aft zone 230B when the divider system <NUM> is in the deployed state.

Turning to <FIG>, generally, as shown in block <NUM>, the method is directed to controlling the divider system <NUM> onboard the elevator car <NUM>, within the cabin 103A of the elevator car <NUM>, located between the front end <NUM> having the front doorway <NUM> and the aft end having the aft doorway <NUM> to transition between the deployed state and the retracted state. In the retracted state, the cabin 103A is undivided. As indicated, in the deployed state, the divider system <NUM> divides the cabin 103A into a front zone <NUM> accessible by the front doorway <NUM> and an aft zone <NUM> accessible by the aft doorway <NUM>.

Sensor data identified herein may be obtained and processed separately, or simultaneously and stitched together, or a combination thereof, and may be processed in a raw or complied form. The sensor data may be processed on the sensor (e.g. via edge computing), by controllers identified or implicated herein, on a cloud service, or by a combination of one or more of these computing systems. The senor may communicate the data via wired or wireless transmission lines, applying one or more protocols as indicated below.

Wireless connections may apply protocols that include local area network (LAN, or WLAN for wireless LAN) protocols. LAN protocols include WiFi technology, based on the Section <NUM> standards from the Institute of Electrical and Electronics Engineers (IEEE). Other applicable protocols include Low Power WAN (LPWAN), which is a wireless wide area network (WAN) designed to allow long-range communications at a low bit rates, to enable end devices to operate for extended periods of time (years) using battery power. Long Range WAN (LoRaWAN) is one type of LPWAN maintained by the LoRa Alliance, and is a media access control (MAC) layer protocol for transferring management and application messages between a network server and application server, respectively. LAN and WAN protocols may be generally considered TCP/IP protocols (transmission control protocol/Internet protocol), used to govern the connection of computer systems to the Internet. Wireless connections may also apply protocols that include private area network (PAN) protocols. PAN protocols include, for example, Bluetooth Low Energy (BTLE), which is a wireless technology standard designed and marketed by the Bluetooth Special Interest Group (SIG) for exchanging data over short distances using short-wavelength radio waves. PAN protocols also include Zigbee, a technology based on Section <NUM>. <NUM> protocols from the IEEE, representing a suite of high-level communication protocols used to create personal area networks with small, low-power digital radios for low-power low-bandwidth needs. Such protocols also include Z-Wave, which is a wireless communications protocol supported by the Z-Wave Alliance that uses a mesh network, applying low-energy radio waves to communicate between devices such as appliances, allowing for wireless control of the same.

Wireless connections may also include radio-frequency identification (RFID) technology, used for communicating with an integrated chip (IC), e.g., on an RFID smartcard. In addition, Sub-<NUM> RF equipment operates in the ISM (industrial, scientific and medical) spectrum bands below Sub <NUM> - typically in the <NUM> - <NUM>, <NUM> and the <NUM> frequency range. This spectrum band below <NUM> is particularly useful for RF IOT (internet of things) applications. The Internet of things (IoT) describes the network of physical objects-"things"-that are embedded with sensors, software, and other technologies for the purpose of connecting and exchanging data with other devices and systems over the Internet. Other LPWAN-IOT technologies include narrowband internet of things (NB-IOT) and Category M1 internet of things (Cat M1-IOT). Wireless communications for the disclosed systems may include cellular, e.g. <NUM>/<NUM>/<NUM> (etc.). Other wireless platforms based on RFID technologies include Near-Field-Communication (NFC), which is a set of communication protocols for low-speed communications, e.g., to exchange date between electronic devices over a short distance. NFC standards are defined by the ISO/IEC (defined below), the NFC Forum and the GSMA (Global System for Mobile Communications) group. The above is not intended on limiting the scope of applicable wireless technologies.

Wired connections may include connections (cables/interfaces) under RS (recommended standard)-<NUM>, also known as the TIA/EIA-<NUM>, which is a technical standard supported by the Telecommunications Industry Association (TIA) and which originated by the Electronic Industries Alliance (EIA) that specifies electrical characteristics of a digital signaling circuit. Wired connections may also include (cables/interfaces) under the RS-<NUM> standard for serial communication transmission of data, which formally defines signals connecting between a DTE (data terminal equipment) such as a computer terminal, and a DCE (data circuit-terminating equipment or data communication equipment), such as a modem. Wired connections may also include connections (cables/interfaces) under the Modbus serial communications protocol, managed by the Modbus Organization. Modbus is a master/slave protocol designed for use with its programmable logic controllers (PLCs) and which is a commonly available means of connecting industrial electronic devices. Wireless connections may also include connectors (cables/interfaces) under the PROFibus (Process Field Bus) standard managed by PROFIBUS & PROFINET International (PI). PROFibus which is a standard for fieldbus communication in automation technology, openly published as part of IEC (International Electrotechnical Commission) <NUM>. Wired communications may also be over a Controller Area Network (CAN) bus. A CAN is a vehicle bus standard that allow microcontrollers and devices to communicate with each other in applications without a host computer. CAN is a message-based protocol released by the International Organization for Standards (ISO). The above is not intended on limiting the scope of applicable wired technologies.

When data is transmitted over a network between end processors as identified herein, the data may be transmitted in raw form or may be processed in whole or part at any one of the end processors or an intermediate processor, e.g., at a cloud service (e.g. where at least a portion of the transmission path is wireless) or other processor. The data may be parsed at any one of the processors, partially or completely processed or complied, and may then be stitched together or maintained as separate packets of information. Each processor or controller identified herein 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 identified herein may be but is not limited to a random access memory (RAM), read only memory (ROM), or other electronic, image, magnetic or any other computer readable medium.

The controller may further include, in addition to a processor and non-volatile memory, one or more input and/or output (I/O) device interface(s) that are communicatively coupled via an onboard (local) interface to communicate among other devices. The onboard interface may include, for example but not limited to, an onboard system bus, including a control bus (for inter-device communications), an address bus (for physical addressing) and a data bus (for transferring data). That is, the system bus may enable the electronic communications between the processor, memory and I/O connections. The I/O connections may also include wired connections and/or wireless connections identified herein. The onboard interface may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable electronic communications. The memory may execute programs, access data, or lookup charts, or a combination of each, in furtherance of its processing, all of which may be stored in advance or received during execution of its processes by other computing devices, e.g., via a cloud service or other network connection identified herein with other processors.

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 code based modules, e.g., computer program code (e.g., computer program product) containing instructions embodied in tangible media (e.g., non-transitory computer readable medium), such as floppy diskettes, CD ROMs, hard drives, on processor registers as firmware, or any other non-transitory computer readable medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes a device for practicing the embodiments. 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, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes a device for practicing the exemplary embodiments.

Claim 1:
An elevator system (<NUM>) comprising:
an elevator car (<NUM>), the elevator car including:
a front end (200A) that includes a front doorway (210A);
an aft end (200B) that includes an aft doorway (210B); and
a cabin (103A) extending from the front end to the aft end; and
a divider system (<NUM>) operationally coupled to the elevator car within the cabin, intermediate the front and aft ends, that is operational to transition between:
a retracted state, where the cabin is undivided;
a deployed state where the divider system divides the cabin into a front zone (230A) that is accessible by the front doorway and an aft zone (230B) that is accessible by the aft doorway; and
a controller (115A) operationally coupled to the divider system and configured to control the divider system to transition between the deployed state and the retracted state,
characterised in that the controller is onboard the elevator car.