BACKGROUND

[ooi] Some electronic devices can use radio-frequency (RF) signals to communicate information. These radio-frequency signals enable users to talk with friends, download information, share pictures, remotely control household devices, receive global positioning information, listen to radio stations, and so forth. It can be challenging to protect the information carried by the radio-frequency signals from a third party. Because the radio-frequency signals propagate through air, the third party can use equipment to detect these radio-frequency signals. Without appropriate security measures, the third party can extract information from the radio-frequency signals and use this information to impersonate the user, gain unauthorized access to the network, eavesdrop on a conversation, invade a user’s privacy, perform disruptive or illegal acts under the user’s identity, and so forth.

[002] To address this issue, wireless communications can use cryptography to encrypt the information that is carried by the radio-frequency signals. This encryption can make it challenging for the third party to extract the information. Some wireless communication standards use symmetric keys, which are provided to a user equipment (UE) and a network to enable the UE and the network to encrypt or decrypt information that is communicated between them. The use of symmetric keys, however, has some inherent vulnerabilities. For example, an entity responsible for assigning a symmetric key to a UE can unintentionally or intentionally distribute the symmetric key to the third party. Additionally, a server responsible for storing the symmetric key of the network can be vulnerable to a cyberattack (e.g., hacking) from the third party. Consequently, it can be challenging to secure symmetric keys that are stored in separate locations.

SUMMARY

[003] Techniques and apparatuses are described for distributed network cellular identity management. In particular, a distributed-network cellular-identity-management (DNCIM) server includes a lookup table with one or more entries associated with different user equipment (UE). Each entry includes a UE public key, a core network (CN) public key, and a subscriber identifier associated with the particular UE. The UE and an authentication server of a network generate respective cipher keys based on a UE private key and the CN public key, and the UE public key and a CN private key. These cipher keys are asymmetric keys that can be used for establishing secure communications (e.g., encrypting and decrypting messages between the UE and the network). The UE and the authentication server can also authenticate one another by e.g. determining if the subscriber identifier stored in the DNCIM server corresponds with the CN public key and the UE public key used by the UE and the authentication server, respectively. With the DNCIM server, a single symmetric key does not need to be securely placed in two locations. Instead, the UE and the authentication server can generate different cipher keys based on information stored and related together by the DNCIM server.

[004] Aspects described below include a method performed by an authentication server. The method includes storing a core-network public key, a core-network private key associated with the core-network public key, and an expected payload. The method also includes receiving a user-equipment public key associated with a user equipment and generating a first cipher key based on both the user-equipment public key and the core network private key. The method additionally includes receiving an encrypted message from the user equipment. The encrypted message includes a payload encrypted with a second cipher key that is based on a user-equipment private key and the core-network public key. The method further includes decrypting the encrypted message using the first cipher key to obtain the payload and verifying the first cipher key and the second cipher key based on a determination that the payload of the encrypted message is equal to the expected payload.

[005] Aspects described below include an authentication server with a first processor and first memory system configured to perform any of the methods described. The processor may be communicatively coupled to the first memory system, wherein the processor may be configured to execute computer-readable instructions that are stored in the first memory system and that cause the authentication server to carry out the steps of any of the methods described and/or claimed. [006] Aspects described below also include a method performed by a user equipment. The method includes storing, by an integrated circuit of the user equipment, a user-equipment private key and a first subscriber identity. The user-equipment private key is associated with a user-equipment public key. The method also includes obtaining a core network public key associated with an authentication server and generating a first cipher key based on the user-equipment private key and the core-network public key. The method additionally includes sending an encrypted message to the authentication server. The encrypted message includes a payload encrypted with the first cipher key. The method further includes sending the core-network public key to a distributed-network cellular- identity-management server and receiving a second subscriber identity that corresponds to the core-network public key from the distributed-network cellular-identity-management server. The method includes authenticating the authentication server based on a determination that the second subscriber identity provided by the distributed-network cellular-identity-management server is equal to the first subscriber identity stored by the integrated circuit.

