8.127 Header Compression Configuration
29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 18Stage 3TS
The Header Compression Configuration includes the information necessary for the ROHC channel setup.
The Header Compression Configuration shall be encoded as specified in Figure 8.127-1.
|
Bits |
||||||||||
|
Octets |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
1 |
Type = 196 (decimal) |
|||||||||
|
2 to 3 |
Length = n |
|||||||||
|
4 |
Spare |
Instance |
||||||||
|
5 to 6 |
ROHC Profiles |
|||||||||
|
7 to 8 |
MAX_CID |
|||||||||
|
9 to (n+4) |
These octet(s) is/are present only if explicitly specified |
|||||||||
Figure 8.127-1: Header Compression Configuration
Table 8.127-1: Header Compression Configuration
|
ROHC Profiles (octets 5 and 6) |
||||||||||||||||
|
Bits The ROHC Profiles shall indicate which of the ROHC profiles specified in 3GPP TS 36.323 [76] are allowed to be used (i.e. have been negotiated) with the UE. When a particular bit is set to 1, this indicates that the corresponding profile is allowed to be used. The No Compression profile 0x000 shall also be considered as allowed if at least one bit is set to 1. When all the bits are set to 0, this indicates that only the No Compression profile 0x000 is allowed to be used. Octet 5 |
||||||||||||||||
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Profile Identifier |
Usage |
|||||||
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0x0002 |
UDP/IP |
|||||||
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0x0003 |
ESP/IP |
|||||||
|
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0x0004 |
IP |
|||||||
|
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0x0006 |
TCP/IP |
|||||||
|
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0x0102 |
UDP/IP |
|||||||
|
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0x0103 |
ESP/IP |
|||||||
|
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0x0104 |
IP |
|||||||
|
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Spare |
||||||||
|
Octet 6 |
||||||||||||||||
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Profile Identifier |
Usage |
|||||||
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
Spare |
||||||||
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
Spare |
||||||||
|
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
Spare |
||||||||
|
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
Spare |
||||||||
|
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
Spare |
||||||||
|
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
Spare |
||||||||
|
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
Spare |
||||||||
|
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Spare |
||||||||
|
MAX_CID (octet 7 to 8) |
||||||||||||||||
|
This is the maximum CID value specified in 3GPP TS 36.323 [76] allowed to be used (i.e. which has been negotiated) with the UE. This shall be encoded as a 2 byte integer with a value in the range from 1 to 16383. |
||||||||||||||||