name: MICH
full_form: MBMS notification Indicator Channel
context: There is one HARQ entity per E-DCH in the UE. A number of parallel HARQ processes (identified by a HARQ process identifier) are used in the UE to support the HARQ entity, allowing transmissions to take place continuously while the UE is granted resources.The HARQ entity identifies the HARQ process for which transmission should take place if resources are available. Also, based on timing with respect to a previously-transmitted MAC-e or MAC-i PDU it routes the receiver feedback (ACK/NACK information), relayed by the physical layer, to the appropriate HARQ process. The minimum number of HARQ processes per HARQ entity is a function of T1 and T2 (see subclause 11.9.1.1). The maximum number of HARQ process identifiers per HARQ entity is 8. Each process is associated with a HARQ process identifier numbered from 0 to 7. For multi-carrier E-DCH operation, the maximum number of HARQ process per HARQ entity is 4. The HARQ entity is responsible for determining which HARQ process will use the
description: The MBMS Notification Indicator Channel (MICH) is a channel used for transmitting notification indicators in the context of Multimedia Broadcast Multicast Service (MBMS). It is utilized by the Node B to send notification indicators based on the information received from the CRNC via the MBMS NOTIFICATION UPDATE COMMAND message. The MICH is controlled by parameters such as the MICH CFN (Counting Frame Number) and the Modification Period, which dictate when and for how long the notification indicators are transmitted.
explanation: The text explicitly states that the MICH is a "channel" used for transmitting notification indicators within the MBMS framework.  Its function is to relay information from the CRNC to Node B regarding updates in notifications.
section_title: 8.2.30.2	Successful Operation
biotag_Context: O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,B-Protocol,O,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,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,I-Service,I-Service,I-Service,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Service,B-Message,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Connection,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O