TECHNICAL FIELD

The invention concerns in general the technical field of people conveyor systems. Especially the invention concerns people conveyor related data collection.

BACKGROUND

Typically, people conveyor systems, such as elevator systems or escalator systems, may comprise a plurality of different sensor devices for collecting various people conveyor system related sensor data. The collected sensor data may for example be used for monitoring and maintenance purposes of the people conveyor system, for example for a predictive maintenance of a machinery of the people conveyor system. Typically, the machinery of the people conveyor system repeats the same cycles over and over again. Thus, the sensor data collected from the same cycles at different times may be analyzed and compared. However, the load (e.g. passengers, goods, and/or freight) being carried by a conveyor entity of the people conveyor system (e.g. an elevator car in the elevator system or steps arranged to an endless conveyor band in the escalator system) has an effect on the operation of the machinery of the people conveyor system, for example as an additional weight the machinery needs to carry and/or in the elevator systems as a source of randomness in travel distances. Therefore, to be able to reliably monitor the sensor data collected at different times the sensor data needs to be collected only when it is known that the conditions are repeatable.

By collecting sensor data continuously time variations, for example due to the load, may be averaged out. However, the continuous collection of the sensor data with a high sampling rate may not be possible in all situations, for example from devices connected with low-bandwidth links to a cloud or from devices that have data transmission quotas. The high sampling rate may be necessary for example if rapid vibrations and/or momentary variations need to be detected from the collected sensor data.

Therefore, there is a need to develop further solutions for collecting people conveyor related sensor data. SUMMARY

The following presents a simplified summary in order to provide basic understanding of some aspects of various invention embodiments. The summary is not an extensive overview of the invention. It is neither intended to identify key or critical elements of the invention nor to delineate the scope of the invention. The following summary merely presents some concepts of the invention in a simplified form as a prelude to a more detailed description of exemplifying embodiments of the invention.

An objective of the invention is to present a method for collecting people conveyor system related sensor data from a people conveyor system, a people conveyor data collection system, and a conveyor system. Another objective of the invention is that the method and the people conveyor data collection system, and the conveyor system enable on demand collection of the people conveyor related sensor data from the people conveyor system.

The objectives of the invention are reached by a method, a people conveyor data collection system, and a conveyor system as defined by the respective independent claims.

According to a first aspect, a method for collecting people conveyor system related sensor data from a people conveyor system is provided, wherein the method comprises: detecting an upcoming predefined operation event of the people conveyor system; generating at least one trigger signal to at least one sensor unit to collect people conveyor system related sensor data with a predefined type from the people conveyor system during the detected upcoming predefined operation event of the people conveyor system; and receiving the collected people conveyor related sensor data with the predefined type from the at least one sensor unit.

The method may further comprise receiving from the at least one sensor unit people conveyor system related sensor data with at least one second type, wherein the at least one second type may differ from the predefined type, and wherein the people conveyor system related sensor data with the at least one second type may be collected by the at least one sensor unit at any other time than during the detected upcoming predefined operation event of the people conveyor system. The generated at least one trigger signal may comprise: a first instruction to start collecting the people conveyor system related sensor data with the predefined type at the start of the upcoming predefined operation event of the people conveyor system and a second instruction to stop collecting the people conveyor related sensor data with the predefined type at the end of the upcoming predefined operation event of the people conveyor system; an instruction to collect the people conveyor system related sensor data with the predefined type during a predetermined time duration of the upcoming predefined operation event of the people conveyor system; or collect data signals generated as long as the upcoming predefined operation event of the people conveyor system is ongoing, wherein the collect data signals comprise an instruction to collect the people conveyor system related sensor data with the predefined type.

Alternatively or in addition, the method may further comprise providing the collected people conveyor related sensor data with the predefined type to a cloud computing unit for further processing and/or analyzing.

The method may further comprise incorporating respective metadata into the collected people conveyor related sensor data with the predefined type to be provided to the cloud computing unit.

Alternatively or in a addition, the method may further comprise checking a time elapsed from a previous collection of the people conveyor related sensor data with the predefined type from the at least one sensor unit and generating the at least one trigger signal to the at least one sensor unit, if the time elapsed meets a predefined time limit.

The upcoming predefined operation event of the people conveyor system may comprise a specific movement cycle of the conveyor entity or a specific movement cycle of any other entity of the people conveyor system than the conveyor entity.

Alternatively or in addition, the upcoming predefined operation event may be detected: in response to receiving a request to perform the predefined operation event, by defining a suitable moment for performing the predefined operation event, and/or according to a predefined schedule.

Alternatively or in a addition, the method may further comprise: obtaining from at least one occupancy detection unit occupancy status data representing oc- cupancy status of a conveyor entity of the people conveyor system; detecting a predefined status of the conveyor entity based on the obtained occupancy status data; and generating the at least one trigger signal to the at least one sensor unit, if the predefined status of the conveyor entity is detected.

The detected predefined status of the conveyor entity may be that the conveyor entity is empty or the conveyor entity carries a known load.

Alternatively or in addition, the method may further comprise: obtaining condition data representing the current conditions of the people conveyor system; detecting whether the obtained condition data corresponds to a predefined condition limit or a predefined condition range; and generating the at least one trigger signal to the at least one sensor unit, if it is detected that the obtained condition data corresponds to the predefined condition limit or to the predefined condition range.

