27.03.2014 Views

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

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.

D0103v1.doc Version 1 6.7.2003<br />

To summarize:<br />

• The Router Advertisements received by the RG on its interface with the AR are intercepted, sent<br />

to the MT on a dedicated TD-CDMA broadcasting channel. They will be transferred to the IPv6<br />

stack on the MT to configure the CoA of the TD-CDMA interface.<br />

• The Neighbour Solicitation requests received by the RG on its interface with the AR are<br />

intercepted. If they are addressed to one of the MT having an open radio connection with the<br />

RG, the RG will reply to them with a Neighbour Advertisement, on behalf of the correct MT,<br />

using its own MAC address instead of the one from the MT.<br />

• The Paging Requests received by the RG on its interface with the AR are intercepted. If they are<br />

addressed to one of the MT having an open radio connection with the RG, the RG will send them<br />

to the MT on a dedicated TD-CDMA paging channel.<br />

• The IPv6 packets received by the RG on its interface with the AR and addressed to a MT having<br />

an open connection with the RG are intercepted (the global scope IPv6 address or the link local<br />

address of the MT can both be used). These packets are transmitted to the MT on a dedicated<br />

channel, with QoS characteristics determined by the DSCP code of the IPv6 packet.<br />

• The IPv6 packets transmitted by the MT to the RG on a dedicated channel, are forwarded by the<br />

RG on its interface with the AR. These packets will then be properly routed by the AR.<br />

• A specific mechanism has been deployed between the RG and the AR / QoS Broker to manage<br />

the opening of radio bearers between the MT and the RG. It is described in details in the chapter<br />

“Bearer Management” of this document.<br />

5.2.10 Paging<br />

5.2.10.1 Interface between Paging Attendant and Paging Module<br />

5.2.10.1.1 Description<br />

On initial registration with or discovery of the Paging Agent, the mobile terminal contacts the paging<br />

attendant in its current Access Router. The protocol messages for discovery and possibly implicit<br />

dormant registration as well as for implicit dynamic establishment of the paging related security<br />

association are specified as ICMPv6 headers and appropriate options.<br />

5.2.10.1.2 Interface mechanisms<br />

The current access technology provides physical interfacing the mobile terminal to its current Access<br />

Router. The ICMPv6-based protocol, specified for building the paging control plane, is carried over this<br />

interface.<br />

5.2.10.1.3 Interface contents<br />

Source Dest Primitive Parameters<br />

MT PA DORMANT_MODE_REQ According to the protocol described in<br />

D0301.<br />

PA MT DORMANT_MODE_REPL According to the protocol described in<br />

D0301.<br />

Table 58: Interface Contents<br />

5.2.10.2 AR Paging Attendant & RG IWF<br />

5.2.10.2.1 Description<br />

To convey on-link paging control messages from the Access Router, implementing the paging attendant,<br />

to the IWF, implemented in the Radio Gateway, many mechanisms have been evaluated, like tunnelling<br />

mechanisms, UDP/IP encapsulation and RG addressing and IWF controlled re-addressing to the paged<br />

mobile terminal’s Solicited Node Multicast Address. The most transparent and realistic solution has been<br />

selected, keeping the complex paging related functionality within the paging attendant (processing of<br />

options, derivation and addressing of the technology specific solicited node multicast address, …). The<br />

paging attendant generates the PAGING_REQUEST message and provides also appropriate addressing of<br />

the dormant mobile terminal. Since the RG performs Proxy Neighbour Discovery for interception and<br />

mapping of Neighbour Solicitations and Neighbour Advertisements, the same mechanisms is deployed<br />

D0103v1.doc 166 / 168

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

Saved successfully!

Ooh no, something went wrong!