[007] Aspects described below include a user equipment with a radio-frequency transceiver. The user equipment also includes a processor and memory system configured to perform any of the methods described. The processor may be communicatively coupled to the memory system, wherein the processor may be configured to execute computer- readable instructions that are stored in the memory system and that cause the authentication server to carry out the steps of any of the methods described and/or claimed. Further, the invention relates to a system comprising an authentication server and a user equipment.

[008] Aspects described below also include a system with means for establishing secure communications between a core network and a user equipment using distributed network cellular identity management.

BRIEF DESCRIPTION OF THE DRAWINGS

[009] Apparatuses of and techniques for distributed network cellular identity management are described with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:

FIG. 1 illustrates an example wireless network environment in which distributed network cellular identity management can be implemented.

FIG. 2 illustrates example entities for distributed network cellular identity management.

FIG. 3 illustrates an example device diagram of a user equipment for distributed network cellular identity management.

FIG. 4 illustrates details of example messaging transactions between entities for distributed network cellular identity management.

FIG. 5 illustrates additional details of example messaging transactions between entities for distributed network cellular identity management. FIG. 6 illustrates an example method for distributed network cellular identity management.

DETAILED DESCRIPTION

Overview

[ooio] This document describes techniques and devices for distributed network cellular identity management. Without appropriate security measures, information carried by radio-frequency signals can be intercepted by a third party. To address this issue, wireless communications can use cryptography to encrypt the information that is carried by the radio-frequency signals. This encryption can make it challenging for the third party to extract the inform tion.

[ooii] Some wireless communication standards use symmetric keys, which are provided to a user equipment (UE) and a network to enable the UE and the network to encrypt or decrypt information that is communicated between them. The use of symmetric keys, however, has some inherent vulnerabilities. For example, an entity responsible for assigning a symmetric key to a UE can unintentionally or intentionally distribute the symmetric key to the third party. Additionally or alternatively, a server responsible for storing the symmetric key of the network can be subject to a cyberattack (e.g., hacking) from the third party.

[0012] To address these vulnerabilities, techniques and apparatuses are described for distributed network cellular identity management. In particular, a distributed-network cellular-identity-management (DNCIM) server includes a lookup table with one or more entries associated with different user equipment (UE). Each entry includes a UE public key, a core network (CN) public key, and a subscriber identifier associated with the particular UE. The UE and an authentication server of a network generate respective cipher keys based on a UE private key and the CN public key, and the UE public key and a CN private key. These cipher keys are asymmetric keys that can be used for establishing secure communications (e.g., encrypting and decrypting messages between the UE and the network). The UE and the authentication server can also authenticate one another by determining if the subscriber identifier stored in the DNCIM server corresponds with the CN public key and the UE public key used by the UE and the authentication server, respectively. With the DNCIM server, a single symmetric key does not need to be securely placed in two locations. Instead, the UE and the authentication server can generate different cipher keys based on information stored and related together by the DNCIM server.

Example Environment

[0013] FIG. 1 illustrates an example environment 100, which includes multiple user equipment 110 (UE 110), illustrated as UE 111, UE 112, and UE 113. Each UE 110 can communicate with base stations 120 (illustrated as base stations 121, 122, 123, and 124) through one or more wireless communication links 130 (wireless link 130), illustrated as wireless links 131 and 132. For simplicity, the UE 110 is implemented as a smartphone but may be implemented as any suitable computing or electronic device, such as a mobile communication device, modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle- based communication system, or an Intemet-of- Things (IoT) device such as a sensor or an actuator. The base stations 120 (e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Evolved Node B, ng-eNB, Next Generation Node B, gNode B, gNB, or the like) may be implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof.

