Gateway for elevator system with dual control units

Abstract

A network system for communicating voice and elevator telemetry data, having a gateway with gateway controllers, the gateway controllers including one or more gateway controllers configured to process telemetry data and to process voice data; the first battery is used for supplying power to the gateway; a first cable operatively coupled to the one or more gateway controllers and the elevator controller, where the first cable is configured to receive telemetry data and power from the elevator controller to recharge the first battery; a PLC connector operatively coupled to the one or more gateway controllers, operatively coupled to an internal communication device in the elevator car via a connector cable, where the connector cable extends from the PLC connector to the internal communication device along the travel cable, and the PLC connector is configured to receive voice data from the internal communication device, and transmit a portion of the power from the elevator controller to recharge a second battery mounted within the internal communication device.

Description

Technical Field

[0001] The embodiments described herein relate to elevator systems, and more specifically, to gateways for elevator systems having dual control units that manage power losses from voice communications. Background Technology

[0002] The elevator system includes a gateway that enables the transmission of telemetry data from the elevator controller to a data center. The elevator car may have an alarm panel that allows passengers to alert the call center about issues such as a stopped elevator. The gateway can connect to the Service Tool (SVT) port on the elevator controller using a cable such as a ribbon cable. The SVT port is typically used by mechanics to communicate with the elevator controller using handheld test equipment. The SVT port can be a serial port, such as a DB-9 pin port, which provides an interface for collecting elevator data from the elevator controller used by the mechanic's test equipment or gateway. The SVT port also provides 5V, 100mA of power from the elevator controller to the devices connected to it, such as the mechanic's test equipment or gateway. The SVT port typically does not provide sufficient power to power, for example, internal communication devices within the elevator car, and to process and transmit voice data to the call center, such as voice calls made by passengers using internal communication devices during warning conditions. Summary of the Invention

[0003] Disclosed is a network system for transmitting voice and telemetry data associated with the operation of an elevator car, the system comprising: a gateway including: a housing; a printed circuit board (PCB) within the housing; a gateway controller coupled to the PCB, including one or more gateway controllers configured to process the telemetry data and the voice data; a first battery powering the gateway; a first cable operatively coupled to the one or more gateway controllers and an elevator controller, wherein the first cable is configured to receive the telemetry data and power from the elevator controller to recharge the first battery; and a power line communication (PLC) connector operatively coupled to the one or more gateway controllers, and an internal communication device operatively coupled to the elevator car via a connector cable, wherein the connector cable extends from the PLC connector along a travel cable to the internal communication device, and wherein the PLC connector is configured to receive the voice data from the internal communication device and transmit a portion of the power from the elevator controller to recharge a second battery installed within the internal communication device.

[0004] In addition to one or more aspects of the system, or as an alternative, the first cable includes an SVT connector.

[0005] Except for one or more aspects of the system, or as an alternative, the gateway does not have a dedicated power port for receiving power from a wall socket.

[0006] In addition to one or more aspects of the system, or as an alternative, the first battery and the second battery are lithium-ion batteries.

[0007] In addition to one or more aspects of the system, or as an alternative, the first cable is configured to receive 5 volts, 100 mA of power from the elevator controller, and the first battery and the second battery are each configured to store 3450 mA-hours.

[0008] In addition to one or more aspects of the system, or as an alternative, the system includes a modem operatively coupled to the one or more gateway controllers and configured to connect the gateway to a cloud service.

[0009] In addition to one or more aspects of the system, or as an alternative, the system includes a display module visible along the housing that displays text indicating the charging status, controller connectivity, and network connectivity of at least one of the first and second batteries. In addition to one or more aspects of the system, or as an alternative: the one or more gateway controllers include a first gateway controller for processing the telemetry data and a second gateway controller for processing the voice data, wherein: the first gateway controller is continuously powered by the elevator controller via the first cable to process the telemetry data; and the second gateway controller is configured to operate in wake-up mode when receiving and processing the voice data, and otherwise in sleep mode.

[0010] In addition to one or more aspects of the system, or as an alternative, the first gateway controller is configured to charge the first battery only when the second gateway controller is in the sleep mode.

[0011] In addition to one or more aspects of the system, or as an alternative, the first gateway controller is configured to divide the power received from the elevator controller between the first battery and the second battery, so that the first battery and the second battery are fully charged during the same time frame, while the second gateway controller is in the sleep mode, and the first gateway controller is powered by the elevator controller via the first cable to process the telemetry data.

