Communication method and communication apparatus

By exchanging identity information between the AUN3 device and the 5G-RG to determine key architecture support, the problem of insecure communication was solved, suitable key generation was achieved, and communication security was improved.

WO2024234974A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/090141
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-26
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

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

Method used

By exchanging information between the terminal device and the first gateway, it is determined whether the AUN3 device supports the first key architecture, and a suitable key deduction method is selected to generate a security protection key based on the support status, including sending and receiving identity information to indicate whether the first key architecture is supported or not.

Benefits of technology

It improves the communication security between AUN3 devices and 5G-RG, ensures that the generated keys are suitable for the terminal devices, and enhances the security and efficiency of information transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024090141_21112024_PF_FP_ABST
    Figure CN2024090141_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A communication method, comprising: in the authentication process of a terminal device and a first gateway, the terminal device sends to the first gateway a message indicating whether the terminal device supports a first key architecture, so that the first gateway can accurately determine whether the terminal device supports the first key architecture and reports same to a network side; according to whether the terminal device supports the first key architecture, the terminal device obtains a first key by derivation for security protection; and the network side can also obtain the first key by derivation. The derivation mode of the first key when the terminal device supports the first key architecture is different from the derivation mode of the first key when the terminal device does not support the first key architecture. The terminal device can report whether the terminal device supports the first key architecture, so that the terminal device and the network side select appropriate derivation modes to generate the required keys, thereby improving the communication security.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 12, 2023, with application number 202310539755.8 and invention name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] After an authenticable non-3rd generation partnership project (AUN3) device establishes a connection with a 5G residential gateway (5G-RG), the AUN3 device can access the 5G core network (5GC) through the 5G-RG. To improve communication security, the AUN3 device and the 5G-RG can use keys to securely protect the established connection. 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, secure communication between the AUN3 device and the 5G-RG cannot be achieved.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a communication method to improve the security of communication.

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

[0007] 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 based on 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.

[0008] 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.

[0009] In combination with the first aspect, in certain implementations of the first aspect, generating the first key based on 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; and generating the first key according to a second key deduction method when the terminal device does not support the first key architecture.

[0010] 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.

[0011] In conjunction with the first aspect, in certain implementations of the first aspect, the first response message is used to indicate whether the terminal device supports the first key architecture, and includes the identity information used to indicate whether the terminal device supports the first key architecture. Directly indicating whether the terminal device supports the first key architecture through identity information can improve information transmission efficiency.

[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 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.

[0013] 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.

[0014] 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 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 the second type of the first identifier, the identity information is used to indicate that the terminal device supports the first key architecture.

[0015] 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.

[0016] 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.

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

[0018] 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.

[0019] 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.

[0020] 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.

[0021] Such explicit first indication information helps 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, increasing the flexibility of the solution.

[0022] 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.

[0023] Based on the above scheme, the service network name determined by the terminal device can be a preset fixed value, the home 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.

[0024] 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 further includes: determining a service network name, the service network name being used for the identity authentication, the service network name including 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.

[0025] Based on the above scheme, the service network name determined by the terminal device can be a preset fixed value, the terminal device's home PLMN ID, 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.

[0026] 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.

[0027] 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.

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

[0029] 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 being 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.

[0030] 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.

[0031] 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 above-mentioned first indication information) 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.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the method further 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 device.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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 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 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 based on 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 based on the fifth key.

[0039] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: the 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 sends the fifth key to the first gateway.

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

[0041] 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 the 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, 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 to the terminal device indicating that the identity authentication is successful; the terminal device is also used to: generate a first key based on 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 based on the fifth key.

[0042] 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 for 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 based on 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.

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

[0044] 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.

[0045] 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.

[0046] 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.

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

[0048] 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.

[0049] 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.

[0050] In the fifth aspect, a communication method is provided. The method can be executed by a data management network element, or it can 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 convenience of description, the following is explained using the execution by the data management network element as an example.

[0051] 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 acquisition of an authentication vector required for authentication, and the acquisition request message includes an identifier 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 authentication vector information and the seventh indication information are obtained based on the identifier of the terminal device.

[0052] 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.

[0053] 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 the identifier of the terminal device, and determines the authentication vector corresponding to the authentication method.

[0054] In combination with the fifth aspect, in certain implementations of the fifth aspect, the method further 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.

[0055] 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.

[0056] 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.

[0057] 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 know whether the terminal device supports the NAS protocol according to the eighth indication information, so that the subsequent mobile management network element on the network side can determine whether to execute the NAS SMC process with the terminal device.

[0058] In the sixth aspect, a communication method is provided. The method can be executed by an access mobility management network element, or it can 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 convenience of description, the following is explained using the example of execution by the access mobility management network element.

[0059] The communication method includes: an access mobility management network element receiving an NAS registration request message from a first gateway, the NAS registration request message including third indication information, the third indication information being used to indicate that a device initiating the registration request is an authenticatable non-third generation partnership project terminal device; the access mobility management network element determining, based on the third indication information, that the registration request is initiated by the terminal device; the access mobility management network element sending 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; the access mobility management network element receiving an authentication response message from the authentication network element, the authentication response message including a third key and ninth indication information, the ninth indication information being used to indicate whether the terminal device supports a first key architecture; the access mobility management network element generating a fifth key based on whether the terminal device supports the first key architecture and the third key; and the access mobility management network element sending the fifth key to the first gateway; wherein the fifth key generation methods corresponding to the terminal device supporting the first key architecture and the terminal device not supporting the first key architecture are different.

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

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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; the access mobility management network element executes a NAS SMC process between the terminal device and the NAS key based on the NAS key.

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

[0066] In the seventh aspect, a communication method is provided. The method can be executed by an authentication network element, or it 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 convenience of description, the following is explained using the example of execution by the authentication network element.

[0067] The communication method includes: an authentication network element receiving an authentication request message from an access mobility management network element, the authentication request message being used to request the authentication network element to authenticate an authenticatable non-third generation partnership project terminal device, the authentication request message including an identifier of the terminal device; the authentication network element sending an acquisition request message to a data management network element, the acquisition request message being used to request acquisition of an authentication vector required for authentication, the acquisition request message including the identifier of the terminal device; the authentication network element receiving an acquisition response message from the data management network element, the acquisition response message including information about the authentication vector and seventh indication information, the seventh indication information being used to indicate whether the terminal device supports a first key architecture; the authentication network element generating a third key based on whether the terminal device supports the first key architecture and the identifier of the terminal device; the authentication network element sending an authentication response message to the access mobility management network element, the authentication response message including the third key and ninth indication information, the ninth indication information being used to indicate whether the terminal device supports the first key architecture; wherein the third key generation methods corresponding to the terminal device supporting the first key architecture and the terminal device not supporting the first key architecture are different.

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

[0069] 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.

[0070] 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.

[0071] In combination with the seventh aspect, in some 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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 the transceiver can transmit it. After being output by the processor, the above information may also need to undergo other processing before reaching the transceiver. Similarly, when the processor receives the input above 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 undergo other processing before being input into the processor.

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

[0077] For the operations such as transmission, sending and acquisition / reception involved in the processor, unless otherwise specified, or if they do not 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 the transmission, sending and receiving operations directly performed by the RF circuit and antenna.

[0078] During implementation, the processor may be a processor specifically configured to execute these methods, or may be 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 disposed on separate chips. The embodiments of the present application do not limit the type of memory or the configuration of the memory and the processor.

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

[0080] In a thirteenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the methods provided in the above aspects.

[0081] 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.

[0082] Optionally, as an implementation method, the chip may further include a memory storing instructions, 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 in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] FIG1 is a schematic diagram of a network architecture 100 provided in this application.

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

[0085] FIG3 is a schematic diagram of the registration process of a terminal device through an untrusted non-3GPP according to an embodiment of the present application.

[0086] FIG4 is a schematic diagram of the registration process of a terminal device through a trusted non-3GPP according to an embodiment of the present application.

[0087] FIG5 is a schematic diagram of an AUN3 device that does not support the 5G key architecture accessing a 5GC, as provided in an embodiment of the present application.

[0088] Figure 6 is a schematic diagram of an AUN3 device supporting a 5G key architecture accessing a 5GC according to an embodiment of the present application.

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

[0090] FIG8 is a schematic diagram of the 5G key architecture provided in an embodiment of the present application.

[0091] FIG9 is a schematic flow chart of a communication method provided in this application.

[0092] FIG10 is a schematic flowchart of another communication method provided in the present application.

[0093] FIG11 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.

[0094] FIG12 is a schematic diagram of another communication device 20 provided in an embodiment of the present application.

[0095] FIG13 is a schematic diagram of a chip system 30 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0096] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

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

