Application function key derivation and refresh

Abstract

This invention provides apparatus, systems, and methods for generating and renewing Application Function (AF) keys. A User Equipment (UE) can communicate with the Application Function (AF) via a Radio Access Network (RAN) using a first AF key and determine that the first AF key has expired. The UE can derive a second AF key based at least on an Application Authentication and Key Management Architecture (AKMA) anchor key (KAKMA) and counter parameters, and use the second AF key to communicate with the AF via the RAN. At least one of the UE, the AF, and / or the AKMA anchor function (AAnF) can be configured to monitor the expiration of the first AF key based on its associated lifetime. The first AF key and the second AF key can be derived using a key derivation function including at least one variable parameter.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for application function (AF) key generation and AF key renewal. Background Technology

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these functions.

[0003] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators worldwide, providing their user base with mobile broadband data and high-speed internet access. LTE defines multiple downlink (DL) physical channels, classified as transport or control channels, to carry blocks of information received from Medium Access Control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL).

[0004] For example, LTE defines the Physical Downlink Shared Channel (PDSCH) as the DL transport channel. The PDSCH is the primary data bearer channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to MAC Protocol Data Units (PDUs), which are passed from the MAC layer to the physical (PHY) layer once every transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as System Information Blocks (SIBs) and paging messages.

[0005] For example, LTE defines the Physical Downlink Control Channel (PDCCH) as the DL Control Channel, which carries the UE's resource allocation contained in the Downlink Control Information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each consisting of nine groups of four resource elements called Resource Element Groups (REGs). The PDCCH uses Quadrature Phase Shift Keying (QPSK) modulation, where four QPSK symbols are mapped to each REG. Furthermore, depending on channel conditions, 1, 2, 4, or 8 CCEs can be used to ensure sufficient robustness.

[0006] Additionally, LTE defines the Physical Uplink Shared Channel (PUSCH) as a UL channel shared by all devices (User Equipment, UE) in a radio cell to transmit user data to the network. Scheduling of all UEs is under the control of the LTE base station (Enhanced Node B or eNB). The eNB uses uplink scheduling clearance (DCI format 0) to inform the UE of resource block (RB) allocations and the modulation and coding schemes to be used. The PUSCH typically supports QPSK and Quadrature Amplitude Modulation (QAM). In addition to user data, the PUSCH carries any control information required for decoding, such as transport format indicators and multiple-input multiple-output (MIMO) parameters. Control data is multiplexed with information data before the Digital Fourier Transform (DFT) expansion.

[0007] The next telecommunications standard proposed to surpass the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called 5G mobile network or 5G radio system, or simply 5G (for 5G New Radio, it is also called 5G-NR, or simply NR). 5G-NR offers higher capacity for higher density mobile broadband users, while supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, compared to current LTE, 5G-NR allows for more flexible UE scheduling. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0008] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for application function (AF) key generation and AF key renewal.

[0009] In some implementations, the User Equipment (UE) may be configured to communicate with the Application Function (AF) via the Radio Access Network (RAN) using a first AF key and determine that the first AF key has expired. The UE may be configured to derive a second AF key based at least on an Application Authentication and Key Management Architecture (AKMA) anchor key (KAKMA) and counter parameters, and use the second AF key to communicate with the AF via the RAN. In some implementations, the UE may be configured to determine that the first AF key has expired based on receiving a first message from the AKMA Anchor Function (AAnF) of the core network indicating that the first AF key has expired. In some implementations, the first message may include counter parameters, and the counter parameters may be incremented each time a new AF key associated with the first AF key is derived. In some implementations, either the AAnF or the AF may be responsible for monitoring the expiration of the first AF key. In some implementations, the UE may be responsible for monitoring the expiration of the first AF key. In such implementations, the UE may be configured to determine that the first AF key has expired based on monitoring the lifetime of the first AF key and determining that the lifetime of the first AF key has expired. In some implementations, the Application Function (AF) may be configured to communicate with the User Equipment (UE) via the Radio Access Network (RAN) using a first AF key and determine that the first AF key has expired. The AF may be configured to notify the AKMA Anchor Function (AAnF) of the core network that the first AF key has expired. The AF may be configured to receive a second AF key derived by the AAnF based at least on the Application Authentication and Key Management Architecture (AKMA) Anchor Key (KAKMA) and counter parameters. In some implementations, the AF may also receive the lifetime associated with the second AF key from the AAnF. The AF may be configured to communicate with the UE via the RAN using the second AF key. The first AF key has expired. The AAnF may be configured to derive the second AF key based at least on the Application Authentication and Key Management Architecture (AKMA) Anchor Key (KAKMA) and counter parameters, and transmit the second AF key to the AF via the RAN. In some implementations, the AAnF may be configured to determine that the first AF key has expired based on receiving a first message from the UE indicating that the first AF key has expired. In some implementations, the first message may include a counter parameter, and the counter parameter may be incremented each time a new AF key associated with the first AF key is derived. In some implementations, either the UE or the AF may be responsible for monitoring the expiration of the first AF key. In some implementations, the AAnF may be responsible for monitoring the expiration of the first AF key. In such implementations, the AAnF may be configured to determine that the first AF key has expired based on monitoring the lifetime of the first AF key and determining that the first AF key has expired.

[0010] The techniques described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of the following computing devices: unmanned aerial vehicles (UAVs), unmanned controllers (UACs), base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, automobiles and / or motor vehicles, and various other computing devices.

[0011] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0012] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0013] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.

[0014] Figure 1B Examples of base stations (BS) and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.

[0015] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) according to some implementation schemes is shown.

[0016] Figure 3 An exemplary block diagram of a BS according to some implementation schemes is shown.

[0017] Figure 4 An exemplary block diagram of a server according to some implementation schemes is shown.

[0018] Figure 5A Example block diagrams of a UE according to some implementation schemes are shown.

[0019] Figure 5B An exemplary block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0020] Figure 6A An example of the connection between the EPC network, the LTE base station (eNB), and the 5G NR base station (gNB) is shown.

[0021] Figure 6B An example of the protocol stack used for eNB and gNB is shown.

[0022] Figure 7A Examples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) access to 5G CN with non-3GPP (e.g., non-cellular) access.

[0023] Figure 7B Examples of 5G network architectures according to some implementation schemes are shown, which combine dual 3GPP (e.g., LTE and 5G NR) access to 5G CN as well as non-3GPP access.

[0024] Figure 8 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0025] Figure 9 An exemplary architecture of the AKMA system according to some implementation schemes is shown.

[0026] Figure 10 Examples of signaling derived for AF keys according to some implementation schemes are shown.

