Communication method and communication device

By sending a response message to the first gateway from the terminal device to indicate whether 5G key architecture is supported, the problem of AUN3 devices and 5G-RG being unable to determine the key architecture is solved, realizing an effective solution for secure communication under different architectures and improving communication security and efficiency.

CN118945649APending Publication Date: 2024-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202310539755.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When establishing a connection between AUN3 devices and 5G-RG, existing technologies cannot determine whether the terminal device supports the 5G key architecture, resulting in insecure communication.

Method used

The terminal device sends a response message to the first gateway, indicating whether it supports the first key architecture. This allows the network side to select an appropriate key deduction method to generate a key based on the actual situation, thus ensuring communication security.

Benefits of technology

It improves communication security, ensuring that terminal devices and the network side can generate correct keys regardless of whether they support or not the 5G key architecture, thereby enhancing the security and efficiency of information transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945649A_ABST
    Figure CN118945649A_ABST
Patent Text Reader

Abstract

The communication method comprises the following steps: in an authentication process of terminal equipment and a first gateway, the terminal equipment sends a message indicating whether the terminal equipment supports a first key architecture to the first gateway, so that the first gateway can accurately judge whether the terminal equipment supports the first key architecture and report the first key architecture to a network side; the terminal device can deduce to obtain the first key for security protection according to whether the terminal device supports the first key architecture, and the network side can also deduce to obtain the first key. The terminal equipment supports or does not support the first key architecture, and the deduction modes of the first key are different. According to the embodiment of the invention, the terminal equipment can report whether the terminal equipment supports the first key architecture or not, so that the terminal equipment and a network side select a proper deduction mode to generate a required key, and the communication security is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Art

[0002] After the authenticable non-the 3rd generation partnership project (AUN3) device and the fifth generation (5G) residential gateway (5G-RG) establish a connection, the AUN3 device can access the 5G core network (5G core network, 5GC) through the 5G-RG. In order to improve the security of communication, the AUN3 device and the 5G-RG can use keys to securely protect the established connection. Among them, the keys used by the AUN3 device and the 5G-RG can be generated using different deduction methods depending on whether the AUN3 device supports the 5G key architecture. Therefore, only when it is determined whether the AUN3 device supports the 5G key architecture can the corresponding deduction method be used to generate the correct key, otherwise the AUN3 device and the 5G-RG cannot communicate securely. Summary of the invention

[0003] The embodiment of the present application provides a communication method to improve the security of communication.

[0004] In a first aspect, a communication method is provided, which can be executed by a terminal device, or can also be executed by a component (such as a chip or circuit) of the terminal device, without limitation. The terminal device includes a terminal device or other device that needs to access a core network through a first gateway.

[0005] The communication method includes: receiving a first request message from a first gateway, the first request message is used to request identity information of a terminal device, the terminal device accesses a core network through a connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; sending a first response message to the first gateway, the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; receiving a message from the first gateway indicating that the identity authentication is successful; generating a first key according to whether the terminal device supports the first key architecture, and the first key is used to securely protect the connection between the terminal device and the first gateway.

[0006] Based on the above scheme, the terminal device can report whether it supports the first key architecture through the first response message, so that the 5G-RG can learn whether the terminal device supports the first key architecture based on the first response message and report it to the network side. The key deduction methods corresponding to the terminal device supporting the first key architecture and the terminal device not supporting the first key architecture are different. When the network side learns whether the terminal device supports the first key architecture, it can select a suitable deduction method to generate the required key. The terminal device can also deduce the first key for security protection based on whether it supports the first key architecture to improve the security of communication.

[0007] In combination with the first aspect, in certain implementations of the first aspect, generating the first key according to whether the terminal device supports the first key architecture includes: generating the first key according to a first key deduction method when the terminal device supports the first key architecture; generating the first key according to a second key deduction method when the terminal device does not support the first key architecture.

[0008] The first key derivation method and the second key derivation method are different. In this way, when determining whether the terminal device supports the first key architecture, the terminal device can generate a correct key according to the corresponding derivation method.

[0009] In combination with the first aspect, in some implementations of the first aspect, the first response message is used to indicate whether the terminal device supports the first key architecture, including: the identity information is used to indicate whether the terminal device supports the first key architecture. In this way, directly indicating whether the terminal device supports the first key architecture through identity information can improve information transmission efficiency.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the identity information is used to indicate whether the terminal device supports the first key architecture, including: when the identity information is a first identifier, the identity information is used to indicate that the terminal device does not support the first key architecture; or, when the identity information is a second identifier, the identity information is used to indicate that the terminal device supports the first key architecture.

[0011] For example, the identity information is a permanent user identifier of the terminal device, indicating that the terminal device does not support the first key architecture; the identity information is a hidden user identifier of the terminal device, indicating that the terminal device supports the first key architecture.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the identity information is used to indicate whether the terminal device supports the first key architecture, including: when the identity information is a first type of a first identifier, the identity information is used to indicate that the terminal device does not support the first key architecture; or, when the identity information is a second type of a first identifier, the identity information is used to indicate that the terminal device supports the first key architecture.

[0013] For example, the identity information is a hidden user identifier of the terminal device, and when the type of the hidden user identifier is an international mobile user identity code, the identity information indicates that the terminal device does not support the first key architecture; or, when the type of the hidden user identifier is a network access identifier, the identity information indicates that the terminal device supports the first key architecture.

[0014] In combination with the first aspect, in some implementations of the first aspect, the identity information is used to indicate whether the terminal device supports the first key architecture, including: the identity information includes a field for indicating whether the terminal device supports the first key architecture.

[0015] For example, the identity information is a user permanent identifier of the terminal device, and a user name part or a domain name part of the user permanent identifier indicates whether the terminal device supports the first key architecture.

[0016] For example, the identity information is a user hidden identifier of the terminal device, and the user hidden identifier includes a field for indicating whether the terminal device supports the first key architecture.

[0017] In combination with the first aspect, in certain implementations of the first aspect, the first response message also includes first indication information; the first response message is used to indicate whether the terminal device supports the first key architecture, including: the first indication information is used to indicate whether the terminal device supports the first key architecture.

[0018] For example, the first indication information includes at least one of the following: character string information, bit information or a non-access layer protocol data unit.

[0019] Such explicit first indication information is helpful for the message recipient to quickly and accurately know whether the terminal device supports the first key architecture. In addition, the first indication information can be in a variety of forms, which increases the flexibility of the solution.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the first response message also includes second indication information, and the second indication information is used to indicate whether the terminal device supports the non-access layer NAS protocol, wherein the terminal device supports the NAS protocol, indicating that the terminal device can generate and process NAS messages.

[0021] Based on the above scheme, the service network name determined by the terminal device can be a preset fixed value, the PLMN ID of the terminal device, the PLMN ID of the access mobile management network element serving the first gateway, and other values ​​that the terminal device can determine, so that the two-way authentication process between the terminal device and the core network can proceed smoothly.

[0022] In combination with the first aspect, in certain implementations of the first aspect, before receiving a message from the first gateway indicating that the identity authentication is successful, the method also includes: determining a service network name, the service network name is used for the identity authentication, and the service network name includes at least one of the following: a preset fixed value, a PLMN ID of the terminal device, or a PLMN ID of an access mobility management network element serving the first gateway.

[0023] Based on the above scheme, the service network name determined by the terminal device can be a preset fixed value, the PLMN ID of the terminal device, the PLMN ID of the access mobile management network element serving the first gateway, and other values ​​that the terminal device can determine, so as to facilitate the terminal device to perform a two-way authentication process.

[0024] In combination with the first aspect, in some implementations of the first aspect, before receiving the first request message from the first gateway, the method also includes: determining an access method for accessing the first gateway, the access method including trusted non-Third Generation Partnership Project 3GPP access or untrusted non-3GPP access.

[0025] In combination with the first aspect, in some implementations of the first aspect, the first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

[0026] In a second aspect, a communication method is provided. The method may be executed by a first gateway, or may be executed by a component (such as a chip or a circuit) of the first gateway. There is no limitation on this. For ease of description, the method is described below by taking the execution by the first gateway as an example.

[0027] The communication method includes: sending a first request message to a terminal device, the first request message is used to request the identity information of the terminal device, the terminal device accesses the core network through the connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; receiving a first response message from the terminal device, the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; sending the identity information and indication information for indicating whether the terminal device supports the first key architecture to an access mobility management network element, the access mobility management network element is located in the core network; receiving a message indicating that the identity authentication is successful and a fifth key from the access mobility management network element, the fifth key is generated based on whether the terminal device supports the first key architecture; sending a message indicating that the identity authentication is successful to the terminal device; generating a first key based on the fifth key, and the first key is used to securely protect the connection between the terminal device and the first gateway.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the fifth key is generated based on whether the terminal device supports the first key architecture, including: when the terminal device supports the first key architecture, the fifth key is generated according to the first key deduction method; when the terminal device does not support the first key architecture, the fifth key is generated according to the second key deduction method.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the sending of the identity information and the indication information for indicating whether the terminal device supports the first key architecture (hereinafter referred to as the fourth indication information, where the fourth indication information can be the identity information of the terminal device or the first indication information mentioned above) to the access mobility management network element includes: sending the identity information and the indication information for indicating whether the terminal device supports the first key architecture to the access mobility management network element through a non-access layer NAS registration request message; wherein the first response message includes the NAS registration request message, or the NAS registration request message is generated by the first gateway based on the first response message.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: the first gateway sends an indication information (hereinafter referred to as the third indication information) to the access mobility management network element for instructing the device initiating the registration request to access the core network through the connection between the first gateway and the first gateway.

[0031] In combination with the second aspect, in some implementations of the second aspect, the first response message is used to indicate whether the terminal device supports the first key architecture, including: the identity information is used to indicate whether the terminal device supports the first key architecture.

[0032] In combination with the second aspect, in some implementations of the second aspect, the first response message also includes first indication information; the first response message is used to indicate whether the terminal device supports the first key architecture, including: the first indication information is used to indicate whether the terminal device supports the first key architecture.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the NAS registration request message also includes fifth indication information, and the fifth indication information is used to indicate whether the terminal device supports the NAS protocol, wherein the terminal device supports the NAS protocol, indicating that the terminal device can generate and process NAS messages.

[0034] In combination with the second aspect, in certain implementations of the second aspect, the first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

[0035] The technical effects of the method shown in the above second aspect and its possible design can refer to the technical effects in the first aspect and its possible design.

[0036] According to a third aspect, a communication system is provided, including: a first gateway sends a first request message to a terminal device, the first request message is used to request identity information of the terminal device, the terminal device accesses a core network through a connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; the terminal device sends a first response message to the first gateway, the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; the first network element obtains a message indicating that the identity authentication is successful and a fifth key, and the fifth key is generated based on whether the terminal device supports the first key architecture; the first gateway sends a message to the terminal device indicating that the identity authentication is successful; the terminal device generates a first key according to whether the terminal device supports the first key architecture, and the first key is used to securely protect the connection between the terminal device and the first gateway, and the first gateway generates the first key according to the fifth key.

[0037] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: an access mobility management network element receives the identity information and indication information for indicating whether the terminal device supports the first key architecture from the first gateway; the access mobility management network element generates the fifth key based on whether the terminal device supports the first key architecture; and the access mobility management network element sends the fifth key to the first gateway.

[0038] In a fourth aspect, a communication system is provided, the communication system comprising a terminal device and a first gateway, wherein:

[0039] The first gateway is used to: send a first request message to the terminal device, the first request message is used to request the identity information of the terminal device, the terminal device accesses the core network through the connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; the terminal device is used to: send a first response message to the first gateway, the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; the first network element is also used to: obtain a message indicating that the identity authentication is successful and a fifth key, and the fifth key is generated based on whether the terminal device supports the first key architecture; the first gateway is also used to: send a message indicating that the identity authentication is successful to the terminal device; the terminal device is also used to: generate a first key according to whether the terminal device supports the first key architecture, and the first key is used to securely protect the connection between the terminal device and the first gateway; the first gateway is also used to: generate the first key according to the fifth key.

[0040] In combination with the fourth aspect, in certain implementations of the fourth aspect, the system also includes an access mobility management network element, wherein: the access mobility management network element is used to: receive the identity information and indication information indicating whether the terminal device supports the first key architecture from the first gateway; the access mobility management network element is also used to: generate the fifth key according to whether the terminal device supports the first key architecture; the access mobility management network element is also used to: send the fifth key to the first gateway.

[0041] In combination with the fourth aspect, in certain implementations of the fourth aspect, the authentication request message includes a service network name, and the service network name is used for the identity authentication, and the service network name includes at least one of the following: a preset fixed value, a PLMN ID of the terminal device, or a PLMN ID of an access mobile management network element serving the first gateway.

[0042] In combination with the fourth aspect, in certain implementations of the fourth aspect, the NAS registration request message also includes fifth indication information, and the fifth indication information is used to indicate whether the terminal device supports the NAS protocol, wherein the terminal device supports the NAS protocol, indicating that the terminal device can generate and process NAS messages.

[0043] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the fifth indication information indicates that the terminal device supports the NAS protocol, the access mobility management network element is further used to generate a NAS key based on the fifth key and the identifier of the terminal device; the access mobility management network element is further used to execute a NAS SMC process between the terminal device and the NAS key.

[0044] In combination with the fourth aspect, in certain implementations of the fourth aspect, the authentication request message also includes sixth indication information, and the sixth indication information is used to indicate that the device to be authenticated is a terminal device that accesses the core network through a connection between the first gateway.

[0045] In combination with the fourth aspect, in certain implementations of the fourth aspect, the authentication network element is also used to send an acquisition request message to the data management network element, the acquisition request message is used to request the acquisition of the authentication vector required for authentication, and the acquisition request message includes the identifier of the terminal device; the authentication network element is also used to receive an acquisition response message from the data management network element, and the acquisition response message includes information about the authentication vector.

[0046] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

[0047] The technical effects of the method shown in the above fourth aspect and its possible design can refer to the technical effects in the first aspect and its possible design.

[0048] In the fifth aspect, a communication method is provided. The method can be executed by a data management network element, or can also be executed by a component of the data management network element (such as a chip or circuit). There is no limitation on this. For the sake of ease of description, the following is explained using the execution by the data management network element as an example.

[0049] The communication method includes: a data management network element receives an acquisition request message from an authentication network element, the acquisition request message is used to request the acquisition of an authentication vector required for authentication, and the acquisition request message includes the identification of an authenticatable non-third generation partnership project terminal device; the data management network element sends an acquisition response message to the authentication network element, the acquisition response message includes information about the authentication vector and seventh indication information, the seventh indication information is used to indicate whether the terminal device supports a first key architecture, wherein the information about the authentication vector and the seventh indication information are obtained based on the identification of the terminal device.

[0050] Based on the above scheme, the data management network element can provide indication information for indicating whether the terminal device supports the first key architecture, so that the network side can know whether the terminal device supports the first key architecture, and select an appropriate deduction method to generate the required key to improve the security of communication.

[0051] In combination with the fifth aspect, in some implementations of the fifth aspect, the method further includes: the data management network element selects an authentication method according to an identifier of the terminal device, and determines the authentication vector corresponding to the authentication method.

[0052] In combination with the fifth aspect, in certain implementations of the fifth aspect, the method also includes: the data management network element determines the contract data of the terminal device based on the identifier of the terminal device, and the contract data of the terminal device includes the seventh indication information; or, the data management network element determines the contract data of the terminal device based on the identifier of the terminal device, and determines whether the terminal device supports the first key architecture based on the contract data of the terminal device.

[0053] Based on the above solution, the data management network element can determine whether the terminal device supports the first key architecture in different ways, thereby improving the flexibility of the solution.

[0054] In combination with the fifth aspect, in certain implementations of the fifth aspect, the acquisition response message also includes eighth indication information, and the eighth indication information is used to indicate whether the terminal device supports the non-access layer NAS protocol, wherein the terminal device supports the NAS protocol, indicating that the terminal device can generate and process NAS messages.

[0055] Based on the above scheme, the data management network element can indicate whether the terminal device supports the NAS protocol through the eighth indication information, so that the network side can obtain information on whether the terminal device supports the NAS protocol based on the eighth indication information, so as to facilitate the subsequent mobile management network element on the network side to determine whether to execute the NAS SMC process with the terminal device.

[0056] In the sixth aspect, a communication method is provided. The method can be executed by an access mobility management network element, or can also be executed by a component of the access mobility management network element (such as a chip or circuit). There is no limitation on this. For the sake of ease of description, the following is explained using the execution by the access mobility management network element as an example.

[0057] The communication method comprises: receiving, by an access mobility management network element, a NAS registration request message from a first gateway, the NAS registration request message comprising third indication information, the third indication information being used to indicate that a device initiating the registration request is an authenticable non-third generation partnership project terminal device; determining, by the access mobility management network element, that the registration request is initiated by the terminal device according to the third indication information; sending, by the access mobility management network element, an authentication request message to an authentication network element, the authentication request message being used to request the authentication network element to authenticate the terminal device; receiving, by the access mobility management network element, an authentication response message from the authentication network element, the authentication response message comprising a third key and ninth indication information, the ninth indication information being used to indicate whether the terminal device supports a first key architecture; generating, by the access mobility management network element, a fifth key according to whether the terminal device supports the first key architecture and the third key; sending, by the access mobility management network element, the fifth key to the first gateway; wherein, the fifth key generation modes corresponding to the terminal device supporting the first key architecture and the terminal device not supporting the first key architecture are different.

[0058] In combination with the sixth aspect, in certain implementations of the sixth aspect, the authentication request message also includes a service network name, and the service network name is used for the identity authentication, and the service network name includes at least one of the following: a preset fixed value, a PLMN ID of the terminal device, or a PLMN ID of an access mobile management network element serving the first gateway.

[0059] In combination with the sixth aspect, in certain implementations of the sixth aspect, the authentication request message also includes sixth indication information, and the sixth indication information is used to indicate that the device to be authenticated is a terminal device that accesses the core network through a connection between the first gateway.

