] >
This set of rules been designed to be efficient in transmitting a data-stream from a splitter node to peers in the network when unicast transmissions are used between the nodes of the team.
(2) |
being the number of peers in the team. Next, must forward this chunk to the rest of peers of the team. Chunks received from other peers are not retransmitted.
In incomming peer performs:
Because the [hello] messages can be lost, some peer of the team could not know in this presentation. However, because peers also learh about their neighbors when a [IMS] message is received, the impact of these lost should be small.
Notice that this rule will remove from the peer’s lists those peers that perform a impolite churn (those peers that leave the team without sending the [goodbye] message).
where is the average encoding rate of the stream. When the size of the team is , the transmission rate of all peers (included the monitor peers, obviously) of the team is:
(3) |
Therefore, only the first (monitor) peer is included in the team without a initial transmission requirement. Notice also that
(4) |
which means that when the team is large enough, all the peers of the team will transmitt the same amount of data that they receive.
In order to handle this unpredictable retransmission delay, the peer’s buffers should store at least chunks. This means that, the team size is limited by the buffer size, i.e., in the DBS module it must be hold that
(5) |