A monitoring system and method for monitoring personnel conveyor systems

Abstract

This invention relates to a monitoring system (100) for monitoring personnel conveyor systems (110, 110a-110c). The monitoring system (100) includes a wireless mesh network (105), which includes multiple node devices (102a-102c) and one or more peripheral devices (104, 106). Node devices (102) joining the wireless mesh network (105) are configured to: acquire connection data indicating a connection from node device (102) to peripheral devices (104, 106), and, if the acquired connection data indicates a connection to a gateway device (104), assign themselves a convergence node (102a) role, or otherwise provide the acquired connection data to the gateway device (104). The gateway device (104) is configured to: assign operational roles to node devices (102) based on the acquired connection data. If the obtained connection data indicates a connection to a sensor device (106) associated with the personnel conveyor, the assigned role is that of a sensor node (102b); or if the obtained connection data indicates that the node device (102) is not connected to any peripheral device (104, 106), the assigned role is that of a router node (102c). The invention also relates to a personnel conveyor system and a method for monitoring the personnel conveyor system (110, 110a-110c).

Description

Technical Field

[0001] This invention generally relates to the technical field of personnel conveyor systems. In particular, this invention relates to the monitoring of personnel conveyor systems. Background Technology

[0002] Typically, data related to a personnel conveyor system can be obtained from the internal bus and / or control unit of a personnel conveyor system, such as an elevator system, escalator system, or moving walkway system, for purposes such as remote maintenance and / or monitoring of personnel conveyor system usage. However, in the case of a third-party personnel conveyor system, for example, the internal bus and / or control unit may not be accessible to obtain personnel conveyor-related data for monitoring purposes. A monitoring unit, including one or more internal or external sensor devices, can be deployed to the personnel conveyor system to obtain personnel conveyor-related data. For example, in the case of an elevator system, a monitoring unit can be deployed to the elevator car traveling along the elevator shaft. However, it may be impossible to cover all fault conditions with said monitoring unit. Furthermore, especially in elevator systems where the monitoring unit travels along the elevator shaft and on the elevator car, adding one or more additional sensor devices residing, for example, inside the elevator shaft and / or machine room, by simply wiring the sensor devices to the monitoring unit would be very expensive and sometimes even impossible.

[0003] Therefore, further solutions are needed to improve the monitoring of personnel conveyor systems. Summary of the Invention

[0004] To provide a basic understanding of some aspects of various embodiments of the invention, a simplified overview is given below. This overview is not a comprehensive summary of the invention. It is neither intended to identify key or essential elements of the invention nor to depict the scope of the invention. The following overview merely presents some concepts of the invention in a simplified form as a prelude to a more detailed description of exemplary embodiments of the invention.

[0005] The object of this invention is to provide a monitoring system, method, and personnel conveyor system for monitoring personnel conveyor systems. Another object of this invention is that the monitoring system, method, computer program, and tangible non-volatile computer-readable medium for monitoring personnel conveyor systems at least partially improve the monitoring of personnel conveyor systems.

[0006] The object of the present invention is achieved by the monitoring system, method and personnel conveyor system as defined by the respective independent claims.

[0007] According to a first aspect, a monitoring system for monitoring a personnel conveyor system is provided, wherein the monitoring system includes a wireless mesh network, the wireless mesh network including multiple node devices and one or more peripheral devices of the personnel conveyor system, wherein a node device joining the wireless mesh network is configured to: obtain connection data indicating a connection of the node device to a peripheral device of the personnel conveyor system, and assign itself a convergence node role if the obtained connection data indicates a connection to a gateway device, wherein the gateway device is deployed to the personnel conveyor system; or otherwise provide the obtained connection data to the gateway device, wherein the gateway device is configured to: assign an operational role to the node device based on the obtained connection data, wherein if the obtained connection data indicates a connection to a sensor device associated with the personnel conveyor, the assigned role is a sensor node role, wherein the sensor device associated with the personnel conveyor is configured to obtain sensor data indicating the status of the personnel conveyor system; or if the obtained connection data indicates that the node device is not connected to any peripheral device of the personnel conveyor system, the assigned role is a router node role.

[0008] After assigning sensor node roles to node devices, gateway devices can also be configured to: determine the types of sensor devices associated with the personnel conveyors connected to the node devices, and obtain application software corresponding to the determined types of sensor devices associated with the personnel conveyors connected to the node devices via a wireless update system.

[0009] The connection from the node device to the gateway device indicated by the obtained connection data can be provided via a first type of serial port connection, wherein the first type of serial port connection can be a Universal Serial Bus (USB) connection.

[0010] Alternatively or additionally, the connection between the node device 102, 102b) indicated by the obtained connection data and the sensor device associated with the personnel conveyor can be provided via a second type of serial port connection, wherein the second type of serial port connection can be an analog connection, an RS-232 connection, an RS-485 connection, or an internal integrated circuit (I) 2 C) Connection and / or Serial Peripheral Interface (SPI) connection.

[0011] Node devices can be configured to obtain connection data by scanning one or more communication interfaces of the node device.

[0012] A scan may include obtaining connection data at least via one or more communication interfaces of the node device.

[0013] Alternatively or additionally, scanning may include providing request data via one or more communication interfaces, and in response to providing request data, obtaining connection data via one or more communication interfaces of the node device.

[0014] Alternatively, node devices can be configured to receive connection data as user input.

[0015] Sensor devices related to personnel conveyors may include hydraulic sensors, door sensors, water presence sensors, light level sensors, human presence sensors, vibration sensors, temperature sensors, energy meters, or universal asynchronous transceiver (UART) devices.

[0016] Personnel conveyor systems can be elevator systems, escalator systems, or moving walkway systems.

[0017] According to a second aspect, a method for monitoring a personnel conveyor system is provided, the method comprising: obtaining connection data indicating a connection between a node device joining a wireless mesh network and a peripheral device of the personnel conveyor system, and assigning an operational role based on the obtained connection data, wherein if the obtained connection data indicates a connection to a gateway device, wherein the gateway device is deployed to the personnel conveyor system, the assigned role is a convergence node role; if the obtained connection data indicates a connection to a sensor device associated with the personnel conveyor, the assigned role is a sensor node role, wherein the sensor device associated with the personnel conveyor is configured to obtain sensor data indicating the status of the personnel conveyor system; or if the obtained connection data indicates that a node device is not connected to any peripheral device of the personnel conveyor system, the assigned role is a router node role.

