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 42 of 319<br />

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

flow QoS description, which allows to support both an Intserv and diffserv type of architectures <strong>in</strong> the access<br />

network (a mapp<strong>in</strong>g between RSVP QoS parameters, and the MAC layer QoS parameters is def<strong>in</strong>ed).<br />

Multicast connection and mapp<strong>in</strong>g with IGMP are also described at the MAC level; furthermore the standard<br />

<strong>in</strong>cludes layer 2 unicast and multicast encryption and authentication tools to ensure subscriber privacy, and<br />

prevent term<strong>in</strong>al clon<strong>in</strong>g.<br />

Security is therefore supported both for unicast and multicast sessions.<br />

The requirement for evolv<strong>in</strong>g the standards are a higher capacity downstream (200 Mbps +) and upstream (100<br />

Mbps +), <strong>in</strong> order to accommodate video related services.<br />

7.2.2.2.3 IP architecture<br />

A complete IP architecture (Figure 11) is def<strong>in</strong>ed <strong>in</strong> the access network for voice communication, and could be<br />

extended <strong>in</strong> general to multimedia services requir<strong>in</strong>g QoS.<br />

Signall<strong>in</strong>g is based on a centralised architecture and th<strong>in</strong> client model (MGCP), and mostly applicable to<br />

telephony services. 2 QoS models are def<strong>in</strong>ed: the most applicable one (called dynamic QoS) relies on Intserv,<br />

and def<strong>in</strong>e the access QoS architecture us<strong>in</strong>g RSVP, or more generally a per flow resource reservation. Another<br />

variant assumes a diffserv architecture. COPS is the protocol of choice for communication between the CMTS<br />

(Or Access Node) and the CMS for policy and authorisation purpose.<br />

Interdoma<strong>in</strong> signall<strong>in</strong>g def<strong>in</strong>es SIP or H248 for signall<strong>in</strong>g between different doma<strong>in</strong>s; <strong>in</strong>terdoma<strong>in</strong> QoS is<br />

obviously not precisely def<strong>in</strong>ed yet, but some recommendations exist.<br />

This centralised architecture is well adapted to a telephony case, but not really scalable to multimedia.<br />

Figure 11: IP-architecture for cable networks

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

Saved successfully!

Ooh no, something went wrong!