[0060] In combination with the sixth aspect, in certain implementations of the sixth aspect, the first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

[0061] In combination with the sixth aspect, in certain implementations of the sixth aspect, the authentication response message also includes tenth indication information, and the tenth indication information is used to indicate whether the terminal device supports the NAS protocol, wherein the terminal device supports the NAS protocol, indicating that the terminal device can generate and process NAS messages.

[0062] In combination with the sixth aspect, in certain implementations of the sixth aspect, when the tenth indication information indicates that the terminal device supports the NAS protocol, the method further includes: the access mobility management network element generates a NAS key based on the fifth key and the identifier of the terminal device; and the access mobility management network element executes a NAS SMC process between the terminal device and the NAS key.

[0063] The technical effects of the method shown in the sixth aspect and its possible design above can refer to the technical effects in the fourth aspect and its possible design.

[0064] In the seventh aspect, a communication method is provided. The method can be executed by an authentication network element, or can also be executed by a component of the authentication network element (such as a chip or circuit). There is no limitation on this. For the sake of ease of description, the following is explained using the execution by the authentication network element as an example.

[0065] The communication method comprises: an authentication network element receives an authentication request message from an access mobility management network element, the authentication request message is used to request the authentication network element to authenticate an authenticable non-third generation partnership project terminal device, and the authentication request message includes the identifier of the terminal device; the authentication network element sends an acquisition request message to a data management network element, the acquisition request message is used to request to acquire an authentication vector required for authentication, and the acquisition request message includes the identifier of the terminal device; the authentication network element receives an acquisition response message from the data management network element, the acquisition response message includes information about the authentication vector and seventh indication information, and the seventh indication information is used to indicate whether the terminal device supports a first key architecture; the authentication network element generates a third key according to whether the terminal device supports the first key architecture and the identifier of the terminal device; the authentication network element sends an authentication response message to the access mobility management network element, the authentication response message includes the third key and ninth indication information, and the ninth indication information is used to indicate whether the terminal device supports the first key architecture; wherein the third key generation modes corresponding to the terminal device supporting the first key architecture and the terminal device not supporting the first key architecture are different.

[0066] In combination with the seventh aspect, in some implementations of the seventh aspect, the method further includes: the authentication network element performing two-way authentication with the terminal device based on the authentication vector.

[0067] In combination with the seventh aspect, in certain implementations of the seventh aspect, the authentication request message also includes sixth indication information, and the sixth indication information is used to indicate that the device to be authenticated is a terminal device that accesses the core network through a connection between the first gateway.

[0068] In combination with the seventh aspect, in certain implementations of the seventh aspect, the acquisition response message also includes eighth indication information, and the eighth indication information is used to indicate whether the terminal device supports the non-access layer NAS protocol, wherein the terminal device supports the NAS protocol, indicating that the terminal device can generate and process NAS messages.

[0069] In combination with the seventh aspect, in certain implementations of the seventh aspect, the authentication response message also includes tenth indication information, and the tenth indication information is used to indicate whether the terminal device supports the NAS protocol.

[0070] In the eighth aspect, a communication system is provided, including a data management network element, an access mobility management network element, and an authentication network element, wherein the data management network element is used to execute the method shown in the fifth aspect, the access mobility management network element executes the method shown in the sixth aspect, and the authentication network element executes the method shown in the seventh aspect.

[0071] In a ninth aspect, a communication device is provided, which includes: a transceiver unit and a processing unit, the transceiver unit is used to execute the steps of sending and receiving information in the methods provided by the above aspects, and the processing unit is used to execute the steps of processing in the methods provided by the above aspects.

[0072] In a tenth aspect, a communication device is provided, which includes: a memory for storing programs; a processor for executing the programs stored in the memory, and when the programs stored in the memory are executed, the processor is used to execute the methods provided in the above aspects.

[0073] In the eleventh aspect, the present application provides a processor for executing the methods provided in the above aspects. In the process of executing these methods, the process of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the transceiver so that it can be transmitted by the transceiver. After being output by the processor, the above information may also need to be processed otherwise before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver obtains / receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed otherwise before being input into the processor.

[0074] Based on the above principle, for example, the receiving request message mentioned in the above method can be understood as the processor receiving input information.

[0075] For the operations such as transmission, sending and acquisition / reception involved in the processor, unless otherwise specified, or unless they conflict with their actual functions or internal logic in the relevant descriptions, they can be more generally understood as processor output, reception, input and other operations, rather than transmission, sending and receiving operations performed directly by the RF circuit and antenna.

[0076] In the implementation process, the processor may be a processor specifically used to execute these methods, or a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately arranged on different chips. The embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor.

[0077] In a twelfth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a program for executing the methods provided in the above aspects.

[0078] In a thirteenth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is used to execute the methods provided in the above aspects.

[0079] In a fourteenth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface to execute the methods provided in the above aspects.

[0080] Optionally, as an implementation manner, the chip may further include a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the methods provided by the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] Figure 1 It is a schematic diagram of the network architecture 100 provided in this application.

[0082] Figure 2 (a) and (b) are schematic diagrams of non-3GPP access provided in an embodiment of the present application.

[0083] Figure 3 This is a schematic diagram of the registration process of a terminal device through a non-trusted non-3GPP provided in an embodiment of the present application.

[0084] Figure 4 This is a schematic diagram of the registration process of a terminal device through a trusted non-3GPP provided in an embodiment of the present application.

[0085] Figure 5 This is a schematic diagram of an AUN3 device that does not support the 5G key architecture accessing 5GC provided in an embodiment of the present application.

[0086] Figure 6 This is a schematic diagram of an AUN3 device supporting a 5G key architecture accessing a 5GC provided in an embodiment of the present application.

[0087] Figure 7 This is a schematic diagram of a non-5G key architecture provided in an embodiment of the present application.

[0088] Figure 8 This is a schematic diagram of the 5G key architecture provided in an embodiment of the present application.

[0089] Fig. 9 It is a schematic flow chart of a communication method provided by the present application.

[0090] Fig.10 It is a schematic flow chart of another communication method provided by the present application.

[0091] Fig.11 It is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.

[0092] Fig.12 It is a schematic diagram of another communication device 20 provided in an embodiment of the present application.

[0093] Fig.13 It is a schematic diagram of a chip system 30 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0095] The technical solutions of the embodiments of the present application can be applied to various communication systems. For example: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system.

[0096] In order to facilitate understanding of the communication method provided below, first combine Figure 1 The following describes communication scenarios to which the communication method provided in the embodiments of the present application is applicable.

[0097] Figure 1It is a schematic diagram of the network architecture 100 provided in the present application, including the following devices (or gateways, nodes, network elements, etc.): AUN3 device, 5G-RG, wireless access gateway function (wireline access gateway function, W-AGF) and core network (core network, CN).

[0098] The core network includes but is not limited to the following network functions (or referred to as equipment, gateway, network element, network function network element or node): access and mobility management function (AMF), session management function (SMF), user plane function (UPF), unified data management function (UDM) and authentication server function (AUSF), etc. UDM and AUSF are not shown in the figure. The functions of each device are briefly described below.

[0099] 1. AUN3 equipment: Figure 1 As shown in , devices that access the core network through 5G-RG are collectively referred to as AUN3 devices. If an AUN3 device wants to access the core network, it must first connect to the 5G-RG and then access the core network through the 5G-RG.

[0100] The AUN3 device in the embodiment of the present application is a device with wireless transceiver functions, which can communicate indirectly using one or more CN devices via 5G-RG (or also called access device).

[0101] For example, the AUN3 device can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0102] 2. 5G-RG: It is both a fixed network device and a terminal device. 5G-RG is a residential gateway (RG) that can register to the core network. From the perspective of the core network, 5G-RG plays the role of a terminal device. 5G-RG communicates with the core network through a communication interface (such as Figure 1 The N1 interface shown in FIG. 4 communicates with the UE.

[0103] Exemplarily, 5G-RG may also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent or user device, etc. 5G-RG can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). 5G-RG can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. Alternatively, 5G-RG can also be a handheld device with wireless communication function, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device or a terminal in the Internet of Things, the Internet of Vehicles, a terminal of any form in a 5G network and a future network, or a terminal in a future evolving 6G network, etc.

[0104] 3. W-AGF: It can also be called (access gateway function, AGF). There is a connection between 5G-RG and W-AGF, which is used to transmit control plane messages and user plane messages exchanged between AUN3 devices and the core network. Among them, the control plane message can also be called non-access stratum (NAS) message.

[0105] For example, after receiving the uplink user plane message from the AUN3 device through the 5G-RG, the W-AGF identifies the protocol data unit (PDU) session and quality of service (QoS) flow corresponding to the uplink user plane message, and sends the uplink user plane message to the UPF through the N3 interface. The purpose of identifying the PDU session and QoS flow corresponding to the uplink user plane message is to determine the processing rules corresponding to the message, so as to process the downlink user plane message.

[0106] For example, after W-AGF receives a downlink user plane message from the core network, it can add an identifier to the downlink user plane message so that the AUN3 device can identify the PDU session and QoS flow to which the downlink user plane message belongs, and then process the downlink user plane message according to the processing rules corresponding to the PDU session and QoS flow.

[0107] 4. AMF: Responsible for the access control and mobility management of terminal devices (such as the above-mentioned 5G-RG) to the operator network, such as mobile state management, allocation of user temporary identity, authentication and authorization of users, etc. For example, in an embodiment of the present application, AMF can determine whether the AUN3 device that initiates the registration request supports the 5G key architecture based on the information sent by the 5G-RG, and when determining whether the AUN3 device supports the 5G key architecture, it can generate the correct key based on the corresponding deduction method.

[0108] 5. SMF: responsible for managing the PDU session of 5G-RG, for example, establishing, maintaining and deleting PDU sessions. Among them, PDU session is a channel for transmitting PDU. 5G-RG and the data network transmit PDU to each other through PDU session. SMF includes session management (such as session establishment, modification and release), service and session continuity (SSC) mode selection, roaming and other session-related functions. Figure 1 In the scenario shown, the PDU session established between 5G-RG and SMF can be used to transfer data of AUN3 device.

[0109] 6. UPF: UPF includes user-plane related functions such as packet routing and transmission, packet detection, service usage reporting, QoS processing, legal monitoring, uplink packet detection, and downlink packet storage.

[0110] 7. UDM: responsible for storing information such as subscriber permanent identifier (SUPI) of subscribers in the operator network, generic public subscription identifier (GPSI) of subscribers, and credentials. SUPI will be encrypted during transmission, and the encrypted SUPI is called a hidden subscriber subscription identifier (SUCI). The information stored in UDM can be used for authentication and authorization of terminal devices to access the operator network. Among them, the subscribers of the above-mentioned operator network can specifically be users who use the services provided by the operator network, such as users who use China Telecom's subscriber identity module (SIM) card, or users who use China Mobile's SIM card. The credentials of the above-mentioned subscribers can be a small file storing long-term keys stored in the SIM card or information related to SIM card encryption, which is used for authentication and / or authorization. It should be noted that permanent identifiers, credentials, security contexts, authentication data (cookies), and tokens are equivalent to verification / authentication and authorization-related information. In the embodiments of the present application, no distinction or restriction is made for the convenience of description.

[0111] 8. AUSF: Usually used for primary authentication, i.e. authentication between the terminal device (subscriber) and the operator network. After receiving the authentication request initiated by the subscriber, AUSF can authenticate and / or authorize the subscriber through the authentication information and / or authorization information stored in the UDM, or generate the authentication and / or authorization information of the subscriber through the UDM. AUSF can feedback the authentication information and / or authorization information to the subscriber.

[0112] It is understandable that the above network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (e.g., a cloud platform). In short, a network function (NF) can be implemented by hardware or software.

[0113] Figure 1Where N1, N2, N3, N4, and N6 are interface serial numbers. Exemplarily, the meaning of the above interface serial numbers can be found in the meaning defined in the 3rd generation partnership project (3GPP) standard protocol, and this application does not limit the meaning of the above interface serial numbers. It should be noted that the interface name between the various network functions in the figure is only an example. In a specific implementation, the interface name of the system architecture may also be other names, which is not limited in this application. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is also only an example and does not constitute any limitation on the function of the message itself.

[0114] For the convenience of explanation, in the embodiments of the present application, the network functions (such as AMF, SMF or UPF) are collectively referred to as NF, that is, the NF described later in the embodiments of the present application can be replaced by any network function. In addition, Figure 1 Only some network functions are schematically described. The NF described below is not limited to Figure 1 The network functions shown in .

[0115] It should be understood that the AMF, SMF, and UPF shown in the figure can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0116] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other names.

[0117] It should also be understood that the above Figure 1 It is only an example of a scenario in which the communication method provided in the present application is applicable, and does not constitute any limitation on the scenario in which the communication method provided in the present application can be applied. The authenticated non-3GPP device accessing the network involved in the present application may also be an authenticated non-3GPP device accessing the network through other types of RGs (such as 6G-RG), which will not be given one by one here.

[0118] To facilitate understanding of the embodiments of the present application, some basic concepts involved in the present application are briefly described.

[0119] 1. Non-3GPP access: refers to accessing the network using technologies other than 3GPP access technologies, such as Wireless Fidelity (wifi), Bluetooth or ZigBee. Among them, 3GPP access refers to accessing the mobile network using 3GPP access technologies, such as 5G, LTE and other technologies. In layman's terms, 3GPP access technology uses the access provided by base stations such as the next generation node base station (gNB) in the 5G system and the evolved node B (eNB) in the long term evolution (LTE).

[0120] 2. Non-3GPP access types: including untrusted non-3GPP access technology and trusted non-3GPP access technology. Untrusted non-3GPP access technology can be: terminal devices access the core network through wireless access nodes purchased by individuals; trusted non-3GPP access technology can be: terminal devices access the core network through wireless access nodes deployed by operators, wired access technology.

[0121] 3. Non-3GPP access network equipment: including but not limited to non-3GPP interworking function (N3IWF), trusted non-3GPP gateway function (TNGF), trusted non-3GPP access point (TNAP), trusted wireless local area network interworking function (TWIF), or W-AGF, etc.

[0122] Among them, N3IWF can be used to allow the terminal equipment and the 3GPP core network to interconnect with each other using non-3GPP technologies. N3IWF supports N2 interface communication with mobile management equipment and N3 interface communication with user plane equipment;

[0123] TNAP can be used to send authentication, authorization, and accounting (AAA) messages. For example, it can encapsulate the extensible authentication protocol (EAP) data packet in the AAA message and interact with the TNGF, which can be used to forward the EAP message.

[0124] TNGF can be used to support N2 interface and N3 interface, and can realize AMF selection, processing and SMF (relayed by AMF) N2 signaling to support sessions and QoS, transparently relay PDU between terminal devices and user plane devices, etc.

[0125] 4. Non-3GPP access process: If the non-3GPP access technology is an untrusted non-3GPP access technology, the corresponding non-3GPP access network equipment may include N3IWF, whose network topology is equivalent to the radio access network (RAN) in the 3GPP access network, and can support N2 and N3 interfaces.

[0126] If the non-3GPP access technology is a trusted non-3GPP access technology, the corresponding non-3GPP access network equipment may include TNGF, whose network topology is equivalent to RAN in the 3GPP access network, and may support N2 and N3 interfaces.

[0127] For ease of understanding, the following Figure 2 (a) and (b) in the figure introduce the untrusted non-3GPP access process and the trusted non-3GPP process respectively.