[0018] After assigning sensor node roles, the method may further include: determining the type of sensor device associated with the personnel conveyor connected to the node device, and obtaining application software corresponding to the type of sensor device associated with the personnel conveyor connected to the node device via a wireless update system.

[0019] The connection from the node device to the gateway device indicated by the obtained connection data can be provided via a first type of serial port connection, wherein the first type of serial port connection can be a Universal Serial Bus (USB) connection.

[0020] Alternatively or additionally, the connection from the node device indicated by the acquired connection data to the relevant sensor device of the personnel conveyor can be provided via a second type of serial port connection, wherein the second type of serial port connection can be an analog connection, an RS-232 connection, an RS-485 connection, or an internal integrated circuit (I) 2 C) Connection and / or Serial Peripheral Interface (SPI) connection.

[0021] Connection data can be obtained by scanning one or more communication interfaces of the node device.

[0022] A scan may include obtaining connection data at least via one or more communication interfaces of the node device.

[0023] Alternatively or additionally, scanning may include providing request data via one or more communication interfaces, and in response to providing request data, obtaining connection data via one or more communication interfaces of the node device.

[0024] Alternatively, connection data can be obtained as user input.

[0025] Sensor devices related to personnel conveyors may include hydraulic sensors, door sensors, water presence sensors, light level sensors, human presence sensors, vibration sensors, temperature sensors, energy meters, or universal asynchronous transceiver (UART) devices.

[0026] Personnel conveyor systems can be elevator systems, escalator systems, or moving walkway systems.

[0027] According to a third aspect, a personnel conveyor system is provided, wherein the personnel conveyor system includes the aforementioned monitoring system.

[0028] Various exemplary and non-limiting embodiments of the invention with respect to structure and operation methods, as well as their additional objects and advantages, will be best understood from the following description of specific exemplary and non-limiting embodiments when read in conjunction with the accompanying drawings.

[0029] The verbs “comprising” and “including” are used herein as limitations on disclosure, neither excluding nor requiring the presence of any uncited features. Unless otherwise expressly stated, the features described in the dependent claims may be freely combined with each other. Furthermore, it should be understood that the use of “a” or “an” throughout this document, i.e., the singular form, does not exclude the plural. Attached Figure Description

[0030] In the accompanying drawings, embodiments of the invention are shown by way of example rather than limitation.

[0031] Figure 1 An example of a monitoring system for monitoring personnel conveyor systems is shown schematically.

[0032] Figure 2A-2C An example of a personnel conveyor system is illustrated schematically.

[0033] Figure 3 An example of a method for monitoring a personnel conveyor system is illustrated schematically.

[0034] Figure 4 Another example of a method for monitoring a personnel conveyor system is illustrated schematically.

[0035] Figure 5 This illustration shows yet another example of a method for monitoring a personnel conveyor system.

[0036] Figure 6 An example of a component of a node device is shown schematically.

[0037] Figure 7 An example of a component of a gateway device is shown schematically. Detailed Implementation

[0038] Figure 1 An example of a monitoring system 100 for monitoring a personnel conveyor system 110 is schematically illustrated. The monitoring system 100 includes a wireless mesh network 105 comprising a plurality of node devices 102a-102c. The monitoring system 100 also includes one or more peripheral devices 104, 106 of the personnel conveyor system 110. Each node device 102a-102c forming the wireless mesh network 105 can be configured to operate as an aggregation node, sensor node, or router node, depending on whether the node device 102a-102c is connected to a peripheral device 104, 106 of the personnel conveyor system 110 and / or the type of peripheral device 104, 106 to which the node device 102a-102c is connected. One or more peripheral devices 104, 106 may include at least one gateway device 104 and / or one or more sensor devices 106 associated with the personnel conveyor. If node device 102a-102c is connected to gateway device 104, then node device 102a is configured to operate as an aggregation node. Alternatively, if node devices 102a-102c are connected to sensor device 106 associated with the personnel conveyor, then node device 102b is configured to operate as a sensor node. Alternatively, if node devices 102a-102c are not connected to any peripheral devices 104, 106, then node device 102c is configured to operate as a router node. Figure 1 In the example monitoring system 100, node device 102a is connected to gateway device 104. Therefore, node device 102a is configured to operate as an aggregation node. Furthermore, in Figure 1 In the example monitoring system 100, node device 102b is connected to sensor device 106 associated with the personnel conveyor. Therefore, node device 102b is configured to operate as a sensor node. Furthermore, in Figure 1 In the example monitoring system 100, node device 102c is not connected to any peripheral devices 104 or 106. Therefore, node device 102c is configured to operate as a router node. Figure 1In the example, the dashed lines between multiple node devices 102a-102c illustrate communication between multiple node devices 102a-102c of the wireless mesh network 105. Communication between the multiple node devices 102a-102c of the wireless mesh network 105 can be bidirectional. Figure 1 In the example, the solid lines between the node devices 102a, 102b and the peripheral devices 104, 106 of the personnel conveyor system 110 show the connection between the node devices 102a, 102b and the peripheral devices 104, 106.

[0039] Figure 1 The example also illustrates a node device 102 that has not yet joined or will join the wireless mesh network 105 of the monitoring system 100. As described above, each node device 102 is capable of operating as a convergence node, a sensor node, and a router node. However, each node device 102 is unaware of its operating mode until it has joined the wireless mesh network 105. For each node device 102, an operating role can be assigned when it joins the wireless mesh network 105, which will be described later in this application.

[0040] The personnel conveyor system 110 can be an elevator system 110a, an escalator system 110b, or a moving walkway system 110c. In other words, the monitoring system 100 can be used to monitor the elevator system 110a, the escalator system 110b, or the moving walkway system 110c. The personnel conveyor systems 110, 110a-110c can include at least the monitoring system 100.

[0041] One or more sensor devices 106 associated with the personnel conveyor can be configured to acquire sensor data representing the status of the personnel conveyor systems 110, 110a-110c. The sensor devices 106 associated with the personnel conveyor can include, for example, but not limited to, hydraulic sensor devices, door sensor devices, water presence sensor devices, light level sensor devices, human presence sensor devices, vibration sensor devices, energy meter devices, temperature sensor devices, or Universal Asynchronous Receiver / Transmitter (UART) devices. Alternatively or additionally, the sensor devices 106 associated with the personnel conveyor can be Modbus-based devices. One or more sensor devices 106 associated with the personnel conveyor systems 110, 110a-110c can be arranged in different locations within the personnel conveyor systems 110, 110a-110c, as will be described later in this application. Depending on the personnel conveyor systems 110, 110a-110c discussed, one or more sensor devices 106 associated with the personnel conveyor can include, for example, one or more elevator-related sensor devices, one or more escalator-related sensor devices, or one or more moving walkway-related sensor devices.

