Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
4.2.3.1.1 Interface mechanisms
Control primitive exchange between Fast-HO module and QoS attendant function on Access Routers
requires deployment of an appropriate interface for bi-directional user-space / kernel communications.
We use for that a character device. The following sections describe the interface.
4.2.3.1.2 Interface contents
Source Dest Primitive Parameters
Fast-HO
in oAR
QoSattend
in oAR
START_QOS_FHO
oCoA, nAR address, nCoA.
Fast-HO
in nAR
QoSattend
in nAR
START_QOSB_LISTEN
none
QoSattend
in nAR
Fast-HO in
nAR
QOS_FHO_ACK
Result info: QOS_AVAILABLE
or
QOS_NOT_AVAILABLE
Table 13: Interface Contents
4.2.3.1.3 Format of the messages
/* Message definition(s) */
struct qos_fho_msg_t
{
int type;
union
{
start_qos_fho_msg_t start_qos_fho;
start_qosb_listen_msg_t start_qosb_listen;
qos_fho_ack_msg_t qos_fho_ack;
} msg;
};
typedef struct qos_fho_msg_t qos_fho_msg_t;
/* FHO module -> QOS-attendant on the oAR: handover initiate info message to QoS */
struct start_qos_fho_msg_t
{
struct in6_addr old_coa;
struct in6_addr new_coa;
struct in6_addr new_ar;
};
typedef struct start_qos_fho_msg_t start_qos_fho_msg_t;
/* FHO module --> QoS attendant on the oAR: trigger the QoS attendant to listen for QoS message */
struct start_qosb_listen_msg_t
{
};
typedef struct start_qosb_listen_msg_t start_qosb_listen_msg_t;
/* QoS attendant --> FHO module on the nAR: allow or deny handover via acknowledgement */
struct qos_fho_ack_msg_t
{
int qos_ack;
};
typedef struct qos_fho_ack_msg_t qos_fho_ack_msg_t;
D0103v1.doc 65 / 168