[0098] In order to facilitate understanding of the communication method provided below, the communication scenario to which the communication method provided in the embodiment of the present application is applicable is first introduced in conjunction with Figure 1.

[0099] Figure 1 is a schematic diagram of the network architecture 100 provided in this application, which includes 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).

[0100] The core network includes but is not limited to the following network functions (or referred to as devices, gateways, network elements, network function network elements or nodes): 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 following is a brief description of the functions of each device.

[0101] 1. AUN3 devices: As shown in Figure 1, 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.

[0102] 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).

[0103] For example, AUN3 devices can be virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0104] 2. 5G-RG: It is both a fixed network device and a terminal device. The 5G-RG is a residential gateway (RG) that can register with the core network. From the core network's perspective, the 5G-RG acts as a terminal device. The 5G-RG communicates with the core network through a communication interface (such as the N1 interface shown in Figure 1).

[0105] Exemplarily, a 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. The 5G-RG can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (e.g., ships); it can also be deployed in the air (e.g., airplanes, balloons, and satellites). The 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, the 5G-RG can also be a handheld device with wireless communication capabilities, a computing device, or other device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle device, or a terminal in the Internet of Things or the Internet of Vehicles, a terminal of any form in a 5G network and future networks, or a terminal in a future evolving 6G network.

[0106] 3. W-AGF: Also known as access gateway function (AGF). A connection exists between the 5G-RG and the W-AGF, which is used to transmit control plane and user plane messages between the AUN3 device and the core network. Control plane messages are also known as non-access stratum (NAS) messages.

[0107] For example, after receiving an 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, thereby processing the downlink user plane message.

[0108] For example, after the 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.

[0109] 4. AMF: Responsible for access control and mobility management of terminal devices (such as the above-mentioned 5G-RG) accessing 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, the 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. If it is determined whether the AUN3 device supports the 5G key architecture, it can generate the correct key based on the corresponding deduction method.

[0110] 5. SMF: Responsible for managing the PDU session of 5G-RG, for example, establishing, maintaining and deleting PDU sessions. Among them, the PDU session is a channel for transmitting PDUs. 5G-RG and the data network transmit PDUs to each other through the 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. In the scenario shown in Figure 1, the PDU session established between 5G-RG and SMF can be used to transmit data of AUN3 devices.

[0111] 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, downlink packet storage, etc.

[0112] 7. UDM: Responsible for storing information such as the subscriber permanent identifier (SUPI) of the subscriber in the operator network, the generic public subscription identifier (GPSI) of the subscriber, and credentials. The SUPI will be encrypted during transmission, and the encrypted SUPI is called a hidden subscriber subscription identifier (SUCI). The information stored in the UDM can be used for authentication and authorization of the terminal device to access the operator network. 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 the permanent identifier, credentials, security context, authentication data (cookie), and token are equivalent to information related to verification / authentication and authorization. In the embodiment of this application, no distinction or restriction is made for the sake of convenience of description.

[0113] 8. AUSF: Usually used for primary authentication, that is, authentication between the terminal device (subscriber) and the operator network. After receiving the authentication request initiated by the subscriber, the AUSF can authenticate and / or authorize the subscriber using the authentication information and / or authorization information stored in the UDM, or generate the subscriber's authentication and / or authorization information through the UDM. The AUSF can feedback the authentication information and / or authorization information to the subscriber.

[0114] 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). Simply put, a network function (NF) can be implemented by hardware or software.

[0115] In Figure 1, N1, N2, N3, N4, and N6 are interface serial numbers. For example, 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 by this application. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0116] For ease of explanation, in the embodiments of this application, network functions (such as AMF, SMF, or UPF) are collectively referred to as NFs. That is, the NFs described later in the embodiments of this application can be replaced with any network function. In addition, Figure 1 only schematically illustrates some network functions, and the NFs described later are not limited to the network functions shown in Figure 1.

[0117] 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.

[0118] It should also be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may adopt other names.

[0119] It should also be understood that the above Figure 1 only exemplifies 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), and examples will not be given one by one here.

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

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

[0122] 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.

[0123] 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.

[0124] Among them, N3IWF can be used to allow terminal devices and 3GPP core networks to interconnect using non-3GPP technologies. N3IWF supports N2 interface communication with mobility management devices and N3 interface communication with user plane devices;

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

[0126] TNGF can be used to support N2 and N3 interfaces, and can implement AMF selection, processing and SMF (relayed by AMF) N2 signaling to support sessions and QoS, transparently relay PDUs between terminal devices and user plane devices, and other functions.

[0127] 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.

[0128] 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 the RAN in the 3GPP access network and can support N2 and N3 interfaces.

[0129] For ease of understanding, the following describes the untrusted non-3GPP access process and the trusted non-3GPP process respectively in conjunction with (a) and (b) in FIG2 .

[0130] Figure 2 (a) shows an untrusted non-3GPP access architecture. Terminal devices can access untrusted non-3GPP devices through a communication interface (e.g., the Y1 interface shown in Figure 2 (a)). Untrusted non-3GPP devices access the gateway N3IWF through a communication interface (e.g., the Y2 interface shown in Figure 2 (a)). The N3IWF is connected to the AMF through a communication interface (e.g., the N2 interface shown in Figure 2 (a)).

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

[0132] 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 3GPP access technology and non-3GPP access technology at the same time; the terminal device can also access the AMF only through 3GPP access technology, or only through non-3GPP access technology.

[0133] 5. Registration process of the terminal device through the untrusted non-3GPP: As shown in Figure 3, the registration process of the terminal device through the untrusted non-3GPP includes the following steps:

[0134] S310: The UE is connected to an untrusted non-3GPP access network.

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

[0136] S320, UE selects N3IWF.

[0137] Specifically, the UE selects an N3IWF and obtains the address information of the N3IWF.

[0138] S330, the UE triggers the establishment of an Internet Protocol Security (IPsec) security association (IPsec SA) with the N3IWF.

[0139] 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.

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

[0141] 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.

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

[0143] Response message #1 includes an EAP-Request / 5G-Start packet. This EAP-Request / 5G-Start packet notifies the UE to initiate an EAP-5G session. For example, response message #1 notifies the UE to begin sending NAS messages (which are encapsulated in EAP-5G packets).

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

[0145] S360, the UE sends a request message #2 to the N3IWF.

[0146] The request message #2 includes an EAP-Response / 5G-NAS packet, which includes access network (AN) parameters and a Non-Access Stratum-Protocol Data Unit (NAS-PDU). The NAS-PDU carries the registration request message. The AN parameters include parameter information used by the N3IWF to select the AMF, such as the Globally Unique AMF Identifier (GUAMI), the selected Public Land Mobile Network (PLMN) identifier (or PLMN ID and NID), etc.

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

[0148] 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.

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

[0150] S370, N3IWF performs AMF selection.

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

[0152] 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, the method flow shown in Figure 3 also includes:

[0153] S381: The AMF sends a request message #3 to the UE via the N3IWF. This request message #3 is used to request the UE's SUCI.

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

[0155] S382: The UE sends a response message #3 to the AMF via the N3IWF. The response message #3 carries the UE's SUCI.

[0156] Optionally, response message #3 is called a 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. The N3IWF then sends the NAS Identity Response to the AMF via the N2 communication interface. The data packet sent by the UE to the N3IWF can be called an IKE_AUTH response message.

[0157] As another possible implementation, when the Registration Request message carries the SUCI or the AMF successfully verifies the integrity protection of the Registration Request message, or when the AMF obtains the SUCI through response message #3, the AMF may initiate a process to authenticate the UE. In this implementation, the method flow shown in FIG3 further includes:

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

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

[0160] 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 in step 7 in section 7.2.1 of the current 3GPP standard TS33.501.

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

[0162] After authentication is complete, the AUSF sends the SEAF key to the AMF, for example, an AAA Key response message that carries the EAF key.

[0163] 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.

[0164] S395: The AMF sends a NAS Security Mode Command to the UE via the 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.

[0165] S396, UE sends NAS Security Mode Complete to AMF through N3IWF.

[0166] 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.

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

[0168] 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.

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

[0170] S398, N3IWF sends EAP-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 exchange.

[0171] As another possible implementation, if the 5G-GUTI is carried in the Registration Request message and the AMF successfully verifies the integrity protection of the Registration Request message, the AMF may decide not to initiate authentication. In this case, steps S381 and S382 and S391 to S398 may not be performed.

[0172] Furthermore, the UE and the N3IWF establish an IPSec SA using the previously acquired N3IWF key. The method flow shown in FIG3 further includes:

[0173] S301: UE and N3IWF establish an IPSec SA using the N3IWF key.