[0042] The wireless mesh network 105 can relay messages to node devices 102a-102c until the message reaches the node device 102a-102c to which it is intended. Messages may include data, such as sensor data obtained by one or more sensor devices 106 associated with the personnel conveyor, as described later. Node devices 102c operating at least as router nodes are configured to participate in message relaying. Each of the plurality of node devices 102a-102c may include a communication interface unit 630 for providing one or more communication interfaces to communicate with any other unit, such as one or more peripheral devices 104, 106, one or more other node devices 102a-102c of the wireless mesh network 105, and / or any other unit. The communication interface unit 630 of each node device 102a-102c may include one or more communication devices, such as at least one radio transceiver, at least one antenna, at least one communication port, etc. Communication between multiple node devices 102a-102c of the wireless mesh network 105 can be based on at least one short-range wireless radio technology. At least one short-range wireless radio technology can include, for example, but not limited to, Bluetooth (e.g., Bluetooth Low Energy (BLE)) and / or Zigbee. Each of the multiple node devices 102a-102c can be configured to receive messages from and transmit messages to other node devices 102a-102c of the wireless mesh network 105. Communication between node devices 102a, 102b operating as convergence node roles and / or sensor node roles and one or more peripheral devices 104, 106 of the personnel conveyor system 110 can be based on one or more known wired communication technologies, as will be described later in this application.

[0043] At least one gateway device 104 is disposed in the personnel conveyor system 110. For example, if the personnel conveyor system 110 is an elevator system 110a, the gateway device 104 may be disposed in the elevator car 202, such as in the roof or machine room of the elevator car 202. Alternatively, if the personnel conveyor system 110 is an escalator system 110b or a moving walkway system 110c, the gateway device 104 may be disposed in one of the platforms of the escalator system 110b or the moving walkway system 110c. At least one gateway device 104 may operate as a gateway between the wireless mesh network 105 and at least one external entity 108. In other words, at least one gateway device 104 may be configured to provide data, such as sensor data obtained by one or more personnel conveyor-related sensor devices 106, from the wireless mesh network 105 to at least one external entity 108 and / or from at least one external entity 108 to the wireless mesh network 105. For example, sensor data obtained by one or more sensor devices 106 associated with the personnel conveyor can be relayed (e.g., routed) to at least one gateway device 104 via a wireless mesh network 105. The gateway device 104 provides the relayed sensor data to at least one external entity 108. According to another example, at least one gateway device 104 can receive data from at least one external entity 108 and provide the received data to one or more node devices 102a-102c of the wireless mesh network 105. At least one external entity 108 can be, for example, a cloud server, an Internet of Things (IoT) platform, a service center, a maintenance center, a data center, and / or a control system 205, 215, 225 of the personnel conveyor system 110. At least one gateway device 104 and at least one external entity 108 can be communicatively connected to each other. Communication between at least one gateway device 104 and at least one external entity 108 can be based on one or more known wired or wireless communication technologies.

[0044] The monitoring system 100 is particularly capable of monitoring third-party personnel conveyor systems 110, 110-110c, where the internal buses and / or control units of the personnel conveyor systems 110, 110a-110c may not be accessible. The monitoring system 100 is capable of monitoring sensor data representing the status of the personnel conveyor systems 110, 110a-110c obtained by one or more personnel conveyor-related sensor devices 106, which is particularly advantageous in the case of third-party personnel conveyor systems 110, 110-110c.

[0045] Figure 2A-2C Non-limiting examples of personnel conveyor systems 110, 110a-110c are schematically shown. For clarity, in Figure 2A-2CNo node devices 102 that have not yet joined or will join the wireless mesh network of monitoring system 100 are shown. Furthermore, for clarity, in Figure 2A-2C The communication between the multiple node devices 102a-102c forming the wireless mesh network 105 is not shown.

[0046] exist Figure 2A In the example, the personnel conveyor systems 110, 110a-110c are elevator systems 110a. Elevator system 110a includes at least one elevator car 202 and an elevator control system (e.g., elevator control unit 205), the elevator car 202 being configured to travel along at least one respective elevator shaft 204 between a plurality of floors 206a-206n. Figure 2A The example elevator system 110a includes one elevator car 202 traveling along an elevator shaft 204; however, elevator system 110a may also include a group of elevators, i.e., a group of two or more elevator cars 202a, each elevator car traveling along a separate elevator shaft 204, the elevator shaft 204 being configured to operate as a unit serving the same floors 206a-206n. Elevator control system 205 may be configured to at least partially control the operation of elevator system 110a. Elevator control system 205 may be located, for example, in a machine room (for clarity, in...). Figure 2A (Not shown in the image) or one of the floors 206a-206n of elevator system 110a. Elevator system 110a may also include one or more other known elevator-related entities, such as hoisting systems, user interface devices, safety circuits and devices, elevator door systems, etc., for clarity. Figure 2A It is not shown in the document.

