Internet of Things: Building a real-time device management system

Family networks have long been commonplace, and now there will be more families connected to the network. With the connection of thousands of households, the goal of the Internet of Things will soon be realized!

The number of devices accessing the Internet in the home environment is increasing dramatically, while other IoT devices will explode in terms of numbers and categories. Faced with such a scale of development, efficient monitoring and automated management is undoubtedly the core of the success of the Internet of Things.

Fortunately, the poadband Forum has provided a solid foundation for remote monitoring and device management at the link level, namely the TR-069 standard. Now, our biggest obstacle lies in the existence of many years of network IP-driven device communication protocol, SNMP. However, with the popularity of TR-069, we have been able to see it on routers, gateways, set-top boxes, VOIP phones and other devices.

In today's article, we will explore how to transform a device management system from a passive and remedial solution to an active real-time tool.

Equipment Management Challenges and Architecture

The biggest challenge in equipment management is that we need to face a very large number of equipment from different manufacturers, and the implementation cost of management services can not be too high. Obviously, a solution that is too costly or requires the end user to constantly restart the device is not an ideal solution.

TR-069 allows each Auto Configuration Server (ACS) to know the device type, manufacturer, serial number, and upload device logs. TR-069 helps users understand the online status, last configuration change and restart of the device through "heartbeat". In addition, the ACS can also request the device to download an updated configuration or a new firmware. TR-069 can even recover from a device failure.

Unfortunately, customer-owned devices have an extremely wide range of uses and configurations, which means they have a high probability of failure. Take routers and residential gateways as examples. They may support LAN WEP or WPA2 encryption, DHCP or static IP allocation, provide variable DHCP lease terms, IPv4 and IPv6, and include multiple routing protocols and bridging methods. In addition, objective factors such as power quality, RF interference, temperature, and downloading software can have a huge impact on its operation.

In the face of router failures, users often restart them frequently. This situation will become more common in smart homes and the Internet of Things, and device management has become critical in such scenarios.

Enhance ACS services with scenarios and operations

Simply put, TR-069 is a feedback-oriented design that waits for an offline problem with the device and then takes action. This approach does not eliminate faults in advance and is more costly to implement, so we need an active mode to identify and operate to take the lead in solving potential failures and maximizing uptime.

There are many reasons for the device to go offline, including software quality, device configuration, device loading, power quality, and device overheating.

In fact, a variety of forward-looking event management models have emerged over the past decade, and are now widely used in banking fraud detection, retailer real-time management, and carrier wireless service management. One of the latest designs can use only one 8-core Linux host with 3 million end-user devices on a 64 GB memory management wireless network.

In this design, it defines a set of scenarios that identify the sequence or pattern of events before the device fails. The system is able to combine commonalities in events and take action in advance of meeting these conditions. For example, a device might need to work with a specific configuration. When the configuration log indicates that the customer has enabled unsupported features, the service provider can alert the customer via email to adjust this improper configuration.

In the system shown below, real-time event collaboration is enabled between the ACS server and the real-time event engine (here named EVAM). In the first step, the event engine collects and identifies events in real time. When a scenario is met, the resulting operation jumps directly to the ACS server (step 2)—for example, asking the device to download a new profile, or the third step—by email, phone, or other means of communication with the client. contact.

Internet of Things: Building a real-time device management system

The key to this system architecture is to accurately identify patterns that may lead to failures and implement operations as soon as they are discovered.

to sum up

As you can see, we can easily implement active event detection and device management in the smart home device management system. The solution mentioned in this article has been verified by many companies, and it can realize the low cost and can smoothly convert the original pure passive management mode into a mixed form of active/passive.

Residual Current Circuit Breaker With Over Load Protection

TWO FUNCTION : MCB AND RCCB FUNCTIONS

leakage breaker is suitable for the leakage protection of the line of AC 50/60Hz, rated voltage single phase 240V, rated current up to 63A. When there is human electricity shock or if the leakage current of the line exceeds the prescribed value, it will automatically cut off the power within 0.1s to protect human safety and prevent the accident due to the current leakage.
leakage breaker can protect against overload and short-circuit. It can be used to protect the line from being overloaded and short-circuited as wellas infrequent changeover of the line in normal situation. It complies with standard of IEC/EN61009-1 and GB16917.1.


RCBO,ELCB,Leakage Circuit Breaker,Residual Current Circuit Breaker,Residual Current Circuit Breaker with Over Load Protection 1p,Residual Current Circuit Breaker with Over Load Protection 2p

Wenzhou Korlen Electric Appliances Co., Ltd. , https://www.zjaccontactor.com