Network-initiated primary authentication
By triggering master authentication or reauthentication in 5G systems, combined with the life and expiration time of the AUSF key, the security problems caused by long-term use of AUSF keys are solved, ensuring timely updates of AKMA keys, preventing service failures and improving The reliability of safety certification.
Patent Information
- Application Number
- CN202380030547.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-28
- Filing Date
- 2023-03-27
- Publication Date
- 2024-11-12
AI Technical Summary
In 5G systems, the UE's master authentication generates AUSF key (KAUSF) shared between the UE and the home network for a long time, resulting in the key not being refreshed, which may lead to security issues during roaming and UE parameter updates, especially In case the same AUSF key is reused after counter wrapping.
Triggering master authentication or reauthentication through the home network, taking into account factors such as authentication vectors, AUSF key lifetime and expiration time, roaming turn counter wrapping, and UE parameter update counter wrapping, to bind the life of AKMA key and application function keys, considering factors such as authentication vectors, AUSF key lifetime and expiration time, roaming turn counter wrapping, and UE parameter update counter wrapping, to bind the life of AKMA key and application function keys. or expiration time to prevent service failure and force the use of new AKMA keys.
It effectively prevents service failures caused by the expiration of application function keys, ensures timely updates and use of security keys, and improves the reliability of secure authentication and data transmission between UE and the network.
Smart Images

