A key generation method and device, and a network device

Abstract

The application discloses a key generation method and device, network equipment, and the method comprises the following steps: after a first network element receives a key generation request message sent by a second network element, checking whether a first network element identifier contained in the key generation request message has a corresponding relationship with an authentication identity of the second network element; if the first network element identifier contained in the key generation request message has a corresponding relationship with the authentication identity of the second network element, generating a key based on the first network element identifier and sending the key to the second network element.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a key generation method and apparatus, and network equipment. Background Technology

[0002] When the User Equipment (UE) initiates communication with the Application Function (AF), the AF needs to obtain the Authentication and Key Management (AKMA) application key (i.e., K) used for communication with the UE. AF ). AF requests the generation of K from the AKMA Anchor node Function (AAnF). AF During the process, AF will provide AF_ID to AAnF, and AanF will deduce K based on AF_ID. AF and K AF This information is provided to the AF. However, the AF_ID is public or can be constructed, which will cause the K used by the AF when communicating with the UE to be affected. AF It is easy to leak information, and the security of communication between the AF and UE cannot be guaranteed. Summary of the Invention

[0003] To address the aforementioned technical problems, embodiments of this application provide a key generation method and apparatus, a network device, a chip, and a computer-readable storage medium.

[0004] The key generation method provided in this application includes:

[0005] After receiving the key generation request message sent by the second network element, the first network element checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element.

[0006] If the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element, then a key is generated based on the first network element identifier and the key is sent to the second network element.

[0007] The key generation device provided in this application embodiment is applied to a first network element, and the device includes:

[0008] The receiving unit is used to receive the key generation request message sent by the second network element;

[0009] The processing unit is used to check whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element; if the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element, then a key is generated based on the first network element identifier.

[0010] The sending unit is used to send the key to the second network element.

[0011] The network device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the above-described key generation methods.

[0012] The chip provided in this application includes a processor for calling and running a computer program from a memory, causing a device on which the chip is installed to perform any of the methods described above.

[0013] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute any of the methods described above.

[0014] In the technical solution of this application embodiment, after the first network element receives the key generation request message sent by the second network element, it checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element. Only when the first network element identifier corresponds to the authentication identity of the second network element, the first network element generates a key for the second network element based on the first network element identifier. In this way, it can be ensured that the key obtained by the second network element is generated based on the network element identifier corresponding to its network element authentication identity, preventing the second network element from stealing the key of other network elements, and also preventing other network elements from stealing the key of the second network element, thus ensuring the security of the key. Attached Figure Description

[0015] Figure 1 This is a diagram of the 5G network system architecture;

[0016] Figure 2 This is a schematic diagram of the AKMA key hierarchy structure;

[0017] Figure 3 It is K AKMA A flowchart illustrating the derivation process;

[0018] Figure 4 It is K AF A flowchart illustrating the derivation process;

[0019] Figure 5 This is a flowchart illustrating the key generation method provided in the embodiments of this application. Figure 1 ;

[0020] Figure 6 This is a flowchart illustrating the key generation method provided in the embodiments of this application. Figure 2 ;

[0021] Figure 7 This is a schematic diagram of the structure of the key generation device provided in the embodiments of this application;

[0022] Figure 8 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0023] Figure 9 This is a schematic structural diagram of the chip according to an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0025] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0026] 5G network system architecture

[0027] Figure 1 This is a 5G network system architecture diagram, such as... Figure 1 As shown, the network elements involved in the 5G network system include: User Equipment (UE), Radio Access Network (RAN), User Plane Function (UPF), Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF), and Unified Data Management (UDM).

[0028] The technical solutions of the embodiments of this application may be applied, but are not limited to, those described above. Figure 1 The 5G network system architecture shown can also be applied to enhanced 5G network system architectures, 6G network system architectures, or future network system architectures.

[0029] AKMA

[0030] Among the related technologies, an architecture and process have been established to provide authentication and key management capabilities for upper-layer applications based on 3GPP credentials in 5G. In 5G networks, based on the terminal cards, network resources, and terminal identity authentication and secure data transmission capabilities controlled by operators, authentication and session keys are provided to business applications, providing a lightweight application-layer authentication and secure channel establishment solution for user terminals to access business applications in the mobile Internet era.

[0031] like Figure 2 As shown, the AKMA key hierarchy includes the following keys: K AUSF K AKMA K AF Among them, K AUSF Generated by AUSF. K AKMA It is ME and AUSF from K AUSF The derived key is the key of AAnF. K AF It is ME and AAnF from K AKMA The derived key is the AF key.

[0032] The following are Figure 2 The AanF and AF in the table will be explained.

[0033] AAnF: AAnF is an anchor function deployed in a local public land mobile network (HPLMN). AAnF stores the AKMA anchor key (i.e., K) for AKMA service. AKMA After the UE successfully completes 5G master authentication, the AUSF sends the key to the AAnF. The AAnF also generates key materials for use between the UE and the AF, and maintains the UE's AKMA context.

