name: MBSF
full_form: Multicast/Broadcast Service Function
context: Figure 6.11.2 -1: Procedure for MTK update 1. The multicast join and session establishment procedure is performed between the UE and 5GS, during which MBSF generates MTK1&KID1 and distributes them to MBSTF and UEs. MTK1&KID1 are used to protect the MBS traffic. Details can be found in solution #3 or solution #8. 2. MBSF subscribes to the UDM/UDR on the changes of the multicast information including the authorization information. The UDM/UDR notifies the MBSF when the authorization for a UE to join the multicast session is changed. The MBS Session ID and UE info (i.e. GPSIs, number of UEs) are included in the notification. The MBS Session ID may be a Temporary Mobile Group Identifier (TMGI) or a multicast address. UE info indicates the change of authorization info. 3. MBSF triggers the MTK update based on the changes of authorization info or the key lifetime of MTK1. MBSF generates MTK2 and KID2 for this MBS session. For example, if the number of UEs whose authorization is revoked
description: The Multicast/Broadcast Service Function (MBSF) is a network function responsible for managing multicast/broadcast services in the 5G core network. It generates and distributes keys for protecting MBS traffic, subscribes to updates on multicast information from the UDM/UDR, and triggers key updates based on changes in authorization info or key lifetime.
explanation: MBSF is classified as a Network Function because it performs specific tasks related to managing multicast/broadcast services within the network, such as generating keys, subscribing to updates, and triggering key updates. This classification is justified by the context provided from 3GPP TS 33.850.
section_title: 6.11.2	Solution details
biotag_Context: O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,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,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Service,O,B-Parameter,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,B-Parameter,O,O,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,B-Device,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O