13.07.2015 Views

Praise for Fundamentals of WiMAX

Praise for Fundamentals of WiMAX

Praise for Fundamentals of WiMAX

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.

9.1 Convergence Sublayer 3099.1 Convergence SublayerTable 9.1 shows the various higher-layer protocol convergence sublayers—or combinations—that are supported in <strong>WiMAX</strong>. Apart from header compression, the CS is also responsible <strong>for</strong>mapping higher-layer addresses, such as IP addresses, <strong>of</strong> the SDUs onto the identity <strong>of</strong> the PHYand MAC connections to be used <strong>for</strong> its transmission. This functionality is required becausethere is no visibility <strong>of</strong> higher-layer addresses at the MAC and PHY layers.The <strong>WiMAX</strong> MAC layer is connection oriented and identifies a logical connection betweenthe BS and the MS by a unidirectional connection indentifier (CID). The CIDs <strong>for</strong> UL and DLconnections are different. The CID can be viewed as a temporary and dynamic layer 2 addressassigned by the BS to identify a unidirectional connection between the peer MAC/PHY entitiesand is used <strong>for</strong> carrying data and control plane traffic. In order to map the higher-layer address tothe CID, the CS needs to keep track <strong>of</strong> the mapping between the destination address and therespective CID. It is quite likely that SDUs belonging to a specific destination address might becarried over different connections, depending on their QoS requirements, in which case the CSdetermines the appropriate CID, based on not only the destination address but also various otherfactors, such as service flow 1 ID (SFID) and source address. As shown in Table 9.1 the IEEE802.16 suite <strong>of</strong> standards defines a CS <strong>for</strong> ATM (asynchronous transfer mode) services andpacket service. However, the <strong>WiMAX</strong> Forum has decided to implement only IP and Ethernet(802.3) CS.9.1.1 Packet Header SuppressionOne <strong>of</strong> the key tasks <strong>of</strong> the CS is to per<strong>for</strong>m packet header suppression (PHS). At the transmitter,this involves removing the repetitive part <strong>of</strong> the header <strong>of</strong> each SDU. For example, if the SDUsdelivered to the CS are IP packets, the source and destination IP addresses contained in theheader <strong>of</strong> each IP packet do not change from one packet to the next and thus can be removedbe<strong>for</strong>e being transmitted over the air. Similarly at the receiver: The repetitive part <strong>of</strong> the headercan be reinserted into the SDU be<strong>for</strong>e being delivered to the higher layers. The PHS protocolestablishes and maintains the required degree <strong>of</strong> synchronization between the CSs at the transmitterand the receiver.In <strong>WiMAX</strong>, PHS implementation is optional; however, most systems are likely to implementthis feature, since it improves the efficiency <strong>of</strong> the network to deliver such services as VoIP.The PHS operation is based on the PHS rule, which provides all the parameters related to headersuppression <strong>of</strong> the SDU. When a SDU arrives, the CS determines the PHS rule to be used, basedon such parameters as destination and source addresses. Once a matching rule is found, it providesa SFID, a CID and PHS-related parameters to be used <strong>for</strong> the SDU. The PHS rule can bedependent on the type <strong>of</strong> service, such as VoIP, HTTP, or FTP, since the number <strong>of</strong> bytes that canbe suppressed in the header is dependent on the nature <strong>of</strong> the service. In <strong>of</strong> VoIP, <strong>for</strong> example,the repetitive part <strong>of</strong> the header includes not only the source and destination IP addresses but1. The concept <strong>of</strong> service flow is discussed in Section 9.2.

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

Saved successfully!

Ooh no, something went wrong!