[0012] Disclosed is a method for operating a network system for transmitting voice data and telemetry data associated with the operation of an elevator car, the method comprising: receiving and processing the telemetry data by one or more gateway controllers of the gateway on a printed circuit board (PCB) mounted within a housing of the gateway, wherein the telemetry data is received via a first cable operatively coupled between the one or more gateway controllers and an elevator controller; receiving power from the elevator controller via the first cable to charge a first battery mounted on the PCB, wherein the first battery is operatively coupled to the one or more gateway controllers mounted on the PCB; receiving and processing the voice data by the one or more gateway controllers mounted on the PCB, wherein the voice data is received via a power line communication (PLC) connector, the PLC connector being operatively coupled to (i) the one or more gateway controllers and (ii) the internal communication device in the elevator car via a connector cable extending from the PLC connector along a travel cable to an internal communication device; and A portion of the power received from the elevator controller is transmitted via the PLC connector to charge a second battery installed in the internal communication device.

[0013] In addition to one or more aspects of the method, or as an alternative, the first cable includes an SVT connector.

[0014] Apart from one or more aspects of the method, or as an alternative, the gateway does not have a dedicated power port.

[0015] In addition to one or more aspects of the method, or as an alternative, the first battery is a lithium-ion battery.

[0016] In addition to one or more aspects of the method, or as an alternative, the first cable is configured to receive 5 volts, 100 mA of power from the elevator controller, and the first battery and the second battery are each configured to store 3450 mA-hours.

[0017] In addition to one or more aspects of the method, or as an alternative, the method includes connecting to a cloud service via a modem operatively coupled to the gateway controller.

[0018] In addition to one or more aspects of the method, or as an alternative, the method includes displaying text via a display module indicating the charging state, controller connectivity, and network connectivity of at least one of the first and second batteries. In addition to one or more aspects of the method, or as an alternative, the one or more gateway controllers include a first gateway controller for processing the telemetry data and a second gateway controller for processing the voice data, and the method includes: continuously powering the first gateway controller with the first battery to process the telemetry data; and operating the second gateway controller in a wake-up mode when receiving and processing the voice data, and otherwise operating the second gateway controller in a sleep mode.

[0019] In addition to one or more aspects of the method, or as an alternative, the method includes charging the first battery only when the second gateway controller is in the sleep mode.

[0020] In addition to one or more aspects of the method, or as an alternative, the method includes: dividing the power received from the elevator controller between the first battery and the second battery, such that the first battery and the second battery are fully charged during the same time frame, while the second gateway controller is in the sleep mode, and the first gateway controller is powered by the elevator controller via the first cable to process the telemetry data. Attached Figure Description

[0021] This disclosure is illustrated by way of example and is not limited to the accompanying drawings, in which similar reference numerals indicate similar elements.

[0022] Figure 1 These are schematic diagrams of elevator systems that can be implemented using various embodiments of this disclosure; Figure 2 An elevator system with a gateway and internal communication device according to an embodiment is shown; Figure 3 Details of a gateway with dual processors according to an embodiment are shown; Figure 4 This is a process diagram of charging the batteries in the gateway and internal communication device according to an embodiment; Figure 5A This is a diagram illustrating the available power of the gateway based on the power supplied to the first gateway processor using the gateway battery when the gateway is only transmitting telemetry data. Figure 5B This is a diagram illustrating the available power of the gateway based on the power supplied to the first and second gateway processors using the gateway battery when the gateway transmits telemetry and voice data. Figure 6AThis is a process diagram illustrating the available power of the internal communication device based on the battery of the internal communication device when no voice data is generated; Figure 6B This is a diagram illustrating the process of generating voice data based on the available power of the internal communication device utilizing the battery of the internal communication device; Figure 7 This is a flowchart illustrating the operation of the gateway to power the first and second gateway processors and to charge the first and second batteries; and Figure 8 This demonstrates an ecosystem that utilizes the system to facilitate calls between internal communication devices and call centers. Detailed Implementation

[0023] Figure 1 This is a perspective view of an elevator system 101, which includes an elevator car 103, a counterweight 105, a tension member 107, guide rails (or track system) 109, a machine (or machine system) 111, a position reference system 113, and an electronic elevator controller (controller) 115. The elevator car 103 and the counterweight 105 are connected to each other via the tension member 107. The tension member 107 may include or be configured as, for example, ropes, cables, and / or coated steel strips. The counterweight 105 is configured to balance the load of the elevator car 103 and to facilitate simultaneous and opposite movement of the elevator car 103 relative to the counterweight 105 within the elevator shaft (or shaft) 117 and along the guide rails 109.

