name: MSCH
full_form: MBMS point-to-multipoint Scheduling Channel
context: - LACs may need re-planning when a new HNB is introduced into a dense deployment and there is not a spare LAC immediately, or possibly on re-start as the LAC 'map' is sorted out; - Location Area Updates to closed accessible cells is rejected if the UE has been previously rejected access in a non-accessible closed cell with same LAC as accessible cells. c) Large LAC pool (>> 10) In this approach there is a large LAC pool. In comparison with the above mechanisms there is the advantage that: - very little LAC re-planning is likely to be needed. Therefore the issues of scalability related to frequent changes of LAC in closed HNBs do not apply. But has the disadvantage that: - in a dense deployment there will be over the air signalling because the UE will be attempting LAUs on cells that it had been previously rejected from. These are summarized in table 7.1.2.3-1. Table 7.1.2.3-1: LAC Pool Size Impact on Cell Broadcast and RAN Observation: Whilst there are mechanisms for approaching
description: The MBMS point-to-multipoint Scheduling Channel (MSCH) is a logical channel used for downlink transmission of MBMS service transmission schedules between the network and User Equipment (UEs) in RRC Connected or Idle Mode. It carries control plane information specific to MBMS services and S-CCPCH, which is sent to UEs receiving MTCH in a cell. The MSCH is mapped to a specific FACH in the S-CCPCH as indicated on the MCCH, with different error requirements than MTCH.
explanation: The context describes MSCH as a 'logical channel' used for transmitting schedules and control plane information related to MBMS services. This aligns with the definition of a Channel entity type, which typically refers to a communication pathway within a telecommunications system.
section_title: 6.2.1.3	MBMS point-to-multipoint Scheduling Channel (MSCH)
biotag_Context: O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,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,B-Parameter,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,O,O,O,O,B-Parameter,O,O,O,O,O,O,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,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,B-Parameter,O,O,O,O,B-Service,I-Service,O,B-Network,O,O,O,O,O,O,O
biotag_Description: O,B-Connection,I-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,B-Device,I-Device,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,B-Device,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O