[0174] This IPSec SA is called the signaling IPSec SA. After the signaling IPSec SA is established, the N3IWF notifies the AMF through the 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 the 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 the NAS_IP_ADDRESS. For the downlink NAS message sent by the AMF to the UE, the source address is the NAS_IP_ADDRESS, and the destination address is the "inner" IP address of the UE.

[0175] S302: The AMF sends an N2 message to the N3IWF. The N2 message includes a NAS Registration Accept message to the UE. Subsequently, when the AMF registers with the UDM, it must provide the UDM with an Access Type of Non-3GPP access.

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

[0177] 6. Registration process of the terminal device through the trusted non-3GPP: As shown in Figure 4, the registration process of the terminal device through the trusted non-3GPP includes the following steps:

[0178] 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).

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

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

[0181] S430: The UE sends a Network Access Identifier (NAI) to the TNAP.

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

[0183] 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.

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

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

[0186] S450: The TNGF initiates an EAP-5G session. Specifically, the 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, to start sending NAS messages (by encapsulating the NAS messages in EAP-5G packets).

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

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

[0189] S470, TNGF performs AMF selection.

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

[0191] 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, the method flow shown in Figure 4 also includes:

[0192] S481: The AMF sends a request message #5 to the UE via the N3IWF. This request message #5 is used to request the UE's SUCI.

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

[0194] S482: The UE sends a response message #5 to the AMF via the N3IWF. The response message #5 carries the UE's SUCI.

[0195] Optionally, response message #5 is called a 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. The N3IWF then sends the NAS Identity Response to the AMF via the N2 communication interface. The data packet sent by the UE to the N3IWF can be called an IKE_AUTH response message.

[0196] As another possible implementation, when the Registration Request message carries the 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, the method flow shown in FIG4 further includes:

[0197] S491, AMF selects AUSF.

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

[0199] 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 art.

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

[0201] After authentication is complete, AUSF sends the SEAF key to AMF, which AMF uses to derive the NAS security key and the TNGF security key.

[0202] S495: The AMF sends a NAS Security Mode Command to the UE via the 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.

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

[0204] 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 AMF.

[0205] S497: AMF sends a request message #6 to TNGF, including the TNGF key.

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

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

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

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

[0210] S499: TNGF sends an AAA message to TNAP.

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

[0212] S401, TNAP sends EAP-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 exchange.

[0213] As another possible implementation, if the 5G-GUTI is carried in the Registration Request message and the integrity protection of the Registration Request message is successfully verified, the AMF may decide not to initiate authentication. In this case, steps S481 and S482 and S491 to S401 may not be performed.

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

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

[0216] 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 it is not encrypted).

[0217] 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 signaling 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 signaling IPSec SA. Among them, for the uplink NAS message sent by the UE to the AMF, the source address is the UE's "inner" IP address 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 UE's "inner" IP address.

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

[0219] S406: AMF sends an N2 message to TNGF.

[0220] The N2 message includes a NAS Registration Accept message to the UE. Subsequently, when the AMF registers with the UDM, it must provide the UDM with an Access Type of Non-3GPP access. The TNGF sends a NAS Registration Request to the UE via the newly established signaling IPSec SA.

[0221] 7. Accessing 5GC for AUN3 devices that do not support the 5G key architecture: As shown in Figure 5, accessing 5GC for AUN3 devices that do not support the 5G key architecture includes the following steps:

[0222] S510: The AUN3 device attempts to establish an L2 connection with the RG through Ethernet or WiFi.

[0223] S520, RG sends an EAP request / identity to AUN3. The EAP request / identity is used to start the EAP authentication process.

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

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

[0226] 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.

[0227] Optionally, if the RG is an 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.

[0228] 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 to the AMF, including the SUCI and AUN3 device indication.

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

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

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

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

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

[0234] S580: The UDM selects an authentication method. Specifically, the UDM calls the SIDF to decrypt the SUCI to obtain the SUPI, and selects an authentication method based on the SUPI.

[0235] S590, the UDM sends a get response message (Nudm_UEAuthentication_Get response) to the 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'.

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

[0237] If the EAP authentication between the AUSF and the AUN3 device is successfully completed, the method flow shown in FIG5 further includes:

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

[0239] 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.

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

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

[0242] 8. Accessing the 5GC with an AUN3 device supporting the 5G key architecture: As shown in Figure 6, accessing the 5GC with an AUN3 device supporting the 5G key architecture includes the following steps:

[0243] S610: The AUN3 device establishes a WLAN connection with an access point (AP) of a WLAN access network (AN) (e.g., the RG shown in FIG6 ). Optionally, the AUN3 device establishes a WLAN connection with the RG based on a WLAN connection establishment procedure specified in a current protocol (e.g., IEEE 802.11). The specific WLAN connection establishment process is not limited in this embodiment.

[0244] S620: RG sends an EAP request / identity to AUN3. The EAP request / identity is used to start the EAP authentication process.

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

[0246] S630: The AUN3 device sends an EAP response / identity to the RG.

[0247] 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.

[0248] Optionally, if the RG is an 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 it is registering on behalf of the AUN3 device, where the interface between the AUN3 device and the RG needs to be protected. The W-AGF selects the AMF / SEAF and 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 applicable), and the new indication. The same message content is forwarded from the AMF to the AUSF, and then from the AUSF to the UDM.

[0249] 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.

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

[0251] S641, AMF / SEAF selects AUSF.

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

[0253] S643, AUSF sends a get request message to UDM.

[0254] S644, UDM selects an authentication method.

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

[0256] For steps S641 to S645 , reference may be made to the description of steps S550 to S590 in FIG5 , which will not be repeated here.

[0257] 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 TS 33.501[4]).

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

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

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

[0261] S690: RG and AUN3 derive a WLAN key. Specifically, RG and AUN3 derive a WLAN key from a PMK.

[0262] 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 WLAN AN.

[0263] 9. Non-5G key architecture: For the process of AUN3 device accessing 5GC in Figure 5 above, the key architecture on the UE and network side is shown in Figure 7.

[0264] As shown in Figure 7, the long-term key is stored on the AUN3 device and the UDM. The presence of the CK and IK on both the UDM and the AUSF indicates that they were passed from the UDM to the AUSF. The MSK is generated by the AUSF and passed to the WAGF via the AMF. The WAGF then generates the PMK based on the MSK and passes it to the AP, which then generates the AP key. The UE then follows this process to generate the same key. At this point, the AP corresponds to the 5G-RG mentioned in the previous process.

[0265] 10. 5G Key Architecture: For the AUN3 device accessing the 5GC process in Figure 6 above, the key architecture on the UE and network side is shown in Figure 8.

[0266] As shown in Figure 8, long-term keys are stored on the AUN3 device and the UDM. The presence of CK and IK on both the UDM and the AUSF indicates that the key was passed from the UDM to the AUSF. Kausf or Kseaf is generated by the AUSF and passed to the AMF. The AMF then generates Kamf based on the Kausf or Kseaf and passes it to the WAGF. The WAGF then generates the PMK based on the Kamf and passes it to the AP. The AP then generates the AP key. The UE then follows this process to generate the same key. At this point, the AP corresponds to the 5G-RG mentioned in the previous process.

[0267] In addition, in order to facilitate understanding of the embodiments of the present application, the following explanations are made.

[0268] First, in the embodiments of the present application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and does not necessarily mean that the indication information includes A.

[0269] The information indicated by the indication information is referred to as the information to be indicated. During 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. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be predefined, for example, according to a protocol, or can be configured by the transmitting device through sending configuration information to the receiving device.

[0270] Second, "at least one" shown in the embodiments of the present application refers to one or more, and "more than one" refers to two or more. In addition, in the embodiments 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 embodiments 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 embodiments of the present application. It should be understood that the objects described in this way can be interchangeable under appropriate circumstances so as to be able to describe solutions other than the embodiments of the present application. In addition, in the embodiments of the present application, words such as "910", "920" are only identifications made for the convenience of description, and are not used to limit the order of execution steps.

[0271] Third, in the embodiments of this 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 this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0272] Fourth, the term "storage" used in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately while partially integrated into a decoder, a processor, or a communication device. The memory may be any type of storage medium and is not limited in this application.

[0273] 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, which is not limited in this application.

[0274] 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.

[0275] Seventh, in the embodiments of this application, the various terms and English abbreviations are provided for convenience of description and should not constitute any limitation on this application. This application does not exclude the possibility of defining other terms in existing or future protocols that can achieve the same or similar functions.

