Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan Moby Dick Consolidated System Integration Plan
D0103v1.doc Version 1 6.7.2003 NCP Set Network Preferences Set Handover Preference Manual Handover Network Environment Infos Explicit Connectivity Request MTNM Set Network Preferences Set Handover Preference Network Environment Infos Manual Handover Attach / Detach Procedure Figure 4: Networking Control Panel 4.1.2.1.3 Network Environment Info block This block will give information to the user, about the network availability. The Ethernet will be either absent or present. The WLAN will have a certain signal to noise ratio and the TD-CDMA will have a certain signal level. These information will be transmitted by the Network Environment Info block of the MTNM, via the message NETWORK_ENVIRONMENT_INFOS. If more than one WLAN or TD-CDMA Access Point is available, only information about the one currently in use by the IP stack, or if another technology is in use by the IP stack, the one with the higher signal level; will be transmitted by the MTNM to the NCP. At the user level, we only want a choice between different network technologies, not a choice among the same network technology. We consider a choice between the same network technology for WLAN and TD-CDMA, to enable QoS driven handover for example, or to consider inter domain handover within the same technology. The information about network availability will be used during a manual handover, as explained in the associated block description. This block will also indicate which Network technology is currently being used. This information is also transmitted by the Network Environment Info block of the MTNM, via the message NETWORK_TECHNOLOGY_IN_USE (it will also contain the subnet prefix of the associated Access Router, to which we are currently attached). It will be updated when a change occurs, triggered by the Attach Procedure block, Manual Handover block, Automatic Handover block of the MTNM. This block will also enable the user to control the paging state. The message SET_PAGING_STATE sent to the MTNM will require entering the following paging state: either dormant or active. The MTNM will forward it to the paging module. This is the way the user is allowed to control paging state, for demonstration purpose. The message PAGING_STATE_INFO received from MTNM (originating from the Paging module) will indicate any change in the paging state, dormant or active. 4.1.2.1.4 Manual Handover block If the Handover preference is set to manual or both, the user can execute a manual handover, selecting among the 3 network technologies (Ethernet, WLAN, TD-CDMA), one that is available (but not the D0103v1.doc 18 / 168
D0103v1.doc Version 1 6.7.2003 currently in use one). The information about the availability will be retrieved from the Network Environment Infos block. The Ethernet will always be considered as available, if present. The WLAN will be considered as available if its signal to noise ratio is higher than a predefined threshold (WLAN_threshold). The TD-CDMA will be considered as available if its signal level is higher than a predefined threshold (TD-CDMA_threshold). The user will have this information: current signal level. In the first implementation stage, the user won’t be able to execute a manual handover within the same technology. If WLAN is selected, and if a better "Access Point" than the current one is available (better signal level), the MTNM may generate (this will be detailed in the description of the MTNM) a fast handover between the two "Access Points", that is not seen by the NCP (the NCP only sees the signal level of the currently used "Access Point", which is always the best choice for this technology). The same applies to TD-CDMA. The order to execute a manual handover will be transmitted to the Manual Handover block of the MTNM, via the message MANUAL_HANDOVER_REQ. An acknowledgement is expected from the MTNM, via message MANUAL_HANDOVER_ACK, with parameter status. As already stated, manual handover within the same technology for WLAN and TD-CDMA will be considered only as a research topic, and will not be implemented. In the case of automatic handover, a spontaneous acknowledgement will be sent by the MTNM, via message AUTOMATIC_HANDOVER_ACK, with parameter status. This will be used to make the user aware that an automatic handover has taken place. 4.1.2.1.5 Explicit Connectivity Request block The effective connection to the network (AAAC procedures) will be explicitly triggered by the message START_NETWORK_CONNECTION , sent by the Explicit Connectivity Request block of the NCP to the Attach / Detach procedure block of the MTNM. The parameters will be the user login and password. An acknowledgement is expected from the MTNM , via message START_NETWORK_CONNECTION_ACK, with parameter status. The message TERMINATE_NETWORK_CONNECTION will be used to end the current network connection. It will also be sent by the Explicit Connectivity Request block to the Attach / Detach procedure block (the handling of this message will imply no AAAC action). No parameters will be needed. An acknowledgement is expected from the MTNM, via message TERMINATE_NETWORK_CONNECTION_ACK, with parameter status. 4.1.2.2 Mobile Terminal Networking Manager The MTNM has interactions with the NCP, the different device drivers, the fast handover module, the registration module and the paging module. It is split into the following sub-blocks. MTNM Set Network Preferences Set Handover Preference Network Environment Infos Attach Procedure Manual Handover Automatic Handover Paging Figure 5: Mobile Terminal Networking Manager 4.1.2.2.1 Set Network Preferences block The following schema can be used to illustrate the description of the 3 first sub-blocks. D0103v1.doc 19 / 168
- Page 1 and 2: IST-2000-25394 Moby Dick D0103 Moby
- Page 3 and 4: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 5 and 6: D0103v1.doc Version 1 6.7.2003 5.1.
- Page 7 and 8: D0103v1.doc Version 1 6.7.2003 Abbr
- Page 9 and 10: D0103v1.doc Version 1 6.7.2003 1 In
- Page 11 and 12: D0103v1.doc Version 1 6.7.2003 3 Mo
- Page 13 and 14: D0103v1.doc Version 1 6.7.2003 Doma
- Page 15 and 16: D0103v1.doc Version 1 6.7.2003 NCP
- Page 17: D0103v1.doc Version 1 6.7.2003 It w
- Page 21 and 22: D0103v1.doc Version 1 6.7.2003 •
- Page 23 and 24: D0103v1.doc Version 1 6.7.2003 No A
- Page 25 and 26: D0103v1.doc Version 1 6.7.2003 o Fo
- Page 27 and 28: D0103v1.doc Version 1 6.7.2003 NCP
- Page 29 and 30: D0103v1.doc Version 1 6.7.2003 4.1.
- Page 31 and 32: D0103v1.doc Version 1 6.7.2003 4.1.
- Page 33 and 34: D0103v1.doc Version 1 6.7.2003 asso
- Page 35 and 36: D0103v1.doc Version 1 6.7.2003 Mobi
- Page 37 and 38: D0103v1.doc Version 1 6.7.2003 WP4
- Page 39 and 40: D0103v1.doc Version 1 6.7.2003 Para
- Page 41 and 42: D0103v1.doc Version 1 6.7.2003 Ackn
- Page 43 and 44: D0103v1.doc Version 1 6.7.2003 inst
- Page 45 and 46: D0103v1.doc Version 1 6.7.2003 MT P
- Page 47 and 48: D0103v1.doc Version 1 6.7.2003 The
- Page 49 and 50: D0103v1.doc Version 1 6.7.2003 RtSo
- Page 51 and 52: D0103v1.doc Version 1 6.7.2003 auth
- Page 53 and 54: D0103v1.doc Version 1 6.7.2003 In a
- Page 55 and 56: D0103v1.doc Version 1 6.7.2003 AR s
- Page 57 and 58: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 59 and 60: D0103v1.doc Version 1 6.7.2003 Even
- Page 61 and 62: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 63 and 64: D0103v1.doc Version 1 6.7.2003 Filt
- Page 65 and 66: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 67 and 68: D0103v1.doc Version 1 6.7.2003 •
D0103v1.doc Version 1 6.7.2003<br />
currently in use one). The information about the availability will be retrieved from the Network<br />
Environment Infos block.<br />
The Ethernet will always be considered as available, if present.<br />
The WLAN will be considered as available if its signal to noise ratio is higher than a predefined threshold<br />
(WLAN_threshold).<br />
The TD-CDMA will be considered as available if its signal level is higher than a predefined threshold<br />
(TD-CDMA_threshold).<br />
The user will have this information: current signal level. In the first implementation stage, the user won’t<br />
be able to execute a manual handover within the same technology. If WLAN is selected, and if a better<br />
"Access Point" than the current one is available (better signal level), the MTNM may generate (this will<br />
be detailed in the description of the MTNM) a fast handover between the two "Access Points", that is not<br />
seen by the NCP (the NCP only sees the signal level of the currently used "Access Point", which is<br />
always the best choice for this technology). The same applies to TD-CDMA.<br />
The order to execute a manual handover will be transmitted to the Manual Handover block of the MTNM,<br />
via the message MANUAL_HANDOVER_REQ.<br />
An acknowledgement is expected from the MTNM, via message MANUAL_HANDOVER_ACK, with<br />
parameter status.<br />
As already stated, manual handover within the same technology for WLAN and TD-CDMA will be<br />
considered only as a research topic, and will not be implemented.<br />
In the case of automatic handover, a spontaneous acknowledgement will be sent by the MTNM, via<br />
message AUTOMATIC_HANDOVER_ACK, with parameter status. This will be used to make the user<br />
aware that an automatic handover has taken place.<br />
4.1.2.1.5 Explicit Connectivity Request block<br />
The effective connection to the network (AAAC procedures) will be explicitly triggered by the message<br />
START_NETWORK_CONNECTION , sent by the Explicit Connectivity Request block of the NCP to the<br />
Attach / Detach procedure block of the MTNM. The parameters will be the user login and password.<br />
An acknowledgement is expected from the MTNM , via message<br />
START_NETWORK_CONNECTION_ACK, with parameter status.<br />
The message TERMINATE_NETWORK_CONNECTION will be used to end the current network<br />
connection. It will also be sent by the Explicit Connectivity Request block to the Attach / Detach<br />
procedure block (the handling of this message will imply no AAAC action). No parameters will be<br />
needed.<br />
An acknowledgement is expected from the MTNM, via message<br />
TERMINATE_NETWORK_CONNECTION_ACK, with parameter status.<br />
4.1.2.2 Mobile Terminal Networking Manager<br />
The MTNM has interactions with the NCP, the different device drivers, the fast handover module, the<br />
registration module and the paging module. It is split into the following sub-blocks.<br />
MTNM<br />
Set<br />
Network<br />
Preferences<br />
Set<br />
Handover<br />
Preference<br />
Network<br />
Environment<br />
Infos<br />
Attach Procedure<br />
Manual<br />
Handover<br />
Automatic<br />
Handover<br />
Paging<br />
Figure 5: Mobile Terminal Networking Manager<br />
4.1.2.2.1 Set Network Preferences block<br />
The following schema can be used to illustrate the description of the 3 first sub-blocks.<br />
D0103v1.doc 19 / 168