[0047] Next, when the personnel conveyor system 110 is an elevator system 110a, example locations of multiple node devices 102a-102c and one or more peripheral devices 104, 106 in the wireless mesh network 105 are discussed. As mentioned above, the gateway device 104 can be arranged in the elevator car 202, for example, on the roof of the elevator car 202, such as... Figure 2AAs shown in the example. Alternatively, gateway device 104 can be deployed in the equipment room. A node device 102a operating as a convergence node can be connected to gateway device 104. If elevator system 110a includes more than one elevator car 202, a gateway device 104 can be deployed to each elevator car 202. Furthermore, one or more elevator-related sensor devices 106 can be deployed at different locations within elevator system 110a. One or more elevator-related sensor devices 106 can be deployed, for example, but not limited to, elevator shafts, elevator cars 202, and / or multiple floors 206a-206n. A node device 102b operating as a sensor node can be connected to each of the one or more elevator-related sensor devices 106. Figure 2A In one example, an elevator-related sensor device 106 is positioned in the elevator car 202, and a node device 102b operating as a sensor node is connected to the elevator-related sensor device 106. Furthermore, in Figure 2A In the example, three elevator-related sensor devices 106 are arranged inside the elevator shaft, such that one elevator-related sensor device 106 is arranged at the top of the elevator shaft 204, and two elevator-related sensor devices 106 are arranged at the bottom of the elevator shaft 204, i.e., the pit of the elevator shaft 204, and a node device 102b operating as a sensor node is connected to each of the three elevator-related sensor devices 106. Therefore, Figure 2A The example wireless mesh network 105 includes four node devices 102b operating as sensor nodes, each of which is connected to an elevator-related sensor device 106. According to a non-limiting example, one or more elevator-related sensor devices 106 may include at least one hydraulic sensor device disposed to the pit of the elevator shaft 204, at least one door sensor device disposed to the door of the elevator car 202, at least one water presence sensor device disposed to the pit of the elevator shaft 204, at least one light level sensor device disposed inside the elevator car 202, and / or at least one human presence sensor device disposed inside the elevator car 202 and / or inside the machine room. One or more node devices 102c operating as router nodes, i.e., one or more node devices 102c not connected to any peripheral devices 104, 106, may be disposed at different locations within the elevator system 110a. One or more node devices 102c operating as router nodes can be deployed, for example, but not limited to, elevator shaft 204, elevator car 202, and / or multiple landings 206a-206n. Figure 2A In the example, four node devices 102c operating as router nodes are arranged inside the elevator shaft 204. As described above, when the personnel conveyor system 110 is the elevator system 110a, Figure 2A Only a non-limiting example of one or more peripheral devices 104, 106 and multiple node devices 102a-102c is shown, but the monitoring system 100 may include any other number of peripheral devices 104, 106 and / or the monitoring system 100 may include any other number of node devices 102a-102c arranged at any location to the elevator system 110a.

[0048] exist Figure 2B In the example, the personnel conveyor system 110 is an escalator system 110b. The escalator system 110b includes a conveying entity 212 and an escalator control system (e.g., an escalator control unit 215). The conveying entity 212 includes steps arranged to a circular track. The escalator control system 215 can be configured to at least partially control the operation of the escalator system 110b. The escalator control system 215 can, for example, be arranged to one of the platforms 214, 216 of the escalator system 110b. Figure 2B In the example, the escalator control system 215 is arranged on the first platform of the escalator system 110b, namely the top platform 214. Alternatively, the escalator control system 215 may be arranged on, for example, the second platform of the escalator system 110b, namely the bottom platform 216. The escalator system 100b may also include one or more other known escalator-related entities, such as drive mechanisms, etc., for clarity. Figure 2B It is not shown in the document.

[0049] Next, when the personnel conveyor system 110 is an escalator system 110b, example locations of multiple node devices 102a-102c and one or more peripheral devices 104, 106 of the wireless mesh network 105 are discussed. As described above, at least one gateway device 104 may be deployed to at least one platform 214, 216 of the escalator system 110b. Figure 2B In the example, gateway device 104 is positioned on the first platform 214 of escalator system 110b. A node device 102a operating as a convergence node can be connected to gateway device 104. Furthermore, one or more escalator-related sensor devices 106 can be positioned at different locations within escalator system 110b. The one or more escalator-related sensor devices 106 can be, for example, but not limited to, positioned on at least one platform 214, 216 of escalator system 110b, at least one handrail 213 of escalator system 110b, the gearbox of escalator system 110b, and / or the conveyor entity 212 of escalator system 110b. A node device 102b operating as a sensor node can be connected to each of the one or more escalator-related sensor devices 106. Figure 2BIn one example, an escalator-related sensor device 106 is positioned on the handrail 213 of the escalator system 110b, and a node device 102b operating as a sensor node is connected to the escalator-related sensor device 106. Furthermore, in Figure 2B In the example, an escalator-related sensor device 106 is positioned on the second platform 216 of the escalator system 110b, and a node device 102b operating as a sensor node is connected to the escalator-related sensor device 106. Therefore, Figure 2B Example wireless mesh network 105 includes two node devices 102b operating as sensor nodes, and each of the two node devices 102b is connected to an escalator-related sensor device 106. According to a non-limiting example, one or more escalator-related sensor devices 106 may include at least one human presence sensor device disposed to escalator system 110b, a gearbox disposed to, for example, escalator system 110b (for clarity, in...). Figure 2B At least one vibration sensor device (not shown), and / or at least one temperature sensor disposed on the gearbox of the escalator system 110b and / or at least one handrail 213 of the escalator system 110b. One or more node devices 102c operating as router nodes, i.e., one or more node devices 102c not connected to any peripheral devices 104, 106, may be disposed at different locations on the escalator system 110b. One or more node devices 102c operating as router nodes may be disposed, for example, but not limited to, at least one platform 214, 216 of the escalator system 110b, at least one handrail 213 of the escalator system 110b, the gearbox of the escalator system 110b, and / or the conveyor body 212 of the escalator system 110b. Figure 2B In the example, three node devices 102c, operating as router nodes, are positioned at different locations within the escalator system 110b. As described above, when the personnel conveyor system 110 is the escalator system 110b, Figure 2B Only a non-limiting example of one or more peripheral devices 104, 106 and multiple node devices 102a-102c is shown, but the monitoring system 100 may include any other number of peripheral devices 104, 106 and / or the monitoring system 100 may include any other number of node devices 102a-102c arranged at any location in the escalator system 110b.

[0050] exist Figure 2CIn the example, the personnel conveyor system 110 is a moving walkway system 110c. The moving walkway system 110c includes a conveying entity 222 and a moving walkway control system (e.g., a moving walkway control unit 225). The conveying entity 222 includes trays arranged to a circular track. The moving walkway control system 225 can be configured to at least partially control the operation of the moving walkway system 110c. The moving walkway control system 225 can, for example, be arranged to one of the platforms 224, 226 of the moving walkway system 110c. Figure 2C In the example, the moving walkway control system 225 is positioned on a first platform of the moving walkway system 110c, such as the top platform 224. Alternatively, the moving walkway control system 225 may be positioned on a second platform of the moving walkway system 110c, such as the bottom platform 226. Figure 2C In the example, the mobile walkway system 110c is an inclined mobile walkway system, i.e., a mobile walkway system configured to transport people or loads across an inclined plane (e.g., between two floors). However, the mobile walkway system 110c can also be a horizontal mobile walkway system, i.e., a mobile walkway system configured to transport people or loads on a horizontal plane. The mobile walkway system 110c may further include one or more other known mobile walkway-related entities, such as drive machines, etc., for clarity. Figure 2C It is not shown in the document.