[0027] Figures 11A to 11F Examples of parameters for the input string used in the key derivation function, according to some implementation schemes, are shown.

[0028] Figures 12 to 14 An example of signaling for generating a new AF key when the current AF key expires, according to some implementation schemes, is shown.

[0029] Figure 15A and Figure 15B An example of signaling for generating a new AF key when determining to change the current AF key is shown, according to some implementation schemes.

[0030] Figures 16 to 18 A block diagram illustrating an example of a method for an AF key renewal process according to some implementation schemes is shown.

[0031] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0032] acronym

[0033] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0034] 3GPP: Third Generation Partnership Project

[0035] TS: Technical Specification

[0036] RAN: Radio Access Network

[0037] • RAT: Radio Access Technology

[0038] UE: User Equipment

[0039] RF: Radio Frequency

[0040] ·BS: Base Station

[0041] DL: Downlink

[0042] ·UL: Uplink

[0043] LTE: Long Term Evolution

[0044] NR: New Radio

[0045] ·5GS: 5G system

[0046] ·5GMM: 5GS Mobility Management

[0047] ·5GC: 5G Core Network

[0048] ·IE: Information Elements

[0049] ·AKMA: Application Authentication and Key Management Architecture

[0050] • AAnF: AKMA Anchor Point Function

[0051] •AF: Application Function

[0052] • AMF: Access and Mobility Management Functions

[0053] • AUSF: Authentication Server Function

[0054] •NEF: Network Exposure Function

[0055] the term

[0056] The following is a glossary of terms used in this disclosure:

[0057] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0058] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0059] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0060] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0061] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on AndroidTM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM This includes laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transported by (or with) a user and is capable of wireless communication.

[0062] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0063] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0064] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0065] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.

[0066] Wi-Fi—The term “Wi-Fi” encompasses the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are distinct from cellular networks.

[0067] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0068] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0069] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0070] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0071] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0072] The headings used herein are for organizational purposes only and are not intended to limit the scope of the specification. As used throughout this application, the word “may” is used in an permissive sense (meaning possibility) rather than a mandatory sense (meaning necessity). The word “comprising” indicates an open relationship and therefore means including but not limited to. Similarly, the word “having” also indicates an open relationship and therefore indicates having but not limited to. The terms “first,” “second,” “third,” etc., as used herein are used as labels for nouns that follow them and, unless expressly indicated otherwise, do not imply any kind of ordering (e.g., spatial, temporal, logical, etc.). For example, unless otherwise specified, “a third component electrically connected to the module substrate” does not exclude the possibility that a “fourth component electrically connected to the module substrate” is connected before the third component. Similarly, unless otherwise specified, a “second” feature does not require a “first” feature to be implemented before the “second” feature.

[0073] Figure 1A and Figure 1B Communication system

[0074] Figure 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0075] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0076] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0077] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0078] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0079] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-106N and similar devices over a geographical area via one or more cellular communication standards.

[0080] Therefore, although base station 102A can act as the "serving cell" for UEs 106A-106N as shown in Figure 1, each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-102N and / or any other base station), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. Such cells may include "macro" cells, "micro" cells, "pecimen" cells and / or any other cells of various other granularities providing service area size. For example, base stations 102A to 102B shown in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0081] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0082] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0083] Figure 1BUser equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0084] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.

[0085] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0086] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0087] Figure 2 Access point diagram

[0088] Figure 2 An exemplary block diagram of access point (AP) 112 is shown. Note that... Figure 2 The block diagram of the AP is only one example of a possible system. As shown, AP 112 may include a processor 204 capable of executing program instructions for AP 112. Processor 204 may also be (directly or indirectly) coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate these addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0089] AP 112 may include at least one network port 270. This network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices, such as UE 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or a corporate network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to an additional network, such as the Internet.

[0090] AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with UE 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in the case of a small cell where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, LTE, LTE-A Advanced, GSM, WCDMA, CDMA2000, etc.

[0091] In some implementations, as further described below, AP 112 can be configured to perform methods for application function (AF) key generation and AF key renewal as further described herein.

[0092] Figure 3 Block diagram of a base station

[0093] Figure 3 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0094] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above in Figure 1 and... Figure 2 The telephone network described herein includes multiple devices such as UE device 106.

[0095] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).

[0096] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or a “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0097] Base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0098] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0099] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 404 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, and 470, the processor 404 of base station 102 may be configured to implement or support some or all of the implementations of the features described herein.

[0100] Furthermore, as described herein, processor 404 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0101] Additionally, as described herein, the radio component 430 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 430. Therefore, the radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 430.

[0102] Figure 4 Server block diagram

[0103] Figure 4 An exemplary block diagram of server 104 according to some implementation schemes is shown. It should be noted that... Figure 4 The base station is merely one example of a possible server. As shown, server 104 may include processor 444 capable of executing program instructions for server 104. Processor 444 may also be coupled to memory management unit (MMU) 474, which may be configured to receive addresses from processor 444 and translate those addresses into locations in memory (e.g., memory 464 and read-only memory (ROM) 454) or to other circuitry or devices.

[0104] Base station 104 can be configured to provide network access functionality to multiple devices, such as base station 102 and / or UE device 106, for example, as further described herein.

[0105] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0106] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 444 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 444 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or configured as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 454, 464, and / or 474, processor 444 of server 104 may be configured to implement or support some or all of the features described herein.

[0107] Furthermore, as described herein, processor 444 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 444. Therefore, processor 444 may include one or more integrated circuits (ICs) configured to perform the functions of processor 444. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 444.

[0108] Figure 5A : UE block diagram

[0109] Figure 5A An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 5AThe block diagram of the communication device is merely one example of possible communication devices. According to embodiments, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. As shown, communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, this set of components 300 may be implemented as individual components or groups of components for various purposes. This set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of communication device 106.

[0110] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 329 (e.g., Bluetooth). TM (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0111] Cellular communication circuitry 330 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 335 and 336 shown. Short-to-medium-range wireless communication circuitry 329 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 337 and 338 shown. Alternatively, short-to-medium-range wireless communication circuitry 329 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 337 and 338, or as an alternative, to antennas 335 and 336. Short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0112] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.

[0113] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.

[0114] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general-purpose integrated circuit cards) 345. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 345, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 310 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 310 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0115] As described above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to remain in standby while awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

[0116] As shown in the figure, the SOC 300 may include a processor 302 and a display circuit 304. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 360. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as the display circuit 304, short-to-medium range wireless communication circuitry 329, cellular communication circuitry 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0117] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for application function (AF) key generation and AF key renewal as further described herein.

