US10392224B2 - Elevator control with mobile devices - Google Patents

Elevator control with mobile devices Download PDF

Info

Publication number
US10392224B2
US10392224B2 US15/103,109 US201315103109A US10392224B2 US 10392224 B2 US10392224 B2 US 10392224B2 US 201315103109 A US201315103109 A US 201315103109A US 10392224 B2 US10392224 B2 US 10392224B2
Authority
US
United States
Prior art keywords
mobile device
service
identifier
elevator
elevator car
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US15/103,109
Other languages
English (en)
Other versions
US20160311647A1 (en
Inventor
Eric C. Peterson
Paul A. Simcik
Ashley Chapman
Luis C. Encinas Carreno
Bradley Armand Scoville
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Otis Elevator Co
Original Assignee
Otis Elevator Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Otis Elevator Co filed Critical Otis Elevator Co
Assigned to OTIS ELEVATOR COMPANY reassignment OTIS ELEVATOR COMPANY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHAPMAN, Ashley, ENCINAS CARRENO, LUIS C., PETERSON, ERIC C., SCOVILLE, Bradley Armand, SIMCIK, PAUL A.
Publication of US20160311647A1 publication Critical patent/US20160311647A1/en
Application granted granted Critical
Publication of US10392224B2 publication Critical patent/US10392224B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B66HOISTING; LIFTING; HAULING
    • B66BELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00Control systems of elevators in general
    • B66B1/34Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/46Adaptations of switches or switchgear
    • B66B1/468Call registering systems
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B66HOISTING; LIFTING; HAULING
    • B66BELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00Control systems of elevators in general
    • B66B1/34Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/3415Control system configuration and the data transmission or communication within the control system
    • B66B1/3446Data transmission or communication within the control system
    • B66B1/3461Data transmission or communication within the control system between the elevator control system and remote or mobile stations
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B66HOISTING; LIFTING; HAULING
    • B66BELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00Control systems of elevators in general
    • B66B1/34Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/46Adaptations of switches or switchgear
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B66HOISTING; LIFTING; HAULING
    • B66BELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B5/00Applications of checking, fault-correcting, or safety devices in elevators
    • B66B5/0006Monitoring devices or performance analysers
    • B66B5/0012Devices monitoring the users of the elevator system
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B66HOISTING; LIFTING; HAULING
    • B66BELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B2201/00Aspects of control systems of elevators
    • B66B2201/40Details of the change of control mode
    • B66B2201/402Details of the change of control mode by historical, statistical or predicted traffic data, e.g. by learning
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B66HOISTING; LIFTING; HAULING
    • B66BELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B2201/00Aspects of control systems of elevators
    • B66B2201/40Details of the change of control mode
    • B66B2201/46Switches or switchgear
    • B66B2201/4607Call registering systems
    • B66B2201/4653Call registering systems wherein the call is registered using portable devices

Definitions

  • an elevator system recognizes the existence of individual users planning to use the elevator in order to respond to demand or requests for service. Buttons, keypad devices, and touchscreen devices may be used for entering a request for elevator service.
  • the elevator system For an elevator system that utilizes a two-button (e.g., up or down button) configuration, the elevator system only recognizes that there is a request for service without any indication as to the number of people waiting to use the elevator.
  • the elevator system recognizes the count of requests made by individual users or passengers who interact with the keypad/touchscreen device. In either case/configuration, a user/passenger engages in an affirmative action to request elevator service.
  • an elevator system does not have a reliable count of users or passengers requesting service. For example, when people travel in groups it is common for a single person to enter a request for service. In a building where more than one elevator car or elevator system is available for potential use, an inadequate number of car calls may be made where the count of users/passengers needing elevator service exceeds the capacity of a car. This can result in an overloading of an elevator car, a rush of passengers into the elevator car, or a situation where not everyone can enter the elevator car, thus requiring an additional request for an elevator car and an additional waiting period. Additionally, access to elevator request devices may be limited, such as during peak use periods (e.g., morning or evening rush period). This creates situations where a user is delayed in making his/her individual request or being able to confirm if a hall button in his/her intended direction of travel has already been pressed.
  • peak use periods e.g., morning or evening rush period
  • An embodiment is directed to a method comprising: receiving, by a computing device comprising a processor, an identifier associated with a mobile device based on a passive transmission of the identifier by the mobile device, and based on the receipt of the identifier, scheduling at least one service associated with an elevator system based on an anticipated demand for the at least one service.
  • An embodiment is directed to an apparatus comprising: memory having instructions stored thereon that, when executed, cause the apparatus to: receive an identifier associated with a mobile device based on a passive transmission of the identifier by the mobile device, and based on the receipt of the identifier, schedule at least one service associated with an elevator system based on an anticipated demand for the at least one service.
  • An embodiment is directed to a conveyance system comprising: a gateway configured to receive a plurality of unique identifiers associated with a corresponding plurality of mobile devices when the mobile devices are within a threshold distance of the gateway based on a passive transmission of the identifiers by the mobile devices, and a controller coupled to the gateway, wherein the controller is configured to schedule at least one service associated with the conveyance system based on an anticipated demand for the at least one service, wherein the anticipated demand is based on a count of the identifiers.
  • FIG. 1 is a schematic block diagram illustrating an exemplary computing system
  • FIG. 2 illustrates a block diagram of an exemplary elevator system
  • FIG. 3 illustrates a flow chart of an exemplary method.
  • Exemplary embodiments of apparatuses, systems, and methods are described for recognizing individuals in a location (e.g., an elevator landing area) by monitoring active mobile devices (e.g., mobile phones).
  • an identifier associated with a mobile device may be obtained and used to count the number of users waiting for service at the location. The number or count of users waiting for service may be based on a passive or hands-free technique, such that the users might not have to take any specific or affirmative action to have a request for elevator service associated with them (other than turning on the mobile device or enabling an application on the mobile device).
  • resources may be scheduled (e.g., elevator car calls may be made) based on the count of users or anticipated demand.
  • the system 100 is shown as including a memory 102 .
  • the memory 102 may store executable instructions.
  • the executable instructions may be stored or organized in any manner and at any level of abstraction, such as in connection with one or more applications, processes, routines, procedures, methods, etc. As an example, at least a portion of the instructions are shown in FIG. 1 as being associated with a first program 104 a and a second program 104 b.
  • the memory 102 may store data 106 .
  • the data 106 may include registration data, elevator car data, a device identifier, or any other type of data.
  • the instructions stored in the memory 102 may be executed by one or more processors, such as a processor 108 .
  • the processor 108 may be operative on the data 106 .
  • the processor 108 may be coupled to one or more input/output (I/O) devices 110 .
  • the I/O device(s) 110 may include one or more of a keyboard or keypad, a touchscreen or touch panel, a display screen, a microphone, a speaker, a mouse, a button, a remote control, a joystick, a printer, a telephone or mobile device (e.g., a smartphone), a sensor, etc.
  • the I/O device(s) 110 may be configured to provide an interface to allow a user to interact with the system 100 .
  • the system 200 may be implemented in connection with one or more components, devices, or other systems (e.g., system 100 ).
  • the system 200 may be associated with an elevator system.
  • the system 200 may be used to detect the presence of a user, or more specifically, a mobile device. The detected presence of the user may be used as a basis for determining a demand for elevator service.
  • the system 200 may include a mobile device 202 , such as a phone, a laptop, a tablet, etc.
  • the mobile device 202 may include an identifier that may distinguish the mobile device 202 from other devices.
  • the identifier may be a media access control (MAC) address, a BLUETOOTH wireless technology Address, an International Mobile Station Equipment Identity (IMEI), an International Mobile Subscriber Identity (IMSI), etc.
  • the mobile device 202 may be associated with (e.g., owned by) a particular user. While a single mobile device 202 is shown in FIG. 2 , more than one mobile device 202 may be present in some embodiments.
  • the system 200 may include a gateway 204 .
  • the gateway 204 may include one or more of a router (e.g., wireless router), an access point, a receiver (e.g., a WiFi receiver), etc.
  • the gateway 204 may be located inside an elevator car (e.g., elevator car(s) 208 ), in proximity to an elevator landing, at points of egress to a building, and/or outside of the building. While a single gateway 204 is shown in FIG. 2 , more than one gateway 204 may be present in some embodiments.
  • the gateway 204 may be configured to communicate with the mobile device 202 .
  • the gateway 204 may obtain the identifier associated with the mobile device 202 as part of the communication.
  • the gateway 204 may communicate the presence of the user or the mobile device 202 to a controller 206 .
  • the controller 206 may generate one or more commands to facilitate elevator service for a user associated with the mobile device 202 .
  • the commands may be used to direct the one or more elevator cars 208 .
  • the commands may be based on a profile associated with the user or the mobile device 202 as described in further detail below.
  • the systems 100 and 200 are illustrative. In some embodiments, one or more of the entities may be optional. In some embodiments, additional entities not shown may be included. For example, in some embodiments the systems 100 and/or 200 may be associated with one or more networks, such as one or more computer or telephone networks. In some embodiments, the entities may be arranged or organized in a manner different from what is shown in FIGS. 1-2 .
  • one or more gateways 204 may be in proximity to an elevator landing, at points of egress to a building, and/or outside of the building. Placing the gateway(s) in such locations may be used to schedule or place elevator car calls based on communication between the gateway(s) 204 and mobile device(s) 202 . For example, a count of mobile device(s) 202 that are in communication with (e.g., proximate to) the gateway(s) 204 may be used as a basis for predicting elevator service demand, such that an appropriate count of elevator cars can be summoned to a particular floor or landing. Such communication between the mobile device(s) 202 and the gateway(s) 204 may be used to reduce the impact of a large number of users or crowds entering a building at once or leaving the building (or a particular floor/landing) at the same time.
  • the system may store data pertaining to building traffic in order to schedule appropriate elevator services to match anticipated demand.
  • Such services may include commanding elevator cars 208 to particular floors or landings, potentially as a function of a day of the week or the time of day.
  • a gateway 204 may be located inside an elevator car 208 . Locating a gateway 204 inside the elevator car 208 may be used as a basis for confirming that a user or the mobile device 202 has actually entered the elevator car 208 , thereby fulfilling the (presumed) service request. If the user did not enter the elevator car 208 , a subsequent car call or request for service may be entered by, e.g., the controller 206 on behalf of the user/mobile device 202 . Such a subsequent car call may be used if, e.g., the user elected not to enter the first arriving elevator car 208 that was available to take the user to the user's destination floor/landing.
  • a timeout or counter may be used such that if a user fails to enter ‘n’ number of cars 208 in a given period of time, future car calls/requests will not be entered for the user (for a specified period of time). In this manner, the elevator system can avoid allocating elevator cars 208 to a user/mobile device 202 that has demonstrated behavior suggesting a lack of intention to use the elevator system.
  • a profile may be associated with a particular mobile device 202 .
  • the profile may be associated with the particular mobile device 202 based on the identifier associated with the mobile device 202 .
  • the profile may be generated or populated on the basis of a user of the mobile device 202 completing a registration process.
  • the registration process may be based on the use of a website or kiosk.
  • the registration process may be conducted remotely from a building housing an elevator or the registration process may be conducted in connection with the mobile device 202 communicating with, e.g., the gateway 204 or the controller 206 .
  • a suggested or default destination may be entered in the profile, such that when the mobile device 202 associated with that user is in communication with a gateway 204 a default destination floor or landing may be selected for the user.
  • the default destination floor may be selected as a function of the day of the week, the time of day, other user preferences, etc.
  • the default destination floor or other parameters associated with a profile may be presented to the user, potentially as a request sent to the mobile device 202 that requests the user to register the mobile device 202 or the profile.
  • the user may have the ability to override the default destination floor or other parameters, either permanently (e.g., as part of an update to the profile or as part of the registration process) or on, e.g., a one-time basis.
  • the profile may include a nickname for a user of a particular mobile device 202 .
  • the nickname may be selected by the user (e.g., as part of a registration process) or may be assigned and provided to the user by a service provider or operator.
  • a database of nicknames may be maintained by the service provider or operator to ensure that each nickname is unique or is only used once.
  • the nickname may be presented on a sign or audio device located proximate to a plurality of elevator cars. Data presented by the sign or audio device may indicate that the user associated with the nickname should enter a particular elevator car for elevator service. In this manner, the elevator system may make decisions to maximize the efficiency or use of the elevator system (e.g., minimizing power consumed, minimizing the number of stops at floors or landings, etc.).
  • the user's actual name or identity may be concealed or not revealed, allowing the user to know which elevator car to enter while still allowing the user to remain anonymous.
  • the user might not need to take the mobile device 202 out of, e.g., her pocket, backpack, briefcase, purse, etc.
  • feedback or directives may be provided to the mobile device 202 .
  • data may be provided to the mobile device 202 that directs a user of the mobile device 202 to enter a particular elevator car 208 for elevator service.
  • FIG. 3 a flowchart of a method 300 is shown that may be used in connection with one or more entities, devices or systems, such as those described herein.
  • the method 300 may be used to provide a passive or hands-free experience in obtaining elevator service.
  • profile information may be obtained.
  • the profile information may be obtained as part of a registration process.
  • the profile information may include one or more of: an identifier associated with a mobile device, a nickname associated with the mobile device or a user of the mobile device, preferences associated with a user of the mobile device, patterns of usage of an elevator system, etc.
  • a determination may be made that one or more mobile devices are proximate to (e.g., within a threshold distance of) an elevator system.
  • the determination may be based on a communication of identifier(s) associated with the mobile device(s) to one or more gateways.
  • the gateway(s) may receive the identifier(s) from the mobile device(s).
  • one or more services may be scheduled for user(s) of the mobile device(s) based on the determination of block 304 .
  • a car call may be made for one or more elevator cars.
  • the service(s) may be selected based on the profile of block 302 .
  • the service(s) may be scheduled based on anticipated demand (e.g., number of mobile devices in proximity to the elevator system plus any affirmative requests for service).
  • a determination may be made whether a user or mobile device exits an elevator at an appropriate floor or destination.
  • a notification may be provided when a user or mobile device does not get out at the right floor or gets off at the wrong floor.
  • the notification may be provided to the user or the mobile device, a building owner, security personnel, etc.
  • the notification may be communicated to a number of entities or devices.
  • the notification may take one or more forms, such as a sound/auditory message or alert, a displayed message or graphic, etc.
  • the notification may be provided in an elevator car, in a hallway proximate to the elevator car or hoistway, or in any other location.
  • the method 300 is illustrative. In some embodiments, one or more of the blocks or operations (or portions thereof) may be optional. In some embodiments, additional operations not shown may be included. In some embodiments, the operations may execute in an order or sequence different from what is shown.
  • elevator cars may be allocated or re-allocated in order to meet anticipated demand for service.
  • a count of users that are likely to need elevator service may be based on one or more identifiers that are transmitted by mobile devices.
  • an explicit request for elevator service might not be entered.
  • a request for elevator service may be inferred based on a transmission of an identifier associated with a mobile device.
  • existing infrastructure e.g., elevator system infrastructure
  • a number of elevator systems located in a number of buildings may be configured to detect the presence of the same mobile device. Accordingly, a user may use the same mobile device to access resources associated with various elevator systems.
  • aspects of the disclosure may be used to place an elevator car call on behalf of a user. If a profile (e.g., a registered profile) is available, a destination floor or landing may be selected for a user.
  • a profile e.g., a registered profile
  • aspects of the disclosure may be used to maintain a user's privacy or anonymity. For example, receipt of a mobile device identifier or indicator by an elevator system allows the elevator system to schedule resources without necessarily knowing the identity of the user of the mobile device. Furthermore, customized services can be provided to the user in connection with a profile, again without requiring specific knowledge as to the identity of the user of the mobile device.
  • aspects of the disclosure may be used in connection with one or more data mining applications. For example, patterns of elevator usage may be analyzed to suggest alternative times that users could consume elevator resources. Advertising opportunities may be available. For example, if a user profile indicates that the user likes to drink coffee, coupons for free coffee may be provided to the user as an incentive to utilize the elevator during off-peak times or periods.
  • various functions or acts may take place at a given location and/or in connection with the operation of one or more apparatuses, systems, or devices. For example, in some embodiments, a portion of a given function or act may be performed at a first device or location, and the remainder of the function or act may be performed at one or more additional devices or locations.
  • an apparatus or system may include one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus or system to perform one or more methodological acts as described herein.
  • digital logic circuits or devices e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), etc.
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • Various mechanical components known to those of skill in the art may be used in some embodiments.
  • Embodiments may be implemented as one or more apparatuses, systems, and/or methods.
  • instructions may be stored on one or more computer program products or computer-readable media, such as a transitory and/or non-transitory computer-readable medium.
  • the instructions when executed, may cause an entity (e.g., an apparatus or system) to perform one or more methodological acts as described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Elevator Control (AREA)
  • Indicating And Signalling Devices For Elevators (AREA)