[0051] Next, when the personnel conveyor system 110 is a mobile walkway system 110c, example locations of multiple node devices 102a-102c and one or more peripheral devices 104, 106 of the wireless mesh network 105 are discussed. As described above, at least one gateway device 104 may be deployed to at least one platform 224, 226 of the mobile walkway system 110c. Figure 2C In the example, gateway device 104 is positioned on first platform 224 of mobile walkway system 110c. A node device 102a operating as a convergence node may be connected to gateway device 104. Furthermore, one or more mobile walkway-related sensor devices 106 may be positioned at different locations within mobile walkway system 110c. The one or more mobile walkway-related sensor devices 106 may be, for example, but not limited to, positioned on at least one platform 224, 226 of mobile walkway system 110c, at least one handrail 223 of mobile walkway system 110c, gearbox of mobile walkway system 110c, and / or conveyor entity 222 of mobile walkway system 110c. A node device 102b operating as a sensor node may be connected to each of the one or more mobile walkway-related sensor devices 106. Figure 2CIn the example, a mobile walkway-related sensor device 106 is positioned on the handrail 223 of the mobile walkway system 110c, and a node device 102b operating as a sensor node is connected to the mobile walkway-related sensor device 106. Furthermore, in Figure 2C In the example, a mobile trail-related sensor device 106 is positioned on the second platform 226 of the mobile trail system 110c, and a node device 102b operating as a sensor node is connected to the mobile trail-related sensor device 106. Therefore, Figure 2C The example wireless mesh network 105 includes two node devices 102b operating as sensor nodes, and each of the two node devices 102b is connected to a mobile trail-related sensor device 106. According to a non-limiting example, one or more mobile trail-related sensor devices 106 may include at least one human presence sensor device disposed to the mobile trail system 110c, a gearbox disposed to, for example, the mobile trail system 110c (for clarity, ...). Figure 2C At least one vibration sensor device (not shown), and / or a gearbox arranged to the moving walkway system 110c and / or at least one temperature sensor of at least one handrail 223 of the moving walkway system 110c. One or more node devices 102c operating as router nodes, i.e., one or more node devices 102c not connected to any peripheral devices 104, 106, may be arranged at different locations on the moving walkway system 110c. One or more node devices 102c operating as router nodes may, for example, but not limited to, be arranged to at least one platform 224, 226 of the moving walkway system 110c, at least one handrail 223 of the moving walkway system 110c, the gearbox of the moving walkway system 110c, and / or the transport entity 222 of the moving walkway system 110b. Figure 2C In the example, three node devices 102c operating as router nodes are arranged at different locations within the mobile walkway system 110c. As described above, when the personnel conveyor system 110 is the mobile walkway system 110c, Figure 2C Only a non-limiting example of one or more peripheral devices 104, 106 and multiple node devices 102a-102c is shown, but the monitoring system 100 may include any other number of peripheral devices 104, 106 and / or the monitoring system 100 may include any other number of node devices 102a-102c arranged at any location in the mobile walkway system 110c.

[0052] Now, through reference Figure 3 To describe at least some aspects of the invention, in Figure 3 Examples of methods for monitoring personnel conveyor systems 110, 110a-110c are shown in the figure. Figure 3 An example method is schematically illustrated in the form of a flowchart. The method is described with reference to a node device 102 joining the wireless mesh network 105 and a gateway device 104 deployed to personnel conveyor systems 110, 110a-110c. However, each node device 102 joining the wireless mesh network 105 can independently perform method steps related to one or more operations of the node device 102. As described above, each node device 102 is capable of operating as a convergence node 102a, a sensor node 102b, and a router node 102c. Furthermore, each node device 102 is unaware of its operating mode before joining the wireless mesh network 105. In other words, each node device 102 can be a generic node device, such as a generic radio dongle. Therefore, when each node device 102 joins the wireless mesh network 105, the node device 102 and / or the gateway device 104 can perform at least some of the following method steps to assign an operating role to the node device 102. Before role assignment, a node device 102 joining the wireless mesh network 105 can obtain network configuration information, for example, by receiving BLE beacon messages from one or more node devices 102a-102c in the wireless mesh network 105, in order to join the wireless mesh network 105, i.e., become part of the wireless mesh network 105 of the monitoring system 100, i.e., belong to the wireless mesh network 105. The node device 102 joining the wireless mesh network 105 can be, for example, a new node device 102 or a node device 102 replacing existing node devices 102a-102c, such as a faulty node device. According to the example, if new peripheral devices 104, 106 are installed in the personnel conveyor system 110, the new node device 102 can be connected to the new peripheral devices 104, 106 and join the wireless mesh network 105, as will be discussed.

[0053] In step 310, the node device 102 joining the wireless mesh network 105 obtains connection data indicating a connection between the node device 102 and peripheral devices 104, 106 of the personnel conveyor systems 110, 110a-110c. The node device 102 can obtain the connection data by scanning (i.e., probing) one or more communication interfaces (i.e., connection interfaces) of the node device 102, as described later. Alternatively, the node device 102 can obtain the connection data as user input via the user interface (UI) unit 640. If the node device 102 is connected to peripheral devices 104, 106, the connection data indicating the connection of the node device 102 may include, for example, information about possible connections between the node device 102 and peripheral devices 104, 106 and / or identification information of the peripheral devices 104, 106 connected to the node device 102.

[0054] In step 320, based on the obtained connection data, roles, i.e., operational roles, are assigned to the node devices 102 that have joined the wireless mesh network 105. In other words, in step 320, operational roles are assigned to the node devices 102 that have joined the wireless mesh network 105 in response to obtaining connection data. Depending on the obtained connection data, the node device 102 may assign operational roles to itself, and / or the gateway device 104 may assign operational roles to the node device 102. After assigning operational roles in step 320, the node device 102 may provide a role assignment message indicating the role assignment to the gateway device 104 via the wireless mesh network 105. In response to receiving the role assignment message from the node device 102, the gateway device 104 may provide an acknowledgment message to the node device 102 via the wireless mesh network 105. Alternatively, the gateway device 104 may forward the role assignment message to at least one external entity 108, such as a cloud server, and in response to receiving the role assignment message, at least one external entity 108 may provide an acknowledgment message to the node device 102 via the wireless mesh network 105. Depending on the role assigned to node device 102, node device 102 may alternatively or additionally perform one or more other operations after the operation role is assigned in step 320, as described above.

