Service tool wireless access management

A service tool wireless access management system includes a wireless access interface and an equipment service system comprising at least one processor. The at least one processor is configured to enable the wireless access interface responsive to a wireless access request initiated through a service tool, establish a wireless communication session with the service tool through the wireless access interface, and disable the wireless access interface responsive to a wireless communication termination event.

BACKGROUND

The present disclosure relates to equipment service systems, and more particularly, to service tool wireless access management.

Current service tools used for accessing equipment controllers (e.g., elevator controllers) typically rely on using a separate hardware tool that physically plugs into an equipment control system. The physical connection ensures that the service tool is used by an individual who is physically present at a specific location when using the service tool. Being physically present helps to ensure that a user of the service tool can observe environmental conditions, such as the presence of other people. As networked/wireless service tools are used in place of physically connected service tools, a wireless network interface is desirable. Keeping a wireless network interface active to communicate with a wireless-enabled service tool at the location of the equipment consumes power even if the wireless network interface is only used occasionally for servicing events.

BRIEF DESCRIPTION

According to some embodiments, a service tool wireless access management system is provided. The service tool wireless access management system includes a wireless access interface and an equipment controller of an equipment service system. The equipment controller includes at least one processor configured to enable the wireless access interface responsive to a wireless access request initiated through a service tool, establish a wireless communication session with the service tool through the wireless access interface, and disable the wireless access interface responsive to a wireless communication termination event.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the wireless access request is relayed from the service tool through a remote server to the at least one processor via one or more communication pathways.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include a plurality of equipment components of the equipment service system having an associated instance of the wireless access interface enabled responsive to the wireless access request.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the equipment controller is an elevator controller, and the wireless communication session provides the service tool with access to one or more functions of the elevator controller.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the wireless access interface includes a first wireless access interface of the equipment controller, and the wireless access request is received on a second wireless access interface of the equipment controller, the second wireless access interface having a reduced wireless communication range relative to the first wireless access interface.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the at least one processor is further configured to enable the wireless access interface responsive to an input received at a user interface of the equipment controller.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where a location of the service tool within a communication range threshold of the wireless access interface is confirmed before enabling the wireless access interface.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the wireless communication termination event comprises one or more of: a timeout period elapsing between enabling the wireless access interface and establishing the wireless communication session, detecting that the service tool is outside of a communication range threshold of the wireless access interface, a timeout period elapsing since a last completed communication of the wireless communication session, a disable command received from the service tool, and an operating mode transition to a primary operating from an auxiliary operating mode of the equipment controller.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the wireless access interface is enabled responsive to a transition of the equipment controller from the primary operating mode to the auxiliary operating mode, wherein the transition is based on a condition detected at one or more of: an input interface, a restricted-access interface, a scanner interface, and at least one sensor.

In addition to one or more of the features described above or below, or as an alternative, further embodiments may include where the wireless access request includes a request identifier, and enablement of the wireless access interface is further conditioned on determining that the request identifier matches an identifier associated with the equipment controller.

According to some embodiments, a method of service tool wireless access management is provided. The method includes enabling a wireless access interface of an equipment service system responsive to a wireless access request initiated through a service tool. A wireless communication session with the service tool is enabled through the wireless access interface, and the wireless access interface is disabled responsive to a wireless communication termination event.

Technical effects of embodiments of the present disclosure include selectively enabling and disabling a wireless access interface proximate to a service location for establishing a wireless communication session with a service tool as needed.

DETAILED DESCRIPTION

Referring toFIG. 1, an exemplary embodiment of an equipment service system20, which may include, or may use portions of, a service tool22, a remote server24, and at least one equipment component25with at least one equipment controller26. The service tool22may communicate with the remote server24and/or the equipment controller26over respective communication pathways28,30when corresponding communication interfaces are enabled. The communication pathways28,30may be associated with such communication protocols as Bluetooth®, Wi-Fi, Near Field Communications (NFC), infrared, mobile broadband (e.g., 3G, 4G, etc.), satellite, and others. The remote server24can facilitate communication between the equipment controller26and the service tool22. One or more communication pathways31between the remote server24and equipment controller26can enable remote access, for instance, for the service tool22to request enablement of communication pathway30. Thus, information can flow over communication pathways28and31, and/or a direct link can be established between the equipment controller26and the service tool22using communication pathway30upon enablement of a wireless access interface of the equipment controller26. Communication pathway31can use a different protocol for longer distance secure communication than protocols used by communication pathways28and30, for example.

