name: ACDC
full_form: Application specific Congestion control for Data Communication
context: With RRC signalling, the UE will in addition be informed about: The E-HICH configuration Including signature sequence number and channelisation code; The E-RGCH configuration - Including signature sequence number, channelisation code (same as the E-HICH), RG reference step size for serving RLS, RG step size for non-serving RL and Serving E-DCH RLS ID; The E-AGCH configuration - Including E-RNTI(s) and channelisation code; The E-DPCCH configuration - E-DPCCH/DPCCH Power Offset; - Threshold (in TTIs) used by the UE when evaluating the time needed to completely empty its buffers. Used as a conditions for setting the âhappyâ bit in E-DPCCH; The E-DPDCH configuration: - A UE is allocated one and only one TB size table by RRC. A total of four TB size tables are defined by the standard: - Exponentially distributed TB sizes over the corresponding dynamic range, one optimized table for 2ms TTI and one optimized table for 10ms TTI; - TB sizes for 336 bit RLC PDU size, one optimized table for 2ms
description: Application specific Congestion control for Data Communication (ACDC) is a protocol feature in the 3GPP specification that enables the network to control new PS domain access attempts from particular applications in the UE in idle mode. This prevents or mitigates overload of the access network and/or the core network by allowing the network to manage congestion based on application-specific categories.
explanation: The context describes ACDC as a mechanism for controlling data communication congestion, outlining its role in managing access attempts from applications in idle mode. The mention of it being configured with other access control mechanisms (ACB, EAB, and DSAC) further classifies it as a protocol due to its specific behaviors and interactions within the network.
section_title: 16	ACDC in Idle Mode
biotag_Context: O,B-Protocol,O,O,B-Device,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,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Connection,O,O,O,B-Network Function,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-Device,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,O,B-Device,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Protocol,B-Connection,O,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,B-Mode,O,O,O,O,O,O,O,O,B-Device,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,O,O