[0055] Figure 4 It was disclosed schematically in a more detailed manner. Figure 3 The flowchart. Especially step 320 from Figure 4The process becomes clear. As described above, step 320 assigns an operational role to the node device 102 joining the wireless mesh network 105 based on the obtained connection data. If, in step 410, the obtained connection data indicates a connection to the gateway device 104, then in step 420, the assigned role of the node device 102 is the aggregation node 102a role. In other words, if the connection data obtained in step 410 indicates that the node device 102 is connected to the gateway device 104, then the node device 102 assigns itself the aggregation node 102a role in step 420. The connection from the node device 102, 102a to the gateway device 104 indicated by the obtained connection data can be provided via a first type of serial port connection between the node device 102 and the gateway device 104. The first type of serial port connection can be a Universal Serial Bus (USB) connection. In other words, if the connection data obtained in step 410 indicates that node device 102 is connected to peripheral device 104 via a first type of serial port connection (i.e., USB connection), then the peripheral device 104 to which node device 102 is connected is gateway device 104, and node device 102 assigns itself the role of convergence node 102a in step 420. Otherwise, if the connection data obtained in step 410 does not indicate a connection to gateway device 104, then in step 415, node device 102 provides the obtained connection data to gateway device 104. If, in step 430, the obtained connection data indicates a connection to sensor device 106 associated with the personnel conveyor, then the assigned role of node device 102 is sensor node 102b role 440. In other words, if the connection data obtained in step 430 indicates that node device 102 is connected to sensor device 106 associated with the personnel conveyor, then gateway device 104 assigns sensor node 102b role 440 to node device 102. The connection between node devices 102, 102b, indicated by the obtained connection data, and the sensor device 106 associated with the personnel conveyor can be provided via a second type of serial port connection. This second type of serial port connection can be, for example, but not limited to, analog connections, RS-232 connections, RS-485 connections, and internal integrated circuits (I...). 2 C) Connection and / or Serial Peripheral Interface (SPI) connection. In other words, if the obtained connection data indicates that node device 102 is connected to peripheral device 106 via a second type of serial port connection, then the peripheral device 106 to which node device 102 is connected is a sensor device 106 related to the personnel conveyor, and gateway device 104 assigns a sensor node 102b role to node device 102 in step 440. According to a non-limiting example, some temperature sensor devices can be connected via I... 2The C connection is connected to the node device. According to another non-limiting example, UART devices, Modbus-based devices, some energy meter devices, some temperature sensor devices, etc., can be connected to the node device, for example, via an RS-485 connection. According to yet another non-limiting example, some temperature sensor devices can be connected to the node device via an analog connection. Alternatively, if the connection data obtained in step 450 indicates that node device 102 is not connected to any peripheral devices 104, 106, then the assigned role of node device 102 is router node 102c role 460. In other words, if the obtained connection data indicates that node device 102 is not connected to any peripheral devices 104, 106, then gateway device 104 assigns router node 102c role 460 to node device 102. After assigning the operating role of node device 102 in step 440 or step 460, gateway device 104 can also notify node device 102 of the assigned operating role, such as sensor node 102b role or router node 102c role.

[0056] As described above, node device 102 can obtain connection data by scanning (i.e., probing) one or more communication interfaces (i.e., connection interfaces) of node device 102. In other words, node device 102 can scan one or more communication interfaces of node device 102 one after another to obtain connection data. According to the example, node device 102 can perform a scan in response to receiving a scan command from gateway device 104. The scan can include passive scanning and / or active scanning of one or more communication interfaces of node device 102. Passive scanning can include obtaining connection data via one or more communication interfaces of node device 102. Active scanning can include providing (i.e., inputting) request data via one or more communication interfaces of node device 102, and obtaining connection data via one or more communication interfaces of node device 102 in response to the provided request data. Request data can include general request data, port-specific request data, and / or device-specific request data. As described above, if node device 102 is connected to peripheral devices 104, 106, the obtained connection data may, for example, include information indicating possible connections from node device 102 to peripheral devices 104, 106 and / or identification information enabling the identification of peripheral devices 104, 106 connected to node device 102. The scan type used (i.e., passive and / or active) may depend on the connection type and / or type of peripheral devices 104, 106 connected to node device 102.

[0057] According to the example, passive scanning can be used to define whether node device 102 is connected to gateway device 104. In other words, node device 102 can use passive scanning to obtain connection data indicating that node device 102 is connected to gateway device 104 via a first-type serial port connection (i.e., USB connection).

[0058] According to another example, passive scanning can be used to define whether node device 102 is connected via an analog connection or I / O. 2 The C-connection is connected to one or more sensor devices 106 associated with the personnel conveyor. In other words, the node device 102 can use passive scanning to acquire connection data, which indicates that the node device 102 is connected via an analog connection or an I-connection. 2 The C-connection is connected to sensor device 106 associated with the personnel conveyor. Node device 102 can, for example, record analog connections, such as analog pins, to obtain connection data via analog connections. For example, a number of temperature sensor devices connected to node device 102 via analog connections can have a half-supply bias depending on the type of temperature sensor device, which can be used as identification information to identify peripheral devices 104, 106 connected to node device 102. Alternatively or additionally, node device 102 can, for example, wait for I-connection... 2 C-connection (e.g., I) 2 The acknowledgment (ACK) response from the C bus is used as connection data.

[0059] According to another example, active scanning can be used to define whether node device 102 is connected to the personnel conveyor-related sensor device 106 via an RS-485 connection or an SPI port connection. In other words, node device 102 can use active scanning to obtain connection data indicating that node device 102 is connected to the personnel conveyor-related sensor device 106 via an RS-485 connection or an SPI connection. Node device 102 can input request data, such as device-specific data or RS-485 port-specific request data, for example via an RS-485 connection (e.g., an RS-485 bus), and obtain connection data via the RS-485 connection in response to the input request data. Alternatively or additionally, node device 102 can input request data, such as device-specific data or SPI port-specific request data, for example via an SPI connection (e.g., an SPI bus), and obtain connection data via the SPI connection in response to the input request data.

[0060] According to the example, a scan may include scanning one or more communication interfaces of node device 102 in a predefined sequence. The predefined sequence may be defined by node device 102 itself or by gateway device 104. If the predefined sequence is defined by gateway device 104, the predefined sequence may be included in a scan command generated for node device 102 to perform the scan according to the predefined sequence. The predefined sequence may include all or more communication interfaces of node device 102. Alternatively, the predefined sequence may include at least some of the one or more communication interfaces of node device 102. According to a non-limiting example, the sequence may be, but is not limited to, USB connections, RS-485 connections, analog connections, I / O connections, etc. 2 USB and SPI connections. In other words, node device 102 can first scan for USB connections, then RS-485 connections, and so on.