[0024] Tension member 107 engages machine 111, which is part of the overhead structure of elevator system 101. Machine 111 is configured to control movement between elevator car 103 and counterweight 105. Position reference system 113 may be mounted on a fixed portion at the top of elevator shaft 117, such as on a support rail or guide rail, and may be configured to provide a position signal relating to the position of elevator car 103 within elevator shaft 117. In other embodiments, position reference system 113 may be directly mounted to a moving component of machine 111, or may be positioned in other locations and / or configurations as known in the art. As known in the art, position reference system 113 can be any device or mechanism for monitoring the position of elevator car and / or counterweight. For example, and not limitingly, as those skilled in the art will appreciate, position reference system 113 can be an encoder, sensor, or other system, and can include speed sensing, absolute position sensing, etc.

[0025] As shown, elevator controller 115 can be located in controller room 121 of elevator shaft 117 and configured to control the operation of elevator system 101 and, in particular, the operation of elevator car 103. It should be understood that elevator controller 115 does not need to be in controller room 121, but can be in the shaft or other location within the elevator system. For example, elevator controller 115 can provide drive signals to machine 111 to control the acceleration, deceleration, leveling, stopping, etc., of elevator car 103. Elevator controller 115 can also be configured to receive position signals from position reference system 113 or any other desired position reference device. As the elevator car 103 moves up or down along guide rail 109 within elevator shaft 117, it can stop at one or more landings 125 as controlled by elevator controller 115. Although shown in controller room 121, those skilled in the art will appreciate that elevator controller 115 can be located and / or configured in other locations or positions within elevator system 101. In one embodiment, elevator controller can be remotely located or located in the cloud.

[0026] Machine 111 may include a motor or similar drive mechanism. According to embodiments of this disclosure, machine 111 is configured to include an electrically driven motor. The power supply for the motor can be any power source, including an electrical grid, which is supplied to the motor in conjunction with other components. Machine 111 may include a traction pulley that transmits force to the tension member 107 to move the elevator car 103 within the elevator shaft 117.

[0027] Although illustrated and described using a rope system including tension member 107, embodiments of this disclosure may be employed in elevator systems employing other methods and mechanisms for moving the elevator car within the elevator shaft. For example, embodiments may be used in cordless elevator systems using linear motors to transmit motion to the elevator car. Embodiments may also be used in cordless elevator systems using hydraulic lifts to transmit motion to the elevator car. Embodiments may also be employed in cordless elevator systems using self-propelled elevator cars (e.g., elevator cars equipped with friction wheels, clamping wheels, or traction sheaves). Figure 1 These are non-restrictive examples presented for illustrative and explanatory purposes only.

[0028] Go to Figure 2The figure illustrates an elevator system 101, which has an elevator car 103 and an elevator controller 115 in a shaft 117. A gateway 160 is operatively connected to the elevator controller 115 via a first cable 180. The gateway 160 can receive telemetry data 182 and other messages from the elevator controller 115. The gateway 160 can transmit the telemetry data 182 to a cloud service 148, including a data center 150, via a network 155. The gateway 160 can be powered by a first battery 165, which receives power 184 via the first cable 180 for recharging the first battery 165.

[0029] Travel cable 118 runs within shaft 117 and supplies power to elevator car 103. An internal communication device (or ICU) 170 may be located within elevator car 103 and may be used by passengers under warning conditions. Internal communication device 170 may be powered by a second battery 175, which indirectly receives power from elevator controller 115 for recharging (the battery may be collectively referred to as 177). Specifically, a second cable 260 extending along (e.g., within) travel cable 118 may connect gateway 160 and internal communication device 170. Power from elevator controller 115 may be directed through gateway 160 to internal communication device 170 to recharge the second battery 175. According to an embodiment, internal communication device 170 is a digital internal communication device configured to transmit voice data 172 via gateway 160 to call center 152, which is part of cloud service 148. Telemetry data 182 and voice data 172 may be collectively referred to as data 173.

[0030] Battery 177 may be a rechargeable lithium-ion battery. Each of batteries 177 may be capable of storing up to 3450 mAh of charge, for example, only in a non-limiting embodiment. In one embodiment, a 3450 mAh capacity for data and voice has been identified as providing a charging capacity that is almost six times the 600 mAh battery capacity of a data gateway commonly used in industry. However, other capacities may be selected within the scope of the embodiments. Cylindrical lithium-ion batteries are chosen instead of the flat pouch-type lithium-ion batteries used in mobile phones to avoid battery swelling, which could affect the operation of flat pouch batteries. However, this is not intended to limit the scope of the embodiments.

