name: AUSF
full_form: Authentication Server Function
context: The AUSF provides UE authentication service to the requester NF by Nausf_UEAuthentication. For AKA based authentication, this operation can be also used to recover from synchronization failure situations. Clause 14.1.2 describes the Nausf_UEAuthentication service. The service operations listed here are used in procedures that are described in clause 6 of the present document and in TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ]  [109]. Clause 14.1.3 describes the Nausf_SoRProtection service used in procedures that are described in clause 6.14 of the present document. Clause 14.1.4 describes the Nausf_UPUProtection service used in procedures that are described in clause 6.15 of the present document. Since AUSF is completely security-related, all service operations are described in the present document. TS 23.501[ System architecture for the 5G System (5GS) ]  [2], clause 7.2.7, only lists the services and TS 23.502[ Procedures for the 5G System (5GS) ]  [8], clause 5.2.10, provides the reference to the present document.
description: The Authentication Server Function (AUSF) is a network function in the 5G core architecture that provides authentication services for User Equipment (UE). It plays a critical role in ensuring secure access to the network by handling UE authentication requests and recovering from synchronization failure situations. The AUSF's operations are described in detail within clause 14.1 of the present document, highlighting its importance in security aspects of proximity-based services (ProSe) in the 5G System (5GS).
explanation: AUSF is classified as a Network Function because it serves as a key component in managing UE authentication and access control within the 5G core network. Its primary role aligns with the 3GPP's specifications for secure network operations, emphasizing its significance in maintaining the integrity of the network.
section_title: 14.1 Services provided by AUSF 14.1.1 General
biotag_Context: O,B-Network Function,O,B-Device,O,O,O,O,O,B-Network Function,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,O,O,O,O,O,O,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,B-Technology,I-Technology,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,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Device,I-Device,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,I-Technology,O