name: DMCR
full_form: Deferred Measurement Control Reading
context: A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode, in URA_PCH and CELL_PCH. When several PCHs exist in the cell, the FACH which carries the CTCH may be mapped to a different SCCPCH than the PCH selected by the UE for paging in Idle mode (as specified in Sec. 8.1). In this case, UEs with basic service capabilities shall be capable to change from the SCCPCH that carries the PCH selected for paging to another SCCPCH which carries Cell Broadcast messages (i.e. the CTCH mapped to an FACH) and receive BMC messages during time intervals which do not conflict with the UE specific paging occasions. The second system information broadcast channel (BCH on SCCPCH) is mapped on a separate SCCPCH, i.e. different from the SCCPCH which carriers the FACH with CTCH. In case CTCH occasions collide with transmissions of the second system information broadcast channel, the UE supporting second system information broadcast channel may decide not to
description: Deferred Measurement Control Reading (DMCR) is a procedure that allows the network to control the acquisition of System Information Blocks (SIBs) by the User Equipment (UE). This feature enables the UE to avoid the latency associated with acquiring SIBs, thereby speeding up CS fallback from LTE. The DMCR procedure also facilitates cell re-selection by allowing the UE to re-acquire system information after cell re-selection, and alleviates access delay in RRC connection request and cell update cases.
explanation: The context describes DMCR as a feature that controls the acquisition of SIBs, which is a specific procedure used in the network. The text highlights how DMCR can be used to avoid latency, speed up CS fallback, and alleviate access delay, indicating that it is a procedural mechanism rather than a protocol, interface, or other entity type.
section_title: 6.1	The impact of longer repetition periods on use cases
biotag_Context: O,B-Device,O,B-Service,I-Service,I-Service,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,B-Device,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,B-Connection,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,B-Service,I-Service,O,O,O,B-Connection,O,O,O,O,O,O,B-Network Function,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,B-Connection,O,O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,B-Device,I-Device,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Mode,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O