Figure CN118947156A_ABST
Abstract
Description
Background Art
[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 324,241, filed on March 28, 2022, entitled “Network Initiated Primary Authentication,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0002] The present disclosure relates to wireless communications and, more particularly, to network initiated primary authentication. Background Art
[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may be further referred to as an eNodeB (eNB), a next generation NodeB (gNB), a core network function (CNF), or other suitable terms. Each network communication device, such as a base station, may support wireless communication of one or more user communication devices, which may be further referred to as a user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system, such as time resources (e.g., symbols, time slots, sub-time slots, mini-time slots, aggregated time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, a wireless communication system may support wireless communication across various radio access technologies (RATs), including third generation (3G) RATs, fourth generation (4G) RATs, fifth generation (5G) RATs, and other suitable RATs other than 5G. In some cases, a wireless communication system may be a non-terrestrial network (NTN), which may support various communication devices for wireless communication in an NTN. For example, the NTN may include network entities on non-ground vehicles, such as satellites, unmanned aerial vehicles (UAVs), and high altitude platform systems (HAPS), as well as network entities on the ground, such as gateway entities capable of transmitting and receiving over long distances.
[0005] In the 5G system, the UE's primary authentication generates the authentication server function (AUSF) key (i.e., K AUSF The purpose of the master authentication and key agreement procedure is to enable mutual authentication between the UE and the network and to provide key material that can be used between the UE and the serving network in subsequent security procedures. Successful master authentication of the UE allows the generation of K AUSF In 5G, K AUSF is a long-term key, since the UE can be communicatively linked to the network for a long duration without refreshing K AUSFIn this long duration scenario, the UE may not refresh K AUSF . Summary of the invention
[0006] The present disclosure relates to methods, apparatuses, and systems for supporting network-initiated primary authentication. By utilizing the described techniques, the home network can trigger primary authentication or re-authentication while taking into account factors such as lifetime and / or expiration time associated with the primary authentication (such as authentication vectors or AUSF keys), Steering of Roaming (SoR) counter wraparound, and UE Parameter Update (UPU) counter wraparound. In addition, the described technical solution enables the application authentication and key management (AKMA) key (K AKMA ) and application function key (K AF ) has a lifetime or expiration time associated with the primary authentication and AUSF key (K AUSF ) life or expiration time. This prevents service failures associated with application function key expiration and implicitly forces the UE and the AKMA Anchor Function (AAnF) to use new AKMA keys associated with a successful primary authentication or re-authentication after the application function key expires.
[0007] Aspects of the present disclosure relate to implementing home network triggered primary authentication and / or re-authentication, and handling the lifetime and / or expiration of related security keys. Aspects of the present disclosure also relate to setting application function key expiration while taking into account the AKMA key (K AKMA ) expiration and / or lifetime. Aspects of the present disclosure also relate to providing authentication-related lifetime and / or expiration times to the AUSF and / or Access and Mobility Management Function (AMF) via unified data management (UDM). The UE and the network may establish a new security context (K) derived from a successful primary authentication or re-authentication. AUSF and K SEAF ) successfully reauthenticates and establishes NAS security and AS security.
[0008] Some implementations of the methods and apparatus described herein may include wireless communications at a device (e.g., a device implemented as (AUSF)), and the device receives an authentication request from a security anchor function (SEAF) and sends a data request for authentication data to a UDM. The AUSF may receive authentication data from the UDM for primary authentication and set an expiration time for security information associated with a success in the primary authentication. The AUSF may then send an authentication message including the authentication information including the security information and the expiration time to an AKMA anchor function (AAnF) that registers the expiration time. The AUSF may also initiate re-authentication based at least in part on the expiration of the authentication information.
[0009] In some implementations of the methods and apparatus described herein, the authentication information may include a SoR counter wrap and / or a UPU counter wrap, and the AUSF initiates re-authentication based on the expiration of the SoR counter wrap or the UPU counter wrap. The authentication information may include an AUSF key (K AUSF ) lifespan, and AUSF is based on K AUSF The AUSF may also initiate re-authentication based on the re-authentication policy of the home network operator. Security information may include the AUSF key (K AUSF ), AKMA key (K AKMA ), authentication vector, primary authentication state, and / or primary authentication result. AUSF may use the authentication message as an AKMA key (K AKMA ) registration request is sent to AAnF, the AKMA key (K AKMA ) The registration request includes the UE subscription permanent identifier (SUPI), AKMA key identifier (A-KID), K AKMA , and / or K AKMA The AUSF may send an authentication response to the SEAF, which includes an indication of successful authentication, SUPI, AKMA key (K AKMA ) and / or the expiration time of the primary authentication. The authentication data received from the UDM includes an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a SUPI, an AKMA indication, and / or a routing indicator.
[0010] In addition, the AUSF may send an authentication trigger request to the AMF / SEAF to initiate re-authentication, the authentication trigger request including the SUPI and / or an indication that re-authentication is required. The AUSF may also receive an acknowledgment (ACK) from the AMF / SEAF in response to the authentication trigger request sent to the AMF / SEAF. The AUSF may send an authentication trigger request to the UDM, the authentication trigger request including: the SUPI, the indication that re-authentication is required, and / or an indication of the reason for the authentication trigger request. The reason for the authentication trigger request may be an expired AUSF key (K AUSF ), counter wrap expiration indication, and / or authentication life expiration indication. The AUSF may receive an ACK from the UDM in response to the authentication trigger request sent to the UDM. The AUSF may also receive authentication result information from the UDM, the authentication result information including an expiration time and an authentication result confirmation.
[0011] Some implementations of the methods and apparatus described herein may include wireless communication at a device (e.g., a device implemented as an AAnF), and the device receives an authentication message from the AUSF, the authentication message including authentication information including at least security information and an expiration time. The AAnF maintains the security information and the expiration time, the security information including at least an AKMA key (K AKMA AAnF can send a registration response to AUSF as a response to the AKMA key (K AKMA ) is registered.
[0012] In some implementations of the methods and apparatus described herein, the authentication message is received from the AUSF as an AKMA key (K AKMA ) registration request, and includes SUPI, AKMA key identifier (A-KID), K AKMA、 and / or K AKMA AAnF can obtain the expiration time of the AKMA key (K AKMA ) Export the application function (AF) key (K AF ), and based on K AKMA The expiration time or lifetime is set to K AF AAnF can receive the expiration time for the AKMA key (K AKMA ) key request, and based on determining the AKMA key (K AKMA ) has expired, and sends a waiting time response to AF. AAnF can receive a response to the AKMA key (K AKMA ), the key request including an AKMA key identifier (A-KID), determining whether a stored AKMA key expiration time or lifetime has expired for the associated A-KID, and one of the following: if the stored AKMA key expiration time or lifetime has not expired, determining to refresh the AF key; or if the stored AKMA key expiration time or lifetime has expired, determining not to refresh the AF key and waiting for a new AKMA key to be provided by the AUSF.
[0013] Some implementations of the methods and apparatus described herein may include wireless communications at a device (e.g., a device implemented as an AMF / SEAF), and the device receives a registration request from a UE and sends an authentication request to the AUSF. The AMF / SEAF receives an authentication response from the AUSF, the authentication response including: an indication of successful authentication, and an expiration time and / or lifetime of the authentication duration. The AMF / SEAF may maintain the expiration time and / or lifetime of the authentication duration together with the SUPI configured to trigger re-authentication.
[0014] In some implementations of the methods and apparatus described herein, the AMF / SEAF may store an expiration time and / or lifetime of the authentication duration, and initiate triggering re-authentication of the UE based on the expiration time and / or lifetime of the authentication duration. The AMF / SEAF may, in response to receiving a handover required message, send the expiration time and / or lifetime of the authentication duration to a target AMF, and the target AMF is configured to store the expiration time and / or lifetime of the authentication duration together with the SUPI and the UE context so that it can be used to invoke re-authentication. The AMF / SEAF may receive an authentication trigger request from the AUSF to initiate re-authentication, the authentication trigger request including the SUPI and / or an indication that re-authentication is required, and in response to the authentication trigger request, send an ACK to the AUSF.
[0015] Some implementations of the methods and apparatus described herein may include wireless communication at a device (e.g., a device implemented as a UDM), and the device receives a data request for authentication data from the AUSF and sends the authentication data to the AUSF for primary authentication. The UDM may receive an authentication trigger request from the AUSF, the authentication trigger request including the SUPI, an indication that reauthentication is required, and / or an indication of a reason for the authentication trigger request. The UDM may request an ACK to be sent to the AUSF in response to the authentication trigger.
[0016] In some implementations of the methods and apparatus described herein, the authentication data sent to the AUSF includes the AV, the expiration time of the AV, the expiration time of the primary authentication, the SUPI, the AKMA indication, and / or the routing indicator. The reasons for the authentication trigger request may include: expired AUSF key (K AUSF ), counter wrap expiration indication, and / or authentication life expiration indication. The UDM may determine whether the authentication trigger request is valid based on the expiration time and / or expiration indication of the life duration as configured for the AV. The UDM may determine whether the authentication trigger request is valid based on the expiration time, the life duration of the primary authentication associated with the SUPI, and / or the expiration indication of the life duration of the primary re-authentication associated with the SUPI. The UDM may store the SoR data and / or UPU data until a successful primary re-authentication is completed and the SoR and / or UPU are re-initiated. The UDM may store the authentication status of the UE and set the authentication expiration time of the UE. The UDM may send an authentication result confirmation response to the AUSF, the authentication result confirmation response including: the expiration time and / or life duration associated with the primary authentication. The UDM may send a registration response result to the AMF, the registration response result including the expiration time and / or life duration associated with the primary authentication. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Various aspects of the present disclosure for network-initiated master authentication are described with reference to the following drawings. The same numbers may be used to reference similar features and components shown in the figures.
[0018] Figure 1 An example of a wireless communication system supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated.
[0019] Figure 2 FIG. 1 illustrates an application anchor key (K) as associated with a network initiated primary authentication according to aspects of the present disclosure. AKMA )Refresh example of authentication and key management for general signaling.
[0020] Figure 3 Illustrated is an example of phase 1 signaling of factors considered by the AUSF to trigger primary re-authentication, which supports network-initiated primary authentication according to aspects of the present disclosure.
[0021] Figure 4 An example of Phase 2 signaling as a process for AUSF triggered re-authentication from a home network is illustrated, which supports network initiated primary authentication according to aspects of the present disclosure.
[0022] Figure 5 An example of setting the expiration time and / or lifetime of an application function key in support of network-initiated primary authentication according to aspects of the present disclosure is illustrated.
[0023] Figure 6 An example of providing authentication-related lifetime and / or expiration times after a successful primary authentication in support of network-initiated primary authentication according to aspects of the present disclosure is illustrated.
[0024] Figure 7 An example block diagram of components of a device (eg, implemented as an AUSF) that supports network-initiated primary authentication according to aspects of the present disclosure is illustrated.
[0025] Figure 8 An example block diagram of components of a device (eg, implemented as an AAnF, AMF / SEAF, or UDM) supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated.
[0026] Figures 9 to 16 A flow chart of a method of supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0027] The implementation of network-initiated primary authentication is described, such as in connection with a successful re-authentication of the UE and the network. By utilizing the described techniques, the home network can trigger a primary authentication or re-authentication while taking into account factors such as the lifetime and / or expiration time associated with the primary authentication (such as the authentication vector or AUSF key), SoR counter wraparound, and UPU counter wraparound. In addition, the described technical solution enables the AKMA key (K AKMA ) and application function key (K AF ) has a lifetime or expiration time associated with the primary authentication and AUSF key (K AUSF ) life or expiration time. This can prevent service failures related to application function key expiration and implicitly force the UE and AKMA anchor function (AAnF) to use new AKMA keys associated with successful primary authentication or re-authentication after application function key expiration.
[0028] In the 5G system, the UE's primary authentication generates the authentication server function (AUSF) key (i.e., K AUSF The purpose of the master authentication and key agreement procedure is to enable mutual authentication between the UE and the network and to provide key material that can be used between the UE and the serving network in subsequent security procedures. Successful master authentication of the UE allows the generation of K AUSF In 5G, K AUSF is a long-term key, since the UE may be communicatively linked to the network for a long duration without refreshing K AUSF In this long duration scenario, the home network does not trigger UE re-authentication to refresh K AUSF Given that the security of AKMA keys, Steering of Roaming (SOR) and UE parameter updates rely on AUSF keys, it is undesirable to use the same AUSF keys for a longer period of time without any re-authentication.
[0029] Aspects of the present disclosure include a technical solution that enables the home network to trigger a primary authentication or re-authentication, taking into account factors such as the lifetime and / or expiration time associated with the primary authentication (such as the authentication vector or AUSF key), SoR counter wraparound, and UPU counter wraparound. In addition, the described technical solution enables the AKMA key (K AKMA ) and application function key (K AF ) has a lifetime or expiration time associated with the primary authentication and AUSF key (K AUSF ) life or expiration time. This can prevent service failures related to application function key expiration and implicitly force the UE and AKMA anchor function (AAnF) to use new AKMA keys associated with successful primary authentication or re-authentication after application function key expiration.
[0030] Aspects of the present disclosure relate to enabling home network triggered primary authentication and / or re-authentication, and handling the lifetime and / or expiration of related security keys. Aspects of the present disclosure also relate to setting application function key expiration while taking into account the AKMA key (K AKMA ) expiration and / or lifetime. Aspects of the present disclosure also relate to providing authentication-related lifetime and / or expiration times to the AUSF and / or AMF via UDM. The UE and the network may determine the lifetime and / or expiration time of the authentication-related authentication based on a new security context (K ) derived from a successful primary authentication or re-authentication. AUSF and K SEAF ) successfully reauthenticates and establishes NAS security and AS security.
[0031] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts related to network-initiated primary authentication.
[0032] Figure 1 An example of a wireless communication system 100 that supports network-initiated primary authentication according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).
[0033] One or more base stations 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more base stations 102 described herein may be or include or may be referred to as a base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB), radio head (RH), relay node, integrated access and backhaul (IAB) node or other suitable terms. The base station 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, the base station 102 and the UE 104 may perform wireless communication via an NRUu interface.
[0034] The base station 102 may provide a geographic coverage area 110 for which the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area. For example, the base station 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the base station 102 may be mobile, such as when implemented as a gNB on a satellite or other non-terrestrial station (NTS) associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, and different geographic coverage areas 110 may be associated with different base stations 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0035] One or more UEs 104 may be dispersed in a geographic area, or coverage area 110, of the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, a customer premises equipment (CPE), a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. In addition, or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In other implementations, UE 104 may be mobile in the wireless communication system 100, such as a ground station in motion (ESIM).
[0036] One or more UEs 104 may be devices in different forms or with different functions. Figure 1 Some examples of UE 104 are illustrated in FIG. UE 104 may be able to communicate with various types of devices, such as base stations 102, other UEs 104, or network devices (e.g., core network 106, relay devices, gateway devices, integrated access and backhaul (IAB) nodes, location servers implementing location management functions (LMFs), or other network devices). In addition, or alternatively, UE 104 may support communication with other base stations 102 or UEs 104, which may act as relays in the wireless communication system 100.
[0037] The UE 104 may also support wireless communications directly with other UEs 104 via a communication link 112. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 112 may be referred to as a side link. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.
[0038] The base station 102 may support communication with the core network 106 or with another base station 102, or both. For example, the base station 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, or other network interfaces). The base stations 102 may communicate with each other via backhaul links 118 (e.g., via X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as remote radio heads, smart radio heads, gateways, transmission-reception points (TRPs), and other network nodes and / or entities.
[0039] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), AMF) and user plane entities that route or interconnect packets to external networks (e.g., serving gateway (SGW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of one or more UEs 104 served by one or more base stations 102 associated with the core network 106.
[0040] Depending on the implementation, one or more devices 116 (e.g., implemented as AUSF), and AAnF 118, AMF / SEAF 120, and / or UDM 122 may be operable to implement various aspects of network-initiated primary authentication as described herein. Any one or more devices (e.g., implemented as AUSF 116, AAnF 118, AMF / SEAF 120, or UDM 122) may be implemented in the wireless communication system 100 as any type of network device or network entity that performs a network-initiated primary authentication process. For example, AUSF 116 may transmit or send any type of primary authentication and / or reauthentication request, signaling, message, information, etc. to one or more of AAnF 118, AMF / SEAF 120, or UDM 122 via the network communication link 114. AAnF 118, AMF / SEAF 120, or UDM 122 may also transmit any authentication and / or reauthentication communications and requests 124 between any other devices. Any one or more of the AAnF 118, AMF / SEAF 120, or UDM 122 may also respond to the AUSF 116 with any type of authentication and / or reauthentication response, signaling, message, information, etc. In addition, the AAnF 118, AMF / SEAF 120, or UDM 122 may communicate any authentication and / or reauthentication communications and responses 126 between any other devices. Thus, the AUSF 116 may receive and process the authentication and / or reauthentication responses 126 to facilitate the UE and the network to communicate based on a new security context (K) derived from a successful primary authentication or reauthentication. AUSF and K SEAF ) successfully reauthenticates and establishes security.
[0041] In the 5G system, the UE's primary authentication generates the AUSF key (i.e. K AUSF The purpose of the master authentication and key agreement procedure is to enable mutual authentication between the UE and the network and to provide key material that can be used between the UE and the serving network in subsequent security procedures. Successful master authentication of the UE allows the generation of K AUSF In 5G, K AUSF is a long-term key, since the UE may be communicatively linked to the network for a long duration without refreshing K AUSF In this long duration scenario, the home network does not trigger UE re-authentication to refresh K AUSFmechanism. Furthermore, there are scenarios where security aspects related to SoR, UPU and AKMA depend on AUSF keys. In SoR and UPU, reusing the same AUSF key after a counter wrap may result in the same MAC generation at the UE, which is undesirable. Furthermore, in the AKMA feature, AKMA key refresh depends on the primary authentication, but Application Function (AF) key refresh is the responsibility of the Ua protocol and the AF key expiration time is independent of the AKMA key. This may result in the root key (i.e., the AKMA key (K AKMA ) and the AUSF key (K AUSF ))Using an application key when it is no longer in use is not an acceptable security principle. It is important to note that, as with any security key derivation, the child key lifetime should not be greater than the parent or root security key from which the child key was derived.
[0042] In the conventional method, the UDM initiates re-authentication of the UE based on the internal network function request to initiate re-authentication to refresh the UE-specific home key (K AUSF ). New master re-authentication may require certain events at the network, resulting in refreshing the latest home key K AUSF . In such a scenario, the internal network function requests the UDM to trigger the re-authentication process. Upon receiving the re-authentication request from the internal network function, the UDM will check whether to initiate a primary re-authentication of the UE based on the operator policy, or whether to reject the request. The operator policy includes details of the waiting period for new requests after the last successful authentication. If the operator policy allows, the UDM requests the AMF currently serving the UE to initiate a primary authentication of the UE. Upon receiving the request from the UDM, the AMF or SEAF initiates the primary authentication (e.g., as described in TS 33.501), which, if performed successfully, results in the generation of fresh key material in the UE and the network.
[0043] Figure 2 The diagram shows the application anchor key (K AKMA ) refreshes the example 200 of authentication and key management of conventional signaling. If the application function key (K AF ) expires, the application function (AF) 202 may use a signaling procedure to request a fresh primary authentication. In this example 200, (at step 1) the UE 104 registers with the network using a successful primary authentication, and derives the AKMA key and application function key based on existing procedures for use. When the UE requests the application function (at steps 2, 3) for access, and if K AFIf the lifetime expires or is about to expire, the application function requests the AKMA anchor function (AAnF) 204 to refresh the key K by transmitting a Naanf_AKMA_ApplicationKey_Get request (including a key refresh indicator). AF If K AF The application function rejects the UE’s access request when the lifetime expires, because the old AKMA key identifier (A-KID) is no longer valid, and it requests the UE to connect using a new A-KID. AF It cannot be used further because the K associated with A-KID AF Having been used for AF, the AAnF requests the AUSF 206 (at steps 4, 5) to generate a fresh K by sending a Nausf_AKMAKey_Get request along with the SUPI AKMA After receiving the request from the AAnF, the AUSF requests the UDM 208 (at step 6) to trigger the re-authentication process.
[0044] It is worth noting that there are limitations with respect to these conventional techniques. For example, the UDM triggers reauthentication, but in some scenarios (such as for SoR and UPU), it is the AUSF that initially knows about the counter wraparound. The AUSF is the authentication server function that handles the primary authentication, and the UDM that triggers reauthentication may lead to scenarios where the primary authentication or reauthentication is triggered without sufficient information. In addition, the application key K AF The expiration time of K is set by the AKMA Anchor Function (AAnF) without considering any factors, and K AF The expiration of K results in denial of service to the UE until a new primary authentication is successfully performed to refresh K AKMA Considering the possibility of service failure of the UE's access request, this technical solution is not optimal.
[0045] Aspects of the present disclosure include a technical solution that enables the home network to trigger a primary authentication or re-authentication, taking into account factors such as the lifetime and / or expiration time associated with the primary authentication (such as the authentication vector or AUSF key), SoR counter wraparound, and UPU counter wraparound. In addition, the described technical solution enables the AKMA key (K AKMA ) and application function key (K AF ) has a lifetime or expiration time associated with the primary authentication and AUSF key (K AUSF) lifetime or expiration time. This can prevent service failures related to application function key expiration and implicitly force the UE and the AKMA anchor function (AAnF) to use new AKMA keys associated with successful primary authentication or reauthentication after the application function key expires. Aspects of the present disclosure are related to enabling home network triggered primary authentication and / or reauthentication, and handling the lifetime and / or expiration time of related security keys. Aspects of the present disclosure are also related to setting application function key expiration while taking into account the AKMA key (K AKMA ) expiration and / or lifespan. Aspects of the present disclosure also relate to providing authentication-related lifespan and / or expiration times to AUSF and / or AMF via UDM.
[0046] In implementation, it is up to the AUSF to consider various factors to determine whether master reauthentication is required, such as Figure 3 and master reauthentication can be triggered by AUSF as shown in Phase 1 of Figure 4 The security aspects related to SoR, UPU and AKMA depend on the AUSF keys, and the home network internal network function (NF) (i.e. AUSF and / or UDM) that triggers the primary authentication should bind the lifetime or expiration time of the primary authentication or re-authentication and AUSF keys to the security usage expiration time / lifetime related to the SoR, UPU and AKMA keys. The implementation that enables the home network to trigger the primary re-authentication includes two stages, which include: Phase 1 signaling of factors considered by the AUSF to trigger the primary re-authentication, and Phase 2 signaling as a process for the AUSF to trigger the re-authentication from the home network, where the AUSF can trigger the re-authentication directly or indirectly via the UDM.
[0047] Figure 3An example 300 of phase 1 signaling of factors considered by the AUSF to trigger primary re-authentication is illustrated, which supports network-initiated primary authentication according to aspects of the present disclosure. In this example 300, the UE 104 sends a registration request (at step 1) or sends a subscription hidden identifier (SUCI) or a 5G globally unique temporary UE identity (GUTI) in any N1 message (i.e., a NAS message). The AMF / SEAF 302 may initiate authentication with the UE (at step 2) during any process of establishing a signaling connection with the UE according to the SEAF's policy. Whenever the SEAF determines to initiate authentication, the SEAF may invoke the Nausf_UEAuthentication service by sending a Nausf_UEAuthentication_Authenticate request message to the AUSF 304. The Nausf_UEAuthentication_Authenticate request may include the SUCI or SUPI (i.e., the SUPI is used if available or in the case where the AMF / SEAF receives a 5G-GUTI and the AMF has the SUPI locally stored with the UE context associated with the 5G-GUTI, where the SEAF may determine to re-authenticate the UE) and the serving network name.
[0048] The AUSF 304 transmits (e.g., sends, sends at step 3) a Nudm_UEAuthentication_Get request to the UDM 306, which may include the SUCI or SUPI and the serving network name. If a SUCI is received, the UDM performs SUCI to SUPI de-hiding (at step 4) using the Subscription Identifier De-hiding Function (SIDF). Based on the SUPI, the UDM / Authentication Credentials Repository and Processing Function (ARPF) shall select an authentication method (Extensible Authentication Protocol (EAP)-Authentication and Key Agreement (AKA) or 5G AKA or any method). Based on the selected authentication method, an Authentication Vector (AV) is generated (at step 5) (i.e., EAP-AKA' AV or 5G HE AV or any AV). The UDM, Unified Data Repository (UDR), or ARPF may include (based on operator configuration or home network operator policy) or set an expiration time / lifetime associated with the primary authentication, AV, or AUSF keys to be used by the AUSF. UDM sends a Nudm_UEAuthentication_Get response message to AUSF, which may include AV, SUPI, expiration time / lifetime indication (if available in UDM, UDR or ARPF (or) if set by UDM), AKMA indication and routing indicator (i.e., if the subscriber has an AKMA subscription, UDM includes the AKMA indication and routing indicator). The expiration time / lifetime indication provided by UDM may indicate to AUSF one or more of the following: (i) the expiration time / lifetime of the use of the AV, master authentication or AUSF key derived from the AV; (ii) triggering master authentication or re-authentication taking into account the expiration time / lifetime provided by UDM; or binding or taking into account the expiration time / lifetime provided by UDM to set the expiration time / lifetime of any security information derived from the AUSF key associated with the AV or master authentication.
[0049] The AUSF performs (at step 6) an authentication method specific message exchange (i.e., one or more message exchanges related to authentication) with the UE to perform mutual authentication related to the primary authentication. After successful mutual authentication (i.e., if the AUSF deems the primary authentication successful), the AUSF derives the AUSF key (i.e., K AUSF ) (at step 7a), and based on the home network operator policy, K AUSF If any expiry time / lifetime indication is received from UDM, or based on the Home Network Operator policy (i.e. if UDM did not provide any expiry time / lifetime in step 5), the AUSF sets the AUSF key (i.e. K AUSF If the AUSF receives an AKMA indication from the UDM, then (at step 7b) the AUSF retrieves the expiry time / lifetime of the AUSF key (i.e. KAUSF ) to export the AKMA key (i.e. K AKMA ) and A-KID. AUSF is based on the AUSF key (i.e. K AUSF ) expiration time / lifetime, set the AKMA key (i.e. K AKMA ) expiration time / lifetime. The AUSF may, based on the home network operator policy or based on the expiration time / lifetime received from the UDM (in step 5), send the AKMA key (i.e., K AKMA ) is set to the same expiry time / lifespan as the AUSF key (i.e. K AUSF ) have the same or smaller expiry time / lifespan.
[0050] The AUSF uses the Naanf_AKMA_KeyRegistration request service operation to select the AKMA anchor function (AAnF) 308 and sends the generated A-KID, K AKMA , and the AKMA key expiration time / lifetime (i.e. K AKMA The expiration time / lifetime) is sent to the AAnF together with the SUPI of the UE (at step 8a). The AAnF may store the latest information, such as the latest A-KID, K AKMA , and the AKMA key expiration time / lifetime (i.e. K AKMA expiration time / lifetime). Note that when reauthentication is run, AUSF generates a new A-KID and a new K AKMA , and set the new AKMA key expiration time / lifetime, and the newly generated A-KID, new K AKMA , and the new AKMA key expiration time / lifetime is sent to AAnF. Upon receiving the newly generated A-KID, K AKMA , and the new AKMA key expiration time / lifetime, AAnF deletes the old A-KID, K AKMA , and AKMA key expiration time / lifetime, and stores the newly generated A-KID, K AKMA , and the new AKMA key expiration time / lifetime.
[0051] AAnF stores (at step 8b) the received SUPI, A-KID, K AKMA , and the AKMA key expiration time / lifetime (i.e. K AKMAexpiration time / lifetime). AAnF sends a response to the AUSF using Naanf_AKMA_AnchorKey_Register in response to the service operation (at step 8c). Note that steps 7b to 8c may occur immediately after step 7a, or may occur at any time shortly after step 9. After a successful primary authentication, the AUSF (at step 9a) may retrieve the K AUSF Export K SEAF , and sends a Nausf_UEAuthentication_Authenticate response message to SEAF, which may include success, Kseaf (i.e. anchor key), SUPI and expiration time / lifetime (if implemented, based on home network operator policy). Only if the AMF / SEAF receives the expiration time / lifetime from the AUSF, the next step 9b is performed, wherein the AMF / SEAF stores the expiration time / lifetime locally together with the SUPI, and uses the expiration time / lifetime to invoke primary authentication or re-authentication of the UE based on the trigger (i.e. set expiration time / lifetime) received by the home network (i.e. AUSF / UDM) in step 9a. If step 9b is performed, and if the AMF (i.e. source AMF) receives the NGAP Handover Required message, the source AMF may provide the expiration time / lifetime (i.e. as related to primary authentication) to the target AMF in a Namf_Communication_CreateUEContext request message, wherein the target AMF / SEAF may store the expiration time / lifetime together with the SUPI and UE context, and the locally stored expiration time / lifetime may be used to invoke primary authentication or re-authentication of the UE.
[0052] The AMF / SEAF sends a success message (i.e., an EAP success message in the case of EAP-AKA'), a key set identifier (ngKSI) in 5G, an inter-architecture anti-bidding (ABBA) parameter to the UE in an N1 message (at step 10a), which may be a NAS security mode command or an authentication result. The UE sends a NAS security mode complete message to the AMF / SEAF (at step 10b). The AMF may send a registration accept message to the UE (at step 10c) and may receive a registration complete message from the UE. The home network (i.e., UDM) may initiate (at step 11) and run one or more SoR and / or UPU procedures with the UE, wherein the UPU and SoR procedures are protected using a protection service provided by the AUSF based on the AUSF keys. At a later point in time (at step 12), the UDM may request the AUSF associated with the Nausf_protection service of the SoR or UPU for the UE. If the AUSF determines (at step 13a) that the counter associated with the SoR or UPU wraps around or is about to wrap around, the AUSF may determine to trigger a primary authentication or re-authentication. Alternatively, if the AUSF discovers (at step 13b) that the locally available AUSF expiration time / lifetime has expired or is about to expire, the AUSF may determine to trigger a primary authentication or re-authentication.
[0053] Additionally, the following factors may be considered by the AUSF to trigger a master re-authentication, where these factors may include one or more of the following: AUSF Lifetime expiration; Authentication vector lifetime expiration; Primary authentication lifetime expiration; Redirection to roaming process, or UE parameter update process, or K-dependent AUSF Counter wrap around related to any security process as root keys; or home network operator configured or UDM provided expiry time / lifetime related to primary authentication or associated security context (such as AV or AUSF keys).
[0054] Once the AUSF determines to trigger a primary authentication or re-authentication, as referenced above Figure 3 As described in stage 1 shown in the figure, it can be implemented as follows Figure 4 Phase 2 shown and described. Note that the network function (NF) (i.e. AUSF or UDM) may store the expiry time / lifetime of the primary authentication along with the serving network name, serving NF information (i.e. AMF ID), SUPI for each access type (i.e. 3GPP access and non-3GPP access). Re-authentication associated with different serving networks of the UE may be triggered independently via the corresponding (multiple) AMF / SEAFs based on the serving network specific access type.
[0055] Figure 4An example 400 of phase 2 signaling as a process for an AUSF triggered reauthentication from a home network is illustrated, which supports network initiated primary authentication according to aspects of the present disclosure. In this example 400, the AUSF 402 may trigger authentication or reauthentication from the home network, where the AUSF may trigger the reauthentication directly or indirectly via the UDM 404. The AUSF determines (at step 1) to trigger primary authentication or reauthentication as described in phase 1. The AUSF then performs option 1 (i.e., steps 2a, 3a, 3b, 3c, and 3d) to trigger and perform primary reauthentication, or performs option 2 (i.e., steps 2b, 2c, 2d, 3a, 3b, 3c, and 3d) to trigger and perform primary reauthentication, based on the implementation.
[0056] In an implementation of Option 1, the AUSF directly triggers a primary authentication or re-authentication with the AMF / SEAF 406 serving the UE 104. The AUSF sends (at step 2a.1) a new Service Operation message to the AMF / SEAF, which may include the SUPI and an indication that a primary authentication or re-authentication is required, or is initiated by the home network. The new Service Operation message supporting triggering of a primary authentication or re-authentication may be named any of the following: Nausf_UEAuthentication_Trigger request; the existing Nausf_UE Authentication request may be reused for this purpose; Nausf_UE Re-Authentication request; Nausf_UE Re-Authentication notification; Nausf_UEAuthentication_Trigger notification; or Nausf_UE Authentication_Initiate request / notification.
[0057] The AMF / SEAF (at step 2a.2), upon receipt at step 2a.1, may send an ACK indication in a response message which may be named any of the following: Nausf_UE Authentication_Trigger response; an existing Nausf_UE authentication response which may be reused for this purpose; Nausf_UE re-authentication response; Nausf_UE re-authentication notification response or ACK; Nausf_UE Authentication_Trigger notification response or ACK; or Nausf_UEAuthentication_Initiate response or notification ACK.
[0058] The AMF / SEAF may initiate (at step 3a) an identity request / response with the UE, wherein the AMF / SEAF may send an identity request to the UE and may receive an identity response with a SUCI from the UE. The SEAF may initiate a primary authentication or re-authentication with the UE based on the indication received from the AUSF (at step 3b) (in step 2a.1). The SEAF may send a Nausf_UEAuthentication_Authenticate request message to the AUSF, which may include a SUCI or SUPI (i.e., using the SUPI if available, or using the SUCI received in step 3a) and a serving network name. The AUSF sends (at step 3c) a Nudm_UEAuthentication_Get request to the UDM, which may include a SUCI or SUPI and a serving network name. If a SUCI is received, the UDM performs (at step 3d) SUCI to SUPI de-hiding using the SIDF. Based on the SUPI, the UDM / ARPF shall select an authentication method and then perform an authentication specific message exchange with the AUSF. The AUSF and the UE may exchange authentication method specific message exchanges with the UE to perform mutual authentication. Such as reference herein Figure 3 The Phase 1 steps 5 to 10b shown and described apply. The UE and the network establish a new security context (K) derived from a successful primary authentication or re-authentication. AUSF and K SEAF ) successfully reauthenticates and establishes NAS security and AS security.
[0059] In the implementation of Option 2, the AUSF indirectly triggers the primary authentication or re-authentication with the AMF / SEAF serving the UE via the UDM. The AUSF sends a request message to the UDM (at step 2b), which may include the SUPI, the re-authentication indication, any cause value (such as K AUSF Expiration indication, SoR counter wrap indication, UPU counter wrap indication, authentication lifetime expiration indication, and / or AV lifetime expiration indication). The request message used in step 2b may include any new service operation message to support triggering primary authentication or re-authentication, and it may be named any of the following: Nudm_UEAuthentication_Trigger request; the existing Nudm_UE Authenticationget request may be reused for this purpose; Nudm_UE Re-Authentication request; Nudm_UE Re-Authentication notification; Nudm_UEAuthentication_Trigger notification; or Nudm_UEAuthentication_Initiate request / notification.
[0060] The UDM receives any of the following (at step 2b.2): a reauthentication instruction, a K AUSF Expiration indication, SoR counter wrap indication, UPU counter wrap indication, authentication lifetime expiration indication, and / or AV lifetime expiration indication are checked for validity based on the expiration time / lifetime configured locally for the AV or primary authentication or re-authentication associated with the SUPI according to the home network operator policy. If a counter wrap indication is received related to a SoR or UPU that is ongoing or needs to be sent, the UDM / UDR may store the SoR or UPU data locally until a successful primary re-authentication is completed and the SoR / UPU is re-initiated accordingly. The UDM (at step 2b.3) upon receiving step 2b.1 may send an ACK indication in a response message, where the response message may be named any of the following: Nudm_UE Authentication_Trigger Response; an existing Nudm_UE Authentication Get Response may be reused for this purpose; Nudm_UE Re-Authentication Response; Nudm_UE Re-Authentication Notification Response or ACK; Nudm_UEAuthentication_Trigger Notification Response or ACK; or Nudm_UE Authentication_Initiate Response or Notification ACK.
[0061] As alternative option A, the UDM, upon receipt (at step 2b.1), may select an authentication method based on the SUPI and generate an AV specific to the selected authentication method. Construction of Serving Network Name by UDM, UDR, or ARPF: The UDM, UDR, or ARPF may check the serving AMF / SEAF of the UE based on the SUPI and construct a serving network name for the specific AMF / SEAF. For example, it may set the service code to "5G", it may set the network identifier to the serving network identifier (SN Id) of the serving network to which the AUSF sends authentication data; and it may concatenate the service code and SN Id with a separator ":". The UDM may send Nudm_UE Authentication to the AUSF to obtain a response with the AV, expiration time / lifetime*, SUPI, AKMA indication, routing indicator, re-authentication confirmation, serving AMF / SEAF identifier (or information), and the calculated SNN. If this alternative option is implemented, steps 2d-3c may be skipped and step 3d is performed, which includes performing primary authentication based on the AV sent by the UDM (in step 2.b.2). In this case, step 3d includes the same Figure 3Operations associated with steps 6, 7a, 7b, 8a, 8b, 8c, 9, 10a, 10a, and / or 10b of the Phase 1 process shown and described.
[0062] As another alternative option B, the UDM may send a SUPI to the serving AMF and initiate a primary authentication or reauthentication indication in a Nudm_UEAuthentication_Request or Nudm_UE Authentication or Reauthentication Trigger message. The AMF / SEAF may initiate an identity request / response with the UE (at step 3a), wherein the AMF / SEAF may send an identity request to the UE and may receive an identity response with a SUCI from the UE. The SEAF may initiate a primary authentication or reauthentication with the UE based on the indication received from the UDM (at step 2c.1) (at step 3b). The SEAF may send a Nausf_UEAuthentication_Authenticate request message to the AUSF, which may include a SUCI or SUPI (i.e., use the SUPI if available, or use the SUCI received in step 3a) and a serving network name. The AUSF sends a Nudm_UEAuthentication_Get request to the UDM (at step 3c), which may include a SUCI or SUPI and a serving network name. If a SUCI is received, the UDM (at step 3d) performs SUCI to SUPI de-hiding using the SIDF. Based on SUPI, UDM / ARPF shall select an authentication method and then perform authentication specific message exchange with AUSF. AUSF and UE may exchange authentication method specific message exchange with UE to perform mutual authentication. This is such as referring to Figure 3 The steps 5 to 10 b shown and described apply here.
[0063] The UE and the network establish a new security context (K) derived from a successful primary authentication or re-authentication. AUSF and K SEAF ) successfully reauthenticates and establishes NAS security and AS security.
[0064] Figure 5An example 500 of setting the expiration time and / or lifetime of an application function key in support of a network-initiated master authentication according to aspects of the present disclosure is illustrated. In this example 500, the expiration time and / or lifetime of an AF key may be set based on the lifetime and / or expiration time provided by a home network NF (such as AUSF 502, or in turn via AUSF from UDM). The expiration time and / or lifetime of an AF key may be set based on the validity of the master authentication, AUSF key, or AKMA key, since the AF key is derived from the AKMA key, which is derived from the AUSF key following a successful authentication. The implementation may also prevent denial of service by the AAnF due to AF key expiration, wherein the implementation updates the AAnF with a new AKMA key and expiration time and / or lifetime shortly after each successful master authentication or re-authentication to be considered for any security purposes, such as AF key generation or refresh and use of the AF key (i.e., AF key expiration time).
[0065] In this example 500, the UE 104 may receive a AKMA application function from the K AUSF Generate AKMA anchor key (K AKMA ) and A-KID. When the UE initiates communication with the AKMA AF 504, it can include the derived A-KID in the application session establishment request message. The UE can derive the KID before or after sending the message. AF If the AF has no active context associated with the A-KID, then (at step 2) the AF selects the AAnF 506 and sends a Naanf_AKMA_ApplicationKey_Get request with the A-KID to the AAnF to request the KID for the UE. AF The AF also includes its identity (AF_ID) in the request. The AAnF is based on the UE-specific K identified by A-KID. AKMA The presence of the key verifies that the subscriber is authorized to use AKMA. If K is present in AAnF AKMA , then AAnF proceeds to step 3. If K does not exist in AAnF AKMA , then AAnF continues with step 4 with an error response.
[0066] If AAnF does not already have K AF , then AAnF (at step 3) from K AKMA Export the AKMA application key (K AF ). The AAnF then sets K taking into account the expiration time and / or lifetime of the locally stored AKMA key. AF The expiration time of K AFThe expiration time of the AKMA key may be less than or equal to the expiration time and / or lifetime of the AKMA key. The expiration time and / or lifetime of the AKMA key available at the AAnF may be used to define K AF The maximum lifetime of a key, where the AAnF can determine not to use or refresh the key beyond the expiration time and / or lifetime of the associated AKMA key AF (ie, the AAnF may determine that the K associated with the A-KID is to be used or refreshed only before the expiration time and / or lifetime of the associated AKMA key. AF ).
[0067] AAnF sends (at step 4) to AF a signal with SUPI, K AF , and K AF The AF sends an Application Session Establishment Response (at step 5a) to the UE. If the information in step 4 indicates a failure of the AKMA key request, the AF may reject the Application Session Establishment by including the reason for the failure. Thereafter, the UE may trigger a new Application Session Establishment Request with the latest A-KID to the AKMA AF. After successful AF key establishment, the UE may communicate with the AF (at step 5b) and use the application. At a later point in time, the following steps may be performed. When the UE requests the AF for access, if the K AF If the lifetime has expired or is about to expire (determined at step 6), the AF (step 7a) requests the AAnF to refresh the key K by sending a Naanf_AKMA_ApplicationKey_Get request (including a key refresh indicator). AF .
[0068] AAnF (step 7b) may find K AFThe lifetime expires, and the AAnF performs the following: the AAnF checks the locally available AKMA key expiration time and / or lifetime for the associated A-KID, and if the expiration time and / or lifetime have not expired, the AAnF may determine to refresh the AF key; or the AAnF checks the locally available AKMA key expiration time and / or lifetime for the associated A-KID, and if the expiration time and / or lifetime have expired, the AAnF may determine not to refresh the AF key, and determines to wait for a new AKMA key (i.e., AUSF) to be provided by the home network. If the AAnF finds that the available AKMA key expires, and it has not yet received a new AKMA key associated with the new A-KID provided by the AF, or if the AAnF receives an A-KID for which the existing AKMA key has expired, the AAnF (at step 7c) sends a Naanf_Response message to the AF, which may include a waiting time (r). The AF may use the waiting time (r) to retry the key request process with the AAnF. If the AAnF finds an AKMA key available and not expired associated with the new A-KID, the AAnF sends a Naanf_Response message to the AF, which may include the new AF key. Note that the external AF may request the AF key from the AAnF via the NEF, and in this case, steps 2, 4, 7a and 7c will be exchanged via the NEF, where the NEF will receive and forward the message exchange between the AF and the AAnF, respectively.
[0069] Figure 6 An example 600 of providing authentication-related lifetime and / or expiration time after a successful primary authentication in support of a network-initiated primary authentication according to aspects of the present disclosure is illustrated. This is an alternative method for providing authentication-related lifetime and / or expiration time by the UDM to the AUSF 602 and / or AMF 604. In this example 600, the AUSF (at step 1) notifies the UDM 606 of the result and time of the authentication process with the UE using a Nudm_UEAuthentication_ResultConfirmation request. This may include the SUPI, the timestamp of the authentication, the authentication type (e.g., EAP method or 5G-AKA), and the serving network name. The UDM may (at step 2) store the authentication status (SUPI, authentication result, timestamp, and serving network name) of the UE, and the UDM may set the expiration time (exp time) and / or lifetime of the primary authentication for the UE based on the operator local policy.
[0070] The UDM may (at step 3) reply to the AUSF with a Nudm_UEAuthentication_ResultConfirmation response, which may include an expiration time and / or lifetime (related to primary authentication), and which may be stored together with the SUPI. Upon receiving the expiration time and / or lifetime, the AUSF may, based on implementation 1, stage 2 description (i.e., option 1 (AUSF directly triggers primary authentication or re-authentication with the AMF / SEAF serving the UE), perform triggering primary authentication or re-authentication when the expiration time is about to be reached or the lifetime is about to expire), or by requesting AV for the SUPI and the serving network, and initiating an authentication request with the AMF for primary authentication.
[0071] After receiving the subsequent UE-related procedures, the UDM receives (at step 4) a Nudm_UECM_Registration_Request from the AMF, and the UDM may apply actions according to the policies of the home operator to detect and implement protection against certain types of fraud. The Nudm_UECM_Registration_Request may include the NF ID, SUPI, access type, RAT type, serving PLMN ID, and / or registration type (if the access type is 3GPP access). The UDM may then send (at step 5) a Nudm_UECM_Registration_Response to the AMF, which may include the SUPI and the expiration time and / or lifetime (related to the primary authentication). The AMF / SEAF may (at step 6) store the expiration time and / or lifetime (related to the primary authentication) locally together with the SUPI and the UE context. Taking into account the received and locally stored expiration time and / or lifetime, when the primary authentication expires, the AMF / SEAF may invoke the primary authentication or re-authentication for the UE (i.e., SUPI). The expiration time and / or lifetime provided by the home network may take precedence over the SEAF policy to invoke authentication or re-authentication. Note that the UDM may provide the expiry time and / or lifetime to the AUSF (i.e., in step 3) or to the AMF (i.e., in step 5).
[0072] Figure 7An example of a block diagram 700 of a device 702 supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated. The device 702 may be an example of a device implementing the AUSF as described herein. The device 702 may support wireless communications and / or network signaling with one or more base stations 102, UEs 104, network entities and devices, or any combination thereof. The device 702 may include components for two-way communications, including components for sending and receiving communications, such as an authentication manager 704, a processor 706, a memory 708, a receiver 710, a transmitter 712, and an I / O controller 714. These components may be coupled electronically (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).
[0073] The authentication manager 704, the receiver 710, the transmitter 712, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the authentication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may support methods for performing one or more functions described herein.
[0074] In some implementations, the authentication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some implementations, the processor 706 and a memory 708 coupled to the processor 706 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 708 by the processor 706).
[0075] Additionally or alternatively, in some implementations, the authentication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in code executed by the processor 706 (e.g., as communication management software or firmware). If implemented in code executed by the processor 706, the functionality of the authentication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supported for performing the functions described in the present disclosure).
[0076] In some implementations, the authentication manager 704 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 710, the transmitter 712, or both. For example, the authentication manager 704 may receive information from the receiver 710, send information to the transmitter 712, or be integrated with the receiver 710, the transmitter 712, or both to receive information, send information, or perform various other operations as described herein. Although the authentication manager 704 is illustrated as a separate component, in some implementations, one or more functions described with reference to the authentication manager 704 may be supported or performed by the processor 706, the memory 708, or any combination thereof. For example, the memory 708 may store code that may include instructions executable by the processor 706 to cause the device 702 to perform various aspects of the present disclosure as described herein, or the processor 706 and the memory 708 may be otherwise configured to perform or support such operations.
[0077] For example, the authentication manager 704 can support wireless communication and / or network signaling at a device (e.g., device 702, AUSF) according to examples as disclosed herein. The authentication manager 704 and / or other device components can be configured as or otherwise support an apparatus comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the device to: receive an authentication request from a security anchor function (SEAF); send a data request for authentication data to a unified data management (UDM); receive authentication data from the UDM for a primary authentication; set an expiration time for security information associated with a primary authentication success; send an authentication message including at least the security information and the expiration time to an authentication and key management (AKMA) anchor function (AAnF) for an application that registers an expiration time; and initiate re-authentication based at least in part on the expiration of the authentication information.
[0078] In addition, the apparatus (e.g., device, AUSF) includes any one or a combination of the following: the authentication information includes at least one of a roaming steering (SoR) counter wrap or a user equipment (UE) parameter update (UPU) counter wrap, and the processor is configured to cause the apparatus to: initiate re-authentication based on expiration of the SoR counter wrap or the UPU counter wrap. The authentication information includes an authentication server function (AUSF) key (K AUSF ) life, and the processor is configured so that the device: based on K AUSF The processor is configured to cause the device to initiate re-authentication based on the re-authentication policy of the home network operator. The security information includes one or more of the following: AUSF key (K AUSF ), AKMA key (KAKMA ), authentication vector, primary authentication state, or primary authentication result. The processor and transceiver are configured to cause the device to: use the authentication message as an AKMA key (K AKMA ) registration request is sent to AAnF, AKMA key (K AKMA ) The registration request includes one or more of the following: UE Subscription Permanent Identifier (SUPI), AKMA Key Identifier (A-KID), K AKMA , or K AKMA The processor and the transceiver are configured to cause the device to: send an authentication response to the SEAF, the authentication response including one or more of the following: an authentication success indication, a SUPI, an AKMA key (K AKMA ), or the expiration time of the primary authentication. The authentication data received from the UDM includes one or more of the following: an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a SUPI, an AKMA indication, or a routing indicator. The processor and the transceiver are configured to cause the device to: send an authentication trigger request to the AMF / SEAF to initiate re-authentication, the authentication trigger request including one or more of the SUPI or an indication that re-authentication is required. The processor and the transceiver are configured to cause the device to: receive an acknowledgment (ACK) from the AMF / SEAF in response to the authentication trigger request sent to the AMF / SEAF. The processor and the transceiver are configured to cause the device to: send an authentication trigger request to the UDM, the authentication trigger request including one or more of the following: the SUPI, an indication that re-authentication is required, or an indication of the reason for the authentication trigger request. The reason for the authentication trigger request includes one or more of the following: an expired AUSF key (K AUSF ), a counter wrap expiration indication, or an authentication life expiration indication. The processor and the transceiver are configured to cause the device to: receive an ACK from the UDM in response to an authentication trigger request sent to the UDM. The processor and the transceiver are configured to cause the device to: receive authentication result information from the UDM, the authentication result information including an expiration time and an authentication result confirmation.
[0079] The authentication manager 704 and / or other device components may be configured to or otherwise support components for wireless communication and / or network signaling at a device (e.g., AUSF), including receiving an authentication request from a security anchor function (SEAF); sending a data request for authentication data to a unified data management (UDM); receiving authentication data from the UDM for primary authentication; setting an expiration time for security information associated with a successful primary authentication; sending an authentication message including at least the security information and the expiration time to an authentication and key management (AKMA) anchor function (AAnF) for an application that registered an expiration time; and initiating re-authentication based at least in part on the expiration of the authentication information.
[0080] In addition, the wireless communication and / or network signaling at the device includes any one or a combination of the following: the authentication information includes at least one of a Steering of Roaming (SoR) counter wrap, or a User Equipment (UE) Parameter Update (UPU) counter wrap, and based on the expiration of the SoR counter wrap or the UPU counter wrap, initiating re-authentication. The authentication information includes an Authentication Server Function (AUSF) key (K AUSF ) lifespan, and based on K AUSF The lifetime expires, and re-authentication is initiated. Re-authentication is initiated based on the re-authentication policy of the home network operator. Security information includes one or more of the following: AUSF key (K AUSF ), AKMA key (K AKMA ), authentication vector, primary authentication state, or primary authentication result. The method also includes using the authentication message as an AKMA key (K AKMA ) registration request is sent to AAnF, the AKMA key (K AKMA ) The registration request includes one or more of the following: UE Subscription Permanent Identifier (SUPI), AKMA Key Identifier (A-KID), K AKMA , or K AKMA The method also includes sending an authentication response to SEAF, the authentication response including one or more of the following: an authentication success indication, SUPI, AKMA key (K AKMA ), or the expiration time of the primary authentication. The authentication data received from the UDM includes one or more of the following: an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a SUPI, an AKMA indication, or a routing indicator. The method also includes: sending an authentication trigger request to the AMF / SEAF to initiate re-authentication, the authentication trigger request including one or more of the SUPI or an indication that re-authentication is required. The method also includes receiving an acknowledgment (ACK) from the AMF / SEAF in response to the authentication trigger request sent to the AMF / SEAF. The method also includes: sending an authentication trigger request to the UDM, the authentication trigger request including one or more of the following: the SUPI, an indication that re-authentication is required, or an indication of the reason for the authentication trigger request. The reason for the authentication trigger request includes one or more of the following: expired AUSF key (K AUSF ), a counter wrap expiration indication, or an authentication life expiration indication. The method also includes: receiving an ACK from the UDM in response to the authentication trigger request sent to the UDM. The method also includes: receiving authentication result information from the UDM, the authentication result information including an expiration time and an authentication result confirmation.
[0081] The processor 706 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 706 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 706. The processor 706 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 708) to cause the device 702 to perform various functions of the present disclosure.
[0082] The memory 708 may include random access memory (RAM) and read-only memory (ROM). The memory 708 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 706, cause the device 702 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some implementations, the code may not be directly executed by the processor 706, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 708 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0083] I / O controller 714 can manage input and output signals for device 702. I / O controller 714 can also manage peripheral devices that are not integrated into device 702. In some implementations, I / O controller 714 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 714 can use an operating system, such as or another known operating system. In some implementations, I / O controller 714 may be implemented as part of a processor, such as processor 706. In some implementations, a user may interact with device 702 via I / O controller 714, or via hardware components controlled by I / O controller 714.
[0084] In some implementations, the device 702 may include a single antenna 716. However, in some other implementations, the device 702 may have more than one antenna 716, which may be capable of simultaneously sending or receiving multiple wireless transmissions. The receiver 710 and the transmitter 712 may communicate bidirectionally via one or more antennas 716 (wired or wireless links as described herein). For example, the receiver 710 and the transmitter 712 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets to provide the modulated packets to one or more antennas 716 for transmission, and to demodulate packets received from one or more antennas 716.
[0085] Figure 8 An example of a block diagram 800 of a device 802 supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated. The device 802 may be an example of a device implementing one or more of AAnF, AMF / SEAF, or UDM as described herein. The device 802 may support wireless communications and / or network signaling with one or more base stations 102, other UEs 104, core network devices and functions (e.g., core network 106), or any combination thereof. The device 802 may include components for bidirectional communication, including components for sending and receiving communications, such as an authentication manager 804, a processor 806, a memory 808, a receiver 810, a transmitter 812, and an I / O controller 814. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).
[0086] The authentication manager 804, the receiver 810, the transmitter 812, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the authentication manager 804, the receiver 810, the transmitter 812, or various combinations thereof, or components thereof may support methods for performing one or more functions described herein.
[0087] In some implementations, the authentication manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure. In some implementations, the processor 806 and a memory 808 coupled to the processor 806 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 808 by the processor 806).
[0088] Additionally or alternatively, in some implementations, the authentication manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be implemented in code executed by the processor 806 (e.g., as communication management software or firmware). If implemented in code executed by the processor 806, the functionality of the authentication manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supported for performing the functions described in the present disclosure).
[0089] In some implementations, the authentication manager 804 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 810, the transmitter 812, or both. For example, the authentication manager 804 may receive information from the receiver 810, send information to the transmitter 812, or be integrated with the receiver 810, the transmitter 812, or both to receive information, send information, or perform various other operations as described herein. Although the authentication manager 804 is illustrated as a separate component, in some implementations, one or more functions described with reference to the authentication manager 804 may be supported or performed by the processor 806, the memory 808, or any combination thereof. For example, the memory 808 may store code that may include instructions executable by the processor 806 to cause the device 802 to perform various aspects of the present disclosure as described herein, or the processor 806 and the memory 808 may be configured in other ways to perform or support such operations.
[0090] For example, the authentication manager 804 can support wireless communication and / or network signaling at a device (e.g., device 802, AAnF) according to examples as disclosed herein. The authentication manager 804 and / or other device components can be configured as, or otherwise support, an apparatus comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: receive an authentication message from an authentication server function (AUSF), the authentication message including authentication information including at least security information and an expiration time; maintain the security information and the expiration time, the security information including at least an application authentication and key management (AKMA) key (K AKMA ); and sending a registration response to AUSF as a response to the AKMA key (K AKMA ) is registered.
[0091] In addition, the apparatus (eg, device, AAnF) includes any one or a combination of the following: receiving an authentication message from the AUSF as an AKMA key (K AKMA ) registration request, the AKMA key (K AKMA ) The registration request includes one or more of the following: UE Subscription Permanent Identifier (SUPI), AKMA Key Identifier (A-KID), K AKMA or K AKMA The processor is configured to cause the device to: AKMA ) Export the application function (AF) key (K AF ), and based on K AKMA One of the expiration time or lifetime, set K AF The processor and the transceiver are configured to cause the device to: receive from an application function (AF) a request for an AKMA key (K AKMA ) of a key request; and based at least in part on determining an AKMA key (K AKMA ) has expired, sending a waiting time response to the AF. The processor and the transceiver are configured to cause the device to: receive a request for an AKMA key (K AKMA ), the key request including an AKMA key identifier (A-KID); determining whether a stored AKMA key expiration time or lifetime has expired for the associated A-KID; and one of the following: if the stored AKMA key expiration time or lifetime has not expired, determining to refresh the AF key; or if the stored AKMA key expiration time or lifetime has expired, determining not to refresh the AF key and waiting for a new AKMA key to be provided by the AUSF.
[0092] The authentication manager 804 and / or other device components may be configured to, or otherwise support components for wireless communication and / or network signaling at a device (e.g., AAnF), including: receiving an authentication message from an authentication server function (AUSF), the authentication message including authentication information including at least security information and an expiration time; maintaining the security information and the expiration time, the security information including at least an application authentication and key management (AKMA) key (K AKMA ); and sending a registration response to AUSF as a response to the AKMA key (K AKMA ) is registered.
[0093] In addition, wireless communication and / or network signaling at the device includes any one or a combination of the following: receiving an authentication message from the AUSF as an AKMA key (K AKMA ) registration request, the AKMA key (K AKMA ) The registration request includes one or more of the following: UE Subscription Permanent Identifier (SUPI), AKMA Key Identifier (A-KID), K AKMA or K AKMA The method also includes obtaining an expiration time from an AKMA key (K AKMA ) Export the application function (AF) key (K AF ), and based on K AKMA One of the expiration time or lifetime, set K AF The method also includes receiving from an application function (AF) a request for an AKMA key (K AKMA ) of a key request; and determining, at least in part, an AKMA key (K AKMA ) has expired and sends a waiting time response to the AF. The method also includes: receiving from the AF a request for an AKMA key (K AKMA ), the key request including an AKMA key identifier (A-KID); determining whether a stored AKMA key expiration time or lifetime has expired for the associated A-KID; and one of the following: if the stored AKMA key expiration time or lifetime has not expired, determining to refresh the AF key; or if the stored AKMA key expiration time or lifetime has expired, determining not to refresh the AF key and waiting for a new AKMA key to be provided by the AUSF.
[0094] In addition, the authentication manager 804 and / or other device components may be configured to, or otherwise support, an apparatus comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: receive a registration request from a user equipment (UE); send an authentication request to an authentication server function (AUSF); receive an authentication response from the AUSF, the authentication response comprising an indication of successful authentication and at least one of an expiration time or a lifetime of the authentication duration; and maintain at least one expiration time or lifetime of the authentication duration together with a UE subscription permanent identifier (SUPI) configured to trigger reauthentication.
[0095] In addition, the apparatus (e.g., device, AMF / SEAF) includes any one or a combination of the following: the processor and the transceiver are configured to enable the apparatus to: store at least one expiration time or lifetime of the authentication duration; and initiate triggering re-authentication of the UE based at least in part on the at least one expiration time or lifetime of the authentication duration. The processor and the transceiver are configured to enable the apparatus to: in response to receiving a handover required message, send at least one expiration time or lifetime of the authentication duration to a target access and mobility management function (AMF), and the target AMF is configured to store at least one expiration time or lifetime of the authentication duration together with the SUPI and the UE context so that it can be used to invoke re-authentication. The processor and the transceiver are configured to enable the apparatus to: receive an authentication trigger request from the AUSF to initiate re-authentication, the authentication trigger request including one or more of the following: a SUPI or an indication that re-authentication is required; and in response to the authentication trigger request, send an acknowledgment (ACK) to the AUSF.
[0096] The authentication manager 804 and / or other device components may be configured to, or otherwise support components for wireless communication and / or network signaling at a device (e.g., AMF / SEAF), including: receiving a registration request from a user equipment (UE); sending an authentication request to an authentication server function (AUSF); receiving an authentication response from the AUSF, the authentication response including an indication of successful authentication and at least one of an expiration time or a lifetime of the authentication duration; and maintaining at least one expiration time or lifetime of the authentication duration together with a UE subscription permanent identifier (SUPI) configured to trigger reauthentication.
[0097] In addition, the wireless communication and / or network signaling at the device includes any one or a combination of the following: The method also includes: storing at least one expiration time or lifetime of the authentication duration; and initiating a trigger for reauthentication of the UE based at least in part on at least one expiration time or lifetime of the authentication duration. The method also includes: in response to receiving a handover required message, sending at least one expiration time or lifetime of the authentication duration to a target access and mobility management function (AMF), the target AMF being configured to store at least one expiration time or lifetime of the authentication duration together with the SUPI and the UE context so that it can be used to invoke reauthentication. The method also includes: receiving an authentication trigger request from the AUSF to initiate reauthentication, the authentication trigger request including one or more of the following: a SUPI or an indication that reauthentication is required; and in response to the authentication trigger request, sending an acknowledgment (ACK) to the AUSF.
[0098] In addition, the authentication manager 804 and / or other device components can be configured to, or otherwise support, an apparatus comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: receive a data request for authentication data from an authentication server function (AUSF); send the authentication data to the AUSF for primary authentication; receive an authentication trigger request from the AUSF, the authentication trigger request comprising one or more of: a user equipment (UE) subscription permanent identifier (SUPI), an indication that reauthentication is required, or an indication of a reason for the authentication trigger request; and, in response to the authentication trigger request, send an ACK to the AUSF.
[0099] In addition, the apparatus (e.g., device, UDM) includes any one or a combination of the following: the authentication data sent to the AUSF includes one or more of the following: an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a SUPI, an AKMA indication, or a routing indicator. The reasons for the authentication trigger request include: an expired AUSF key (K AUSF), a counter wrap expiration indication, or an authentication life expiration indication. The processor is configured to cause the device to: determine whether the authentication trigger request is valid based at least in part on an expiration indication of at least one of an expiration time or a life duration as configured for the AV. The processor is configured to cause the device to: determine whether the authentication trigger request is valid based at least in part on an expiration indication of at least one of an expiration time, a life duration of a primary authentication associated with the SUPI, or a life duration of a primary re-authentication associated with the SUPI. The processor is configured to cause the device to: store at least one of roaming steering (SoR) data or user equipment (UE) parameter update (UPU) data until a successful primary re-authentication is completed, and re-initiate at least one of the SoR or UPU. The processor is configured to cause the device to: store the authentication state of the UE, and set the authentication expiration time of the UE. The processor and the transceiver are configured to cause the device to: send an authentication result confirmation response to the AUSF, the authentication result confirmation response including at least one of the expiration time or the life duration associated with the primary authentication. The processor and transceiver are configured to cause the apparatus to: send a registration response result to an access and mobility management function (AMF), the registration response result including at least one of an expiration time or a lifetime duration associated with the primary authentication.
[0100] The authentication manager 804 and / or other device components may be configured to or otherwise support components for wireless communication and / or network signaling at a device (e.g., UDM), including: receiving a data request for authentication data from an authentication server function (AUSF); sending the authentication data to the AUSF for primary authentication; receiving an authentication trigger request from the AUSF, the authentication trigger request including one or more of: a user equipment (UE) subscription permanent identifier (SUPI), an indication that reauthentication is required, or an indication of a reason for the authentication trigger request; and sending an acknowledgment (ACK) to the AUSF in response to the authentication trigger request.
[0101] In addition, the wireless communication and / or network signaling at the device includes any one or a combination of the following: the authentication data sent to the AUSF includes one or more of the following: an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a SUPI, an AKMA indication, or a routing indicator. The reasons for the authentication trigger request include: an expired AUSF key (K AUSF), a counter wrap expiration indication, or an authentication life expiration indication. The method further includes determining whether the authentication trigger request is valid based at least in part on an expiration indication of at least one of an expiration time or a life duration as configured for the AV. The method further includes determining whether the authentication trigger request is valid based at least in part on an expiration indication of at least one of an expiration time, a life duration of a primary authentication associated with the SUPI, or a life duration of a primary re-authentication associated with the SUPI. The method further includes storing at least one of Steering of Roaming (SoR) data or User Equipment (UE) Parameter Update (UPU) data until a successful primary re-authentication is completed and at least one of the SoR or UPU is re-initiated. The method further includes storing an authentication state of the UE and setting an authentication expiration time of the UE. The method further includes sending an authentication result confirmation response to the AUSF, the authentication result confirmation response including at least one of the expiration time or the life duration associated with the primary authentication. The method further includes sending a registration response result to an access and mobility management function (AMF), the registration response result including at least one of the expiration time or the life duration associated with the primary authentication.
[0102] The processor 806 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 806 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 806. The processor 806 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 808) to cause the device 802 to perform various functions of the present disclosure.
[0103] The memory 808 may include random access memory (RAM) and read-only memory (ROM). The memory 808 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 806, cause the device 802 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some implementations, the code may not be directly executed by the processor 806, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 808 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0104] The I / O controller 814 can manage input and output signals for the device 802. The I / O controller 814 can also manage peripheral devices that are not integrated into the device 802. In some implementations, the I / O controller 814 can represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 814 can use an operating system, such as or another known operating system. In some implementations, the I / O controller 814 may be implemented as part of a processor, such as the processor 806. In some implementations, a user may interact with the device 802 via the I / O controller 814 or via hardware components controlled by the I / O controller 814.
[0105] In some implementations, the device 802 may include a single antenna 816. However, in some other implementations, the device 802 may have more than one antenna 816, which may be capable of simultaneously sending or receiving multiple wireless transmissions. The receiver 810 and the transmitter 812 may communicate bidirectionally via one or more antennas 816 (wired or wireless links as described herein). For example, the receiver 810 and the transmitter 812 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets, provide the modulated packets to one or more antennas 816 for transmission, and demodulate packets received from one or more antennas 816.
[0106] Fig. 9 A flow chart of a method 900 for supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated. The operations of the method 900 may be performed by, for example, a reference Figures 1 to 8 The described device or its components implemented as a device of AUSF are implemented and executed. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.
[0107] At 902, the method may include receiving an authentication request from SEAF. The operations of 902 may be performed according to examples as described herein. In some implementations, aspects of the operations of 902 may be performed as described in reference to Figure 1 The described device performs.
[0108] At 904, the method may include sending a data request for authentication data to the UDM. The operations of 904 may be performed according to examples as described herein. In some implementations, aspects of the operations of 904 may be performed as described in reference to Figure 1 The described device performs.
[0109] At 906, the method may include receiving authentication data from the UDM for primary authentication. The operations of 906 may be performed according to examples as described herein. In some implementations, aspects of the operations of 906 may be performed as described in reference to Figure 1 The described device performs.
[0110] At 908, the method may include setting an expiration time for security information associated with a successful primary authentication. The operations of 908 may be performed according to examples as described herein. In some implementations, aspects of the operations of 908 may be performed as described in reference to Figure 1 The described device performs.
[0111] At 910, the method may include: sending an authentication message including authentication information including security information and an expiration time to the AAnF registering the expiration time. The operations of 910 may be performed according to examples as described herein. In some implementations, aspects of the operations of 910 may be performed as described in reference to Figure 1 The described device performs.
[0112] At 912, the method may include initiating re-authentication based on expiration of the authentication information. The operations of 912 may be performed according to examples as described herein. In some implementations, aspects of the operations of 912 may be performed as described in reference to Figure 1 The described device performs.
[0113] Fig.10 1000 is a flowchart of a method 1000 for supporting network-initiated primary authentication according to aspects of the present disclosure. The operations of the method 1000 may be performed by, for example, Figures 1 to 8 The described device or its components implemented as a device of AUSF are implemented and executed. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.
[0114] At 1002, the method may include: using the authentication message as an AKMA key (K AKMA ) registration request is sent to AAnF, the AKMA key (K AKMA ) The registration request includes: SUPI, AKMA key identifier (A-KID), K AKMA , and / or K AKMA The operation of 1002 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1002 may be performed as described in reference to Figure 1 The described device performs.
[0115] At 1004, the method may include: sending an authentication response to SEAF, the authentication response including: an indication of successful authentication, SUPI, AKMA key (K AKMA ), and / or the expiration time of the primary authentication. The operation of 1004 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1004 may be performed as described in reference to Figure 1 The described device performs.
[0116] At 1006, the method may include: sending an authentication trigger request to the AMF / SEAF to initiate re-authentication, the authentication trigger request including: the SUPI, and / or an indication that re-authentication is required. The operation of 1006 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1006 may be performed as described in reference to Figure 1 The described device performs.
[0117] At 1008, the method may include: receiving an ACK from the AMF / SEAF in response to the authentication trigger request sent to the AMF / SEAF. The operations of 1008 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1008 may be performed as described in reference to Figure 1 The described device performs.
[0118] At 1010, the method may include: sending an authentication trigger request to the UDM, the authentication trigger request including the SUPI, an indication that re-authentication is required, and / or an indication of a reason for the authentication trigger request. The operations of 1010 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1010 may be performed as described in reference to Figure 1 The described device performs.
[0119] At 1012, the method may include: receiving an ACK from the UDM in response to the authentication trigger request sent to the UDM. The operations of 1012 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1012 may be performed as described in reference to Figure 1 The described device performs.
[0120] At 1014, the method may include: receiving authentication result information from the UDM, the authentication result information including an expiration time and an authentication result confirmation. The operations of 1014 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1014 may be performed as described in reference to Figure 1 The described device performs.
[0121] Fig.11 100 is a flowchart of a method 1100 for supporting network-initiated primary authentication according to aspects of the present disclosure. The operations of the method 1100 may be performed by, for example, Figures 1 to 8 The described device or its components implemented as a device of AAnF are implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.
[0122] At 1102, the method may include: receiving an authentication message from the AUSF, the authentication message including authentication information including at least security information and an expiration time. The operations of 1102 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1102 may be performed as described in reference to Figure 1 The described device performs.
[0123] At 1104, the method may include maintaining security information and an expiration time, the security information including an AKMA key (K AKMA ). The operations of 1104 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1104 may be performed as described in reference Figure 1 The described device performs.
[0124] At 1106, the method may include sending a registration response to the AUSF as a response to the AKMA key (K AKMA ) is registered. The operation of 1106 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1106 may be performed as described in reference to Figure 1 The described device performs.
[0125] Fig.12 1 is a flow chart of a method 1200 for supporting network-initiated primary authentication according to aspects of the present disclosure. The operations of the method 1200 may be performed by, for example, Figures 1 to 8 The described device or its components implemented as a device of AAnF are implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.
[0126] At 1202, the method may include: AKMA )Export AF key (K AF ), and based on K AKMA One of the expiration time or lifetime, set K AF The operation of 1202 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1202 may be performed as described in reference to Figure 1 The described device performs.
[0127] At 1204, the method may include receiving from the AF a request for an AKMA key (K AKMA ) key request. The operation of 1204 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1204 may be performed as described in reference Figure 1 The described device performs.
[0128] At 1206, the method may include: determining an AKMA key (K AKMA ) has expired, a waiting time response is sent to the AF. The operation of 1206 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1206 may be performed as described in reference to Figure 1 The described device performs.
[0129] At 1208, the method may include receiving a key request for an AKMA key (KAKMA) from the AF, the key request including the A-KID. The operations of 1208 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1208 may be performed as described in reference to Figure 1 The described device performs.
[0130] At 1210, the method may include determining whether a stored AKMA key expiration time or lifetime has expired for the associated A-KID. The operations of 1210 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1210 may be performed as described in reference to Figure 1 The described device performs.
[0131] At 1212, the method may include determining to refresh the AF key if the stored AKMA key expiration time or lifetime has not expired. The operations of 1212 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1212 may be performed as described in reference to Figure 1 The described device performs.
[0132] At 1214, the method may include: if the stored AKMA key expiration time or lifetime has expired, determining not to refresh the AF key and waiting for a new AKMA key to be provided by the AUSF. The operation of 1214 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1214 may be described with reference to Figure 1 The device described performs the following.
[0133] Fig.13 1300 is a flowchart of a method 1300 for supporting network-initiated primary authentication according to aspects of the present disclosure. The operations of the method 1300 may be performed by, for example, Figures 1 to 8The described device or its components implemented as a device of AMF / SEAF are implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.
[0134] At 1302, the method may include: receiving a registration request from a UE. The operations of 1302 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1302 may be performed as described in reference to Figure 1 The described device performs.
[0135] At 1304, the method may include sending an authentication request to the AUSF. The operations of 1304 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1304 may be performed as described in reference to Figure 1 The described device performs.
[0136] At 1306, the method may include receiving an authentication response from the AUSF, the authentication response including an indication of successful authentication, and an expiration time and / or lifetime of the authentication duration. The operations of 1306 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1306 may be performed as described in reference to Figure 1 The described device performs.
[0137] At 1308, the method may include maintaining an expiration time and / or lifetime of the authentication duration with the SUPI configured to trigger re-authentication. The operations of 1308 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1308 may be performed as described in reference to Figure 1 The described device performs.
[0138] Fig.14 1400 is a flowchart of a method 1400 for supporting network-initiated primary authentication according to aspects of the present disclosure. The operations of the method 1400 may be performed by, for example, Figures 1 to 8 The described device or its components implemented as a device of AMF / SEAF are implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.
[0139] At 1402, the method may include storing an expiration time and / or lifetime of the authentication duration. The operations of 1402 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1402 may be performed as described in reference to Figure 1 The described device performs.
[0140] At 1404, the method may include initiating a trigger for re-authentication of the UE based on the expiration time and / or lifetime of the authentication duration. The operations of 1404 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1404 may be performed as described in reference to Figure 1 The described device performs.
[0141] At 1406, the method may include: in response to receiving the handover required message, sending the expiration time and / or life of the authentication duration to the target AMF, the target AMF being configured to store the expiration time and / or life of the authentication duration together with the SUPI and the UE context so as to be available for invoking re-authentication. The operations of 1406 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1406 may be performed as described in reference to Figure 1 The described device performs.
[0142] At 1408, the method may include receiving an authentication trigger request from the AUSF to initiate re-authentication, the authentication trigger request including the SUPI, and / or an indication that re-authentication is required. The operations of 1408 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1408 may be performed as described in reference to Figure 1 The described device performs.
[0143] At 1410, the method may include: sending an ACK to the AUSF in response to the authentication trigger request. The operations of 1410 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1410 may be performed as described in reference to Figure 1 The described device performs.
[0144] Fig.15 1500 is a flowchart of a method 1500 for supporting network-initiated primary authentication according to aspects of the present disclosure. The operations of the method 1500 may be performed by, for example, Figures 1 to 8 The described device or its components implemented as a UDM device implement and execute. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.
[0145] At 1502, the method may include receiving a data request for authentication data from the AUSF. The operations of 1502 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1502 may be performed as described in reference to Figure 1 The described device performs.
[0146] At 1504, the method may include sending authentication data to the AUSF for primary authentication. The operations of 1504 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1504 may be performed as described in reference to Figure 1 The described device performs.
[0147] At 1506, the method may include receiving an authentication trigger request from the AUSF, the authentication trigger request including the SUPI, an indication that re-authentication is required, and / or an indication of a reason for the authentication trigger request. The operations of 1506 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1506 may be performed as described in reference to Figure 1 The described device performs.
[0148] At 1508, the method may include: sending an ACK to the AUSF in response to the authentication trigger request. The operations of 1508 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1508 may be performed as described in reference to Figure 1 The described device performs.
[0149] Fig.16 A flow chart of a method 1600 for supporting network-initiated primary authentication according to aspects of the present disclosure is illustrated. The operations of the method 1600 may be performed by, for example, Figures 1 to 8 The described device or its components implemented as a UDM device implement and execute. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.
[0150] At 1602, the method may include determining whether the authentication trigger request is valid based on an expiration indication such as an expiration time or a lifetime duration configured for the AV. The operations of 1602 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1602 may be performed as described in reference to Figure 1 The described device performs.
[0151] At 1604, the method may include determining whether the authentication trigger request is valid based on an expiration time, a lifespan duration of a primary authentication associated with the SUPI, and / or an expiration indication of a lifespan duration of a primary re-authentication associated with the SUPI. The operations of 1604 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1604 may be performed as described in reference to Figure 1 The described device performs.
[0152] At 1606, the method may include storing the SoR data and / or UPU data until a successful master re-authentication is completed and the SoR and / or UPU is re-initiated. The operations of 1606 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1606 may be performed as described in reference to Figure 1 The described device performs.
[0153] At 1608, the method may include storing the authentication state of the UE and setting the authentication expiration time of the UE. The operations of 1608 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1608 may be performed as described in reference to Figure 1 The described device performs.
[0154] At 1610, the method may include sending an authentication result confirmation response to the AUSF, the authentication result confirmation response including an expiration time or lifetime associated with the primary authentication. The operations of 1610 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1610 may be performed as described in reference to Figure 1 The described device performs.
[0155] At 1612, the method may include sending a registration response result to the AMF, the registration response result including an expiration time and / or lifetime associated with the primary authentication. The operations of 1612 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1612 may be performed as described in reference to Figure 1 The described device performs.
[0156] It should be noted that the methods described herein describe possible implementations, and operations and steps may be rearranged or otherwise modified, and other implementations are also possible. In addition, two or more aspects from the methods may be combined. The order of the methods described should not be considered as limiting, and any number or combination of the method operations described may be performed in any order to perform a method or an alternative method.
[0157] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.
[0158] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located at various locations, including being distributed so that parts of the functions are implemented at different physical locations.
[0159] Computer-readable media include both non-transient computer storage media and communication media, including any medium that is convenient for transferring a computer program from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or can be used to carry or store the required program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor. Any other non-transient medium.
[0160] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are all included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. The above combinations are also included in the scope of computer-readable media.
[0161] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, for example, a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Similarly, a list of one or more of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein (including in the claims), a "set" may include one or more elements.
[0162] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "in favor of other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be implemented without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0163] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. It will be apparent to one of ordinary skill in the art that various modifications to the present disclosure are present, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A device comprising: Transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: Set the expiration time of the security information associated with the primary authentication success; receiving an authentication trigger request with cause information from a network function; Determining to initiate re-authentication based on at least one of the expiration of the authentication information or the reason information; as well as An authentication message is sent to at least one of a mobility management function (AMF) or a security anchor function (SEAF) to initiate the re-authentication.
2. The apparatus of claim 1 , wherein the network function is an authentication server function (AUSF), and the cause information comprises at least one of: a Steering of Roaming (SoR) counter wraps, an SoR counter is about to wrap indication, a User Equipment (UE) Parameter Update (UPU) counter wraps, or a UPU counter is about to wrap indication, and the processor is configured to cause the apparatus to: initiate the reauthentication based on the expiration of the SoR counter wrap or the UPU counter wrap.
3. The device according to claim 2, wherein: The processor and the transceiver are configured to cause the apparatus to: receive the authentication trigger request from the AUSF, the authentication trigger request comprising one or more of: a subscription permanent identifier (SUPI), an indication that the re-authentication is required, or an indication of a reason for the authentication trigger request; and The reason for the authentication trigger request includes one or more of the following: expired AUSF key (K AUSF ), a SoR counter wrap indication, an indication that the SoR counter is about to wrap, a UPU counter wrap indication, an indication that the UPU counter is about to wrap, or an authentication lifetime expiration indication. 4 . The apparatus according to claim 1 , wherein the processor is configured to cause the apparatus to initiate the reauthentication based on a reauthentication policy or an authentication policy of a home network operator.
5. The apparatus of claim 1, wherein the security information comprises one or more of the following: an authentication server function (AUSF) key (K AUSF ), Application Authentication and Key Management (AKMA) Key (K AKMA ), authentication vector, primary authentication state, or primary authentication result.
6. The apparatus of claim 1, wherein the authentication data provided from a unified data management (UDM) to an authentication server function (AUSF) comprises one or more of: an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a subscription permanent identifier (SUPI), an application key management (AKMA) indication, or a routing indicator.
7. The apparatus according to claim 1, wherein the processor and the transceiver are configured to cause the apparatus to: send an authentication request to the AMF or SEAF to initiate the re-authentication, the authentication request comprising one or more of the following: a subscription permanent identifier (SUPI), or an indication that the re-authentication is required.
8. The apparatus according to claim 1, wherein the processor and the transceiver are configured to cause the apparatus to: receive an acknowledgment (ACK) from the AMF or SEAF in response to an authentication trigger request sent to the AMF or SEAF.
9. The apparatus of claim 8, wherein the ACK indicates one of an authentication success or an authentication failure.
10. The apparatus of claim 1, wherein the processor and the transceiver are configured to cause the apparatus to: receive an acknowledgement (ACK) from a unified data management (UDM) in response to the authentication trigger request.
11. An apparatus comprising: Transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: receiving an authentication message from an authentication server function (AUSF), the authentication message comprising authentication information including at least security information and an expiration time; Maintain the security information and the expiration time, the security information including at least an application authentication and key management (AKMA) key (K AKMA ); as well as Send a registration response to the AUSF as a response to the AKMA key (K AKMA ) is registered.
12. The apparatus according to claim 11, wherein the authentication message is provided as an AKMA key (K AKMA ) a registration request is received from the AUSF, the AKMA key (K AKMA ) The registration request includes one or more of the following: a user equipment (UE) subscription permanent identifier (SUPI), an AKMA key identifier (A-KID), the K AKMA , or the K AKMA The expiration time.
13. The apparatus according to claim 11, wherein the processor is configured to cause the apparatus to: AKMA ) Export the application function (AF) key (K AF ), and based on the expiration time or the K AKMA One of the lifetimes, set K AF Expiration time.
14. The apparatus of claim 11, wherein the processor and the transceiver are configured such that the apparatus: Receives from the application function (AF) the key for the AKMA (K AKMA ) key request; and Based at least in part on determining the AKMA key (K AKMA ) has expired, sending a waiting time response to the AF.
15. An apparatus comprising: Transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: receiving an authentication request from a unified data management (UDM) to initiate re-authentication, the authentication message including one or more of: a subscription permanent identifier (SUPI), or an indication that re-authentication is required; and In response to the authentication response, an acknowledgement (ACK) is sent to the UDM. The apparatus of claim 15 , wherein the ACK indicates one of an authentication success or an authentication failure.
17. An apparatus comprising: Transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: Set the expiration time of the security information associated with the primary authentication success; as well as An authentication message including at least the security information and the authentication information of the expiration time is sent to an authentication and key management (AKMA) anchor function (AAnF) of the application registered with the expiration time, wherein the authentication message is used as an AKMA key (K AKMA ) registration request is sent to the AAnF, the AKMA key (K AKMA ) The registration request includes one or more of the following: User Equipment (UE) Subscription Permanent Identifier (SUPI), AKMA Key Identifier (A-KID), K AKMA , or the K AKMA The expiry time of as well as Based at least in part on the expiration of the authentication information, a determination is made to initiate re-authentication.
18. The apparatus of claim 17, wherein the authentication information comprises at least one of: a Steering of Roaming (SoR) counter wrap, an SoR counter wrap indication, a User Equipment (UE) Parameter Update (UPU) counter wrap, or an UPU counter wrap indication, and the processor is configured to cause the apparatus to: initiate the re-authentication based on expiration of the SoR counter wrap or the UPU counter wrap.
19. The apparatus of claim 17, wherein the security information comprises one or more of the following: an authentication server function (AUSF) key (K AUSF ), the K AKMA , authentication vector, primary authentication state, or primary authentication result.
20. An apparatus according to claim 17, wherein the processor and the transceiver are configured to enable the apparatus to: receive authentication data for the primary authentication, the authentication data comprising one or more of the following: an authentication vector (AV), an expiration time of the AV, an expiration time of the primary authentication, a subscription permanent identifier (SUPI), an AKMA indication, or a routing indicator.