[0034] AF: An AF with AKMA service can request an AKMA application key (i.e., K) from an AAnF via the AKMA key identifier (i.e., A-KID). AF AF must be certified and authorized by the operator's network to obtain K. AF AFs deployed within carrier networks should implement the AAnF selection function.

[0035] The AKMA function does not require additional UE authentication; it only needs to reuse the 5G primary authentication to authenticate the UE, for example, by performing the 5G primary authentication process during UE registration. After successful 5G primary authentication, K... AUSF It should be stored in AUSF and UE, and AUSF and UE are based on K AUSF Derivation of K AKMA Specifically, such as Figure 3 As shown, it includes the following steps:

[0036] Step 301: AUSF sends a UE authentication request message to UDM.

[0037] Here, the UE authentication request message can be Nudm_UEAuthentication_Get Request, which contains the UE's SUPI / SUCI.

[0038] Step 302: UDM sends a UE authentication response message to AUSF.

[0039] Here, the UE authentication response message can be Nudm_UEAuthentication_Get Response, which contains the following information: AV, [AKMA Ind], [RID].

[0040] Step 303a: UE and AUSF according to K AUSF Generate K AKMA .

[0041] Step 303b: UE and AUSF generate A-KID.

[0042] Step 304: AUSF sends an AKMA anchor key registration request message to AAnF.

[0043] Here, the AKMA anchor key registration request message can be Naanf_AKMA_AnchorKey_RegisterRequest, which contains the following information: SUPI, A-KID, K AKMA .

[0044] Step 305: AAnF sends an AKMA anchor key registration response message to AUSF.

[0045] Here, the AKMA anchor key registration response message can be Naanf_AKMA_AnchorKey_RegisterResponse.

[0046] The UE should, before interacting with the AKMA application server, obtain information from K... AUSF Derivation of K AKMA And A-KID, see reference Figure 3Steps 303a and 303b in the above steps. Before communication between the UE and AF begins, the UE and AF need to know whether AKMA can be used. This is implicit in the specific application of the UE and AF or indicated by the AF to the UE. When the AF is located within the operator's network, the AF directly requests the AKMA application key (i.e., K) from the AF. AF Specifically, such as Figure 4 As shown, it includes the following steps:

[0047] Step 401: The UE sends an application session establishment request message to the AF, which contains the A-KID.

[0048] Here, when the UE initiates communication with the AF, the UE sends an application session establishment request message to the AF, which contains the A-KID. The UE may, before or after sending this message, determine the K... AKMA Derivation of K AF .

[0049] Step 402: AF sends a key generation request message to AAnF, which contains A-KID and AF_ID.

[0050] Here, the key generation request message can be Naanf_AKMA_ApplicationKey_Get Request.

[0051] If there is no activation context associated with A-KID in the AF, the AF performs AAnF selection and sends a key generation request message to the selected AAnF, which contains A-KID and AF_ID. AF_ID includes the AF's FQDN and Ua* protocol identifier, where the Ua* protocol identifier is used to identify the security protocol used between the AF and the UE.

[0052] AAnF should use the AF_ID to check whether it can provide services to AF, based on the configured local policy or the authorization information or policy provided by NRF. If yes, AAnF will execute the following process; otherwise, AAnF should reject the following process.

[0053] AAnF can verify whether the corresponding K can be found through A-KID. AKMA (i.e., effective K) AKMA This determines whether a user is authorized to use AKMA.

[0054] If a valid K exists in AAnF AKMA If so, AAnF should continue with step 403.

[0055] If there is no valid K in AAnF AKMA If so, AAnF should continue with step 404 and send an error response.

[0056] Step 403: AAnF according to K AKMA Deducing K AF .

[0057] Here, if AAnF does not have K AF If so, then AAnF is based on K AKMA Derivation of K AF When AAnF is based on K AKMA Derivation of K AF When the input key of the Key Deduction Function (KDF) is K AKMA The following parameters are used to construct the input S of the KDF:

[0058] -FC = 0x82;

[0059] -P0 = AF_ID;

[0060] -L0 = the length of AF_ID.

[0061] The AF_ID is constructed as follows: AF_ID = AF's FQDN || Ua* protocol identifier, where the Ua* protocol identifier is used to identify the security protocol used between the AF and the UE.

[0062] Step 404: AAnF sends a key generation response message to AF, which contains K AF K AF Lifecycle (K) AF expTime), SUPI.

[0063] Here, the key generation response message can be Naanf_AKMA_ApplicationKey_Get Response.

[0064] If the information in step 404 indicates that the AKMA key request failed, the AF should reject the application session establishment request and include the error reason in this step. Afterwards, the UE may send a new application session establishment request message to the AF, carrying the new A-KID.

[0065] Step 405: The AF sends an application session establishment response message to the UE.