[0118] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or otherwise), processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), in conjunction with one or more of other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0119] Furthermore, as described in this invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0120] Further, as described herein, the cellular communication circuit 330 and the short-to-medium-range wireless communication circuit 329 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-to-medium-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 329.

[0121] Figure 5B Block diagram of cellular communication circuit

[0122] Figure 5BAn exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5B The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of these devices.

[0123] Cellular communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 5A Antennas 335a-335b and 336 are shown in the diagram. In some embodiments, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as shown... Figure 5B As shown, the cellular communication circuit 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0124] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0125] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0126] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0127] In some implementations, the cellular communication circuit 330 may be configured to perform methods for application function (AF) key generation and AF key renewal as further described herein.

[0128] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0129] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0130] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0131] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0132] Figure 6: 5G NR architecture using LTE

[0133] In some specific implementations, fifth-generation (5G) wireless communication will initially be deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been designated as part of the initial NR deployment. Therefore, as... Figures 6A to 6B As shown, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). Furthermore, eNB 602 can communicate with the 5G NR base station (e.g., gNB 604) and can transfer data between the core network 600 and gNB 604. Therefore, the EPC network 600 can be used (or reused), and gNB 604 can serve as additional capacity for user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Therefore, LTE can be used to establish connections to the network, and NR can be used for data services.

[0134] Figure 6BThe proposed protocol stack for eNB 602 and gNB 604 is illustrated. As shown, eNB 602 may include a Media Access Control (MAC) layer 632 that interfacing with Radio Link Control (RLC) layers 622a-622b. RLC layer 622a may also interfacing with Packet Data Convergence Protocol (PDCP) layer 612a, and RLC layer 622b may interfacing with PDCP layer 612b. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 612a may interfacing with EPC network 600 via Primary Cell Group (MCG) bearer, while PDCP layer 612b may interfacing with EPC network 600 via decoupling bearer.

[0135] Additionally, as shown in the figure, gNB 604 may include a MAC layer 634 that interfacing with RLC layers 624a-624b. RLC layer 624a may interfacing with the PDCP layer 612b of eNB 602 via the X2 interface for information exchange and / or coordination (e.g., UE scheduling) between eNB 602 and gNB 604. Furthermore, RLC layer 624b may interfacing with PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 614 may interfacing with EPC network 600 via a secondary cell group (SCG) bearer. Therefore, eNB 602 can be considered the primary node (MeNB), and gNB 604 can be considered the secondary node (SgNB). In some cases, it may be required that the UE maintain connectivity with both the MeNB and the SgNB. In such cases, the MeNB can be used to maintain the Radio Resource Control (RRC) connection with the EPC, while the SgNB can be used for capacity (e.g., additional downlink and / or uplink throughput).

[0136] Figure 7A , Figure 7B and Figure 8 5G Core Network Architecture—Interoperability with Wi-Fi

[0137] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architecture / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architecture / protocols such as Wi-Fi connections). Figure 7AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, e.g., gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP Interoperability Function (N3IWF) 702 network entity. N3IWF may include a connection to the 5G CN's core access and mobility management function (AMF) 704. AMF 704 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. As shown, AMF 704 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 720, Short Message Service Function (SMSF) 722, Application Function (AF) 724, Unified Data Management (UDM) 726, Policy Control Function (PCF) 728, and / or Authentication Server Function (AUSF) 730). It should be noted that these functional entities may also be supported by the 5G CN's Session Management Functions (SMF) 706a and SMF 706b. AMF 706 may connect to (or communicate with) SMF 706a. In some implementations, such functional entities may reside on, and / or be performed by, or supported by, one or more servers 104 located within the RAN and / or core network. Furthermore, gNB 604 may communicate with (or connect to) the User Plane Function (UPF) 708a, which may also communicate with SMF 706a. Similarly, the N3IWF 702 can communicate with the UPF 708b, which in turn can communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0138] Figure 7BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. The N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of 5G MM functionality associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via base station 602) and a 5G network (e.g., via base station 604). As shown, base station 602 can have connections to both Mobility Management Entity (MME) 742 and Service Gateway (SGW) 744. MME 742 can have connections to both SGW 744 and AMF 704. Furthermore, SGW 744 can have connections to both SMF 706a and UPF 708a. As shown, AMF 704 can include one or more functional entities associated with the 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). Note that UDM 726 can also include Home Subscriber Server (HSS) functionality, and PCF can also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 706a and SMF 706b. The AMF 706 can connect to (or communicate with) the SMF 706a. In some implementations, such functional entities may reside on, and / or be performed by, or supported by, one or more servers 104 located within the RAN and / or core network. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 708a, which can also communicate with the SMF 706a. Similarly, the N3IWF 702 can communicate with the UPF 708b, which can also communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0139] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, including, for example, mechanisms for application function (AF) key generation and AF key renewal as further described herein.

[0140] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some implementation schemes is shown. As described above, Figure 8 The baseband processor architecture 800 described herein can be implemented on one or more radio components (e.g., radio components 329 and / or 330) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access stratum (AS) 870. The 5G NAS 820 may include communication connections with a 5G AS 840 and a non-3GPP AS 830, as well as a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with both access strata. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional AS 850 may include functional entities such as Short Message Service (SMS) entity 852, Evolved Packet System (EPS) Session Management (ESM) entity 854, Session Management (SM) entity 856, EPS Mobility Management (EMM) entity 858, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 860. Furthermore, the traditional AS 870 may include functional entities such as LTE AS 872, UMTS AS 874, and / or GSM / GPRS 876.

[0141] Therefore, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0142] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for application function (AF) key generation and AF key renewal, as further described herein.

[0143] Figure 9 AKMA System Architecture

[0144] Figure 9 An exemplary architecture of an AKMA system according to some implementation schemes is shown. As shown, UE 106 can maintain connectivity to Radio Access Network (RAN) 101 and core network functions such as Application Function (AF) 724 and Access and Mobility Management Function (AMF) 704. RAN 101 can implement any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Furthermore, RAN 101 can provide connectivity to the core network, such as Network 100. As shown, RAN 101 can also maintain connectivity with AMF 704. AMF 704 and AF 724 can also maintain connectivity with each other and with other core network functions, such as Network Open Function (NEF) 942, AKMA Anchor Function (AAnF) 940, and Authentication Server Function (AUSF) 730, which can interconnect with each other. AAnF 940 can reside in the UE 106's local Public Land Mobile Network (HPLMN) and can generate (or derive) keys to be used between UE 106 and AF 724. Furthermore, AAnF 940 can maintain the UE AKMA context to be used in subsequent requests. Additionally, AAnF 940 can enable AKMA Anchor Key (KAKMA) derivation for AKMA services. It should be noted that in some implementations, UE 106 may have successfully registered to the 5G core before initiating AKMA services. In some implementations, NEF 942 can identify AAnF 940, and AF 724 can request AF keys from AAnF 940 using the AKMA key identifier.