According to a second aspect, a people conveyor data collection system of a people conveyor system is provided, wherein the people conveyor data collection system comprises: at least one sensor unit for collecting people conveyor system related sensor data from the people conveyor system, and a conveyor control system configured to: detect an upcoming predefined operation event of the people conveyor system; and generate at least one trigger signal to the at least one sensor unit to collect people conveyor system related sensor data with a predefined type during the detected upcoming predefined operation event of the people conveyor system; and receive the collected people conveyor related sensor data with the predefined type from the at least one sensor unit.

The conveyor control unit may further be configured to receive from the at least one sensor unit people conveyor system related sensor data with at least one second type, wherein the at least one second type may differ from the predefined type, and wherein the people conveyor system related sensor data with the at least one second type may be collected by the at least one sensor unit at any other time than during the detected upcoming predefined operation event of the people conveyor system.

The generated at least one trigger signal may comprise: a first instruction to start collecting the people conveyor system related sensor data with the predefined type at the start of the upcoming predefined operation event of the peo- pie conveyor system and a second instruction to stop collecting the people conveyor related sensor data with the predefined type at the end of the upcoming predefined operation event of the people conveyor system; an instruction to collect the people conveyor system related sensor data with the predefined type during a predetermined time duration of the upcoming predefined operation event of the people conveyor system; or collect data signals generated as long as the upcoming predefined operation event of the people conveyor system is ongoing, wherein the collect data signals comprise an instruction to collect the people conveyor system related sensor data with the predefined type.

Alternatively or in addition, the conveyor control system may further be configured to provide the collected people conveyor related sensor data with the predefined type to a cloud computing unit for further processing and/or analyzing.

The conveyor control system may further be configured to incorporate respective metadata into the collected people conveyor related sensor data with the predefined type to be provided to the cloud computing unit.

Alternatively or in addition, the conveyor control system may further be configured to check a time elapsed from a previous collection of the people conveyor related sensor data with the predefined type from the at least one sensor unit and generate the at least one trigger signal to the at least one sensor unit, if the time elapsed meets a predefined time limit.

The upcoming predefined operation event of the people conveyor system may comprise a specific movement cycle of the conveyor entity or a specific movement cycle of any other entity of the people conveyor system than the conveyor entity.

Alternatively or in addition, the upcoming predefined operation event may be detected: in response to receiving a request to perform the predefined operation event, by defining a suitable moment for performing the predefined operation event, and/or according to a predefined schedule.

Alternatively or in a addition, the people conveyor system may further comprise at least one occupancy detection unit configured to provide occupancy status data representing occupancy status of a conveyor entity of the people conveyor system, wherein the conveyor control system may further be configured to: obtain from the at least one occupancy detection unit the occupancy status data; detect a predefined status of the conveyor entity based on the obtained occupancy status data; and generate the at least one trigger signal to the at least one sensor unit, if the predefined status of the conveyor entity is detected.

The detected predefined status of the conveyor entity may be that the conveyor entity is empty or the conveyor entity carries a known load.

Alternatively or in addition, the conveyor control system may further be configured to: obtain condition data representing the current conditions of the people conveyor system; detect whether the obtained condition data corresponds to a predefined condition limit or a predefined condition range; and generate the at least one trigger signal to the at least one sensor unit, if it is detected that the obtained condition data corresponds to the predefined condition limit or to the predefined condition range.

According to a third aspect, a people conveyor system is provided, wherein the people conveyor system comprises the people conveyor data collection system discussed above.

The people conveyor system may be an elevator system or an escalator system.

Various exemplifying and non-limiting embodiments of the invention both as to constructions and to methods of operation, together with additional objects and advantages thereof, will be best understood from the following description of specific exemplifying and non-limiting embodiments when read in connection with the accompanying drawings.

The verbs “to comprise” and “to include” are used in this document as open limitations that neither exclude nor require the existence of unrecited features. The features recited in dependent claims are mutually freely combinable unless otherwise explicitly stated. Furthermore, it is to be understood that the use of “a” or “an”, i.e. a singular form, throughout this document does not exclude a plurality.

BRIEF DESCRIPTION OF FIGURES

The embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings. Figure 1 illustrates schematically an example of a people conveyor data collection system of a people conveyor system.

Figure 2 illustrates schematically an example of an implementation of a people conveyor data collection system in an elevator system.

Figure 3 illustrates schematically an example of an implementation of a people conveyor data collection system in an escalator system.

Figure 4A illustrates schematically an example of a method for collecting people conveyor system related sensor data from a people conveyor system.

Figures 4B-4D illustrate schematically other examples of the method.

Figure 5 illustrate schematically yet another example of the method.

Figure 6 illustrates schematically an example of components of a conveyor control system.

DESCRIPTION OF THE EXEMPLIFYING EMBODIMENTS