[0061] Figure 5 An example of the method is illustrated schematically, wherein after assigning a role to sensor node 102b in step 440, gateway device 104 can further determine 510 the type of personnel conveyor-related sensors 106 connected to node device 102b. For example, the determination in step 510 can be based on acquired connectivity data, such as identification information of the personnel conveyor-related sensors 106 included in the acquired connectivity data. In other words, the type of personnel conveyor-related sensors 106 connected to node devices 102, 102b can be defined, for example, based on identification information included in the acquired connectivity data. Alternatively or additionally, if connectivity data is obtained as described above by scanning one or more communication interfaces of node device 102, the determination in step 510 can be based on the connectivity data obtained during the scan. Gateway device 104 can also obtain 520 application software via a wireless update system, the application software corresponding to the determined type of personnel conveyor-related sensor devices 106 connected to node devices 102, 102b. In other words, in response to determining the type of sensor 106 associated with the personnel conveyor connected to node devices 102 and 102b, gateway device 104 can also obtain application software corresponding to the identification information of the sensor device 106 associated with the personnel conveyor connected to node devices 102 and 102b via a wireless update system. According to a non-limiting example, the wireless update system may be an over-the-air (OTAP) update system. Gateway device 104 can also provide the obtained application software to node device 102, the application software corresponding to the identification information of the sensor device 106 associated with the personnel conveyor connected to node devices 102 and 102b. After obtaining the application software, node devices 102 and 102b can update their software based on the obtained application software.

[0062] Figure 6Examples of components of node devices 102, 102a-102c are schematically shown. Node devices 102, 102a-102c may include a processing unit 610 containing one or more processors, a memory unit 620 containing one or more memories, a communication interface unit 630 containing one or more communication devices, and possibly a user interface (UI) unit 640. The aforementioned components may be communicatively connected to each other via, for example, an internal bus. The memory unit 620 may store and maintain portions of a computer program (code) 625 and any other data, such as acquired connection data, identification information of peripheral devices 104, 106, and / or acquired application software. The computer program 625 may include instructions that, when executed by the processing unit 610 of node devices 102, 102a-102c, cause the processing unit 610 and node devices 102, 102a-102c to perform desired tasks, such as operation of node devices 102, 102a-102c and / or at least some of the above-described method steps. Therefore, the processing unit 610 can be arranged to access the memory unit 620 and retrieve and store any information in the memory unit 620. For clarity,

[0063] The processor referred to herein is any unit suitable for processing the operation of information and control node devices 102, 102a-102c, and other tasks. These operations can also be implemented using a microcontroller solution with embedded software. Similarly, memory unit 620 is not limited to a specific type of memory, but any type of memory suitable for storing the described information segments can be applied in the context of this invention. As described above, communication interface unit 630 provides one or more communication interfaces for communicating with any other unit, such as peripheral devices 104, 106 of the personnel conveyor system 110, one or more other node devices 102, 102a-102c of the mesh network, and / or any other unit. Communication interface unit 630 may include one or more communication devices, such as at least one radio transceiver, at least one antenna, at least one communication port, etc. User interface unit 640 may include one or more input / output (I / O) devices, such as buttons, keyboards, touchscreens, microphones, speakers, displays, etc., for receiving user input and output information. Computer program 625 may be a computer program product, which may be contained in a tangible, non-volatile (non-transitory) computer-readable medium carrying embedded computer program code 625 for use with a computer (i.e., node devices 102, 102a-102c). Node devices 102, 102a-102c may be powered by a power source, such as a wall plug. Alternatively, node devices 102, 102a-102c may be powered by one or more batteries; that is, node devices 102, 102a-102b may be battery powered.

[0064] Figure 7Examples of components of gateway device 104 are schematically illustrated. Gateway device 104 may include a processing unit 710 containing one or more processors, a memory unit 720 containing one or more memories, a communication interface unit 730 containing one or more communication devices, and possibly a user interface (UI) unit 740. The aforementioned components may be communicatively connected to each other, for example, via an internal bus. Memory unit 720 may store and maintain portions of computer program (code) 725 and any other data, such as acquired connection data, identification information of peripheral device 106, and / or acquired application software. Computer program 725 may include instructions that, when executed by processing unit 710 of gateway device 104, may cause processing unit 710 and gateway device 104 to perform desired tasks, such as operating gateway device 104 and / or at least some of the above-described method steps. Therefore, processing unit 710 may be arranged to access memory unit 720 and retrieve and store any information in memory unit 720. For clarity, processor herein refers to any unit suitable for processing information and controlling the operation of gateway device 104 and other tasks. These operations can also be implemented using a microcontroller solution with embedded software. Similarly, memory unit 720 is not limited to a specific type of memory, but any type of memory suitable for storing the described information segments can be applied in the context of this invention. Communication interface unit 730 provides one or more communication interfaces for communicating with any other unit, such as node devices 102, 102a and / or any other unit of the personnel conveyor system 110. Communication interface unit 730 may include one or more communication devices, such as at least one radio transceiver, at least one antenna, at least one communication port, etc. User interface unit 740 may include one or more input / output (I / O) devices, such as buttons, keyboards, touch screens, microphones, speakers, displays, etc., for receiving user input and output information. Computer program 725 may be a computer program product, which may be contained in a tangible, non-volatile (non-transitory) computer-readable medium carrying embedded computer program code 725 for use with a computer (i.e., gateway device 104). Gateway device 104 may be powered by a power source, such as a wall plug. Alternatively, the gateway device 104 may be powered by one or more batteries, i.e., the gateway device 104 may be battery powered.

[0065] The monitoring system 100 and method discussed above make it easy and simple to add new node devices 102 to the monitoring system 100 and / or replace faulty node devices of the monitoring system 100 with new node devices 102. The new node device 102 can be a generic node device, such as a generic radio dongle. The role assignment of the node device 102 can then be performed locally by the node device 102 itself and / or the gateway device 104 by assigning (i.e., identifying) the operational role of the node device, for example, by using prior information obtained as user input or by scanning the peripheral devices 104, 106 connected to the node device 102 as described above.

[0066] The specific examples provided in the description above should not be construed as limiting the applicability and / or interpretation of the appended claims. Unless otherwise expressly stated, the list and groups of examples provided in the description above are not exhaustive.

Claims