[0014] The base stations 120 communicate with the UE 110 using the wireless links 131 and 132, which may be implemented as any suitable type of wireless link. The wireless links 131 and 132 include control and data communication, such as downlink of data and control information communicated from the base stations 120 to the UE 110, uplink of other data and control information communicated from the UE 110 to the base stations 120, or both. The wireless links 130 may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3rd Generation Partnership Project Long-Term Evolution (3 GPP LTE), Enhanced Long-Term Evolution (eLTE), Fifth-Generation New Radio (5G NR), Fourth- Generation (4G) standard, and so forth. Multiple wireless links 130 may be aggregated in a carrier aggregation to provide a higher data rate for the UE 110. Multiple wireless links 130 from multiple base stations 120 may be configured for Coordinated Multipoint (CoMP) communication with the UE 110.

[0015] The base stations 120 are collectively a Radio Access Network 140 (e.g., RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN or NR RAN). The RANs 140 are illustrated as an NR RAN 141 and an E-UTRAN 142. In FIG. 1, core network 190 is shown to include a Fifth-Generation Core (5GC) network 150 (5GC 150) and an Evolved Packet Core (EPC) network 160 (EPC 160), which are different types of core networks. The base stations 121 and 123 in the NR RAN 141 are connected to the 5GC 150. The base stations 122 and 124 in the E-UTRAN 142 are connected to the EPC 160. Optionally or additionally, the base station 122 may connect to both the 5GC 150 and EPC 160 networks.

[0016] The base stations 121 and 123 connect, at 102 and 104 respectively, to the 5GC 150 through an NG2 interface for control-plane signaling and using an NG3 interface for user-plane data communications. The base stations 122 and 124 connect, at 106 and 108 respectively, to the EPC 160 using an S 1 interface for control-plane signaling and user- plane data communications. Optionally or additionally, if the base station 122 connects to the 5GC 150 and EPC 160 networks, the base station 122 connects to the 5GC 150 using an NG2 interface for control-plane signaling and through an NG3 interface for user-plane data communications, at 180.

[0017] In addition to connections to core networks 190, the base stations 120 may communicate with each other. For example, the base stations 121 and 123 communicate through an Xn interface at 105, the base stations 122 and 123 communicate through an Xn interface at 105, and the base stations 122 and 124 communicate through an X2 interface at 107.

[0018] The 5GC 150 includes an Access and Mobility Management Function 152 (AMF 152), which provides control-plane functions, such as registration and authentication of multiple UE 110, authorization, and mobility management in the 5G NR network. The EPC 160 includes a Mobility Management Entity 162 (MME 162), which provides control- plane functions, such as registration and authentication of multiple UE 110, authorization, or mobility management in the E-UTRA network. The AMF 152 and the MME 162 communicate with the base stations 120 in the RANs 140 and also communicate with multiple UE 110, using the base stations 120.

[0019] The core network 190 also includes an authentication server 164 and a distributed-network cellular-identity-management (DNCIM) server 166. The authentication server 164 can participate in an authentication and key agreement procedure with the multiple UE 110 to authenticate the multiple UE 110 and generate cipher keys to enable secure communications with the multiple UE 110. Generally, the authentication server 164 can communicate with the AMF 152 or the MME 162 or can access inform tion and functions of the AMF 152 or the MME 162. In 4G wireless communication standards, the authentication server 164 can be implemented as a home subscriber server (HSS). In

5G wireless communication standards, the authentication server 164 can include an authentication server function (AUSF) or a unified data management (UDM) module. The DNCIM server 166 can generate, distribute, or store public keys of the multiple UE 110 and the core network 190 for distributed network cellular identity management. The UE 110, the authentication server 164, and the DNCIM server 166 are further described with respect to FIG. 2.

[0020] FIG. 2 illustrates example entities for distributed network cellular identity management. These entities include the UE 110, the authentication server 164, and the DNCIM server 166. In the depicted configuration, the UE 110 includes an integrated circuit (IC) 200, which can be implemented as a subscriber identity module (SIM) 202 (e.g., a SIM card). The integrated circuit 200 can securely store information to identify and authenticate a network subscriber (e.g., a user of the UE 110).

