Downloads provided by UsageCounts
handle: 2117/393910
En la empresa en la que trabajo, Albedo Telecom, se desarrolló un dispositivo llamado Net.Time. La función de este dispositivo es la de trabajar como master en una red que trabaje con el protocolo PTP. El protocolo PTP (Precise Time Protocolo) es un protocolo de sincronización de dispositivos que usa la jerarquía de master-slave. El master recibe su tiempo de referencia desde una fuente de tiempo de alta precisión. Los slaves se comunican con el master mediante intercambio de paquetes para ir sincronizando sus relojes internos con el del master. Cuando Net.Time fue lanzado al mercado, se ofrecía una capacidad de servicio para 256 slaves, pero este valor nunca fue comprobado empíricamente. En este proyecto se desarrollará una herramienta que simula el comportamiento del protocolo PTP. El objetivo principal es simular una serie de slaves para que ataquen a un Net.Time con la intención de ver a cuantos slaves puede dar servicio este dispositivo. La herramienta desarrollada no ha sido del todo terminada, la parte unicast no se ha terminado. Pero se han podido realizar tests usando el modo de direccionamiento multicast. Estos tests han probado diferentes conjuntos de slaves, se han hecho pruebas con 256 slaves, con 512 slaves y con 1024 slaves. Los resultados obtenidos han sido satisfactorios, se ha comprobado que, en modo multicast, Net.Time es capaz de dar servicio a 1024 slaves, más de lo que se prometía a los clientes. No se ha encontrado el límite de servicio del master ya que para más cantidad de slaves los tests tardaban mucho en procesarse y no ha dado tiempo de realizarlos.
In the company where I work, Albedo Telecom, a device called Net.Time was developed. The function of this device is to work as a master in a network that works with the PTP protocol. The Precise Time Protocol (PTP) is a device synchronization protocol that uses the master-slave hierarchy. The master receives its reference time from a high precision time source. The slaves communicate with the master by exchanging packets to synchronize their internal clocks with the master's. When Net.Time was released, a service capacity for 256 slaves was offered, but this value was never empirically proven. This project will develop a tool that simulates the behavior of the PTP protocol. The main objective is to simulate a series of slaves to attack a Net.Time with the intention of seeing how many slaves this device can serve. The tool developed has not been completely finished, the unicast part has not been finished. But tests could be performed using multicast addressing mode. These tests have tested different sets of slaves, tested 256 slaves, 512 slaves and 1024 slaves. The results have been satisfactory, it has been proven that, in multicast mode, Net.Time is able to serve 1024 slaves, more than what was promised to customers. The serve limit of the master has not been found since for more slaves the tests took a long time to process and it has not given time to perform them.
PTP, esclau, Announce message, Delay-Reponse message, missatge de Announce, master, missatge de Delay-Request, Àrees temàtiques de la UPC::Enginyeria de la telecomunicació::Telemàtica i xarxes d'ordinadors, rellotge PTP, clock PTP, Sync message, Delay-Request message, missatge de Sync, Computer network protocols, missatge de Delay-Response, slave, Protocols de xarxes d'ordinadors
PTP, esclau, Announce message, Delay-Reponse message, missatge de Announce, master, missatge de Delay-Request, Àrees temàtiques de la UPC::Enginyeria de la telecomunicació::Telemàtica i xarxes d'ordinadors, rellotge PTP, clock PTP, Sync message, Delay-Request message, missatge de Sync, Computer network protocols, missatge de Delay-Response, slave, Protocols de xarxes d'ordinadors
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
| views | 104 | |
| downloads | 66 |

Views provided by UsageCounts
Downloads provided by UsageCounts