The service tool22may include a user interface32that facilitates system interaction with a user (e.g., an equipment repairperson/service technician). Non-limiting examples of the service tool22may include a smartphone, a tablet computer, laptop computer, and other electronic devices. The remote server24may be cloud-based (i.e., in a cloud network environment). The equipment service system20generally controls the flow of information between the service tool22, the remote server24and/or the equipment controller26. In some embodiments, the service tool22may provide an interface to one or more remotely executed applications with reduced local code execution. In one embodiment, the remote server24and the equipment controller26may be owned and/or controlled by a common company.

The equipment service system20may further include at least one site (i.e., two illustrated as34,36inFIG. 1). Each site34,36may include at least one equipment controller26(i.e., three illustrated for each site34,36) operable to control one or more equipment components25. Non-limiting examples of sites34,36may be a building, a set of floors within a building, a portion of a floor within a building, a collection of buildings, and others. A non-limiting example of an equipment controller26may be an elevator controller that can be serviced by the manufacturer of the elevator, and the one or more equipment components25can be one or more elevator components such as elevator cars. The service tool22, the remote server24, and the equipment controller26may each include respective processors38,40,42(e.g., microprocessors), and storage mediums44,46,48that may be computer writeable and readable.

In the example ofFIG. 1, a service tool wireless access management system10can include the service tool22and the equipment controller26, where various location-based operations can be distributed between either or both of the service tool22and the equipment controller26. For example, at least one processor38of the service tool22can determine whether the service tool22is located at a predetermined service location of an equipment service system20and/or at least one processor42of the equipment controller26can determine/confirm the location of the service tool22. Further, the remote server24may/may also determine or verify the location of the service tool22. One or more location determination techniques can be employed, such as use of global positioning system (GPS) data, network address information, and proximity detection, etc. The predetermined service location can be defined in terms of being “local” or “remote”, e.g., at one of the sites34,36or not at one of the sites34,36. For instance, if the service tool22is locally at site34, then the service tool22may be considered remote from site36. “Local” can be defined being on-site (e.g., within a building) or proximate to a specific predetermined location within and/or near the site, depending upon the technology used. For instance, “local” can be defined as being within signal communication range for direct wireless communication of the wireless communication protocol used, such as Wi-Fi. In one embodiment, “local” can be defined as being within a specific geospatial area (e.g., certain GPS coordinates, certain cellular triangulation area, etc.). “Remote” can be defined as an off-site location or out of wireless transmission range. The remote server24can be used to enable wireless access at sites34,36for the service tool22and may provide authentication services.

FIG. 2is a perspective view of an elevator system101including an elevator car103, a counterweight105, one or more load bearing members107, a guide rail109, a machine111, a position encoder113, and an elevator controller115. The elevator system101includes examples of various equipment components25ofFIG. 1and predetermined service locations (e.g., a general onsite location134, at various landings125, at a location136within elevator car103, at a location140proximate to machine111, at a pit location138, in controller room121, or any other desired location), where the elevator controller115is an example of the equipment controller26ofFIG. 1. For instance, the onsite location134can be within a building/structure that includes the elevator system101, while an offsite location142can be external to the building/structure that includes the elevator system101.

In the example ofFIG. 2, the elevator car103and counterweight105are connected to each other by the load bearing members107. The load bearing members107may be, for example, ropes, steel cables, and/or coated-steel belts. The counterweight105is configured to balance a load of the elevator car103and is configured to facilitate movement of the elevator car103concurrently and in an opposite direction with respect to the counterweight105within an elevator shaft117and along the guide rail109. The load bearing members107engage the machine111, which is part of an overhead structure of the elevator system101. The machine111is configured to control movement between the elevator car103and the counterweight105. The position encoder113may be mounted on an upper sheave of a speed-governor system119and may be configured to provide position signals related to a position of the elevator car103within the elevator shaft117. In other embodiments, the position encoder113may be directly mounted to a moving component of the machine111, or may be located in other positions and/or configurations as known in the art.