[0031] The power 184 available from the elevator controller 115 via the first cable 180 can be limited to, for example, 100 mA at 5 volts, or 0.5 watts. This is merely exemplary to illustrate that the components can draw more power than the controller can continuously supply in terms of usage. According to specifications, the internal communication device 170 and the gateway 160 should have sufficient battery backup power to allow for a four-hour talk time each during periods of potential power loss to the elevator system due to power loss to the building.

[0032] Go to Figure 3 The diagram illustrates a configuration of gateway 160 that enables power to be supplied to gateway 160 and internal communication device 170 to charge battery 177 and utilize available charging power from elevator controller 115 to achieve four hours of talk time. In one embodiment, gateway 160 may not have a dedicated power port for connection to NEMA (National Electrical Manufacturers Association) type power lines. That is, the gateway has no or does not require a traditional connection to a wall outlet or wired power from building power. Gateway 160 has a housing 200. A printed circuit board (PCB) 210 is located within housing 200.

[0033] Gateway controller 220 is coupled to PCB 210 and includes a first gateway controller 230 and a second gateway controller 240. Charging circuitry 225 is also coupled to PCB 210 and gateway controller 220. A first battery 165, supplying power to gateway controller 220, is mounted to PCB 210. As indicated, a first cable 180 is operatively coupled to the first gateway controller 230 and elevator controller 115. The first cable 180 may include an SVT (Electrical) connector 181.

[0034] A power line communication (PLC) connector 250 is operatively coupled to a second gateway controller 240. The PLC connector 250 is also operatively coupled to an internal communication device 170 in the elevator car 130 via a second cable 260 extending from the PLC connector 250 along the travel cable 118. The PLC connector 250 is configured to receive voice data from the internal communication device 170 and transmit a portion of the power 184 from the elevator controller 115 to recharge a second battery 175 installed within the internal communication device 170.

[0035] Modem 270 may be located within a housing and connected to PCB 210. Modem 270 may be operatively coupled to gateway controller 220. Modem 270 may be configured to connect gateway 160 to cloud service 148 to transmit telemetry data 182 to data center 150 and voice data 172 to call center 152.

[0036] Gateway 160 may include a display module 280 visible along housing 200. Display module 280 is configured to display text indicating, for example, the charging status of battery 177, device connectivity with, for example, elevator controller 115 and internal communication device 170, and network connectivity with, for example, cloud service 148 via network 155. Display module 280 may include an actuator 282, which may be a button, for activating or deactivating display module 280 or selecting different status indicators.

[0037] Gateway 160 may also include an Ethernet port 290 as a backup for modem 270, a USB port 292 for use by maintenance personnel to perform diagnostic tests and provide additional power, and a CAN bus port 294 for providing backup communication to elevator controller 115. Magnet 296 may be disposed around housing 200 for connecting housing 200 to a metal structure around or near elevator controller 115. Depending on the location of gateway 160, antenna connector 298 may be provided to enhance the signal to and from modem 270.

[0038] As indicated, the first cable 180 is configured to receive telemetry data 182 and power 184 (e.g., 0.5 watts, or 100 mA at 5 volts, as indicated above) from the elevator controller 115 to recharge the battery 177, for example, to a capacity of 3450 mA. As indicated above, these figures are exemplary and are not intended to limit the scope of the embodiments. The power available from the controller, capable of being stored in the battery, and utilized by the processor may differ (higher or lower) and fall within the scope of this disclosure. Power from the elevator controller 115 is directed through a charging circuit 225 having a step-down voltage operating at 4.2 volts, thereby increasing the available current for charging the battery 177 to over 110 mA.

[0039] Go to Figure 4 As indicated, elevator controller 115 provides 500mW of power, or 100mA at 5V. This 100mA is passed through charging circuit 225 to step down the voltage to 4.2V and increase the amperage to 110mA. This can be divided between batteries 177, providing, for example, 77.3mA to the first battery 165 and 32.7mA to the second battery 175. This will charge these batteries 177 (if not already charged) to approximately 106 hours of capacity. Because telemetry data 182 is continuously transmitted to data center 150, the first battery 106 continuously utilizes 44.6mA (box 410) to power the first gateway controller 230. When no voice data 172 is being transmitted, the second gateway controller 240 and internal communication device 170 are asleep, and the second battery 175 utilizes its nominal power, 0.01mA.

[0040] For example, the total available current is 110mA. For normal data-only operations, 44.6mA is consumed, and the gateway receives this current. This current allows the available 65.4mA to charge both batteries. In the disclosed non-limiting embodiment, a current allocation scheme is selected to provide an equal amount of current to each battery, i.e., 32.7mA each. The ICU receives 32.7mA, and the gateway receives 32.7 + 44.6mA = 77.3mA. The gateway receives a larger amount of current and ensures that data-only operations receive priority before battery charging allocation.

