name: DUIK
full_form: Discovery User Integrity Key
context: m at UTC time t, the announcing UE first computes the current timeslot j as j = CEIL (t â t0)/tDelta where CEIL(x) maps x to the least integer greater than or equal to x. This implies that the announcing UE has to use DUIHC link HN-j(S). Note that this requires that N-j > 0. The announcing UE uses HN-j(S) together with the DUIK to compute the final key (DHCUIK) used in the creation of the MIC of the message m. This key is denoted as Discovery Hash Chain User Integrity Key (DHCUIK) and is computed as: DHCUIK = KDF(DUIK, HN-j(S)) The reason for including the DUIK in the derivation of the DUIKHCL is to: (1) provide interoperability with the existing TS 33.303 solution and (2) show that this solution is as secure as the existing one since the existing DUIK is used in the generation of the key that will be used in the MIC computation. The MIC of message m is denoted MICm and is computed as: MICm = MIC(m, DHCUIK) When the announcing UE broadcasts message m towards the monitoring UEs, the
description: The Discovery User Integrity Key (DUIK) is a critical network attribute used in the derivation of the Discovery Hash Chain User Integrity Key (DHCUIK), which is utilized for computing the Message Integrity Code (MIC) of messages broadcasted by the announcing UE. The DUIK plays a vital role in ensuring interoperability with existing solutions and maintaining security levels comparable to those of established standards.
explanation: The context explicitly mentions the use of DUIK in the computation of DHCUIK, which is then used for MIC calculation. This highlights the importance of DUIK as a parameter in the underlying procedure described in 3GPP TS 33.847.
section_title: 6.43.2.1	Underlying procedure
biotag_Context: O,O,B-Miscellaneous,O,O,O,O,B-Device,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-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,O,O,O,O,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-Specification,O,O,O,O,O,O,O,O,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-Organization,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,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,O,O,O,O,O,O