[0066] The above Figure 4 In the illustrated process, an AF with AKMA service can request an AKMA application key (i.e., K) from an AAnF using the AKMA key identifier (A-KID) and the AF_ID that identifies the application. AFThe AF_ID is constructed as: AF_ID = AF's FQDN || Ua* Protocol Identifier, where the Ua* Protocol Identifier is used to identify the security protocol used between the AF and the UE. However, AF_ID is easily forged. Consider the following scenario: both application a (i.e., AF a, identified as AF_IDa) and application b (i.e., AF b, identified as AF_IDb) have AKMA service and can both request the AKMA application key (i.e., K) from AAnF through the AKMA key identifier (i.e., A-KID). AF The UE's AKMA key identifier is A-KID. When the UE initiates the AKMA procedure of AF a and AF b and accesses AF a and AF b, AF a and AF b obtain A-KID. AF a sends a key generation request message (containing A-KID and AF_IDa) to AAnF to obtain the application key K for communication between the UE and AF a. AFa AF_IDa is not easily obtained; it is public or can be constructed. Therefore, AF_b can also send a key generation request message (containing A-KID and AF_IDa) to AAnF. However, the current process only mentions that "AAnF should check whether AAnF can provide services to AF based on the configured local policy or the authorization information or policy provided by NRF using AF_ID," without specifying how to check. If AAnF only checks AF_ID, for example, whether the received AF_ID is in AAnF's service list, then in the above scenario, because AF_IDa is also in AAnF's service list, AAnF's check will pass and the same key generation request message will be sent to AAnF. AKMA And AF_IDa generate K for it AFa That is, AF b also obtained K AFa This allows the key to be used to crack encrypted communication between the UE and AFa, meaning the key is compromised and cannot prevent legitimate AFs from eavesdropping on other legitimate AFs. Although an AF should obtain the key through authentication and authorization from the operator's network. AF (This can prevent unauthorized AF eavesdropping). However, according to the SBA mechanism, it generally means that ANF determines whether to respond to the AF's key generation request based on the AF's authentication result. Since the authentication result and AF_ID are not associated, the aforementioned risk of leakage still exists. To address this, the following technical solution based on the embodiments of this application is proposed.

[0067] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0068] Figure 5This is a flowchart illustrating the key generation method provided in the embodiments of this application. Figure 1 ,like Figure 5 As shown, the key generation method includes the following steps:

[0069] Step 501: After receiving the key generation request message sent by the second network element, the first network element checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element.

[0070] In this embodiment, the first network element can be AAnF, and the second network element can be AF. It should be noted that this application does not limit the names of the first and second network elements.

[0071] In this embodiment of the application, after the first network element receives the key generation request message sent by the second network element, it authenticates and authorizes the second network element. After the authentication and authorization are passed, it checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element.

[0072] It should be noted that when authenticating and authorizing the second network element, the first network element can obtain the authentication identity of the second network element, that is, obtain the authentication result of the second network element.

[0073] In this embodiment, the first network element acquires first information. This first information can be stored on the first network element or on other network elements. The first information includes the correspondence between network element authentication identities and network element identifiers. Optionally, in the first information, the network element authentication identity and its corresponding network element identifier are the same content, or the network element authentication identity and its corresponding network element identifier are different content. When the network element authentication identity and its corresponding network element identifier are different content, one network element authentication identity corresponds to one or more network element identifiers. Here, one network element authentication identity corresponds to one network element identifier, which can also be described as a one-to-one correspondence between network element authentication identities and network element identifiers; one network element authentication identity corresponds to multiple network element identifiers, which can also be described as a one-to-many correspondence between network element authentication identities and network element identifiers.

[0074] As an example: The network element identifier is AF_ID. The correspondence between the pre-set network element authentication identities and AF_IDs in the first network element is shown in Table 1 below. Table 1 lists the AF_IDs corresponding to each network element authentication identity. One network element authentication identity can correspond to one or more AF_IDs. The "Whether to provide service" option in Table 1 is optional. When this option is not present, the default is to provide service.

[0075]

[0076] Table 1

[0077] As an example: Network element identifiers are serial numbers. The correspondence between the pre-set network element authentication identities and serial numbers in the first network element is shown in Table 2 below. Table 2 lists the serial numbers corresponding to each network element authentication identity. Each serial number corresponds to one AF_ID, and one network element authentication identity can correspond to one or more serial numbers (i.e., one or more AF_IDs). The "Whether to provide service" option in Table 2 is optional. When this option is not present, the default is to provide service.

[0078]

[0079] Table 2

[0080] As an example: The network element identifier is AF_ID. The correspondence between the pre-set network element authentication identities and AF_IDs in the first network element is shown in Table 3 below. Table 3 lists the network element authentication identities corresponding to each AF_ID. The network element authentication identities corresponding to different AF_IDs can be different or the same. The "Whether to provide service" option in Table 3 is optional. When this option is not present, the default is to provide service.

[0081]

[0082] Table 3

