Service Data Flow Classification
The following features are supported for Service Data Flows.
Support for Traffic Flow Template (TFT)
- One TFT is associated with each EPS bearer and is defined as part of the bearer's configuration at UE nodes in the following attribute: LTE > EPS Bearer Configurations > TFT Packet Filters
- Multiple packet filters can be defined per TFT. Each filter can be uplink only, downlink only, or bidirectional.
- Each packet filter specifies an IP Service Data Flows (SDF) based on one of the following:
- Type of service / traffic class
- Source IP address (host or network)
- Destination IP address (host or network)
- Protocol
- Source port (single value or range)
- Destination port (single value or range)
- SDFs with no matching filter under any EPS bearer use the Default bearer
- SDFs with matching filters for which the corresponding EPS/radio bearer is rejected by admission control may use the Default bearer instead of being dropped. This can be specified by setting the corresponding attribute while configuring the EPS bearer at UE nodes.
End-to-End EPS Bearer Mapping
In the uplink direction, the data messages are routed into the corresponding EPS bearer and EPS bearer subcomponents by using the following mapping:
- UE: SDF->TFT. At the UE the SDF information (e.g. ToS, source port, etc.) is mapped to a TFT.
- UE: TFT->RB-ID. For any given TFT there is a corresponding RB-ID that identifies the radio bearer which transports the user data over the radio to the eNodeB.
- eNodeB: RB-ID->S1-TEID. For a given RB-ID at the eNodeB a tunnel ID on the S1 interface is available towards the EPC.
In the downlink direction, the data messages are routed into their corresponding EPS bearer and EPS bearer subcomponents by using the following mapping:
- P-GW (EPC): SDF ->TFT. At the EPC the SDF information (e.g. ToS, source port, etc.) is mapped to a TFT.
- P-GW (EPC): TFT->S1-TEID. Any given TFT in the EPC has a corresponding tunnel ID on the S1 interface that transports the data traffic towards the corresponding eNodeB.
- eNodeB: S1-TEID->RB-ID. Once the data traffic reaches the eNodeB, the S1 tunnel ID is mapped to a corresponding RB-ID, which is the radio bearer that will deliver the data traffic to the corresponding UE.