The elevator controller115can be located, as shown, in a controller room121of the elevator shaft117and is configured to control the operation of the elevator system101, and particularly the elevator car103. For example, the elevator controller115may provide drive signals to the machine111to control the acceleration, deceleration, leveling, stopping, etc. of the elevator car103. The elevator controller115may also be configured to receive position signals from the position encoder113. When moving up or down within the elevator shaft117along guide rail109, the elevator car103may stop at one or more landings125as controlled by the elevator controller115. Although shown in a controller room121, those of skill in the art will appreciate that the elevator controller115can be located, distributed between, and/or configured in other locations or positions within the elevator system101. In some embodiments, the elevator controller115can be configured to control features within the elevator car103, including, but not limited to, lighting, display screens, music, spoken audio words, etc.

The machine111may include a motor or similar driving mechanism and an optional braking system. In accordance with embodiments of the disclosure, the machine111is configured to include an electrically driven motor. The power supply for the motor may be any power source, including a power grid, which, in combination with other components, is supplied to the motor. Although shown and described with a rope-based load bearing system, elevator systems that employ other methods and mechanisms of moving an elevator car within an elevator shaft, such as hydraulics, ropeless, or any other methods, may employ embodiments of the present disclosure.FIG. 2is merely a non-limiting example presented for illustrative and explanatory purposes.

FIG. 3depicts an example of interfaces200of the equipment controller26ofFIG. 1that can be used to establish a wireless communication session with the service tool22ofFIG. 1. One or more instances of the interfaces200can be installed at each site34,36to serve various purposes during a primary operating mode (e.g., normal operation) and one or more auxiliary operating modes (e.g., service mode, inspection mode, error state modes, etc.), including enabling and disabling wireless communication upon transitions between modes or within modes. For instance, the interfaces200can be located in whole or in part within the elevator car103ofFIG. 2as part of an elevator control interface. Further, the interfaces200can be located at one or more of the landings125ofFIG. 2, in controller room121ofFIG. 2, and/or at other locations. The interfaces200can provide various inputs and/or outputs to equipment controller26ofFIG. 1. For example, the interfaces200can include a display202, an input interface204including a plurality of buttons206, a restricted-access input interface208, a scanner interface209, and at least one wireless access interface214. In some embodiments, the display202is touch-sensitive and operable to receive user inputs. The display202, input interface204, restricted-access input interface208, and/or scanner interface209are collectively referred to as user interfaces205. The restricted-access input interface208can include an access control210, such as a lock, operable to restrict input unless an associated key212is used (e.g., a fire key switch). The restricted-access input interface208may be used to transition between a primary operating mode and an auxiliary operating mode. The scanner interface209can include a camera, a radio-frequency identification (RFID) transceiver, a barcode reader, a fingerprint reader, and/or similar interface operable to detect information about a user. For instance, the scanner interface209can identify an authorized user/user type based on an identification card/device, biometric data, and/or other observable information. An interface controller201can process inputs and outputs of the interfaces200as a data concentrator of the equipment controller26. For example, the interfaces200can be integrated into the elevator car103ofFIG. 2, while all or a portion of the equipment controller26ofFIG. 1may be located in the elevator controller115at controller room121. The interface controller201can also detect the presence of a user through one or more sensors218, such as door/gate sensors, load sensors, thermal sensors, audio sensors, and/or other types of sensors known in the art. Input from the input interface204, scanner interface209, and/or sensors218may also or alternatively be used to transition between the primary operating mode and the auxiliary operating mode based on a condition detected.