[0128] Figure 2 (a) is a non-trusted non-3GPP access architecture, where the terminal device can access the Figure 2 The untrusted non-3GPP device accesses the untrusted non-3GPP device through the communication interface (such as, Figure 2 The Y2 interface shown in (a) in FIG. 1 is connected to the gateway N3IWF. N3IWF uses a communication interface (such as, Figure 2 The N2 interface shown in (a) is connected to the AMF.

[0129] Figure 2 (b) is a trusted non-3GPP access architecture, where the terminal device can access the network through a communication interface (e.g. Figure 2 The trusted non-3GPP access point is connected to the trusted non-3GPP access point through a communication interface (such as, Figure 2The trusted non-3GPP gateway function accesses the trusted non-3GPP gateway function through a communication interface (such as, Figure 2 The N2 interface shown in (b) is connected to the AMF.

[0130] In addition, the terminal device can also connect to the AMF through 3GPP access technology. In other words, the terminal device can access the same or different AMFs through both 3GPP access technology and non-3GPP access technology; the terminal device can also access the AMF only through 3GPP access technology, or only through non-3GPP access technology.

[0131] 5. The terminal device passes the untrusted non-3GPP registration process: Figure 3 As shown, the terminal device goes through the untrusted non-3GPP registration process, including the following steps:

[0132] S310, the UE is connected to an untrusted non-3GPP access network.

[0133] Specifically, the UE is connected to an untrusted non-3GPP access device and is assigned an IP address.

[0134] S320, UE selects N3IWF.

[0135] Specifically, the UE selects a N3IWF and obtains the address information of the N3IWF.

[0136] S330, UE triggers to establish an Internet Protocol Security (IPsec) security association (IPsec Security Association, IPSec SA) with N3IWF.

[0137] Specifically, the UE triggers the establishment of an IPSec SA with the N3IWF by initiating an initial exchange of the Internet Key Exchange (IKE) protocol.

[0138] S340, UE sends a request message #1 to N3IWF.

[0139] The request message #1 does not include an authorized (AUTH) payload, and it can be understood that the request message #1 is used for extensible authentication protocol (EAP) signaling interaction. Optionally, the request message #1 is called an IKE_AUTH request message.

[0140] S350, N3IWF sends a response message #1 to the UE.

[0141] The response message #1 includes an EAP-Request / 5G-Start packet. The EAP-Request / 5G-Start packet notifies the UE to initiate an EAP-5G session. For example, the response message #1 notifies the UE to start sending a NAS message (the NAS message is encapsulated in an EAP-5G packet).

[0142] Optionally, the response message #1 is called an IKE_AUTH response message.

[0143] S360, UE sends request message #2 to N3IWF.

[0144] The request message #2 includes an EAP response (EAP-Response) / 5G-NAS data packet, which includes access network (AN) parameters and non-access stratum protocol data unit (NAS-PDU), wherein the NAS PDU carries a registration request message. Among them, the AN parameters include parameter information used by N3IWF to select AMF, such as the globally unique AMF identifier (Globally Unique AMF Identifier, GUAMI), the selected public land mobile network (Public Land Mobile Network, PLMN) identifier (identify, ID) (or PLMN ID and NID), etc.

[0145] Optionally, the request message #2 is called an IKE_AUTH request message.

[0146] If the UE has previously accessed the 3GPP system, for example, through 3GPP technology, the UE carries a 5G Globally Unique Temporary Identifier (5G-GUTI) in the registration request message.

[0147] If the UE has not accessed the 3GPP system before, the registration request message may carry a Subscription concealed identifier (SUCI).

[0148] S370, N3IWF performs AMF selection.

[0149] S380, N3IWF sends a registration request message to AMF.

[0150] As a possible implementation, when the above-mentioned registration request message does not carry SUCI, or when the AMF fails to verify the integrity protection of the registration request message, the AMF can obtain the UE's SUCI by sending a request message #3 to the UE. In this implementation, Figure 3 The method flow shown also includes:

[0151] S381, AMF sends a request message #3 to the UE through N3IWF. The request message #3 is used to request to obtain the SUCI of the UE.

[0152] Optionally, the request message #3 is called NAS Identity Request. For example, AMF sends NAS Identity Request to N3IWF through N2 communication interface, and N3IWF encapsulates NAS Identity Request in EAP / 5G-NAS data packet and sends it to UE. Among them, the data packet sent by N3IWF to UE can be called IKE_AUTH request message.

[0153] S382, the UE sends a response message #3 to the AMF via the N3IWF. The response message #3 carries the SUCI of the UE.

[0154] Optionally, the response message #3 is called NAS Identity Response. For example, the UE encapsulates the NAS Identity Response in an EAP / 5G-NAS data packet and sends it to the N3IWF, and the N3IWF sends the NAS Identity Response to the AMF through the N2 communication interface. Among them, the data packet sent by the UE to the N3IWF can be called an IKE_AUTH response message.

[0155] As another possible implementation, when the above-mentioned registration request message carries SUCI or the AMF successfully verifies the integrity protection of the registration request message, or when the AMF obtains SUCI through the response message #3, the AMF may initiate a process to authenticate the UE. In this implementation, Figure 3 The method flow shown also includes:

[0156] S391, AMF selects the Authentication Server Function (AUSF) network element.

[0157] S392, AMF sends an authentication request message to AUSF. Optionally, the authentication request message is called an AAA key request message (AAA Key Request). The authentication request message carries SUCI or SUPI.

[0158] S393, AUSF performs authentication on the UE. Specifically, the process of AUSF performing authentication on the UE is not described in detail in this embodiment, and reference may be made to the introduction of the related technology of step 7 in section 7.2.1 of the current 3GPP standard TS33.501.

[0159] S394, AUSF sends the security anchor function (SEAF) key to AMF.

[0160] After the authentication is completed, the AUSF sends the SEAF key to the AMF, for example, an AAA key response message (AAA Keyresponse), which carries the EAF key.

[0161] The AMF can use the SEAF key to derive the NAS security key and the N3IWF security key. The N3IWF key is used by the UE and N3IWF to establish the IPSec SA.

[0162] S395, AMF sends a NAS Security Mode Command to the UE via N3IWF to activate NAS security. The NAS Security Mode Command includes EAP-Success, indicating that the EAP-AKA' authentication performed by the core network is successful.

[0163] S396, UE sends NAS security mode complete (Security Mode Complete) to AMF through N3IWF.

[0164] Specifically, N3IWF forwards the NAS Security Mode Command sent by AMF to the UE, and sends the NAS Security Mode Complete message sent by the UE to AMF.

[0165] S397, AMF sends a request message #4 to N3IWF. The request message #4 includes the N3IWF key.

[0166] Optionally, request message #4 may be referred to as a Protocol for NG Interface (NGAP) initial context setup request (NGAP Initial Context Setup Request) message.

[0167] Specifically, when AMF receives the NAS Security Mode Complete message from the UE, AMF sends an NGAP Initial Context Setup Request to N3IWF, which includes the N3IWF key.

[0168] S398, N3IWF sends EAP completion (Success) to UE. After UE receives EAP-Success, it indicates that the EAP-5G session is completed, and there is no subsequent EAP-5G data packet interaction.

[0169] As another possible implementation, if 5G-GUTI is carried in the above-mentioned registration request message, and AMF verifies the integrity protection of the registration request message successfully, then AMF may decide not to initiate authentication. Then the above-mentioned steps S381 and S382 and S391 to S398 may not be performed.

[0170] Furthermore, the UE and N3IWF establish an IPSec SA using the N3IWF key obtained earlier. Figure 3 The method flow shown also includes:

[0171] S301, an IPSec SA is established between the UE and the N3IWF using the N3IWF key.

[0172] This IPSec SA is called signaling IPSec SA. After the signaling IPSec SA is established, N3IWF notifies AMF through NGAP Initial Context Setup Response that the UE context has been created. At this time, the signaling IPSec SA will be configured to run in tunnel mode, and N3IWF will assign an "inner" IP address and NAS_IP_ADDRESS to the UE. All subsequent NAS messages are transmitted through the signaling IPSec SA. Among them, for the uplink NAS message sent by the UE to the AMF, the source address is the "inner" IP address of the UE, and the destination address is NAS_IP_ADDRESS. For the downlink NAS message sent by the AMF to the UE, the source address is NAS_IP_ADDRESS, and the destination address is the "inner" IP address of the UE.

[0173] S302, AMF sends N2 message to N3IWF. N2 message includes NAS Registration Accept message sent to UE. Later, when AMF registers with UDM, it needs to provide UDM with Access Type of Non-3GPP access.

[0174] S303, N3IWF sends a NAS registration request to the UE through signalling IPSec SA.

[0175] 6. The terminal device passes the trusted non-3GPP registration process: Figure 4 As shown, the terminal device passes the trusted non-3GPP registration process, including the following steps:

[0176] S410, the UE selects a PLMN and a Trusted Non-3GPP Access Network (TNAN) connected to the PLMN. The UE establishes a Layer-2 connection with a Trusted Non-3GPP Access Point (TNAP).

[0177] S420, TNAP initiates an EAP process. The EAP message is encapsulated in the L2 data packet, for example, in an IEEE802.3 or 802.1x or Point-to-Point Protocol (PPP) data packet.

[0178] Optionally, the TNAP sends an EAP request or identification (EAP-Req / Identity) message to the UE, requesting to obtain identification information of the UE.

[0179] S430, the UE sends a Network Access Identifier (NAI) to the TNAP.

[0180] NAI indicates a request for 5G connectivity to a specific PLMN.

[0181] Optionally, the UE sends an EAP response or identification (EAP-Res / Identity) message to the TNAP, where the EAP-Res / Identity message includes the NAI.

[0182] For example, NAI = "<any_username> @nai.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org". This NAI triggers TANP to send an AAA request to TNGF.

[0183] S440, TANP sends an AAA request to TNGF. The EAP data packet between TNAP and TNGF is encapsulated by an AAA message. The AAA request also includes a TNAP identifier, which can be used as User Location Information (ULI).

[0184] S450, TNGF initiates an EAP-5G session. Specifically, TNGF sends an EAP Request / 5G-Start packet to the UE. The EAP-Request / 5G-Start packet notifies the UE to initiate an EAP-5G session, for example, notifies the UE to start sending NAS messages (by encapsulating the NAS messages in EAP-5G packets).

[0185] S460, UE sends an EAP response data packet / 5G-NAS data packet to TNGF, which includes AN parameters and NAS-PDU, where NAS PDU carries a registration request message. AN parameters include parameter information used by TNGF to select AMF, such as GUAMI, selected PLMN ID (or PLMN ID and NID), etc.

[0186] Optionally, if the UE has previously accessed the 3GPP system, such as through 3GPP technology, the UE carries 5G-GUTI in the registration request message. If the UE has not previously accessed the 3GPP system, the registration request message carries SUCI.

[0187] S470, TNGF performs AMF selection.

[0188] S480, TNGF sends a registration request message to AMF.

[0189] As a possible implementation, when the above-mentioned registration request message does not carry SUCI, or when the AMF successfully verifies the integrity protection of the registration request message, the AMF can obtain the UE's SUCI by sending a request message #5 to the UE. In this implementation, Figure 4 The method flow shown also includes:

[0190] S481, AMF sends a request message #5 to the UE through N3IWF. The request message #5 is used to request to obtain the SUCI of the UE.

[0191] Optionally, the request message #5 is called NAS Identity Request. For example, AMF sends NAS Identity Request to N3IWF through N2 communication interface, and N3IWF encapsulates NAS Identity Request in EAP / 5G-NAS data packet and sends it to UE. Among them, the data packet sent by N3IWF to UE can be called IKE_AUTH request message.

[0192] S482, the UE sends a response message #5 to the AMF via the N3IWF. The response message #5 carries the SUCI of the UE.

[0193] Optionally, the response message #5 is called NAS Identity Response. For example, the UE encapsulates the NAS Identity Response in an EAP / 5G-NAS data packet and sends it to the N3IWF, and the N3IWF sends the NAS Identity Response to the AMF through the N2 communication interface. Among them, the data packet sent by the UE to the N3IWF can be called an IKE_AUTH response message.

[0194] As another possible implementation, when the above-mentioned registration request message carries SUCI, or when the AMF successfully verifies the integrity protection of the registration request message, the AMF may initiate a process to authenticate the UE. In this implementation, Figure 4 The method flow shown also includes:

[0195] S491, AMF selects AUSF.

[0196] S492, AMF sends an authentication request message to AUSF.

[0197] S493, AUSF performs authentication on the UE. Specifically, the process of AUSF performing authentication on the UE is not described in detail in this embodiment, and reference may be made to the introduction in the current related technology.

[0198] S494, AUSF sends the SEAF key to AMF.

[0199] After authentication is completed, AUSF sends the SEAF key to AMF. AMF uses this key to derive the NAS security key and the TNGF security key.

[0200] S495, AMF sends a NAS Security Mode Command to the UE via TNGF to activate NAS security. The NAS Security Mode Command includes EAP-Success, indicating that the EAP-AKA' authentication performed by the core network is successful.

[0201] S496, UE sends NAS security mode completion (Security Mode Complete) to AMF through TNGF.

[0202] Specifically, TNGF forwards the NAS Security Mode Command sent by AMF to the UE, and sends the NAS Security Mode Complete message sent by the UE to the AMF.

[0203] S497, AMF sends a request message #6 to TNGF. The request message #6 includes the TNGF key.

[0204] Optionally, request message #6 can be called NGAP Initial Context Setup Request message.

[0205] Specifically, when AMF receives the NAS Security Mode Complete message from the UE, AMF sends an NGAP Initial Context Setup Request message to TNGF, and the NGAP Initial Context Setup Request message includes the TNGF key.

[0206] S498, TNGF sends an EAP request / 5G notification to the UE.

[0207] Specifically, the EAP-Response / 5G-Notification includes the address information of the TNGF, which is used for the subsequent establishment of an IPSec SA between the UE and the TNGF. The UE sends the EAP-Response / 5G-Notification to the TNGF.

[0208] S499, TNGF sends an AAA message to TNAP.

[0209] The AAA message includes an EAP-Success message sent to the UE and a TNAP key derived by the TNGF and sent by the TNGF to the TNAP.

[0210] S401, TNAP sends EAP completion (Success) to UE. After UE receives EAP-Success, it indicates that the EAP-5G session is completed, and there is no subsequent EAP-5G data packet interaction.

[0211] As another possible implementation, if the 5G-GUTI is carried in the above-mentioned registration request message and the integrity protection of the registration request message is successfully verified, the AMF may decide not to initiate authentication. Then the above-mentioned steps S481 and S482 and S491 to S401 may not be performed.

[0212] S402: L2 security is established between the UE and the TNAP.

[0213] S403, the UE receives the IP configuration of the TNAN, for example, through the Dynamic Host Configuration Protocol (DHCP), that is, the UE obtains its own IP address.

[0214] S404, UE initiates a secure NWt (the connection interface between UE and TNGF is defined as NWt in the standard) connection with TNGF. The UE successfully connects to TNAN and obtains the IP configuration. The UE initiates IKE_INIT interaction using the address of TNGF. In this interaction, the UE identifier (identify, ID) provided by the UE is the same as the UE ID included in step S460. This is to allow TNGF to determine the TNGF key corresponding to the UE. The TNGF key is used for two-way authentication. The transmission between the UE and TNGF is not encrypted because it is a trusted network (deployed by the operator and considered to be trusted, so no encryption is performed).

[0215] TNGF assigns an "inner" IP address, TCP port, NAS_IP_ADDRESS and a differentiated services code point (DSCP) value to the UE. All IP packets transmitted between the UE and TNGF are marked with the DSCP value. The UE and TNAP may map the DSCP value to the corresponding QoS level. After establishing the signalling IPSec SA, the UE establishes a TCP connection with the TNGF using NAS_IP_ADDRESS and TCP port. All subsequent NAS messages are transmitted through the signalling IPSec SA. Among them, for the uplink NAS message sent by the UE to the AMF, the source address is the "inner" IP address of the UE, and the destination address is NAS_IP_ADDRESS. For the downlink NAS message sent by the AMF to the UE, the source address is NAS_IP_ADDRESS, and the destination address is the "inner" IP address of the UE.

[0216] S405, TNGF sends a notification message to AMF. After the NWt connection is successfully established, TNGF notifies AMF through a notification message (such as NGAP Initial Context Setup Response message) that the UE context has been created.

[0217] S406, AMF sends an N2 message to TNGF.

[0218] The N2 message includes a NAS Registration Accept message sent to the UE. Subsequently, when the AMF registers with the UDM, it needs to provide the UDM with an Access Type of Non-3GPP access. The TNGF sends a NAS Registration Request to the UE via the signalling IPSec SA that has just been established.

[0219] 7. AUN3 devices that do not support 5G key architecture access 5GC: Figure 5 As shown, the AUN3 device that does not support the 5G key architecture accesses the 5GC, including the following steps:

[0220] S510, the AUN3 device attempts to establish an L2 connection with the RG through Ethernet or WiFi.

[0221] S520, RG sends an EAP request / identity to the AUN3 device. The EAP request / identity (EAP request / Identity) is used to start the EAP authentication process.

[0222] Optionally, the RG sends an EAP request / identity to the AUN3 device in a layer frame (eg, Extensible Authentication Protocol Over Lan (EAPOL)).

[0223] S530, the AUN3 device sends an EAP response / identity to the RG.

[0224] Specifically, the AUN3 device returns an EAP response / identity in the form of username@realm, which includes its Network Access Identifier (NAI). If the AUN3 device supports SUPI protection, the username part of the NAI may be encrypted.

[0225] Optionally, if the RG is a FN-RG, the FN-RG sends an EAP Response / Identity including the NAI to the W-AGF. The W-AGF constructs a SUCI from the SUPI based on the NAI using the NULL scheme and sends a NAS Registration Request message including the SUCI and AUN3 Device Indication to the AMF.

[0226] Optionally, if the RG is a 5G-RG, the 5G-RG constructs a SUCI based on the SUPI in the NAI, and sends a NAS registration request message including the SUCI and AUN3 device indication to the AMF.

[0227] S540, RG sends a registration request message to AMF / SEAF.

[0228] S550, select AUSF for AMF / SEAF.

[0229] S560, AMF / SEAF sends an authentication request message to AUSF.

[0230] Specifically, AMF / SEAF selects AUSF according to the SUCI in the received registration request, and sends an authentication request message (eg, Nausf_UEAuthentication_Authentication Request message) to AUSF. The authentication request message includes the SUCI of the AUN3 device and the AUN3 device indication.

[0231] S570, AUSF sends an acquisition request message (Nudm_UEAuthentication_Get request) to UDM, and the acquisition request message includes the SUCI of the AUN3 device and the AUN3 device indication.

[0232] S580, UDM selects an authentication method. Specifically, UDM calls SIDF to decrypt SUCI to obtain SUPI, and selects an authentication method according to SUPI.

[0233] S590, UDM sends a get response message (Nudm_UEAuthentication_Get response) to AUSF, where the get response message includes the SUPI of the AUN3 device and an indication of the selected authentication method, for example, an indication of the selected EAP-AKA'.

[0234] S591, AUSF and AUN3 devices execute the selected authentication method.

[0235] If the EAP authentication between AUSF and AUN3 device is completed successfully, Figure 5 The method flow shown also includes:

[0236] S592, AUSF sends an EAP-Success message to AMF / SEAF, and carries SUPI and MSK in the Nausf_UEAuthentication_Authentication Response message.

[0237] S593, AMF / SEAF sends an authentication result message to RG. AMF / SEAF sends the EAP-Success message and MSK to 5G-RG in the authentication result message.

[0238] S594, RG sends an EAP-Success message to the AUN3 device. Specifically, RG sends the EAP-Success message to the AUN3 device in a layer 2 frame.

[0239] S595, AUN3 and RG perform a four-way handshake to establish a WLAN security connection. AUN3 and RG use the first 256 bits of MSK as PMK, from which the WLAN key is derived.

[0240] 8. AUN3 devices supporting 5G key architecture access 5GC: Figure 6 As shown, the AUN3 device supporting the 5G key architecture accesses the 5GC, including the following steps:

[0241] S610, the AUN3 device and the access point (AP) (eg, Figure 6 Optionally, the AUN3 device establishes a WLAN connection with the RG based on a WLAN connection establishment procedure specified in a current protocol (eg, IEEE 802.11). The specific WLAN connection establishment process is not limited in this embodiment.

[0242] S620, RG sends an EAP request / identity to the AUN3 device. The EAP request / identity (EAP request / Identity) is used to start the EAP authentication process.

[0243] Optionally, the RG sends an EAP request / identity to the AUN3 device in a layer frame (eg, Extensible Authentication Protocol Over Lan (EAPOL)).

[0244] S630, the AUN3 device sends an EAP response / identity to the RG.

[0245] Specifically, the AUN3 device returns an EAP response / identity in the form of username@realm, which includes its network access identifier (NAI) or SUCI of 5G-GUTI.

[0246] Optionally, if the RG is a FN-RG, the FN-RG sends an EAP Response / Identity including the NAI to the W-AGF. The W-AGF creates a Registration Request on behalf of the AUN3 device and indicates that the registration is on behalf of the AUN3 device, where the interface between the AUN3 device and the RG needs to be protected. The W-AGF selects an AMF / SEAF, and the W-AGF sends a Registration Request to the AMF / SEAF on behalf of the AUN3 device. The Registration Request includes the NAI SUCI, the wired network name (if available), and the new indication. The same message content is forwarded from the AMF to the AUSF, and then from the AUSF to the UDM.

[0247] Optionally, if the RG is a 5G-RG, the 5G-RG sends a NAS registration request message to the AMF, including the received SUCI and the encryption indication required by the AUN3 device.

[0248] S640, RG sends a registration request message to AMF / SEAF. The registration request message includes the received SUCI and the encryption indication required by the AUN3 device.

[0249] S641, AMF / SEAF selects AUSF.

[0250] S642, AMF / SEAF sends an authentication request message to AUSF.

[0251] S643, AUSF sends an acquisition request message to UDM.

[0252] S644, UDM selects an authentication method.

[0253] S645, UDM sends a get response message to AUSF.

[0254] Steps S641 to S645 can refer to Figure 5 The description of steps S550 to S590 will not be repeated here.

[0255] S650, EAP-AKA' authentication. Optionally, the EAP-AKA' authentication process is performed according to the definition in the current protocol (eg, Section 6.1.3.1 of TS33.501[4]).

[0256] S660, AMF derives WAGF key. Specifically, AMF derives WAGF key according to the new encryption indication required by the AUN3 device in step S640.

[0257] S670, AMF provides the WAGF key (KWAGF') to the W-AGF. Optionally, AMF sends a NAS security mode command mode and provides the WAGF key to the W-AGF.

[0258] S680, W-AGF derives KRG as the PMK key. Specifically, W-AGF derives KRG as the PMK key from the WAGF key (KWAGF').

[0259] S690, the RG and the AUN3 device derive the WLAN key. Specifically, the RG and the AUN3 device derive the WLAN key from the PMK key.

[0260] S691, the RG and the AUN3 device establish a secure connection. Optionally, the RG and the AUN3 device perform a 4-way handshake to establish a secure connection with the WLANAN.

[0261] 9. Non-5G key architecture: for the above Figure 5 The process of AUN3 device accessing 5GC in the UE and network side key architecture is as follows Figure 7 shown.

[0262] from Figure 7 It can be seen that the long term key is stored on the AUN3 device and UDM. CK and IK appear on both the UDM and AUSF, indicating that the CK and IK are passed from UDM to AUSF. MSK is generated in AUSF and passed to WAGF through AMF. Afterwards, WAGF generates PMK based on MSK and passes PMK to AP, which then generates AP key. The UE side can generate the same key according to this process. At this point, AP can correspond to the 5G-RG mentioned in the previous process.

[0263] 10. 5G key architecture: for the above Figure 6 The process of AUN3 device accessing 5GC in the UE and network side key architecture is as follows Figure 8 shown.

[0264] from Figure 8 It can be seen that the long-term key is stored on the AUN3 device and UDM. CK, IK appear on both the UDM and the AUSF, which indicates that the key is passed from the UDM to the AUSF. Kausf or Kseaf is generated in the AUSF and passed to the AMF. Then the AMF generates Kamf based on Kausf or Kseaf and passes it to the WAGF. After that, the WAGF generates PMK based on Kamf and passes the PMK to the AP. The AP then generates the AP key. The UE side can generate the same key according to this process. At this point, the AP can correspond to the 5G-RG mentioned in the previous process.

[0265] In addition, in order to facilitate understanding of the embodiments of the present application, the following points are explained.

[0266] First, in the embodiment of the present application, "used for indication" may include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used for indicating A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must include A.

[0267] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. The information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending period and / or sending time of these sub-information can be pre-defined, for example, pre-defined according to the protocol, or can be configured by the transmitting end device by sending configuration information to the receiving end device.

[0268] Second, "at least one" shown in the embodiment of the present application refers to one or more, and "multiple" refers to two or more. In addition, in the embodiment of the present application, "first", "second" and various digital numbers (for example, "#1", "#2", etc.) are only for the convenience of description, and are not used to limit the scope of the embodiment of the present application. The size of the sequence number of each process below does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe the scheme outside the embodiment of the present application. In addition, in the embodiment of the present application, words such as "910", "920" are only marks made for the convenience of description, and the order of execution steps is not limited.

[0269] Third, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0270] Fourth, the "storage" involved in the embodiments of the present application may refer to storage in one or more memories. The one or more memories may be separately set or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially separately set and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, which is not limited by the present application.

[0271] Fifth, the "protocol" involved in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0272] Sixth, in the embodiments of the present application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0273] Seventh, in the embodiments of the present application, each term and English abbreviation is provided for the convenience of description and shall not constitute any limitation to the present application. The present application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future protocols.

[0274] Eighth, the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0275] Combination of the above Figure 1 The present invention briefly introduces the scenarios in which the communication method provided in the embodiments of the present invention can be applied, and introduces the basic concepts that may be involved in the embodiments of the present invention. In the basic concepts, the process of AUN3 devices that do not support the 5G key architecture accessing 5GC and the process of AUN3 devices that support the 5G key architecture accessing 5GC are introduced. Figure 5 and Figure 6 In the description of the process of AUN3 device accessing 5GC, AMF and AUSF distinguish whether AUN3 device supports or does not support 5G key architecture mainly by an identifier, namely the above Figure 6 The encryption indication involved in the process of AUN3 device accessing 5GC is shown. In the case of encryption indication, AMF and AUSF generate relevant keys based on 5G key architecture. In the case of no encryption indication, relevant keys are generated based on non-5G key architecture. Specifically, the encryption indication is added by 5G-RG when sending NAS registration request message to AMF.

[0276] The problem existing in the above-mentioned process of AUN3 device accessing 5GC is: how does 5G-RG judge and determine whether the AUN3 device supports or does not support the 5G key architecture? Therefore, this application mainly solves how to judge whether the AUN3 device supports or does not support the 5G key architecture.

[0277] The present application provides a communication method which can be applied in Figure 1 This application does not impose any limitation on the application scenario.

[0278] It should be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application may be a network element, or a functional module in the network element that can call and execute the program.

[0279] Fig. 9 This is a schematic flow chart of a communication method provided by the present application. It includes the following steps:

[0280] S911, the first gateway registers with the core network.

[0281] In this embodiment, the first gateway is a gateway that can be connected to the core network, responsible for assisting the AUN3 device to access the core network, and can be a 5G-RG or other network element that can implement the function of 5G-RG. For the convenience of description, the following takes the first gateway as 5G-RG as an example for explanation. When the first gateway is other devices (or nodes, network elements), the 5G-RG in the following can be replaced with the corresponding device, and no further description is given.

[0282] In this embodiment, for 5GC, 5G-RG can be regarded as a terminal device. The process of registering 5G-RG to 5GC can refer to the description of the process of terminal device registration to 5GC in the current related technology. In this embodiment, how 5G-RG registers to 5GC is not described in detail.

[0283] S910, AUN3 device and 5G-RG establish a connection.

[0284] In this embodiment, the AUN3 device is a terminal device connected to the core network through 5G-RG, which can be understood as a terminal device supporting non-3GPP communication (such as supporting WiFi communication).

[0285] Specifically, after the connection between the AUN3 device and the 5G-RG is established, the core network can be accessed through the connection. The AUN3 device can initiate a registration process to the core network through the 5G-RG. For example, the AUN3 device sends a registration request to the 5G-RG through the EAP authentication process, and then the 5G-RG forwards the registration request to the core network, thereby initiating a registration process between the AUN3 device and the 5G-RG.

[0286] Fig. 9 The method flow shown also includes:

[0287] S921, 5G-RG sends a first request message to the AUN3 device, or in other words, the AUN3 device receives the first request message from the 5G-RG.

[0288] Specifically, the first request message is used to request identity information from the AUN3 device, and the identity information is used by the core network to authenticate the AUN3 device. For example, the first request message is used to start the authentication process. At this time, the first request message can be an EAP-Request / Identity message. It should be understood that the first request message can also be other messages that can request the identity information of the AUN3 device. In the embodiment of the present application, the specific message type of the first request message is not limited, and it is sufficient to implement the corresponding function. For the convenience of description, the following description takes the first request message as an EAP-Request / Identity message as an example.

[0289] There may be transmission of other messages between step S910 and step S921, which is not specifically limited in the embodiments of the present application.

[0290] S920, the AUN3 device sends a first response message to the 5G-RG, or the 5G-RG receives a first response message from the AUN3 device. The first response message includes the identity information of the AUN3 device, and the first response message is used to indicate whether the AUN3 device supports the first key architecture.

[0291] Optionally, when the first request message is an EAP-Response / Identity request message, the first response message also includes an EAP response message to respond to the first request message.

[0292] In this embodiment, the first key architecture can refer to any key architecture. For example, the first key architecture can be a 5G key architecture, a non-5G key architecture, a 4G 3GPP key architecture (refer to the relevant definition in TS33.401), or a 4G non-3GPP key architecture (refer to the relevant definition in TS33.402).

[0293] The key deduction method required for network-side security protection when the AUN3 device supports the first key architecture is different from the key deduction method required for network-side security protection when the AUN3 device does not support the first key architecture.

[0294] Specifically, the AUN3 device and the network side deduce the keys required for security protection according to whether the AUN3 device supports the first key architecture. If the AUN3 device supports the first key architecture, the AUN3 device and the network side deduce the keys required for security protection according to the first key deduction method. If the AUN3 device does not support the first key protection method, the AUN3 device and the network side use the second key deduction method to deduce the keys required for security protection. Among them, the first key deduction method can be understood as the AUN3 device and the network side deduce the key according to the first key architecture, and the second key deduction method can be understood as the AUN3 device and the network side deduce the key according to the second key architecture. The second key architecture is a key generation method different from the first key architecture, and its definition can refer to the relevant description of the first key architecture. For example, the 5G key architecture is the first key architecture, and the non-5G key architecture is the second key architecture.

[0295] Exemplarily, the first key architecture may be the 5G key architecture introduced in the basic concepts above (eg Figure 8 As shown), it can also be a key architecture defined by future 3GPP standards. This embodiment takes the 5G key architecture introduced in the basic concepts as an example for illustration. If the AUN3 device supports the 5G key architecture, the process of deducing keys on the network side is: AUSF generates Kausf based on CK, IK, AUSF uses Kausf or Kseaf, and passes Kseaf to AMF, AMF generates Kamf based on Kseaf, and further generates Kwagf, and passes Kwagf to WAGF, WAGF generates PMK based on Kwagf, and passes PMK to 5G-RG, 5G-RG generates the keys required for security protection based on PMK. The process of deducing keys on the AUN3 device side is: AUN3 device derives CK, IK based on the locally stored long-term key, then generates Kausf based on CK, IK, generates Kseaf based on Kausf, then generates Kamf based on Kseaf, and then generates Kwagf based on Kamf, then generates PMK based on Kwagf, and finally generates the keys required for security protection based on PMK.

[0296] Alternatively, if the AUN3 device does not support the 5G key architecture, the process of deducing keys on the network side can be: AUSF generates MSK based on CK and IK, and passes MSK to WAGF through AMF; WAGF generates PMK based on MSK, and passes PMK to 5G-RG; 5G-RG generates the keys required for security protection based on PMK. The process of deducing keys on the AUN3 device side is: AUN3 device derives CK and IK based on the locally stored long-term key, then generates MSK based on CK and IK, then generates PMK based on MSK, and finally generates the keys required for security protection based on PMK.

[0297] The above security protection can be understood as encryption and integrity protection of the connection between the AUN3 device and the 5G-RG. For example, the sender encrypts and integrity protects the message based on the generated key, and the receiver decrypts and integrity checks the message based on the key.

[0298] In this embodiment, the AUN3 device sends a first response message to the 5G-RG to assist the 5G-RG in determining whether the AUN3 device supports the first key architecture, so that subsequent core network elements can clearly understand whether the AUN3 device currently requesting access supports the first key architecture and select a suitable key deduction method to generate a key to improve the security of communication.

[0299] Optionally, in this embodiment, the first response message sent by the AUN3 device to the 5G-RG includes an EAP response message and information indicating whether the AUN3 device supports the first key architecture, which can also be understood as the AUN3 device sending an EAP response message and information indicating whether the AUN3 device supports the first key architecture to the 5G-RG. The AUN3 device sending the EAP response message and information indicating whether the AUN3 device supports the first key architecture to the 5G-RG includes but is not limited to the following possible implementations:

[0300] As a possible implementation, the AUN3 device sends an EAP response message and information indicating whether the AUN3 device supports the first key architecture to the 5G-RG: the AUN3 device sends an EAP response message to the 5G-RG, and the EAP response message includes the first indication information. In this implementation, the information indicating whether the AUN3 device supports the first key architecture can be understood as that in addition to the AUN3 identity in the EAP response message, there is also a newly added information element (IE) for carrying information indicating whether the AUN3 device supports the first key architecture. For example, the first response message is EAP-Response / Identity (AUN3 ID, information indicating whether the AUN3 device supports the first key architecture).

[0301] As another possible implementation, the AUN3 device sends an EAP response message and information indicating whether the AUN3 device supports the first key architecture to the 5G-RG: the AUN3 device sends an EAP response message to the 5G-RG, and the EAP response message includes the information indicating whether the AUN3 device supports the first key architecture. In this implementation, the information indicating whether the AUN3 device supports the first key architecture can be understood as only the identity of AUN3 in the EAP response message, and the identity of AUN3 itself has an indicative function. For example, the first response message is EAP-Response / Identity (AUN3 ID).

[0302] As another possible implementation, the AUN3 device sends an EAP response message and information indicating whether the AUN3 device supports the first key architecture to the 5G-RG: the AUN3 device sends an EAP response message and information indicating whether the AUN3 device supports the first key architecture to the 5G-RG respectively. In this implementation, the information indicating whether the AUN3 device supports the first key architecture can be understood as an IE newly added outside the EAP response message.

[0303] It should be understood that in this embodiment, there is no limitation on how to send information to 5G-RG to indicate whether the AUN3 device supports the first key architecture. Existing messages can be reused, or existing IEs can be used to transmit the first indication information. Alternatively, new signaling can be added, or new IEs can be used to transmit information indicating whether the AUN3 device supports the first key architecture. This will not be described in detail here. For example, the first response message is EAP-Response / Identity, which is used to indicate whether the AUN3 device supports the first key architecture.

[0304] As an example but not limitation, the process of 5G-RG sending a first request message to the AUN3 device in step S921 and the AUN3 device sending a first response message to the 5G-RG in step S920 is the message required to be transmitted between the AUN3 device and the 5G-RG to perform the EAP authentication process. For example, the first request message includes an EAP request message, and the first response message includes an EAP response message. For descriptions related to the EAP request message and the EAP response message, reference can be made to the description of the messages involved in starting the EAP authentication process in the current related art, and the descriptions of the EAP request message and the EAP response message in the following three implementations (such as the following implementation A, implementation B, and implementation C):

[0305] Implementation A: If the AUN3 device and the 5G-RG in this embodiment use untrusted non-3GPP technology to access each other, the description of the first request message can refer to Figure 3 For the description of response message #1 in the registration process, please refer to the description of the first response message. Figure 3 The description of request message #2 in the registration process is not repeated here.

[0306] In the case shown in implementation method A, the AUN3 device and 5G-RG transmit IKE_AUTH request message and IKE_AUTH response message to notify the AUN3 device to initiate an EAP-5G session. After receiving the EAP-Request / 5G-Start data packet, the AUN3 device sends an EAP response message. For the specific process, please refer to the previous article Figure 3 In the description of steps S330 to S360 in the registration process shown in FIG. 1 , the AUN3 device is regarded as Figure 3 UE in 5G-RG Figure 3 The N3IWF in the code will not be described in detail here.

[0307] Implementation method B: If the AUN3 device and the 5G-RG in this embodiment use a trusted non-3GPP technology to access each other, the description of the first request message involved can refer to Figure 4 For the description of the EAP-Req / Identity message in the registration process, the first response message can be found in Figure 4 The description of the EAP response data packet / 5G-NAS data packet in the registration process is not repeated here.

[0308] In the case shown in implementation B, the AUN3 device and 5G-RG transmit EAP-Req / Identity messages, EAP-Res / Identity messages, and EAP Request / 5G-Start packets to notify the AUN3 device to initiate an EAP-5G session. For the specific process, please refer to the previous article. Figure 4 In the description of steps S420 to S460 in the registration process shown in FIG. 1 , the AUN3 device is regarded as Figure 4 UE in 5G-RG Figure 4 The TNAP and TNGF in it will not be described in detail here.

[0309] Exemplarily, the first response message involved in the above implementation A and implementation B includes EAP-Response / 5G-NAS data packet #1, which includes AN parameters and a registration request message. Among them, the AN parameters include parameter information used by 5G-RG to select AMF, such as GUAMI, selected PLMN ID (or PLMN ID and NID), etc.

[0310] If the AUN3 device has previously accessed the 3GPP system, for example, through 3GPP technology, the AUN3 device can carry 5G-GUTI in the registration request message. If the AUN3 device has not previously accessed the 3GPP system, the registration request message carries SUCI.

[0311] In the case of implementation method C: If the AUN3 device and the 5G-RG in this embodiment use a traditional access method, such as the access method mentioned in IEEE 802.1x. The description of the first request message can be referred to Figure 5 The description of steps S520 to S530 in the process shown in the above, or refer to Figure 6 Description of steps S620 to S630 in the process shown.

[0312] In the above three implementations, combined with the transmission method of the first response message, it can be understood that the first request message is an EAP-Req / Identity message or an EAP-Req / 5G-START message; the first response is an EAP-RES / Identity message, or an EAP-Response / 5G-NAS message. When the first response is an EAP-Response / 5G-NAS message, according to the above description, the information used to indicate whether the AUN3 device supports the first key architecture can be carried in the EAP-Response / 5G-NAS message, or carried outside the EAP-Response / 5G-NAS message. When the information used to indicate whether the AUN3 device supports the first key architecture can be carried in the EAP-Response / 5G-NAS message, its AN parameter part can carry information used to indicate whether the AUN3 device supports the first key architecture. Specifically, a new IE is added to the AN parameter to carry information used to indicate whether the AUN3 device supports the first key architecture, or the UE ID part in the AN parameter has an indication function. When the information indicating whether the AUN3 device supports the first key architecture can be carried outside the EAP-Response / 5G-NAS message, a new IE is sent to the 5G-RG along with the EAP-Response / 5G-NAS message.

[0313] It can be seen from the above three implementation methods that in this embodiment, the AUN3 device can access the 5G-RG through different processes.

[0314] For example, in this embodiment, before the AUN3 device accesses the 5G-RG, it can determine the specific process used between the AUN3 device and the 5G-RG based on the judgment condition or the predefined access method. The predefined access method can be understood as an access process agreed in advance; the judgment condition includes but is not limited to judging whether it belongs to the same user (or owner), judging whether the user has made a choice, etc.

[0315] If the judgment condition is that the AUN3 device and the first gateway do not belong to the same user, or the user confirms that the AUN3 device and the first gateway do not belong to the same user, the AUN3 device determines to access the first gateway through the process corresponding to implementation method A;

[0316] If the judgment condition is that the AUN3 device and the first gateway belong to the same user, or the user confirms that the AUN3 device and the first gateway belong to the same user, the AUN3 device determines to access the first gateway through the process corresponding to implementation method B;

[0317] If the predefined access method is to access by the process corresponding to implementation method A first, the AUN3 device determines to first try to access the first gateway by the process corresponding to the untrusted non-3GPP access technology;

[0318] If the predefined access method is to preferentially access through a process corresponding to implementation method B, the AUN3 device determines to first try to access the first gateway through a process corresponding to a trusted non-3GPP access technology.

[0319] If the predefined access method is to access by a process corresponding to implementation method C first, the AUN3 device determines to first try to access the first gateway by a process specified by 802.1x and related protocols.

[0320] It should be noted that the above judgment conditions are only examples and do not constitute any limitation on the scope of protection of this application. The AUN3 device can also determine how to access the 5G-RG in other ways, for example, by judging the communication quality or communication distance of the 5G-RG, etc., and examples will not be given one by one here.

[0321] The AUN3 device can also first look for a specific type of 5G-RG, and determine which implementation method to use based on the 5G-RG. Specifically, AUN3 selects a 5G-RG based on implementation, configuration, or its own capabilities, or the capabilities of the 5G-RG, and determines to use implementation method A, implementation method B, or implementation method C based on the selected 5G-RG. For example, if the UE finds a nearby 5G-RG that can use a trusted non-3GPP access process, then after the UE determines to select the 5G-RG, the AUN3 device uses implementation method A to access. For another example, if the UE finds a 5G-RG that can use an untrusted non-3GPP access process, then after the UE determines to select the 5G-RG, the AUN3 device uses implementation method B to access. For another example, if the UE finds a 5G-RG that can use an 802.1x access process, then after the UE determines to select the 5G-RG, the AUN3 device uses implementation method C to access.

[0322] Specifically, in this embodiment, the information used to indicate whether the AUN3 device supports the first key architecture indicates whether the AUN3 device supports the first key architecture, including the following possible implementations:

[0323] As a possible implementation manner, the information used to indicate whether the AUN3 device supports the first key architecture indicates that the AUN3 device supports the first key architecture.

[0324] Under this implementation method, when the AUN3 device supports the first key architecture, the AUN3 device sends information to the 5G-RG to indicate whether the AUN3 device supports the first key architecture; when the AUN3 device does not support the first key architecture, the AUN3 device may not send information to the 5G-RG to indicate whether the AUN3 device supports the first key architecture.

[0325] As another possible implementation, the information indicating whether the AUN3 device supports the first key architecture indicates that the AUN3 device does not support the first key architecture. In this implementation, when the AUN3 device does not support the first key architecture, the AUN3 device sends information indicating whether the AUN3 device supports the first key architecture to the 5G-RG; when the AUN3 device supports the first key architecture, the AUN3 device may not send information indicating whether the AUN3 device supports the first key architecture to the 5G-RG.

[0326] In another possible implementation method, when the AUN3 device supports the first key architecture, the information used to indicate whether the AUN3 device supports the first key architecture is set to a first value; when the AUN3 device does not support the first key architecture, the AUN3 device sets the information used to indicate whether the AUN3 device supports the first key architecture to a second value.

[0327] Exemplarily, in the embodiment of the present application, the first response message is used to indicate whether the AUN3 device supports the first key architecture, including the following two possible ways:

[0328] Mode #1: The first response message includes the identity information of the AUN3 device, where the identity information is used to indicate whether the AUN3 device supports the first key architecture.

[0329] As a possible implementation, when the identity information is a first identifier, the identity information is used to indicate that the terminal device does not support the first key architecture; or when the identity information is a second identifier, the identity information is used to indicate that the terminal device supports the first key architecture. The first identifier and the second identifier are different.

[0330] For example, the identity information is SUPI or SUCI. When the EAP response message (i.e., the first response message) carries the identity information of the AUN3 device in the form of SUPI, it indicates that the AUN3 device does not support the first key architecture; when the EAP response message carries the identity information of the AUN3 device in the form of SUCI, it indicates that the AUN3 device supports the first key architecture.

[0331] Accordingly, the 5G-RG can distinguish whether the received information is SUPI or SUCI according to the specific format of the AUN3 device identity information. For example, assuming that the SUPI of the AUN3 device is 00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org. If the AUN3 device does not support the first key architecture, the identity information of the AUN3 device sent is SUPI, that is, 00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org is sent; if the AUN3 device supports the first key architecture, the identity information of the AUN3 device sent is SUCI, that is, type3.rid0.schid0.userid00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org is sent, or anonymous SUCI is sent, that is, anonymous@5gc.mnc012.mcc345.3gppnetwork.org is sent.

[0332] As another possible implementation manner, when the identity information is of the first type of the first identifier, the identity information is used to indicate that the terminal device does not support the first key architecture; or,

[0333] When the identity information is of the second type of the first identifier, the identity information is used to indicate that the terminal device supports the first key architecture.

[0334] For example, the identity information is SUCI in different formats. Different SUPI formats of the AUN3 device have different corresponding SUCI formats. For example, the type of SUPI that supports the first key architecture is the SUPI in the International Mobile Subscriber Identification Number (IMSI) format, and the type of SUPI that does not support the first key architecture is the SUPI in the NAI format. The formats of the SUCI in IMSI format and the SUCI in NAI format are also different. Therefore, when the 5G-RG receives the SUCI in the NAI format, it determines that the AUN3 device does not support the first key architecture, and when the 5G-RG receives the SUCI in the IMSI format, it determines that the AUN3 device supports the first key architecture. For another example, the SUCI that does not support the first key architecture is calculated using the null algorithm, while the SUCI that supports the first key architecture is calculated using the non-null algorithm.

[0335] As another possible implementation manner, the identity information includes a field for indicating whether the terminal device supports the first key architecture.

[0336] For example, the identity information may be a SUPI or SUCI of an AUN3 device, and a field carried in a username or realm part of the SUPI or SUCI. The identity information may be at least one bit of information in the username or realm part, such as the username or realm part carries information such as AUN3 or 5GK. If the username or realm part of the SUPI or SUCI carries the identity information, it indicates that the first key architecture is supported, and if the identity information is not carried, it indicates that the first key architecture is not supported; or if the first key architecture is not carried, it indicates that the first key architecture is supported, and if the first key architecture is carried, it indicates that the first key architecture is not supported, or if the first value carried indicates that the first key architecture is supported, and the second value carried indicates that the first key architecture is not supported.

[0337] For example, assuming that the SUPI of the AUN3 device is 00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org, when the AUN3 device supports the first key architecture, the SUPI carrying the field can be 00-00-5E-00-53-00.5G key hierarchy@5gc.mnc012.mcc345.3gppnetwork.org. At this time, the first response message is EAP-Identity / Response(00-00-5E-00-53-00.5G key hierarchy@5gc.mnc012.mcc345.3gppnetwork.org).

[0338] Or the SUPI carrying the field can be 00-00-5E-00-53-00@5Gkey.5gc.mnc012.mcc345.3gppnetwork.org. In this case, the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5Gkey hierarchy.5gc.mnc012.mcc345.3gppnetwork.org). If the AUN3 device does not support the first key architecture, the SUPI can be 00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org. In this case, the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org).

[0339] For example, suppose the SUPI of the AUN3 device is Network Specific Identifier user17 @ example.com , the corresponding SUCI is type1.rid678.schid1.hnkey27.ecckey<ECC ephemeralpublic key> .cip<encryption of user17> .mac<MAC tag value> @example.com, then if the AUN3 device supports the first key architecture, the SUCI carried in the field is type1.rid678.schid1.hnkey27.ecckey<ECC ephemeral public key> .cip<encryption of user17> .mac<MAC tag value> @AUN3.example.com, type1.rid678.schid1.hnkey27.eckey<ECC ephemeral publickey> .cip<encryption of user17> .mac<MAC tag value> @AUN3-5GK.example.com, type1.rid678.schid1.hnkey27.eckey<ECC ephemeral public key> .cip<encryption ofuser17> .mac<MAC tag value> @AUN3-N5GK.example.com. At this time, when the field is AUN3 or AUN3-5GK, it means that the 5G key architecture is supported; when the field is not carried or is AUN3-N5GK, it means that the 5G key architecture is not supported.

[0340] Mode #2: The first response message also includes first indication information, and the first indication information is used to indicate whether the AUN3 device supports the first key architecture. Exemplarily, the first indication information may be in the form of, but not limited to, character string information, bit information, or non-access stratum protocol data unit NAS-PDU.

[0341] For example, the first indication information may be string indication information (such as "5G key hierarchy" or "5G NAS", "5GK", "N5GK", "AUN3-5GK", "AUN3-N5GK"). In the case where the string indication information is always carried, the 5G-RG (including the subsequent AMF and AUSF) can determine that the AUN3 device supports the first key architecture according to the string information. In the case where the string indication information is not always carried, the 5G-RG (including the subsequent AMF and AUSF) determines that the AUN3 device supports the first key architecture according to the first indication information when the string indication information appears; if the string indication information does not appear, it is determined that the AUN3 device does not support the first key architecture. The string can be placed in SUCI or SUPI as part of SCUI or SUPI, and can also be transmitted as an independent IE. For an example of transmission as part of SUCI or SUPI, see the previous example, which is not described in detail here.

[0342] For example, when transmitted as an independent IE, assuming that the SUPI of the AUN3 device is 00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org, when the AUN3 device supports the first key architecture, the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org, "5Gkey hierarchy"), or the first response message is: "5G key hierarchy", EAP-Identity / Response(00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org). When the AUN3 device supports the first key architecture, the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org, "non-5G key hierarchy") (this time it means that the 5G key architecture is not supported), or the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org, "NULL") (this time it means that the first key architecture is not supported, and the default key architecture can be used according to the pre-configuration.), or the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org) (this time it means that the first key architecture is not supported, and the default key architecture can be used according to the pre-configuration).

