An improved design of P4P based on distributed tracker Online publication date: Tue, 10-Apr-2018
by Lixin Li; Feng Wang; Wentao Yu; Xiuqing Mao; Mengmeng Yang; Zuohui Li
International Journal of Information and Communication Technology (IJICT), Vol. 13, No. 3, 2018
Abstract: The P4P architecture is mainly composed of appTracker, iTracker and peer. The single appTracker manages sharing resources in the different ISP domains. Every peer registers with appTracker when joining the network, and then requests resources from appTracker. In this architecture, there is too much workload for the single appTracker, thus, the bottleneck problem often appears when the scale of the network is enlarged in this centralised structure. An improved design of P4P based on distributed tracker is proposed to solve the overload problem of single appTracker server. In the improved P4P system, a distributed tracker overlay network replaces the appTracker to manage the resources in the different ISP domains. The functions of iTracker arranged by ISP are extended and the info interfaces of the iTracker are designed in detail in order to realise sharing the resources among the different iTrackers. The experiments prove that the P4P framework based on the distributed tracker can solve the server bottleneck problem and improve the scalability and stability while maintaining the characteristics of locality and transmission capacity.
Online publication date: Tue, 10-Apr-2018
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Information and Communication Technology (IJICT):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email firstname.lastname@example.org