[0145] In some implementations, one or more of AMF 704, AF 724, AUSF 730, AAnF 940, and / or NEF 942 may reside on and / or be executed on one or more servers 104. Additionally, in various implementations, one or more of the aforementioned functional entities of the AKMA system may be configured to perform methods for application function (AF) key generation and AF key renewal, as further described herein.

[0146] AKMA K AF Derivation and Refresh

[0147] Application Authentication and Key Management (AKMA) is an authentication and key distribution service where access to an application server is based on a user's cellular subscription. AKMA can support authentication and key management aspects for both applications and 3GPP services. In current specific implementations of AKMA, the following signaling framework has been specified: AKMA keys (e.g., K...) have been generated in the UE and Authentication Server Function (AUSF). AKMA (KAKMA and / or K_AKMA) and associated K AKMA The Application Function (AF) key is generated (or derived) after the identifier (ID). However, the current implementation described by 3GPP TS 33.535 V0.3.0 does not address the actual derivation of the AF key (except for specifying that key derivation for AKMA will be performed using the key derivation function specified in Appendix B.2.0 of 3GPP TS 33.220 V16.0 and the construction specification of input string S and input key), nor does the current implementation address the renewal of the AF key upon expiration.

[0148] The embodiments described herein provide systems, methods, and mechanisms for application function (AF) key generation and AF key renewal. In some embodiments, at least one input to a key derivation function, such as that specified in 3GPP TS 33.220, may be a dynamic value. In some embodiments, at least one of the P0 parameter and / or P1 parameter may have a dynamic value. In some embodiments, the value of the input to the key derivation function may be based on a counter. In some embodiments, the counter may be incremented each time a key for a particular AF is generated. In some embodiments, the AF may be responsible for monitoring the expiration of the AF key. In such embodiments, the AF may notify the Application Authentication Function (AAnF) of the expiration, and the AAnF may then generate a new AF key. In some embodiments, the AAnF may be responsible for monitoring both the expiration of the AF key and the generation of a new AF key. In some embodiments, the UE may be responsible for monitoring the expiration of the AF key. In such embodiments, the UE may notify the AAnF of the expiration, and the AAnF may then generate a new AF key.

[0149] For example, Figure 10 Examples of signaling for AF key derivation according to some implementation schemes are shown. Among other things, Figure 10 The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0150] At point 1002, UE 106 can exchange signaling with AUSF 730 and / or AAnF 940 to authenticate UE 106 and derive (and / or establish) an AKMA key (e.g., KAKMA) and / or an AKMA key identifier (KAKMA ID). Once the KAKMA is derived (and / or established), UE 106 can initiate communication with an AKMA AF such as AF 724. Therefore, UE 106 can send an Application Session Establishment Request message 1004 to AF 724. The Application Session Establishment Request message 1004 may include the KAKMA ID. AF 724 can determine whether an active context associated with the KAKMA ID exists. In response to determining that no active context is associated with the KAKMA ID, AF 724 can send a Key Request message 1006 to AAnF 940. The Key Request message 1006 may include the KAKMA ID and an ID associated with AF 724 (e.g., AF ID). AAnF 940 can determine whether it can provide service to AF 724 by checking the AF ID. In response to determining that it can provide service to AF 724, AAnF 940 can determine whether it has a UE-specific KAKMA identified by the KAKMA ID. In response to determining that it does not have a UE-specific KAKMA identified by the KAKMA ID, AAnF 940 can send an AKMA key request message 1008 to AUSF 730. The AKMA key request message 1008 may include the KAKMA ID. AUSF 730 can then send an AKMA key response message 1010 to AAnF 940. The AKMA key response message 1010 may include the KAKMA ID.

[0151] At position 1012, AAnF 940 can derive the AF key (e.g., K) from (e.g., at least in part based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of the AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include a string with the following characteristics: Figures 11A to 11F The parameter is shown with the indicated value. For example, as... Figures 11A to 11F As shown, the input string (e.g., "S") may include FC parameters that can be defined by the network (e.g., by network standards such as 3GPP standards). Additionally, the input string may include parameters L0 and L1 that define and / or indicate the lengths of the associated parameters P0 and P1. In some implementations, such as Figure 11A As shown, P0 can be a constant value, such as the value associated with AF 724 (e.g., as...). Figure 11B (as shown) and / or the value associated with the AF key ID (e.g., as shown) Figure 11C (As shown). In such implementations, P1 can have variable values, such as... Figures 11A to 11C The counter value shown (e.g., COUNT). In some implementations, such as Figure 11D As shown, P1 can be a constant value, such as the value associated with AF 724 (e.g., as shown in the image). Figure 11E (as shown) and / or the value associated with the AF key ID (e.g., as shown) Figure 11F (As shown). In such implementations, P0 can have variable values, such as... Figures 11D to 11F The counter value shown (e.g., COUNT).

[0152] Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some implementations, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some implementations, the variable value can be based on a counter (e.g., COUNT). In some implementations, the counter can be incremented each time the AAnF 940 generates an AF key. In some implementations, the increment value can be 1. In other implementations, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0153] Once the AF key has been derived, the AANF can send a key response message 1014 to the AF 724. The key response message may include the AF key and its associated lifetime. In some implementations, the lifetime may be approximately minutes, hours, days, and / or weeks. In some implementations, the AF key may expire once the time period specified by the lifetime has expired. In some implementations, the lifetime may be specified by a standard. In some implementations, the lifetime may be associated with and / or specified by the AF 724. In other words, the AANF 940 can determine the lifetime of the AF key based on at least one of the following: a reference to a standard, a time period associated with a specific AF, a time period associated with a specific type of AF, and / or a time period associated with a specific category of AF. The AF 724 can then send an application session establishment response message 1016 to the UE 106.

[0154] As noted above, when an AF key is generated (derived), there may be a lifetime assigned to the AF key (and / or associated with it). Therefore, when the lifetime expires, a new AF key can be generated. Figures 12 to 14 An example of signaling for generating a new AF key (e.g., AF key renewal) when the current AF key expires, according to some implementation schemes, is shown.