[0343] For another example, the first indication information may be bit information, which may contain one or more bits. For example, 0, or 00, 01. When the bit is set to a certain specific value, it indicates support for the first key architecture, and when the value is set to another specific value, it indicates support for the second key architecture, or does not support the first key architecture; or, when the bit information is carried, it indicates support for the first key architecture, and when it is not carried, it indicates support for the first key architecture; or, when the bit information is carried, it indicates non-support for the first key architecture, and when it is not carried, it indicates support for the first key architecture. In the case of multiple bits, different bits may represent different key architectures. For example, 00 represents support for the first key architecture, and 01 represents support for a non-first key architecture.

[0344] For example, the first indication information may be NAS-PDU. If the first response message carries NAS-PDU, it indicates that the AUN3 device indicates support for the first key architecture. Alternatively, it may be understood that if the first indication information is NAS-PDU, it indicates that the AUN3 device supports the NAS protocol, which is indirectly understood as indicating support for the first key architecture. The first indication information may also indicate that the AUN3 device supports the first key architecture by indicating that the AUN3 device supports the NAS protocol (e.g., the 5G NAS protocol), wherein the AUN3 device supports the 5G NAS protocol, indicating that the AUN3 device can generate and process 5G NAS messages (e.g., registration request messages, NAS SMC messages, PDU session establishment request messages, etc.).