[0021] The DNCIM server 166 includes a lookup table 204. The lookup table 204 contains public information associated with the UE 110 and the core network 190, as further described below. In some aspects, the DNCIM server 166 is implemented using multiple public or private entities (e.g., multiple servers or multiple databases) and the lookup table 204 is implemented as a distributed ledger 206. In this manner, the lookup table 204 can be maintained, updated, and secured using techniques such as blockchain. In general, the information stored in the lookup table 204 is public information, which can be obtained by any entity able to communicate with DNCIM server 166.

[0022] A network provider generates two pairs of cryptographic keys (e.g., numbers). Each pair of cryptographic keys includes a private key and a public key, which are mathematically linked and differ from one another. A variety of different mathematical operations can be used to relate the private key and the public key together, including factorization or discrete logarithms. In general, it is relatively easy (e.g., computationally efficient) to generate the public key given the private key. However, it is challenging (e.g., computationally inefficient) to derive the private key from the public key. As such, the public key can be distributed and shared with other entities without exposing the private key. Due to the mathematical relationship between the public key and the private key, messages encrypted with the public key can be decrypted using the private key.

[0023] As shown in FIG. 2, the network provider generates a UE private key 208, a UE public key 210, a core network (CN) private key 212, and a CN public key 214. The UE private key 208 and the UE public key 210 are a pair of asymmetric cryptographic keys, and the CN private key 212 and the CN public 214 are a second pair of asymmetric cryptographic keys. The network provider can employ a variety of different types of asymmetric key generation algorithms to generate these pairs of cryptographic keys, including a Rivest-Shamir-Adleman (RSA) algorithm, a Difffie-Hellman key exchange, elliptic curve cryptography (ECC), and so forth.

[0024] The network provider passes the UE private key 208 and the CN private key 212 to the UE 110 and the authentication server 164, respectively. Within the UE 110, the integrated circuit 200 (e.g., the SIM 202) can securely store the UE private key 208.

The network provider also assigns a subscriber identity 216 of the network subscriber to the UE 110. The subscriber identity 216 can be used by the authentication server 164 or other network entities to uniquely identify the network subscriber. As an example, the subscriber identity 216 can be an international mobile subscriber identity (IMSI) 218 that is securely stored by the SIM 202. Although not explicitly shown, the UE 110 can also store the UE public key 210 or the CN public key 214. These public keys 210 and 214 can be stored by the integrated circuit 200 or a computer-readable storage media (CRM) (e.g., CRM 312 of FIG. 3).

[0025] In some aspects, the network provides the authentication server 164 the CN public key 214. In other aspects, the authentication server 164 can obtain the CN public key 214 from the DNCIM server 166. The authentication server 164 can also store an expected payload 220, which can include the CN public key 214, a nonce (e.g., an arbitrary number), or some predetermined number. The expected payload 220 can be specified by the network provider.

[0026] The network provider also passes the UE public key 210, the CN public key 214, and the subscriber identity 216 to the DNCIM server 166. The DNCIM server 166 stores this inform tion in an entry of the lookup table 204. With this entry, the DNCIM server 166 can relate the UE public key 210, the CN public key 214, and the subscriber identity 216 together. In some aspects, the DNCIM server 166 can lock or prevent changes to the entry within the lookup table 204 using a cryptographic hash based on a cryptographic key stored in the DNCIM server 166 (e.g., a DNCIM update key 222). The

DNCIM server 166 can also make updates to the lookup table 204 by adding new entries or replacing the UE public key 210 or the CN public key 214 of the entry with a new UE public key or a new CN public key, respectively. The lookup table 204 can also include multiple entries associated with different UEs 110. In this manner, the DNCIM server 166 can provide at least one of the UE public key 210, the CN public key 214, or the subscriber identity 216 associated with an entry of the multiple entries responsive to receiving the UE public key 210, the CN public key 214, or the subscriber identity 216 corresponding to the entry.

Example Devices

