name: MAC
full_form: Master Auxiliary Concept
context: The MAC header for SHCCH is as shown in figure 9.2.1.6-1. a) SHCCH mapped to RACH and USCH/FACH and DSCH: - TCTF has to be included. b) SHCCH mapped to RACH and USCH/FACH and DSCH, where SHCCH is the only channel. Figure 9.2.1.6-1: MAC PDU format for SHCCH 9.2.1.7 MAC Header for MCCH The MAC PDU format for MCCH is as shown in figure 9.2.1.7-1. a) If the MAC header for MCCH is not configured through the MAC control SAP: - there is no MAC header for MCCH. b) If the MAC header for MCCH is configured through the MAC control SAP: - TCTF field is included in the MAC header for MCCH. NOTE: If MCCH is not the only channel on the FACH, the MAC header shall be configured for the MCCH. Figure 9.2.1.7-1: MAC PDU format for MCCH 9.2.1.8 MAC Header for MTCH The TCTF field and MBMS-Id field are included in the MAC header for MTCH as shown in figure 9.2.1.8.1. Figure 9.2.1.8-1: MAC PDU format for MTCH 9.2.1.9 MAC Header for MSCH The MAC PDU format for MSCH is as shown in figure 9.2.1.9-1. a) If the
description: The Master Auxiliary Concept (MAC) is a sublayer of the Data Link Layer in the OSI model. It manages data transmission and multiplexing on a single physical link. In 3GPP TS 25.321, MAC focuses on formatting and structuring MAC headers for channels like SHCCH, MCCH, MTCH, and MSCH.
explanation: MAC is classified as a 'Protocol' because it defines the rules governing data transmission at the Data Link Layer. Its role in specifying header formats for different channels aligns with the function of protocols in standardizing communication.
section_title: 9.2.1.6	MAC Header for SHCCH
biotag_Context: O,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Protocol,B-Connection,O,O,B-Connection,O,B-Protocol,O,O,B-Message,O,B-Protocol,B-Connection,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Message,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,B-Message,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,B-Connection,O,O,B-Message,O,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,O,B-Protocol,B-Connection,O,O,B-Connection,O,B-Protocol,O,O,B-Connection,O,B-Protocol,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O