EP4250037A1 - Système de concentrateur-capteur sans fil bout à bout - Google Patents

Système de concentrateur-capteur sans fil bout à bout Download PDF

Info

Publication number
EP4250037A1
EP4250037A1 EP23163083.1A EP23163083A EP4250037A1 EP 4250037 A1 EP4250037 A1 EP 4250037A1 EP 23163083 A EP23163083 A EP 23163083A EP 4250037 A1 EP4250037 A1 EP 4250037A1
Authority
EP
European Patent Office
Prior art keywords
sensor
data
hubs
network
hub
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23163083.1A
Other languages
German (de)
English (en)
Inventor
Bodhayan DEV
Atish P. Kamble
Prem SWAROOP
Vijay Karthick BASKAR
Richard BUTEAU
Sreedhar PATNALA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Delaware Capital Formation Inc
Capital Formation Inc
Original Assignee
Delaware Capital Formation Inc
Capital Formation Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Delaware Capital Formation Inc, Capital Formation Inc filed Critical Delaware Capital Formation Inc
Publication of EP4250037A1 publication Critical patent/EP4250037A1/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/048—Monitoring; Safety
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24075—Predict control element state changes, event changes

Definitions

  • Sensors can be used to capture data associated with industrial equipment.
  • Industrial equipment includes machines used in manufacturing and fabrication.
  • industrial equipment includes but is not limited to pumps, heavy duty industrial tools, compressors, automated assembly equipment, and the like.
  • Industrial equipment also includes machine parts and hardware, such as springs, nuts and bolts, screws, valves, pneumatic hoses, and the like.
  • a method includes configuring sensor hubs in an order using a sequence established by a time of addition to a network.
  • the method includes configuring the sensor hubs into one or more groups, wherein a number of sensor hubs in a respective group is calculated according to a maximum bandwidth consumed by a group of sensor hubs, wherein the maximum bandwidth does not exceed a data bandwidth of the network.
  • the method includes obtaining sensor data captured by the one or more groups according to a current group number, wherein the sensor data is obtained from each group of the one or more groups according to a predetermined schedule.
  • the sensor data is captured by one or more sensors of a sensor hub and sensor data is transmitted to condition monitoring applications for predictive maintenance of the industrial equipment, e.g., predictive maintenance of actuators used in the transportation sector, such as for fleet management for fuel tank systems, motion platforms, automation systems used in garbage trucks, etc.
  • a respective mounting position of each sensor-hub on the industrial equipment is determined by a series of trials that characterize various 'anomalous conditions' that occur throughout the lifetime of use of the equipment. The sensor data collected during these trials can be used to train machine learning models.
  • Some mounting positions capture sensor data that do not accurately characterize operation of the industrial equipment. In particular, some mounting positions fail to capture data that enables a machine learning model to characterize the operation of the industrial equipment due to being remote from the source of sensor data. The mounting positions that fail to capture sensor data that characterizes operation of the industrial equipment are not used.
  • the sensor-hubs can transfer captured raw sensor data using a low-power wireless personal area network with secure mesh based communication technology.
  • the network can include one or more router nodes, terminating at an internet of things (IoT) edge device.
  • the network enables communications according to an Internet Protocol version 6 (IPv6) communications protocol.
  • IPv6 Internet Protocol version 6
  • the communications protocol used across the network is an IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN).
  • 6LoWPAN Low-Power Wireless Personal Area Networks
  • the sensor data is ingested into a workflow and one or more trained machine learning models learn from the sensor data for continuous improvement.
  • the trained machine learning model(s) are deployed onto edge or cloud devices.
  • the edge devices are deployed at an operational site.
  • the sensor hubs enable low power data collection and transmission, thereby conserving power consumption.
  • the mesh network used for data transfer is resilient to failures and handles outages of member nodes.
  • FIG 1A shows an example of a sensor hub 100.
  • the sensor hub 100 captures sensor data that is input to the data flow architecture 200 of Figure 2 .
  • a sensor hub 100 corresponds to each of the nodes 100A, 100B, and 100C of the network 300A of Figure 3A , and a sensor hub 100 can be placed at various positions as shown in the example of the computer numerically controlled (CNC) machine 300B of Figure 3B and/or the industrial machine 300C of Figure 3C .
  • the CNC 300B and industrial machine 300C are examples, and the industrial equipment (including the CNC 300B and the industrial machine 300C) can be designed and built to perform a single operation or be designed and built to perform a combination of two or more operations. In any case, the industrial equipment can perform one or more operations that generate multiple functional parameters that can be understood by a trained machine learning algorithm through the use of various data inputs, as described in this specification.
  • two or more sensor hubs 100 are coupled with the industrial equipment.
  • the sensor hub 100 includes a controller 102.
  • the controller 102 includes one or more processing cores and memory.
  • the controller 102 is a system on a chip (SoC).
  • SoC system on a chip
  • the controller 102 is a mixed signal controller that integrates both analog and digital inputs. Analog inputs 106 are provided to the controller 102. The controller 102 outputs analog outputs 108. Similarly, the controller 102 receives digital inputs 110. The controller 102 outputs digital outputs 112.
  • the controller 102 also communicates via a serial RS-485 interface 104.
  • the controller 102 includes future expansion 114.
  • the future expansion 114 is an expansion bus.
  • the expansion bus may be for example, an Inter-Integrated Circuit bus (I 2 C).
  • I 2 C Inter-Integrated Circuit bus
  • the future expansion 114 enables lower speed peripheral components to be communicatively coupled with the controller 102.
  • the controller 102 is communicatively coupled with the interface 104.
  • the interface 104 is operable according to an RS-485 standard.
  • RS-485 is a standard defining the electrical characteristics of drivers and receivers for use in serial communications systems.
  • RS-485 specifies the electrical characteristics of a generator and receiver. It does not specify or recommend any communications protocol.
  • RS-485 is a transmission standard that uses differential voltages to code transmission data for multipoint, multi-drop LAN systems.
  • the sensor-hub can use the RS-485 interface to communicate directly with equipment like variable frequency drives, programmable logic controllers (PLCs), and other industrial control equipment.
  • PLCs programmable logic controllers
  • the sensor hub includes fewer or additional components than those provided in the example of Figure 1A .
  • a sensor hub 100 includes an accelerometer and a temperature sensor, is battery operated, and uses a very-low power design approach.
  • an analog-only sensor hub 100 includes an accelerometer and a temperature sensor, is not battery operated, and also enables users to connect multiple external analog sensors, thus extending the capability of the sensor hub 100.
  • an analog only sensor hub includes multiple analog outputs and an RS-485 port.
  • a fully-loaded sensor hub 100 extends the features of the analog-only sensor hub described in the second example, and additionally enables multiple digital inputs, multiple digital outputs and an expansion bus (I 2 C).
  • Figure 1B is a drawing of a sensor hub 150.
  • the sensor hub 150 can be, for example, the sensor hub 100 described with respect to Figure 1A .
  • the sensor hub 150 can include components described with respect to the sensor hub 100 in a plastic enclosure 160.
  • the sensor hub 150 and the plastic enclosure 160 are small.
  • the sensor hub 150 and plastic enclosure 160 are less than or equal to 83 millimeters (mm) x 83 mm x 39 mm for a sensor hub that is fully loaded or an analog-based sensor hub.
  • the sensor hub 150 and plastic enclosure 160 are less than or equal to 83 mm x 83 mm x 55 mm for a sensor hub that is battery operated.
  • the small size of the sensor hub 150 and plastic enclosure 160 along with the wireless communication of the sensed data facilitates placement of the sensor hub 150 and plastic housing 160 in many different locations on industrial equipment, including hard to reach locations.
  • the sensor hub 150 and plastic enclosure are mounted to the industrial equipment using stud mounting or two-pole magnetic mounting, depending on the equipment being monitored.
  • IP67 waterproof M12 connectors 170 are shown.
  • the IP67 waterproof M12 connectors 170 enable coupling the power supply, analog and digital inputs/outputs, RS485, and I 2 C with the sensor hub.
  • FIG 2 is a block diagram of a data flow architecture 200 for sensor hub implementation.
  • the sensor hubs may be, for example a sensor hub 100 as shown in Figure 1A .
  • An operational site 202 represents a location where industrial equipment is located.
  • the operational site 202 may be that of an organization that owns or operates industrial equipment.
  • Hardware 220 and software 230 are located at the operational site 202.
  • the hardware 220 includes one or more sensor hubs.
  • Sensor data is captured at the operational site 202 and transmitted to a cloud infrastructure 204.
  • the cloud infrastructure 204 includes one or more trained machine learning models 240.
  • the machine learning models are an ensemble-based model trained to predict an operating condition of the industrial equipment based on sensor data captured during operation of the industrial machinery. Trained machine learning models can also detect model accuracy and data drifts. Additionally, the trained machine learning models are self-learning, where the models are updated based on newly available sensor data.
  • trained machine learning models are deployed in the cloud infrastructure 204, where the trained machine learning models predict an operating condition of the industrial equipment in an online manner (e.g., with cloud access). In some embodiments, trained machine learning models are deployed at the operational site 202, where the trained machine learning model predicts an operating condition of the industrial equipment in an offline manner (e.g., without access to a cloud infrastructure).
  • the sensor data is labeled to characterize the subtle differences or trends that appear over a period of use, e.g., over the lifetime of use of the industrial equipment.
  • the labels are acquired via periodic polling from control equipment (including PLCs, variable frequency drives (VFDs), pump controllers, refrigeration controllers, building management system (BMS), etc.) for a state associated with the industrial equipment.
  • the labels are acquired via manual inputs from the equipment operator(s) (including truck drivers, service technicians, maintenance personnel, shop-floor supervisors, fleet operators, CNC (computer numerically controlled) machine operators, etc.) using the provided user interface running on a portable tablet device (e.g., device 314 of Figure 3 ).
  • the machine learning models can be trained using the labeled sensor data. This degradation during operation thus produces “anomalous conditions" that exhibit a physically measurable (using attached sensors) data footprint that is different from the data footprint when the industrial equipment is new, freshly mounted/installed, and configured according to manufacturer specifications. With enough cycles of usage, the machine learning models can distinguish between good sensor data, various levels of degradation, and bad sensor data.
  • good data includes properly installed pumps running without any cavitation, rotary equipment used in cutting operations that produce the "right” quality of cuts of media being operated on, rotary equipment used in surface-finish operations that produce the "right” surface-finish, etc.
  • bad data includes improperly installed pumps, pumps running dry over a long time, pumps producing lots of cavitation, rotary equipment used in cutting operations that produce "bad” quality cuts, rotary equipment used in surface-finish operations that produce "bad” quality surface-finish, etc.
  • the sensor data is captured across multiple operational sites (e.g., multiple customer installations).
  • the data is transmitted from the operational site 202 to the cloud infrastructure 204 according to a secure communication protocol.
  • the protocol is the Advanced Message Queuing Protocol (AMQP) or the MQTT protocol according to the OASIS Message Queuing Telemetry Transport Technical Committee.
  • Figure 3A is a block diagram of an edge architecture operable via a network 300A that includes one or more sensor hubs.
  • the network 300A is a low power, peer-to-peer, multi-hop wireless network, wherein nodes of the network collectively coordinate routing of frames across the network.
  • the present systems and techniques include a power-optimized sensor hub platform and an end-to-end support ecosystem for machine learning prediction completely offline and at the edge.
  • cloud connectivity is optional.
  • trained machine learning models e.g., machine learning models 240 of Figure 2
  • secure communication pathways are shown in Figure 3A with a lock adjacent to the arrow representing the communication pathway.
  • secure communication pathways are enabled via a trusted platform module (TPM).
  • TPM trusted platform module
  • the network 300A includes nodes 100A, 100B, and 100C.
  • Each of the nodes 100A, 100B, and 100C represent a respective sensor hub (e.g., sensor hub 100 and/or sensor hub 150 of Figures 1A and 1B ).
  • the sensor hubs are positioned at predetermined locations on or near the industrial equipment.
  • Figure 3B is a drawing of a computer numerically controlled (CNC) machine 300B.
  • Figure 3C is a drawing of an industrial machine 300C.
  • Sensor hubs, such as sensor hubs corresponding to nodes 100A, 100B, and 100C may be placed at predetermined locations with respect to the CNC 300B and industrial machine 300C.
  • the sensor hubs are located adjacent to components of the CNC 300B and industrial machine 300C that are sources of sensor data.
  • a position and an orientation of the at least one sensor hub enables capture of sensor data associated with the component and avoids attenuation (e.g., reduction in amplitude) of the sensor data due to a distance between the component and the at least one sensor hub.
  • installation technicians e.g., technicians that install sensor hubs at locations on or near the industrial equipment
  • the tool can report the quality of the signal dynamically to determine the best mounting position or if signal routers have to be installed between the sensor-hub and the gateway.
  • a source of sensor data is a source of energy that moves or controls a component of the industrial equipment.
  • the CNC 300B includes components such as a cutter and a motorized maneuverable platform. Sensor hubs are located at a predetermined location 350 on or near the cutter of the CNC 300B, and a predetermined location 352 on or near a motor of the motorized maneuverable platform of the CNC 300B.
  • the cutter and the motorized maneuverable platform are sources of sensor data that is captured by sensors of one or more sensor hubs.
  • the industrial machine 300C includes components such as a motor and a feed roll end.
  • Sensor hubs are located at a predetermined location 360 on or near the motor of the industrial machine 300C, and a predetermined location 362 on the side of the drive shaft opposite to the motor end of the rotor on the industrial machine 300C.
  • the motor and the feed roll end are sources of sensor data that is captured by sensors of one or more sensor hubs.
  • an operational site 202 and a cloud infrastructure 206 is shown.
  • the cloud infrastructure 206 is a Microsoft Azure cloud.
  • a Modbus Remote Terminal Unit (RTU) protocol is used to for communications with the sensor hub via the RS-485 physical bus (e.g., interface 104 of Figure 1A ).
  • the sensor hubs are driven by a variable frequency drive 302.
  • Inputs/outputs 304 correspond to analog inputs 106, analog outputs 108, digital inputs 110, and digital outputs 112 as described with respect to Figure 1A .
  • inputs/outputs 304 include inputs such as digital inputs (used for on/off type inputs), analog inputs (used for reference inputs like temperature reference, speed reference, etc.), RS485 inputs (used for Modbus RTU communication with PLC, etc.) and I 2 C input (used for future expansion).
  • inputs/outputs 304 include digital outputs (used to turn an indication light on/off or start/stop something) and analog outputs (used to provide reference to an externa system, like used to control the speed of a motor, etc.)
  • the exemplary sensor hub also includes four digital outputs and two analog outputs.
  • a thermopile 306 is used to capture surface temperature of the media under operation. This surface temperature data is used to train machine learning models. In some examples, the temperature of the media affects the output quality of the process.
  • Media refers to anything that is being operated upon. For example, in a CNC machine, media is a block of metal that needs to be machined. In other examples, such as a pelletizer, media is strands of extruded plastic that needs to be cut to form pellets. In the example of a paper cutter or textile cutter, media is paper and textile respectively.
  • the nodes 100A, 100B, and 100C capture sensor data associated with industrial equipment and transmit the sensor data using the network 300A.
  • the network 300A is an IPv6-based network.
  • the network 300A is an OpenThread network (e.g., 802.15.4 Thread) that routes data from one or more sensor hubs across the network consisting of one or more router nodes that form the mesh.
  • the network 300A is a Matter network as provided by the Connectivity Standards Alliance.
  • the network 300A is a Bluetooth Low Energy (LE) network as provided by the Bluetooth Special Interest Group.
  • the network 300A is a Bluetooth mesh network as provided by the Bluetooth Special Interest Group.
  • the network 300A is a Zigbee network as provided by the Connectivity Standards Alliance.
  • the network 300A is an ANT Network as provided by the ANT+ Alliance.
  • the network 300A is a proprietary 2.4GHz networking protocol, developed in-house.
  • the network 300A is an IPv6-based, low-power mesh networking technology for IoT devices, and is secure and future-proof.
  • the sensor hubs e.g., sensor hubs 100, 150 of Figures 1A and 1B
  • the low power IP based smart mesh network is operable in the high temperature industrial environment by isolating the electronics (e.g., processor, peripheral silicon devices and networking radio) from a transducer (e.g., device that converts energy to an electric signal) of the sensor hub.
  • the isolation enables the electronics to operate at a reduced temperature at up-to 85°C when compared to the high temperature industrial environment.
  • intelligent sequencing enables large data transfer from multiple sensor-hubs.
  • the sensor hubs communicate according to a predefined protocol that enables each sensor hub to participate in the data transmission on the network.
  • Each sensor hub is an endpoint of the network that transmits captured sensor data via one or more router nodes 308 to finally reach the IoT gateway 316.
  • This data can include metrics from sensors such as an accelerometer, temperature sensor, RS-485 (data from variable frequency drives, PLCs, etc.)
  • the one or more router nodes 308 transmit sensor data captured at the sensor hubs corresponding to nodes 100A, 100B, and 100C.
  • the network 300A includes multiple types of nodes.
  • a node can be a full thread device (FTD), a minimal thread device (MTD), or any combinations thereof.
  • An FTD includes a radio that is always on, while an MTD includes a radio that is periodically placed in a sleep state.
  • the nodes 100A, 100B, and 100C are a type of MTD referred to as a sleepy node.
  • a sleepy node optimizes power consumption by waking up from a sleep mode for a brief amount of time during which it does end-use application specific tasks. Upon completion of the tasks, the sleepy node returns to a sleep state. The longer a node sleeps, the more power is conserved.
  • the one or more router nodes 308 transmit data to the border router 310.
  • the sensor data is wirelessly transmitted to the router nodes 308, which relay information to the border router 310.
  • the border router 310 translates between the IPV4 network (e.g., the Internet) to which a gateway 316 is connected, and the IPV6 network. Data moving between the nodes 100A, 100B, and 100C and the cloud infrastructure 206 are transmitted through the gateway 316.
  • the border router 310 is positioned at an edge of the network 300A, and in some embodiments, the border router 310 routes data between the low-power mesh network 300A and an external network, such as the Internet.
  • the border router 310 enables connectivity of nodes on the low-power mesh network 300A to other devices in external networks or to the cloud infrastructure 206. As shown, the border router 310 is communicatively coupled to an IoT gateway 316. The border router 310 transmits sensor data to the IoT gateway 316, and the IoT gateway 316 to the device 314.
  • the device 314 is a tablet computer, cellular phone, laptop, or other mobile electronic device. In some embodiments, the device 314 operates using an Android or iOS based operating system. In some embodiments, a rate of data sampling for each node 100A, 100B, and 100C is configurable via the device 314.
  • the device 314 and gateway 316 are communicatively coupled with the cloud infrastructure 206 via a WiFi router 312.
  • the device 314 and gateway 316 communicate with the cloud infrastructure 206 using Long-Term Evolution (LTE) or Wi-Fi communication standard.
  • the cloud infrastructure 206 includes application cloud and device management 330.
  • an application cloud is used to display data in a central web dashboard so that an engineer or customer can look at machine trends over time to understand degradation of machine tools.
  • device management includes a web application used to manage lifecycle of the IoT devices deployed at customer sites. Management, for example, includes deploying a new device, over-the-air software updates, rebooting an unresponsive device remotely, etc.
  • the gateway 316 is hardware and/or software a program that is a connection point between the cloud infrastructure 206, various controllers, nodes 100A-100C, and other devices on the network 300A.
  • the gateway 316 can execute a software library that enables edge functionality on the network.
  • the gateway 316 can execute a Microsoft IoT Edge runtime (e.g., IoT edge runtime 318), which enables predictive monitoring applications and the associated machine learning models (e.g., machine learning models 240 of Figure 2 ).
  • the device 314 is connected on the IPV4 network and acts as the user interface to securely onboard and provision new sensor-hubs on the low-power mesh network, add users with Role Based Access Control (RBAC), send configuration updates to the sensor-hubs, send over-the-air update firmware for the sensor-hubs, and manually label data for machine learning model training.
  • RBAC Role Based Access Control
  • outputs from the machine learning models are visually indicated via one or more lights (e.g., "traffic” lights) connected to the digital outputs of the sensor hub.
  • the gateway 316 processes the sensor data locally at the edge before transmitting it to the cloud infrastructure 206. For example, the gateway 316 can aggregate or de-duplicate the sensor data as a way of reducing the volume of data that is transmitted to the cloud infrastructure 206. In some embodiments, the gateway 316 provides security to the network. In the example of Figure 3A , the gateway 316 includes an IoT edge runtime 318, edge device lifecycle management module 320, end-use application module 322, database module 324, edge device remote device management module 326, and data science module 328. In some embodiments, the IoT edge runtime 318 enables deploying IoT workloads on an IoT gateway.
  • the IoT edge runtime 318 may be, for example, a Microsoft Azure product.
  • an edge device lifecycle management module 320 includes a proprietary application that manages the lifecycle of an IoT gateway. Managing the lifecycle of the gateway includes, for example, deploying the gateway from scratch, receiving and processing over-the-air software updates, etc.
  • An end-use application module 322 is a proprietary application that handles data coming in from the sensor hubs. In some embodiments, the end-use application module 322 transmits data from sensor hubs to the cloud for training machine learning models. The end-use application module 322 also executes the machine learning model to perform predictions on-premise and locally.
  • the database module 324 stores data captured by the sensor hubs in a database.
  • the peak data throughput of the low-power networking protocol used for communication between the nodes 100A-100C and the gateway 316 without using any routers between them is 250 kilobits per second (kbps).
  • Large amounts of raw, unprocessed data from multiple sensors on-board each sensor-hub can be captured from multiple such sensor-hubs for training the machine learning models.
  • the raw, unprocessed data is captured from multiple sensor hubs for input into trained machine learning models.
  • a smart data transfer mechanism assigns a sequence number and a group number to each sensor hub during onboarding. The gateway ensures that at a given point in time, a predetermined number of sensor-hubs are allowed to transfer data while all other sensor-hubs are in a halted mode.
  • this assignment occurs after every reboot of the sensor hub or gateway application).
  • This correlation ID is appended in each of the frames along with 50 accelerometer data points and sent to the gateway. Every frame which has the same correlation ID is considered to be part of the data that all belongs to the one time instance and is assembled together at the gateway to reconstruct the whole data sample.
  • the order in which the individual frames (including 50 data points) arrive at the gateway does not change. Even if a particular frame is lost, the networking protocol ensures that frames are delivered in-order and at least once.
  • the gateway assembles the frames in-sequence.
  • a particular sensor hub is offline for more than a predetermined time interval (e.g., 30 seconds) after beginning a transmission of sensor data, then the gateway will give the sensor hub a second chance to respond (e.g., an additional predetermined time interval of 30 seconds). After that, the gateway can discard the partial data received from the sensor hub, as partial data is generally not useful for analysis.
  • a predetermined time interval e.g. 30 seconds
  • sensor hubs transmitting at the same time use the 115.2 kbps throughput of a border router.
  • the network also transmits heartbeat messages and other messages that are internal to the network to ensure proper function of the mesh network. Transmission of sensor data across the network avoids consuming the maximum throughput of the network. For a border router with a maximum throughput of 250 kbps, more than two sensor hubs transmitting data simultaneously clogs the network, and the network failed transmissions may create an avalanche of further failures.
  • groups of sensor hubs are configured such that each group includes two sensor hubs. When a sensor hub is not a member of the current group selected for data transmission across the network, the sensor hub is in a halted mode.
  • a halted sensor hub receives a response message from the gateway of "stop data transmission" in response to their heartbeat request.
  • the halted sensor hubs continue to transmit heartbeat messages at predetermined intervals and wait for a start data transmission response from the gateway.
  • a sensor hub will initiate capture of sensor data after receiving a start response message from the gateway.
  • a sensor hub is placed in a low power mode when the sensor hub is not actively sampling. For example, after receipt of a "stop data transmission," a sensor hub can enter a low power mode. The low power mode enables the sensor hub to conserve power consumption and extend battery life.
  • Figure 5 is a block diagram of a system 500 that enables an end-to-end wireless sensor hub system.
  • the system 500 can execute the process 400 of Figure 4 .
  • the system 500 includes, among other equipment, a controller 502.
  • the controller 502 is small in size and operates with lower processing power, memory and storage when compared to other processors such as GPUs or CPUs. In some embodiments, the controller 502 consumes very little energy and is efficient.
  • the controller 502 is a component of (or is) a mobile device, such as a cellular phone, tablet computer, and the like. In some cases, the controller 502 is operable using battery power and is not required to be connected to mains power.
  • the controller 502 includes a processor 504.
  • the processor 504 can be a microprocessor, a multi-core processor, a multithreaded processor, an ultra-low-voltage processor, an embedded processor, or a virtual processor.
  • the processor 504 can be part of a system-on-a-chip (SoC) in which the processor 504 and the other components of the controller 502 are formed into a single integrated electronics package.
  • SoC system-on-a-chip
  • the processor 504 can communicate with other components of the controller 502 over a bus 506.
  • the bus 506 can include any number of technologies, such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies.
  • ISA industry standard architecture
  • EISA extended ISA
  • PCI peripheral component interconnect
  • PCIx peripheral component interconnect extended
  • PCIe PCI express
  • the bus 506 can be a proprietary bus, for example, used in an SoC based system.
  • Other bus technologies can be used, in addition to, or instead of, the technologies above.
  • the bus 506 can couple the processor 504 to a memory 508.
  • the memory 508 is integrated with a data storage 510 used for long-term storage of programs and data.
  • the memory 508 can include any number of volatile and nonvolatile memory devices, such as volatile random-access memory (RAM), static random-access memory (SRAM), flash memory, and the like. In smaller devices, such as programmable logic controllers, the memory 508 can include registers associated with the processor itself.
  • the storage 510 is used for the persistent storage of information, such as data, applications, operating systems, and so forth.
  • the storage 510 can be a nonvolatile RAM, a solid-state disk drive, or a flash drive, among others.
  • the storage 510 will include a hard disk drive, such as a micro hard disk drive, a regular hard disk drive, or an array of hard disk drives, for example, associated with a distributed computing system or a cloud server.
  • the bus 506 couples the processor 504 to an input/output interface 512.
  • the input/output interface 512 connects the controller 502 to the input/output devices 514.
  • the input/output devices 514 include printers, displays, touch screen displays, keyboards, mice, pointing devices, and the like.
  • one or more of the I/O devices 514 can be integrated with the controller 502 into a computer, such as a mobile computing device, e.g., a smartphone or tablet computer.
  • the controller 502 also includes machine learning models 516.
  • the machine learning models 516 are trained using sensor data captured by one or more sensor hubs 518. Sensor data from the sensor hubs 518 is transmitted to the machine learning models 516 using a gateway 520.
  • the gateway 520 enables the controller 502 to transmit and receive information across a network 522. Although not shown in the interests of simplicity, several similar controllers 502 can be connected to the network 522.
  • implementations of the subject matter and the functional operations described above can be implemented in other types of digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.
  • Implementations of the subject matter described in this specification such as control of a data generation, model training, and model execution can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program carrier, for example a computer-readable medium, for execution by, or to control the operation of, a processing system.
  • the computer readable medium can be a machine readable storage device, a machine readable storage substrate, a memory device, or a combination of one or more of them.
  • system may encompass all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers.
  • a processing system can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
  • a computer program (also known as a program, software, software application, script, executable logic, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • a computer program does not necessarily correspond to a file in a file system.
  • a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).
  • a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile or volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks or magnetic tapes; magneto optical disks; and CD-ROM, DVD-ROM, and Blu-Ray disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks or magnetic tapes
  • magneto optical disks e.g., CD-ROM, DVD-ROM, and Blu-Ray disks.
  • the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
  • a server is a general purpose computer, and sometimes it is a custom-tailored special purpose electronic device, and sometimes it is a combination of these things.
  • Implementations can include a back end component, e.g., a data server, or a middleware component, e.g., an application server, or a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described is this specification, or any combination of one or more such back end, middleware, or front end components.
  • the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)
