Go to file
Leandro Antônio Farias Machado d4b6e6775a chore(controller): ignore tmp folder
2023-06-16 11:29:58 -03:00
.github feat(devops): deploy front on ec2 [test1] 2023-06-03 10:14:16 -03:00
backend/services chore(controller): ignore tmp folder 2023-06-16 11:29:58 -03:00
devops fix(devops): nginx.conf for api 2023-06-08 02:00:11 -03:00
frontend fix(env):api route 2023-06-12 20:12:47 -03:00
.gitignore feat(mqtt): change proj structure to services and add mochi broker 2023-03-20 11:19:02 -03:00
LICENSE Initial commit 2023-02-15 09:49:02 -03:00
README.en.md feat : api documentation close #33 2023-04-27 00:48:50 -03:00
README.es.md feat : api documentation close #33 2023-04-27 00:48:50 -03:00
README.md feat : api documentation close #33 2023-04-27 00:48:50 -03:00

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.

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.

  • Infrastructure:

Oktopus-infra


If you are interested in internal information about the team and our intentions, visit our Wiki.