[0155] For example, Figure 12 An example of signaling for an AF key renewal (or refresh) process initiated by an AF such as AF 724, according to some implementation schemes, is shown. Among other devices, Figure 12 The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0156] As shown in the figure, once it has been, for example, as referenced above... Figure 10 By deriving the AF key, an application session can be established between UE 106 and AF 724 at point 1300. AF 724 can monitor the lifetime of the AF key. At point 1202, AF 724 can detect (e.g., determine) that the lifetime of the AF key has expired. In other words, AF 724 can determine that the amount of time (and / or period) during which the AF key was valid has passed (and / or expired). In response to determining that the lifetime of the AF key has expired, AF 724 can send a key refresh request message 1204 to AAnF 940. In some implementations, the key refresh request message 1204 may include the expired AF key and the KAKMA ID and AF ID associated with the expired AF key.

[0157] At position 1206, AAnF 940 can derive a new AF key. In some implementations, AAnF 940 can also delete expired AF keys. In some implementations, AAnF 940 can identify AF 724 using one or more of the KAKMA ID and / or AF ID. Additionally, AAnF 940 can use expired AF keys to identify AF keys to be deleted at AAnF 940. In some implementations, AAnF 940 can derive AF keys (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0158] Once a new AF key has been derived (and / or generated), AAnF 940 can send an AF key refresh notification message 1208 to UE 106 and a key response message 1210 to AF 724. In some embodiments, the AF key refresh notification message 1208 may include a counter variable, such as the COUNT parameter as described herein. In some embodiments, the key response message 1210 may include the new AF key and its associated lifetime.

[0159] At 1212, the UE can derive a new AF key based on KAKMA and a counter variable provided by AAnF 940. In some implementations, the UE 106 can derive the AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0160] For example, Figure 13 An example of signaling for an AF key renewal (or refresh) process initiated by AAnF, such as AAnF 940, according to some implementation schemes is shown. Among other devices, Figure 13 The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0161] As shown in the figure, once it has been, for example, as referenced above... Figure 10 By deriving the AF key, an application session can be established between UE 106 and AF 724 at point 1300. AAnF 940 can monitor the lifetime of the AF key. At point 1302, AAnF 940 can detect (e.g., determine) the expiration of the AF key's lifetime. In other words, AAnF 940 can determine that the amount of time (and / or period) during which the AF key was valid has passed (and / or expired).

[0162] At 1306, in response to determining that the AF key's lifetime has expired, AAnF 940 can derive a new AF key. In some implementations, AAnF 940 can also delete the expired AF key. In some implementations, AAnF 940 can identify AF 724 using one or more of the KAKMA ID and / or AF ID. Additionally, AAnF 940 can use the expired AF key to identify the AF key to be deleted at AAnF 940. In some implementations, AAnF 940 can derive an AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF(K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0163] Once a new AF key has been derived (and / or generated), AAnF 940 can send an AF key refresh notification message 1308 to UE 106 and a refresh notification message 1310 to AF 724. In some embodiments, the AF key refresh notification message 1308 may include a counter variable, such as the COUNT parameter as described herein. In some embodiments, the key refresh notification message 1310 may include the new AF key and its associated lifetime.

[0164] At 1312, the UE can derive a new AF key based on KAKMA and a counter variable provided by AAnF 940. In some implementations, the UE 106 can derive the AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11FThe parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0165] For example, Figure 14 An example of signaling for an AF key renewal (or refresh) procedure initiated by a UE such as UE 106 according to some implementation schemes is shown. Among other devices, Figure 14 The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0166] As shown in the figure, once it has been, for example, as referenced above... Figure 10 By deriving the AF key, an application session can be established between UE 106 and AF 724 at point 1400. UE 106 can monitor the lifetime of the AF key. At point 1402, UE 106 can detect (e.g., determine) that the AF key's lifetime has expired. In other words, UE 106 can determine that the amount of time (and / or period) during which the AF key was valid has passed (and / or expired).

[0167] At 1404, in response to determining that the AF key's lifetime has expired, UE 106 can derive a new AF key. In some implementations, UE 106 can identify AF 724 using one or more of the KAKMA ID and / or AF ID. In some implementations, UE 106 can derive the AF key (e.g., K...) from (e.g., at least in part based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11FThe parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the UE 106 generates an AF key. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0168] Once a new AF key has been derived (and / or generated), UE 106 can send an AF key refresh notification message 1406 to AAnF 940. In some implementations, the AF key refresh notification message 1406 may include a counter variable, such as the COUNT parameter as described herein.

[0169] At 1408, AAnF 940 can derive a new AF key based on KAKMA and a counter variable provided by UE 106. In some implementations, AAnF 940 can also delete expired AF keys. In some implementations, AAnF 940 can identify AF 724 using one or more of the KAKMA ID and / or AF ID. Additionally, AAnF 940 can use expired AF keys to identify AF keys to be deleted at AAnF 940. In some implementations, AAnF 940 can derive an AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown with respect to the values. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and an AF key can be generated from the AKMA key using the KDF function as described herein. In some implementations, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some implementations, the variable value can be based on a counter (e.g., COUNT).

[0170] Once a new AF key has been derived (and / or generated), the AAnF 940 can send an AF key refresh notification message 1410 via AF 724. In some implementations, the AF key refresh notification message 1410 may include the new AF key and its associated lifetime.

[0171] In some implementations, the expiration of the AF key's lifetime can be triggered for reasons unrelated to the expiration of a time period (associated with its lifetime). For example, the AF key may become corrupted, such as being leaked. In other words, the AF (such as AF 724) and / or the UE (such as UE 106) may determine that the AF key used for communication between the AF and the UE has become corrupted and / or has been leaked to the other party (e.g., a third party has become aware of the AF key). In some embodiments, the AF key refresh process can be initiated when the AF / UE determines that the AF key is no longer valid (e.g., because the AF key has become corrupted, because the time period associated with the AF key has expired, and / or because of various other reasons, such as AF key revocation (e.g., one of the AF / UE revoks the AF key)).

[0172] For example, Figure 15A Examples of signaling are shown for an AF key renewal (or refresh) process initiated by an AF such as AF 724 when determining to update and / or refresh the AF key for various reasons, according to some implementation schemes. Among other things, Figure 15A The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0173] As shown in the figure, once it has been, for example, as referenced above... Figure 10 By deriving the AF key, an application session can be established between UE 106 and AF 724 at point 1500. AAnF 940 can monitor the lifetime of the AF key. However, at point 1502, AF 724 can detect that the AF key needs to be refreshed and / or renewed, for example, because the AF key is compromised (e.g., a party / device other than UE 106 and / or AF 724 already knows and / or understands the AF key) and / or because the UE has determined (and / or decided) to revoke the AF key. For example, AF 724 can detect that the AF key has been shared (and / or leaked) to another device in the radio access network (e.g., another UE) and determine / determine that the AF key is compromised.