[0041] As indicated, these figures are exemplary and are not intended to limit the scope of the embodiments. The power available to the controller, capable of being stored in the battery, and utilized by the processor may vary (higher or lower) and fall within the scope of this disclosure.

[0042] Go to Figure 5A If no power 184 is available from elevator controller 115, for example during an emergency, the maximum available power from the first battery 165 in gateway 160 will be considered. When gateway 160 is only transmitting telemetry data 182, there is a power consumption of 44.68 mA (3450 mA) from the first battery 165 to power the first gateway controller 230, and gateway 160 can operate for up to 77.2 hours, as shown in block 510A. That is, Figure 5A The system is shown in data-only mode, where power is utilized by the first processor and other components such as a modem. In data-only mode, the second processor is effectively in sleep mode.

[0043] As indicated, these figures are exemplary and are not intended to limit the scope of the embodiments. The power available to the controller, capable of being stored in the battery, and utilized by the processor may vary (higher or lower) and fall within the scope of this disclosure.

[0044] Go to Figure 5B When gateway 160 transmits both telemetry data 182 and voice data 172, there is a power consumption of 44.68 mA from the 3450 mA available in the first battery 165 to power the first gateway controller 230. There is also a power consumption of 176.1 mA from the 3450 mA available in the first battery 165 to power the second gateway controller 240. This is because the second gateway controller 240 requires more power to process voice data 172 than the first gateway controller 230 requires to process telemetry data 182. In other words, a 9.4-minute voice call depletes the first battery 165 by 1 percentage point. Under these conditions, gateway 160 can operate for up to 15.6 hours.

[0045] Go to Figure 6A When the internal communication device 170 is not transmitting voice data 172, there is a nominal power consumption of 0.01 mA from the 3450 mA available in the second battery 175. When there is no voice call, the internal communication device transmits nominal data. This is typically different from telemetry data from the elevator controller. Instead, data from the internal communication device ensures the link between the gateway and the ICU is active, even in sleep mode. That is, there is no elevator data collected by the internal communication device, as is the case with elevator data collected by the gateway connected to the elevator controller. For example, there might be battery status information sent from the ICU to the gateway, allowing it to be reported to a cloud service. Furthermore, some component failures in the ICU might be reported to the gateway, potentially requiring action from the mechanic to resolve any issues related to the ICU.

[0046] The second battery 175 will remain charged for an extended period of time. For example... Figure 6B As shown, when the internal communication device 170 transmits voice data 172, there is a power consumption of 86.1mA from the second battery 175 to power the internal communication device 170, so that the internal communication device will operate for up to 40 hours.

[0047] Regarding the charging of battery 177 while power 184 remains available from elevator controller 115, in order to maximize battery charging and utilization, second gateway controller 240 is configured to operate in wake-up mode when receiving voice data 172, and otherwise in sleep mode.

[0048] In the disclosed non-limiting embodiments, the gateway controller does not manage battery charging. In one non-limiting example, the gateway controller's function is to manage and process elevator controller data so that it can be sent to a cloud service. The gateway controller requires 44.68mA and consumes that much available power initially. Remaining current is equally distributed and allocated to the gateway battery and the ICU battery by the battery management circuitry 225.

[0049] However, when the second gateway controller 240 wakes up and processes the voice data 172, the first battery 165 will be depleted. Figure 5B As shown, during data and voice operation, the current consumption is 44.68mA (data) and 176.1mA (voice), totaling 220.78mA, which is greater than the 110mA supplied by the SVT port from the elevator controller. Therefore, during this period, the power from the battery is utilized without change.

[0050] Note that the controller power source provides the same power regardless of the gateway's mode. If the power demand is below 110mA, it will be met, and the remaining available power (in mA) will be used to charge the battery. Battery charging can only occur when there is excess power (in mA), i.e., in data-only mode. Figure 5A This is done when adding voice (e.g., Figure 5B The excess available power becomes insufficient, and the gateway relies on the power in the battery to supplement the power from the SVT port.

[0051] That is, as indicated, the total available current is 110mA. For normal data-only operation, the gateway consumes 44.6mA, leaving 65.4mA available to charge both batteries. The batteries are charged equally, with the remaining power at 32.7mA. Therefore, the ICU receives 32.7mA, and the gateway receives 32.7mA and 44.6mA, or 77.3mA. The gateway receives a larger amount of available charge during this operation to ensure that data-only operation is prioritized before battery charging allocation. As indicated, when charging both batteries 177, the available power is equally divided between batteries 177, i.e., equally divided between the first gateway, the first battery 165, and the PLC connector 250, to charge the second battery 175.

