Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
It will be implemented as a kernel module (RCM and RCF will be grouped in a same kernel module,
namely a driver).
The behaviour of the different sub-blocks of the RCM will be detailed in the next section.
Radio Convergence Function
This module will act as a specific TD-CDMA driver, giving low level interfaces to open / close
connections, manage data channels, send and receive IP packets, get some feedback on the TD-CDMA
conditions, handle the broadcasting and paging channels.
It will be implemented as a kernel module (RCM and RCF will be grouped in a same kernel module,
namely a driver).
The behaviour of the different sub-blocks of the RCF will be detailed in the next section.
Monitoring Extensions to Ethernet / WLAN driver
For Ethernet, the purpose is to detect the presence of the Ethernet card, and to receive Router
Advertisements.
For WLAN, the purpose is to detect different Access Point, to retrieve the associated signal to noise
ratios, and to receive Router Advertisements.
These functions should be implemented at a L2 level. The behaviour of these components will be detailed
in the next section.
4.1.1.8 Access Stratum
The Access Stratum provides services related to the transmission of data over the radio interface and the
management of the radio interface.
It includes the following Radio Interface protocols: the Physical layer, the data link layer, divided into 2
sub-layers: Medium Access Control (MAC) and Radio Link Control (RLC). In the user-plane, an
additional service dependant protocol exists: the Packet Data Convergence Protocol (PDCP). The lowest
sub-layer of the network layer consists of one protocol, called Radio Resource Control (RRC), which
belongs to the control plane.
The functions and services provided by the Access Stratum will be detailed in next section.
4.1.2 Detailed description of the components
This section gives a detailed description of the sub-blocks of each component, and their interactions with
other components .
4.1.2.1 Networking Control Panel
The NCP has interactions (only) with the user and the MTNM, as described in the figure below. It is split
into the following sub-blocks.
• Set Network Preference Sub-block
• Set Handover Preference Sub-block
• Manual Handover Sub-block
• Network Environment Info Sub-block
• Explicit Connectivity Request Sub-block
4.1.2.1.1 Set Network Preferences block
The user will set his/her preferences as follows: first choice x, second choice y, third choice z; with each
x,y,z as one of the possible choices: Ethernet, TD-CDMA, WLAN. Each time the preferences change,
they will be transmitted to the Set Network Preferences block of the MTNM (to be used for automatic
handover decision), via the message SET_NETWORK_PREFERENCES. These preferences will be stored
in a configuration file (one per user).
Each time a user requests a connection via the Explicit Connectivity Request sub-block, the data from this
configuration file will be loaded and used as the default preferences. In particular, they will be used to
establish the initial connection.
Each time a user requests a disconnection via the Explicit Connectivity Request sub-block, the data will
be saved in the configuration file.
4.1.2.1.2 Set Handover Preference block
The user will set its preference as follows: automatic handover or manual handover or both. Each time the
preference change, it will be transmitted to the Set Handover preference block of the MTNM, via the
message SET_HANDOVER_PREFERENCE.
This preference will be stored in a configuration file (one per user, same as previous one).
Each time a user requests a disconnection via the Explicit Connectivity Request sub-block, the data from
this configuration file will be loaded and used as the default preference.
Each time a user requests a de-connection via the Explicit Connectivity Request sub-block, the data will
be saved in the configuration file.
D0103v1.doc 17 / 168