[0174] In response to determining that the AF key is corrupted, AF 724 may send a key refresh request message 1504 to AAnF 940. In some implementations, the key refresh request message 1504 may include the expired AF key and the KAKMA ID and AF ID associated with the expired AF key.

[0175] At 1506, AAnF 940 can detect (e.g., determine) the expiration of the AF key's lifetime, for example, based on receiving a key refresh request message 1504 from AF 724.

[0176] At 1508, in response to determining that the AF key's lifetime has expired, AAnF 940 can derive a new AF key. In some implementations, AAnF 940 can also delete the expired AF key. In some implementations, AAnF 940 can identify AF 724 using one or more of the KAKMA ID and / or AF ID. Additionally, AAnF 940 can use the expired AF key to identify the AF key to be deleted at AAnF 940. In some implementations, AAnF 940 can derive an AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0177] Once a new AF key has been derived (and / or generated), AAnF 940 can send an AF key refresh notification message 1510 to UE 106 and a refresh notification message 1512 to AF 724. In some embodiments, the AF key refresh notification message 1510 may include a counter variable, such as a COUNT parameter as described herein. In some embodiments, the key refresh notification message 1512 may include the new AF key and its associated lifetime.

[0178] At 1514, the UE can derive a new AF key based on KAKMA and a counter variable provided by AAnF 940. In some implementations, the UE 106 can derive the AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0179] For example, Figure 15B Examples of signaling are shown for an AF key renewal (or refresh) process initiated by a UE such as UE 106 when determining to update and / or refresh the AF key for various reasons, according to some implementation schemes. Among other things, Figure 15B The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0180] As shown in the figure, once it has been, for example, as referenced above... Figure 10By deriving the AF key, an application session can be established between UE 106 and AF 724 at point 1520. AAnF 940 can monitor the lifetime of the AF key. However, at point 1522, UE 106 can detect that the AF key needs to be refreshed and / or renewed, for example, because the AF key is corrupted (e.g., a party / device other than UE 106 and / or AF 724 already knows and / or understands the AF key) and / or because the UE has determined (and / or decided) to revoke the AF key. For example, UE 106 can detect that the AF key has been shared (and / or leaked) to another device in the radio access network (e.g., another UE) and determine / confirm that the AF key is corrupted.

[0181] In response to determining that the AF key is corrupted, UE 106 may send a key refresh request message 1524 to AAnF 940. In some implementations, the key refresh request message 1524 may include the expired AF key and the KAKMA ID and AF ID associated with the expired AF key.

[0182] At 1526, AAnF 940 can detect (e.g., determine) the expiration of the AF key's lifetime, for example, based on receiving a key refresh request message 1524 from UE 106.

[0183] At point 1528, in response to determining that the AF key's lifetime has expired, AAnF 940 can derive a new AF key. In some implementations, AAnF 940 can also delete the expired AF key. In some implementations, AAnF 940 can identify AF 724 using one or more of the KAKMA ID and / or AF ID. Additionally, AAnF 940 can use the expired AF key to identify the AF key to be deleted at AAnF 940. In some implementations, AAnF 940 can derive an AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11FThe parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0184] Once a new AF key has been derived (and / or generated), AAnF 940 can send an AF key refresh notification message 1530 to UE 106 and a refresh notification message 1532 to AF 724. In some embodiments, the AF key refresh notification message 1530 may include a counter variable, such as a COUNT parameter as described herein. In some embodiments, the key refresh notification message 1532 may include the new AF key and its associated lifetime.

[0185] At position 1534, the UE can derive a new AF key based on KAKMA and a counter variable provided by AAnF 940. In some implementations, the UE 106 can derive the AF key (e.g., K...) from (e.g., at least partially based on) KAKMA. AF (K_AF and / or KAF). In some implementations, key derivation of a new AF key can be performed using a key derivation function (KDF) as specified in 3GPP TS 33.220. In some implementations, the input string may include, as described above, a string with the following characteristics: Figures 11A to 11F The parameters are shown in the diagram. Furthermore, the input key to the KDF can be an AKMA key (KAKMA), and the AF key can be generated from the AKMA key using the KDF function as described herein. In some embodiments, as described above, one of the input parameters P0 and P1 can be variable (e.g., dynamic). In some embodiments, the variable value can be based on a counter (e.g., COUNT). In some embodiments, the counter can be incremented each time the AF key is generated by the AAnF 940. In some embodiments, the increment value can be 1. In other embodiments, the increment value can be generated, specified by a standard, and / or some other constant and / or derivable value.

[0186] Figure 16 A block diagram illustrating an example method for an Application Function (AF) key renewal process according to some implementation schemes is shown. Among other things, Figure 16 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0187] At 1602, an application function (e.g., such as AF 724) can communicate with a UE (e.g., such as UE 106) via a radio access network (e.g., such as RAN 101). In some embodiments, the first AF key may have already been obtained from a source such as the one referenced above. Figure 10 The AF key derivation process is described above. In some embodiments, the first AF key may have been derived from an AKMA anchor function (AAnF) such as AAnF 940 of the core network (e.g., such as network 100). In some embodiments, the first AF key may be associated with (and / or have) a lifetime. In some embodiments, the lifetime may include the duration from the date the first AF key is derived to be valid. In some embodiments, the duration may be at least one of approximately several minutes, several hours, several days, several weeks, and / or several months.

[0188] At point 1604, the AF can determine that the first AF key has expired. In some embodiments, determining that the first AF key has expired may include: the AF monitoring the lifetime of the first AF key and determining that the first AF key has expired. In some embodiments, determining that the first AF key has expired may include: the AF determining that the AF key has been changed. For example, in some embodiments, the AF can determine that the first AF key has been compromised (e.g., intentionally and / or unintentionally shared with another device in the radio access network). In some embodiments, the AF can determine that the first AF key should be revoked.

[0189] At point 1606, the AF can notify the AAnF in the core network that the first AF key has expired. In some implementations, the notification may be an AF key refresh request message. In some implementations, the notification may include one or more of the KAKMA identifier (ID), AF ID, or the first AF key.

[0190] At position 1608, the AF can receive a second AF key from the AAnF. In some implementations, the AAnF can be based on the reference above. Figure 10The derivation process is used to derive the second AF key. For example, in some embodiments, deriving the second AF key may include: AAnF using a Key Derivation Function (KDF) as specified in the 3GPP standard. In some embodiments, the input string to the KDF may include a counter parameter. In some embodiments, the counter parameter may be one of the P0 parameter or the P1 parameter of the input string. In such embodiments, the other of the P0 parameter or the P1 parameter may be a fixed value. For example, when the counter parameter is the P0 parameter of the input string, the P1 parameter of the input string may be one of the first AF key identifier (ID) or AF. As another example, when the counter parameter is the P1 parameter of the input string, the P0 parameter of the input string may be one of the first AF key identifier (ID) or AF.