[0083] As an example: Network element identifiers are sequence numbers. The correspondence between the pre-set network element authentication identities and sequence numbers in the first network element is shown in Table 4. Table 4 lists the network element authentication identities corresponding to each sequence number. Each sequence number corresponds to one AF_ID. Different sequence numbers can correspond to different or the same network element authentication identities. It should be noted that in this case, the sequence number is unique for all network element authentication identities; that is, different AF_IDs correspond to different sequence numbers. The "Whether to provide service" option in Table 4 is optional. When this option is not present, the default is to provide service.

[0084]

[0085]

[0086] Table 4

[0087] In this embodiment, after receiving a key generation request message from a second network element, the first network element checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element based on the first information. The following explains how the first network element checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element based on the first information.

[0088] Option 1

[0089] As an optional implementation, the first network element can check whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element through the following steps:

[0090] S11: Determine the network element identifier corresponding to the authentication identity of the second network element based on the first information;

[0091] S12: Check whether the first network element identifier contained in the key generation request message belongs to the network element identifier corresponding to the authentication identity of the second network element;

[0092] S131: If the first network element identifier belongs to the network element identifier corresponding to the authentication identity of the second network element, then it is determined that there is a correspondence between the first network element identifier and the authentication identity of the second network element.

[0093] Optionally, the following steps may also be included:

[0094] S132: If the first network element identifier does not belong to the network element identifier corresponding to the authentication identity of the second network element, then send an error response message to the second network element; or, check whether the first network element identifier is a network element identifier corresponding to the authentication identity of another network element based on the first information; if the first network element identifier is a network element identifier corresponding to the authentication identity of another network element, then send an error response message to the second network element; if the first network element identifier is not a network element identifier corresponding to the authentication identity of another network element, then set the correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information; wherein, the other network element authentication identity refers to a network element authentication identity that is different from the authentication identity of the second network element.

[0095] In some alternative implementations, before S11 described above, the following S09 is also included:

[0096] S09: Check if the authentication identity of the second network element exists in the first information.

[0097] If the authentication identity of the second network element exists in the first information, then execute S11 as described above. If the authentication identity of the second network element does not exist in the first information, then execute S10 as follows.

[0098] S10: Send an error response message to the second network element; or, based on the first information, check whether the first network element identifier is a network element identifier corresponding to another network element authentication identity; if the first network element identifier is a network element identifier corresponding to another network element authentication identity, then send an error response message to the second network element; if the first network element identifier is not a network element identifier corresponding to another network element authentication identity, then set the correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information; wherein, the other network element authentication identity refers to a network element authentication identity that is different from the authentication identity of the second network element.

[0099] Option 2

[0100] As an optional implementation, the first network element can check whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element through the following steps:

[0101] S21: Determine the network element authentication identity corresponding to the first network element identifier contained in the key generation request message based on the first information;

[0102] S22: Check whether the authentication identity of the second network element is the same as the authentication identity of the network element corresponding to the first network element identifier;

[0103] S231: If the authentication identity of the second network element is the network element authentication identity corresponding to the first network element identifier, then it is determined that there is a correspondence between the first network element identifier and the authentication identity of the second network element.

[0104] Optionally, the following steps may also be included:

[0105] S232: If the authentication identity of the second network element is not the network element authentication identity corresponding to the first network element identifier, then send an error response message to the second network element; or, check whether the authentication identity of the second network element exists in the first information; if the authentication identity of the second network element exists in the first information, then determine the second network element identifier corresponding to the authentication identity of the second network element based on the first information, and use the second network element identifier as the network element identifier used to generate the key; if the authentication identity of the second network element does not exist in the first information, then send an error response message to the second network element.

[0106] In some alternative implementations, before S21 described above, the following S19 is also included:

[0107] S19: Check whether the first network element identifier contained in the key generation request message exists in the first information.

[0108] If the first information contains the first network element identifier included in the key generation request message, then execute S21 as described above. If the first information does not contain the first network element identifier included in the key generation request message, then execute S20 as follows.

[0109] S20: Send an error response message to the second network element; or, set the correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information.

[0110] Step 502: If the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element, then generate a key based on the first network element identifier and send the key to the second network element.

[0111] In this embodiment of the application, the first network element identifier contained in the key generation request message is a sequence number, or empty, or AF_ID (that is, including FQDN and security protocol identifier).

[0112] As an optional approach, the first network element identifier contained in the key generation request message is AF_ID. If the AF_ID contained in the key generation request message corresponds to the authentication identity of the second network element, then a key is generated based on the AF_ID and the key is sent to the second network element.

[0113] As an optional approach, the first network element identifier included in the key generation request message is a sequence number. If the sequence number in the key generation request message corresponds to the authentication identity of the second network element, the AF_ID corresponding to the sequence number is located in the AF_ID set corresponding to the authentication identity of the second network element. A key is then generated based on the AF_ID corresponding to the sequence number and sent to the second network element. Here, since the first network element already stores the AF_ID, and the overhead of the sequence number is much smaller than that of the AF_ID, to save overhead, the sequence number can be carried in the key generation request message instead of the AF_ID itself. The sequence number can be, for example, 0, 1, 2, etc., referring to the sequence number corresponding to the AF_ID. The first network element can locate the AF_ID corresponding to the sequence number in the AF_ID set corresponding to the authentication identity of the second network element.