The wireless access interface214can be used to establish various types of wireless communication, such as the communication pathway30ofFIG. 1. In some embodiments, there are multiple instances of the wireless access interface214that may have different communication ranges, as further illustrated in conjunction withFIG. 4. For instance, embodiments may have a single communication range threshold304defined relative to a location302of the wireless access interface214. Other embodiments can include a first communication range threshold308for a first wireless access interface214A and a second communication range threshold310for a second wireless access interface214B at a location306, where the second wireless access interface214B has a reduced wireless communication range relative to the first wireless access interface214A (as indicated by a smaller diameter of the second communication range threshold310relative to the first communication range threshold308). For instance, the first wireless access interface214A may be a Wi-Fi interface, while the second wireless access interface214B may be a Bluetooth® or NFC communication interface. The communication range thresholds304,308,310can be used to check/ensure proximity with respect to the service tool22. For example, in some embodiments, the wireless access interface214is not enabled until the service tool22is within the communication range threshold304at location302, which may be confirmed by GPS coordinates provided from the service tool22to the remote server24. In some embodiments, the first wireless access interface214A is not enabled until the service tool22is within the second communication range threshold310. The second wireless access interface214B may use less power than the first wireless access interface214A, and selectively enabling/disabling the first wireless access interface214A reduces overall power consumption and can reduce exposure to potential cybersecurity threats. The communication range thresholds304,308can also be used to determine when to disable wireless access interfaces214,214A, such as within a timeout period elapsing since the service tool22was last within the communication range thresholds304,308.

With further reference toFIG. 3, an identifier216can be associated with the interfaces200and a corresponding equipment controller26ofFIG. 1. The identifier216can be an alpha-numeric code or symbol (e.g., a bar code or quick response code) that identifies a location of the wireless access interface214to be accessed. In some embodiments, a user of the service tool22can photograph, scan, or manually input information associated with the identifier216to target communication with a specific instance of the wireless access interface214, for instance, where multiple other wireless access interfaces214are also in close physical proximity to the service tool22. Where the identifier216is used, a wireless access request from the service tool22can include a request identifier, and enablement of the wireless access interface214can be conditioned on determining that the request identifier matches the identifier216associated with the equipment controller26. As depicted in the example ofFIG. 5, a location may include an elevator bank400include elevator shafts402A,402B,402C,402D with corresponding elevator cars404A,404B,404C,404D, a control room406, and corresponding wireless access interfaces414A,414B,414C,414D,414E as instances of wireless access interface214. The use of identifiers, such as identifier216ofFIG. 3, can ensure that a user of the service tool22is interfacing with the desired target, where wireless access interfaces414A-414E may have an overlapping communication range, particularly when the elevator cars404A-404D are at or near a same height within elevator shafts402A-402D.

Entering inputs directly through the user interfaces205ofFIG. 3can also be used to selectively enable or confirm enablement of a wireless access interface. For example, each of the elevator cars404A-404D and control room406may have instances of the user interfaces205. A sequence or combination of pressing buttons206, using key212on restricted-access input interface208, and/or making touch-based inputs through display202at a particular location can enable or confirm enablement of one or more of the wireless access interfaces414A-414E ofFIG. 5. As an example, the service tool22may request enablement of the wireless access interfaces414A-414E, and entry of a code or sequence through user interfaces205at elevator car404B may result in keeping wireless access interface414B enabled while disabling wireless access interfaces414A and414C-414E.

In the example ofFIG. 5, the wireless access interfaces414A-414E are normally disabled to conserve power and/or reduce exposure to cyberattacks. Alternatively or in addition to requesting enablement of one or more of the wireless access interfaces414A-414E through the service tool22, the user can push one or more of the buttons206ofFIG. 3or a press/toggle a switch to enable or confirm enablement of one or more of the wireless access interfaces414A-414E. For instance, a combination of button206pushes could include simultaneously pushing a combination of buttons206for at least a minimum time period and/or entering a predetermined sequence. In some embodiments, the service tool22receives a code from the remote server24indicating the needed combination or sequence. Similarly, in addition to requesting enablement of one or more of the wireless access interfaces414A-414E through the service tool22or to confirm user presence, the scanner interface209can be used to capture scanned user data, such as an RFID-enabled card, a barcode on an identification card or work order, and/or biometric data of an authorized user. In some embodiments, upon enablement of one of the wireless access interfaces414A-414E, other instances of the wireless access interfaces414A-414E are enabled. For instance, if a user of the service tool22enables the wireless access interface414E, the remote server24or other system may also enable wireless access interfaces414A-414D. Various wireless communication termination events can result in disabling one or more of the wireless access interfaces414A-414E as further described in reference toFIG. 6.

