name: KDF
full_form: Key Derivation Function
context: For eNB-KDF, MME-KDF, HSS-KDF negotiation, the following two solutions may be used: The KDF negotiation is not needed, i.e. one KDF is specified and used in all network entities. This solution is simple. This has been decided for Rel-8. The KDF negotiation is needed. There are several KDF negotiation solutions possible: One common KDF is negotiated by MME and UE; eNB-KDF, MME-KDF, HSS-KDF are negotiated by MME and UE; eNB, MME and HSS respectively negotiates an appropriate KDF with UE; eNB-KDF and MME-KDF are negotiated by MME and UE, HSS-KDF is negotiated by HSS and UE. KDF negotiation between UE and eNB & MME could be implicit In the future, UE and network devices may be upgraded, and they may support a newer and securer KDF algorithm. If the KDF negotiation is used, the upgraded network devices and UE can negotiate to use the securer KDF. In this way, the KDF can be flexibly updated. The following clauses sketches the impact of the above KDF negotiation solutions to the network.
description: A Key Derivation Function (KDF) is a protocol used in telecommunications for deriving keys from a shared secret value, ensuring secure communication between network entities.
explanation: The text describes KDF as being negotiated between network entities like MME, UE, and eNB to establish secure communication. This negotiation process and its purpose within the network framework classify it as a protocol.
section_title: 7.6.6.3	Possible solutions for KDF negotiation and their requirements
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,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,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,B-Device,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O