Figure 1 illustrates schematically an example of a people conveyor data collection system 100 of a people conveyor system 200, 300. The people conveyor data collection system 100 comprises at least one sensor unit 120, and a conveyor control system 130. The at least one sensor unit 120 is configured to collect people conveyor system related sensor data from the people conveyor system 200, 300. The at least one sensor unit 120 may be communicatively coupled to the conveyor control system 130. The communication between the at least one sensor unit 120 and the conveyor control system 130 may be based on one or more known communication technologies, either wired or wireless. The at least one sensor unit 120 may for example, but not limited to, comprise at least one humidity sensor, at least one temperature sensor, at least one air pressure sensor, at least one carbon dioxide (CO2) sensor, at least one odor sensor, at least one acceleration sensor, at least one inclinometer, at least one magnetometer, at least one microphone, at least one camera, at least one radar, at least one passive infrared (PIR) sensor, at least one infrared (IR) sensor, at least one movement detector, and/or at least one proximity sensor. Preferably, the at least one sensor unit 120 may comprise at least one sensor unit with a high sampling frequency (i.e. a high sampling rate), e.g. at least one accelerometer, at least one microphone, at least one camera, and/or at least one radar, etc.. The people conveyor system related data collected with the at least one sensor unit 120 depends on the type of the at least one sensor unit 120. The people conveyor data collection system 100 may further comprise at least one occupancy detection unit 110. The at least one occupancy detection unit 110 may be configured to provide occupancy status data representing occupancy status of a conveyor entity of the people conveyor system 200, 300. The at least one occupancy detection unit 110 may be communicatively coupled to the conveyor control system 130. The communication between the at least one occupancy detection unit 110 and the conveyor control system 130 may be based on one or more known communication technologies, either wired or wireless. Alternatively or in addition, according to an example, the people conveyor data collection system 100 may further comprise a cloud computing unit 140. The cloud computing unit 140 may be communicatively coupled to the conveyor control system 130. The communication between the cloud computing unit 140 and the conveyor control system 130 may be based on one or more known communication technologies, either wired or wireless.

The people conveyor system 200, 300 may be an elevator system 200 or an escalator system 300. In other words, the people conveyor data collection system 100 may be implemented in the elevator system 200 for collecting data from the elevator system 200 or in the escalator system for collecting data from the escalator system 300. The people conveyor system 200, 300 comprises a conveyor entity 202, 302 and the conveyor control system 130. The people conveyor system 200, 300 may further comprise the people conveyor data collection system 100.

Figure 2 illustrates an example of an implementation of the people conveyor data collection system 100 in the elevator system 200. The elevator system 200 comprises at least one elevator car 202 configured to travel along a respective at least one elevator shaft 204 between a plurality of landings, i.e. floors, 206a-206n and an elevator control system, e.g. an elevator control unit. In the elevator system implementation of the people conveyor data collection system 100, the at least one elevator car 202 is the conveyor entity and the elevator control system is the conveyor control system 130. The elevator system 200 of the example of Figure 2 comprises one elevator car 202 travelling along one elevator shaft 204, however the elevator system 200 may also comprise an elevator group, i.e. group of two or more elevator cars 202 each travelling along a separate elevator shaft 204 configured to operate as a unit serving the same landings 206a-206n. The conveyor control system 130 may be configured to control the operation of the elevator system 200 at least in part. The conveyor control system 130 may reside e.g. in a machine room (for sake of the clarity not shown in Figure 2) or in one of the landings 206a-206n of the elevator system 200. The elevator system 200 may further comprise one or more other known elevator related entities, e.g. hoisting system, user interface devices, safety circuit and devices, elevator brakes, elevator doors, etc., which are not shown in Figure 2 for sake of clarity. In the elevator system implementation of the people conveyor data collection system 100, the at least one sensor unit 120 may be arranged anywhere within the elevator system 200. In the example of Figure 2, the at least one sensor unit 120 of the people conveyor data collection system 100 comprises a first sensor unit 120a (e.g. an acceleration sensor) arranged to a rooftop of the elevator car 202 and a second sensor unit 120b (e.g. a microphone) arranged inside the elevator shaft 204. This is only one non-limiting example of the implementation of the at least one sensor unit 120 in the elevator system implementation of the people conveyor data collection system 100. In the elevator system implementation of the people conveyor data collection system 100, the at least one occupancy detection unit 110 may comprise a load weighting device 110a and/or at least one sensorbased device 110b, e.g. at least one PIR device, at least one time-of-flight (TOF) sensor device, at least one radar device, and/or at least one optical imaging device (e.g. a camera and/or a video camera). The at least one occupancy detection unit 110 implemented as the at least one sensor-based device 110b may be arranged inside the elevator car 202 to be able to provide the occupancy status data of the elevator car 202 from inside the elevator car 202. In the example of Figure 2, the at least one occupancy detection unit 110 of the people conveyor data collection system 100 comprises the load weighting device 110a and one sensor-based device 110b. This is only one non-limiting example of the implementation of the at least one occupancy detection unit 110 in the elevator system implementation of the people conveyor data collection system 100.