[0276] Eighth, the term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0277] The above text briefly introduces the scenarios in which the communication method provided in the embodiment of the present application can be applied in conjunction with Figure 1, as well as the basic concepts that may be involved in the embodiment of the present application, and introduces 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 in the basic concepts. According to the description of the process of AUN3 devices accessing 5GC in Figures 5 and 6 above, AMF and AUSF distinguish whether the AUN3 device supports or does not support the 5G key architecture mainly by an identifier, that is, the encryption indication involved in the process of AUN3 devices accessing 5GC shown in Figure 6 above. In the case of an encryption indication, AMF and AUSF generate relevant keys based on the 5G key architecture. In the case of no encryption indication, relevant keys are generated based on the non-5G key architecture. Specifically, the encryption indication is added by 5G-RG when sending a NAS registration request message to AMF.

[0278] The problem 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.

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

[0280] 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.

[0281] FIG9 is a schematic flow chart of a communication method provided by the present application, which includes the following steps:

[0282] S911: The first gateway registers with the core network.

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

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

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

[0286] 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 that supports non-3GPP communication (such as supporting WiFi communication).

[0287] Specifically, after the AUN3 device establishes a connection with the 5G-RG, it can access the core network through the connection. The AUN3 device can initiate a registration process with 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 the 5G-RG then forwards the registration request to the core network, thereby initiating the registration process between the AUN3 device and the 5G-RG.

[0288] The method flow shown in FIG9 further includes:

[0289] S921, the 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.

[0290] Specifically, the first request message is used to request identity information from the AUN3 device. This identity information is used by the core network to authenticate the AUN3 device. For example, the first request message is used to initiate the authentication process. In this case, the first request message may be an EAP-Request / Identity message. It should be understood that the first request message may also be other messages capable of requesting identity information from the AUN3 device. The embodiments of this application are not limited to the specific message type of the first request message; it only needs to be able to implement the corresponding functionality. For ease of description, the following description uses the EAP-Request / Identity message as an example.

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

[0292] 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.

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

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

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

[0296] Specifically, the AUN3 device and the network derive the keys required for security protection based on whether the AUN3 device supports the first key architecture. If the AUN3 device supports the first key architecture, the AUN3 device and the network derive the keys required for security protection using the first key derivation method. If the AUN3 device does not support the first key protection method, the AUN3 device and the network use the second key derivation method to derive the keys required for security protection. The first key derivation method can be understood as the AUN3 device and the network performing key derivation according to the first key architecture, and the second key derivation method can be understood as the AUN3 device and the network performing key derivation according to the second key architecture. The second key architecture is a key generation method that is 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.

[0297] Exemplarily, the first key architecture can be the 5G key architecture introduced in the basic concepts above (as shown in Figure 8), or it can be a key architecture defined by future 3GPP standards. This embodiment is illustrated by taking the 5G key architecture introduced in the basic concepts as an example. If the AUN3 device supports the 5G key architecture, the process of deducing the key 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 key required for security protection based on PMK. The key derivation process on the AUN3 device side is as follows: the AUN3 device derives CK and IK based on the locally stored long-term key, then generates Kausf based on CK and IK, generates Kseaf based on Kausf, then generates Kamf based on Kseaf, then generates Kwagf based on Kamf, then generates PMK based on Kwagf, and finally generates the key required for security protection based on PMK.

[0298] Alternatively, if the AUN3 device does not support the 5G key architecture, the network-side key derivation process can be as follows: AUSF generates MSK based on CK and IK, and passes the MSK to WAGF through AMF. WAGF generates PMK based on MSK and passes PMK to 5G-RG. 5G-RG generates the key required for security protection based on PMK. The AUN3 device-side key derivation process is as follows: The 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 key required for security protection based on PMK.

[0299] 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.

[0300] 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 an appropriate key deduction method to generate a key to improve the security of communication.

[0301] 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:

[0302] 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 as follows: 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 the EAP response message including, in addition to the AUN3 identity, a new information element (IE) that carries 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).

[0303] 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 AUN3 identity in the EAP response message. In this case, the AUN3 identity itself serves as an indicator. For example, the first response message is EAP-Response / Identity(AUN3 ID).

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

[0305] It should be understood that this embodiment does not limit how to send information indicating whether the AUN3 device supports the first key architecture to the 5G-RG. Existing messages or existing IEs can be reused to transmit the first indication information. Alternatively, new signaling or a new IE can be added 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.

[0306] As an example and not a limitation, the process of the 5G-RG sending the first request message to the AUN3 device in step S921 and the AUN3 device sending the 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 initiating 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 implementation methods (such as the following implementation methods A, B, and C):

[0307] Implementation method A: If non-trusted non-3GPP technology is used to access the AUN3 device and the 5G-RG in this embodiment, the relevant description of the above-mentioned first request message can refer to the description of response message #1 in the registration process described in Figure 3, and the relevant description of the first response message can refer to the description of request message #2 in the registration process described in Figure 3, which will not be repeated here.

[0308] In the case of Implementation A, the AUN3 device and the 5G-RG transmit IKE_AUTH Request and IKE_AUTH Response messages to notify the AUN3 device to initiate an EAP-5G session. After receiving the EAP-Request / 5G-Start packet, the AUN3 device sends an EAP Response message. The specific process can be referred to the description of steps S330 to S360 in the registration process shown in Figure 3 above. The AUN3 device is considered to be the UE in Figure 3, and the 5G-RG is considered to be the N3IWF in Figure 3. The details are not repeated here.

[0309] Implementation method B: If trusted non-3GPP technology is used to access the AUN3 device and the 5G-RG in this embodiment, the relevant description of the first request message involved can refer to the description of the EAP-Req / Identity message in the registration process described in Figure 4, and the relevant description of the first response message can refer to the description of the EAP response data packet / 5G-NAS data packet in the registration process described in Figure 4, which will not be repeated here.

[0310] In the case shown in implementation method B, the AUN3 device and the 5G-RG notify the AUN3 device to initiate an EAP-5G session by transmitting EAP-Req / Identity messages, EAP-Res / Identity messages, and EAP Request / 5G-Start data packets. For the specific process, please refer to the description of steps S420 to S460 in the registration process shown in Figure 4 above. The AUN3 device is regarded as the UE in Figure 4, and the 5G-RG is regarded as the TNAP and TNGF in Figure 4. No further details are given here.

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

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

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

[0314] In the three implementations described above, combined with the delivery 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, and 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 indicating whether the AUN3 device supports the first key architecture can be carried within the EAP-Response / 5G-NAS message or outside the EAP-Response / 5G-NAS message. When the information indicating whether the AUN3 device supports the first key architecture can be carried within the EAP-Response / 5G-NAS message, its AN parameter portion can carry information indicating whether the AUN3 device supports the first key architecture. Specifically, a new IE is added to the AN parameter to carry information indicating whether the AUN3 device supports the first key architecture, or the UE ID portion of the AN parameter has the 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.

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

[0316] 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 conditions or predefined access methods. The predefined access method can be understood as an access process agreed in advance; the judgment conditions include but are not limited to determining whether they belong to the same user (or owner) and whether the user has made a selection.

[0317] 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;

[0318] 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;

[0319] If the predefined access method is to preferentially access through the process corresponding to implementation method A, the AUN3 device determines to first attempt to access the first gateway through the process corresponding to the untrusted non-3GPP access technology;

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

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

[0322] 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 no examples will be given here one by one.

[0323] 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 the implementation, or configuration, or its own capabilities, or the capabilities of the 5G-RG, and determines whether 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.

[0324] 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:

[0325] 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.

[0326] 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.

[0327] 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, if the AUN3 device does not support the first key architecture, the AUN3 device sends the information indicating whether the AUN3 device supports the first key architecture to the 5G-RG; if the AUN3 device supports the first key architecture, the AUN3 device may not send the information indicating whether the AUN3 device supports the first key architecture to the 5G-RG.

[0328] 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.

[0329] For example, 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:

[0330] Method #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.

[0331] 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.

[0332] 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.

[0333] Accordingly, the 5G-RG can distinguish whether the received information is SUPI or SUCI based on the specific format of the AUN3 device identity information. For example, assume 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.

[0334] As another possible implementation, 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,

[0335] 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.

[0336] 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 the IMSI format and the SUCI in the 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. 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.

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

[0338] For example, the identity information may be a field carried in the username or realm portion of the AUN3 device. The identity information may be at least one bit of information in the username or realm portion, such as information that carries information such as the AUN3 or 5GK. If the username or realm portion of the SUPI or SUCI carries identity information, it indicates support for the first key architecture; if it does not carry identity information, it indicates support for the first key architecture. Alternatively, if it does not carry identity information, it indicates support for the first key architecture; if it carries identity information, it indicates non-support for the first key architecture; or if it carries a first value, it indicates support for the first key architecture, while if it carries a second value, it indicates non-support for the first key architecture.

[0339] For another example, assuming that the SUPI of the AUN3 device is 00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org, then if the AUN3 device supports the first key hierarchy, 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).

