name: FLUTE
full_form: File delivery over Unidirectional Transport
context: The BM-SC controls the use of the MBMS Service Keys (MSKs) to secure the different RTP sessions and FLUTE channels. The MSKs are used to protect the delivery of MBMS Transport Keys (MTKs), which are used to secure the RTP sessions and FLUTE channels as specified within clauses 6.5 and 6.6. The delivery of MSKs is secured with user specific MBMS User Key (MUK), which is received from GBA, cf. clause 6.1. MSKs and MTKs are managed at the MBMS User Service Level. The following rules apply for MBMS key management: The use of the same MTK within two different RTP sessions is not allowed according to RFC3711 [11] section 9.1. It shall be possible to update the MTKs during an RTP session or FLUTE channel to enhance the security. MSKs shall be used to protect MTKs of only one RTP session or FLUTE channel. It shall be possible to update the MSKs during an RTP session or FLUTE channel to enhance the security. MSKs within one Key Group shall be used to protect MTKs of only one RTP session or
description: FLUTE (File delivery over Unidirectional Transport) is a protocol designed for secure file transfer over unidirectional transport channels. It works in conjunction with protocols like RTP to ensure the safe delivery of MBMS Transport Keys (MTKs).
explanation: The text explicitly states that FLUTE is a protocol for file delivery over unidirectional transport.  It also mentions its use in securing the delivery of MTKs, further solidifying its classification as a protocol.
section_title: 4.2	Key management overview
biotag_Context: O,B-Network Function,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,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,B-Service,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,B-Parameter,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,B-Protocol,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,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O
biotag_Description: 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,O,B-Protocol,O,O,O,O,O,O,B-Service,O,O,O