Figure 3 illustrates an example of an implementation of the people conveyor data collection system 100 in the escalator system 300. The escalator system 300 comprises the conveyor entity 302 comprising steps arranged to an endless conveyor band, which is carried by a truss, and an escalator control sys- tem, e.g. an escalator control unit. In the escalator implementation of the people conveyor data collection system 100, the escalator control system is the conveyor control system 130. The conveyor control system 130 may be configured to control the operation of the escalator system 300 at least in part. The conveyor control system 130 may for example be arranged to one of the platforms 304, 306 of the escalator system 300. In the example of Figure 3 the conveyor control system 130 is arranged to a first platform, e.g. a top platform, 304 of the escalator system 300. Alternatively, the conveyor control system 130 may be arranged for example to a second platform, e.g. a bottom platform, 306 of the escalator system 300. The escalator system 300 may further comprise one or more other known escalator related entities, e.g. a driving machine, etc., which are not shown in Figure 3 for sake of clarity. In the escalator implementation of the people conveyor data collection system 100, the at least one sensor unit 120 may be arranged anywhere within the escalatory system 300. In the example of Figure 3, the at least one sensor unit 120 of the people conveyor data collection system 100 comprises one sensor unit 120 (e.g. a microphone) arranged to the second platform 306 of the escalator system 300. This is only one non-limiting example of the implementation of the at least one sensor unit 120 in the escalator system implementation of the people conveyor data collection system 100. In the escalator implementation of the people conveyor data collection system 100, the at least one occupancy detection unit 110 may comprise at least one sensor-based detection system, e.g. a photo- cell-based detection system a radar-based detection system, a PIR -based detection system, and/or a TOF sensor-based detection system; and/or at least one imaging device -based detection system, e.g. a camera-based detection system. The at least one optical imaging device -based detection system may for example comprise an optical imaging device, e.g. a camera, capturing image data covering the whole conveyor entity 302 and a processing unit for detecting passengers travelling on the conveyor entity 302 based on the image data provided by the optical imaging device. The at least one occupancy detection unit 110 of the escalator system 300 may also be used in the escalator system 300 for passenger detection in an activation and/or a deactivation of an energy saving mode of the escalator system 300, i.e. a standby mode of the escalator system 300. In the energy saving mode of the escalator system 300, the escalator control system 130 may be configured to control the conveyor entity 302 to run at a reduced speed, i.e. at a standby speed, or to stop the operation of the conveyor entity 302. Typically, the energy saving mode of the escalator system 300 may be activated in response to detecting with the at least one occupancy detection unit 110 of the escalator system 300 that the conveyor entity 302 is empty of passengers. The energy saving mode of the escalator system 300 may then be deactivated in response to detecting with the at least one occupancy detection unit 110 of the escalator system 300 that at least one passenger is entering the conveyor entity 302 of the escalator system 300. Preferably at least one occupancy detection unit 110 implemented as the at least one sensor-based detection system is arranged to each platform 304, 306 of the escalator system 300. For sake of clarity, the at least one occupancy detection unit 110 is not shown in the example of Figure 3. The expression “escalator system” used in this patent application covers also moving walk systems. The moving walk system is otherwise similar to the escalator system 300 described above referring to Figure 3, but the conveyor entity of the moving walk system comprises pallets arranged to the endless conveyor band. Thus, everything disclosed above referring to the escalator system 300 above applies also to the moving walk system. The moving walk system may be an inclined moving walk system, i.e. a moving walk system configured to convey people and/or goods across an inclined plane, e.g. between two platforms. Alternatively, the mowing walk system may be a horizontal moving walk system, i.e. a moving walk system configured to convey people and/or goods across a horizontal plane, e.g. between two platforms.

Next an example of a method for collecting people conveyor system related sensor data from the people conveyor system 200, 300 is described by referring to Figure 4A. Figure 4A schematically illustrates the example of the method as a flow chart.

At a step 410, the conveyor control system 130 detects an upcoming predefined operation event of the people conveyor system 200, 300. The upcoming predefined operation event of the people conveyor system 200, 300 may for example comprise a specific movement cycle of the conveyor entity 202, 302 or a specific movement cycle of any other entity of the people conveyor system than the conveyor entity 202, 302. In the elevator system implementation of the people conveyor data collection system 100, the upcoming predefined operation event of the people conveyor system 200 may for example comprise a specific movement cycle of the elevator car 202, a closing event and/or an opening event of an elevator brake, a specific movement cycle of an elevator door (e.g. opening of the elevator and/or closing of the elevator door). In the escalator system implementation of the people conveyor data collection system 100, the upcoming predefined operation event of the people conveyor system 300 may for example comprise a full movement cycle of the steps around the conveyor band, a heavy load operation of the escalator system 300 (i.e. when there are a large amount of passengers travelling on the conveyor entity 302), and/or emergency stop of the escalator system 300. The expression “upcoming predefined operation event of the people conveyor system” may be used in this patent application to mean a predefined operation event that is going to occur in the future, preferably in the near future. For example, the upcoming predefined operation event of the people conveyor system 200, 300 may be the next operation of the people conveyor system 200, 300. According to an example, the upcoming predefined operation event of the people conveyor system 200, 300 may be detected for example in response to receiving a request to perform the predefined operation event. For example, in the elevator system implementation of the people conveyor data collection system 100, the conveyor control system 130 may receive a request to move the elevator car 202 according to a specific movement cycle, e.g. between desired landings 206a-206n into a desired direction. Preferably, the upcoming predefined operation event is a part of a normal operation mode of the people conveyor system 200, 300. In other words, the upcoming predefined operation event may preferably not be a part of a maintenance mode and/or an inspection mode of the people conveyor system 200, 300. The request may for example be received in response a user interaction, e.g. an elevator call is generated via an elevator user interface device, e.g. an elevator button. Alternatively or in addition, in the elevator system implementation of the people conveyor data collection system 100, the conveyor control system 130 may receive a request to open and/or close the elevator door and/or a request to open and/or close the elevator brake. For example, in the escalator system implementation of the people conveyor data collection system 100, the conveyor control system 130 may receive a request to move the conveyor entity 302 after the energy saving mode in response to detecting with the at least one occupancy detection unit 110 of the escalator system 300 that at least one passenger is entering the conveyor entity 302 of the escalator system 300. According to another example, the upcoming predefined operation event of the people conveyor system 200, 300 may alternatively or in addition be detected for example by defining a suitable moment for performing the predefined operation event. The suitable moment may for example be a time, when an occupancy rate of the people conveyor system 200, 300 is detected to be low. The conveyor control system 130 may for example control the people conveyor system 200, 300 to perform the predefined operation event in response to defining the suitable moment for performing the predefined operation event. According to yet another example, the upcoming predefined operation event of the people conveyor system 200, 300 may alternatively or in addition be detected for example according to a predefined schedule. The conveyor control system 130 may for example control the people conveyor system 200, 300 to perform the predefined operation event according to the predefined schedule, e.g. when the occupancy rate of the people conveyor system 200, 300 is known to be low, e.g. at a night-time.

