diff --git a/README.en.md b/README.en.md index 9fd2204..52c1189 100644 --- a/README.en.md +++ b/README.en.md @@ -1,20 +1,185 @@ -
Read in other languages: Português, Español
-This repository aims to promote the development of a multi-vendor management platform for IoTs. Any device that follows the TR-369 protocol can be managed. The form of communication with the IoT chosen for the project is MQTT. The main objective of the undertaking is to facilitate and unify device management, which generates countless benefits for the end user and service providers, extinguishes old problems in the telecommunications area and suppresses the demands that today's technologies require: device interconnection, data collection, speed, availability and much more. +This repository aims to promote the development of a multi-vendor management platform for IoTs. Any device that follows the TR-369 protocol can be managed. The main objective is to facilitate and unify device management, which generates countless benefits for the end user and service providers, suppressing the demands that today's technologies require: device interconnection, data collection, speed, availability and much more. . +
++The advent of the Internet of Things brings countless opportunities and challenges for service providers, with over a billion devices across the globe today making use of TR-069, what is the future of the protocol and what can we expect ahead?
-With the creation of new technologies, it became necessary to create a more robust solution that covered a wider range of niches, so the TR-369 emerged, seeking to fill gaps in its predecessor (TR-069), which served its purpose well at the time, but now undergoes depreciation. With that in mind, we seek to bring an alternative to IT integrators, providers, system administrators, and others who may be interested. -
--This solution is inspired by the project GenieACS and other commercial solutions found on the market. We seek to strictly follow the specifications of USP TR-369, choosing to use MQTT in the MTP (Message Transfer Protocol) layer. +The CWMP (CPE Wan Management Protocol), better known as TR-069, opened many doors for the ecosystem of providers, through which it is possible to deliver services with agility, which meet or exceed customer expectations, with proactive management and secure network, also bearing in mind the lower cost and greater efficiency for service providers.
++With the rise of what we now call the smart home, the Internet of Things and the demand for increasingly interconnected and cloud-based environments, new demands and obstacles have emerged, opening the door to the creation of a new form of communication that meets the needs of current market needs. +
++There is a fierce race to monetize the IoT devices that are now part of the connected home and other environments. As a result, many companies are creating their own proprietary solutions; this is understandable given such pressure generated by the promise of Smart Home monetization. Unfortunately, these applications contribute to a poor ecosystem, where a provider ends up dependent and limited to a vertical solution, from a single vendor. This generates an low competition environment (which leads to greater risks), less innovation, and the potential for very high cost solutions. +
++The technologies behind Wi-Fi, device-to-device connectivity, the Smart Home and IoTs are constantly evolving and improving. It is important that when service providers look for a solution, they look for something that is "future proof", always thinking ahead. +
++Seeking to solve the challenges mentioned above, providers and manufacturers together developed the USP (User Services Platform), defined by the Broadband Forum's TR-369 standard, which is the natural evolution of the TR-069. This new standard is designed to be flexible, secure, scalable and standardized to meet the demands of a connected world today, and in the future. +
+ +
+
+
+
+
+
++leandro@leandro-laptop:~$ cd oktopus/devops +leandro@leandro-laptop:~/oktopus/devops$ docker compose up ++
Bibliographic sources: MU-461.pdf, TR-369.html, USP Training Session SlidesTR-369.html a>