[0114] In one implementation, the first network element identifier in the key generation request message is empty. A key is generated based on the AF_ID corresponding to the authentication identity of the second network element, and the key is sent to the second network element. Here, if an AF has only one AF_ID, then the AF_ID does not need to be sent in the key generation request message (i.e., the first network element identifier is empty). Instead, the first network element determines the unique AF_ID based on the authentication identity of the second network element. This can significantly reduce overhead.

[0115] Figure 6 This is a flowchart illustrating the key generation method provided in the embodiments of this application. Figure 2 In this example, the first network element is AAnF, and the second network element is AF, such as... Figure 6 As shown, the key generation method includes the following steps:

[0116] On the one hand, the UE should, before interacting with the AKMA application server, obtain information from K... AUSF Derivation of K AKMA And A-KID. On the other hand, AAnF has a pre-configured mapping between AF authentication identities and AF network element identifiers.

[0117] Step 601: The UE sends an application session establishment request message to the AF, which contains the A-KID.

[0118] Here, when the UE initiates communication with the AF, the UE sends an application session establishment request message to the AF, which contains the A-KID. The UE may, before or after sending this message, determine the K... AKMA Derivation of K AF .

[0119] Step 602: AF sends a key generation request message to AAnF, which contains A-KID and AF network element identifier.

[0120] Here, the key generation request message can be Naanf_AKMA_ApplicationKey_Get Request.

[0121] If there is no activation context associated with A-KID in the AF, the AF performs AAnF selection and sends a key generation request message to the selected AAnF. This message contains the A-KID and the AF network element identifier. The AF network element identifier is used to identify the AF and can be a sequence number, empty, or AF_ID. Here, AF_ID includes the AF's FQDN and Ua* protocol identifier, where the Ua* protocol identifier is used to identify the security protocol used between the AF and the UE.

[0122] AAnF should use the AF_ID to check whether it can provide services to AF, based on the configured local policy or the authorization information or policy provided by NRF. If yes, AAnF will execute the following process; otherwise, AAnF should reject the following process.

[0123] Step 603: AAnF checks whether the AF network element identifier in the key generation request message corresponds to the AF authentication identity based on the preset correspondence. If a correspondence exists, the AF_ID that can provide services to the AF is determined.

[0124] As one implementation method, AAnF checks whether the AF network element identifier in the key generation request message corresponds to the AF authentication identity based on a pre-defined correspondence, including the following options:

[0125] Option a) If the AF element identifier in the key generation request message is empty, then determine the AF_ID corresponding to the AF authentication identity based on the correspondence, and use the AF_ID as the AF_ID to provide services to the AF, that is, as the AF_ID used to generate the key. AF AF_ID.

[0126] Option b) If the AF element identifier in the key generation request message is a sequence number (denoted as sequence number 1), then the sequence number set corresponding to the AF authentication identity is determined based on the correspondence. It is then checked whether sequence number 1 belongs to this sequence number set. If it does, the AF_ID corresponding to sequence number 1 in the AF_ID set corresponding to the AF authentication identity is used as the AF_ID to provide services to the AF, i.e., as the AF_ID used to generate the key. AF If the AF_ID does not belong to the given information, the subsequent process can be rejected.

[0127] Option c) If the AF element identifier in the key generation request message is AF_ID (denoted as AF_ID1), then determine the AF_ID set corresponding to the AF authentication identity based on the correspondence, check whether AF_ID1 belongs to the AF_ID set, and if it does, then use AF_ID1 as the AF_ID to provide services to the AF, that is, as the AF_ID used to generate the key. AF If the AF_ID does not belong to the corresponding identity, the subsequent process can be rejected. Alternatively, the corresponding relationship between AF_ID1 and other AF authentication identities can be checked in the corresponding relationship. If they do, the subsequent process can be rejected. If not, the corresponding relationship between AF_ID1 and AF authentication identities can be added.

[0128] In the above scheme, the premise for AAnF to check whether the AF network element identifier in the key generation request message has a correspondence with the AF authentication identity based on the pre-set correspondence is that AAnF finds the AF authentication identity in the correspondence. If AAnF cannot find the AF authentication identity in the correspondence, it can reject the subsequent process, or, provided that the policy allows providing services to AF, it can search the correspondence to see if the AF network element identifier (e.g., AF_ID1) carried in the key generation request message has a correspondence with other AF authentication identities. If so, the subsequent process is rejected; if not, the correspondence between AF_ID1 and the AF authentication identity can be added.

[0129] As another implementation, AAnF checks whether the AF network element identifier (e.g., AF_ID1) in the key generation request message corresponds to the AF authentication identity based on a pre-defined correspondence, including the following options:

[0130] Option A) Determine the AF authentication identity corresponding to AF_ID1 based on the correspondence, and check whether the AF authentication identity corresponding to AF_ID1 matches the AF authentication identity. If they match, then use AF_ID1 as the AF_ID to provide services to the AF, that is, as the one used to generate K. AF If the AF_ID is not specified, the subsequent process can be rejected.

[0131] In the above scheme, AAnF determines the AF authentication identity corresponding to AF_ID1 based on the correspondence relationship, provided that AAnF finds AF_ID1 in the correspondence relationship. If AAnF cannot find AF_ID1 in the correspondence relationship, it can either reject the subsequent process or add the correspondence relationship between AF_ID1 and AF authentication identity, provided that the policy allows it to provide services to AF.

[0132] AAnF can verify whether the corresponding K can be found through A-KID. AKMA (i.e., effective K) AKMA This determines whether a user is authorized to use AKMA.

[0133] If a valid K exists in AAnF AKMA If so, AAnF should continue with step 604.

[0134] If there is no valid K in AAnF AKMA If so, AAnF should continue with step 605 and send an error response.

[0135] Step 604: AAnF according to K AKMA Deducing K AF .

[0136] Here, if AAnF does not have K AFIf so, then AAnF is based on K AKMA Derivation of K AF When AAnF is based on K AKMA Derivation of K AF When the input key of the Key Deduction Function (KDF) is K AKMA The following parameters are used to construct the input S of the KDF:

[0137] -FC = 0x82;

[0138] -P0 = AF_ID;

[0139] -L0 = the length of AF_ID.

[0140] Here, AF_ID refers to the AF_ID that corresponds to the AF authentication identity, or the AF_ID that provides services to the AF. The AF_ID is constructed as follows: AF_ID = AF's FQDN || Ua* Protocol Identifier, where the Ua* Protocol Identifier is used to identify the security protocol used between the AF and the UE.

[0141] Step 605: AAnF sends a key generation response message to AF, which contains K AF K AF Lifecycle (K) AF expTime), SUPI.

[0142] Here, the key generation response message can be Naanf_AKMA_ApplicationKey_Get Response.

[0143] If the information in step 605 indicates that the AKMA key request failed, the AF should reject the application session establishment request and include the error reason in this step. Afterwards, the UE may send a new application session establishment request message to the AF, carrying the new A-KID.

[0144] Step 606: The AF sends an application session establishment response message to the UE.

[0145] The technical solution of this application embodiment, by pre-setting the correspondence between AF authentication identity and AF network element identifier on the AAnF, can check whether the AF network element identifier contained in the key generation request message corresponds to the AF network element authentication identity based on this correspondence. This can prevent legitimate AFs from obtaining the UE's access key to other AFs by sending the AF network element identifiers of other legitimate AFs. AF This prevents the risk of eavesdropping on other legitimate AF access.

[0146] Figure 7 This is a schematic diagram of the structure of the key generation device provided in the embodiments of this application, applied to the first network element, such as...Figure 7 As shown, the key generation device includes:

[0147] The receiving unit 701 is used to receive the key generation request message sent by the second network element;

[0148] Processing unit 702 is used to check whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element; if the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element, then a key is generated based on the first network element identifier;

[0149] The sending unit 703 is used to send the key to the second network element.

[0150] In some optional implementations, the first network element stores first information, which includes the correspondence between the network element authentication identity and the network element identifier;

[0151] The processing unit 702 is used to check, based on the first information, whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element.

[0152] In some optional implementations, in the first information, the network element authentication identity and its corresponding network element identifier are the same content, or the network element authentication identity and its corresponding network element identifier are different content.

[0153] In some alternative implementations, in the first information, one network element authentication identity corresponds to one or more network element identifiers.

[0154] In some optional embodiments, the processing unit 702 is configured to determine the network element identifier corresponding to the authentication identity of the second network element based on the first information; check whether the first network element identifier contained in the key generation request message belongs to the network element identifier corresponding to the authentication identity of the second network element; if the first network element identifier belongs to the network element identifier corresponding to the authentication identity of the second network element, then determine that there is a correspondence between the first network element identifier and the authentication identity of the second network element.

[0155] In some optional embodiments, the processing unit 702 is configured to: send an error response message to the second network element if the first network element identifier does not belong to the network element identifier corresponding to the authentication identity of the second network element; or, check whether the first network element identifier is a network element identifier corresponding to the authentication identity of another network element based on the first information; if the first network element identifier is a network element identifier corresponding to the authentication identity of another network element, send an error response message to the second network element; if the first network element identifier is not a network element identifier corresponding to the authentication identity of another network element, set a correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information; wherein, the other network element authentication identity refers to a network element authentication identity that is different from the authentication identity of the second network element.

[0156] In some optional embodiments, the processing unit 702 is used to check whether the authentication identity of the second network element exists in the first information; if the authentication identity of the second network element exists in the first information, then the network element identifier corresponding to the authentication identity of the second network element is determined based on the first information.