FIG. 6depicts a process500that can be performed by the service tool wireless access management system10ofFIG. 1as shown and described herein and/or by variations thereon. Various aspects of the process500can be carried out using one or more sensors, one or more processors, and/or one or more machines and/or controllers. For example, some aspects of the flow process involve sensors (e.g., GPS, cameras, etc.), as described above, in communication with a processor or other control device and transmit detection information thereto. The process500is described in reference toFIGS. 1-6.

At block502, at least one processor38,40,42of the service tool wireless access management system10(e.g., at an equipment component25) enables a wireless access interface214responsive to a wireless access request initiated through a service tool22. The wireless access request can be relayed from the service tool22through a remote server24to the at least one processor via one or more communication pathways28,31. The service tool wireless access management system10can include a plurality of equipment components25and equipment controllers26having an associated instance of the wireless access interface214(e.g., wireless access interfaces414A-414E) enabled responsive to the wireless access request. The wireless access interface214can be a first wireless access interface214A of the equipment controller26, and the wireless access request can be received on a second wireless access interface214B of the equipment controller26, where the second wireless access interface214B has a reduced wireless communication range relative to the first wireless access interface214A. The at least one processor can be further configured to enable the wireless access interface214responsive to an input received at a user interface205of the equipment controller26. The at least one processor can be configured to confirm a location of the service tool22within a communication range threshold304of the wireless access interface214before enabling the wireless access interface214. The wireless access request can include a request identifier, and enablement of the wireless access interface214may be further conditioned on determining that the request identifier matches an identifier216associated with the equipment controller26.

At block504, at least one processor of the service tool wireless access management system10establishes a wireless communication session with the service tool22through the wireless access interface214. The wireless communication session can provide the service tool22with access to one or more functions of an elevator controller115. Functions can include monitoring of performance parameters, modifying performance parameters, change performance aspects, entering a test/diagnostic mode, and other such actions.

At block506, at least one processor of the service tool wireless access management system10disables the wireless access interface214responsive to a wireless communication termination event. The wireless communication termination event can be one or more of: a timeout period elapsing between enabling the wireless access interface214and establishing the wireless communication session, detecting that the service tool22is outside of a communication range threshold304of the wireless access interface214, a timeout period elapsing since a last completed communication of the wireless communication session, a disable command received from the service tool, and an operating mode transition to a primary operating from an auxiliary operating mode. The wireless access interface214can be enabled responsive to a transition of the equipment controller26from the primary operating mode to the auxiliary operating mode.

Process500can be repeated periodically to confirm whether a change in location of the service tool22necessitates a change in enablement of the wireless access interface214. For example, the process500can be repeated every N minutes, hourly, or at any other suitable period. In some embodiments, the process500repeats at a faster rate when the service tool22transitions from an offsite location142to an onsite location134.

The various functions described above may be implemented or supported by a computer program that is formed from computer readable program codes and that is embodied in a computer readable medium. Computer readable program codes may include source codes, object codes, executable codes, and others. Computer readable mediums may be any type of media capable of being accessed by a computer, and may include Read Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or other forms.

Terms used herein such as component, module, system, and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, or software execution. By way of example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. It is understood that an application running on a server and the server may be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.

While the present disclosure is described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the spirit and scope of the present disclosure. In addition, various modifications may be applied to adapt the teachings of the present disclosure to particular situations, applications, and/or materials, without departing from the essential scope thereof. The present disclosure is thus not limited to the particular examples disclosed herein, but includes all embodiments falling within the scope of the appended claims.