TFT 23060 also details in TS24.008节10.5.6.12
TRACE 36422
TFT operation code (octet 3)
Bits
8 7 6
0 0 0 Spare
0 0 1 Create new TFT
0 1 0 Delete existing TFT
0 1 1 Add packet filters to existing TFT
1 0 0 Replace packet filters in existing TFT
1 0 1 Delete packet filters from existing TFT
1 1 0 No TFT operation
1 1 1 Reserved
The TFT operation code "No TFT operation" shall be used if a parameters list is included but no packet filter list is included in the traffic flow template information element.
E bit (bit 5 of octet 3)
The E bit indicates if a parameters list is included in the TFT IE and it is encoded as follows:
0 parameters list is not included
1 parameters list is included
Number of packet filters (octet 3)
The number of packet filters contains the binary coding for the number of packet filters in the packet filter list. The number of packet filters field is encoded in bits 4 through 1 of octet 3 where bit 4 is the most significant and bit 1 is the least significant bit. For the "delete existing TFT" operation and for the "no TFT operation", the number of packet filters shall be coded as 0. For all other operations, the number of packet filters shall be greater than 0 and less than or equal to 15.
Packet filter list (octets 4 to z)
The packet filter list contains a variable number of packet filters. For the "delete existing TFT" operation and the "no TFT operation", the packet filter list shall be empty.
For the "delete packet filters from existing TFT" operation, the packet filter list shall contain a variable number of packet filter identifiers. This number shall be derived from the coding of the number of packet filters field in octet 3.
For the "create new TFT", "add packet filters to existing TFT" and "replace packet filters in existing TFT" operations, the packet filter list shall contain a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 3.
Each packet filter is of variable length and consists of
- a packet filter identifier and direction (1 octet);
- a packet filter evaluation precedence (1 octet);
- the length of the packet filter contents (1 octet); and
- the packet filter contents itself (v octets).
The packet filter identifier field is used to identify each packet filter in a TFT. The least significant 4 bits are used.
The packet filter direction is used to indicate, in bits 5 and 6, for what traffic direction the filter applies:
00 - pre Rel-7 TFT filter
01 - downlink only
10 - uplink only
11 - bidirectional
Bits 8 through 7 are spare bits.
The packet filter evaluation precedence field is used to specify the precedence for the packet filter among all packet filters in all TFTs associated with this PDP address. Higher the value of the packet filter evaluation precedence field, lower the precedence of that packet filter is. The first bit in transmission order is the most significant bit.
The length of the packet filter contents field contains the binary coded representation of the length of the packet filter contents field of a packet filter. The first bit in transmission order is the most significant bit.
The packet filter contents field is of variable size and contains a variable number (at least one) of packet filter components. Each packet filter component shall be encoded as a sequence of a one octet packet filter component type identifier and a fixed length packet filter component value field. The packet filter component type identifier shall be transmitted first.
In each packet filter, there shall not be more than one occurrence of each packet filter component type. Among the "IPv4 remote address type" and "IPv6 remote address type" packet filter components, only one shall be present in one packet filter. Among the "single local port type" and "local port range type" packet filter components, only one shall be present in one packet filter. Among the "single remote port type" and "remote port range type" packet filter components, only one shall be present in one packet filter.
The term local refers to the MS and the term remote refers to an external network entity.
Packet filter component type identifier
Bits
8 7 6 5 4 3 2 1
0 0 0 1 0 0 0 0 IPv4 remote address type
0 0 0 1 0 0 0 1 IPv4 local address type
0 0 1 0 0 0 0 0 IPv6 remote address type
0 0 1 0 0 0 0 1 IPv6 remote address/prefix length type
0 0 1 0 0 0 1 1 IPv6 local address/prefix length type
0 0 1 1 0 0 0 0 Protocol identifier/Next header type
0 1 0 0 0 0 0 0 Single local port type
0 1 0 0 0 0 0 1 Local port range type
0 1 0 1 0 0 0 0 Single remote port type
0 1 0 1 0 0 0 1 Remote port range type
0 1 1 0 0 0 0 0 Security parameter index type
0 1 1 1 0 0 0 0 Type of service/Traffic class type
1 0 0 0 0 0 0 0 Flow label type
All other values are reserved.
For "IPv4 remote address type", the packet filter component value field shall be encoded as a sequence of a four octet IPv4 address field and a four octet IPv4 address mask field. The IPv4 address field shall be transmitted first.
For "IPv4 local address type", the packet filter component value field shall be encoded as defined for "IPv4 remote address type".
Both the MS and network indication for support of the Local address in TFTs are required to use this packet filter component.
For "IPv6 remote address type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and a sixteen octet IPv6 address mask field. The IPv6 address field shall be transmitted first.
For "IPv6 remote address/prefix length type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and one octet prefix length field. The IPv6 address field shall be transmitted first.
This parameter shall be used, instead of IPv6 remote address type, when both the MS and network indication for support of the Local address in TFT are present.
For "IPv6 local address/prefix length type", the packet filter component value field shall be encoded as defined for "IPv6 remote address /prefix length".
Both the MS and network indication for support of the Local address in TFTs are required to use this packet filter component.
For "Protocol identifier/Next header type", the packet filter component value field shall be encoded as one octet which specifies the IPv4 protocol identifier or IPv6 next header.
For "Single local port type" and "Single remote port type", the packet filter component value field shall be encoded as two octet which specifies a port number.
For "Local port range type" and "Remote port range type", the packet filter component value field shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first.
For "Security parameter index", the packet filter component value field shall be encoded as four octet which specifies the IPSec security parameter index.
For "Type of service/Traffic class type", the packet filter component value field shall be encoded as a sequence of a one octet Type-of-Service/Traffic Class field and a one octet Type-of-Service/Traffic Class mask field. The Type-of-Service/Traffic Class field shall be transmitted first.
For "Flow label type", the packet filter component value field shall be encoded as three octet which specifies the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label.
Parameters list (octets z+1 to v)
The parameters list contains a variable number of parameters that may be transferred. If the parameters list is included, the E bit is set to 1; otherwise, the E bit is set to 0.
Each parameter included in the parameters list is of variable length and consists of:
- a parameter identifier (1 octet);
- the length of the parameter contents (1 octet); and
- the parameter contents itself (v octets).
The parameter identifier field is used to identify each parameter included in the parameters list and it contains the hexadecimal coding of the parameter identifier. Bit 8 of the parameter identifier field contains the most significant bit and bit 1 contains the least significant bit. In this version of the protocol, the following parameter identifiers are specified:
- 01H (Authorization Token);
- 02H (Flow Identifier); and
- 03H (Packet Filter Identifier).
If the parameters list contains a parameter identifier that is not supported by the receiving entity the corresponding parameter shall be discarded.
The length of parameter contents field contains the binary coded representation of the length of the parameter contents field. The first bit in transmission order is the most significant bit.
When the parameter identifier indicates Authorization Token, the parameter contents field contains an authorization token, as specified in 3GPP TS 29.207 [100]. The first octet is the most significant octet of the authorization token and the last octet is the least significant octet of the authorization token.
The parameters list shall be coded in a way that an Authorization Token (i.e. a parameter with identifier 01H) is always followed by one or more Flow Identifiers (i.e. one or more parameters with identifier 02H).
If the parameters list contains two or more consecutive Authorization Tokens without any Flow Identifiers in between, the receiver shall treat this as a semantical TFT error.
When the parameter identifier indicates Flow Identifier, the parameter contents field contains the binary representation of a flow identifier. The Flow Identifier consists of four octets. Octets 1 and 2 contains the Media Component number as specified in 3GPP TS 29.207 [100]. Bit 1 of octet 2 is the least significant bit, and bit 8 of octet 1 is the most significant bit. Octets 3 and 4 contains the IP flow number as specified in 3GPP TS 29.207 [100]. Bit 1 of octet 4 is the least significant bit, and bit 8 of octet 3 is the most significant bit.
When the parameter identifier indicates Packet Filter Identifier, the parameter contents field contains the binary representation of one or more packet filter identifiers. Each packet filter identifier is encoded in one octet, in the 4 least significant bits. This parameter is used by the MS and the network to identify one or more packet filters in a TFT when modifying the QoS of a PDP context without modifying the packet filter itself.