[0157] In some optional embodiments, the processing unit 702 is configured to: send an error response message to the second network element if the authentication identity of the second network element is not present in the first information; or, check whether the first network element identifier is a network element identifier corresponding to the authentication identity of another network element based on the first information; if the first network element identifier is a network element identifier corresponding to the authentication identity of another network element, send an error response message to the second network element; if the first network element identifier is not a network element identifier corresponding to the authentication identity of another network element, set a correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information; wherein, the other network element authentication identity refers to a network element authentication identity that is different from the authentication identity of the second network element.

[0158] In some optional implementations, the processing unit 702 is configured to determine, based on the first information, the network element authentication identity corresponding to the first network element identifier contained in the key generation request message; check whether the authentication identity of the second network element is the network element authentication identity corresponding to the first network element identifier; if the authentication identity of the second network element is the network element authentication identity corresponding to the first network element identifier, then determine that there is a correspondence between the first network element identifier and the authentication identity of the second network element.

[0159] In some optional embodiments, the processing unit 702 is configured to: send an error response message to the second network element if the authentication identity of the second network element is not the network element authentication identity corresponding to the first network element identifier; or check whether the authentication identity of the second network element exists in the first information; if the authentication identity of the second network element exists in the first information, determine the second network element identifier corresponding to the authentication identity of the second network element based on the first information, and use the second network element identifier as the network element identifier for generating the key; if the authentication identity of the second network element does not exist in the first information, send an error response message to the second network element.

[0160] In some optional embodiments, the processing unit 702 is used to check whether the first information contains a first network element identifier included in the key generation request message; if the first information contains a first network element identifier included in the key generation request message, then the network element authentication identity corresponding to the first network element identifier included in the key generation request message is determined based on the first information.

[0161] In some optional embodiments, the processing unit 702 is configured to send an error response message to the second network element if the first network element identifier contained in the key generation request message is not present in the first information; or, set a correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information.

[0162] In some optional implementations, the first network element identifier included in the key generation request message may be a sequence number, or empty, or may include an FQDN and a security protocol identifier.

[0163] In some alternative implementations, the first network element is AAnF and the second network element is AF.

[0164] Those skilled in the art should understand that Figure 7 The functions of each unit in the key generation device shown can be understood by referring to the relevant descriptions of the aforementioned method. Figure 7 The functions of each unit in the key generation device shown can be implemented by a program running on a processor or by specific logic circuits.

[0165] Figure 8 This is a schematic structural diagram of a communication device 800 provided in an embodiment of this application. Figure 8 The communication device 800 shown includes a processor 810, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0166] Optionally, such asFigure 8 As shown, the communication device 800 may further include a memory 820. The processor 810 can retrieve and run computer programs from the memory 820 to implement the methods described in this embodiment.

[0167] The memory 820 can be a separate device independent of the processor 810, or it can be integrated into the processor 810.

[0168] Optionally, such as Figure 8 As shown, the communication device 800 may also include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0169] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0170] The communication device 800 may specifically be a network device (such as the first network element) in the embodiments of this application, and the communication device 800 may implement the corresponding processes implemented by the network device (such as the first network element) in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0171] Figure 9 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 9 The chip 900 shown includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0172] Optionally, such as Figure 9 As shown, chip 900 may further include memory 920. Processor 910 can retrieve and run computer programs from memory 920 to implement the methods described in this embodiment.

[0173] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0174] Optionally, the chip 900 may also include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0175] Optionally, the chip 900 may also include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0176] The chip can be applied to network devices (such as the first network element) in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device (such as the first network element) in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0177] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0178] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0179] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0180] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0181] This application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to a network device (such as a first network element) in the embodiments of this application, and the computer program causes a computer to execute the corresponding processes implemented by the network device (such as the first network element) in the various methods of the embodiments of this application. For the sake of brevity, further details are omitted here.

[0182] This application also provides a computer program product, including computer program instructions. This computer program product can be applied to network devices (such as a first network element) in the embodiments of this application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the network device (such as the first network element) in the various methods of the embodiments of this application. For the sake of brevity, further details are omitted here.

[0183] This application also provides a computer program. This computer program can be applied to the network device (such as the first network element) in the embodiments of this application. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the network device (such as the first network element) in the various methods of the embodiments of this application. For the sake of brevity, these will not be elaborated further here.

[0184] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0185] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0186] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0187] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0188] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0189] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0190] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A key generation method, characterized in that, The method includes: After receiving the key generation request message sent by the second network element, the first network element checks whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element. If the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element, then a key is generated based on the first network element identifier and the key is sent to the second network element; wherein, when the first network element identifier is empty, the authentication identity of the second network element is used by the first network element to generate the key based on the network element identifier corresponding to the authentication identity of the second network element; The first network element obtains first information, which includes the correspondence between the network element's authentication identity and the network element's identifier; The step of checking whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element includes: Based on the first information, check whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element.

2. The method according to claim 1, characterized in that, In the first information, the network element authentication identity and its corresponding network element identifier are the same content, or the network element authentication identity and its corresponding network element identifier are different content.

