name: 3GPP TS 24.161
full_form: 3GPP Technical Specification 24.161
context: In order to request the allocation of bearer resources for one traffic flow aggregate, the UE shall send a BEARER RESOURCE ALLOCATION REQUEST message to the MME, start timer T3480 and enter the state PROCEDURE TRANSACTION PENDING (see example in figureÂ 6.5.3.2.1).
  The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create new TFT". The packet filters in the Traffic flow aggregate IE shall include at least one packet filter applicable for the uplink direction. In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the additional GBR required for the traffic flow aggregate.
  Figure 6.5.3.2.1: UE requested bearer resource allocation procedure
  For the NBIFOM procedures as defined in 3GPPÂ TSÂ 24.161Â [36], the UE may send a BEARER RESOURCE ALLOCATION REQUEST message to the MME. If the traffic flow aggregate IE is not needed in those procedures, the UE shall set:
  -	the length indicator of the Traffic flow aggregate IE to the value 1;
  -	the TFT operation code to "000";
  -	the E bit to zero; and
  -	the number of packet filters to zero;
  and in the Required traffic flow QoS IE:
  -	the length indicator to the value 1; and
  -	the QCI to zero.
description: 3GPP TS 24.161 specifies the stage 2 and 3 description of the NAS protocol for NBIFOM procedures.
explanation: Categorized as a Specification because it outlines key technical requirements and standards for NAS.
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,B-Device,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O
biotag_Description: B-Specification,I-Specification,I-Specification,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Procedure,O