The AKMA service requires a new logical entity, called the AKMA Anchor Function (AAnF).
The AKMA Architecture in Figure 4.1-2 is applicable to both roaming scenario and non-roaming scenario:
non-roaming: UE is in HPLMN and accessing an AF;
roaming scenario#1: UE is in VPLMN and accessing an internal HPLMN AF;
roaming scenario#2: UE is in VPLMN and accessing an internal VPLMN AF;
roaming scenario#3: UE is in VPLMN and accessing an external AF in the Data Network.
The AAnF is the anchor function in the HPLMN. The AAnF stores the AKMA Anchor Key (KAKMA) and SUPI/GPSI for AKMA service, which is received from the AUSF/UDM after the UE completes a successful 5G primary authentication. The AAnF also generates the key material to be used between the UE and the Application Function (AF) and maintains UE AKMA contexts. The AAnF sends SUPI/GPSI of the UE to AF located inside the operator's network according to the AF request or sends SUPI to NEF. If GPSI is required, the AAnF retrieves the GPSI from UDM based on available SUPI. The AAnF has the capability to trigger a primary authentication for KAKMA refreshing purpose.
The following interfaces are involved in AKMA network architecture:
Nnef: Service-based interface exhibited by NEF.
Nudm: Service-based interface exhibited by UDM.
Naanf: Service-based interface exhibited by AAnF.
The AAnF interacts with the AUSF and the AF using Service-based Interfaces. When the AF is located in the operator's network, the AAnF shall use Service-Based Interface to communicate with the AF directly. When the AF is located outside the operator's network, the NEF shall be used to exchange the messages between the AF and the AAnF.