[0027] FIG. 3 illustrates an example device diagram 300 of the UE 110. The UE 110 may include additional functions and interfaces that are omitted from FIG. 3 for the sake of clarity. The UE 110 includes antennas 302, a radio-frequency (RF) front end 304 (RF front end 304), an LTE transceiver 306, and a 5G NR transceiver 308 for communicating with base stations 120 in the 5G RAN 141 and/or the E-UTRAN 142. The RF front end 304 of the UE 110 can couple or connect the LTE transceiver 306 and the 5G NR transceiver 308 to the antennas 302 to facilitate various types of wireless communication. The antennas 302 of the UE 110 may include an array of multiple antennas that are configured similarly to or differently from each other. The antennas 302 and the RF front end 304 can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3 GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 306, and/or the 5G NR transceiver 308. By way of example and not limitation, the antennas 302 and the RF front end 304 can be implemented for operation in sub gigahertz bands, sub-6 GHZ bands, and/or bands with frequencies between approximately 6 and 300 GHz that are defined by the 3 GPP LTE and 5G NR communication standards.

[0028] The UE 110 also includes processor(s) 310 and computer-readable storage media 312 (CRM 312). The processor 310 may be a single-core processor or a multi-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. CRM 312 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 314 of the UE 110. The device data 314 includes user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the UE 110, which are executable by processor(s) 310 to enable user-plane communication, control-plane signaling, and user interaction with the UE 110.

[0029] CRM 312 also includes an authentication module 316. Alternatively or additionally, the authentication module 316 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the

UE 110. In at least some aspects, the authentication module 316 participates in the authentication and key agreement process with the authentication server 164, which is further described with respect to FIG. 4. During this process, the authentication module 316 generates a cipher key, which can enable the authentication module 316 to establish secure communications with the network. In particular, the authentication module 316 can use the cipher key to encrypt information that is sent to the base station 120 or decrypt information that is received from the base station 120. The UE 110, the authentication server 164, and the DNCIM server 166 can at least partially implement distributed network cellular identity management, as further described with respect to

FIG. 4

Distributed Network Cellular Identity Management

[0030] FIG. 4 illustrates details of example messaging transactions between entities for distributed network cellular identity management. In FIG. 4, a closed lock symbol and an open lock symbol respectively indicate if a message is communicated over a secure channel or an unsecured channel (e.g., whether the message is encrypted or not encrypted).

[0031] At 405, the authentication module 316 of the UE 110 directs the UE 110 to send the subscriber identity 216 (e.g., the IMSI 218) to the authentication server 164 of the core network 190. For example, the authentication module 316 can obtain the subscriber identity 216 from the SIM 202 and direct the LTE transceiver 306 or the 5G NR transceiver 308 to transmit, using the RF front end 304 and the antennas 302, a message that contains the subscriber identity 216. The authentication server 164 can receive the subscriber identity 216 from the base station 120.

[0032] At 410, the authentication server 164 forwards the subscriber identity 216 to the DNCIM server 166. The DNCIM server 166 provides the subscriber identity 216 as an input to a lookup function 415. The lookup function 415 uses the lookup table 204 to determine the UE public key 210 associated with the subscriber identity 216.

[0033] At 420, the DNCIM server 166 sends the corresponding UE public key 210 to the authentication server 164. If the authentication server 164 does not have the CN public key 214, the authentication server 164 can also request that the DNCIM server 166 sends the CN public key 214 associated with the subscriber identity 216 and the DNCIM 166 can respond by sending the CN public key 214 (not shown). In other aspects, the steps described at 410, 415, and 420 can be bypassed if the UE 110 sends the UE public key 210 to the authentication server 164 at 405. With the UE public key 210, the authentication server 164 can proceed to cipher key generation 425 and encryption 430, which are further described below.

[0034] Responsive to receiving the UE public key 210, the authentication server 164 performs cipher key generation at 425 and encryption at 430. At 425, the authentication server 164 generates a cipher key Kc 426 based on the UE public key 210 and the CN private key 212. The cipher key Kc 426 can be used to verify a UE llO’s cipher key, as further described below.

