Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
D0103v1.doc Version 1 6.7.2003<br />
The behaviour of the different sub-blocks of the IWF will be detailed in the next chapter.<br />
4.3.1.3 IP stack<br />
The IP stack will be the basic IPv6 stack from the Linux kernel, with no specific functionalities related to<br />
Mobility and AAA. As regards QoS, the DSCP marking software is not needed, as the IP signalling<br />
packets generated by the IWF will be addressed only to the corresponding Access Router.<br />
The IP traffic received from the Mobile Terminal by the TD-CDMA driver will be sent by the IWF to the<br />
Ethernet driver, to be forwarded to the Access Router (raw socket interfaces will be used between the<br />
IWF and the TD-CDMA / Ethernet drivers).<br />
The IP traffic received from the Access Router by the Ethernet driver will not be handled by the IP stack,<br />
but by the IP to TD-CDMA relay block. Depending on its kind, it will be treated by this block, or<br />
transmitted to the TD-CDMA driver (via a raw socket interface), to be sent to the Mobile Terminal.<br />
The only exception is the IP packets for the Radio Gateway QoS Attendant (exchanged with the QoS<br />
Broker, which will go through the IP stack.<br />
IWF<br />
TD-CDMA to<br />
IP relay<br />
QoS<br />
attendant<br />
IP to<br />
TD-CDMA<br />
relay<br />
QoS attendant on AR<br />
Info<br />
Management<br />
Raw Socket<br />
Interface<br />
Standard Socket<br />
Interface<br />
Raw Socket<br />
Interface<br />
Internal interface<br />
Protocol<br />
communication<br />
IPv6 Protocol Stack<br />
Kernel space<br />
Standard Network<br />
Device Interface<br />
User space<br />
TD-CDMA NDD on MT<br />
TD-CDMA Network Device Driver<br />
RCM / RCF<br />
Ethernet<br />
Network<br />
Device<br />
Driver<br />
AS on MT<br />
NAS / AS interface<br />
Access Stratum<br />
4.3.1.4 Radio Channel Manager (RCM)<br />
Figure 56: Radio Gateway Software Architecture.<br />
This module will act as a generic radio driver, giving a high level interface to manage the connections and<br />
the associated data channels; to send and receive IP packets and other specific radio data; and get some<br />
feedback on the radio conditions.<br />
It will be implemented as a kernel module (RCM and RCF will be grouped in a same kernel module,<br />
namely a driver).<br />
The behaviour of the different sub-blocks of the RCM will be detailed in the next chapter.<br />
D0103v1.doc 74 / 168
Change language