[0345] It should be noted that the function of the identity information or first indication information carried in the above-mentioned first response message is to indicate whether the AUN3 device supports the first key architecture. Therefore, the identity information can also be understood as a type of first indication information. For the sake of convenience of description, the information carried in the first response message for indicating whether the AUN3 device supports the first key architecture is collectively referred to as the first indication information. However, it should be noted that the form of the first indication information below includes the above-mentioned identity information.

[0346] Optionally, the first response message may include second indication information, and the second indication information is used to indicate whether the AUN3 device supports the non-access layer NAS protocol. Similar to the above-mentioned first indication information, possible forms of the second indication information include: a specific format of the AUN3 device identity information, a special format of SUPI, a special format of SUCI, character string information, bit information or NAS-PDU, which will not be repeated here. It should be noted that only one of the first indication information and the second indication information can be sent.

[0347] The second indication information can be called 5G NAS indication information #1, which is used to indicate that the following NAS registration request message sent by 5G-RG to AMF is generated by the AUN3 device, or it can also be understood that 5G NAS indication information #1 is used to inform AMF that the AUN3 device supports the 5G NAS protocol, and AMF can perform the NAS SMC process with the AUN3 device.

[0348] In addition, it should be noted that when the AUN3 device sends the first indication information to the 5G-RG and does not send the second indication information, the first indication information can also be used to indicate that the AUN3 device supports the 5G NAS protocol, and supporting the 5G NAS protocol can also be understood as supporting the first key architecture.

[0349] In this embodiment, after the 5G-RG receives the first response message, it can be determined that the AUN3 device that sends the first response message requests to initiate a registration process, and then the 5G-RG initiates the registration process instead of the AUN3 device. Fig. 9 The method flow shown also includes:

[0350] S930, 5G-RG sends a NAS registration request message to the access mobility management network element, or the access mobility management network element receives a NAS registration request message from 5G-RG.

[0351] In this embodiment, the access mobility management network element may be an access and mobility management function network element, which is responsible for access control and mobility management of the AUN3 device accessing the operator network, and may be an AMF or other network element capable of implementing the functions of the AMF. For ease of description, the following description takes the access mobility management network element as an example of an AMF.

[0352] Exemplarily, if 5G-RG transmits messages through W-AGF and AMF, 5G-RG sends a NAS registration request message to AMF, including: 5G-RG sends a second request message to W-AGF, and the second request message carries the NAS registration request message. After receiving the second request message, W-AGF forwards the NAS registration request message in the second request message to AMF.

[0353] In a possible implementation, when 5G-RG sends a NAS registration request message to W-AGF, it also sends to W-AGF whether the AUN3 device supports the first key architecture. Please refer to the relevant description of step S920. Specifically, the EAP authentication response message in the first response message can be replaced with the NAS registration request message, and the first response message can be replaced with the second response message.

[0354] As a possible implementation method, the above-mentioned AUN3 device supports the 5G NAS protocol, and the registration request message carried in the first response message is the NAS registration request message.

[0355] In this implementation mode, 5G-RG only needs to forward the NAS registration request message carried in the first response message to AMF.

[0356] As another possible implementation method, the above-mentioned AUN3 device does not support the 5G NAS protocol, and the first response message does not carry the NAS registration request message.

[0357] In this implementation, the 5G-RG generates a NAS registration request message instead of the AUN3 device, and sends the generated NAS registration request message to the AMF.

[0358] Specifically, the NAS registration request message includes third indication information, and the third indication information is used to indicate that the type of the device initiating the registration request is an AUN3 device. The third indication information may be an identifier of the AUN3 device, or bit indication information, or character string indication information.

[0359] Optionally, the NAS registration request message further includes fourth indication information. The fourth indication information is used to indicate whether the AUN3 device supports the first key architecture.

[0360] In a possible implementation manner, the NAS registration request message always carries fourth indication information for indicating whether the AUN3 device supports or does not support the first key architecture.

[0361] In another possible implementation, when the AUN3 device supports the first key architecture, the NAS registration request message carries the fourth indication information. At this time, the NAS registration request message carries the fourth indication information, indicating that the AUN3 device supports the first key architecture, and the NAS registration request message does not carry the fourth indication information, indicating that the AUN3 device does not support the first key architecture.

[0362] In another possible implementation, when the AUN3 device does not support the first key architecture, the NAS registration request message carries the fourth indication information. At this time, the NAS registration request message carries the fourth indication information, indicating that the AUN3 device does not support the first key architecture, and the NAS registration request message does not carry the fourth indication information, indicating that the AUN3 device supports the first key architecture.

