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

This entity communicates with the QoS Manager on the Access Router and the QoS Broker.<br />

The radio resources will be negotiated dynamically each time a radio bearer is requested by a Mobile<br />

Terminal (in the case of a first incoming IP packet originating fro m the Access Router, the QoS broker<br />

will send the necessary information without solicitation from the RG).<br />

When the RCF on the Radio Gateway receives a request from the RCF on the Mobile Terminal to open a<br />

radio bearer, it will send the message IWF_RADIO_BEARER_REQ to the QoS Attendant of the IWF,<br />

with the characteristics associated to the requested bearer (local connection reference, DSCP code, IP<br />

source address of original packet on MT, IP destination address of original packet on MT).<br />

The QoS Attendant will send a “dummy packet” (an echo request will do the trick) with the<br />

characteristics of the original packet on the MT: IP source address, IP destination address, DSCP code.<br />

This packet will be intercepted by the QoS Manager on the Access Router and will trigger the “QoS<br />

authorisation process” involving the QoS Broker.<br />

The QoS Attendant on the RG then expects an answer from the QoS Broker, message<br />

RADIO_ACCESS_ALLOCATION, with the following parameters: DSCP code, Home Address of MT (for<br />

identification purpose), Radio QoS Class, status.<br />

In the case of an incoming packet from the Access Router (and not from the MT), the QoS Broker will<br />

also have to send the message RADIO_ACCESS_ALLOCATION, with the parameters corresponding to<br />

the incoming packet.<br />

In the case of a fast handover with the RG as destination, the QoS Broker will have to send the message<br />

RADIO_ACCESS_ALLOCATION, with a list of entries with once again the same parameters. This will<br />

enable the Radio Gateway to open the radio bearers corresponding to the DSCP codes used by the Mobile<br />

Terminal, immediately after the radio connection between MT and RG has been established.<br />

A specific value will be given to the status parameters in the message RADIO_ACCESS_ALLOCATION,<br />

to recognize this case of fast handover.<br />

Hence, the message RADIO_ACCESS_ALLOCATION should be in fact a list of the following parameters:<br />

DSCP code, Home Address of MT (for identification purpose), Radio QoS Class, status (ok, not ok,<br />

specific value in fast handover case).<br />

It can be a UDP packet exchanged between two known ports on the Radio Gateway and the QoS Broker.<br />

After reception of the message RADIO_ACCESS_ALLOCATION, the QoS Attendant on the RG will send<br />

the message IWF_RADIO_BEARER_CONF to the RCF, with the following parameters: local connection<br />

reference corresponding to the MT Home Address, list of [DSCP code, Radio QoS class, status].<br />

4.3.1.11 TD-CDMA to IP relay block<br />

The TD-CDMA to IP relay block will receive the IP packets from the TD-CDMA driver via a raw socket<br />

interface, and transmit them to the Ethernet Driver via a raw socket interface. We will use the message<br />

IWF_IP_PACKET for the interface between the RCM and the IWF.<br />

D0103v1.doc 79 / 168

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

Saved successfully!

Ooh no, something went wrong!