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

NCP<br />

Set<br />

Network<br />

Preferences<br />

Set<br />

Handover<br />

Preference<br />

Manual<br />

Handover<br />

Network<br />

Environment<br />

Infos<br />

Explicit<br />

Connectivity<br />

Request<br />

MTNM<br />

Set<br />

Network<br />

Preferences<br />

Set<br />

Handover<br />

Preference<br />

Network<br />

Environment<br />

Infos<br />

Network device drivers<br />

TDCDMA WLAN Ethernet<br />

Figure 6: Interactions between MTNM / NCP<br />

The MTNM will update its Network preferences each time it receives a request from the NCP, via the<br />

message SET_NETWORK_PREFERENCES. These preferences will be expressed as for the NCP: first<br />

choice x, second choice y, third choice z; with x,y,z in Ethernet, TD-CDMA, WLAN.<br />

4.1.2.2.2 Set Handover Preference block<br />

The MTNM will update the Handover preference each time it receives a request from the NCP, via the<br />

message SET_HANDOVER_PREFERENCE. This preference will be expressed as for the NCP:<br />

automatic, manual or both. This information will be used to authorize automatic handover, if the<br />

preference is automatic or both.<br />

4.1.2.2.3 Network Environment Info block<br />

This block will analyse information received from the Network device drivers, store them for use by the<br />

automatic handover decision algorithm, attach procedure; and transmit them to the NCP (as already<br />

explained in the description of the corresponding block in the NCP).<br />

The messages received from the device drivers will be ETHERNET_INFO, TD-CDMA_INFO and<br />

WLAN_INFO. The message sent to the NCP will be NETWORK_ENVIRONMENT_INFOS.<br />

First of all, we will not consider every router advertisement or signal level indications received by the<br />

different device drivers. Instead, we will limit ourselves to a “reasonable” time interval between two<br />

consecutive messages from the device drivers to the Network Environment Info block. This will avoid too<br />

frequent handover (backward and forward) if a user moves around the border of two radio coverage areas,<br />

in the case of WLAN or TD-CDMA.<br />

For the three possible network technologies, if we don’t receive an info message at the time we expect<br />

one, we will consider that the technology is not available.<br />

For Ethernet, the message INTERNET_INFO will contain the following information: absent or present,<br />

IPv6 address of the corresponding Access Router, which will be stored locally. The information absent or<br />

present will be transmitted to the NCP, if it changes, via message NETWORK_ENVIRONMENT_INFOS.<br />

For WLAN, the message WLAN_INFO will contain the following information: a list of [signal to noise<br />

ratio, IPv6 address of the corresponding Access Router, IPv6 subnet prefix of Access Router].<br />

Locally, we will keep up to two entries: the current WLAN “access point” if this technology is in use, and<br />

the best candidate for handover (which can be different from the currently used “access point”).<br />

First we will erase the current best candidate for handover, and the following algorithm will be applied to<br />

each element of the list:<br />

• If WLAN is the currently used Network technology and we receive from the WLAN device<br />

driver an update with the same identification and a different signal to noise ratio, we update the<br />

current signal to noise ratio in the MTNM and send an update message<br />

NETWORK_ENVIRONMENT_INFOS to the NCP, with the new signal level.<br />

D0103v1.doc 20 / 168

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

Saved successfully!

Ooh no, something went wrong!