US15/103,109 2013-12-17 2013-12-17 Elevator control with mobile devices Active 2035-05-17 US10392224B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/075615 WO2015094178A1 (en) 2013-12-17 2013-12-17 Elevator control with mobile devices

Publications (2)

Publication Number Publication Date
US20160311647A1 US20160311647A1 (en) 2016-10-27
US10392224B2 true US10392224B2 (en) 2019-08-27

Family

ID=53403301

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/103,109 Active 2035-05-17 US10392224B2 (en) 2013-12-17 2013-12-17 Elevator control with mobile devices

Country Status (4)

Country Link
US (1) US10392224B2 (de)
EP (1) EP3083465B1 (de)
CN (1) CN105829223B (de)
WO (1) WO2015094178A1 (de)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190161317A1 (en) * 2017-11-30 2019-05-30 Otis Elevator Company Sequence triggering for automatic calls & multi-segment elevator trips
US20190161316A1 (en) * 2017-11-30 2019-05-30 Otis Elevator Company Sequence triggering for automatic calls & multi-segment elevator trips
US20190292010A1 (en) * 2018-03-23 2019-09-26 Otis Elevator Company Wireless signal device, system and method for elevator service request
US10990071B2 (en) * 2017-11-07 2021-04-27 Kone Corporation Managing power demand of a plurality of passenger transport installations

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016094491A1 (en) * 2014-12-12 2016-06-16 Otis Elevator Company Elevator route selection system
CN108349687B (zh) 2015-11-06 2020-06-09 奥的斯电梯公司 用于通过输入电梯呼叫来起始电梯服务的系统和方法
EP3439998B1 (de) 2016-04-06 2022-01-12 Otis Elevator Company Zustandsverwaltung einer mobilen vorrichtung und lagebestimmung
EP3440000B1 (de) 2016-04-06 2021-01-06 Otis Elevator Company Voreingestellte aufzugsrufe
US10486938B2 (en) 2016-10-28 2019-11-26 Otis Elevator Company Elevator service request using user device
WO2018138234A1 (en) * 2017-01-30 2018-08-02 Inventio Ag Electronic elevator guard device and method for monitoring a set of integrity states of a plurality of elevator features
US10358318B2 (en) 2017-04-10 2019-07-23 International Business Machines Corporation Predictive analytics to determine elevator path and staging
EP3412613B1 (de) * 2017-06-07 2024-03-13 Otis Elevator Company Handdetektion für aufzugsbetrieb
CN109110593B (zh) 2017-06-22 2022-04-26 奥的斯电梯公司 用于电梯系统的通信系统和通信方法
CN109279461B (zh) * 2017-07-20 2022-05-27 奥的斯电梯公司 电梯轿厢中的乘客人流的无缝跟踪
CN109969877B (zh) * 2017-12-27 2023-02-07 奥的斯电梯公司 自动呼梯系统和自动呼梯控制方法
CN109969878A (zh) * 2017-12-27 2019-07-05 奥的斯电梯公司 自动呼梯请求系统中的非正常呼梯请求的确定
CN110228734B (zh) * 2018-03-06 2022-11-01 奥的斯电梯公司 电梯服务请求的授权管理
CN110228735B (zh) * 2018-03-06 2022-08-02 奥的斯电梯公司 电梯服务请求和电梯服务请求的离线认证
CN110228733B (zh) 2018-03-06 2022-08-09 奥的斯电梯公司 电梯服务请求的授权管理和授权请求
US11040850B2 (en) 2018-03-27 2021-06-22 Otis Elevator Company Seamless elevator call from mobile device application
US11072515B2 (en) 2018-03-27 2021-07-27 Otis Elevator Company Automated elevator maintenance mode initiation
EP3556703B1 (de) * 2018-04-19 2022-06-01 Otis Elevator Company E-registrierung für einen aufzug
CN110407043B (zh) 2018-04-26 2023-01-13 奥的斯电梯公司 用于电梯服务请求的通信
US11919742B2 (en) 2018-06-19 2024-03-05 Otis Elevator Company Mobile car operating panel
US11153004B2 (en) * 2018-06-21 2021-10-19 Otis Elevator Company Conveyance system data transfer
CN110626891B (zh) * 2018-06-25 2023-09-05 奥的斯电梯公司 用于改进的电梯调度的系统和方法
US11999588B2 (en) 2018-07-25 2024-06-04 Otis Elevator Company Dynamic car assignment process
US20200122965A1 (en) * 2018-10-19 2020-04-23 Otis Elevator Company System for providing elevator service
US20200122958A1 (en) * 2018-10-22 2020-04-23 Otis Elevator Company System and method for prioritizing service to remote elevator calls based on proximity to elevator lobby
US20200130996A1 (en) * 2018-10-27 2020-04-30 Otis Elevator Company System and method for assigning elevator service based on passenger usage
US12030741B2 (en) * 2019-03-25 2024-07-09 Otis Elevator Company Processing multiple elevator service requests
AU2020247061B2 (en) * 2019-03-28 2023-07-06 Inventio Ag Method and system for commissioning of a communication gateway
CN112533852A (zh) * 2019-07-12 2021-03-19 开利公司 用于自动呼叫一个或多个电梯的系统和方法
US11897726B2 (en) * 2019-09-19 2024-02-13 Otis Elevator Company Communications system for conveyance system
US20210395038A1 (en) * 2020-06-23 2021-12-23 Otis Elevator Company Travel-speed based predictive dispatching

