Patent Description:
Existing elevator systems require elevator users to call a central service center when entering an elevator service request. Elevator users often do not know who to call, when to call, what to report, and fail to correctly identify the elevator error and time of the error.

<CIT> discloses a method including receiving, from a portable recording device, multiple recordings of sounds made by an elevator, analyzing the recording to detect changes in elevator operation over time and generating a notification to perform an action on an elevator.

<CIT> discloses a system for remote maintenance of an elevator using a mobile phone, in which an elevator maintenance worker connects with the system through a mobile phone.

<CIT> discloses an elevator system and a method for servicing such an elevator system. The elevator system comprises at least one door and at least one acceleration sensor mounted on the door.

According to the invention a method of interacting with an elevator system as claimed in claim <NUM> is provided.

Further embodiments of the method may include: receiving maintenance data; determining a maintenance task in response to at least one of the maintenance data and the maintenance issue; and transmitting the maintenance task to a maintenance device.

Further embodiments of the method may include activating an alarm on the maintenance device when the maintenance issue is received.

Futher emobodiments of the method may include determining a time of the issue report in response to at least one of the issue report and the performance data.

Further embodiments of the method may include determining that maintenance issue is a duplicate maintenance issue; and transmitting an alert to the user mobile device indicating the duplicate maintenance issue.

Further embodiments of the method may include: determining that maintenance issue is a duplicate maintenance issue; and transmitting an alert to the user mobile device indicating the duplicate maintenance issue.

Further embodiments of the method may include the issue report may be entered via a verbal input from a user of the user mobile device.

Further embodiments of the method may include where the issue report may be entered via selection of predefined options on a drop-down menu.

Further embodiments of the method may include where the predefined options may be selected via a verbal command.

Further embodiments of the method may include: detecting a location of the user mobile device; and determining an elevator car that triggered the issue report in response to at least one of the issue report and the location of the user mobile device.

Further embodiments of the method may include: generating on a user interface a service and maintenance screen on the user mobile device; and displaying at least one maintenance issue on the service and maintenance screen.

Further embodiments of the method may include: displaying at least one maintenance issue on the service and maintenance screen.

Further embodiments of the method may include: generating on a user interface a service and maintenance screen on the maintenance device; and displaying at least one maintenance issue on the service and maintenance screen.

Further embodiments of the method may include: receiving from the maintenance device an indication of completion of a maintenance task; and updating the maintenance database to include completion of the maintenance task.

Further embodiments of the method may include where the maintenance device is a mobile device.

Technical effects of embodiments of the present disclosure include the ability for an elevator user to report an issue with an elevator system via a mobile device.

The foregoing features and elements may be combined in various combinations within the scope of the appended claims.

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

The elevator system <NUM> may be operably connected to one or more computing devices, such as a controller <NUM>. The controller <NUM> may be configured to control dispatching operations for one or more elevator cars (e.g., elevator cars <NUM>-<NUM>, <NUM>-<NUM>. <NUM>-n) associated with the elevator system <NUM>. It is understood that the elevator system <NUM> may utilize more than one controller <NUM>, and that each controller may control a group of elevators cars <NUM>-<NUM> and <NUM>-<NUM>. Although two elevator cars <NUM>-<NUM> and <NUM>-<NUM> are shown in <FIG>, it is understood that any number of elevators cars <NUM>-n may be used in the elevator system <NUM>. The elevator cars <NUM>-<NUM> and <NUM>-<NUM> may be located in the same hoistway or in different hoistways so as to allow coordination amongst elevator cars <NUM>-<NUM> and <NUM>-<NUM> in different elevator banks serving different floors. It is understood that other components of the elevator system <NUM> (e.g., drive, counterweight, safeties, etc.) are not depicted for ease of illustration.

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

