Professional Documents
Culture Documents
Multi‐‐Level
Multi Level Header
Header Compression
July 2011
All rights reserved © SIAE MICROELETTRONICA
Multi‐‐Level
Multi Level Header
Header Compression
• Main concepts:
M i
Packets belonging to the same flow share a large part of the header that does
not vary over time (up to 90% of header: IP and MAC addresses, Ethernet
TAGs, MPLS labels, etc.). As a basic idea, Header Compression operates at the
terminations of a radio link, storing all the information that repeats identically
packet after packet and transmitting only the variable fields (sequence
number, timestamp, etc.): thus, in the presence of long communication flows
characterized by a large number of packets (such as, for example, real‐time
communications), we can achieve good throughput gains.
You should simultaneously support several streams in order to maximize the
gain. All the static information of the packets belonging to the same flow are
stored by the compressor/decompressor block and we call them context.
Ethernet HC context ID
18 bytes
(802 1Q)
(802.1Q) 20 24
20‐24
HC dynamic fields
bytes
4 bytes MPLS HC CRCs
10 bytes Payload
20 bytes
20 bytes IPv4
Header
4 bytes Ethernet FCS
8 bytes UDP Compression
34 38 bytes packet
34‐38 bytes
12 bytes RTP
10 bytes Payload
76 bytes packet
(62 bytes of header)
(62 bytes of header)
4 bytes MPLS
HC context ID
20 bytes
20 bytes IPv4 32 bytes HC dynamic fields
HC CRCs
8 bytes UDP
10 bytes Payload
12 bytes GTP‐U
Header
4 bytes Ethernet FCS
40 bytes IPv6 Compression
46 bytes packet
46 bytes
8 bytes UDP
12 bytes RTP
10 bytes Payload
4 bytes
4 bytes Ethernet FCS
136 bytes packet
(122 bytes of header) MuLeHC – July 2011
All rights reserved © SIAE MICROELETTRONICA
Multi‐‐Level
Multi Level Header
Header Compression
Maximum system throughput gain
with Header Optimization and
Multi-Level Header Compression
270,00%
VoIP over PBB [2 levels HC]
260,00%
250 00%
250,00% VoIP with eNodeB (IP Tunneling) [2 levels HC]
180,00%
802.1Q
170,00%
Ethernet (MAC only)
160,00%
Header optimization (no header compression)
150,00%
Maxiimum throughp
140,00%
130,00%
120,00%
110,00%
100,00%
90 00%
90,00%
80,00%
70,00%
60,00%
50,00%
40,00%
30,00%
20,00% ALCplus2e
10,00% Radio fragmentation disabled
0,00% Radio concatenation disabled
Ports in secure mode
-10,00%
64
96
28
60
92
24
56
88
20
52
84
416
48
80
512
44
76
08
40
72
04
36
68
00
32
64
96
28
60
92
24
56
88
20
52
84
1216
48
80
1312
44
76
08
40
72
04
6
9
12
16
19
22
25
28
32
35
38
44
48
54
57
60
64
67
70
73
76
80
83
86
89
92
96
99
102
105
108
112
115
118
124
128
134
137
140
144
147
150
Packet size [bytes]
650 802.1Q
Ethernet (MAC only)
600
Header optimization (no header compression)
550
500
450
400
350
300
250
200
150
100 ALCplus2e
Radio fragmentation disabled
50 Radio concatenation disabled
Ports in secure mode
0
64
96
28
60
92
24
56
88
20
52
84
416
48
80
512
44
76
08
40
72
04
36
68
00
32
64
96
28
60
92
24
56
88
20
52
84
1216
48
80
1312
44
76
08
40
72
04
56 MHz – 256 QAM
6
9
12
16
19
22
25
28
32
35
38
44
48
54
57
60
64
67
70
73
76
80
83
86
89
92
96
99
102
105
108
112
115
118
124
128
134
137
140
144
147
150
Packet size [bytes]
650 802.1Q
Ethernet (MAC only)
600
Header optimization (no header compression)
550
500
450
400
350
300
250
200
150
100 ALCplus2e
Radio fragmentation disabled
50 Radio concatenation disabled
Ports in secure mode
0
64
96
28
60
92
24
56
88
20
52
84
416
48
80
512
44
76
08
40
72
04
36
68
00
32
64
96
28
60
92
24
56
88
20
52
84
1216
48
80
1312
44
76
08
40
72
04
56 MHz – 256 QAM
6
9
12
16
19
22
25
28
32
35
38
44
48
54
57
60
64
67
70
73
76
80
83
86
89
92
96
99
102
105
108
112
115
118
124
128
134
137
140
144
147
150
Packet size [bytes]
190,00% 802.1ad
put gain [%]
180,00% 802.1Q
170,00% Ethernet (MAC only)
160,00% Header optimization (no header compression)
150,00%
Maxiimum throughp
140,00%
130,00%
120,00%
110,00%
100,00%
90 00%
90,00%
80,00%
70,00%
60,00%
50,00%
40,00%
30,00%
20,00% ALCplus2e
10,00% Radio fragmentation disabled
0,00% Radio concatenation enabled
Ports in secure mode
-10,00%
64
96
28
60
92
24
56
88
20
52
84
416
48
80
512
44
76
08
40
72
04
36
68
00
32
64
96
28
60
92
24
56
88
20
52
84
1216
48
80
1312
44
76
08
40
72
04
6
9
12
16
19
22
25
28
32
35
38
44
48
54
57
60
64
67
70
73
76
80
83
86
89
92
96
99
102
105
108
112
115
118
124
128
134
137
140
144
147
150
Packet size [bytes]
950
900
850
800
Maximum L1 equivalent tthroughput [Mbps]
750
700
650
600
550
500
450
VoIP over PBB [2 levels HC]
400
VoIP with eNodeB (IP Tunneling) [2 levels HC]
350
VoIP over IPv6+MPLS [2 levels HC]
300 802.1ad + MPLS + IPv4 + UDP + RTP
100 802.1Q
ALCplus2e
Ethernet (MAC only) Radio fragmentation disabled
50 Radio concatenation enabled
Header optimization (no header compression)
Ports in secure mode
0
64
96
28
60
92
24
56
88
20
52
84
416
48
80
512
44
76
08
40
72
04
36
68
00
32
64
96
28
60
92
24
56
88
20
52
84
1216
48
80
1312
44
76
08
40
72
04
56 MHz – 256 QAM
6
9
12
16
19
22
25
28
32
35
38
44
48
54
57
60
64
67
70
73
76
80
83
86
89
92
96
99
102
105
108
112
115
118
124
128
134
137
140
144
147
150
Packet size [bytes]
950
900
850
800
Maximum L2 equivalent tthroughput [Mbps]
750
700
650
600
550
500
450
VoIP over PBB [2 levels HC]
400
VoIP with eNodeB (IP Tunneling) [2 levels HC]
350
VoIP over IPv6+MPLS [2 levels HC]
300 802.1ad + MPLS + IPv4 + UDP + RTP
100 802.1Q
ALCplus2e
Ethernet (MAC only) Radio fragmentation disabled
50 Radio concatenation enabled
Header optimization (no header compression)
Ports in secure mode
0
64
96
28
60
92
24
56
88
20
52
84
416
48
80
512
44
76
08
40
72
04
36
68
00
32
64
96
28
60
92
24
56
88
20
52
84
1216
48
80
1312
44
76
08
40
72
04
56 MHz – 256 QAM
6
9
12
16
19
22
25
28
32
35
38
44
48
54
57
60
64
67
70
73
76
80
83
86
89
92
96
99
102
105
108
112
115
118
124
128
134
137
140
144
147
150
Packet size [bytes]
The reasons for a Multi‐Level HC (1)
• Traffic coverage of a single‐level context
T ffi f i l l l
The reasons for a Multi‐Level HC (2)
• Memory requirements for a single‐level header compression
M i f i l l lh d i
HIGH layer header compression
“No Context” header compression
The reasons for a Multi‐Level HC (3)
• Multi‐Level Header Compression approach
We compress low layer and high layer sessions simultaneously in the same
W l l d hi h l i i lt l i th
flow and using different contexts, independent from each other. We call this
compression scheme Multi‐Level Header Compression (MuLeHC).
This can combine the benefits of low layer and high layer header compression:
This can combine the benefits of low layer and high layer header compression:
Compressing a great portion of the traffic with low layer header
compression
Reaching the high compression gain of high layer header compression