[0052] Go to Figure 7The flowchart illustrates the process for powering a gateway to maximize battery charging and utilization. As shown in block 710, the method includes receiving and processing telemetry data 192 via a first gateway controller 230 through a first cable 180. As shown in block 720, the method includes receiving and processing voice data via a second gateway controller 240 through a PLC connector 250. As shown in block 730, the method includes receiving power from an elevator controller 115 via the first cable 180 to recharge a first battery 165. As shown in block 740, the method includes transmitting a portion of the power 184 received from the elevator controller 115 via the PLC connector 250 to charge a second battery 175. As shown in block 750, the method includes continuously powering the first gateway controller 230 via an SVT port from the elevator controller to process telemetry data 182. As shown in block 760, the method includes operating the second gateway controller 240 in wake-up mode when receiving and processing voice data 172, and otherwise operating the second gateway controller 240 in sleep mode. As shown in box 770, the method includes charging the first battery 165 only when the second gateway controller 240 is in sleep mode. As shown in box 780, the method includes dividing the power received from the elevator controller 115 between the first battery 165 and the second battery 175, so that battery 177 completes charging during the same time frame, while a portion of the power received from the elevator controller powers the first gateway controller 230 to process telemetry data 182. As shown in box 790, the method includes displaying text indicating the charging status of battery 177, controller connectivity, and network connectivity via display module 280.

[0053] To be understood, in one embodiment, the gateway controller may manage battery charging. For example, the gateway controller may include battery charging circuitry, and in such an embodiment, the gateway controller will include power management circuitry functionality.

[0054] Go to Figure 8 This illustrates an ecosystem for using gateway 160 to complete calls from internal communication device 170 in elevator car 103 to call center 152 via network 155. Two variants of call center 152 are shown, including call center 152A capable of using the IP protocol and another call center 152B capable of using the PTSN (Public Switched Telephone Network) protocol.

[0055] Voice is received by microphone 300 of internal communication device 170, and this voice is applied to SIP (Session Layer) codec 310 in internal communication device 170 to generate voice data 172. Regarding SIP codec 310, this codec is an audio codec used for Voice over Internet Protocol (VoIP) calls, for example... Figure 8This was completed in [the context of the original text]. An efficient and readily available codec that delivers high-quality voice is Opus, a variant of Silk (developed by Silk Technologies, Inc. and available on the Azure Marketplace), which is used by Skype and Teams (developed by Microsoft).

[0056] Voice data 172 is transmitted to gateway 160 via PLC connector 250. Gateway 160 initiates a SIP call 320 via network 155. A ten-digit phone number is associated with the SIP call to identify its origin (i.e., the specific elevator car 103 associated with the call), thus supporting PTSN calls. If call center 152A supports calls over IP, the SIP call is maintained, traversing the network through a SIP system such as IVR (Interactive Voice Response) technology or Session Border Controller (SBC) 330, and completed at call center 152A. Note that IVR is illustrated because this is a configuration already used in North America. However, the use of IVR is not a requirement of this disclosure. Technically, if the call center is IP-enabled, the data transmitted in SIP remains in IP format.

[0057] If call center 152B does not support IP-based calling but supports the PTSN protocol, the call is switched to PTSN 340 and completed at call center 152B. As indicated, call center 152B can directly contact elevator car 103 using the ten-digit number assigned by gateway 160. Personnel at call center 152B can communicate with passengers in elevator car 103 via speaker 360 in internal communication device 170. Using the operation of the above-disclosed gateway 160 and internal communication device 170, calls can be reliably completed for many hours.

[0058] The wireless connections identified above can utilize protocols including Local Area Network (LAN, or WLAN for wireless LAN) and / or Private Area Network (PAN) protocols. LAN protocols include WiFi technology based on the IEEE Section 802.11 standard. PAN protocols include, for example, Bluetooth Low Energy (BTLE), a wireless technology standard designed and marketed by the Bluetooth Special Interest Group (SIG) for exchanging data over short distances using short-wavelength radio waves. PAN protocols also include Zigbee, a technology based on the IEEE Section 802.15.4 protocol, representing a set of advanced communication protocols for creating personal area networks with small, low-power digital wireless devices for low-power, low-bandwidth requirements. Such protocols also include Z-Wave, a wireless communication protocol supported by the Z-Wave Alliance, which uses mesh networking and low-energy radio waves to communicate between devices such as appliances, thereby allowing for wireless control.