[0035] At 430, the authentication server 164 generates an encrypted message 436 whose payload (e.g., contents) is encrypted using the UE public key 210. The payload of the encrypted message 436 includes the CN public key 214. In some aspects, the payload also includes a nonce or some predetermined number. At 435, the authentication serverl64 sends the encrypted message 436 to the UE 110 using the base station 120. [0036] Responsive to receiving the encrypted message 436, the authentication module 316 performs decryption at 440, cipher key generation at 445, and encryption at 450. At 440, the authentication module 316 decrypts the encrypted message 436 using the UE private key 208 to identify the CN public key 214 in the payload of the received encrypted message 436. In other aspects, the CN public key 214 can be pre-loaded and stored by the UE 110. As an example, the integrated circuit 200 or the CRM 312 can store the CN public key 214.

[0037] At 445, the authentication module 316 generates a cipher key Kc’ 446 using both the UE private key 208 and the CN public key 214.

[0038] At 450, the authentication module 316 generates an encrypted message 456 whose payload is encrypted using the cipher key Kc’ 446. The payload of the encrypted message 456 can include part or all of the content of the received encrypted message 436 (e.g., the CN public key 214 and/or the nonce), a second nonce, the UE public key 210, or a predetermined number.

[0039] At 455, the authentication module 316 directs the UE 110 to send the encrypted message 456 to the authentication server 164.

[0040] At 460, the authentication server 164 performs a key agreement function 460 to verify the cipher key Kc’ 446 and the cipher key Kc 426. For example, the authentication server 164 decrypts the encrypted message 456 using the cipher key Kc 426 to obtain (e.g., extract) the payload of the encrypted message 456. If the payload matches the expected payload 220, which is stored by the authentication server 164, the authentication server 164 determines that the cipher key 446 of the UE 110 agrees with the cipher key 426 of the core network 190. In other words, the cipher keys 426 and 446 can be used to establish secure communications between the network and the UE 110. Responsive to verifying the cipher keys 426 and 446, the authentication module 316 and the authentication server 164 can authenticate each other, as further described with respect to FIG. 5.

[0041] FIG. 5 illustrates additional details of example messaging transactions between entities for distributed network cellular identity management. At 505, the authentication server 164 sends the UE public key 210 to the DNCIM server 166.

[0042] At 510, the DNCIM server 166 uses a lookup function to determine the subscriber identity 216 associated with the UE public key 210.

[0043] At 515, the DNCIM server 166 sends the subscriber identity 216 to the authentication server 164. Responsive to receiving the subscriber identity 216, the authentication server 164 performs authentication at 520 to determine whether the previous subscriber identity 216 obtained at 405 in FIG. 4 is equal to the subscriber identity 216 obtained at 515. If these identities match, the authentication server 164 can establish secure communications with the UE 110 using the cipher key Kc 426. In other words, the DNCIM server 166 provides further information to reduce the risk of a successful spoof attack (or impersonation) of the UE 110 through using a false subscriber identity.

[0044] At 525, the authentication module 316 sends the CN public key 214, which was decrypted and extracted from the encrypted message 436 at 440 in FIG. 4, to the

DNCIM server 166. [0045] At 530, the DNCIM server 166 uses the lookup function to determine the subscriber identity 216 corresponding to the CN public key 214.

[0046] At 535, the DNCIM server 166 sends the subscriber identity 216 to the UE 110.

[0047] At 540, the authentication module 316 performs authentication to determine whether the subscriber identity 216 provided by the DNCIM server 166 is equal to the subscriber identity 216 stored in the integrated circuit 200 (e.g., the SIM 202). If these identities match, the authentication server 164 is authenticated, and the UE 110 can establish secure communications with the authentication server 164 using the cipher key Kc’ 446.

