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 />
DomainD<br />
DomainE<br />
PA<br />
DomainB2<br />
AAAC.h<br />
QoSB.h<br />
CN<br />
PALa<br />
QoSBa<br />
AAAC.fa<br />
DomainA<br />
Rax<br />
QoS aware<br />
IP Backbone<br />
AAAC.fc<br />
QoSBc<br />
HA<br />
DomainB1<br />
DomainC<br />
Rcx<br />
RARa1 RARa2 RARc1<br />
IPsubnetA1<br />
W-CDMA<br />
IPsubnetA2<br />
W-CDMA<br />
IPsubnetC1<br />
802.11<br />
RARc2<br />
IPsubnetC2<br />
W-CDMA<br />
ARc3<br />
IPsubnetC3<br />
Ethernet<br />
MT<br />
Figure 2: Conceptual view of the <strong>Moby</strong> <strong>Dick</strong> architecture<br />
The Home Agent (HA), “home” QoS Broker (QoSB.h), and the Home AAAC server (AAAC.h) are<br />
placed currently in the same home domain – Domain B. However, this is not a must. Both, the HA and<br />
the QoS.h have to be placed in the same domain but the AAAC.h can be located somewhere else in a<br />
different domain. In this case, some additional AAA communication has to take place. Of course, each<br />
domain operated a Home Agent (HA), but for not giving the impression that a mobile user could establish<br />
dynamically relations to different Has, in the figure above only one HA is shown.<br />
The Paging Agent (PA) will be somewhere, connected as well through a QoS aware network technology<br />
to the backbone.<br />
For <strong>Moby</strong> <strong>Dick</strong> access networks the following components are necessary:<br />
• QoSB: QoS Broker for management of the QoS “requests” via profiles.<br />
• AAAC.f: Foreign AAAC server for handling Authentication, Authorisation, Accounting, and<br />
Charging issues.<br />
• (Radio) Access Routers: They are policy points in the access network. Each air interface TD-<br />
CDMA or wireless LAN (802.11) – will cover one IP sub-network. The Radio Access Router<br />
(RAR) will have at least one radio interface and one fixed line interface to the domain network.<br />
Access Router (AR) will have only interfaces to fixed lines and to each access interface a subnetwork<br />
will be assigned.<br />
• Routers (R): They are normal ingress (for incoming flows), egress (for leaving flows), and<br />
interior (inside a DS domain) DS routers.<br />
Optional for the access domains will be a local Paging Agent (PA). A local PA offers direct<br />
communication, if needed. This leads to less signalling through the backbone.<br />
The following components have to be Differentiated Services capable:<br />
• CN or the router next to this node: The CN is the source of the flow.<br />
D0103v1.doc 13 / 168
Change language