name: PHY
full_form: Physical layer
context: Figure 27Q: MBMS Notification Update procedure, Successful Operation The procedure is initiated with an MBMS NOTIFICATION UPDATE COMMAND message sent from the CRNC to the Node B using the Node B Control Port. The Node B shall use the different NIs in the NI Information IE to generate, as specified in ref. TS 25.211 [7], the notification indicators it shall transmit on the MICH starting at the next coming MICH CFN equal to the value in the MICH CFN IE and for a duration equal to the Modification Period. If the value of MICH CFN IE is the same as the one in a previously received MBMS NOTIFICATION UPDATE COMMAND message, and if the MICH CFN occurrence has not been reached yet, the Node B shall overwrite the value of the NI Information IE in the previously received MBMS NOTIFICATION UPDATE COMMAND message. If the Modification Period IE is included in the MBMS NOTIFICATION UPDATE COMMAND message, the Node B shall use this as the new Modification Period starting at the next coming MICH CFN
description: The Physical layer (PHY) is the lowest layer in the OSI model and is responsible for transmitting raw bits over a physical medium. In the context of 3GPP TS 25.814, the PHY layer is specifically referred to as the downlink multi-carrier PHY channels, which include data-payload channels and control/supporting channels.
explanation: The term 'PHY' is classified as a Layer because it describes a specific level in the OSI model responsible for physical transmission of data. The context explicitly states that 'PHY' refers to the Physical layer within the 3GPP standard.
section_title: 7.2.2.5	DL Multi-Carrier PHY Channels
biotag_Context: O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,B-Service,B-Message,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,I-Network Function,O,O,B-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,B-Parameter,O,B-Message,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,B-Parameter,O,O,O,O,O,O,B-Connection,B-Parameter,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Parameter,B-Message,O,O,O,O,O,O,O,O,O,O,B-Service,B-Message,O,O,O,O,O,O,B-Connection,B-Parameter,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,B-Parameter,O,B-Message,O,O,O,O,B-Service,B-Message,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Service,B-Message,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Parameter
biotag_Description: O,B-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O