[0059] Other applicable protocols include Low Power WAN (LPWAN), which is a wireless wide area network (WAN) designed to allow long-range communication at low bit rates, enabling terminal devices to operate on battery power for extended periods (years). Long Range WAN (LoRaWAN) is a type of LPWAN maintained by the LoRa Alliance and is a Media Access Control (MAC) layer protocol used to transmit management and application messages between network servers and application servers. Such wireless connectivity can also include Radio Frequency Identification (RFID) technology, used for communication with integrated chips (ICs) on, for example, RFID smart cards. Furthermore, Sub-1GHz RF devices operate in the ISM (Industrial, Scientific, and Medical) spectrum band below Sub-1GHz (typically in the 769–935 MHz, 315MHz, and 468MHz frequency range). This sub-1GHz spectrum band is particularly useful for RF IoT (Internet of Things) applications. Other LPWAN-IoT technologies include Narrowband IoT (NB-IoT) and LTE-M1 category IoT (LTE Cat M1 or LTE-M). Wireless communication used in the disclosed systems may include cellular technologies, such as 2G / 3G / 4G / 5G (etc.). The above is not intended to limit the scope of applicable wireless technologies.

[0060] The wired connections identified above can include connections (cables / interfaces) under RS-422 (Recommended Standard), also known as TIA / EIA-422, a technical standard supported by the Telecommunications Industry Association (TIA) and initiated by the Electronic Industries Alliance (EIA), which specifies the electrical characteristics of digital signaling circuits. Wired connections can also include connections (cables / interfaces) under the RS-232 standard for serial communication transmission of data. The RS-232 standard formally defines the signaling connection between a DTE (Data Terminal Equipment), such as a computer terminal, and a DCE (Data Circuit Termination Equipment or Data Communication Equipment), such as a modem. Wired connections can also include connections (cables / interfaces) under the Modbus serial communication protocol managed by the Modbus organization. Modbus is a server / client protocol designed for use by programmable logic controllers (PLCs) and is a commonly available means of connecting industrial electronic devices. Wireless connections can also include connectors (cables / interfaces) under the PROFibus (Process Fieldbus) standard managed by PROFIBUS & PROFINET International (PI). PROFibus is a standard for fieldbus communication in automation technology, publicly published as part of IEC (International Electrotechnical Commission) 61158. Wired communication can also be achieved via Controller Area Network (CAN) bus. CAN is a vehicle bus standard that allows microcontrollers and devices to communicate with each other in applications without a host computer. CAN is a message-based protocol published by the International Organization for Standardization (ISO). The above is not intended to limit the scope of applicable wired technologies.

[0061] As indicated, when data is transmitted over a network between terminal processors, the data may be transmitted in its raw form, or it may be processed, in whole or in part, at any of the terminal processors or intermediate processors (e.g., at a cloud service or other processor). The data may be parsed, partially or completely processed or compiled at any of the processors, and may then be concatenated together or maintained as separate information packets.

[0062] Each processor identified herein can be, but is not limited to, a single-processor or multi-processor system of any of a variety of possible architectures, including field-programmable gate arrays (FPGAs), central processing units (CPUs), application-specific integrated circuits (ASICs), digital signal processors (DSPs), or graphics processing units (GPUs) arranged homogeneously or heterogeneously. Memory identified herein can be, but is not limited to, random access memory (RAM), read-only memory (ROM), or other electronic, optical, magnetic, or any other computer-readable medium. Embodiments can take the form of processes implemented by a processor and means for practicing those processes, such as a processor. Embodiments can also take the form of modules based on computer code, such as computer program code containing instructions (e.g., a computer program product) embodied in a tangible medium (e.g., a non-transitory computer-readable medium) (e.g., a floppy disk, CD-ROM, hard disk drive), as firmware on processor registers, or in any other non-transitory computer-readable medium, wherein when the computer program code is loaded into and executed by the computer, the computer becomes means for practicing the embodiments. Embodiments may also take the form of computer program code, for example, whether stored in a storage medium, loaded into a computer, and / or executed by a computer, or transmitted via a transmission medium (e.g., via wires or cables, via optical fibers, or via electromagnetic radiation), wherein when the computer program code is loaded into and executed by the computer, the computer becomes an apparatus for practicing exemplary embodiments. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

[0063] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The term “about” is intended to include the degree of error associated with a measurement of a particular quantity and / or with manufacturing tolerances of the equipment available at the time of filing. As used herein, the singular forms “a,” “an,” and “the” are intended to also include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “comprises and / or comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

Claims

