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 IWF TD-CDMA to IP relay IP stack RCM Packet Reception Ethernet RCM driver Control Packet Data Packet RCF Control Channel Mngt Data Channel Mngt Send / Receive Open / Close Send / Receive Data Data Channels Data AS Figure 61: TD-CDMA to IP relay block 4.3.1.12 IP stack This part does not need to be further detailed. D0103v1.doc 80 / 168
D0103v1.doc Version 1 6.7.2003 4.3.2 Radio Channel Manager RCM Radio Connection Manager Broad casting Paging Open / Close Conn Packet Transmission Control Data Packet Packet Packet Reception Control Data Packet Packet Figure 62: Radio Channel Manager The Radio Channel Manager is the generic part of the Radio driver. It provides a generic interface to the IWF and to the IP stack. It provides also a generic interface to the lower layer of the Radio driver: the Radio Convergence Function. 4.3.2.1 Radio Connection Manager block • Broadcasting sub-block It will transmit the broadcast requests from the IWF, message IWF_BROADCAST_REQ, directly to the Broadcasting sub-block of the RCF. • Paging sub-block It will transmit the paging requests from the IWF, message IWF_PAGING_REQ, directly to the Paging sub-block of the RCF. • Open / Close connection sub-block The Open / Close Connection sub-block manages the Radio Connections with Mobile Terminal. The connections are always opened on the initiative of the Mobile Terminal. When the Open / Close Connection sub-block of the RCF opens a connection, it will transmit the message OPEN_TD-CDMA_CONN_IND, to the Open / Close Connection sub-block of the RCM, which will transmit it to the Info Management block of the IWF. There will be two parameters: local connection reference and IMEI of MT. When a connection has been opened, the RCF of the MT sends a NAS signalling message to the RCF of the RG (NAS_CONNECTION_INFO), with the parameters: Home Address and CoA of MT. This information is passed to the Open / Close Connection sub-block of the RCM, with the associated local connection reference, via message OPEN_TD-CDMA_CONN_INFO. Then this message OPEN_TD-CDMA_CONN_INFO is forwarded to the Info Management block of the IWF, with the parameters: local connection reference, Home Address and CoA of MT. The association “local connection reference / Mobile Terminal Care Of Address” is important for IP packets received from the Access Router, to be transmitted to a Mobile Terminal: a match is searched between the destination address of the IP packet and the list of Care Of Address, and the associated connection reference is used to send the packet on the proper radio bearer to the Mobile Terminal. The connections are always closed on the initiative of the Mobile Terminal. When the Open / Close Connection sub-block of the RCF closes a connection, it will transmit the message CLOSE_TD-CDMA_CONN_IND, to the Open / Close Connection sub-block of the RCM, which will forward it to the Info Management block of the IWF. There will be one parameter: local connection reference. When the Open / Close Connection sub-block of the RCF detects a connection loss, it will transmit the message LOST_TD-CDMA_CONN_IND, to the Open / Close Connection sub-block of the RCM, which will forward it to the Info Management block of the IWF. There will be one parameter: local connection reference. 4.3.2.2 Packet Transmission block The connection must have been opened by the Radio Connection Manager sub-block, before any IP packet can be transmitted (if it’s not the case, they will be dropped: this can only happen with packet arriving from the Access Router, and there is nothing we can do if the MT has not opened the connection yet). An open connection means that the RCF has also established all the associated radio control channels, but that no radio bearer has been pre-established. In case of connection loss, we do nothing on the Radio Gateway side (the IP packets from the Access Router to the Mobile Terminal will be lost). The connection loss will be detected on the Mobile Terminal side too, and a new connection will be established on its initiative, if appropriate. D0103v1.doc 81 / 168
- 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 •
- Page 69 and 70: D0103v1.doc Version 1 6.7.2003 The
- Page 71 and 72: D0103v1.doc Version 1 6.7.2003 is t
- Page 73 and 74: D0103v1.doc Version 1 6.7.2003 4.3
- Page 75 and 76: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 77 and 78: D0103v1.doc Version 1 6.7.2003 This
- Page 79: D0103v1.doc Version 1 6.7.2003 This
- Page 83 and 84: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 85 and 86: D0103v1.doc Version 1 6.7.2003 The
- Page 87 and 88: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 89 and 90: D0103v1.doc Version 1 6.7.2003 be u
- Page 91 and 92: D0103v1.doc Version 1 6.7.2003 o Ma
- Page 93 and 94: D0103v1.doc Version 1 6.7.2003 Gene
- Page 95 and 96: D0103v1.doc Version 1 6.7.2003 Upli
- Page 97 and 98: D0103v1.doc Version 1 6.7.2003 Now
- Page 99 and 100: D0103v1.doc Version 1 6.7.2003 3. D
- Page 101 and 102: D0103v1.doc Version 1 6.7.2003 User
- Page 103 and 104: D0103v1.doc Version 1 6.7.2003 Inte
- Page 105 and 106: D0103v1.doc Version 1 6.7.2003 User
- Page 107 and 108: D0103v1.doc Version 1 6.7.2003 Serv
- Page 109 and 110: D0103v1.doc Version 1 6.7.2003 S1 E
- Page 111 and 112: D0103v1.doc Version 1 6.7.2003 The
- Page 113 and 114: D0103v1.doc Version 1 6.7.2003 Old
- Page 115 and 116: D0103v1.doc Version 1 6.7.2003 This
- Page 117 and 118: D0103v1.doc Version 1 6.7.2003 Leng
- Page 119 and 120: D0103v1.doc Version 1 6.7.2003 4.5.
- Page 121 and 122: D0103v1.doc Version 1 6.7.2003 MN M
- Page 123 and 124: D0103v1.doc Version 1 6.7.2003 4.5.
- Page 125 and 126: D0103v1.doc Version 1 6.7.2003 Afte
- Page 127 and 128: D0103v1.doc Version 1 6.7.2003 Pack
- Page 129 and 130: D0103v1.doc Version 1 6.7.2003 4.5.
D0103v1.doc Version 1 6.7.2003<br />
IWF<br />
TD-CDMA<br />
to IP relay<br />
IP stack<br />
RCM<br />
Packet Reception<br />
Ethernet RCM driver<br />
Control<br />
Packet<br />
Data<br />
Packet<br />
RCF<br />
Control Channel Mngt<br />
Data Channel Mngt<br />
Send /<br />
Receive<br />
Open /<br />
Close<br />
Send /<br />
Receive<br />
Data<br />
Data<br />
Channels<br />
Data<br />
AS<br />
Figure 61: TD-CDMA to IP relay block<br />
4.3.1.12 IP stack<br />
This part does not need to be further detailed.<br />
D0103v1.doc 80 / 168