The elevator system <NUM> includes a sensor system <NUM> having one or more sensors (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. Although two sensors <NUM>-<NUM> and <NUM>-<NUM> are shown in <FIG>, it is understood that any number of sensors <NUM>-n may be used in the sensor system <NUM>. The controller <NUM> is coupled to the sensor system <NUM>. The sensor system <NUM> may include one or more sensors (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. The sensor system <NUM> may include a variety of different types of sensors (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. The sensor system <NUM> captures performance and/or other operational data <NUM> of the elevator system <NUM>. The performance data <NUM> indicates performance parameters of the elevator system <NUM>, such as for example, location, speed, voltage, vibration, acceleration, noise, , jerk, and any other performance parameter of any component of the elevator system <NUM> known to one of skill in the art.

Other sensors (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) in the sensor system may include cameras, people counters, microphones, etc. to capture information relevant to the usage of the elevator system <NUM>. Thus, the type and nature of sensors (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) within the sensor system <NUM> is not limited to the embodiments disclosed herein. The sensor system <NUM> collects performance data <NUM> regarding each elevator car (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) that may be stored in a maintenance database <NUM> operatively connected to the controller <NUM> or stored within the controller <NUM>. In one embodiment, the performance data may be stored on a building computer, remotely in the cloud, or on any other electronic storage medium.

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

Also shown in <FIG> is a maintenance device 208b. The maintenance device 208b may be a computing device such as a desktop computer. The maintenance device 208b may also be a mobile computing device that is typically carried by a person, such as, for example a phone, PDA, smart watch, tablet, laptop, etc. The maintenance device 208b may include a processor 250b, memory 252b and communication module 254b as shown in <FIG>. The processor 250b can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory 252b is an example of a non-transitory computer readable storage medium tangibly embodied in the maintenance device 208b including executable instructions stored therein, for instance, as firmware. The communication module 254b may implement one or more communication protocols as described in further detail herein. The maintenance device 208b belongs to a maintenance worker of the building <NUM>, such as, for example, maintenance personnel, building maintenance manager, and elevator service repair person.

The user mobile device 208a and maintenance device 208b may both be referred to as a device <NUM> for ease of explanation. The device <NUM> and the controller <NUM> communicate with one another. For example, the device <NUM> and the controller <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The device <NUM> and the controller <NUM> may communicate over a wireless network, such as <NUM>. 11x (WiFi), short-range radio (Bluetooth), cellular, satellite, etc. In some embodiments, the controller <NUM> may include, or be associated with (e.g., communicatively coupled to) a networked element, such as kiosk, beacon, hall call fixture, lantern, bridge, router, network node, door lock, elevator control panel, building intercom system, etc. The networked element may communicate with the device <NUM> using one or more communication protocols or standards. For example, the networked element may communicate with the device <NUM> using near field communications (NFC). In other embodiments, the controller <NUM> may establish communication with a device <NUM> that is outside of the building <NUM>. This connection may be established with various technologies including GPS, triangulation, or signal strength detection, by way of non-limiting example. In example embodiments, the device <NUM> communicates with the controller <NUM> over multiple independent wired and/or wireless networks. Embodiments are intended to cover a wide variety of types of communication between the device <NUM> and controller <NUM>, and embodiments are not limited to the examples provided in this disclosure. Communication between the device <NUM> and the controller <NUM> will allow the controller <NUM> to determine the location of the device <NUM> in relation to the elevator system <NUM> and/or the door system <NUM>. Knowing the relative location of the device <NUM> will allow the controller <NUM> to determine what elevator car (e.g., <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) may have caused a user to submit a maintenance request.

Embodiments generate a user interface on the device <NUM> through a maintenance application 255a, 255b. The maintenance application 255a may be used for user of the elevator system to report maintenance issues regarding the elevator system <NUM> in an issue report <NUM>. For example, a resident may report that they heard a squeaking in elevator car <NUM>-<NUM>.

<FIG> depict an example user interface <NUM> on user mobile device 208a. Referring to <FIG> with continued reference to <FIG>, when the user mobile device 208a launches the maintenance application 255a, an elevator service and maintenance screen <NUM> may be presented as shown in <FIG>. The maintenance application 255a may display an elevator alert <NUM> and an elevator notice <NUM>. The elevator alert <NUM> may indicate maintenance issues <NUM> that have been reported in the elevator system <NUM>. The elevator notices <NUM> may indicate scheduled maintenance on the elevator system <NUM>.

In order to report an issue with the elevator system <NUM>, a user can select the "Report an Issue" <NUM> button, which will prompt the user interface <NUM> to generate the maintenance screen <NUM> shown in <FIG>. As seen in <FIG>, the service and maintenance screen <NUM> includes a text input section <NUM> where an issue with the elevator system <NUM> may be reported. In an embodiment, the issue report <NUM> may be manually typed into a text input section <NUM> by a user of the user mobile device 208a. The text input section <NUM> is not intended to be limiting as other data input methods may be used, such as, for example drop-down menus or icons to display multiple predefined issue options. The drop-down menus or icons may include issue options for elevator cars and may be categorized with submenu to guide a user in selecting the appropriate issue. The issue options may be a static list of issues and/or dynamic list of issues built using commonly reported issues within the building itself. In an embodiment, the issue report <NUM> may be entered via selection of predefined issue options on the drop-down menu. In an embodiment, the predefined options may be selected via a verbal command. In another embodiment, the issue report <NUM> may be entered via a verbal input from a user of the user mobile device 208a. The user mobile device 208a may also contain an accelerometer (not shown) located within the user mobile device 208a and configured to collect accelerometer data. In another embodiment, the issue report <NUM> is generated in response to the accelerometer data. For example, if the accelerometer detects an unusual jerk of the elevator car (e. g, <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) then an issue report <NUM> may be automatically generated by the maintenance application 255a detailing the jerk.

Also, included on the service and maintenance screen <NUM> is a date entry block <NUM> where the date that the issue occurred may be entered by the user of the user mobile device 208a. In one embodiment, the date and tome of the report may be automatically entered and/or stored by the maintenance application 255a. Additionally, the service and maintenance screen <NUM> may include a known issues section <NUM> to display issues with the elevator system <NUM> that are known and are currently being worked. Advantageously, a known issue section <NUM> will help avoid duplicity in issue reports <NUM> that results in wasted time for both the user and the maintenance personnel. Once a user of the user mobile device has completed entry of their issue in the text input section <NUM>, the user may select a "Send to Maintenance" button <NUM> to transmit the issue report <NUM> to the controller <NUM> and eventually maintenance personnel who may view the issue on the maintenance device 208b.

Referring now to <FIG>, while referencing components of <FIG>. <FIG> shows a flow chart of method <NUM> of interacting with an elevator system, in accordance with an embodiment of the disclosure. At block <NUM>, a sensor system <NUM> detects performance data <NUM> for an elevator system <NUM>. The elevator system <NUM> may include one or more elevator cars (e. g, <NUM>-<NUM>, <NUM>-<NUM>,. The sensor system <NUM> may include one or more sensors (e. g, <NUM>-<NUM>, <NUM>-<NUM>,. The performance data <NUM> indicates performance parameters of the elevator system <NUM>, such as for example, location, speed, voltage, vibration, acceleration, noise, deceleration, jerk, and any other performance parameter of any component of the elevator system <NUM> known to one of skill in the art. Abnormalities in the performance data <NUM> may indicate a need for maintenance and issue reports <NUM> from users of the elevator system <NUM> may confirm the need for maintenance. In an embodiment, the sensor system <NUM> collects performance data <NUM> continuously. In another embodiment, the sensor system <NUM> collects performance data <NUM> at predefined intervals and/or when an issue report <NUM> is received.

At block <NUM>, the controller <NUM> receives an issue report <NUM> from a user mobile device 208a. As mentioned above, generated on a user interface <NUM> is a service and maintenance screen <NUM> on the user mobile device 208a. The service and maintenance screen <NUM> is configured to allow entry of the issue report <NUM>. In an embodiment, the issue report <NUM> may be manually typed into a text input section <NUM>. In another embodiment, the issue report <NUM> may be entered via a verbal input from a user of the user mobile device 208a. The user mobile device 208a may also contain an accelerometer (not shown) located within the user mobile device 208a and configured to collect accelerometer data. In another embodiment, the issue report <NUM> is generated in response to the accelerometer data. For example, if the accelerometer detects an unusual jerk of the elevator car (e. g, <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) then an issue report <NUM> may automatically be generated by the maintenance application 255a detailing the jerk.

At block <NUM>, the controller <NUM> determines a maintenance issue <NUM> of the elevator system <NUM> in response to at least one of the issue report <NUM> and the performance data <NUM>. For example, the maintenance issue <NUM> may be that the guide wheel of an elevator car is squeaking. The controller <NUM> may also determine a maintenance task in response to at least one of the maintenance data <NUM> and the maintenance issue <NUM>. The maintenance task may be transmitted to a maintenance device 208b. In an example, the maintenance task may be add a lubricant to guide wheels of the elevator car to decrease squeaking. The controller <NUM> may also receive maintenance data from a maintenance device 208b. For example, after maintenance personnel has performed a maintenance activity on the elevator system <NUM>, the maintenance data <NUM> may be entered in to the maintenance application 255b on the maintenance device 208b and sent to the controller <NUM> to be stored in the maintenance database <NUM>.

In an embodiment, the controller <NUM> may also determine a time of the issue report <NUM> in response to at least one of the issue report <NUM> and the performance data <NUM>. In one example, the controller <NUM> correlates the issue report <NUM> with performance data <NUM> in order to determine a time of the issue report <NUM>. In another example, a location of the user mobile device 208a may be tracked in order to determine what elevator car (e. g, <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) the user mobile device 208a has entered and at what time, thus performance data <NUM> at that same time and elevator car (e. g, <NUM>-<NUM>, <NUM>-<NUM>,. <NUM>-n) may determine the maintenance issue <NUM>. In another embodiment, the controller <NUM> may also determine that the maintenance issue <NUM> is a duplicate maintenance issue, meaning that the maintenance issue <NUM> has already been reported by another issue report <NUM>. If the maintenance issue <NUM> is a duplicate maintenance issue, then an alert to the user mobile device 208a indicating the duplicate maintenance issue.

At block <NUM>, the controller <NUM> transmits the maintenance issue <NUM> to a maintenance device 208b. In an embodiment, an alarm is activated on the maintenance device 208b when the maintenance issue is received. The alarm may also be sent to a central computer/cloud, a maintenance dispatcher and/or the building owner. The alarm may be audible and/or visual. Generated on a user interface <NUM> is a service and maintenance screen <NUM> on the maintenance device 208b. The service and maintenance screen <NUM> being configured to display at least one maintenance issue <NUM> on the maintenance device 208b. Further, the maintenance issue <NUM> may also be sent to the user mobile device 208a. Generated on a user interface <NUM> is a service and maintenance screen <NUM> on the user mobile device 208a. The service and maintenance screen <NUM> being configured to display at least one maintenance issue <NUM> on the maintenance device 208b.

While the present disclosure has been described with reference to an exemplary embodiment or embodiments, it will be understood by those skilled in the art that various changes may be within the scope of the appended claims.

Claim 1:
A method of interacting with an elevator system (<NUM>) comprising a sensor system (<NUM>), the method comprising:
detecting, using the sensor system (<NUM>), performance data (<NUM>) for the elevator system (<NUM>), the elevator system (<NUM>) including one or more elevator cars;
generating on a user interface a service and maintenance screen (<NUM>) on a user mobile device (208a), through a maintenance application (255a, <NUM>) for a user of the elevator system to report maintenance issues regarding the elevator system (<NUM>) in an issue report (<NUM>), and entering the issue report on the service and maintenance screen (<NUM>), or
collecting accelerometer data using an accelerometer located in the user mobile device (208a) and generating an issue report in response to the accelerometer data;
a controller (<NUM>) receiving the issue report from the user mobile device (208a);
the controller (<NUM>) determining a maintenance issue of the elevator system (<NUM>) in response to at least one of the issue report and the performance data (<NUM>); and
the controller (<NUM>) transmitting the maintenance issue to a maintenance device (208b) belonging to a maintenance worker of the elevator system.