name: MAC
full_form: Message Authentication Code
context: The solution follows the SUCI generation scheme, but the MAC tag is generated out of a new MAC key, which is the result of an additionally introduced one-time function taking the Ephemeral MAC key and KSUCI as input. The rest of the known SUCI generation scheme is not touched. KSUCI is generated by considering long term key K, FC and newly generated RANDSUCI. UE can share the scheme output of SUCI to UDM as "Final output = Eph. public key || RANDSUCI || Ciphertext || MAC tag [|| any other parameter]". During SUCI generation, after the Ephemeral MAC key has been generated (according to the scheme described in Annex A of TS 33.501), a new one-way function f is applied. f is using the generated KSUCI as additional input to the ephemeral MAC key. The result is used as the new MAC key: MAC key f (KSUCI, Ephemeral MAC key). The USIM always performs the computation of the key KSUCI, even in case of SUCI calculation in the ME. With the new MAC key, the computation of the SUCI is continued as
description: Message Authentication Code (MAC) is a cryptographic technique used to verify the authenticity and integrity of data transmitted over a network. It involves generating a unique code based on the message content and a shared secret key. This code, called the MAC tag, is appended to the message. The recipient can then use the same key to calculate the expected MAC tag. If the calculated tag matches the received tag, it confirms the message's authenticity and that it hasn't been tampered with.
explanation: MAC is classified as a security mechanism because its primary function is to protect data integrity and authenticity during transmission. It achieves this by using cryptographic techniques to generate a unique code that verifies the sender's identity and ensures the message hasn't been altered.
section_title: 6.2.8.2	Solution details
biotag_Context: O,O,O,O,B-Parameter,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,O,O,B-Parameter,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,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,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Protocol,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Parameter,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,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,O,O,B-Protocol,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O