[0340] Alternatively, the SUPI with the field can be 00-00-5E-00-53-00@5G key.5gc.mnc012.mcc345.3gppnetwork.org. In this case, the first response message is EAP-Identity / Response(00-00-5E-00-53-00@5G key hierarchy.5gc.mnc012.mcc345.3gppnetwork.org). If the AUN3 device does not support the first key hierarchy, 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).

[0341] For example, if the SUPI of the AUN3 device is Network Specific Identifier user17@example.com, the corresponding SUCI is type1.rid678.schid1.hnkey27.ecckey<ECC ephemeral public 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 public key> .cip<encryption of user17> .mac<MAC tag value> @AUN3-5GK.example.com, type1.rid678.schid1.hnkey27.eckey<ECC ephemeral public key> .cip<encryption of user17> .mac<MAC tag value> @AUN3-N5GK.example.com. In this case, when the field is AUN3 or AUN3-5GK, it indicates support for the 5G key architecture. When the field is not carried or is AUN3-N5GK, it indicates support for the 5G key architecture.

[0342] Method #2: The first response message also includes first indication information, which 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.

[0343] 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 will not be described in detail here.

[0344] 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, "5G key 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 indicates 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 indicates 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 indicates that the first key architecture is not supported, and the default key architecture can be used according to the pre-configuration).

[0345] 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 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 can represent different key architectures. For example, 00 represents support for the first key architecture, and 01 represents support for non-first key architecture.

[0346] For another example, the first indication information may be a NAS-PDU. If the first response message carries a 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 a 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 described above 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). The fact that the AUN3 device supports the 5G NAS protocol indicates that the AUN3 device is capable of generating and processing 5G NAS messages (e.g., registration request messages, NAS SMC messages, PDU session establishment request messages, etc.).

[0347] 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 will be collectively referred to as the first indication information below. However, it should be noted that the form of the first indication information below includes the above-mentioned identity information.

[0348] Optionally, the first response message may include second indication information, where the second indication information is used to indicate whether the AUN3 device supports the non-access stratum (NAS) protocol. Similar to the first indication information described above, the second indication information may take the form of: a specific format of AUN3 device identity information, a special format SUPI, a special format SUCI, a character string, bit information, or a NAS-PDU, which is not further described here. It should be noted that only one of the first and second indication information may be sent.

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

[0350] 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.

[0351] In this embodiment, after receiving the first response message, the 5G-RG may determine that the AUN3 device that sent the first response message requests to initiate a registration process. Then, the 5G-RG initiates the registration process on behalf of the AUN3 device. The method shown in FIG9 further includes:

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

[0353] 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's network. It may be an AMF or other network element capable of implementing the functions of an AMF. For ease of description, the following description uses the AMF as an example.

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

[0355] In one possible implementation, when the 5G-RG sends the NAS Registration Request message to the W-AGF, it also sends to the W-AGF information indicating whether the AUN3 device supports the first key architecture. For details, see the 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.

[0356] 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.

[0357] In this implementation, the 5G-RG simply forwards the NAS registration request message carried in the first response message to the AMF.

[0358] As another possible implementation, 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.

[0359] 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.

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

[0361] 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.

[0362] In a possible implementation, 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.

[0363] In another possible implementation, when the AUN3 device supports the first key architecture, the NAS registration request message carries the fourth indication information. In this case, the NAS registration request message carrying the fourth indication information indicates that the AUN3 device supports the first key architecture, and the NAS registration request message not carrying the fourth indication information indicates that the AUN3 device does not support the first key architecture.

[0364] In another possible implementation, if the AUN3 device does not support the first key architecture, the NAS registration request message carries the fourth indication information. In this case, the NAS registration request message carrying the fourth indication information indicates that the AUN3 device does not support the first key architecture, and the NAS registration request message not carrying the fourth indication information indicates that the AUN3 device supports the first key architecture.

[0365] 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.

[0366] 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 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 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. In this case, 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. For example, the 5G-RG directly carries the received first indication information in the NAS registration request message and forwards it to the AMF.

[0367] Optionally, the first indication information and the fourth indication information are information with the same meaning but different formats. 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 bit indication information.

[0368] It should be understood that regardless of whether the first indication information and the fourth indication information are in the same form, the meaning expressed is the same. Therefore, the fourth indication information will not be described again. The description of the fourth indication information can refer to the description of the first indication information above.

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

[0370] When the NAS registration request message carries the fifth indication information indicating that the AUN3 device supports the 5G NAS protocol, the fourth indication information may not be carried. In this case, the AMF can determine whether the AUN3 device supports the first key architecture based on whether the AUN3 device supports the 5G NAS protocol.

[0371] Exemplarily, the third and fourth indication information described 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 portion, the first indication information may function as both the third and fourth indication information. Specifically, when the first indication information is "AUN3-5GK" or "AUN3-N5GK," the first indication information indicates an AUN3 device that supports the 5G key architecture, or an AUN3 device that does not support the 5G key architecture. For another example, if the 5G-RG determines that the AUN3 device supports the 5G key architecture, the 5G-RG uses the indication information "AUN3-5GK" to indicate both an AUN3 device and a device that supports the 5G key architecture. If the 5G-RG determines that the AUN3 device does not support the 5G key architecture, the 5G-RG uses the indication information "AUN3-N5GK" to indicate both an AUN3 device and a device that does not support the 5G key architecture. Therefore, a single indication information may simultaneously include the functions of the third and fourth indication information. The indication information can be added by the 5G-RG or from the AUN3 device. It should be noted that if the indication information from the AUN3 device already carries the functions of the third and fourth indication information, then the AMF may not add additional indication information, or may redundantly add the third and fourth indication information according to other needs.

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

[0373] S940: The AMF determines whether the AUN3 device supports the first key architecture.

[0374] 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.

[0375] 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.