At a step 420, in response to detecting the upcoming predefined operation event of the people conveyor system 200, 300 at the step 410, the conveyor control system 130 generates at least one trigger signal to the at least one sensor unit 120 to collect people conveyor system related sensor data with a predefined type from the people conveyor system 200, 300 during the detected upcoming predefined operation event of the people conveyor system 200, 300. If the people conveyor data collection system 100 comprises more than one sensor unit 120, the at least on trigger signal may be generated to all of the sensor units 120 or to one or more sensor units 120, for example depending on a prevailing need, e.g. depending on what kind of data (e.g. acceleration, sound, temperature, and/or humidity, etc.) is needed to be collected at that time. The people conveyor system related sensor data with the predefined type may for example, but not limited to, comprise the people conveyor system related sensor data with a predefined accuracy, a predefined amount of the people conveyor system related sensor data, the people conveyor system related sensor data with a predefined sampling frequency, the people conveyor system related sensor data with a predefined processing, and/or the people conveyor system related sensor data without processing (i.e. unprocessed or raw data), etc.. According to an example, the generated at least one trigger signal may comprise an indication of the predefined type of the people conveyor system related sensor data to be collected. The collecting of the people conveyor related sensor data with the predefined type in response to detecting the upcoming predefined operation event of the people conveyor system 200, 300 enables on demand collection of the people conveyor related sensor data from the people conveyor system 200, 300. Furthermore, it improves a battery life of battery powered sensor units 120. The collecting of the people conveyor related sensor data with the predefined type in response to detecting the upcoming predefined operation event of the people conveyor system 200, 300 may be especially beneficial in cases where the high sampling frequency is needed. According to another example, the generated at least one trigger signal may comprise a first instruction to start collecting the people conveyor system related sensor data with the predefined type at the start of the upcoming predefined operation event of the people conveyor system 200, 300 and a second instruction to stop collecting the people conveyor related sensor data with the predefined type at the end of the upcoming predefined operation event of the people conveyor system 200, 300. The first and second instructions may be included in a single trigger signal or in separate trigger signals. According to yet another example, if the upcoming predefined operation event has a predefined time duration, the generated at least one trigger signal may comprise an instruction to collect the people conveyor system related sensor data with the predefined type during the predetermined time duration of the upcoming predefined operation event of the people conveyor system 200, 300. This enables that a separate stop instruction is not needed. According to yet another example, the generated at least one trigger signal may comprise collect data signals generated as long as the upcoming predefined operation event of the people conveyor system 200, 300 is ongoing. Each collect data signal may comprise an instruction to collect the people conveyor system related sensor data with the predefined type. In response to receiving the at least one trigger signal from the conveyor control system 130, the at least one sensor unit 120 collects the people conveyor system related sensor data with the predefined type from the people conveyor system 200, 300 during the detected upcoming predefined operation event of the people conveyor system 200, 300 according to the received at least one trigger signal.

At a step 430, the conveyor control system 130 receives the collected people conveyor related sensor data with the predefined type from the at least one sensor unit 120. According to an example, the at least one sensor unit 120 may provide the collected people conveyor related sensor data with the predefined type to the conveyor control system 130 after the at least one sensor unit 120 has accomplished the collection of the people conveyor related sensor data with the predefined type. In other words, the conveyor control system 130 may receive the collected people conveyor related sensor data with the predefined type from the at least one sensor unit 120 after the at least one sensor unit 120 has accomplished the collection of the people conveyor related sensor data with the predefined type. According to another example, the at least one sensor unit 120 may provide the collected people conveyor related sensor data with the predefined type to the conveyor control system 130 in response to receiving from the conveyor control system 130 a request to provide the collected people conveyor related sensor data with the predefined type to the conveyor control system 130. In other words, to receive the collected people conveyor related sensor data with the predefined type from the at least one sensor unit 120, the conveyor control system 130 may generate to the at least one sensor unit 120 the request to provide the collected people conveyor related sensor data with the predefined type. According to yet another example, the at least one sensor unit 120 may provide the collected people conveyor related sensor data with the predefined type to the conveyor control system 130 according to a predefined data delivery schedule. In other words, the conveyor control system 130 may receive the collected people conveyor related sensor data with the predefined type from the at least one sensor unit 120 according to the predefined data delivery schedule. According to an example, in the escalator implementation of the people conveyor data collection system 100, the conveyor control system 130 may delay the activation of the energy saving mode of the escalator system 300 until the people conveyor related sensor data with the predefined type has been collected by the at least one sensor unit 120.

