name: MRNC
full_form: MBMS Master RNC (as specified in TS 25.346 [4])
context: In this section the performance evaluation of E-DPCCH less is provided. The gains with the E-DPCCH less solution can be computed as follows: Gains on SDT device capacity (%) = ((supported UE number when E-DPCCH less is used) â (supported UE number when legacy transmission is used))/ (supported UE number when legacy transmission is used) (9) In Equation (9), supported UE number when legacy transmission is used denotes the number of supported SDT UEs when both E-DPDCH and E-DPCCH are transmitted. The supported UE number when E-DPCCH less is used denotes the supported number of SDT UEs when E-DPCCH is less. Based on the model given in Section 6.2.1.2.1, both quantities can be evaluated under the assumption of different repetition numbers. In the evaluation, the total RoT is assumed to be 10dB, similarly as in other coverage evaluations in the SDT study. The total RoT of 10dB corresponds to the total uplink load factor () of 90%. When introducing the SDT traffic in the WCDMA system, the
description: The MBMS Master RNC (MRNC) is a network function responsible for controlling logical resources of Radio Network Subsystems (RNSs) used for Multimedia Broadcast Multicast Service (MBMS) operations within an MBSFN cluster. It plays a crucial role in managing the MCCH configuration and scheduling information to be used, in coordination with the Controlling RNC (CRNC).
explanation: MRNC is classified as a Network Function based on its role in controlling and managing MBMS resources and configurations within the network, as described in the context. The context highlights MRNC's responsibilities, such as controlling logical resources, sending MCCH configuration information to CRNC, and scheduling information to be used.
section_title: 5.3.2	MBMS Control Plane Protocol Stack Architecture
biotag_Context: 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-Procedure,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,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-Procedure,B-Device,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,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,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Technology,O,O
biotag_Description: O,B-Service,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Service,I-Service,I-Service,I-Service,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O