name: LAC
full_form: Link Access Control
context: a) DTCH or DCCH mapped to DCH, no multiplexing of dedicated channels on MAC: - no MAC header is required. b) DTCH or DCCH mapped to DCH, with multiplexing of dedicated channels on MAC: - C/T field is included in MAC header. c) DTCH or DCCH mapped to RACH/FACH: - TCTF field, C/T field, UE-Id type field and UE-Id are included in the MAC header. For FACH, the UE-Id type field used is the C-RNTI or U-RNTI. For RACH, the UE-Id type field used is the C-RNTI. d) DTCH or DCCH mapped to DSCH or USCH: - the TCTF field is included in the MAC header. The C/T field is included if multiplexing on MAC is applied. e) DTCH or DCCH mapped to DSCH or USCH where DTCH or DCCH are the only logical channels: - The C/T field is included in the MAC header if multiplexing on MAC is applied. Figure 9.2.1.1-1: MAC PDU formats for DTCH and DCCH
description: The Link Access Control (LAC) is a unique identifier used in the context of Home NodeB (HNB) deployments. It plays a crucial role in managing Location Area Updates and cell access control, particularly in dense HNB deployments. The LAC is utilized to reject location area updates to closed accessible cells if the UE has been previously rejected access in a non-accessible closed cell with the same LAC as accessible cells.
explanation: The context explicitly states that LAC is a unique identifier used for managing cell access and location area updates. Its function revolves around controlling access and updates based on this identifier.
section_title: 7.1.2.3	Number of LACs and Scaling
biotag_Context: O,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Connection,O,B-Connection,O,O,B-Connection,O,B-Connection,O,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,B-Connection,O,O,B-Connection,O,B-Connection
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,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,B-Parameter,O,O,O