REMPLI PLC network is designed to cope with the specific characteristics of the communication channel. In [1], we have shown its good behaviours from the network performance point of view (minimized network transfer delay with small protocol overheads). However, when the REMPLI PLC is used for supporting REMPLI applications which share the same available bandwidth but require different quality of service (e.g. periodic transfer for network management services, short end to end delay for aperiodic data request services, urgent alarm handling, etc.), the REMPLI PLC must also give the possibility to serve those applications differently in order to satisfy their different QoS (Quality of Service) requirements. This comes to say that a traffic scheduling policy must be defined and implemented. The purpose of this document is, on the one hand, to describe the traffic scheduling policy adopted in REMPLI PLC as well as its implementation under the name of Dispatcher, and on the other hand to prove its benefice in providing for the different application traffic with the differentiated QoS. In this sense, the Dispatcher ensures therefore the QoS mapping between an application and a REMPLI PLC network traffic class. This document first recalls the application services defined within the REMPLI project, gives then the traffic classes that the REMPLI PLC network supports as well as the mapping between them. The adopted network traffic scheduling policy is then explained and the principle of the dispatcher described. Finally simulations have been carried out showing the interest of the proposed dispatcher.