The conveyor control unit 130 may further receive from the at least one sensor unit 120 people conveyor system related sensor data with at least one second type collected by the at least one sensor unit 120 at any other time than during the detected upcoming predefined operation event of the people conveyor system 200, 300. The at least one second type differs from the predefined type. In other words, at any other time than during the detected upcoming predefined operation event of the people conveyor system 200, 300 the at least one sensor unit 120 may collect people conveyor system related sensor data with the at least one second type differing from the predefined type and provide the collected people conveyor system related sensor data with the at least one second type to the people conveyor unit 130. The people conveyor system related sensor data with the at least one second type may for example be collected by the at least one sensor unit 120 substantially continuously, occasionally, periodically, or at specific moments. Similarly, the at least one sensor unit 120 may for example provide the collected people conveyor system related sensor data with the at least one second type to the conveyor control unit 130 substantially continuously, occasionally, periodically, or at specific moments. According to an example, the people conveyor system related sensor data with the predefined type may be more accurate than the people conveyor system related sensor data with the at least one second type. According to another example, the people conveyor system related sensor data with the predefined type may alternatively or in addition comprise data with a higher sampling frequency than the people conveyor system related sensor data with the at least one second type. According to yet another example, the people conveyor system related sensor data with the predefined type may alternatively or in addition comprise a larger amount of data than the people conveyor system related sensor data with the at least one second type. According to yet another example, the people conveyor system related sensor data with the predefined type may alternatively or in addition comprise less processed data than the people conveyor system related sensor data with the at least one second type or even unprocessed data.

The method may further comprise one or more further triggering conditions for the generating the at least one trigger signal to the at least one sensor unit 120. Next some examples of the method with different further triggering conditions are described referring to Figures 4B to 4D. In the example of Figure 4B, the one or more further triggering conditions comprises a time elapsed from the previous collection of the people conveyor related sensor data with the predefined type. In the example of Figure 4C, the one or more further triggering conditions comprises the current conditions of the people conveyor system 200, 300. In the example of Figure 4D, the one or more further triggering conditions comprises an occupancy status of the conveyor entity 202, 302 of the people conveyor system 200, 300. Although the different further triggering conditions are illustrated individually in the examples of Figures 4B to 4D, the method may comprise more than one further triggering condition. Furthermore, the order of performing the further triggering conditions is not limited and the further triggering conditions may be performed in any order after detecting the upcoming predefined operation event of the people conveyor system 200, 300 at the step 410 discussed above, but before generating the at least one trigger signal to the at least one sensor unit 120 at the step 420 discussed above. According to an example, after detecting the upcoming predefined operation event of the people conveyor system 200, 300 at the step 410 discussed above the conveyor control system 130 may further check a time elapsed from a previous collection of the people conveyor related sensor data with the predefined type from the at least one sensor unit 120. This is illustrated with a step 440 in the example of Figure 4B. The conveyor control system 130 may generate the at least one trigger signal to the at least one sensor unit 120 at the step 420, if the time elapsed meets a predefined time limit. In other words, the time elapsed from the previous collection of the people conveyor related sensor data with the predefined type from the at least one sensor unit 120 may be used as one further triggering condition of the one or more further triggering conditions. This enables that the data collection may be postponed or prevented if the people conveyor related sensor data with the predefined type has been collected by the at least one sensor unit 120 recently, and if there is no need to collect the people conveyor related sensor data with the predefined type more frequently. The predefined time limit may for example be defined based in the frequency of the need for collection of the people conveyor related sensor data with the predefined type. If the people conveyor data collection system 100 comprises more than one sensor unit 120, the predefined time limit may be the same for all the sensor units 120, or the predefined time limit may be a sensor unit specific, i.e. the predefined time limit may be defined separately for each sensor unit 120. The verb “meet” in context of a predefined limit, e.g. the predefined time limit, is used in this patent application to mean that a predefined condition is fulfilled. For example, the predefined condition may be that the predefined limit is reached and/or exceeded.

Alternatively or in addition, after detecting the upcoming predefined operation event of the people conveyor system 200, 300 at the step 410 discussed above, the conveyor control system 130 may further obtain condition data representing the current conditions of the people conveyor system 200, 300. This is illustrated with a step 450 in the example of Figure 4C. For example, the obtained condition data may comprise one or more condition parameters, e.g. temperature, humidity, and/or air pressure. The condition data may be obtained from at least one condition sensor device being internal or external to the people conveyor system 200, 300. The at least one condition sensor device may for example comprise at least one temperature sensor device, at least one humidity sensor device, and/or at least one air pressure sensor device.

At a step 460 in the example of Figure 4C, the conveyor control system 130 may further detect whether the obtained condition data corresponds to a predefined condition limit or a predefined condition range. The predefined condition limit or the predefined condition range may be defined based on condition data obtained, when the people conveyor related sensor data with the predefined type is collected previous time(s) by the at least one sensor unit 120. Alternatively or in addition, the predefined condition limit or the predefined condition range may be defined based on average conditions of the conveyor control system 200, 300. If the condition data comprises more than one condition parameter, a separate predefined condition limit or a separate predefined condition range may be defined for each condition parameter. The conveyor control system 130 may generate the at least one trigger signal to the at least one sensor unit 120 at the step 420, if it is detected that the obtained condition data corresponds to the predefined condition limit/range at the step 460. In other words, the current conditions of the people conveyor system 200, 300 may be used as one further triggering condition of the one or more further triggering conditions. This improves homogeneity and comparability of the people conveyor system related sensor data with the predefined type collected at different times, which in turn improves reliability of monitoring and/or analyzing the people conveyor system related sensor data with the predefined type collected at the different times.

