name: ASME
full_form: Access Security Management Entity
context: the HSS derives a PLMN- and RAT-specific key KASME from the original CK, IK included in AV* and replaces these by KASME in AV*. How such a key could be transported from HSS to ASME is explained in S3-060632. HSS gets knowledge of the corresponding PLMN, RAT combination and the ASME (MME) identity as part of the SAE-specific authentication vector request received from MME as HSS needs this information anyway to be able to take authorization decisions of whether PLMN is allowed to serve a particular subscriber in combination with a particular RAT HSS transfers the modified AV* to ASME (MME). ASME (MME) sends , AUTN of the first AV* to UE. Upon receipt of a RAND, AUTN pair, the USIM checks whether MAC is correctly computed over AUTN. USIM is thus assured that AMF was not changed during transfer from AuC to USIM. This is all in accordance with Release 99 specifications. USIM does not interpret AMF. Instead ME interprets AMF and computes the key KASME from CK, IK if the corresponding
description: The Access Security Management Entity (ASME) is a network function responsible for managing access security in the Evolved Packet System (EPS). It plays a crucial role in the authentication and key agreement process, interacting with the Home Subscriber Server (HSS) and the Mobile Equipment (ME) to ensure secure access to the network.
explanation: The context provided highlights ASME's involvement in the SAE-specific authentication vector request, its interaction with HSS and ME, and its role in computing the key KASME. This justifies classifying ASME as a Network Function, given its responsibilities in managing access security within the network.
section_title: 7.4.8.2	SAE binding with AMF
biotag_Context: O,B-Network Function,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Technology,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,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,B-Technology,B-Network Function,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Specification,I-Specification,O,B-Device,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O