[0191] At 1610, the AF can use the second AF key to communicate with the UE via the RAN.

[0192] Figure 17 A block diagram is shown as another example of a method for an Application Function (AF) key renewal process according to some implementation schemes. Among other things, Figure 17 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0193] At 1702, the AKMA anchor function (AAnF) (e.g., AAnF940) of the core network (e.g., such as network 100) can derive a first (e.g., current) application function key (AF key) based on a request received from an application function such as AF 724. In some embodiments, AF 724 can use the first AF key to communicate with the UE (e.g., such as UE 106) via a radio access network (RAN) such as RAN 101. In some embodiments, the first AF key can be transmitted via a RAN such as the one referenced above. Figure 10 The AF key derivation process is described above. In some embodiments, the first AF key may be associated with (and / or have) a lifetime. In some embodiments, the lifetime may include the duration from the date the first AF key is derived to be valid. In some embodiments, the duration may be at least one of approximately minutes, hours, days, weeks, and / or months.

[0194] At 1704, AAnF can determine that the first AF key has expired. In some embodiments, determining that the first AF key has expired may include: AAnF receiving a first message from the UE and / or AF that can indicate the expiration of the first AF key. In some embodiments, the first message may be or include an AF key refresh request message. In some embodiments, the first message may be sent in response to one of the AF and / or UE determining that the first AF key has been changed (e.g., refreshed and / or renewed). For example, in some embodiments, one of the AF and / or UE may determine that the first AF key has become corrupted (e.g., intentionally and / or unintentionally shared with another device in the radio access network). In some embodiments, the first message may include counter parameters. In some embodiments, the counter parameters may be incremented each time a new AF key associated with the first AF key is derived. In some embodiments, determining that the first AF key has expired may include: AAnF monitoring the lifetime of the first AF key and determining that the lifetime of the first AF key has expired. In such embodiments, AAnF may transmit a message to the AF that can indicate the expiration of the first AF key after deriving a second AF key. In some embodiments, this message may be an AF key refresh notification message. In some implementations, the message may include one or more of the KAKMA identifier (ID), AF ID, or first AF key.

[0195] At position 1706, AAnF can derive a second AF key based at least on KAKMA and the counter parameter. In some implementations, deriving the second AF key may include as referenced above. Figure 10 The derivation process is described above. For example, in some embodiments, deriving a second AF key may include: AAnF using a Key Derivation Function (KDF) as specified in the 3GPP standard. In some embodiments, the input string to the KDF may include a counter parameter. In some embodiments, the counter parameter may be one of the P0 parameter or the P1 parameter of the input string. In such embodiments, the other of the P0 parameter or the P1 parameter may be a fixed value. For example, when the counter parameter is the P0 parameter of the input string, the P1 parameter of the input string may be one of the first AF key identifier (ID) or AF. As another example, when the counter parameter is the P1 parameter of the input string, the P0 parameter of the input string may be one of the first AF key identifier (ID) or AF.

[0196] At point 1708, AAnF can notify the AF of the second AF key. In some implementations, this notification may be an AF key refresh notification. In some implementations, the notification may include the second AF key and the associated lifetime of the second AF key.

[0197] Figure 18A block diagram illustrating another example of a method for an Application Function (AF) key renewal process according to some embodiments is shown. Among other devices, Figure 18 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0198] At 1802, the UE (e.g., such as UE 106) can communicate with an application function (e.g., such as AF 724) via a radio access network (e.g., such as RAN 101). In some embodiments, the first AF key may have already been specified by a method such as the one referenced above. Figure 10 The AF key derivation process is described above. In some embodiments, the first AF key may have been derived from an AKMA anchor function (AAnF) such as AAnF 940 of the core network (e.g., such as network 100). In some embodiments, the first AF key may be associated with (and / or have) a lifetime. In some embodiments, the lifetime may include the duration from the date the first AF key is derived to be valid. In some embodiments, the duration may be at least one of approximately several minutes, several hours, several days, several weeks, and / or several months.

[0199] At 1804, the UE can determine that the first AF key has expired. In some implementations, determining that the first AF key has expired may include: the UE receiving a first message from the AAnF of the core network indicating that the first AF key has expired. In some implementations, the first message may be or include an AF key refresh message. In some implementations, the first message may include counter parameters. In some implementations, the counter parameters may be incremented each time a new AF key associated with the first AF key is derived. In some implementations, determining that the first AF key has expired may include: the UE monitoring the lifetime of the first AF key and determining that the lifetime of the first AF key has expired. In such implementations, the UE may transmit a message indicating that the first AF key has expired to the AAnF of the core network after deriving a second AF key. In some implementations, this message may be an AF key refresh request message. In some implementations, this message may include counter parameters. In some implementations, this message may include (and / or further include) one or more of a KAKMA identifier (ID), an AF ID, or the first AF key. In some implementations, determining that the first AF key has expired may include: the UE determining to change the AF key. For example, in some implementations, the UE may determine that the first AF key has been compromised (e.g., intentionally and / or unintentionally shared with another device in the radio access network). In some implementations, the UE may determine to revoke the first AF key. In some implementations, the UE may transmit a message to the AAnF of the core network indicating that the first AF key has expired after deriving the second AF key. In some implementations, this message may be an AF key refresh request message. In some implementations, this message may include counter parameters. In some implementations, this message may include (and / or further include) one or more of a KAKMA identifier (ID), an AF ID, or the first AF key.

[0200] At point 1806, the UE can derive a second AF key based at least on the KAKMA and counter parameters. In some implementations, deriving the second AF key may include methods as described in the reference above. Figure 10The derivation process is described above. For example, in some embodiments, deriving a second AF key may include the UE using a Key Derivation Function (KDF) as specified in the 3GPP standard. In some embodiments, the input string to the KDF may include a counter parameter. In some embodiments, the counter parameter may be either a P0 parameter or a P1 parameter of the input string. In such embodiments, the other of the P0 or P1 parameter may be a fixed value. For example, when the counter parameter is a P0 parameter of the input string, the P1 parameter of the input string may be either a first AF key identifier (ID) or an AF. Similarly, when the counter parameter is a P1 parameter of the input string, the P0 parameter of the input string may be either a first AF key identifier (ID) or an AF.