[0363] From the description of the first indication information in step S920, it can be seen that the first indication information is used to indicate whether the AUN3 device supports the first key architecture. Therefore, after the 5G-RG receives the first indication information, it can determine whether the AUN3 device supports the first key architecture based on the first indication information, thereby determining the value or type of the fourth indication information carried in the NAS registration request message to realize the function of indicating to the AMF and / or AUSF whether the AUN3 device supports the first key architecture.

[0364] For example, when the first key architecture is a 5G key architecture, when the first indication information indicates that the AUN3 device supports the 5G key architecture, and when the 5G-RG determines that the AUN3 device supports the 5G key architecture, the NAS registration request message does not carry the fourth indication information; when the first indication information indicates that the AUN3 device does not support the 5G key architecture, and when the 5G-RG determines that the AUN3 device does not support the 5G key architecture, the NAS registration request message carries the fourth indication information, and at this time the fourth indication information is used to indicate that the AUN3 device does not support the 5G key architecture. Optionally, the first indication information and the fourth indication information are exactly the same, such as the 5G-RG directly carries the received first indication information in the NAS registration request message and forwards it to the AMF.

[0365] Optionally, the first indication information and the fourth indication information are information with the same meaning but different forms. In this case, the 5G-RG processes the received first indication information to obtain the fourth indication information. For example, the first indication information is the specific format of the identity information of the AUN3 device, and the fourth indication information is the bit indication information.

[0366] It should be understood that regardless of whether the first indication information and the fourth indication information are in the same form, the meanings expressed are the same, so the fourth indication information is not described again, and the description of the fourth indication information can refer to the description of the first indication information mentioned above.

[0367] Optionally, the NAS registration request message also includes fifth indication information, and the fifth indication information is used to indicate whether the AUN3 device supports the NAS protocol. For example, the 5G-RG receives the second indication information, and the 5G-RG learns whether the AUN3 device supports the NAS protocol based on the second indication information, so that the fifth indication information can be carried in the NAS registration request message. The fifth indication information and the second indication information have the same meaning, and the form may be the same or different. For another example, the 5G-RG can determine that the registration request message is a NAS registration request message based on the received registration request message, so that the 5G-RG can determine that the AUN3 device supports the NAS protocol, and thus the fifth indication information can be carried in the NAS registration request message.

[0368] When the fifth indication information is carried in the NAS registration request message to indicate that the AUN3 device supports the 5G NAS protocol, the fourth indication information mentioned above may not be carried. At this time, the AMF can determine whether the AUN3 device supports the first key architecture based on the support of the 5G NAS protocol by the AUN3 device.

[0369] Exemplarily, the third indication information and the fourth indication information mentioned above may be represented by the same indication information. For example, when the first indication information is SUPI or SUCI, and the first indication information is carried in the username or realm part, the first indication information may simultaneously play the role of the third indication information and the fourth indication information. Specifically, when the first indication information is "AUN3-5GK" and "AUN3-N5GK", the first indication information indicates that it is an AUN3 device that supports the 5G key architecture, or an AUN3 device that does not support the 5G key architecture. For another example, when 5G-RG determines that the AUN3 device supports the 5G key architecture, 5G-RG uses the indication information "AUN3-5GK" to indicate that it is both an AUN3 device and a device that supports the 5G key architecture; when 5G-RG determines that the AUN3 device does not support the 5G key architecture, 5G-RG uses the indication information "AUN3-N5GK" to indicate that it is both an AUN3 device and a device that does not support the 5G key architecture. Therefore, one indication information may simultaneously contain the functions of the third indication information and the fourth indication information. The indication information can be added by 5G-RG or from AUN3 device. It should be noted that if the indication information from AUN3 device already carries the functions of the third and fourth indication information, then AMF may not add additional indication information, or may redundantly add the third and fourth indication information according to other needs.

[0370] Specifically, in this embodiment, after receiving the above-mentioned NAS registration request message, the AMF can determine whether the AUN3 device supports the first key architecture based on the information carried in the NAS registration request message. Fig. 9 The method flow shown also includes:

[0371] S940, AMF determines whether the AUN3 device supports the first key architecture.

[0372] The AMF determines that it is the registration of the AUN3 device according to the third indication information in the NAS registration request message, and determines whether the AUN3 device supports the first key architecture according to the fourth indication information or the fifth indication information in the NAS registration request message.

[0373] As a possible implementation manner, when the NAS registration request message carries the fifth indication information, the AMF determines that the AUN3 device supports the first key architecture based on the fifth indication information.

[0374] In this implementation, the AMF can determine through the fifth indication information that the AUN3 device supports the 5G NAS protocol and can interact with the AUN3 device for NAS messages. It can also be understood that the AMF can determine through the fifth indication information that the NAS registration request message is sent by the AUN3 device, and the AMF can regard the AUN3 device as an ordinary terminal device (i.e., a UE that can interact with NAS messages). For example, the AMF generates a 5G NAS key and performs a NAS SMC process with the AUN3 device based on the 5GNAS key.

[0375] As another possible implementation method, AMF determines whether the AUN3 device supports the first key architecture based on the fourth indication information. For example, when the fourth indication information is used to indicate that the 5G key architecture is not supported, if the NAS registration request message does not carry the fourth indication information, the AMF determines that the AUN3 device supports the 5G key architecture. It can also be understood that the AMF does not determine whether the AUN3 device supports the 5G key architecture and generates keys according to the existing key generation method; when the NAS registration request message carries the fourth indication information, the AMF determines that the AUN3 device does not support the 5G key architecture, and generates keys according to the non-5G key architecture. For another example, when the fourth indication information is used to indicate whether the 5G key architecture is supported, the AMF determines whether the AUN3 device supports the 5G key architecture based on the specific value of the fourth indication information, and determines the subsequent key deduction method based on the judgment result.

[0376] In another implementation, the AMF determines whether the AUN3 device supports the first key architecture and the method of using the key according to the fourth indication information and the fifth indication information. For example, when the fourth indication information indicates that the AUN3 device supports the first key architecture and the fifth indication information indicates that the NAS protocol is not supported, the AMF can determine through the fourth indication information that the AUN3 device supports the first key architecture but determines through the fifth indication information that the 5G NAS protocol is not supported, and the AMF generates a 5GNAS key, which is used to derive the key between the 5G-RG and the AUN3 device, and the AMF does not have NAS message interaction with the AUN3 device, or the AMF uses the 5G NAS key to perform NAS interaction with the 5G-RG, or the AMF determines that the interaction object of the NAS message is the 5G-RG, and then different NAS message processing methods can be determined. Different NAS message processing methods include, but are not limited to: for ordinary 5G UE (which can be called a first-class terminal device) and terminal devices that can access 5GC but have only partial functions (which can be called a second-class terminal device). For example, for the first type of terminal devices, 5G UE and AMF will perform the normal NAS SMC process, and NAS security will be activated after the NAS SMC process; while for the second type of terminal devices, NAS security will not be activated after the device or the device that sends the registration request on behalf of the device interacts with the AMF through the NAS SMC process.

[0377] In a possible implementation, the AMF may only determine that the device is an AUN3 device, but not determine whether the AUN3 device supports the first key architecture. That is, the determination of whether the AUN3 device supports the first key architecture in this step may not be performed here, but may be performed in step 993.

[0378] Furthermore, the AMF sends an authentication request message to the authentication network element so that the authentication network element authenticates the AUN3 device. Fig. 9 The method flow shown also includes:

[0379] S950, AMF sends an authentication request message to the authentication network element, or the authentication network element receives an authentication request message from the AMF.

[0380] In this embodiment, the authentication network element is responsible for the authentication between the AUN3 device and the operator network, and may be an AUSF or other network element capable of implementing the function of the AUSF. For ease of description, the following description takes the authentication network element as an example of the AUSF.

[0381] The authentication request message is used to request the AUSF to authenticate the AUN3 device, and the authentication request message includes the identifier and SN name of the AUN3 device. The identifier of the AUN3 device may be the SUCI or SUPI of the AUN3 device, and the value of the SN name includes but is not limited to: a preset fixed value (e.g., 5G: AUN3, which may be a value predefined or preconfigured by the protocol), the PLMN ID of the network to which the AMF belongs, and the Home PLMN ID of the SUCI of the AUN3 device (e.g., 5G: Home PLMN ID of the AUN3 device).

[0382] Optionally, the authentication request message also includes sixth indication information, and the sixth indication information is used to indicate that the device to be authenticated is an AUN3 device. It should be noted that the sixth indication information has the same meaning as the third indication information carried in the NAS registration request message in the above step S930, indicating an AUN3 device, but the specific expression form may be the same or different. For example, the sixth indication information is that the AMF directly forwards the third indication information to the AUSF, then the expression form of the sixth indication information is the same as the first indication information; for another example, the sixth indication information is that the AMF processes the received third indication information (such as refilling) and then sends it to the AUSF, then the expression form of the sixth indication information and the third indication information may be different, or even if the expression form is the same, the AMF does not directly forward the received third indication information to the AUSF.

[0383] Optionally, the authentication request message also includes an eleventh indication information, and the eleventh indication information is used to indicate whether the AUN3 device supports the first key architecture. For example, if the eleventh indication information is that the AMF directly forwards the fourth indication information to the AUSF, then the eleventh indication information and the fourth indication information have the same form of expression; for another example, if the eleventh indication information is that the AMF processes the received fourth indication information (such as refilling) and then sends it to the AUSF, then the eleventh indication information and the fourth indication information may have different forms of expression, or even if the forms of expression are the same, the AMF does not directly forward the received fourth indication information to the AUSF. For another example, the eleventh indication information may be directly the first indication information, or directly the fourth indication information.

[0384] In a possible implementation manner, the authentication request message always carries the eleventh indication information for indicating whether the AUN3 device supports or does not support the first key architecture.

[0385] In another possible implementation, when the AUN3 device supports the first key architecture, the authentication request message carries the eleventh indication information. At this time, the eleventh indication information carried in the authentication request message indicates that the AUN3 device supports the first key architecture, and the eleventh indication information not carried in the authentication request message indicates that the AUN3 device does not support the first key architecture.

[0386] In another possible implementation, when the AUN3 device does not support the first key architecture, the authentication request message carries the eleventh indication information. At this time, the eleventh indication information carried in the authentication request message indicates that the AUN3 device does not support the first key architecture, and the eleventh indication information not carried in the authentication request message indicates that the AUN3 device supports the first key architecture.

[0387] In a possible implementation, in this step, the AUSF does not determine whether the AUN3 device supports the first key architecture. That is, the AUSF determination of whether the AUN3 device supports the first key architecture in this step may not be performed here, but may be performed in step 991. Exemplarily, the authentication request message is called Nausf_UEAuthentication_AuthenticateRequest.

[0388] In this embodiment, after receiving the authentication request message, the AUSF sends an acquisition request message to the data management network element to obtain the authentication credentials required for authentication. Fig. 9 The method flow shown also includes:

[0389] S960, AUSF sends an acquisition request message to the data management network element, or the data management network element receives an acquisition request message from AUSF.

[0390] In this embodiment, the data management network element is responsible for storing the data of the subscribers in the operator network, and may be a UDM or other network element capable of implementing the function of a UDM. For ease of description, the following description takes the data management network element as an example of a UDM.

[0391] Specifically, the acquisition request message is used to request the authentication parameters required for authentication, which are used in the subsequent authentication process. The acquisition request message includes the SUCI or SUPI of the AUN3 device and the SN name.

[0392] Optionally, the acquisition request message also includes the above-mentioned AUN3 device indication information, such as the sixth indication information, or indication information having this function.

[0393] Optionally, the acquisition request message also includes the above-mentioned first key architecture indication information, such as the eleventh indication information, or indication information having this function.

[0394] Exemplarily, the get request message is called Nudm_UEAuthentication_GetRequest.

[0395] If the SN name is not carried in step S950, the AUSF determines that it is an AUN3 device according to the AUN3 device indication information, generates an SN name according to the method in step S950, and sends it to the UDM in step S960.

[0396] S970, UDM generates an authentication vector.

[0397] Exemplarily, when the UDM receives the SUCI of the AUN3 device, the UDM obtains the SUPI of the AUN3 device through the SUCI of the AUN3 device. Further, the UDM determines the authentication method through the SUPI of the AUN3 device or the AUN3 device information.

[0398] Specifically, the UDM may determine the subscription data according to the SUPI of the AUN3 device, and then determine the authentication method according to the subscription data; or,

[0399] Based on the sixth indication information of AUN3, UDM determines that it is an AUN3 device and then determines the authentication method.

[0400] Furthermore, the UDM generates a corresponding authentication vector (AV) according to the authentication method.

[0401] For example, the UDM determines to use the EAP-AKA' authentication method based on the AUN3 device information, and generates an EAP-AKA' authentication vector using the received SN name.

[0402] It should be understood that if the type of SUCI is anonymous SUCI, the authentication method is determined according to the realm part in the SUCI, and an authentication vector corresponding to the authentication method is further generated.

[0403] S980, UDM sends a get response message to AUSF, or AUSF receives a get response message from UDM.

[0404] The get response message includes the authentication vector.

[0405] Exemplarily, the get response message is called Nudm_UEAuthentication_GetResponse message. Optionally, when the UDM receives the SUCI, the get response message carries the SUPI of the AUN3 device.

[0406] S990, AUN3 device and AUSF perform two-way authentication.

[0407] In this embodiment, there is no limitation on the process of two-way authentication between the AUN3 device and the AUSF, and reference may be made to the description of the process of two-way authentication between the AUN3 device and the AUSF in the current related technology.

[0408] It should be noted that during the authentication process, the AUN3 device also determines the SN name. Specifically, the AUN3 device generates the same SN name using the method in step S950. This embodiment does not limit the specific time when the AUN3 device generates the SN name. For example, the AUN3 device can generate the SN name after receiving the authentication vector, or it can generate the SN name before receiving the authentication vector. The AUN3 device uses the SN name and the parameters in the authentication vector to verify the authenticity of the network side.

[0409] S991, AUSF determines the key generation method and generates a key.

[0410] Specifically, if AUSF has made a judgment after receiving the step S950 message, it does not need to make another judgment; if AUSF does not make a judgment after receiving the step S950 message, AUSF determines whether the AUN3 device supports the first key architecture, and determines the key generation method based on the judgment result. For example, AUSF can determine the key generation method based on the received indication information (such as the eleventh indication information or the sixth indication information mentioned above). Among them, the eleventh indication information can be directly the first indication information, or directly the fourth indication information, and the sixth indication information can be directly the third indication information. For the convenience of description, the following is an example of AUSF determining the key generation method based on the eleventh indication information.

[0411] In a possible implementation, when the above-mentioned authentication request message indicates through the eleventh indication information that the AUN3 device does not support the 5G key architecture, if the authentication request message does not carry the eleventh indication information, the AUSF determines that the AUN3 device supports the 5G key architecture. It can also be understood that the AUSF does not determine whether the AUN3 device supports the 5G key architecture, and generates keys according to the existing method of generating keys. At this time, a third key (denoted as Kseaf) is generated; when the authentication request message carries the eleventh indication information, the AUSF determines that the AUN3 device does not support the 5G key architecture, and generates keys according to the non-5G key architecture. At this time, a fourth key (denoted as MSK) is generated.

[0412] In a possible implementation, when the eleventh indication information in the above-mentioned authentication request message indicates whether the AUN3 device supports the 5G key architecture, if the authentication request message carries the eleventh indication information indicating that the AUN3 device supports the 5G key architecture, the AUSF generates a third key (denoted as Kseaf); when the eleventh indication information indicates that the 5G key architecture is not supported, the AUSF determines that the AUN3 device does not support the 5G key architecture, then generates a key according to the non-5G key architecture, and at this time, a fourth key (denoted as MSK) is generated.

[0413] S992, AUSF sends an authentication response message to AMF, or AMF receives an authentication response message from AUSF.

[0414] Exemplarily, the authentication response message is called a Nausf_UEAuthentication_AuthenticateResponse message. The Nausf_UEAuthentication_AuthenticateResponse message carries EAP-Success, the SUPI of the AUN3 device, the third key, or the fourth key.

[0415] S993, AMF determines the second key.

[0416] As a possible implementation method, if AMF has made a judgment in step S940, AMF determines the method of generating the second key according to the judgment result of S940, and then generates the second key; if AMF has not made a judgment in step S940, AMF first determines, based on the judgment method of the above step S940, that the AUN3 device supports the first key architecture, or determines that the AUN3 device does not support the first key architecture, and then determines the method of obtaining the second key, and further generates the second key if the second key needs to be generated.

[0417] In this implementation, the first key architecture is taken as the 5G key architecture as an example. When the AUN3 device supports the 5G key architecture, the AMF generates the second key using the third key.

[0418] In one possible implementation, the AMF uses the third key to directly generate the second key. For example, if the second key is K 5G-RG , then the generation method can be: second key = KDF (third key, first parameter, second parameter). At least one of the first parameter and the second parameter is used. The first parameter and the second parameter can be values ​​in the form of strings, numbers, etc. For example, the first parameter is a fixed value. For example, it is a value of all 0s, or it is 2 32 The value of -1, or the SQN in the authentication vector, etc. The second parameter, for example, is a string "AUN3", for example, a distinguishing identifier 0x02. This embodiment does not limit the use of more input parameters in the DKF function.

[0419] In another implementation, AMF may also use the third key to generate the sixth key, and then use the sixth key to generate the second key. For example, if the second key is Kwagf, the generation method may be: second key = KDF (sixth key, first parameter, second parameter). The sixth key is generated based on the third key. For example, if the sixth key is Kamf, the specific generation method may refer to the prior art. At least one of the first parameter and the second parameter is used. The first parameter and the second parameter may be in the form of a string, a number, or the like. For example, the first parameter is a fixed value. For example, it is a value of all 0s, or it is 2. 32 The value of -1, or the SQN in the authentication vector, etc. For another example, the first parameter is the string "AUN3". The second parameter, for example, is the string "AUN3", for example, the distinguishing identifier 0x02. This embodiment does not limit the use of more input parameters in the DKF function.