[0376] In this implementation, the AMF can determine through the fifth indication information that the AUN3 device supports the 5G NAS protocol and can exchange NAS messages with the AUN3 device. 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. The AMF can regard the AUN3 device as an ordinary terminal device (that is, 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 5G NAS key.

[0377] 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.

[0378] In another implementation, the AMF determines whether the AUN3 device supports the first key architecture and the method of using the key based on 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 it does not support the 5G NAS protocol. The AMF generates a 5G NAS 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 determines different NAS message processing methods. 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, the 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.

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

[0380] Furthermore, the AMF sends an authentication request message to the authentication network element so that the authentication network element authenticates the AUN3 device. The method flow shown in FIG9 further includes:

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

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

[0383] The authentication request message is used to request the AUSF to authenticate the AUN3 device. The authentication request message includes the identifier and SN name of the AUN3 device. The identifier of the AUN3 device can be the AUN3 device SUCI or SUPI, and the value of the SN name includes but is not limited to: a preset fixed value (e.g., 5G: AUN3, which can 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).

[0384] 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 step S930 above, 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 that of 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.

[0385] Optionally, the authentication request message also includes an eleventh indication information, which 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 can be directly the first indication information, or directly the fourth indication information.

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

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

[0388] In another possible implementation, if the AUN3 device does not support the first key architecture, the authentication request message carries the eleventh indication information. In this case, the eleventh indication information carried in the authentication request message indicates that the AUN3 device does not support the first key architecture, and the absence of the eleventh indication information in the authentication request message indicates that the AUN3 device supports the first key architecture.

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

[0390] 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. The method flow shown in FIG9 also includes:

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

[0392] 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 functions of a UDM. For ease of description, the following description takes the data management network element as an example of a UDM.

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

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

[0395] 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.

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

[0397] 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.

[0398] S970: UDM generates an authentication vector.

[0399] For example, upon receiving the SUCI of the AUN3 device, the UDM obtains the SUPI of the AUN3 device through the SUCI of the AUN3 device. Furthermore, the UDM determines the authentication method through the SUPI of the AUN3 device or the AUN3 device information.

[0400] 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, the UDM may determine that it is an AUN3 device according to the AUN3 sixth indication information, and then determine the authentication method.

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

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

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

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

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

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

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

[0408] In this embodiment, there is no limitation on the process of two-way authentication between the AUN3 device and the AUSF. For example, 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 art.

[0409] 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 may generate the SN name after receiving the authentication vector or 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.

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

[0411] Specifically, if AUSF has made a judgment after receiving the step S950 message, it does not need to make a judgment again; 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 sake of convenience of description, the following is an example of AUSF determining the key generation method based on the eleventh indication information.

[0412] In one 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 key generation method. 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.

[0413] In one possible implementation, when the above-mentioned authentication request message indicates whether the AUN3 device supports the 5G key architecture through the eleventh indication information, 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, the fourth key (denoted as MSK) is generated.

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

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

[0416] S993, AMF determines the second key.

[0417] As a possible implementation method, if the AMF has made a judgment in step S940, the AMF determines the method for generating the second key based on the judgment result of S940, and then generates the second key; if the AMF has not made a judgment in step S940, the 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 for obtaining the second key, and further generates the second key if the second key needs to be generated.

[0418] In this implementation, the first key architecture is described as a 5G key architecture. When the AUN3 device supports the 5G key architecture, the AMF uses the third key to generate the second key.

[0419] 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 2 32 The value of -1, or the SQN in the authentication vector, etc. The second parameter is, for example, a string "AUN3", for example, a distinguishing identifier 0x02. This embodiment does not limit the use of more input parameters in the DKF function.

[0420] 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 is, for example, the string "AUN3" or the distinguishing identifier 0x02. This embodiment does not limit the use of more input parameters in the DKF function.

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

[0422] If the AUN3 device does not support the 5G key architecture, the AMF does not generate a new key after receiving the fourth key and determines the fourth key as the second key. Alternatively, the AMF uses the fourth key to generate the NAS encryption key and the NAS integrity protection key.

[0423] 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 may 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. The method shown in Figure 9 may also include:

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

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

[0426] If the AMF determines that the AUN3 device supports the NAS protocol, the AMF sends a NAS SMC message to the AUN3 device. The NAS SMC message is protected using a non-null integrity protection algorithm and a NAS integrity protection key. After receiving the NAS SMC message, the AUN3 device verifies the integrity protection of the NAS SMC message using the same NAS key and non-null integrity protection algorithm. If verification is successful, the AUN3 device responds 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 is protected using a NAS integrity protection key and a NAS encryption key.

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

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

[0429] 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.

[0430] 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 through a NAS message or an N2 message. For example, the AMF sends the fifth key through a NAS downlink transport message or an N2 initial context setup request message.

[0431] In another possible implementation, AMF sends the second key to W-AGF, and W-AGF determines the 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. In the case of determining that the AUN3 device does not support the first key architecture, the second key is directly sent to 5G-RG as the fifth key; in the case of determining 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 the second response message.

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

[0433] 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 four-way handshake to establish a secure connection.

[0434] Before establishing a secure connection, the AUN3 device generates Key #1 based on the fifth key. This Key #1 generates the first key required for security protection. The first key is used to protect the secure connection established between the 5G-RG and the AUN3. For example, the first key encrypts and integrity-protects the connection between the AUN3 device and the 5G-RG. For example, the sender encrypts and integrity-protects messages using the first key, and the receiver decrypts and integrity-checks messages using the first key. If the AUN3 device supports the first key architecture (using the 5G key architecture as an example), the AUN3 device generates Key #1 using the fifth key. Specifically, Key #1 is the PMK, the fifth key is Kwagf, and the first key is a key generated further from the PMK.

[0435] In a possible implementation, the AUN3 device and the 5G-RG respectively use the fifth key to directly generate the key #1. For example, if the key #1 is K 5G-RG , then 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," such as 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 based on key #1.

[0436] In another implementation, the AUN3 device and the 5G-RG can each 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, if the second key is Kwagf, PMK is generated based on Kwagf.

[0437] 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.

[0438] Optionally, in one possible implementation, after the 5G-RG establishes a secure connection with the AUN3 device, the 5G-RG replies to the AMF to notify 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 UL transport message or an N2 initial context setup ack message.

[0439] 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.

[0440] In the embodiment shown in FIG9 , the 5G-RG can determine whether the AUN3 device supports the first key architecture based on the information sent by the AUN3 device, and the AMF can determine whether the AUN3 device supports the first key architecture based on the information reported by the 5G-RG. The present application also provides a communication method, in which the AMF and AUSF can determine whether the AUN3 device supports the first key architecture based on the information received from the UDM. The communication method is described in detail below with reference to FIG10 .

[0441] FIG10 is a schematic flow chart of a communication method provided by the present application, which includes the following steps:

[0442] S1011, 5G-RG is registered with 5GC.

[0443] Please refer to the description of step S911 in FIG9 , which will not be repeated here.

[0444] S1010: The AUN3 device establishes a connection with the first gateway.

[0445] Please refer to the description of step S910 in FIG9 , which will not be repeated here.

[0446] S1021, the 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.

[0447] Please refer to the description of step S921 in FIG9 , which will not be repeated here.

[0448] 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.

[0449] The description of the first response message may refer to the description of the first response message in step S920 in Figure 9. The difference is that in this embodiment, the first response message may not indicate whether the AUN3 device supports the first key architecture, which will not be repeated here.

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

[0451] For a description of the NAS Registration Request message, refer to the description of the NAS Registration Request message in step S930 in Figure 9 . The difference is that the NAS Registration Request message in this embodiment may not carry the fourth indication information, which is not further described here. For ease of distinction, the NAS Registration Request message in this embodiment is referred to as NAS Registration Request Message #1.

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

[0453] For a description of the authentication request message, refer to the description of the authentication request message in step S950 in Figure 9. In this embodiment, the authentication request message may not carry the eleventh indication information and will not be described in detail here. For ease of distinction, the NAS registration request message in this embodiment is referred to as authentication request message #1.

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

[0455] Please refer to the description of step S960 in FIG9 , which will not be repeated here.

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

[0457] Specifically, the way in which UDM determines the authentication vector can refer to the description of how to determine the authentication vector in step S970 of Figure 9, which 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.

[0458] As a possible implementation method, UDM can obtain the SUPI of the AUN3 device in step S1060, then determine the subscription data based on the SUPI of the AUN3 device, and then determine whether the AUN3 device supports the first key architecture and / or whether it supports 5G NAS based on 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.

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

[0460] As another possible implementation, the UDM may obtain the SUPI of the AUN3 device in step 1060. The 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), the UDM obtains the SUPI, which is equivalent to obtaining information about whether the AUN3 device supports the first key architecture and / or whether it supports 5G NAS. In this case, the AUN3-5GC is sent to the AUSF as part of the SUPI. Therefore, the seventh indication information can be regarded as the SUPI itself, or the AUN3-5GC field in the SUPI.

[0461] It should be understood that the above-mentioned several implementation methods are only examples of how the 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 this application. The 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. No further details will be given here.

[0462] Furthermore, 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. The method flow shown in FIG10 further includes:

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

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

[0465] Exemplarily, possible forms of the seventh indication information include, but are not limited to: a special format SUPI, a special format SUCI, string information, and at least one bit of information. For a specific description, reference may be made to the description of the first indication information in the communication method shown in FIG. 9 , which will not be repeated here.

[0466] Optionally, when the UDM receives the SUCI, it obtains the SUPI of the AUN3 device carried in the response message #1. 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 that indicates whether the first key architecture is supported.

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

[0468] S1080, the AUN3 device and AUSF perform bidirectional authentication.

[0469] Please refer to the description of step S990 in FIG9 , which will not be repeated here.

[0470] 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.

[0471] The method flow shown in FIG10 further includes:

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

[0473] Refer to the description of step S991 in Figure 9 and will not be repeated here. It should be noted that, if 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 in step S1010. If the seventh indication information is optional, 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 in step S1010 appears.

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

[0475] For ease 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.

[0476] 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.

[0477] 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.

[0478] It should be understood that regardless of whether the ninth indication information and the seventh indication information are in the same form, the meaning expressed is the same. Therefore, the ninth indication information will not be described again. The description of the ninth indication information can refer to the description of the seventh indication information above.

[0479] Exemplarily, the authentication response message #1 also includes 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 based on the eighth indication information, the AUSF learns whether the AUN3 device supports the NAS protocol, and thus can carry the tenth indication information in the authentication response message #1. The tenth indication information and the eighth indication information have the same meaning and may be in the same or different form.

[0480] S1092: AMF determines whether the AUN3 device supports the first key architecture.

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

[0482] The specific determination method can be found in the description of step S940 in Figure 9 and will not be repeated here. It should be noted that, if the ninth indication message must be sent, the AMF determines whether the AUN3 device supports the first key architecture and determines the key generation method based on the ninth indication message in step S1010. If the ninth indication message is optional, the AMF determines whether the AUN3 device supports the first key architecture and determines the key generation method based on whether the ninth indication message in step S1010 is present.

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

[0484] 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 may further generate a NAS key and initiate a NAS SMC process between the AUN3 device and the AUN3 device based on the NAS key.

[0485] The method flow shown in FIG10 may further include:

[0486] S1094: The NAS SMC process is performed between the AMF and the AUN3 device.

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

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

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

[0490] 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.

[0491] The method flow shown in FIG10 further includes:

[0492] S1093, AMF determines the second key.

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

[0494] Please refer to the description of step S995 in FIG9 , which will not be repeated here.

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

