03.11.2012 Views

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4-June-07 P1901_PRO_016_r0<br />

Service Class Application<br />

Examples<br />

7 Management<br />

messages<br />

6 VoIP<br />

5 Video, Games<br />

4 Data Highprio<br />

3 Data Highprio<br />

2 Data Highprio<br />

1 Data Lowprio<br />

0 Data Lowprio<br />

Table 19 Mapping applications to service classes: example<br />

8.2.6 Provisioning Service Class Definitions to slaves<br />

As detailed in 0, nodes that wish to request a resource reservation through the Connection Admission <strong>Control</strong><br />

procedure must make a reference to the requested service class. As a matter of fact, it is necessary for the slaves to<br />

have an idea of the service class definitions. The description of the available service classes will be obtained<br />

through the Autoconfiguration process.<br />

8.3 CONGESTION MANAGEMENT<br />

The mission of CM is to manage the accepted connections in congested networks (due to a sudden drop in the<br />

channel quality, for example). There are two possible policies that can be configured in the system:<br />

• Fair Congestion Management Policy (FCMP): all traffic flows are treated equally. Therefore, if the<br />

traffic scheduler cannot meet the b<strong>and</strong>width <strong>and</strong> latency requirements from users, it will decrease the<br />

performance of all active flows equally until new b<strong>and</strong>width <strong>and</strong> latency definitions can be supported.<br />

Submission page 183 UPA-OPERA

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

Saved successfully!

Ooh no, something went wrong!