3. The method according to claim 1, characterized in that, In the first information, one network element authentication identity corresponds to one or more network element identifiers.

4. The method according to claim 1, characterized in that, The step of checking whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element based on the first information includes: Based on the first information, determine the network element identifier corresponding to the authentication identity of the second network element; Check whether the first network element identifier contained in the key generation request message belongs to the network element identifier corresponding to the authentication identity of the second network element; If the first network element identifier belongs to the network element identifier corresponding to the authentication identity of the second network element, then it is determined that there is a corresponding relationship between the first network element identifier and the authentication identity of the second network element.

5. The method according to claim 4, characterized in that, The method further includes: If the first network element identifier does not belong to the network element identifier corresponding to the authentication identity of the second network element, then: Send an error response message to the second network element; or, Based on the first information, check whether the first network element identifier is a network element identifier corresponding to another network element authentication identity; if the first network element identifier is a network element identifier corresponding to another network element authentication identity, then send an error response message to the second network element; if the first network element identifier is not a network element identifier corresponding to another network element authentication identity, then set the correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information; wherein, the other network element authentication identity refers to a network element authentication identity that is different from the authentication identity of the second network element.

6. The method according to claim 4, characterized in that, Before determining the network element identifier corresponding to the authentication identity of the second network element based on the first information, the method further includes: checking whether the authentication identity of the second network element exists in the first information; The step of determining the network element identifier corresponding to the authentication identity of the second network element based on the first information includes: if the authentication identity of the second network element exists in the first information, then determining the network element identifier corresponding to the authentication identity of the second network element based on the first information.

7. The method according to claim 6, characterized in that, The method further includes: If the authentication identity of the second network element is not found in the first information, then: Send an error response message to the second network element; or, Based on the first information, check whether the first network element identifier is a network element identifier corresponding to another network element authentication identity; if the first network element identifier is a network element identifier corresponding to another network element authentication identity, then send an error response message to the second network element; if the first network element identifier is not a network element identifier corresponding to another network element authentication identity, then set the correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information; wherein, the other network element authentication identity refers to a network element authentication identity that is different from the authentication identity of the second network element.

8. The method according to claim 1, characterized in that, The step of checking whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element based on the first information includes: Based on the first information, determine the network element authentication identity corresponding to the first network element identifier contained in the key generation request message; Check whether the authentication identity of the second network element is the same as the authentication identity of the network element corresponding to the first network element identifier; If the authentication identity of the second network element is the same as the authentication identity of the first network element identifier, then it is determined that there is a correspondence between the first network element identifier and the authentication identity of the second network element.

9. The method according to claim 8, characterized in that, The method further includes: If the authentication identity of the second network element is not the network element authentication identity corresponding to the first network element identifier, then: Send an error response message to the second network element; or, Check if the first information contains the authentication identity of the second network element; if the first information contains the authentication identity of the second network element, determine the second network element identifier corresponding to the authentication identity of the second network element based on the first information, and use the second network element identifier as the network element identifier used to generate the key; if the first information does not contain the authentication identity of the second network element, send an error response message to the second network element.

10. The method according to claim 8, characterized in that, Before determining the network element authentication identity corresponding to the first network element identifier contained in the key generation request message based on the first information, the method further includes: checking whether the first network element identifier contained in the key generation request message exists in the first information; The step of determining the network element authentication identity corresponding to the first network element identifier contained in the key generation request message based on the first information includes: if the first information contains the first network element identifier contained in the key generation request message, then determining the network element authentication identity corresponding to the first network element identifier contained in the key generation request message based on the first information.

11. The method according to claim 10, characterized in that, The method further includes: If the first network element identifier contained in the key generation request message is not present in the first information, then: Send an error response message to the second network element; or, Set the correspondence between the first network element identifier and the authentication identity of the second network element, and add the correspondence between the authentication identity of the second network element and the first network element identifier to the first information.

12. The method according to any one of claims 1 to 11, characterized in that, The first network element identifier contained in the key generation request message is either a sequence number, empty, or includes a fully qualified domain name (FQDN) and a security protocol identifier.

13. The method according to any one of claims 1 to 11, characterized in that, The first network element is the Authentication and Key Management (AKMA) anchor function (AAnF), and the second network element is the application function (AF).

14. A key generation device, characterized in that, Applied to the first network element, the device includes: The receiving unit is used to receive the key generation request message sent by the second network element; The processing unit is configured to check whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element; if the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element, then a key is generated based on the first network element identifier; wherein, when the first network element identifier is empty, the authentication identity of the second network element is used by the first network element to generate the key based on the network element identifier corresponding to the authentication identity of the second network element; A sending unit is used to send the key to the second network element; The first network element stores first information, which includes the correspondence between the network element authentication identity and the network element identifier; The processing unit is configured to check, based on the first information, whether the first network element identifier contained in the key generation request message corresponds to the authentication identity of the second network element.

15. A network device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 13.

16. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 13.

17. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 13.

Images