1. A network system for transmitting voice data and telemetry data associated with the operation of an elevator car, the system comprising: Gateway, the gateway includes: case; The printed circuit board (PCB) inside the housing; One or more gateway controllers are coupled to the PCB, and the one or more gateway controllers are configured to process the telemetry data and process the voice data; A first battery that powers the gateway; A first cable, operatively coupled to the one or more gateway controllers and elevator controllers, wherein the first cable is configured to receive telemetry data and power from the elevator controller to recharge the first battery; and A power line communication (PLC) connector, operatively coupled to one or more gateway controllers, and operatively coupled to an internal communication device in the elevator car via a connector cable, wherein the connector cable extends from the PLC connector along a travel cable to the internal communication device, and wherein the PLC connector is configured to receive the voice data from the internal communication device and transmit a portion of the power from the elevator controller to recharge a second battery installed within the internal communication device.

2. The system according to claim 1, wherein The first cable includes an SVT connector.

3. The system according to claim 1, wherein The gateway does not have a dedicated power port for receiving power from a wall socket.

4. The system according to claim 2, wherein The first battery and the second battery are lithium-ion batteries.

5. The system according to claim 4, wherein The first cable is configured to receive 5 volts, 100 mA of power from the elevator controller, and the first battery and the second battery are each configured to store 3450 mA-hours.

6. The system according to claim 1, comprising A modem, operatively coupled to the one or more gateway controllers, and configured to connect the gateway to a cloud service.

7. The system according to claim 6, comprising Along the housing, a display module is visible that displays text indicating the charging status, controller connectivity, and network connectivity of at least one of the first and second batteries.

8. The system according to claim 1, wherein: The one or more gateway controllers include a first gateway controller for processing the telemetry data and a second gateway controller for processing the voice data. in: The first gateway controller is continuously powered by the elevator controller via the first cable to process the telemetry data; and The second gateway controller is configured to operate in wake-up mode when receiving and processing the voice data, and otherwise in sleep mode.

9. The system according to claim 8, wherein The first gateway controller is configured to charge the first battery only when the second gateway controller is in the sleep mode.

10. The system according to claim 9, wherein The first gateway controller is configured to divide the power received from the elevator controller between the first battery and the second battery, so that the first battery and the second battery are charged within the same time frame, while the second gateway controller is in the sleep mode, and the first gateway controller is powered by the elevator controller via the first cable to process the telemetry data.

11. A method of operating a network system for transmitting voice data and telemetry data associated with the operation of an elevator car, the method comprising: One or more gateway controllers of the gateway, which are mounted on a printed circuit board (PCB) within the housing of the gateway, receive and process the telemetry data, wherein the telemetry data is received via a first cable operatively coupled between the one or more gateway controllers and the elevator controller. Power is received from the elevator controller via the first cable to charge a first battery mounted on the PCB, wherein the first battery is operatively coupled to the one or more gateway controllers mounted on the PCB; The voice data is received and processed by the one or more gateway controllers mounted to the PCB, wherein the voice data is received via a power line communication (PLC) connector, the PLC connector being operatively coupled to (i) the one or more gateway controllers and (ii) the internal communication device in the elevator car via a connector cable extending from the PLC connector along a travel cable to the internal communication device; and A portion of the power received from the elevator controller is transmitted via the PLC connector to charge a second battery installed in the internal communication device.

12. The method according to claim 11, wherein, The first cable includes an SVT connector.

13. The method according to claim 11, wherein, The gateway does not have a dedicated power port.

14. The method according to claim 11, wherein, The first battery is a lithium-ion battery.

15. The method according to claim 14, wherein, The first cable is configured to receive 5 volts, 100 mA of power from the elevator controller, and the first battery and the second battery are each configured to store 3450 mA-hours.

16. The method of claim 11, further comprising connecting to a cloud service via a modem operatively coupled to the gateway controller.

17. The method of claim 16, comprising: The display module displays text indicating the charging status, controller connectivity, and network connectivity of at least one of the first and second batteries.

18. The method of claim 11, wherein The one or more gateway controllers include a first gateway controller for processing the telemetry data and a second gateway controller for processing the voice data, and The method further includes: The first battery continuously supplies power to the first gateway controller to process the telemetry data; as well as The second gateway controller operates in wake-up mode when receiving and processing the voice data, and otherwise operates in sleep mode.

19. The method of claim 18, comprising: The first battery is charged only when the second gateway controller is in the sleep mode.

20. The method of claim 19, comprising: The power received from the elevator controller is divided between the first battery and the second battery, so that the first battery and the second battery are fully charged during the same time frame, while the second gateway controller is in the sleep mode, and the first gateway controller is powered by the elevator controller via the first cable to process the telemetry data.

Images