EP23163083.1A 2022-03-21 2023-03-21 Système de concentrateur-capteur sans fil bout à bout Pending EP4250037A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US202263322055P 2022-03-21 2022-03-21

Publications (1)

Publication Number Publication Date
EP4250037A1 true EP4250037A1 (fr) 2023-09-27

Family

ID=85571356

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23163083.1A Pending EP4250037A1 (fr) 2022-03-21 2023-03-21 Système de concentrateur-capteur sans fil bout à bout

Country Status (2)

Country Link
US (1) US20230297058A1 (fr)
EP (1) EP4250037A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080211666A1 (en) * 2007-03-02 2008-09-04 Motorola, Inc. Method and apparatus for battery-aware dynamic bandwidth allocation for groups of wireless sensor nodes in a wireless sensor network
US20140274181A1 (en) * 2013-03-15 2014-09-18 Rosemount Inc. Resource optimization in a field device
CN109640283A (zh) * 2018-12-28 2019-04-16 北京航天测控技术有限公司 一种基于自供能技术的低功耗无线传感网络设计方法
US20200379442A1 (en) * 2019-05-09 2020-12-03 Aspen Technology, Inc. Combining Machine Learning With Domain Knowledge And First Principles For Modeling In The Process Industries

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080211666A1 (en) * 2007-03-02 2008-09-04 Motorola, Inc. Method and apparatus for battery-aware dynamic bandwidth allocation for groups of wireless sensor nodes in a wireless sensor network
US20140274181A1 (en) * 2013-03-15 2014-09-18 Rosemount Inc. Resource optimization in a field device
CN109640283A (zh) * 2018-12-28 2019-04-16 北京航天测控技术有限公司 一种基于自供能技术的低功耗无线传感网络设计方法
US20200379442A1 (en) * 2019-05-09 2020-12-03 Aspen Technology, Inc. Combining Machine Learning With Domain Knowledge And First Principles For Modeling In The Process Industries

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ARORA (RESEARCH SCHOLAR) VISHAL KUMAR ET AL: "A survey on LEACH and other's routing protocols in wireless sensor network", OPTIK, WISSENSCHAFTLICHE VERLAG GMBH, DE, vol. 127, no. 16, 26 April 2016 (2016-04-26), pages 6590 - 6600, XP029544100, ISSN: 0030-4026, DOI: 10.1016/J.IJLEO.2016.04.041 *
WIKIPEDIA: "Wireless sensor network", 18 November 2019 (2019-11-18), XP055718451, Retrieved from the Internet <URL:https://en.wikipedia.org/w/index.php?title=Wireless_sensor_network&oldid=926811057> [retrieved on 20200727] *