[0048] At 545, the UE 110 and the core network 190 communicate together using one or more encrypted messages 546. For example, the authentication server 164 can send an encrypted message 546 to the UE 110 with a payload that is encrypted using the cipher key Kc 426. The UE 110 can decrypt the encrypted message 546 using the cipher key Kc’ 446 to obtain a payload of the encrypted message 546. Similarly, the UE 110 can send an encrypted message 546 to the authentication server 164 with a payload that is encrypted using the cipher key Kc’ 446. The authentication server 164 can decrypt the encrypted message 546 using the cipher key Kc 426 to obtain the payload of the encrypted message 546. In this manner, secure communications are established between the UE 110 and the core network 190. Example Method

[0049] FIG. 6 depicts an example method 600 for distributed network cellular identity management. Method 600 is shown as a set of operations (or acts) performed but not necessarily limited to the order or combinations in which the operations are illustrated. Further, any of one or more of the operations may be repeated, combined, reorganized, or linked to provide a wide array of additional and/or alternate methods. In portions of the following discussion, reference may be made to environment 100 of FIG. 1 and entities detailed in FIGs. 2-4, reference to which is made for example only. The techniques are not limited to performance by one entity or multiple entities operating on one device.

[0050] At 602 a CN public key, a CN private key associated with the CN public key, and an expected payload are stored. For example, the authentication server 164 stores the CN public key 214, the CN private key 212, and the expected payload 220, as shown in FIG. 2. The CN private key 212 and the CN public key 214 represent a pair of cryptographic keys that are mathematically linked. The expected payload 220 can include the CN public key 214, a nonce, or a predetermined number. The CN private key 212, the CN public key 214, and the expected payload 220 can be individually provided to the authentication server 164 at different times. In some cases, the expected payload 220 can be determined by the authentication server 164 at a later time (e.g., after 604, after 606, or prior to 612). The authentication server 164 can be implemented as the HSS server for 4G standards or can include the AUSF or the UDM module for 5G standards. [0051] At 604 a UE public key associated with a UE is received. For example, the authentication server 164 receives the UE public key 210 associated with the UE 110. The UE public key 210 can be received from the UE 110 or the DNCIM server 166. If the authentication server 164 receives the subscriber identity 216 from the UE 110, as shown in FIG. 4 at 405, the authentication server 164 can send the subscriber identity 216 to the DNCIM server 166, as shown in FIG. 4 at 410, to request that the DNCIM server 166 sends the UE public key 210 that corresponds to the subscriber identity 216. The authentication server 164 can also send the CN public key 214 to the UE 110. In some aspects, the authentication server 164 sends the CN public key 214 to the UE 110 using an encrypted message 436, as shown in FIG. 4 at 435. At 606, a first cipher key is generated based on the UE public key and the CN public key. For example, the authentication server 164 can generate the cipher key Kc 426 based on the UE public key 210 and the CN private key 212, as shown in FIG. 4 at 425.

[0052] At 608, an encrypted message is received from the UE. The encrypted message includes a payload encrypted with a second cipher key that is based on a UE private key and the CN public key. For example, the authentication server 164 receives the encrypted message 456 from the UE 110, as shown in FIG. 4 at 455. The encrypted message 456 includes a payload encrypted with the cipher key Kc’ 446, which is based on the UE private key 208 and the CN public key 214. The payload can include the CN public key 214, a nonce, or some predetermined number. [0053] At 610, the encrypted message is decrypted using the first cipher key to obtain the payload. For example, the authentication server 164 decrypts the encrypted message 456 to obtain the payload. The decryption can be performed as part of the key agreement function at 460 of FIG. 4.

[0054] At 612, the first cipher key and the second cipher key are verified based on a determination that the payload of the encrypted message is equal to the expected payload. For example, the authentication server 164 verifies the cipher key Kc 426 and the cipher key Kc’ 446 based on a determination that the payload of the encrypted message 456 is equal to the expected payload 220. This determination can be performed as part of the key agreement function at 460 of FIG. 4.

Conclusion

[0055] Although techniques for distributed network cellular identity management have been described in language specific to features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of distributed network cellular identity management.