1. A monitoring system (100) for monitoring a personnel conveyor system (110, 110a-110c), wherein the monitoring system (100) includes a wireless mesh network (105), the wireless mesh network including multiple node devices (102a-102c) and one or more peripheral devices (104, 106) of the personnel conveyor system (110, 110a-110c). The node device (102) joining the wireless mesh network (105) is configured as follows: Obtain connection data, which represents the connection between the node device (102) and the peripheral devices (104, 106) of the personnel conveyor system (110, 110a-110c), and If the obtained connection data indicates a connection to the gateway device (104), then the gateway device (104) is assigned the role of a convergence node (102a), wherein the gateway device (104) is deployed to the personnel conveyor system (110, 110a-110c), and wherein, The gateway device (104) is included in the peripheral devices (104, 106), or Otherwise, the obtained connection data is provided to the gateway device (104), wherein the gateway device (104) is configured to: Based on the obtained connection data, an operation role is assigned to the node device (102), wherein: If the obtained connection data indicates a connection to a sensor device (106) associated with the personnel conveyor, the assigned role is a sensor node (102b) role, wherein the sensor device (106) associated with the personnel conveyor is configured to obtain sensor data representing the status of the personnel conveyor system (110, 110a-110c), and wherein the sensor device (106) associated with the personnel conveyor system is included in the peripheral devices (104, 106); or If the obtained connection data indicates that the node device (102) is not connected to any peripheral device (104, 106) of the personnel conveyor system (110, 110a-110c), the assigned role is router node (102c).

2. The monitoring system (100) according to claim 1, wherein after assigning the sensor node (102b) role to the node device (102), the gateway device (104) is further configured to: Determine the type of sensor device (106) associated with the personnel conveyor connected to the node devices (102, 102b), and Application software is obtained via a wireless update system, the application software corresponding to a determined type of sensor device (106) associated with the personnel conveyor connected to the node devices (102, 102b).

3. The monitoring system (100) according to any one of the preceding claims, wherein the connection from the node device (102, 102a) to the gateway device (104) indicated by the obtained connection data is provided via a first type serial port connection, wherein the first type serial port connection is a Universal Serial Bus (USB) connection.

4. The monitoring system (100) according to claim 1 or 2, wherein the connection from the node device (102, 102b) indicated by the obtained connection data to the sensor device (106) associated with the personnel conveyor is provided via a second type of serial port connection, wherein the second type of serial port connection is an analog connection, an RS-232 connection, an RS-485 connection, or an internal integrated circuit (I... 2 C) Connection and / or Serial Peripheral Interface (SPI) connection.

5. The monitoring system (100) according to claim 1, wherein the node device (102) is configured to obtain the connection data by scanning one or more communication interfaces of the node device (102).

6. The monitoring system (100) according to claim 5, wherein the scanning includes at least obtaining connection data via one or more communication interfaces of the node device (102).

7. The monitoring system (100) according to claim 5 or 6, wherein the scanning includes providing request data via the one or more communication interfaces, and in response to providing request data, obtaining the connection data via one or more communication interfaces of the node device (102).

8. The monitoring system (100) according to claim 1 or 2, wherein the node device (102) is configured to obtain the connection data as user input.

9. The monitoring system (100) according to claim 1 or 2, wherein the sensor devices (106) related to the personnel conveyor include hydraulic sensor devices, door sensor devices, water presence sensor devices, light level sensor devices, human presence sensor devices, vibration sensor devices, temperature sensor devices, energy meter devices or universal asynchronous transceiver (UART) devices.

10. The monitoring system (100) according to claim 1, wherein the personnel conveyor system (110, 110a-110c) is an elevator system (110a), an escalator system (110b), or a moving walkway system (110c).

11. A method for monitoring a personnel conveyor system (110, 110a-110c), wherein the method comprises: (310) Connection data is obtained, the connection data representing the connection between the node device (102) joining the wireless mesh network (105) and the peripheral devices (104, 106) of the personnel conveyor system (110, 110a-110c), and Based on the obtained connection data, assign (320) operation roles, where: If the obtained connection data indicates (410) a connection to the gateway device (104), the assigned role is the aggregation node (102a) role (420), wherein the gateway device (104) is arranged to the personnel conveyor system (110, 110a-110c). If the obtained connection data indicates (430) a connection to a sensor device (106) associated with the personnel conveyor, the assigned role is a sensor node (102b) role (440), wherein the sensor device (106) associated with the personnel conveyor is configured to obtain sensor data representing the status of the personnel conveyor system (110, 110a-110c); or If the obtained connection data indicates (450) that the node device (102) is not connected to any peripheral device (104, 106) of the personnel conveyor system (110, 110a-110c), the assigned role is router node (102c) role (460).

12. The method of claim 11, wherein after assigning (320) the role of the sensor node (102b), the method further comprises: Determine (510) the type of sensor device (106) related to the personnel conveyor connected to the node devices (102, 102b), and Application software (520) is obtained via a wireless update system, the application software corresponding to the type of sensor device (106) associated with the personnel conveyor connected to the node devices (102, 102b).

13. The method of claim 11 or 12, wherein the connection from the node device (102, 102a) to the gateway device (104) indicated by the obtained connection data is provided via a first type of serial port connection, wherein the first type of serial port connection is a Universal Serial Bus (USB) connection.

14. The method according to claim 11 or 12, wherein the connection from the node device (102, 102b) indicated by the obtained connection data to the sensor device (106) associated with the personnel conveyor is provided via a second type of serial port connection, wherein the second type of serial port connection is an analog connection, an RS-232 connection, an RS-485 connection, or an internal integrated circuit (I... 2 C) Connection and / or Serial Peripheral Interface (SPI) connection.

15. The method of claim 11, wherein the connection data is obtained by scanning one or more communication interfaces of the node device (102).

16. The method of claim 15, wherein the scanning at least includes obtaining connection data via one or more communication interfaces of the node device (102).

17. The method of claim 15 or 16, wherein the scanning includes providing request data via the one or more communication interfaces, and in response to providing the request data, obtaining the connection data via one or more communication interfaces of the node device (102).

18. The method of claim 11 or 12, wherein the connection data is obtained as user input.

19. The method according to claim 11 or 12, wherein the sensor device (106) associated with the personnel conveyor includes a hydraulic sensor device, a door sensor device, a water presence sensor device, a light level sensor device, a human presence sensor device, a vibration sensor device, a temperature sensor device, an energy meter device, or a universal asynchronous transceiver (UART) device.

20. The method according to claim 11, wherein the personnel conveyor system (110, 110a-110c) is an elevator system (110a), an escalator system (110b), or a moving walkway system (110c).

21. A personnel conveyor system (110, 110a-110c) comprising a monitoring system (100) according to any one of claims 1 to 10.

Images