[0420] In addition, optionally, the AMF further uses the sixth key to generate NAS encryption keys and NAS integrity protection keys.

[0421] When the AUN3 device does not support the 5G key architecture, the AMF will no longer generate a new key after receiving the fourth key, and will determine the fourth key as the second key. Alternatively, the AMF will use the fourth key to generate the NAS encryption key and the NAS integrity protection key.

[0422] In another implementation, if the AMF determines that the AUN3 device supports the first key architecture by determining that the AUN3 device supports 5G NAS, the AMF can also and further use the sixth key to generate a NAS encryption key and a NAS integrity protection key, and optionally initiate a NAS SMC process between the AUN3 device and the NAS key. Fig. 9 The method flow shown may also include:

[0423] S994: ​​NAS SMC process is performed between AMF and AUN3 devices.

[0424] When AMF determines that the AUN3 device supports the first key architecture, AMF sends a NAS SMC message to 5G-RG. The NAS SMC message uses a null integrity protection algorithm. After receiving the NAS SMC message, 5G-RG replies with a NAS SMP message to AMF. The NAS SMP message uses a null encryption algorithm and a null integrity protection algorithm.

[0425] When AMF determines that the AUN3 device supports the NAS protocol, AMF sends a NAS SMC message to the AUN3 device. The NASSMC message is protected by a non-null integrity protection algorithm and a NAS integrity protection key. After receiving the NASSMC message, the AUN3 device verifies the integrity protection of the NAS SMC message using the same NAS key and non-null integrity protection algorithm. After successful verification, the AUN3 device replies with a NAS SMP message to the AMF. The NAS SMP message uses a non-null encryption algorithm and a non-null integrity protection algorithm, and uses a NAS integrity protection key and a NAS encryption key for security protection.

[0426] When AMF determines that the AUN3 device does not support the first key architecture, AMF sends a NAS SMC message to 5G-RG. The NAS SMC message uses a null integrity protection algorithm. After receiving the NAS SMC message, 5G-RG replies with a NAS SMP message to AMF, which uses a null encryption algorithm and a null integrity protection algorithm.

[0427] S995, AMF sends a message indicating successful authentication and the fifth key to 5G-RG, or in other words, 5G-RG receives the fifth key from AMF.

[0428] Exemplarily, the AMF sends a NAS Security Mode Command to the 5G-RG to activate NAS security. The NAS Security Mode Command includes EAP-Success, which indicates that the authentication performed by the core network is successful and is used to indicate that the identity authentication is successful.

[0429] In one possible implementation, the AMF uses the second key as the fifth key and may send the fifth key (e.g., K5G-RG) to the 5G-RG via a NAS message or an N2 message. For example, the AMF sends the fifth key via a NAS downlink transport (NAS DLtransport) message or an N2 initial context setup request (N2 initial context setup request) message.

[0430] In another possible implementation, AMF sends the second key to W-AGF, and W-AGF determines a method for obtaining the fifth key based on whether the AUN3 device supports the first key architecture. Specifically, the method for W-AGF to determine whether the AUN3 device supports the first key architecture can refer to the relevant description of the judgment made by AMF in step S940, or AMF sends the twelfth indication information to W-AGF, and W-AGF determines whether the AUN3 device supports the first key architecture based on the twelfth indication information. When it is determined that the AUN3 device does not support the first key architecture, the second key is directly sent to 5G-RG as the fifth key; when it is determined that the first key architecture is supported, W-AGF generates the fifth key based on the second key, and then sends the fifth key to 5G-RG through a second response message.

[0431] S996, 5G-RG establishes a secure connection with the AUN3 device.

[0432] Specifically, the 5G-RG and the AUN3 device establish a secure connection based on the fifth key. For example, the 5G-RG and the AUN3 device perform a 4-way handshake to establish a secure connection.

[0433] Before establishing a secure connection, the AUN3 device generates key #1 based on the fifth key, and the key #1 generates the first key required for security protection. The first key is used to perform security protection on the secure connection established between the 5G-RG and the AUN3. For example, the first key encrypts and performs integrity protection on the connection between the AUN3 device and the 5G-RG. For example, the sender encrypts and performs integrity protection on the message based on the first key, and the receiver decrypts and performs integrity protection verification on the message based on the first key. If the AUN3 device supports the first key architecture (taking the first key architecture as the 5G key architecture as an example for explanation), the AUN3 device generates key #1 using the fifth key. Specifically, key #1 is PMK, the fifth key is Kwagf, and the first key is a key further generated based on PMK.

[0434] In a possible implementation, the AUN3 device and the 5G-RG respectively use the fifth key to directly generate key #1. For example, if key #1 is K 5G-RG , the generation method can be: Key #1 = KDF (fifth key, first parameter, second parameter). At least one of the first parameter and the second parameter is used. The first parameter and the second parameter can be values ​​in the form of strings, numbers, etc. For example, the first parameter is a fixed value. For example, it is a value of all 0s, or it is 2 32 The value of -1, or the SQN in the authentication vector, etc. The second parameter, for example, is the string "AUN3", for example, the distinguishing identifier 0x02. This embodiment does not limit the use of more input parameters in the DKF function. After generating key #1, the first key is generated according to key #1.

[0435] In another implementation, the AUN3 device and the 5G-RG can also use the fifth key to generate the sixth key, then use the sixth key to generate the second key, and then generate key #1 based on the second key. For example, the second key is Kwagf, and PMK is regenerated based on Kwagf.

[0436] If the AUN3 device does not support the first key architecture (taking the first key architecture as the 5G key architecture as an example for explanation), the fifth key is MSK.

[0437] Optionally, in a possible implementation, after the 5G-RG establishes a secure connection with the AUN3 device, the 5G-RG replies to the AMF with a message notifying that the secure connection establishment is complete. Exemplarily, the notification may be sent via a NAS message or an N2 message. For example, the notification may be sent via a NAS uplink transport message or an N2 initial context setup ack message.

[0438] In another possible implementation, after 5G-RG establishes a secure connection with the AUN3 device, 5G-RG replies to the W-AGF, and W-AGF then notifies AMF that the secure connection is established.

[0439] Fig. 9 In the embodiment shown, 5G-RG can determine whether the AUN3 device supports the first key architecture based on the information sent by the AUN3 device, and AMF can determine whether the AUN3 device supports the first key architecture based on the information reported by 5G-RG. The present application also provides a communication method, in which AMF and AUSF can determine whether the AUN3 device supports the first key architecture based on the information received from UDM. Fig.10 This communication method is described in detail.

[0440] Fig.10 This is a schematic flow chart of a communication method provided by the present application. It includes the following steps:

[0441] S1011, 5G-RG is registered to 5GC.

[0442] refer to Fig. 9 The description of step S911 in will not be repeated here.

[0443] S1010, the AUN3 device establishes a connection with the first gateway.

[0444] refer to Fig. 9 The description of step S910 is not repeated here.

[0445] S1021, 5G-RG sends a first request message to the AUN3 device, or in other words, the AUN3 device receives the first request message from the 5G-RG.

[0446] refer to Fig. 9 The description of step S921 in will not be repeated here.

[0447] S1020, the AUN3 device sends a first response message to the 5G-RG, or the 5G-RG receives the first response message from the AUN3 device.

[0448] The description of the first response message can be found in Fig. 9 The difference is that the first response message in this embodiment may not indicate whether the AUN3 device supports the first key architecture, which will not be described here.

[0449] S1030, 5G-RG sends a NAS registration request message to AMF, or AMF receives a NAS registration request message from 5G-RG.

[0450] For a description of the NAS registration request message, please refer to Fig. 9 The difference is that the NAS registration request message in step S930 in this embodiment may not carry the fourth indication information, which will not be described here. For the sake of distinction, the NAS registration request message in this embodiment is recorded as NAS registration request message #1.

[0451] S1040, AMF sends an authentication request message to AUSF, or AUSF receives an authentication request message from AMF.

[0452] For a description of the authentication request message, please refer to Fig. 9 The description of the authentication request message in step S950 in the embodiment. In this embodiment, the authentication request message may not carry the eleventh indication information, which will not be repeated here. For the convenience of distinction, the NAS registration request message in this embodiment is recorded as authentication request message #1.

[0453] S1050, AUSF sends an acquisition request message to UDM, or UDM receives an acquisition request message from AUSF.

[0454] refer to Fig. 9 The description of step S960 is not repeated here.

[0455] S1060, the UDM determines the authentication vector and obtains whether the AUN3 device supports the first key architecture.

[0456] Specifically, the method for UDM to determine the authentication vector can be referred to Fig. 9 The description of how to determine the authentication vector in step S970 will not be repeated here. This embodiment mainly involves how UDM obtains information on whether the AUN3 device supports the first key architecture, and how to indicate to AMF and AUSF whether the AUN3 device supports the first key architecture.

[0457] As a possible implementation manner, UDM can obtain the SUPI of the AUN3 device in step S1060, and then determine the subscription data according to the SUPI of the AUN3 device, and then determine whether the AUN3 device supports the first key architecture and / or supports 5G NAS according to the subscription data, and obtain the seventh indication information and / or the eighth indication information, the seventh indication information is used to indicate whether the AUN3 device supports the first key architecture, and the eighth indication information is used to indicate whether the AUN3 device supports 5G NAS.

[0458] As another possible implementation manner, the subscription data of the AUN3 device includes seventh indication information,

[0459] As another possible implementation, the UDM may obtain the SUPI of the AUN3 device in step 1060, which SUPI itself is a SUPI in a special format (eg, <5G_device_unique_identity>@AUN3-5GC.mnc as described above). <mnc>.mcc <mcc>.3gppnetwork.org), UDM obtains SUPI, which is equivalent to obtaining information on whether the AUN3 device supports the first key architecture and / or whether it supports 5G NAS. At this time, AUN3-5GC is sent to AUSF as part of SUPI, so the seventh indication information can be said to be SUPI itself, or the AUN3-5GC field in SUPI.

[0460] It should be understood that the above-mentioned several implementation methods are only examples of how UDM obtains whether the AUN3 device supports the first key architecture and / or supports 5G NAS, and does not constitute any limitation on the scope of protection of the present application. UDM can also obtain information on whether the AUN3 device supports the first key architecture and / or supports 5G NAS in other ways, for example, judging whether the AUN3 device supports the first key architecture and / or supports 5G NAS based on the SUCI of the AUN3 device; for example, obtaining historical communication data from the 5G-RG that the AUN3 device has accessed, and judging whether the AUN3 device supports the first key architecture and / or supports 5G NAS based on the historical communication data, which will not be repeated here.

[0461] Further, after the UDM obtains the information of whether the AUN3 device supports the first key architecture and / or whether it supports 5G NAS, the UDM may transmit the seventh indication information to the AUSF so that the AUSF determines how to generate the key, that is, determines how to generate the key according to whether the AUN3 device supports the first key architecture and / or whether it supports 5G NAS. Fig.10 The method flow shown also includes:

[0462] S1070, UDM sends a get response message to AUSF, or AUSF receives a get response message from UDM.

[0463] For the sake of distinction, the acquisition response message in this embodiment is recorded as acquisition response message #1. The acquisition response message #1 includes information about the authentication vector and, optionally, seventh indication information, the seventh indication information being used to indicate whether the AUN3 device supports the first key architecture.

[0464] Exemplarily, possible forms of the seventh indication information include, but are not limited to: a SUPI in a special format, a SUCI in a special format, a string information, and at least one bit information. For a specific description, please refer to Fig. 9 The description of the first indication information in the communication method shown is not repeated here.

[0465] Optionally, when the UDM receives the SUCI, the SUPI of the AUN3 device carried in the response message #1 is obtained. If the SUPI of the AUN3 device can indicate whether the AUN3 device supports the first key architecture (e.g., the SUPI is a SUPI in a special format), the seventh indication information can be understood as the SUPI of the AUN3 device, or a field in the SUPI indicating whether the first key architecture is supported.

[0466] Optionally, when UDM determines whether the AUN3 device supports 5G NAS, the eighth indication information is carried in the acquisition response message #1, and the eighth indication information is used to indicate whether the AUN3 device supports 5G NAS.

[0467] S1080, the AUN3 device and the AUSF perform two-way authentication.

[0468] refer to Fig. 9 The description of step S990 is not repeated here.

[0469] Furthermore, in this embodiment, after receiving the above-mentioned acquisition response message #1, the AUSF can determine whether the AUN3 device supports the first key architecture.

[0470] Fig.10 The method flow shown also includes:

[0471] S1090, AUSF determines the key generation method and generates a key.

[0472] refer to Fig. 9 The description of step S991 in step S1010 will not be repeated here. It should be additionally noted that, in the case where the seventh indication information must be sent, the AUSF determines whether the AUN3 device supports the first key architecture and determines the key generation method based on the seventh indication information of step S1010. In the case where the seventh indication information is optional to send, the AUSF determines whether the AUN3 device supports the first key architecture and determines the key generation method based on whether the seventh indication information of step S1010 appears.

[0473] S1091, AUSF sends an authentication response message to AMF, or AMF receives an authentication response message from AUSF.

[0474] For the sake of distinction, the authentication response message in this embodiment is recorded as authentication response message #1. The authentication response message #1 carries ninth indication information, which is used to indicate whether the AUN3 device supports the first key architecture.

[0475] Optionally, the ninth indication information and the seventh indication information are the same information, such as AUSF forwards the received seventh indication information to AMF.

[0476] Optionally, the ninth indication information and the seventh indication information are information with the same meaning but different forms. For example, the 5G-RG processes the received seventh indication information to obtain the ninth indication information.

[0477] It should be understood that regardless of whether the ninth indication information and the seventh indication information are in the same form, the meanings expressed are the same, so the ninth indication information is not described again, and the description of the ninth indication information can refer to the description of the seventh indication information mentioned above.

[0478] Exemplarily, the authentication response message #1 also includes the tenth indication information, which is used to indicate whether the AUN3 device supports the NAS protocol. For example, the AUSF receives the eighth indication information, and the AUSF learns whether the AUN3 device supports the NAS protocol based on the eighth indication information, so that the tenth indication information can be carried in the authentication response message #1. The tenth indication information has the same meaning as the eighth indication information, and the form may be the same or different.

[0479] S1092, AMF determines whether the AUN3 device supports the first key architecture.

[0480] After receiving the above-mentioned authentication response message #1, the AMF can determine whether the AUN3 device supports the first key architecture.

[0481] For specific determination methods, please refer to Fig. 9 The description of step S940 in step S1010 will not be repeated here. It should be noted that, in the case where the ninth indication information must be sent, AMF determines whether the AUN3 device supports the first key architecture according to the ninth indication information of step S1010, and determines the key generation method. In the case where the ninth indication information is optional to send, AMF determines whether the AUN3 device supports the first key architecture according to whether the ninth indication information of step S1010 appears, and determines the key generation method.

[0482] As a possible implementation method, AMF determines that the AUN3 device supports the first key architecture and 5G NAS based on the judgment of the above step S1092.

[0483] Optionally, in this implementation, if the AMF determines that the AUN3 device supports the first key architecture by determining that the AUN3 device supports 5G NAS, the AMF can also and further generate a NAS key, and initiate a NAS SMC process between the AUN3 device and the AUN3 device based on the NAS key.

[0484] Fig.10 The method flow shown may also include:

[0485] S1094: NAS SMC process is performed between AMF and AUN3 devices.

[0486] As another possible implementation manner, the AMF determines that the AUN3 device supports the first key architecture based on the judgment in the above step S1092.

[0487] In this implementation, the AMF generates Kamf using the third key and the SUPI of the AUN3 device, and further uses Kamf to generate the key K5G-RG, or Kwagf.

[0488] As another possible implementation manner, the AMF determines that the AUN3 device supports the first key architecture based on the judgment in the above step S1092.

[0489] In this implementation, the AMF does not need to further generate the second key, and can simply pass the received third key to the 5G-RG.

[0490] Fig.10 The method flow shown also includes:

[0491] S1093, AMF determines the second key.

[0492] S1095, AMF sends the fifth key to 5G-RG, or in other words, 5G-RG receives the fifth key from AMF.

[0493] refer to Fig. 9 The description of step S995 is not repeated here.

[0494] S1096, 5G-RG establishes a secure connection with the AUN3 device.

[0495] refer to Fig. 9 The description of step S996 will not be repeated here.

[0496] Fig.10 In the illustrated embodiment, AMF and AUSF can determine whether the AUN3 device supports 5G NAS or the first key architecture based on the indication information of UDM, so that subsequent core network elements can clearly understand whether the AUN3 device currently requesting access supports the first key architecture, and select a suitable key derivation method to generate keys to improve the security of communications.

[0497] It should be understood that the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0498] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0499] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for exemplary description (such as AUN3 devices, 5G-RG, AMF, AUSF and UDM, etc.), and it should be understood that the specific form of the device is not limited in the embodiments of the present application. For example, devices that can achieve the same function in the future are applicable to the embodiments of the present application.

[0500] It can be understood that in the above-mentioned method embodiments, the methods and operations implemented by devices (such as AUN3 devices, 5G-RG, AMF, AUSF and UDM, etc.) can also be implemented by components of the device (such as chips or circuits).

[0501] Above, combined Fig. 9 and Fig.10 The communication method provided by the embodiment of the present application is described in detail. The above communication method is mainly introduced from the perspective of interaction between various protocol layers of the terminal device. It can be understood that in order to realize the above functions, the terminal device includes a hardware structure and / or software module corresponding to each function.

[0502] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0503] The following combination Figures 11 to 13 The communication device provided by the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, the content not described in detail can be referred to the method embodiment above, and some content will not be repeated for the sake of brevity.

[0504] The embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0505] Fig.11 1 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to perform data processing, or in other words, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform other operations besides receiving and sending. The transceiver module 11 can also be called a communication interface or a communication unit.

