name: MTK
full_form: MBMS Traffic Key
context: The MTK is updated based on the change of the authorization information or based on the local policy (e.g. key lifetime expiration) as detailed in TS 33.501 [3]. In such cases, the MBSF or MB-SMF in PLMN1 triggers the MTK update procedure by requesting the AF to provide a fresh MTK. The key update request message includes the MBS session ID. If the AF has generated a fresh MTK, the AF provides the fresh MTK to the NEF/MBSF in the Nnef_MBSSession_Update request. Then the refreshed MTK is delivered to the UE as specified in TS 33.501 [3]. As both PLMN1 and PLMN2 supports MOCN, the MTK in PLMN2 should also be updated. Therefore, the AF initiates the MTK update procedure for the PLMN2 by sending the updated MTK to the NEF/MBSF in PLMN2, in the Nnef_MBSSession_Update request. If MSK needs to be updated, then the AF provides the newly generated MSK along with the MTK and the associated MSK ID and MTK ID to the PLMNs. Then the refreshed MSK and MTK is delivered to the UE as specified in TS
description: The MBMS Traffic Key (MTK) is a critical network attribute used for securing multimedia broadcast/multicast services (MBMS) traffic. It is updated based on changes in authorization information or local policy, such as key lifetime expiration, and is provided by the Application Function (AF) to the Network Exposure Function/Multimedia Broadcast Single Frequency Network (NEF/MBSF) for delivery to the User Equipment (UE).
explanation: The context explicitly mentions that MTK is updated based on specific conditions and is used for securing MBMS traffic, indicating its role as a critical network attribute. This aligns with the definition of a Parameter in the provided categories.
section_title: 6.2.2.4	Key update procedure
biotag_Context: 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,B-Specification,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,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,B-Network Function,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,B-Parameter,B-Parameter,O,B-Parameter,B-Parameter,O,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,B-Device,O,O,O,B-Specification
biotag_Description: O,B-Parameter,I-Parameter,I-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,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Network,O,O,B-Service,B-Technology,I-Technology,I-Technology,O,O,O,O,O,B-Device,I-Device,O