26.12.2012 Views

Project Number: FP6-IST-507554 Project Title: BROADBAND in ...

Project Number: FP6-IST-507554 Project Title: BROADBAND in ...

Project Number: FP6-IST-507554 Project Title: BROADBAND in ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Page 46 of 319<br />

<strong>FP6</strong>-<strong>IST</strong>-<strong>507554</strong>/JCP/R/Pub/D2.2-3.2<br />

Different technological choices are possible, ma<strong>in</strong>ly based on an evolution to centralized or decentralized<br />

architectures:<br />

• A centralized architecture corresponds to today cable access networks implementations, and has the<br />

follow<strong>in</strong>g classical advantages:<br />

- Network easy to ma<strong>in</strong>ta<strong>in</strong> and reliable, as all the “<strong>in</strong>telligent” (layer 3 and above) elements are<br />

centralized<br />

- Cheap user term<strong>in</strong>al, as the signall<strong>in</strong>g protocols are very light (like MGCP for <strong>in</strong>stance)<br />

- A network capacity <strong>in</strong>crease can be imag<strong>in</strong>ed under these assumptions.<br />

• The current trend is to evolve to a decentralized architecture where the network elements are placed<br />

closer to the subscriber. It is based on peer to peer signall<strong>in</strong>g paradigms like SIP. The current<br />

economical drawbacks of this architecture (reliability and ma<strong>in</strong>ta<strong>in</strong>ability, network elements and<br />

term<strong>in</strong>al costs) will no longer apply <strong>in</strong> the future, and the complexity is compensated by the scalability<br />

of the architecture.<br />

Figure 14: Technology roadmap related with network capacity<br />

Different technology roadmaps (Figure 14) can be deduced accord<strong>in</strong>g to the 2 categories of paradigms which<br />

will prevail <strong>in</strong> the future (centralized or decentralized), correspond<strong>in</strong>g to different application scenarios (peer to<br />

peer will most probably lead to decentralized architectures, whereas client server types of applications would<br />

lead to centralized architectures).<br />

Note that upper layer and lower layers centralized and decentralized architecture can be uncorrelated (upper<br />

layer decentralized model can be implemented over a centralized architecture).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!