[0506] Optionally, the device 10 may further include a storage module 13, which may be used to store instructions and / or data. The processing module 12 may read the instructions and / or data in the storage module so that the device implements the actions of the devices in the aforementioned method embodiments.

[0507] In one design, the apparatus 10 may correspond to the AUN3 device in the above method embodiment, or a component (such as a chip) of the AUN3 device.

[0508] The device 10 can implement the steps or processes executed by the AUN3 device in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the AUN3 device in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the AUN3 device in the above method embodiment.

[0509] In one possible implementation, the transceiver module 11 is used to receive a first request message from a first gateway, where the first request message is used to request identity information of a terminal device, where the terminal device accesses a core network through a connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; the transceiver module 11 is used to send a first response message to the first gateway, where the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; the transceiver module 11 is used to receive a message from the first gateway indicating that the authentication is successful; the processing module 12 is used to generate a first key according to whether the terminal device supports the first key architecture, where the first key is used to securely protect the connection between the terminal device and the first gateway.

[0510] Wherein, when the device 10 is used to perform Fig. 9 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S910, S921, S920, S994 and S996; the processing module 12 can be used to execute the processing steps in the method.

[0511] When the device 10 is used to perform Fig.10 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1010, S1021, S1020, S1094 and S1096; the processing module 12 can be used to execute the processing steps in the method.

[0512] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0513] In another design, the device 10 may correspond to the first gateway in the above method embodiment, or a component (such as a chip) of the first gateway.

[0514] The device 10 can implement the steps or processes executed by the first gateway in the above method embodiment, wherein the transceiver module 11 can be used to perform the transceiver-related operations of the first gateway in the above method embodiment, and the processing module 12 can be used to perform the processing-related operations of the first gateway in the above method embodiment.

[0515] In one possible implementation, the transceiver module 11 is used to send a first request message to a terminal device, wherein the first request message is used to request identity information of the terminal device, the terminal device accesses the core network through the connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; the transceiver module 11 is used to receive a first response message from the terminal device, wherein the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; the transceiver module 11 is used to send the identity information and indication information indicating whether the terminal device supports the first key architecture to an access mobile management network element, wherein the access mobile management network element is located in the core network; the transceiver module 11 is used to send a message to the terminal device indicating that the identity authentication is successful; the processing module 12 generates a first key based on the fifth key, and the first key is used to securely protect the connection between the terminal device and the first gateway.

[0516] Wherein, when the device 10 is used to perform Fig. 9 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S910, S921, S920, S930, S995 and S996; the processing module 12 can be used to execute the processing steps in the method, such as step S911.

[0517] When the device 10 is used to perform Fig.10 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1010, S1021, S1020, S1030, S1095 and S1096; the processing module 12 can be used to execute the processing steps in the method, such as step S1011.

[0518] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0519] In yet another design, the apparatus 10 may correspond to the access mobility management network element in the above method embodiment, or may be a component (such as a chip) of the access mobility management network element.

[0520] The device 10 can implement the steps or processes corresponding to those executed by the access mobility management network element in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the access mobility management network element in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the access mobility management network element in the above method embodiment.

[0521] In one possible implementation, the transceiver module 11 is used to receive the identity information and indication information indicating whether the terminal device supports the first key architecture from the first gateway; the processing module 12 is used to generate the fifth key according to whether the terminal device supports the first key architecture; the transceiver module 11 is used to indicate the message of successful identity authentication and the fifth key.

[0522] Wherein, when the device 10 is used to perform Fig. 9 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S930, S950, S992 and S994; the processing module 12 can be used to execute the processing steps in the method, such as steps S940 and S993.

[0523] When the device 10 is used to perform Fig.10 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1091 and S1094; the processing module 12 can be used to execute the processing steps in the method, such as steps S1092 and S1093.

[0524] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0525] In one design, the device 10 may correspond to the data management network element in the above method embodiment, or a component of the data management network element (such as a chip).

[0526] The device 10 can implement the steps or processes executed by the data management network element in the above method embodiment, wherein the transceiver module 11 can be used to execute the operations related to the transmission and reception of the data management network element in the above method embodiment, and the processing module 12 can be used to execute the operations related to the processing of the data management network element in the above method embodiment.

[0527] In one possible implementation, the transceiver module 11 is used to receive an acquisition request message from an authentication network element, where the acquisition request message is used to request an authentication vector required for authentication, and the acquisition request message includes an identifier of an authenticatable non-third generation partnership project AUN3 device; the transceiver module 11 is used to send an acquisition response message to the authentication network element, where the acquisition response message includes information about the authentication vector and seventh indication information, and the seventh indication information is used to indicate whether the AUN3 device supports a first key architecture, wherein the authentication vector information and the seventh indication information are obtained based on the identifier of the AUN3 device.

[0528] Wherein, when the device 10 is used to perform Fig. 9 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S960 and S980; the processing module 12 can be used to execute the processing steps in the method, such as step S970.

[0529] When the device 10 is used to perform Fig.10 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1050 and S1070; the processing module 12 can be used to execute the processing steps in the method, such as step S1060.

[0530] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0531] In one design, the apparatus 10 may correspond to the authentication network element in the above method embodiment, or a component of the authentication network element (such as a chip).

[0532] The device 10 can implement the steps or processes executed by the authentication network element in the above method embodiment, wherein the transceiver module 11 can be used to execute the operations related to the transmission and reception of the authentication network element in the above method embodiment, and the processing module 12 can be used to execute the operations related to the processing of the authentication network element in the above method embodiment.

[0533] In a possible implementation, the transceiver module 11 is used to receive an authentication request message from an access mobility management network element, the authentication request message is used to request the authentication network element to authenticate an authenticatable non-third generation partnership project AUN3 device, and the authentication request message includes an identifier of the AUN3 device; the transceiver module 11 is used to send an acquisition request message to a data management network element, the acquisition request message is used to request to acquire an authentication vector required for authentication, and the acquisition request message includes the identifier of the AUN3 device; the transceiver module 11 is used to receive an acquisition response message from the data management network element, and the acquisition response message includes the information of the authentication vector. information and seventh indication information, the seventh indication information is used to indicate whether the AUN3 device supports the first key architecture; the processing module 12 is used to generate a third key according to whether the AUN3 device supports the first key architecture and the identifier of the AUN3 device; the transceiver module 11 is used to send an authentication response message to the access mobility management network element, the authentication response message includes the third key and ninth indication information, the ninth indication information is used to indicate whether the AUN3 device supports the first key architecture; wherein the third key generation methods corresponding to the AUN3 device supporting the first key architecture and the AUN3 device not supporting the first key architecture are different.

[0534] Wherein, when the device 10 is used to perform Fig. 9 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S950, S960, S980 and S992; the processing module 12 can be used to execute the processing steps in the method, such as step S991.

[0535] When the device 10 is used to perform Fig.10 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1040, S1050, S1070 and S1091; the processing module 12 can be used to execute the processing steps in the method, such as step S1090.

[0536] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0537] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, a person skilled in the art may understand that the device 10 may be specifically a mobile management network element in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the mobile management network element in the above-mentioned method embodiments; or, the device 10 may be specifically a terminal device in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the terminal device in the above-mentioned method embodiments. To avoid repetition, it will not be repeated here.

[0538] The device 10 of each of the above schemes has the function of implementing the corresponding steps performed by the devices in the above methods (such as AUN3 devices, 5G-RG, AMF, AUSF and UDM, etc.). This function can be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as processing modules, can be replaced by processors to respectively perform the transceiver operations and related processing operations in each method embodiment.

[0539] In addition, the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.

[0540] Fig.12 2 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, and the processor 21 is used to execute a computer program or instruction stored in a memory 22, or read data / signaling stored in the memory 22 to execute the method in each method embodiment above. Optionally, there are one or more processors 21.

[0541] Alternatively, if Fig.12 As shown, the device 20 also includes a memory 22, which is used to store computer programs or instructions and / or data. The memory 22 can be integrated with the processor 21, or can also be separately set. Optionally, the memory 22 is one or more.

[0542] Alternatively, if Fig.12 As shown, the device 20 further includes a transceiver 23, and the transceiver 23 is used for receiving and / or sending signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

[0543] As a solution, the apparatus 20 is used to implement the operations performed by the AUN3 device in the above method embodiments.

[0544] As another solution, the device 20 is used to implement the operations performed by the 5G-RG in the above method embodiments.

[0545] As another solution, the device 20 is used to implement the operations performed by the AMF in the above method embodiments.

[0546] As another solution, the device 20 is used to implement the operations performed by the AUSF in the above method embodiments.

[0547] As another solution, the device 20 is used to implement the operations performed by the UDM in the above method embodiments.

[0548] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0549] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: 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 rambus RAM (DR RAM).

[0550] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0551] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0552] Fig.13 Schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0553] Among them, the logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 30 can implement the methods and functions of each embodiment of the present application. The input / output interface 32 can be an input / output circuit in the chip system 30, outputting information processed by the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.

[0554] As a solution, the chip system 30 is used to implement the operations performed by the AUN3 device, 5G-RG, AMF, AUSF or UDM in the above method embodiments.

[0555] For example, the logic circuit 31 is used to implement the processing-related operations performed by the AUN3 device, 5G-RG, AMF, AUSF or UDM in the above method embodiments; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the AUN3 device, 5G-RG, AMF, AUSF or UDM in the above method embodiments.

[0556] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods performed by the AUN3 device, 5G-RG, AMF, AUSF or UDM in the above-mentioned method embodiments.

[0557] For example, when the computer program is executed by a computer, the computer can implement the methods performed by the AUN3 device, 5G-RG, AMF, AUSF or UDM in each embodiment of the above method.

[0558] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by the AUN3 device, 5G-RG, AMF, AUSF or UDM in the above-mentioned method embodiments.

[0559] An embodiment of the present application also provides a communication system, including the aforementioned AUN3 device, 5G-RG, AMF, AUSF and UDM.

[0560] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0561] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0562] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0563] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.< / mcc> < / mnc> < / mcc> < / mnc>

Claims

1. A communication method, It is characterized in that include: receiving a first request message from a first gateway, wherein the first request message is used to request identity information of a terminal device, the terminal device accesses a core network through a connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; Sending a first response message to the first gateway, where the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports a first key architecture; receiving a message from the first gateway indicating that the identity authentication is successful; A first key is generated according to whether the terminal device supports the first key architecture, where the first key is used to securely protect a connection between the terminal device and the first gateway.

2. The method according to claim 1, It is characterized in that The generating the first key according to whether the terminal device supports the first key architecture includes: In a case where the terminal device supports the first key architecture, generating the first key according to a first key derivation method; When the terminal device does not support the first key architecture, the first key is generated according to a second key derivation method.

3. The method according to claim 1 or 2, It is characterized in that The first response message is used to indicate whether the terminal device supports the first key architecture, including: The identity information is used to indicate whether the terminal device supports the first key architecture.

4. The method according to claim 3, It is characterized in that The identity information is used to indicate whether the terminal device supports the first key architecture, including: When the identity information is a first identifier, the identity information is used to indicate that the terminal device does not support the first key architecture; or, When the identity information is a second identifier, the identity information is used to indicate that the terminal device supports the first key architecture.

5. The method according to claim 3, It is characterized in that The identity information is used to indicate whether the terminal device supports the first key architecture, including: When the identity information is of the first type of the first identifier, the identity information is used to indicate that the terminal device does not support the first key architecture; or, When the identity information is of the second type of the first identifier, the identity information is used to indicate that the terminal device supports the first key architecture.

6. The method according to claim 3, It is characterized in that The identity information is used to indicate whether the terminal device supports the first key architecture, including: The identity information includes a field for indicating whether the terminal device supports the first key architecture.

7. The method according to claim 1 or 2, It is characterized in that The first response message also includes first indication information; The first response message is used to indicate whether the terminal device supports the first key architecture, including: The first indication information is used to indicate whether the terminal device supports the first key architecture.

8. The method according to claim 7, It is characterized in that The first indication information includes at least one of the following: character string information, bit information or non-access layer protocol data unit.

9. The method according to any one of claims 1 to 8, It is characterized in that Before receiving the message from the first gateway indicating that the identity authentication is successful, the method further includes: Determine a service network name, the service network name is used for the identity authentication, and the service network name includes at least one of the following: a preset fixed value, a land public mobile communication network identifier PLMNID of the terminal device, or a PLMN ID of an access mobility management network element serving the first gateway.

10. The method according to any one of claims 1 to 9, It is characterized in that Before receiving the first request message from the first gateway, the method further includes: An access mode for accessing the first gateway is determined, where the access mode includes trusted non-3rd Generation Partnership Project 3GPP access or untrusted non-3GPP access.

11. The method according to any one of claims 1 to 10, It is characterized in that The first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

12. A communication method, It is characterized in that include: Sending a first request message to a terminal device, where the first request message is used to request identity information of the terminal device, where the terminal device accesses a core network through a connection between the terminal device and a first gateway, and the identity information is used by the core network to authenticate the terminal device; receiving a first response message from the terminal device, the first response message including the identity information, and the first response message being used to indicate whether the terminal device supports a first key architecture; Sending the identity information and indication information for indicating whether the terminal device supports the first key architecture to an access mobility management network element, the access mobility management network element being located in the core network; Receiving a message indicating success of the identity authentication and a fifth key from the access mobility management network element, where the fifth key is generated based on whether the terminal device supports the first key architecture; Sending a message to the terminal device indicating that the identity authentication is successful; A first key is generated according to the fifth key, where the first key is used to securely protect a connection between the terminal device and the first gateway.

13. The method according to claim 12, It is characterized in that The fifth key is generated based on whether the terminal device supports the first key architecture, including: In the case where the terminal device supports the first key architecture, the fifth key is generated according to the first key derivation method; When the terminal device does not support the first key architecture, the fifth key is generated according to the second key derivation method.

14. The method according to claim 12 or 13, It is characterized in that The sending the identity information and the indication information used to indicate whether the terminal device supports the first key architecture to the access mobility management network element includes: Sending the identity information and the indication information for indicating whether the terminal device supports the first key architecture to the access mobility management network element through a non-access layer NAS registration request message; The first response message includes the NAS registration request message, or the NAS registration request message is generated by the first gateway according to the first response message.

15. The method according to claim 14, It is characterized in that The method further comprises: The first gateway sends indication information to the access mobility management network element for instructing the device that initiates the registration request to access the core network through the connection between the device and the first gateway.

16. The method according to any one of claims 12 to 15, It is characterized in that The first response message is used to indicate whether the terminal device supports the first key architecture, including: The identity information is used to indicate whether the terminal device supports the first key architecture.

17. The method according to any one of claims 12 to 15, It is characterized in that The first response message also includes first indication information; The first response message is used to indicate whether the terminal device supports the first key architecture, including: The first indication information is used to indicate whether the terminal device supports the first key architecture.

18. The method according to any one of claims 12 to 17, It is characterized in that The first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

19. A communication method, It is characterized in that include: The first gateway sends a first request message to the terminal device, where the first request message is used to request identity information of the terminal device, where the terminal device accesses the core network through the connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; The terminal device sends a first response message to the first gateway, where the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports the first key architecture; The first network element obtains a message indicating that the identity authentication is successful and a fifth key, where the fifth key is generated based on whether the terminal device supports the first key architecture; The first gateway sends a message to the terminal device indicating that the identity authentication is successful; The terminal device generates a first key according to whether the terminal device supports the first key architecture, where the first key is used to securely protect a connection between the terminal device and the first gateway; The first gateway generates the first key according to the fifth key.

20. The method according to claim 19, It is characterized in that The method further comprises: The access mobility management network element receives the identity information and indication information indicating whether the terminal device supports the first key architecture from the first gateway; The access mobility management network element generates the fifth key according to whether the terminal device supports the first key architecture; The access mobility management network sends the fifth key to the first gateway.

21. A communication system, It is characterized in that It includes a terminal device and a first gateway, wherein: The first gateway is used to: send a first request message to the terminal device, the first request message is used to request identity information of the terminal device, the terminal device accesses the core network through the connection between the terminal device and the first gateway, and the identity information is used by the core network to authenticate the terminal device; The terminal device is used to: send a first response message to the first gateway, the first response message includes the identity information, and the first response message is used to indicate whether the terminal device supports the first key architecture; The first network element is further used to: obtain a message indicating that the identity authentication is successful and a fifth key, where the fifth key is generated based on whether the terminal device supports the first key architecture; The first gateway is further used to: send a message indicating that the identity authentication is successful to the terminal device; The terminal device is further used to: generate a first key according to whether the terminal device supports the first key architecture, wherein the first key is used to securely protect a connection between the terminal device and the first gateway; The first gateway is further used to generate the first key according to the fifth key.

22. The system according to claim 21, It is characterized in that The system also includes an access mobility management network element, wherein: The access mobility management network element is used to: receive the identity information and indication information used to indicate whether the terminal device supports the first key architecture from the first gateway; The access mobility management network element is further used to: generate the fifth key according to whether the terminal device supports the first key architecture; The access mobility management network element is further used to: send the fifth key to the first gateway.

23. A communication device, It is characterized in that The device comprises means for performing the method according to any one of claims 1 to 11.

24. A communication device, It is characterized in that The device comprises means for performing the method according to any one of claims 12 to 18.

25. A communication device, It is characterized in that include: Memory for storing computer programs; A processor, configured to execute a computer program stored in the memory so that the communication device performs the method of any one of claims 1 to 11; or so that the communication device performs the method of any one of claims 12 to 18.

26. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the method according to any one of claims 1 to 18 is implemented.

27. A computer program product, It is characterized in that The computer program product comprises instructions for executing the steps performed by the storage function network element in the method according to any one of claims 1 to 18.

Citation Information

Cited By

  • Communication method and communication apparatus

    EP4697771A1

  • Communication method and communication apparatus

    WO2024234974A1