Alternatively or in addition, after detecting the upcoming predefined operation event of the people conveyor system 200, 300 at the step 410, the conveyor control system 130 may further obtain from the at least one occupancy detection unit 110 occupancy status data representing occupancy status of the conveyor entity 202, 302 of the people conveyor system 200, 300. This is illustrated with a step 470 in the example of Figure 4D. As discussed above in the elevator system implementation of the people conveyor data collection system 100, the at least one occupancy detection unit 110 may comprise the load weighting device 110a and/or the at least one sensor-based device 110b. The load weighting device 110a may provide weight data representing weight of the load carried by the elevator car 202. The occupancy status data may comprise the weight data provided by the load weighting device 110a. The occupancy status of the elevator car 202 may then be defined from the occupancy status data comprising the weight data. The at least one sensor-based device 110b may provide sensor data from inside the elevator car 202. The occupancy status data may comprise the sensor data provided by the at least one sensor-based device 110b. The occupancy status of the elevator car 202 may then be defined from the occupancy status data comprising the sensor data. The occupancy status data obtained from the at least one PIR device may for example comprise motion data representing movement (e.g. movement of one or more passengers) inside the elevator car 202 from which the occupancy status of the elevator car 202 may be defined. The occupancy status data obtained from the at least one ToF sensor device may for example comprise distance data. The distance data may for example comprise the distance to each point in a scene, e.g. the interior of the elevator car 202. Alternatively or in addition, the distance data may for example comprise three dimensional (3D) depth data formed based on the distance to each point in the scene. The 3D depth data may for example comprise a depth map or a point cloud data of the scene. The occupancy status of the elevator car 202 may then be defined from the distance data obtained from the at least one ToF sensor device. The occupancy status data obtained from the at least one optical imaging device may for example comprise image data from inside the elevator car 202, e.g. image data of the interior of the elevator car 202. The image data provided by the at least one optical imaging device may for example comprise one or more (still) images and/or video images comprising a plurality of consecutive images, i.e. frames. The occupancy status of the elevator car 202 may then be defined from the image data obtained from the at least one optical imaging device. As discussed above in the escalator system implementation of the people conveyor data collection system 100, the at least one occupancy detection unit 110 may comprise the at least one sensor-based detection system and/or the at least one optical imaging device -based detection system. The at least one sensor-based detection system may provide detection data indicating a detection of at least one passenger arriving to the conveyor entity 302 of the escalator system 300 as the occupancy status data. The detection data may depend on what kind of the occupancy detection unit is used. The occupancy status of the conveyor entity 302 may then be defined from the detection data being obtained from the at least one sensor-based detection system. The at least one optical imaging device -based detection system may provide the image data as the occupancy status data. The image data provided by the at least one optical imaging device -based detection system may for example comprise one or more (still) images and/or video images comprising a plurality of consecutive images, i.e. frames. The occupancy status of the conveyor entity 302 may then be defined from the image data obtained from the at least one optical imaging device -based detection system.

At a step 480 in the example of Figure 4D, the conveyor control system 130 may detect a predefined status of the conveyor entity 202, 302 based on the obtained occupancy status data. According to an example, the detected predefined status of the conveyor entity 202, 302 may for example be that the conveyor entity 202, 302 is empty. The term “empty” in context of the conveyor entity 202, 302 is used in this patent application to mean that the conveyor entity 202, 302 is empty of load, e.g. empty of people (such as passengers), and freight. When the conveyor entity 202, 302 is empty, the load of the conveyor entity 202, 302 is known. In the elevator system implementation of the people conveyor data collection system 100, the detection of the elevator car 202 being empty may be detected based on the occupancy status data obtained from the at least one occupancy detection unit 110 comprising the load weighting device 110a and/or the at least one sensor-based device 110b. In the escalator system implementation of the people conveyor data collection system 100, the detection of the conveyor entity 302 being empty may be detected based on the occupancy status data obtained from the at least one occupancy detection unit 110 comprising at least one optical imaging device -based detection system. Alternatively or in addition, in the escalator system implementation of the people conveyor data collection system 100, the detection of the conveyor entity 302 being empty may be detected based on the occupancy status data obtained from the at least one occupancy detection unit 110 comprising at least one sensor-based detection system , for example so that after a fixed travel time since the last detection of the at least one passenger it may be concluded that the conveyor entity 302 is empty. According to another example, the detected predefined status of the conveyor entity 202, 302 may for example be that the conveyor entity 202, 302 carries a known load. In the elevator system implementation of the people conveyor data collection system 100, the detection that the elevator car 202 carries the known load may be detected based on the occupancy status data obtained from the at least one occupancy detection unit 110 comprising the load weighting device 110a. In the escalator system implementation of the people conveyor data collection system 100, the detection that the conveyor entity carries the known load may be detected indi- rectly from a motor of the escalator driving machine (e.g. based on power, torque and/or direction of the motor) and the obtained occupancy status data from the at least on occupancy detection unit 110 is used to detect when the known load arrives to the conveyor entity 302 and is estimated to exit the conveyor entity 302 after a fixed travel time since arriving to the conveyor entity 302. As the load of the conveyor entity 202, 302 is known (either in case of being empty or carrying known load), the conditions for people conveyor related sensor data with the predefined type collection are known to be repeatable, which enables reliable collection of the people conveyor related sensor data with the predefined type at different times. The conveyor control system 130 may generate the at least one trigger signal to the at least one sensor unit 120 at the step 420, if the predefined status of the conveyor entity 202, 302 is detected at the step 480. In other words, the occupancy status of the conveyor entity 202, 302 of the people conveyor system 200, 300 may be used as one further triggering condition of the one or more further triggering conditions. Because the people conveyor system related sensor data with the predefined type is collected in response to receiving the at least one trigger signal from the conveyor control system 130 generated in response to the detection of the predefined status of the conveyor entity 202, 302 (e.g. being empty), it enables that the collection of the people conveyor system related sensor data with the predefined type may be limited to so called standardized scenarios, e.g. when the conveyor entity 302 of the escalator system 300 is running empty without passengers, and/or when the elevator car 202 of the elevator system 200 is traveling between specific landings 206a-206n without passengers. Moreover, it enables collecting sensitive people conveyor system related sensor data with the predefined type, e.g. audio data or other potential sensitive data, when it is certain that there are no passengers inside the elevator car 202.