[0201] At 1808, the UE can use the second AF key to communicate with the AF via the RAN.

[0202] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0203] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0204] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, if executed by a computer system, the program instructions cause the computer system to perform a method, such as any method embodiment of the method embodiments described herein, or any combination of method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0205] In some implementations, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0206] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0207] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A non-transitory computer-readable storage medium storing program instructions executable by processing circuitry to enable a user equipment device (UE): The application function AF communicates with the application function AF via the radio access network RAN ​​using a first application function AF key, wherein the first AF key is associated with the lifetime. Determining that the first AF key has expired includes monitoring the lifespan of the first AF key and determining that the lifespan of the first AF key has expired; The second AF key is derived based at least on the AKMA anchor key KAKMA of the application authentication and key management architecture and the counter parameters; After deriving the second AF key, a first message is transmitted to the AKMA anchor function AAnF, wherein the first message indicates that the first AF key has expired; and The second AF key is used to communicate with the AF via the RAN.

2. The non-transitory computer-readable storage medium according to claim 1, In order to determine that the first AF key has expired, the program instructions can be further executed to enable the UE to: A second message is received from the AKMA anchor function AAnF, wherein the second message indicates that the first AF key has expired.

3. The non-transitory computer-readable storage medium according to claim 2, The second message includes the counter parameter, and the counter parameter is incremented each time a new AF key associated with the first AF key is derived.

4. The non-transitory computer-readable storage medium according to claim 1, In order to determine the expiration of the lifetime of the first AF key, the program instructions can be further executed to enable the UE to: It is determined that the duration since the derivation of the first AF key has exceeded the duration specified by the lifetime; Determine to revoke the first AF key; or It was determined that the first AF key was corrupted.

5. The non-transitory computer-readable storage medium according to claim 1, The first message includes the counter parameter, and the counter parameter is incremented each time a new AF key associated with the first AF key is derived.

6. The non-transitory computer-readable storage medium according to claim 1, The first message includes one or more of the following: KAKMA identifier ID, AF ID, or the first AF key.

7. The non-transitory computer-readable storage medium according to claim 1, In order to derive the second AF key based at least on the KAKMA and the counter parameters, the program instructions can be further executed to enable the UE to: The key derivation function (KDF) specified in the 3GPP standard is used, wherein the input string to the KDF includes the counter parameter, wherein the counter parameter is one of the P0 parameter or the P1 parameter of the input string, and wherein the other of the P0 parameter or the P1 parameter is a fixed value.

8. The non-transitory computer-readable storage medium according to claim 7, Wherein, when the counter parameter is the P0 parameter of the input string, the P1 parameter of the input string is either the first AF key identifier ID or a value associated with the AF; and Wherein, when the counter parameter is the P1 parameter of the input string, the P0 parameter of the input string is either the first AF key identifier ID or a value associated with the AF.

9. The non-transitory computer-readable storage medium according to claim 1, The lifetime mentioned therein includes the duration from the time the first AF key is derived to be valid.

10. A network entity, comprising: Memory; and At least one processor, which communicates with the memory, wherein the at least one processor is configured to: A first application function AF key is derived based on a request received from the application function AF, wherein the first AF key is associated with a lifetime. Determining that the first AF key has expired includes monitoring the lifespan of the first AF key and determining that the lifespan of the first AF key has expired; The second AF key is derived based at least on the AKMA anchor key KAKMA of the application authentication and key management architecture and the counter parameters; After deriving the second AF key, a first message is transmitted to the User Equipment (UE) communicating with the AF, wherein the first message indicates that the first AF key has expired, wherein the first message includes the counter parameter, and wherein the counter parameter is incremented each time a new AF key associated with the first AF key is derived; and The second AF key and associated lifetime are notified to the AF.

11. The network entity according to claim 10, In order to derive the second AF key based at least on the KAKMA and the counter parameters, the at least one processor is further configured to: The key derivation function (KDF) specified in the 3GPP standard is used, wherein the input string to the KDF includes the counter parameter, wherein the counter parameter is one of the P0 parameter or the P1 parameter of the input string, and wherein the other of the P0 parameter or the P1 parameter is a fixed value.

12. A user equipment (UE) comprising: At least one antenna; At least one radio component, wherein the at least one radio component is configured to perform cellular communication using at least one radio access technology (RAT); and One or more processors, said one or more processors being coupled to said at least one radio component, wherein said one or more processors and said at least one radio component are configured to perform voice and / or data communication; The one or more processors wherein the UE is configured to: The application function (AF) communicates with the application function (AF) via the radio access network (RAN) using a first application function (AF) key, wherein the first AF key is associated with a lifetime, and wherein the lifetime includes the duration from the date the first AF key is derived to be valid; Determining that the lifetime of the first AF key has expired includes monitoring the lifetime of the first AF key and determining that the lifetime of the first AF key has expired; The second AF key is derived based at least on the AKMA anchor key KAKMA of the application authentication and key management architecture and the counter parameters; After deriving the second AF key, a first message is transmitted to the AKMA anchor function AAnF, wherein the first message indicates that the first AF key has expired; and The second AF key is used to communicate with the AF via the RAN.

13. The UE according to claim 12, In order to determine that the first AF key has expired, the one or more processors are further configured to cause the UE to: A second message is received from the AKMA anchor function AAnF, wherein the second message indicates that the first AF key has expired, wherein the second message includes the counter parameter, and wherein the counter parameter is incremented each time a new AF key associated with the first AF key is derived.

14. The UE according to claim 12, In order to determine the expiration of the lifetime of the first AF key, the one or more processors are further configured to cause the UE to: Determine that the duration since the derivation of the first AF key has exceeded the duration specified by the lifetime; or Determine to revoke the first AF key; or It was determined that the first AF key was corrupted; and The first message includes the counter parameter, and the counter parameter is incremented each time a new AF key associated with the first AF key is derived.

15. The UE according to claim 12, In order to derive the second AF key based at least on the KAKMA and the counter parameters, the one or more processors are further configured to cause the UE to: The key derivation function (KDF) specified in the 3GPP standard is used, wherein the input string to the KDF includes the counter parameter, wherein the counter parameter is one of the P0 parameter or the P1 parameter of the input string, and wherein the other of the P0 parameter or the P1 parameter is a fixed value.

16. The UE according to claim 15, Wherein, when the counter parameter is the P0 parameter of the input string, the P1 parameter of the input string is either the first AF key identifier ID or a value associated with the AF; and Wherein, when the counter parameter is the P1 parameter of the input string, the P0 parameter of the input string is either the first AF key identifier ID or a value associated with the AF.

Images