Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
0 GetMa 31 0 Map 31 0 TLV 31
Message Type p = 1 Message Type = 2
Type
Length of CoA
CoA
TLV
TLV
Length
Value
4.2.2.7 DSCP Marking Software
4.2.2.7.1 Motivations
Figure 47. Message format for CoA to NAI mapping
Initially, the marking process was expected to work only in the Mobile Terminal. However, a few
network entities (Home Agent for ex.) may generate signalling packets that must be marked. In fact, with
Ethernet and WLAN technologies, these packets do not cause any problem, even if they are marked with
a default DSCP set to ‘0’. With TD-CDMA, these packets may be dropped. To cross the interface, all the
packets are associated with a specific radio bearer, according to their DSCP. In Moby Dick, a DSCP set to
‘0’ is not recognized (see Table 10), and signalling and data packets use separate radio bearers associated
with different DSCPs. So, the signalling packets must be marked just before sending them on a TD-
CDMA interface, i.e. in the Access Router.
Service Relative
Typical Usage
Name Class Priority
Service parameters
Description
DSCP
SIG AF41 2 Unspecified Signalling (network usage) 0x22
S1 EF 1 Peak BW: 32 kbit/s Real time services 0x2e
S2 AF21 3 CIR: 256 kbit/s
Priority (urgent)
data transfer
0x12
Three drop precedences (kbps): Olympic service
S3 AF1* 4
AF11 – 64
AF12 – 128
(better then
BE:streaming, ftp,
0x0a
0x0c
AF13 – 256
etc) 0x0e
S4 BE 0 Peak bit rate: 32 kbit/s Best Effort (BE) 0x00
S5 BE 0 Peak bit rate: 64 kbit/s Best effort 0x02
S6 BE 0 Peak bit rate: 256 kbit/s Best effort 0x04
Table 10: Classes of Service and associated DSCP codes
D0103v1.doc 60 / 168