name: HXRES
full_form: Hash eXpected RESponse
context: function is publicly known. Note that R is not sent along by the UE and, hence, not known to an outside attacker. Note further that the HPLMN cannot, by assumption, control R and hxres, and, hence, cannot find a pre-image of hxres with a false SUPI. HPLMN decrypts SUPI* and thus obtains SUPI and R. When the VPLMN receives from HPLMN the SUPI and R, it can quickly calculate hres=H(SUPI,R). By comparing hres=hxres the VPLMN (AMF) knows that HPLMN has returned the SUPI (under the above assumption) which the UE sent in a concealed way. The advantage of having the UE sent hxres in addition to SUPI* is that the HPLMN needs to return only a random value R in addition to the SUPI and VPLMN can fulfil LI by light-weight calculation of the hash hres. NOTE: Another option for hxres to be calculated is by H(SUPI*,SUPI,R). In this case, the VPLMN uses the combination of SUPI* and hxres as an identity proof information from UE. When then SUPI and R from HPLMN is received, the VPLMN can calculate
description: Hash eXpected RESponse (HXRES) is a parameter used in the authentication process between the User Equipment (UE) and the network. It is calculated using the SUPI (Subscriber Permanent Identifier), R (a random value), and a hash function H(). The HXRES is sent by the UE to the Home PLMN (HPLMN) and then forwarded to the Visited PLMN (VPLMN), which uses it to verify the authenticity of the SUPI.
explanation: The context describes HXRES as a value calculated using specific inputs (SUPI, R, and hash function H()) and used for authentication purposes. This matches the definition of a parameter in the telecommunications context.
section_title: 5.7.4.7.2.3	Solution 7.7-C: UE provides proof of SUPI in HPLMN-authenticated use case
biotag_Context: 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,B-Parameter,O,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,B-Parameter,O,O,O,O,B-Network,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Network,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,B-Network,O,O
biotag_Description: B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O