Citations (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6109396A (en) * 1998-11-09 2000-08-29 Otis Elevator Company Remote elevator call placement with provisional call verification
US6202799B1 (en) * 1999-07-02 2001-03-20 Otis Elevator Company Processing and registering automatic elevator cell destinations
US6209685B1 (en) * 1999-06-04 2001-04-03 Otis Elevator Company Selective, automatic elevator call registering system
US6382363B1 (en) * 1999-01-29 2002-05-07 Inventio Ag Method for preselecting a destination floor in an elevator installation
US6397976B1 (en) * 1999-10-04 2002-06-04 Otis Elevator Company Automatic elevator destination call processing
US6868945B2 (en) 2000-05-01 2005-03-22 Inventio Ag Method for controlling an elevator utilizing a mobile telephone
US7140469B2 (en) * 2003-03-20 2006-11-28 Inventio Ag Three-dimensional monitoring in the area of an elevator by means of a three-dimensional sensor
CN101065310A (zh) 2005-09-26 2007-10-31 三菱电机株式会社 电梯控制装置
US7347303B2 (en) 2004-06-28 2008-03-25 Kone Corporation Method and apparatus for generating elevator calls
EP1984286A1 (de) 2006-02-13 2008-10-29 Kone Corporation Kommunikationssystem
US7552800B2 (en) * 2005-08-31 2009-06-30 Kone Corporation Method and call system for remotely communicating with an elevator in prediction of a passenger
US20090294221A1 (en) 2004-06-29 2009-12-03 Zuhair Bahjat Programmable adaptable touch screen elevator devices
US7823700B2 (en) * 2007-07-20 2010-11-02 International Business Machines Corporation User identification enabled elevator control method and system
WO2011009358A1 (zh) 2009-07-20 2011-01-27 杭州优迈科技有限公司 被动式无线远程电梯召唤的操控系统及控制方法
US7882938B2 (en) * 2005-04-12 2011-02-08 Otis Elevator Company Elevator system control providing specialized service features to facilitate a passenger accessing an assigned elevator car
US8020672B2 (en) * 2006-01-12 2011-09-20 Otis Elevator Company Video aided system for elevator control
US8047333B2 (en) * 2005-08-04 2011-11-01 Inventio Ag Method and elevator installation for user selection of an elevator
WO2011141627A1 (en) 2010-05-10 2011-11-17 Kone Corporation Method and system for limiting access rights
US8061485B2 (en) * 2005-09-30 2011-11-22 Inventio Ag Elevator installation operating method for transporting elevator users
US20120090922A1 (en) 2009-06-03 2012-04-19 Kone Corporation Elevator system
WO2012059639A1 (en) 2010-11-03 2012-05-10 Kone Corporation Elevator system
US20120252498A1 (en) 2009-09-30 2012-10-04 Telecom Italia S.P.A. Method and system for notifying proximity of mobile communication terminals users
US8960373B2 (en) * 2010-08-19 2015-02-24 Kone Corporation Elevator having passenger flow management system
US9284158B2 (en) * 2011-12-15 2016-03-15 Kone Corporation Elevator system
US9323232B2 (en) * 2012-03-13 2016-04-26 Nokia Technologies Oy Transportion remote call system based on passenger geo-routines
US9481548B2 (en) * 2013-10-09 2016-11-01 King Fahd University Of Petroleum And Minerals Sensor-based elevator system and method using the same
US9580272B2 (en) * 2011-03-29 2017-02-28 Inventio Ag User guidance with mobile electronic devices
US9834408B2 (en) * 2014-01-28 2017-12-05 Mitsubishi Electric Corporation Elevator call registering system

Patent Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6109396A (en) * 1998-11-09 2000-08-29 Otis Elevator Company Remote elevator call placement with provisional call verification
US6382363B1 (en) * 1999-01-29 2002-05-07 Inventio Ag Method for preselecting a destination floor in an elevator installation
US6209685B1 (en) * 1999-06-04 2001-04-03 Otis Elevator Company Selective, automatic elevator call registering system
US6202799B1 (en) * 1999-07-02 2001-03-20 Otis Elevator Company Processing and registering automatic elevator cell destinations
US6397976B1 (en) * 1999-10-04 2002-06-04 Otis Elevator Company Automatic elevator destination call processing
US6868945B2 (en) 2000-05-01 2005-03-22 Inventio Ag Method for controlling an elevator utilizing a mobile telephone
US7140469B2 (en) * 2003-03-20 2006-11-28 Inventio Ag Three-dimensional monitoring in the area of an elevator by means of a three-dimensional sensor
US7347303B2 (en) 2004-06-28 2008-03-25 Kone Corporation Method and apparatus for generating elevator calls
US20090294221A1 (en) 2004-06-29 2009-12-03 Zuhair Bahjat Programmable adaptable touch screen elevator devices
US7882938B2 (en) * 2005-04-12 2011-02-08 Otis Elevator Company Elevator system control providing specialized service features to facilitate a passenger accessing an assigned elevator car
US8047333B2 (en) * 2005-08-04 2011-11-01 Inventio Ag Method and elevator installation for user selection of an elevator
US20120037461A1 (en) 2005-08-04 2012-02-16 Lukas Finschi User selection of an elevator
US8348021B2 (en) * 2005-08-04 2013-01-08 Inventio Ag User selection of an elevator
US7552800B2 (en) * 2005-08-31 2009-06-30 Kone Corporation Method and call system for remotely communicating with an elevator in prediction of a passenger
CN101065310A (zh) 2005-09-26 2007-10-31 三菱电机株式会社 电梯控制装置
US8061485B2 (en) * 2005-09-30 2011-11-22 Inventio Ag Elevator installation operating method for transporting elevator users
US8020672B2 (en) * 2006-01-12 2011-09-20 Otis Elevator Company Video aided system for elevator control
EP1984286A1 (de) 2006-02-13 2008-10-29 Kone Corporation Kommunikationssystem
US7823700B2 (en) * 2007-07-20 2010-11-02 International Business Machines Corporation User identification enabled elevator control method and system
US20120090922A1 (en) 2009-06-03 2012-04-19 Kone Corporation Elevator system
US8573366B2 (en) * 2009-06-03 2013-11-05 Kone Corporation Elevator system to execute anticipatory control function and method of operating same
WO2011009358A1 (zh) 2009-07-20 2011-01-27 杭州优迈科技有限公司 被动式无线远程电梯召唤的操控系统及控制方法
US20120252498A1 (en) 2009-09-30 2012-10-04 Telecom Italia S.P.A. Method and system for notifying proximity of mobile communication terminals users
US8813917B2 (en) * 2010-05-10 2014-08-26 Kone Corporation Method and system for limiting access rights within a building
WO2011141627A1 (en) 2010-05-10 2011-11-17 Kone Corporation Method and system for limiting access rights
US8960373B2 (en) * 2010-08-19 2015-02-24 Kone Corporation Elevator having passenger flow management system
WO2012059639A1 (en) 2010-11-03 2012-05-10 Kone Corporation Elevator system
US9580272B2 (en) * 2011-03-29 2017-02-28 Inventio Ag User guidance with mobile electronic devices
US9284158B2 (en) * 2011-12-15 2016-03-15 Kone Corporation Elevator system
US9323232B2 (en) * 2012-03-13 2016-04-26 Nokia Technologies Oy Transportion remote call system based on passenger geo-routines
US9481548B2 (en) * 2013-10-09 2016-11-01 King Fahd University Of Petroleum And Minerals Sensor-based elevator system and method using the same
US9834408B2 (en) * 2014-01-28 2017-12-05 Mitsubishi Electric Corporation Elevator call registering system

Non-Patent Citations (11)

* Cited by examiner, † Cited by third party
Title
Alessandro Carlotto, "Proximity Classification For Mobile Devices Using Wi-Fi Envrionment Similarity", MELT '08 Proceedings Of The First ACM International Workshop On Mobile Entity Localization And Tracking In GPS-less Environments, accessed Nov. 7, 2013, 2pg.
BlipSystems.com, "BlipTrack Tracking-Privacy Concerns", downloaded from http://www.blipsystems.com/urban/privacy-concerns/ on Nov. 7, 2013, 1 page.
BlipSystems.com, "BlipTrack Tracking—Privacy Concerns", downloaded from http://www.blipsystems.com/urban/privacy-concerns/ on Nov. 7, 2013, 1 page.
BlueMotion/Blooth FAQ, "InterVistas BlueMotion/Blooth, Bluetooth Monitoring for Airports", Dec. 1, 2010, downloaded from http://www.intervistas.com/downloads/BlueMotion_FAQ_08Feb2011.pdf on Nov. 7, 2013, 3 pages.
Chinese Fourth Office Action for application CN 201380081672.3, dated Mar. 5, 2019, 10 pages.
European Search Report for application EP 13899919.8, dated Aug. 30, 2017, 9 pages.
International Search Report for application PCT/US2013/075615; dated Sep. 24, 2014, pp. 1-6.
Melanie D.G. Kaplan, "Intelligent Elevators Answer Vertical Challenges", SmartPlanet.com, Jul. 17, 2012, 5 pages.
Stackoverflow.com, "Detecting Proximity Using MAC Address", downloaded from http://stackoverflow.com/questions/19641454/detecting-proximity-using-mac-address on Nov. 7, 2013, 2 pages.
Superuser.com, "Wi-Fi Client Mac Address Scanning", downloaded from http://superuser.com/questions/471450/wi-fi-client-mac-address-scanning on Nov. 7, 2013, 1 pages.
Written Opinion for application PCT/US2013/075615; dated Sep. 24, 2014, pp. 1-8.

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10990071B2 (en) * 2017-11-07 2021-04-27 Kone Corporation Managing power demand of a plurality of passenger transport installations
US20190161317A1 (en) * 2017-11-30 2019-05-30 Otis Elevator Company Sequence triggering for automatic calls & multi-segment elevator trips
US20190161316A1 (en) * 2017-11-30 2019-05-30 Otis Elevator Company Sequence triggering for automatic calls & multi-segment elevator trips
US10947085B2 (en) * 2017-11-30 2021-03-16 Otis Elevator Company Sequence triggering for automatic calls and multi-segment elevator trips
US10947086B2 (en) * 2017-11-30 2021-03-16 Otis Elevator Company Sequence triggering for automatic calls and multi segment elevator trips
US20190292010A1 (en) * 2018-03-23 2019-09-26 Otis Elevator Company Wireless signal device, system and method for elevator service request
US11939186B2 (en) * 2018-03-23 2024-03-26 Otis Elevator Company Wireless signal device, system and method for elevator service request

Also Published As

Publication number Publication date
WO2015094178A1 (en) 2015-06-25
CN105829223B (zh) 2019-09-03
EP3083465A4 (de) 2017-09-27
EP3083465A1 (de) 2016-10-26
EP3083465B1 (de) 2021-07-07
US20160311647A1 (en) 2016-10-27
CN105829223A (zh) 2016-08-03

Similar Documents

Publication Publication Date Title
US10392224B2 (en) Elevator control with mobile devices
CN105813969B (zh) 使用无线可编程装置进行的服务请求
US10118797B2 (en) Mobile application based elevator dispatching using tenant identity
KR102518973B1 (ko) 모바일 장치 상태 관리 및 위치 결정
JP6841842B2 (ja) 事前設定エレベータ呼び出し
CN110116945B (zh) 电梯系统
EP3080025B1 (de) Verkehrsflussdaten für fördersystem
US10294071B2 (en) Elevator activity level management of mobile device access
US11827491B2 (en) Elevator service request using user device
EP3116200A2 (de) Bakensystem und -verfahren zur wegfindung bei personenförderung
EP3505476A1 (de) Aufzugsdienstanforderung unter verwendung einer benutzervorrichtung mit gefilterter zielstockwerkauswahl
US10273118B2 (en) Device and method providing traffic forecasts for elevator systems
AU2018202212A1 (en) Elevator service request using user device with app-retained floor pairs
US20170096318A1 (en) Variable elevator assignment
CN109071151B (zh) 用于移动装置和固定显示器的电梯分配
CN106115387A (zh) 电梯运行控制系统及控制方法
AU2015268847A1 (en) Automatic determination of elevator user's current location and next destination with mobile device technology
JP2015199558A (ja) エレベータ装置およびエレベータ予測配車制御方法
CN108313843A (zh) 电梯通信系统和方法中的连接管理
CN107444997A (zh) 使用目的地键入固定装置对乘坐者疏散操作进行的统筹安排

Legal Events

Date Code Title Description
AS Assignment

Owner name: OTIS ELEVATOR COMPANY, CONNECTICUT

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PETERSON, ERIC C.;SIMCIK, PAUL A.;SCOVILLE, BRADLEY ARMAND;AND OTHERS;REEL/FRAME:038861/0349

Effective date: 20131206

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4