Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
Router. The acknowledge message USE_WLAN_AR_ACK will be received from the WLAN
driver, with parameter status.
• If TD-CDMA is the new L2 technology, the message OPEN_TD-CDMA_CONN must be sent
to the TD-CDMA driver, with parameters cell Id of selected Radio Gateway, Home Address and
CoA of MT. The acknowledge message OPEN_TD-CDMA_CONN_ACK will be received from
the TD-CDMA driver, with parameters local_connection_reference and status.
• If Ethernet is the old L2 technology, nothing needs to be done.
• If WLAN is the old L2 technology, nothing needs to be done.
• If TD-CDMA is the old L2 technology, the message CLOSE_TD-CDMA_CONN must be sent
to the TD-CDMA driver, with parameter local_connection_reference. The acknowledge
message CLOSE_TD-CDMA_CONN_ACK will be received from the TD-CDMA driver, with
parameters local_connection_reference and status.
• If WCMA is the old and new L2 technology, we will use only the message OPEN_TD-
CDMA_CONN, with a specific parameter (fho_optimisation). The TD-CDMA driver will first
close the old connection, then open the new one, and send the acknowledge message OPEN_TD-
CDMA_CONN_ACK.
If the L2 handover was successful, the MTNM will “link” the IP stack to the new L2 driver and send
message L2_ACK to the FHO module, with status OK.
If the L2 handover was not successful, the MTNM will send message L2_ACK to the FHO module, with
status NOT OK; and will request an automatic handover (as we have lost L2 connectivity), that will be
“slow” (new registration).
If the L2 handover was successful, the MTNM will wait for the answer of the Fast Handover module,
FHO_ACK, which will be either OK or NOT OK. If it is OK, we are done. If it is NOT OK, at this point,
we cannot go back and the MTNM will request an automatic handover, that will be “slow” (new
registration).
We have to consider the case when the FHO module answers directly to message START_FHO with
message START_FHO_ACK, with a negative status. This situation will happen when there are no
available QoS resources on the new Access Router. In this case, we are still connected with the old
Access Router, and we can try another Fast Handover manually or automatically, based on the current
user preferences. For this, we will have to mark the Access Router that we have tried as unavailable for
the next choice.
Then we consider inter-domain handover or the case where the Fast Handover procedure cannot apply
because the layer two connection has been lost, as explained in the section on Network Environment Infos
block.
In this case, a “slow” handover should be used, which for the moment is identical to the registration
scenario.
The attach procedure sub-block will take care of this handover procedure, which will basically consist of
a registration procedure (one of the first thing to do will be to establish a L2 connection to the selected
Access Router, as explained in details before, for the fast handover procedure).
4.1.2.2.8 Paging block
The Paging sub-block of the MTNM will basically perform the requests received from the Paging
module.
Upon reception of the message INFO_REQ from the Paging module, it will retrieve the appropriate
information from the Network Environment Infos sub-block of the MTNM, and send them to the Paging
module via message INFO_REPLY. These will be: the IPv6 address of the current Access Router, and the
MAC address of the different available device drivers (Ethernet, WLAN, TD-CDMA upon availability).
Upon reception of the message SET_STATE_INFO, with parameter state, it will:
• If state is dormant, forward the information to the Network Environment Infos sub-block of MTNM,
so that every time a handover is needed, it will be only a Layer 2 handover (no Fast Handover or
Registration signalling will be involved).
• If state is active, exit the paging dormant mode by contacting the Attach Procedure sub-block, to
trigger a new Registration.
This information will also be transmitted to the Network Environment Infos sub-block of NCP, via
message PAGING_STATE_INFO.
The Paging sub-block of the MTNM can also receive a request from the Network Environment Infos subblock
of NCP, via message SET_PAGING_STATE, with parameter state (active or dormant). This is the
way the user is allowed to control paging state, for demonstration purpose.
This request will be transmitted to the paging module via message NOTIFY_MSG.
D0103v1.doc 26 / 168