As discussed above, the people conveyor data collection system 100 may further comprise the cloud computing unit 140. According to an example, the method may further comprise providing the collected people conveyor related sensor data with the predefined type to the cloud computing unit 140. Figure 5 illustrates schematically yet another example of the method, wherein the collected people conveyor related sensor data with the predefined type may be provided further to the cloud computing unit 140.

At a step 510, after receiving the collected people conveyor related sensor data with the predefined type from the at least one sensor unit 120 at the step 430 discussed above, the conveyor control system 130 may provide the collected people conveyor related sensor data with the predefined type to the cloud computing unit 140 for further processing and/or analyzing. The collected sensor data with the predefined type may also be processed at the conveyor control unit 130, but due to a limited processing capacity of the conveyor control unit 130 it may be preferable to perform at least part of the processing at the cloud computing unit 140. Because the people conveyor system related sensor data with the predefined type is collected in response to receiving the at least one trigger signal from the conveyor control system 130, it enables that the collected people conveyor system related sensor data with a high sampling rate may be provided from the sensor units 120 via the conveyor control unit 130 to the cloud computing unit 130 connected with a low-bandwidth connection to the conveyor control system 130. A non-limiting example of the low- bandwidth connection may be a 2G cellular network.

According to an example, before providing the collected people conveyor related sensor data with the predefined type to the cloud computing unit 140 at the step 510, the conveyor control system 130 may incorporate respective metadata into the collected people conveyor related sensor data with the predefined type to be provided to the cloud computing unit 140. This is illustrated with an optional step 520 in the example of Figure 5. For example, in the elevator system implementation of the people conveyor data collection system 100, the metadata may comprise elevator system operation mode data, landing data, direction data, and/or operation state data, etc.. The landing data may for example comprise data indicating a departure landing and/or a destination landing of a movement cycle of the elevator car 202, and/or a landing, where the elevator car 202 has been stopped, etc. The elevator system operation mode data may for example comprise data indicating the operation mode of the elevator system 200. Some non-limiting operation modes of the elevator system 200 may comprise a normal operation mode, a maintenance mode, and/or an inspection mode. The direction data may comprise data indicating a movement direction of the elevator car 202, i.e. up or down. The operation state data may comprise data indicating the operation state of the elevator system 200, e.g. broken (i.e. in fault) or operational. For example, in the escalator system implementation the people conveyor collection system 100, the metadata may comprise escalator system operation mode data, direction data, and/or operation state data, etc. The escalator system operation mode data may for example comprise data indicating the operation mode of the escalator system 300. Some non-limiting operation modes of the escalator system 300 may comprise a normal operation mode, an idle mode, the energy saving mode, a stopped mode, and/or an inspection mode. The direction data may comprise data indicating a movement direction of the conveyor entity 302, i.e. up or down. The operation state data may comprise data indicating the operation state of the escalator system 300, e.g. broken or operational.

Figure 6 illustrates schematically an example of components of the conveyor control system 130. The conveyor control system 130 may comprise a processing unit 610 comprising one or more processors, a memory unit 620 comprising one or more memories, a communication unit 630 comprising one or more communication devices, and possibly a user interface (III) unit 640. The mentioned elements may be communicatively coupled to each other with e.g. an internal bus. The memory unit 620 may store and maintain portions of a computer program (code) 625, the obtained occupancy status data, the collected people conveyor related sensor data with the predefined type, the collected people conveyor related sensor data with the at least one second type, and/or any other data. The computer program 625 may comprise instructions which, when the computer program 625 is executed by the processing unit 610 of the conveyor control system 130 may cause the processing unit 610, and thus the conveyor control system 130 to carry out desired tasks of the conveyor control system 130, e.g. one or more of the method steps described above. The processing unit 610 may thus be arranged to access the memory unit 620 and retrieve and store any information therefrom and thereto. For sake of clarity, the processor herein refers to any unit suitable for processing information and control the operation of the conveyor control system 130, among other tasks. The operations may also be implemented with a microcontroller solution with embedded software. Similarly, the memory unit 620 is not limited to a certain type of memory only, but any memory type suitable for storing the described pieces of information may be applied in the context of the present invention. The communication unit 630 provides one or more communication interfaces for communication with any other unit, e.g. the at least one occupancy detection unit 110, 110a, 110b the at least one sensor unit 120, the cloud computing unit 140, one or more databases, and/or with any other unit. The user interface unit 640 may comprise one or more input/output (I/O) devices, such as buttons, keyboard, touch screen, microphone, loudspeaker, display and so on, for receiving user input and outputting information. The computer program 625 may be a computer program product that may be comprised in a tangible nonvolatile (non-transitory) computer-readable medium bearing the computer program code 625 embodied therein for use with a computer, i.e. the conveyor control system 130.

The specific examples provided in the description given above should not be construed as limiting the applicability and/or the interpretation of the appended claims. Lists and groups of examples provided in the description given above are not exhaustive unless otherwise explicitly stated.