name: TFT
full_form: Traffic Flow Template
context: sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". b) if the mapped EPS bearer context includes a traffic flow template, the UE shall check the traffic flow template for different types of TFT IE errors as follows: 2) Semantic errors in TFT operations: i) TFT operation = "Create a new TFT" when there is already an existing TFT for the EPS bearer context. ii) When the TFT operation is an operation other than "Create a new TFT" and there is no TFT for the EPS bearer context. iii) TFT operation = "Delete packet filters from existing TFT" when it would render the TFT empty. iv) TFT operation = "Delete existing TFT" for a dedicated EPS bearer context. In case iv, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU
description: A Traffic Flow Template (TFT) is a parameter used in telecommunications to define packet filters and operations for traffic management within an EPS bearer context. It is utilized by the UE to manage packet flows based on specific rules, ensuring efficient data transmission.
explanation: The text describes TFT as a parameter used to define packet filters and operations for traffic management. This aligns with the definition of a Parameter as a configurable attribute that influences network behavior.
section_title: 10.1.2.1Network-requested PDU session modification / Accepted
biotag_Context: O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-State,I-State,I-State,O,B-Procedure,O,O,O,O,B-Network,O,O,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Parameter,B-Message,O,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Network,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Network,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O