[0496] Please refer to the description of step S996 in FIG9 , which will not be repeated here.

[0497] In the embodiment shown in Figure 10, AMF and AUSF can determine whether the AUN3 device supports 5G NAS or supports the first key architecture based on the indication information of UDM, so that subsequent core network 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 keys to improve the security of communications.

[0498] It should be understood that the size of the serial numbers of the above processes 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 embodiments of the present application.

[0499] 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.

[0500] It should also be understood that in some of the above embodiments, exemplary descriptions are mainly given using devices in existing network architectures as examples (e.g., AUN3 devices, 5G-RG, AMF, AUSF, and UDM, etc.). It should be understood that the embodiments of the present application do not limit the specific form of the devices. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0501] 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 devices (such as chips or circuits).

[0502] The communication method provided by the embodiments of the present application is described in detail above in conjunction with Figures 9 and 10. The above communication method is mainly introduced from the perspective of the interaction between the various protocol layers of the terminal device. It is understandable that in order to implement the above functions, the terminal device includes the corresponding hardware structure and / or software modules for performing each function.

[0503] 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.

[0504] The communication device provided in this application is described in detail below with reference to Figures 11 to 13. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, please refer to the method embodiment above. For the sake of brevity, some contents will not be repeated.

[0505] In the embodiment of the present application, the functional modules of the transmitting device or the receiving device can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules 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 according to each function.

[0506] Figure 11 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 process data. In other words, the transceiver module 11 is used to perform operations related to receiving and sending, while the processing module 12 is used to perform operations other than receiving and sending. The transceiver module 11 can also be referred to as a communication interface or a communication unit.

[0507] 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.

[0508] 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.

[0509] The apparatus 10 can implement the steps or processes corresponding to those performed by the AUN3 device in the above method embodiment, wherein the transceiver module 11 can be used to perform the transceiver-related operations of the AUN3 device in the above method embodiment, and the processing module 12 can be used to perform the processing-related operations of the AUN3 device in the above method embodiment.

[0510] 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 based on 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.

[0511] When the device 10 is used to execute the method in Figure 9, 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.

[0512] When the device 10 is used to execute the method in Figure 10, 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.

[0513] 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.

[0514] 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.

[0515] The device 10 can implement steps or processes corresponding to those performed 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.

[0516] In one possible implementation, the transceiver module 11 is used to send a first request message to the terminal device, where 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 transceiver module 11 is used to receive a first response message from the terminal device, 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 transceiver module 11 is used to send the identity information and the indication information indicating whether the terminal device supports the first key architecture to an access mobile management network element, where 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, where the first key is used to secure the connection between the terminal device and the first gateway.

[0517] In which, when the device 10 is used to execute the method in Figure 9, 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.

[0518] When the device 10 is used to execute the method in Figure 10, 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.

[0519] 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.

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

[0521] 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 perform 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 perform the processing-related operations of the access mobility management network element in the above method embodiment.

[0522] 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.

[0523] In which, when the device 10 is used to execute the method in Figure 9, 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.

[0524] When the device 10 is used to execute the method in Figure 10, 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.

[0525] 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.

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

[0527] The device 10 can implement the steps or processes corresponding to those executed by the data management network element in the above method embodiment, wherein the transceiver module 11 can be used to perform 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 perform operations related to the processing of the data management network element in the above method embodiment.

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

[0529] When the device 10 is used to execute the method in FIG. 9 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S960 and S980 ; the processing module 12 may be used to execute the processing steps in the method, such as step S970 .

[0530] When the device 10 is used to execute the method in Figure 10, 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.

[0531] 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.

[0532] 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).

[0533] The device 10 can implement the steps or processes corresponding to those 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.

[0534] In a possible implementation, the transceiver module 11 is configured to receive an authentication request message from an access mobility management network element, the authentication request message being used to request the authentication network element to authenticate an authenticatable non-third generation partnership project AUN3 device, the authentication request message including an identifier of the AUN3 device; the transceiver module 11 is configured to send an acquisition request message to a data management network element, the acquisition request message being used to request acquisition of an authentication vector required for authentication, the acquisition request message including an identifier of the AUN3 device; the transceiver module 11 is configured to receive an acquisition response message from the data management network element, the acquisition response message including an identifier of the authentication vector. information and seventh indication information, the seventh indication information being used to indicate whether the AUN3 device supports the first key architecture; a processing module 12 being used to generate a third key according to whether the AUN3 device supports the first key architecture and an identifier of the AUN3 device; the transceiver module 11 being used to send an authentication response message to the access mobility management network element, the authentication response message including the third key and ninth indication information, the ninth indication information being 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.

[0535] In which, when the device 10 is used to execute the method in Figure 9, 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.

[0536] When the device 10 is used to execute the method in Figure 10, 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.

[0537] 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.

[0538] 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, those skilled in the art will understand that the device 10 may be specifically the 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 the 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 described here.

[0539] 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 the processing module, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.

[0540] 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.

[0541] Figure 12 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, which is configured to execute computer programs or instructions stored in a memory 22, or read data / signaling stored in the memory 22, to perform the methods described in the above method embodiments. Optionally, there are one or more processors 21.

[0542] Optionally, as shown in FIG12 , the device 20 further includes a memory 22 for storing computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21 or may be separately provided. Optionally, there may be one or more memories 22 .

[0543] Optionally, as shown in Figure 12, the device 20 further includes a transceiver 23, which is used to receive and / or send signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

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

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

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

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

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

[0549] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be 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. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0550] 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).

[0551] 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.

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

[0553] 13 is a 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.

[0554] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may 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.

[0555] 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 various method embodiments.

[0556] 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.

[0557] 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.

[0558] 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.

[0559] 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.

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

[0561] 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.

[0562] In the several embodiments provided in this 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. In actual implementation, there may be other division methods, 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.

[0563] 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 device. 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 one website, computer, server or data center to another website, 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. 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 includes 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 code, 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.

[0564] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.< / mcc> < / mnc> < / mcc> < / mnc>

Claims

1. A communication method, characterized in that: include: The authentication network element receives an authentication request message from an access mobility management network element, wherein the authentication request message is used to request the authentication network element to authenticate the terminal device; The authentication network element sends an acquisition request message to the data management network element, where the acquisition request message includes an identifier of the terminal device, and the acquisition request message is used to request acquisition of an authentication vector required for the authentication; The authentication network element receives an acquisition response message from the data management network element, where the acquisition response message includes the authentication vector; The authentication network element performs the authentication on the terminal device according to the authentication vector; The authentication network element sends an authentication response message to the access mobility management network element, where the authentication response message indicates that the authentication is successful and includes a key; In a case where the terminal device does not support the first key architecture, the key is an MSK key, the acquisition response message further includes seventh indication information for indicating that the terminal device does not support the first key architecture, and the method further includes: In response to the seventh indication information, the authentication network element generates the MSK key according to a non-first key architecture.

2. The method according to claim 1, characterized in that When the terminal device does not support the first key architecture, the authentication network element does not generate a Kausf key.

3. The method according to claim 1 or 2, characterized in that: In the case where the terminal device supports the first key architecture, the key is a Kseaf key, and the method further includes: The authentication network element generates the Kseaf key according to the first key architecture.

4. The method according to claim 3, characterized in that In a case where the terminal device supports the first key architecture, the acquisition response message further includes information used to indicate that the terminal device supports the first key architecture, and the authentication network element generates the Kseaf key according to the first key architecture, including: In response to the information indicating that the terminal device supports the first key architecture, the authentication network element generates the Kseaf key according to the first key architecture.

5. The method according to claim 3 or 4, characterized in that: The authentication network element generates the Kseaf key according to the first key architecture, including: The authentication network element generates a Kausf key, and generates the Kseaf key according to the Kausf key.

6. A communication method, characterized in that: include: The data management network element receives an acquisition request message from the authentication network element, the acquisition request message includes an identifier of the terminal device, and the acquisition request message is used to request to acquire an authentication vector required for authenticating the terminal device; The data management network element sends an acquisition response message to the authentication network element, where the acquisition response message includes the authentication vector; Wherein, in a case where the terminal device does not support the first key architecture, the acquisition response message further includes seventh indication information for indicating that the terminal device does not support the first key architecture.

7. The method according to claim 6, characterized in that The subscription data of the terminal device includes indication information for indicating whether the terminal device supports the first key architecture; In the case where the terminal device does not support the first key architecture, the acquisition response message further includes seventh indication information used to indicate that the terminal device does not support the first key architecture, including: In a case where the indication information is used to indicate that the terminal device does not support the first key architecture, the acquisition response message further includes seventh indication information used to indicate that the terminal device does not support the first key architecture.

