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 />

a remote CN. When a configurable amount of time has been expired after all remote bindings have been<br />

expired, the dormant state watchdog initiates dormant state transition, notifying the MT dormant state<br />

manager block. However, for demonstration purposes, the dormant state transition is triggered manually<br />

from the NCP and indicated to the paging module through the MTNM and the MT dormant state<br />

manager. This allows dormant registration without waiting for expiration of remote binding entries.<br />

Optionally, automatic dormant state transition might be supported in the dormant state watchdog, based<br />

on timers and remote CNs' binding cache entries' lifetime for the respective MN. Also, in case of mobile<br />

terminal initiated active registration with the network is to be shown, this is also done via the NCP for<br />

demonstration purposes. Optionally, detection of packets to be sent from an application and automatic<br />

active registration initiation might be supported.<br />

4.1.2.6.2 Common ID handler<br />

Independent of L2 identifiers for addressing or paging purposes, the IP paging concept deploys a common<br />

paging identifier, allowing the MT to be identified independent of access technology specifics. A<br />

structure for a common IP paging identifier has been proposed, allowing paging attendants implemented<br />

with ARs to map the generic IP paging request messages to access technology specific addressing and to<br />

build IPv6 Solicited Node Multicast Addresses for individual access technologies and their respective<br />

interface identifiers. On IP level, this common identifier is used to address and to identify mobile<br />

terminals on IP layer. According to the previous specifications, MAC address parts of each interface<br />

implemented in the mobile terminal are included in the common paging ID, which is to be built by the<br />

common ID handler block. To gather information on each interface’s MAC address, the common ID<br />

handler block requests a list of interface addresses from the respective MTNM entity. The derivation of<br />

the common paging ID is to be done on module loading time, assuming that the interfaces do not change<br />

afterwards. An enhanced mechanism could trigger the common ID handler to build a new ID when a new<br />

interface has been brought up in the mobile terminal. To take hot-plugging of networking interfaces into<br />

consideration for future systems, the Common ID handler requests MAC addresses of available access<br />

interfaces each time the mobile enters dormant mode. This allows always for updated and valid MAC<br />

addresses to be incorporated into the common paging identifier. In addition to MAC address info of<br />

implemented access interfaces, the MTNM provides the Common ID handler with information on the<br />

current Access Router, since this information is kept updated in the MTNM.<br />

4.1.2.6.3 MT dormant state manager<br />

The mobile terminal dormant state manager is the high-level entity for maintenance of dormant/active<br />

state as well as for initiation of the signalling procedure for state transition purposes. On receipt of a<br />

notification from the dormant mode watchdog to enter the dormant mode, the dormant state manager<br />

initiates the signalling procedure by contacting the signalling state machine block. After the Paging Agent<br />

discovery phase and the dormant registration procedure have been initiated, an intermediate state should<br />

be entered, indicating that the mobile is going to enter a dormant mode. Active or passive session<br />

initiation while being in this intermediate state would cause immediate re -establishment of active state<br />

behaviour. When the dormant registration has completed successfully, active session initiation would<br />

cause initiation of the normal dormant de-registration procedure. Incoming packets can reach a dormant<br />

mobile terminal, which has entered dormant state before, only after a successful paging and deregistration<br />

procedure, including re -establishment of system information.<br />

Furthermore, this block should store information on the discovered Paging Agent address.<br />

4.1.2.6.4 Signalling state machine<br />

The signalling state machine block has the responsibility to handle the PA discovery and the registration<br />

procedure, therefore representing an abstraction layer between the dormant state manager and the actual<br />

signalling procedure. High granularity states should be maintained within this block. To initiate the<br />

signalling procedure for dormant mode registration, the respective notification comes always from the<br />

‘high-level’ dormant state manager. In case of having entered the dormant mode before, an incoming<br />

paging request is directly to be processed from the signalling state machine, common paging ID matching<br />

is to be checked with the common paging ID block and high-level actions are to be requested from the<br />

dormant state manager.<br />

4.1.2.7 Registration Module<br />

D0103v1.doc 36 / 168

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

Saved successfully!

Ooh no, something went wrong!