Also Published As

Publication number Publication date
US20230297058A1 (en) 2023-09-21

Similar Documents

Publication Publication Date Title
EP3668192B1 (fr) Procédé et système d&#39;amélioration de la durée de vie de batterie pour dispositifs de faible puissance dans des réseaux de capteurs sans fil
RU2547708C2 (ru) Информационная система для промышленных машин, включающая в себя циклически повторяющееся информационное сообщение машины
EP2558916B1 (fr) Architecture pour des outils activés par réseau
US9465371B2 (en) Building automation and control system and method for operating the same
CN110291242A (zh) 利用针位传感器信号的生产信息计算系统及其方法
US10219134B2 (en) Bluetooth low energy based emergency backup and recovery solution in an industrial controller
WO2022216522A2 (fr) Maintenance prédictive d&#39;équipement industriel
CN103294020A (zh) 无线控制设备中的调度功能
WO2021050545A1 (fr) Dispositif capteur et protocole de communication sans fil sécurisé
CN104898525A (zh) 一种数据采集装置、数据采集系统以及数据采集方法
Gatial et al. Concept of energy efficient ESP32 chip for industrial wireless sensor network
WO2013040850A1 (fr) Système et procédé basés sur l&#39;informatique en nuage pour la gestion et la commande d&#39;un appareil de traitement d&#39;air
EP4250037A1 (fr) Système de concentrateur-capteur sans fil bout à bout
US11794923B2 (en) Aircraft refueling system
CA3122404C (fr) Systemes et procedes de surveillance d&#39;un systeme de criblage
US20240184282A1 (en) Predictive maintenance of industrial equipment
US12045041B2 (en) Wireless communication for industrial automation
CN116128059A (zh) 基于数字孪生推断马达能耗
KR102549411B1 (ko) 멀티홉 메쉬 네트워크용 통신장치
ES2687460T3 (es) Control de un sistema domótico
US20230396968A1 (en) On-location telemetry subscriptions
CN113475125B (zh) 用于操作无线现场设备网络的方法
RU2819589C1 (ru) Датчик для генерации данных управления мощностью
KR20120137584A (ko) 건물 내 효율적인 환경정보를 모니터링하기 위한 환경정보 센서 네트워크 시스템
WO2022038884A1 (fr) Procédé de finalisation de trajet de communication dans un système de surveillance, et système de surveillance

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230321

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20240619