8. The method according to claim 6 or 7, characterized in that: In the case where the terminal device supports the first key architecture, the acquisition response message also includes information for indicating that the terminal device supports the first key architecture, or the acquisition response message does not include information for indicating whether the terminal device supports the first key architecture.

9. The method according to claim 8, characterized in that The subscription data of the terminal device includes indication information for indicating whether the terminal device supports the first key architecture; In the case where the terminal device supports the first key architecture, the acquisition response message further includes information used to indicate that the terminal device supports the first key architecture, or the acquisition response message does not include information used to indicate whether the terminal device supports the first key architecture, including: In the case where the indication information is used to indicate that the terminal device supports the first key architecture, the acquisition response message also includes the information used to indicate that the terminal device supports the first key architecture, or the acquisition response message does not include the information used to indicate whether the terminal device supports the first key architecture.

10. A communication method, characterized in that: include: The access mobility management network element sends an authentication request message to the authentication network element, wherein the authentication request message is used to request the authentication network element to authenticate the terminal device; The access mobility management network element receives an authentication response message from the authentication network element, wherein the authentication response message indicates that the authentication is successful and includes a key; In the case that the terminal device does not support the first key architecture, the key is an MSK key, the access mobility management network element sends the MSK key to the first network element, and the MSK key is used to establish a secure connection between the terminal device and the first network element.

11. The method according to claim 10, characterized in that When the terminal device does not support the first key architecture, the access mobility management network element does not generate a Kamf key.

12. The method according to claim 10 or 11, characterized in that: In the case where the terminal device supports the first key architecture, the key is a Kseaf key, and the method further includes: The access mobility management network element generates a second key based on the Kseaf key, and sends the second key to the first network element, where the second key is used to establish a secure connection between the terminal device and the first network element.

13. The method according to claim 12, characterized in that The authentication response message also includes a user permanent identifier of the terminal device, and the access mobility management network element generates a second key according to the Kseaf key, including: The access mobility management network element generates a Kamf key according to the Kseaf key and the user permanent identifier, and generates the second key according to the Kamf key.

14. A communication method, characterized in that: include: The access mobility management network element sends an authentication request message to the authentication network element, wherein the authentication request message is used to request the authentication network element to authenticate the terminal device; The authentication network element receives the authentication request message from the access mobility management network element; The authentication network element sends an acquisition request message to the data management network element, where the acquisition request message includes an identifier of the terminal device, and the acquisition request message is used to request acquisition of an authentication vector required for the authentication; The data management network element receives the acquisition request message from the authentication network element; The data management network element sends an acquisition response message to the authentication network element, where the acquisition response message includes the authentication vector; The authentication network element receives the acquisition response message from the data management network element, and performs the authentication on the terminal device according to the authentication vector; The authentication network element sends an authentication response message to the access mobility management network element, where the authentication response message indicates that the authentication is successful and includes a key; The access mobility management network element receives the authentication response message from the authentication network element; Wherein, in the case where the terminal device does not support the first key architecture, the key is an MSK key, the acquisition response message further includes seventh indication information for indicating that the terminal device does not support the first key architecture, and the method further includes: In response to the seventh indication information, the authentication network element generates the MSK key according to the non-first key architecture; The access mobility management network element sends the MSK key to the first network element, and the MSK key is used to establish a secure connection between the terminal device and the first network element.

15. The method according to claim 14, characterized in that The subscription data of the terminal device includes indication information for indicating whether the terminal device supports the first key architecture; In the case where the terminal device does not support the first key architecture, the acquisition response message further includes seventh indication information used to indicate that the terminal device does not support the first key architecture, including: In a case where the indication information is used to indicate that the terminal device does not support the first key architecture, the acquisition response message further includes seventh indication information used to indicate that the terminal device does not support the first key architecture.

16. The method according to claim 14 or 15, characterized in that When the terminal device does not support the first key architecture, the authentication network element does not generate a Kausf key, and the access mobility management network element does not generate a Kamf key.

17. The method according to any one of claims 14 to 16, characterized in that: In the case where the terminal device supports the first key architecture, the key is a Kseaf key, and the method further includes: The authentication network element generates the Kseaf key according to the first key architecture; The access mobility management network element generates a second key based on the Kseaf key, and sends the second key to the first network element, where the second key is used to establish a secure connection between the terminal device and the first network element.

18. The method according to claim 17, characterized in that The authentication network element generates the Kseaf key according to the first key architecture, including: The authentication network element generates a Kausf key, and generates the Kseaf key according to the Kausf key.

19. The method according to claim 17 or 18, characterized in that The authentication response message also includes a user permanent identifier of the terminal device, and the access mobility management network element generates a second key according to the Kseaf key, including: The access mobility management network element generates a Kamf key according to the Kseaf key and the user permanent identifier, and generates the second key according to the Kamf key.

20. The method according to any one of claims 14 to 19, characterized in that: In the case where the terminal device supports the first key architecture, the acquisition response message also includes information for indicating that the terminal device supports the first key architecture, or the acquisition response message does not include information for indicating whether the terminal device supports the first key architecture.

21. The method according to claim 20, characterized in that The subscription data of the terminal device includes indication information for indicating whether the terminal device supports the first key architecture; In the case where the terminal device supports the first key architecture, the acquisition response message further includes information used to indicate that the terminal device supports the first key architecture, or the acquisition response message does not include information used to indicate whether the terminal device supports the first key architecture, including: In the case where the indication information is used to indicate that the terminal device supports the first key architecture, the acquisition response message also includes the information used to indicate that the terminal device supports the first key architecture, or the acquisition response message does not include the information used to indicate whether the terminal device supports the first key architecture.

22. The method according to claim 20 or 21, characterized in that In a case where the acquisition response message further includes information indicating that the terminal device supports the first key architecture, the authentication network element generates the Kseaf key according to the first key architecture, including: In response to the information indicating that the terminal device supports the first key architecture, the authentication network element generates the Kseaf key according to the first key architecture.

23. The method according to any one of claims 12 or 13 or 17-19, characterized in that: The second key is a Kwagf key.

24. The method according to any one of claims 1 to 23, characterized in that The first key architecture is the fifth-generation 5G key architecture.

25. The method according to any one of claims 1 to 24, characterized in that The terminal device is an authenticatable non-3rd Generation Partnership Project AUN3 device.

26. The method according to any one of claims 1 to 25, characterized in that The first gateway is the fifth-generation residential gateway 5G-RG.

27. A communication system, characterized in that: It includes authentication network element, data management network element and access mobility management network element, among which: The authentication network element is used to execute the method according to any one of claims 1 to 5; The data management network element is used to execute the method according to any one of claims 6 to 9; The access mobility management network element is used to execute the method as described in any one of claims 10-13.

28. A communication method, 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.

29. The method according to claim 28, 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.

30. The method according to claim 28 or 29, 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.

31. The method according to claim 30, 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.

32. The method according to claim 30, 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.

33. The method according to claim 30, 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.

34. The method according to claim 28 or 29, 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.

35. The method according to claim 34, 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.

36. The method according to any one of claims 28 to 35, 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 PLMN ID of the home public land mobile communication network of the terminal device, or a PLMN ID of an access mobility management network element serving the first gateway.

37. The method according to any one of claims 28 to 36, 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.

38. The method according to any one of claims 28 to 37, characterized in that The first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

39. A communication method, 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.

40. The method according to claim 39, 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.

41. The method according to claim 39 or 40, 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.

42. The method according to claim 41, 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.

43. The method according to any one of claims 39 to 42, 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.

44. The method according to any one of claims 39 to 42, 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.

45. The method according to any one of claims 39 to 44, characterized in that The first gateway includes a fifth-generation residential gateway 5G-RG, and the first key architecture includes a 5G key architecture.

46. ​​A communication method, 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.

47. The method according to claim 46, characterized in that The method further comprises: The access mobility management network element receives 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 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.

48. A communication system, 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.

49. The system according to claim 48, 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.

50. A communication device, characterized in that: The apparatus comprises means for performing the method of any one of claims 1 to 13 or any one of claims 28 to 45.

51. A communication device, 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 13 or any one of claims 28 to 45.

52. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions. When the computer instructions are executed on a computer, the computer executes the method according to any one of claims 1 to 13 or any one of claims 28 to 45.

53. A computer program product, characterized in that The computer program product comprises computer instructions, which, when executed on a computer, are used to execute the steps performed by the storage function network element in the method according to any one of claims 1 to 13 or any one of claims 28 to 45.

Citation Information

Patent Citations

  • Communication method and communication device

    CN118945649A

  • Key derivation for non-3GPP access

    CN113545002A

  • Communication method and related device

    CN115915121A

  • Non-3GPP device access to core network

    US20210258787A1