Communication method and communication apparatus
By utilizing a flexible differentiation mechanism of identifiers and authentication vectors in non-Generation 3 Partners networks, the incompatibility of security authentication between core networks of different communication technologies has been resolved, thereby improving both security and efficiency.
Patent Information
- Application Number
- PCT/CN2026/091279
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-17
- Publication Date
- 2026-11-12
AI Technical Summary
When non-3GPP networks access the core network, the security authentication mechanisms between core networks using different communication technologies are incompatible, leading to confusion in security policies, increased resource requirements, and higher operating costs.
By working together with gateway devices and authentication network elements, and utilizing a flexible differentiation mechanism of identifiers and authentication vectors, the type of core network that the terminal device requests to access can be identified, and an appropriate authentication mechanism can be selected according to the type, thus avoiding confusion of security authentication mechanisms and waste of resources.
It improves the authentication security and efficiency of terminal devices accessing the core network, reduces resource consumption, and enhances the resource utilization of network connections.
Smart Images

Figure CN2026091279_12112026_PF_FP_ABST
Abstract
Description
Communication methods and communication devices
[0001] This application claims priority to Chinese Patent Application No. 202510602288.8, filed on May 9, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology
[0003] When a terminal device accesses the core network through a non-3GPP network, the security authentication mechanisms used by core networks employing different communication technologies may differ. For example, the security authentication mechanisms used by 4G and 5G technologies are different. In a non-3GPP network architecture compatible with different communication technologies, network devices, unable to ascertain the communication technology (or core network type) used by the core network the terminal device is requesting access from, may select an incorrect security authentication mechanism. This can lead to security policy confusion, resulting in terminal authentication failure and inability to access the network.
[0004] In addition, when different non-3GPP technologies access the core network, the gateways used are not fully compatible, and separate access gateways are often required for different technologies. There are also incompatibility issues between these technologies when accessing different communication technologies, which leads to increased resource requirements and higher operating costs for network connections. Summary of the Invention
[0005] This application provides a communication method and a communication device that can improve the authentication security of different core network types and increase the efficiency of terminal devices accessing the core network in scenarios where access is made through a non-3GPP network.
[0006] In a first aspect, a communication method is provided, which is executed by a gateway device. The gateway device may be an evolved packet data gateway (ePDG), or it may be a component (such as a chip, chip system or circuit) for the gateway device, or it may be a logic module or software that can implement some or all of the functions of the gateway device, etc. This application does not limit it in this way.
[0007] The method may include: receiving first request information from a terminal device, the first request information being used to indicate that the terminal device requests access to the core network through a non-3GPP network, the first request information including a first identifier, the first identifier being associated with the type of core network that the terminal device requests to access;
[0008] Send a second request message to the first authentication network element, wherein the second request message is used to request the first authentication network element to authenticate the terminal device, the first authentication network element is the authentication network element associated with the first identifier among at least two authentication network elements, the at least two authentication network elements correspond one-to-one with at least two core network types, and / or, the second request message includes the second identifier, and the first authentication network element is used for authentication processing of at least two types of core networks, the at least two types include the type associated with the first identifier, and the second identifier is used to indicate the core network type associated with the first identifier.
[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first identifier is defined in the format of network access identifiers (NAIs). Specifically, taking a terminal device requesting access to the 4G core network and the 5G core network as an example, the first identifier has two possible implementations:
[0010] In the first implementation, the first identifier is used to indicate the communication technology requested for access, or the network type. This first identifier is a new type of subscription permanent identifier (SUPI), for example, it can be denoted as new type Y (networkTypeY), where Y represents any integer from 4 to 7.
[0011] The format of the first identifier can be represented as:
[0012] “ <networktypey> <username>@wlan.mnc <mnc>.mcc <mcc>.3gppnetwork.org”
[0013] in, <networktypey>This is a placeholder used to indicate the network type corresponding to this information; <username>It serves as a user identification identifier, used to distinguish different terminal devices or users; <mnc>This is another placeholder used to replace the actual mobile network code in the actual transmission; <mcc>This is another placeholder used to identify the country or region where the terminal device is located; 3gppnetwork.org is the domain name suffix.
[0014] In addition, "@wlan.mnc" indicates the network type. For example, when requesting access to the 4G core network, it can be written as "@epc.mnc", and when requesting access to the 5G core network, it can be written as "@5gc.mnc".
[0015] The second implementation uses NAI information as the first identifier, meaning it doesn't introduce a new SUPI type but instead introduces network type indication information. The first identifier can be represented as follows:
[0016] " <networktype0> <username>@5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org”
[0017] In this context, "@5gc.mnc" indicates that the network type requested for access is the 5G core network.
[0018] It should be understood that the above implementation method takes the terminal device requesting access to the 4G and 5G core networks as an example. This application is not limited to this, and may also include the 5G core network and future communication technologies.
[0019] According to the above scheme, the terminal device carries the network type information requested for access in the request information, so that the network elements related to authentication can obtain the network type information, which is conducive to improving the efficiency of terminal device access to the network and enhancing the security of the authentication mechanism.
[0020] In conjunction with the first aspect, in some implementations of the first aspect, the authentication network element has the following two possible implementations:
[0021] In the first implementation, the authentication network element is used for authentication processing of at least two types of core networks. The at least two types include the type associated with the first identifier and the second identifier is used to indicate the core network type associated with the first identifier.
[0022] For example, an authentication network element may include two interfaces, one for 4G and the other for 5G core network access. When a terminal device requests access to the core network, it selects the corresponding interface type to transmit authentication-related information. As another example, an authentication network element may include one interface for either 4G or 5G core network access. When the core network type requested by the terminal device does not match the type supported by this interface, a new interface associated with the core network type requested by the terminal device is created to receive the authentication-related information from that terminal device.
[0023] In the second implementation, the authentication network element includes at least two authentication network elements, which correspond one-to-one with at least two core network types. The first authentication network element associated with the first identifier receives the second request information sent by the gateway device.
[0024] For example, an authentication network element may include at least two authentication network elements, each used for access to different types of networks. When a terminal device requests access to the core network, it selects the corresponding type of authentication network element for authentication. As another example, an authentication network element may originally include one authentication network element used for 4G and 5G core network authentication. When the type of core network the terminal device requests to access does not match the type associated with that authentication network element, a new authentication network element is created associated with the type of core network the terminal device is requesting to access, used to receive authentication-related information from the terminal device.
[0025] It should be understood that the above number of interfaces is only an example and not a limitation. For example, the authentication network element may also include multiple peer interfaces or service interfaces corresponding to multiple network types, or the authentication network element may also construct multiple peer interfaces or service interfaces corresponding to multiple network types.
[0026] According to the above scheme, the authentication network element can adjust its working mode according to different scenarios and network requirements, so as to flexibly distinguish between 4G and 5G core network access and information reception, avoid confusion in the selection of security authentication mechanisms, and improve the security of non-3GPP network access.
[0027] In conjunction with the first aspect, in some implementations of the first aspect, the first request information may further include authentication information of the terminal device, which is used in the authentication process of the terminal device. Similarly, the second request information may also include authentication information of the terminal device.
[0028] For example, when a terminal device requests access to a 4G core network, the first request information may also include the access network identifier and / or network type. When a terminal device requests access to a 5G core network, the first request information may also include the serving network and / or network type.
[0029] Optionally, the authentication information may be included in the first identifier. For example, if the terminal device requests access to the 4G core network, the first identifier includes the access network identifier and / or network type; or if the terminal device requests access to the 5G core network, the first identifier includes the serving network and / or network type. If the first identifier includes authentication information, the first request information does not need to indicate authentication-related information. After receiving the request information, the network device can obtain the authentication information by parsing the first identifier.
[0030] According to the above scheme, resource consumption can be reduced and signal transmission efficiency can be improved during information transmission.
[0031] In conjunction with the first aspect, in some implementations of the first aspect, when the terminal device requests access to the 4G core network, the first identifier is in an unencrypted format; or, when the terminal device requests access to the 5G core network, the first identifier is in an encrypted format.
[0032] In conjunction with the first aspect, in some implementations of the first aspect, when the terminal device requests access to the 4G core network, the second identifier is in an unencrypted format; or, when the terminal device requests access to the 5G core network, the second identifier is in an encrypted format.
[0033] It should be understood that the above implementation method takes the terminal device requesting access to the 4G and 5G core networks as an example, and this application is not limited to this. According to the above scheme, network devices can distinguish the type of core network requested by the terminal device by whether or not encryption is used, thereby reducing resource consumption and improving resource utilization.
[0034] Optionally, the second identifier in the second request information and the first identifier in the first request information can be the same, or the second identifier and the first identifier can be different. For example, the gateway device saves the received first identifier and sends it as the second identifier to the authentication network element, in which case the second identifier is the same as the first identifier; another example is that the gateway device parses the received first identifier and sends the parsed information as the second identifier to the authentication network element, in which case the second identifier is different from the first identifier; yet another example is that when the authentication network element includes at least two authentication network elements, each authentication network element is used for authentication processing of a type of core network, in which case the gateway device sends the second request information to the data management network element of the corresponding core network type, and the second identifier does not need to include specific core network type information, in which case the second identifier is different from the first identifier.
[0035] Secondly, a communication method is provided, which can be executed by an authentication network element. The gateway device can be an authentication, authorization, and accounting server (AAA server), or an authentication server function (AUSF) network element, or an AUSF server, or it can be a component (such as a chip, chip system, or circuit) used for the authentication network element, or it can be a logic module or software that can implement some or all of the functions of the authentication network element, etc. This application does not limit it in this regard.
[0036] The method may include: receiving second request information from a gateway device, wherein the second request information is used to request authentication of a terminal device, the terminal device accessing the core network through a non-3GPP network, the authentication network element being used for authentication processing of at least two types of core networks, the second request information including a second identifier, the second identifier being used to indicate the type of core network that the terminal device requests to access, and the at least two types including the type associated with the second identifier; and authenticating the terminal device based on the second request information.
[0037] In conjunction with the second aspect, in some implementations of the second aspect, the method may further include: sending a third request message to a first data management network element, the third request message being used to request the first data management network element to authenticate the terminal device, the third request message including a third identifier, the third identifier being used to indicate the type of core network the terminal device requests to access, the first data management network element being a data management network element associated with a second identifier among at least two data management network elements, the at least two data management network elements corresponding one-to-one with at least two core network types, and / or, the first data management network element being used for the authentication process of at least two types of core networks, the third identifier being used to indicate the core network type associated with the second identifier; and receiving an authentication vector sent by the first data management network element, the authentication vector being used to authenticate the terminal device.
[0038] In conjunction with the second aspect, in some implementations of the second aspect, the data management network element has the following two possible scenarios:
[0039] In the first scenario, the data management network element is used for the authentication process of at least two types of core networks, including the type associated with the third identifier, which is used to indicate the core network type associated with the second identifier.
[0040] For example, a data management network element may include two interfaces, one for 4G and the other for 5G core network access. When a terminal device requests access to the core network, it selects the corresponding interface type to transmit data management-related information. As another example, a data management network element may include one interface for either 4G or 5G core network access. When the core network type requested by the terminal device does not match the type supported by this interface, a new interface associated with the core network type requested by the terminal device is created to receive authentication-related information from the terminal device.
[0041] In the second scenario, the data management network element includes at least two data management network elements, which correspond one-to-one with at least two core network types. The first data management network element associated with the third identifier receives the third request information sent by the gateway device.
[0042] For example, a data management network element may include two data management network elements, one for 4G and the other for 5G core network access. When a terminal device requests access to the core network, it selects the corresponding type of data management network element for the terminal device authentication process. As another example, a data management network element may originally include one data management network element used for 4G and 5G core network authentication. When the type of core network the terminal device requests to access does not match the type associated with that data management network element, a new data management network element is created associated with the core network type requested by the terminal device to receive authentication-related information from the terminal device.
[0043] It should be understood that the above scenario is only an example of a terminal device requesting access to the 4G and 5G core networks. This application is not limited to this, and the number of interfaces mentioned above is only an example and not a limitation.
[0044] According to the above scheme, the data management network element can adjust its working mode according to different scenarios and network requirements, realize flexible differentiation of information reception between 4G and 5G core networks, avoid confusion during authentication vector generation, and improve the security of non-3GPP network access.
[0045] In conjunction with the second aspect, in some implementations of the second aspect, in addition to the aforementioned identification information, the second request information may also include the authentication information of the terminal device. For example, when the terminal device requests access to the 4G core network, the second request information may also include the access network identifier and / or network type; similarly, when the terminal device requests access to the 5G core network, the second request information may also include and / or network type. The setting method for the third request information is similar to that of the second request information and will not be elaborated here.
[0046] In conjunction with the second aspect, in some implementations of the second aspect, the aforementioned authentication information may be included in the second identifier. For example, when a terminal device requests access to the 4G core network, the second identifier includes the access network identifier and / or network type; or, when a terminal device requests access to the 5G core network, the second identifier includes the serving network and / or network type. The third identifier is set in a similar manner to the second identifier and will not be described in detail here.
[0047] In conjunction with the second aspect, in some implementations of the second aspect, the second identifier can also be implicitly indicated. Specifically, when the terminal device requests access to the 4G core network, the second identifier is in an unencrypted format; or, when the terminal device requests access to the 5G core network, the second identifier is in an encrypted format. The setting method of the third identifier is similar to that of the second identifier and will not be elaborated here.
[0048] Thirdly, a communication method is provided, which can be executed by a terminal device, or it can be a component for a terminal device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem core, etc.), or it can be a logic module or software that can realize some or all of the functions of the terminal device, etc., and this application does not limit it in this regard.
[0049] The method may include: sending a first request message to a gateway device, the first request message being used to instruct a terminal device to request access to the core network through a non-3GPP network, the first request message including a first identifier, the first identifier being associated with the type of core network to which the terminal device requests access.
[0050] In conjunction with the third aspect, in some implementations of the third aspect, the first request information may further include authentication information of the terminal device, which is used in the terminal device's authentication process. For example, when the terminal device requests access to the 4G core network, the first request information may further include the access network identifier and / or network type. When the terminal device requests access to the 5G core network, the first request information may further include the serving network and / or network type.
[0051] Optionally, the authentication information may be included in the first identifier. For example, if the terminal device requests access to the 4G core network, the first identifier includes the access network identifier and / or network type; or if the terminal device requests access to the 5G core network, the first identifier includes the serving network and / or network type. If the first identifier includes authentication information, the first request information does not need to indicate authentication-related information. After receiving the request information, the network device obtains the authentication information by parsing the first identifier.
[0052] In conjunction with the third aspect, in some implementations of the third aspect, when a terminal device requests access to the 4G core network, the first identifier is in an unencrypted format; or, when a terminal device requests access to the 5G core network, the first identifier is in an encrypted format.
[0053] Fourthly, a communication method is provided, which can be executed by a data management network element. The gateway device can be a unified data management (UDM) network element, or a component (such as a chip, chip system, or circuit) for a data management network element, or a logic module or software that can implement some or all of the functions of the data management network element, etc. This application does not limit this.
[0054] The method may include: receiving third request information sent by an authentication network element, the third request information being used for the authentication process of a terminal device, the terminal device accessing the core network through a non-3GPP network, the data management network element being used for the authentication process of at least two types of core networks, the third request information including a third identifier, the third identifier being used to indicate the type of core network that the terminal device requests to access, and at least two types including the type associated with the third identifier; generating an authentication vector based on the third request information, the authentication vector being used to authenticate the terminal device; and sending the authentication vector to the authentication network element.
[0055] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the third request information may further include authentication information of the terminal device, which is used in the terminal device's authentication process. For example, when the terminal device requests access to the 4G core network, the third request information may further include the access network identifier and / or network type. When the terminal device requests access to the 5G core network, the third request information may further include the serving network and / or network type.
[0056] Optionally, the authentication information may be included in the third identifier. For example, if the terminal device requests access to the 4G core network, the third identifier may include the access network identifier and / or network type; or if the terminal device requests access to the 5G core network, the third identifier may include the serving network and / or network type. If the third identifier includes authentication information, the third request information does not need to indicate authentication-related information. After receiving the request information, the network device obtains the authentication information by parsing the third identifier.
[0057] In conjunction with the fourth aspect, in some implementations of the fourth aspect, when the terminal device requests access to the 4G core network, the third identifier is in an unencrypted format; or, when the terminal device requests access to the 5G core network, the third identifier is in an encrypted format.
[0058] Fifthly, a communication apparatus is provided for performing the method in any of the possible implementations of the first to fourth aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any of the possible implementations of the first to fourth aspects, such as processing units and / or communication units.
[0059] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.
[0060] In another implementation, the device is a chip, chip system, or circuit for communication equipment (such as terminal equipment or network equipment). When the device is a chip, chip system, or circuit for communication equipment, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.
[0061] A sixth aspect provides a communication device comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any of the possible implementations of the first to fourth aspects. Optionally, the device further comprises a memory for storing the computer program or instructions; correspondingly, the at least one processor is configured to execute the computer program or instructions in the memory. Optionally, the device further comprises a communication interface coupled to the processor, which can be used to input information to the processor or output information from the processor. Optionally, the processor reads the computer program or instructions from the memory through the communication interface.
[0062] In one implementation, the device is a communication device (such as a terminal device or a network device).
[0063] In another implementation, the device is a chip, chip system, or circuit for communication equipment (such as terminal equipment or network equipment).
[0064] In a seventh aspect, a processor is provided for performing the methods provided in the first to fourth aspects described above.
[0065] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.
[0066] Eighthly, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a communication device, cause the communication device to perform the method of any one of the possible implementations of the first to fourth aspects described above.
[0067] A ninth aspect provides a computer program product comprising a computer program or instructions for performing the methods of any of the possible implementations of the first to fourth aspects. In other words, when the computer program product is run on a computer, it causes the computer to perform the methods of any of the possible implementations of the first to fourth aspects.
[0068] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, wherein the processor reads instructions from a memory through the communication interface and executes the method provided by any of the above-described implementations of any of the first to fourth aspects.
[0069] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to perform the method provided by any of the above implementations of any of the first to fourth aspects. Attached Figure Description
[0070] Figure 1 is a schematic diagram of a network architecture 100 provided in an embodiment of this application.
[0071] Figure 2 is a schematic diagram of the untrusted non-3GPP system architecture 200 provided in this application.
[0072] Figure 3 is a schematic diagram of the trusted non-3GPP system architecture 300 provided in this application.
[0073] Figure 4 is a schematic diagram of a communication method 400 provided in an embodiment of this application.
[0074] Figure 5 is a schematic diagram of another communication method 500 provided in an embodiment of this application.
[0075] Figure 6 is a schematic diagram of another communication method 600 provided in an embodiment of this application.
[0076] Figure 7 is a schematic block diagram of a communication device 700 provided in an embodiment of this application.
[0077] Figure 8 is a schematic diagram of another communication device 800 provided in an embodiment of this application.
[0078] Figure 9 is a schematic diagram of another communication device 900 provided in an embodiment of this application. Detailed Implementation
[0079] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0080] Before introducing the scheme of this application, the following points should be noted.
[0081] (1) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction as being used to instruct A, it can be understood that the instruction carries A, carries the identifier of A, carries B which is associated with A, carries the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction can determine A based on the instruction, it can be described as the instruction being used to instruct A, and the specific method of determination is not limited. When it is understood that the instruction carries A, "instruction" or "used to instruct" can be replaced with "includes". In this case, a statement similar to "sending / receiving instruction information, the instruction information being used to instruct A" can be replaced with "sending / receiving A".
[0082] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.
[0083] (2) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.
[0084] (3) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.
[0085] (4) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0086] (5) In this application, "first", "second", "#1" and "#2" are used only for the convenience of description and to distinguish objects, and are not used to limit the scope of the embodiments of this application.
[0087] (6) In this application, "predefined" may refer to a standard protocol predefined, or it may refer to a pre-agreed or pre-negotiated agreement between devices. Here, "protocol" may refer to a standard protocol in the field of communications, such as fourth-generation (4G) protocols. th Generation 4G network, fifth generation (5G) network th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR), 5.5G, and related protocols used in future communication networks.
[0088] (7) In this application, the words "exemplarily," "for example," "for instance," etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "example" is intended to present the concept in a specific manner. In the embodiments of this application, "of," "corresponding, relevant," and "corresponding" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.
[0089] First, let me introduce the communication system to which this application applies.
[0090] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) system, 4G / 5G mobile communication system, Future Mobile Communication System or New Radio (NR) system, Wireless Local Area Network (WLAN) system, and Wireless Fidelity (WiFi) system. Among these, the 5G mobile communication system can be either non-standalone (NSA) or standalone (SA) network.
[0091] The technical solutions provided in this application can also be applied to machine-type communication (MTC), long-term evolution-machine (LTE-M) technology, device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks. IoT networks, for example, can include vehicle-to-everything (V2X) networks. The communication methods in V2X systems are collectively referred to as vehicle-to-other-device (V2X), where X can represent anything. For example, V2X can include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.
[0092] Referring to Figure 1, as an example, Figure 1 is a network architecture 100 applicable to the communication system of the embodiments of this application.
[0093] Network architecture 100 can be applied to 4G communication systems and 5G communication systems, for example. The various parts involved in network architecture 100 are described below.
[0094] 1. User equipment (UE) 110: may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of terminals, mobile stations (MS), terminals, soft terminals, etc.
[0095] 2. Radio access network (RAN) element 120: Used to provide network access functionality for authorized user equipment in a specific area, and can use transmission tunnels of different quality according to the user equipment level, service requirements, etc.
[0096] (R)AN network element 120 can manage radio resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and core network. (R)AN network element 120 can also be understood as a base station in a traditional network.
[0097] 3. User plane network element 130: Used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data.
[0098] In a 5G communication system, the user plane network element 130 can be a user plane function (UPF) network element. In future communication systems, the user plane network element 130 can still be a UPF network element, or it can have other names; this application does not limit this.
[0099] 4. Data network element 140: Used to provide a network for transmitting data.
[0100] In a 5G communication system, data network element 140 can be a data network (DN) element. In future communication systems, data network element 140 can still be a DN element, or it can have other names; this application does not limit this.
[0101] 5. Access and Mobility Management Network Element 150: Mainly used for mobility management and access management, it can be used to implement other functions of the mobility management entity (MME) besides session management, such as access authorization / authentication.
[0102] In 5G communication systems, the access and mobility management network element 150 can be an access and mobility management function (AMF). In future communication systems, the access and mobility management network element 150 can still be an AMF, or it can have other names; this application does not limit this.
[0103] 6. Session Management Element 160: Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification, etc.
[0104] In a 5G communication system, the session management network element 160 can be a session management function (SMF) network element. In future communication systems, the session management network element 160 can still be an SMF network element, or it can have other names; this application does not limit this.
[0105] 7. Policy Control Element 170: A unified policy framework used to guide network behavior, providing policy rule information to control plane functional elements (such as AMF, SMF, etc.).
[0106] In 4G communication systems, the policy control network element 170 can be a policy and charging rules function (PCRF) network element. In 5G communication systems, the policy control network element 170 can be a policy control function (PCF) network element. In future communication systems, the policy control network element 170 can still be a PCF network element, or it can have other names; this application does not limit this.
[0107] 8. Authentication Server 180: Used for authentication services, generating keys to achieve two-way authentication of user devices, and supporting a unified authentication framework.
[0108] In 5G communication systems, the authentication server 180 (or authentication server functional network element) can be an AUSF network element. In future communication systems, the authentication server 180 can still be an AUSF network element, or it can have other names; this application does not limit this.
[0109] 9. Data Management Network Element 190: Used to handle user equipment identification, access authentication, registration, and mobility management, etc.
[0110] In a 5G communication system, the data management network element 190 can be a UDM network element; in a 4G communication system, the data management network element 190 can be a home subscriber server (HSS) network element. In future communication systems, the data management network element 190 can still be a UDM network element, or it can have other names, which are not limited in this application.
[0111] 10. Application Network Element 1100: Used for data routing affected by applications, accessing network open function network elements, and interacting with the policy framework for policy control, etc.
[0112] In a 5G communication system, application network element 1100 can be an application function (AF) network element. In future communication systems, application network element 1100 can still be an AF network element, or it can have other names; this application does not limit this.
[0113] 11. Network storage element: Used to maintain real-time information of all network function services in the network.
[0114] In 5G communication systems, this network storage element can be a network repository function (NRF) element. In future communication systems, the network storage element can still be an NRF element, or it can have other names; this application does not limit its scope.
[0115] It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). For ease of explanation, this application will subsequently use the access and mobility management device as AMF, the data management network element as UDM, the session management network element as SMF, and the user plane network element as UPF as an example for illustration.
[0116] For ease of explanation, this application uses AMF entities and UDM entities as examples to describe the method for session establishment. For the implementation method of chips within AMF entities and UDM entities, please refer to the specific descriptions of AMF entities and UDM entities respectively, which will not be repeated here.
[0117] In the network architecture shown in Figure 1, User Equipment (UE) connects to the AMF via interface N1, (R)AN connects to the AMF via interface N2, and (R)AN connects to the UPF via interface N3. UPFs are connected to each other via interface N9, and UPFs are interconnected via interface N6 (DN). The SMF controls the UPF via interface N4. The AMF connects to the SMF via interface N11. The AMF obtains UE subscription data from the UDM unit via interface N8, and the SMF obtains UE subscription data from the UDM unit via interface N10.
[0118] It should be understood that the network architecture described above for the embodiments of this application is merely an example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.
[0119] For example, in some network architectures, network function elements such as AMF, SMF, PCF, BSF, and UDM are all called network function (NF) elements; or, in other network architectures, a collection of elements such as AMF, SMF, PCF, BSF, and UDM can be called control plane function elements.
[0120] In the embodiments of this application, user equipment can refer to access terminal, user unit, user station, mobile station, mobile station, relay station, remote station, remote terminal, mobile device, UE, terminal equipment, terminal, wireless communication equipment, user agent, or user device. User equipment can also be cellular phone, cordless phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, vehicle-mounted device, wearable device, user equipment in future 5G networks, or user equipment in future evolved public land mobile network (PLMN), etc., and the embodiments of this application are not limited thereto.
[0121] The network device in this application embodiment can be any device with wireless transceiver function used for communicating with user equipment. This equipment includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved Node B (or home Node B (HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a WIFI system. It can also be a next-generation base station (gNB) in a 5G system, such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU).
[0122] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It is understood that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as a network device in the radio access network (RAN) or as a network device in the core network (CN), and this application does not limit this.
[0123] It should be understood that 3GPP access refers to accessing a mobile network using 3GPP access technologies, including but not limited to 5G, LTE, and UMTS. In simpler terms, 3GPP access technologies utilize base stations such as gNB and eNB for access. Non-3GPP access refers to accessing the network using technologies other than 3GPP access technologies. Non-3GPP access technologies include, but are not limited to, WiFi, Bluetooth, and ZigBee. Non-3GPP access types include untrusted non-3GPP access and trusted non-3GPP access. For example, untrusted non-3GPP access accesses the core network through radio access nodes deployed by non-operators, while trusted non-3GPP access access accesses the core network through radio access nodes deployed by operators, as well as wired access technologies.
[0124] The system architectures of non-trusted non-3GPP and trusted non-3GPP are described below with reference to Figures 2 and 3, respectively.
[0125] Referring to Figure 2, as an example, Figure 2 is a schematic diagram of the untrusted non-3GPP system architecture 200 provided in this application.
[0126] As shown in Figure 2, the network architecture 200 may include, but is not limited to, the following network elements (or functional network elements, functional entities, nodes, devices, etc.): UE, non-3GPP interworking function (N3IWF), 3GPP(R)AN, UPF, DN, AMF, SMF, etc.
[0127] For example, a UE can access an untrusted, non-3GPP access network device, such as WiFi, via the Y1 interface. The untrusted non-3GPP access network device can access the N3IWF via the Y2 interface. The N3IWF can connect to the AMF via the N2 interface and to the UPF via the N3 interface. Alternatively, the UE can also connect to the AMF via a 3GPP access technology (e.g., the N1 interface). In other words, a UE can simultaneously access the same or different AMFs via both 3GPP and non-3GPP access technologies; a UE can also access the AMF solely via 3GPP access technology or solely via non-3GPP access technology.
[0128] The N3IWF can be used to allow interconnection between terminal equipment (e.g., UE) and the 3GPP core network (e.g., AMF) using non-3GPP technologies. The N3IWF supports communication with the Mobility Management Equipment (MME) via the N2 interface and with the User Plane Equipment (MPA) via the N3 interface. For descriptions of other network element functions, please refer to the corresponding network element function descriptions in Figure 1; they will not be repeated here. N1, N2, N3, N4, N6, and N11 are interface sequence numbers; the meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols and are not limited here.
[0129] Referring to Figure 3, as an example, Figure 3 is a schematic diagram of the trusted non-3GPP system architecture 300 provided in this application.
[0130] As shown in Figure 3, the network architecture 300 may include, but is not limited to, the following network elements (or functional network elements, functional entities, nodes, devices, etc.): UE, trusted non-3GPP access point (TNAP), trusted non-3GPP gateway function (TNGF), 3GPP(R)AN, UPF, DN, AMF, SMF, etc. Among them, TNAP and TNGF belong to the trusted non-3GPP access network (TNAN), and TNAP and TNGF can be connected through the Ta interface, while TNGF can be connected to TNAN through the Tn interface.
[0131] For example, a UE can access the TNAP via the Yt interface and the TNGF via the NWt interface. The TNGF can connect to the AMF via the N2 interface and to the UPF via the N3 interface. Alternatively, the UE can also connect to the AMF via 3GPP access technology (e.g., the N1 interface). In other words, a UE can simultaneously access the same or different AMFs via both 3GPP and non-3GPP access technologies; a UE can also access the AMF solely via 3GPP access technology or solely via non-3GPP access technology.
[0132] TNAP can be referred to as a trusted non-3GPP access node, which can be an access node deployed by the operator. TNAP can be used to send AAA messages, such as encapsulating Extensible Authentication Protocol (EAP) packets in AAA messages and interacting with TNGF, and can be used to forward NAS messages. TNGF can be used to support N2 and N3 interfaces, terminate EAP-5G signaling, implement AMF selection, process N2 signaling with SMF (relayed by AMF) to support sessions and QoS, and transparently relay PDUs between terminal equipment and user plane equipment. For introductions to other network element functions, please refer to the corresponding network element function descriptions in Figure 1, which will not be repeated here. N1, N2, N3, N4, N6, and N11 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols, and are not limited here.
[0133] It should be understood that the solutions provided in this application are applicable to both untrusted non-3GPP and trusted non-3GPP system architectures, and do not specifically limit or distinguish specific application scenarios.
[0134] To facilitate understanding of the solutions in the embodiments of this application, relevant concepts are explained.
[0135] 1. Access technology:
[0136] This refers to the access technology used by the terminal device to connect to the communication device, or the access technology used by the terminal device to establish a communication connection with the communication device.
[0137] As an example, access technologies may include NR, UMTS terrestrial radio access network (E-UTRAN), Multefire, 3GPP access technologies, non-3GPP access technologies, 4G cellular access technologies, 5G cellular access technologies, trusted or untrusted WiFi access technologies, fixed or wired access technologies, etc. No limitation is imposed.
[0138] The access network using non-3GPP access technology (or simply non-3GPP access network) may include, but is not limited to: WiFi network, WLAN, MulteFire network, wired network (e.g., wireless and wireline convergence (WWC) network), or home base station network.
[0139] 2. Evolved Residential Gateway (eRG):
[0140] eRG is a gateway device between public carrier networks (such as fixed, mobile, or wired networks) and customer premises networks (such as networks in homes, offices, or shops).
[0141] 3. Evolved Packet Data Gateway (ePDG):
[0142] ePDG is used to ensure that the UE uses non-3GPP access technology to access the EPC for data transmission. For example, in the initial attachment scenario where the UE accesses the core network via non-3GPP access technology, ePDG can use the Domain Name System (DNS) to query and determine the packet data gateway (PGW) network element corresponding to the access point name (APN) in the user's subscription data; or, ePDG can directly obtain the PGW identifier corresponding to the APN from the user's subscription data, select the appropriate session management network element to establish a PDN connection for the terminal device, and thus enable the UE to establish a connection with the PGW, thereby providing the UE with the corresponding Internet Protocol (IP) services, such as IP Multimedia Subsystem (IMS) and Packet Switching Service (PSS).
[0143] 4. AAA Server:
[0144] The AAA server is used to register the received PGW identifier with the HSS and to account for UEs using network resources. This process includes three steps: authentication (verifying user access rights), authorization (authorizing services the user can use), and accounting (recording user network resource usage). During the authentication and authorization process, the AAA server also requests and obtains relevant user subscription data from the HSS and executes the corresponding authentication and authorization procedures based on this data. Furthermore, the AAA server may include an AAA agent, which can perform operations on behalf of the AAA server.
[0145] 5. Network access identifiers (NAIs):
[0146] The NAI format is a standardized format used to identify network users. It is commonly used in network authentication and authorization processes for terminal devices to identify and verify user identities. The NAI format mainly consists of a user part and a realm part. The user part identifies the specific user, while the realm part identifies the network scope.
[0147] 6. User Permanent Identifier SUPI:
[0148] SUPI is a globally unique permanent 5G user identifier assigned to each user and stored in the 5G core network's UDM or unified data management (UDR). In non-3GPP network access scenarios, SUPI is in NAI format. Currently, SUPI types include Type 0 (International Mobile Subscriber Identity (IMSI)), Type 1 (Network Specific Identifier (NSI)), Type 2 (Global Line Identifier (GLI)), and Type 3 (Global Cable Identifier (GCI)). Among these, NSI, GLI, and GCI types of SUPI are all in NAI format.
[0149] Among them, the NAI format SUPI is a type of SUPI generated by a third party rather than the operator. It is a general format, and its representation is username@realm. Here, username represents the username corresponding to the SUPI, and realm represents the domain name corresponding to the SUPI.
[0150] When terminal devices access the core network through a non-3GPP network, the security authentication mechanisms used by different communication technologies may differ. Taking the security authentication mechanisms used by the Evolved Packet Core Network (EPC) (4G core network) and the 5G core network (5GC) as examples, the 4G core network typically implements authentication based on the Extensible Authentication Protocol (EAP-AKA) authentication method protocol, and generally manages authentication through an AAA server. This authentication mechanism can prevent replay attacks and protect the security of users and the network. The 5G core network typically adopts a unified authentication framework, supports multiple authentication methods such as 5G-AKA and EAP-AKA, and is processed by the AUSF network elements and UDM network elements of the 5G core network, which can provide higher security for terminal devices.
[0151] Due to differences in security authentication mechanisms, network devices need to select the correct security authentication mechanism for authentication during the process of terminal devices accessing the core network. For non-3GPP network architectures compatible with both 4G and 5G core networks, the network device cannot determine whether the terminal device is requesting access to the 4G or 5G core network during the process of requesting access to the core network. Therefore, it may select the wrong security authentication mechanism, resulting in confusion of security policies, leading to authentication failure and inability to access the network.
[0152] Furthermore, the gateways used to access the core network for different non-3GPP technologies are not fully compatible. Therefore, it is usually necessary to deploy separate access gateways for different technologies. Moreover, the access technologies between the 4G core network and the 5G core network are not compatible, which in turn increases the demand for network connection resources and the operating costs.
[0153] To address the aforementioned issues, this application proposes a communication method that includes the core network type requested by the terminal device in the security authentication request information. This allows network elements related to security authentication to obtain network type information, thereby selecting the correct security authentication mechanism to authenticate the terminal device, improving the accuracy of the terminal device's access to the core network, and enhancing the security of the network connection.
[0154] The methods provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings. In the following embodiments, terminal devices and network devices (e.g., gateways and network elements) are used as examples for illustrative purposes. The terminal device can be replaced by a component of the terminal device (e.g., a chip, chip system, or circuit), and the network device can be replaced by a component of the network device (e.g., a chip, chip system, or circuit).
[0155] Referring to Figure 4, as an example, Figure 4 is a schematic diagram of a communication method 400 provided in an embodiment of this application.
[0156] S410, the terminal device sends a first request message to the gateway device, and correspondingly, the gateway device receives the first request message from the terminal device. This first request message indicates that the terminal device requests access to the core network through a non-3GPP network. The first request message includes a first identifier, which is associated with the type of core network the terminal device requests to access. Optionally, the terminal device may be an eRG (eRG).
[0157] Specifically, based on its own resource configuration or preset information, the terminal device sends the core network type and device information to the gateway device to request the authentication process for accessing the corresponding core network. The request information includes identification information (e.g., a first identifier), which may be, for example, the ID of the eRG (or eRG_ID), including the core network type requested by the terminal device, and other device information.
[0158] In the embodiments of this application, the first identifier is used to indicate the communication technology requested for access, or network type. The format of the first identifier is NAI format. Specifically, the first identifier has the following two possible implementations.
[0159] One possible implementation is that the first identifier can be a SUPI type. In the embodiments of this application, the first identifier is a new SUPI type, for example, it can be denoted as a new type Y (networkTypeY), used to indicate the network type. For example, the first identifier can be represented as:
[0160] " <networktypey> <username>@wlan.mnc <mnc>.mcc <mcc>.3gppnetwork.org”
[0161] in, <networktypey>This is a placeholder used to indicate the network type corresponding to this information; <username>It serves as a user identification identifier, used to distinguish different terminal devices or users; <mnc>This is another placeholder used to replace the actual mobile network code in the actual transmission; <mcc>This is another placeholder used to identify the country or region where the terminal device is located; 3gppnetwork.org is the domain name suffix. Additionally, "@wlan.mnc" indicates the network type; for example, when requesting access to the 4G core network, the first identifier can be represented as:
[0162] " <networktypey> <username>@epc.mnc <mnc>.mcc <mcc>.3gppnetwork.org”
[0163] When requesting access to the 5G core network, the first identifier can be represented as:
[0164] " <networktypey> <username>@5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org.
[0165] In networkTypeY, "Y" can be any positive integer from 4 to 7, meaning that this information can be any of the newly defined SUPI types 4 to 7.
[0166] Another possible implementation is that the first identifier can be NAI information, that is, instead of introducing a new SUPI type, network type indication information is introduced. Specifically, the NAI introduces access network type indication information, which can be represented as follows:
[0167] " <networktypex> <username>@wlan.mnc <mnc>.mcc <mcc>.3gppnetwork.org”
[0168] Where X can be any positive integer from 0 to 3, meaning this information can be set to any of the existing SUPI types 0 to 3. "@wlan.mnc" represents the network type. For example, when requesting access to the 4G core network, the first identifier can be represented as:
[0169] " <username>@epc.mnc <mnc>.mcc <mcc>.3gppnetwork.org”
[0170] When requesting access to the 5G core network, the first identifier can be represented as:
[0171] " <username>@5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org.
[0172] Based on the above definition of the first identifier format and representation method, the terminal device can carry the network type requested for access in the request information, enabling the network elements related to authentication to obtain the network type information during signal transmission, thereby reducing errors caused by the misalignment of network information between network elements, improving the efficiency of the terminal device accessing the network, and enhancing the security of the authentication mechanism.
[0173] It should be understood that the above implementation method is based on the case of a terminal device requesting access to the 4G and 5G core networks. This application is not limited to this. For example, it can also be the case of a terminal device requesting access to future communication technologies and the 5G core network.
[0174] In addition to the identification information mentioned above, the first request information may also include the authentication information of the terminal device, which is used in the authentication process of the terminal device.
[0175] Specifically, when a terminal device requests access to the 4G core network, the first request information may also include an access network identity (ANID) and / or a network type. The ANID identifies different network types to help the user equipment and the network identify the type of network to access. In non-3GPP access scenarios, the ANID identifies the access network information and, combined with other authentication information, completes user authentication. Of the parameters mentioned above, the ANID can be pre-configured by the terminal device (e.g., eRG) or assigned to the terminal device by the network device. The network type is assigned to the terminal device by the network device. Assignment by the network device means that the network device sends the authentication information to the terminal device, and then the terminal device sends it along with the first request information to the network device.
[0176] Alternatively, when a terminal device requests access to the 5G core network, the first request information may also include the serving network name (SNN) and / or network type. The SNN is the name or identifier of the access network, used in the authentication process between the core network and the terminal device. This ensures the terminal device can securely access the correct serving network and supports efficient authentication and key management processes. The SNN can be configured by the network device; that is, the terminal device sends a request to the network device, the network device sends the authentication information, such as the SNN, to the terminal device, and the terminal device then includes this authentication information in the first request information and sends it to the network device to request the network authentication process.
[0177] As one possible implementation, the authentication information can be included in the first identifier. For example, when a terminal device requests access to the 4G core network, the eRG_ID includes the ANID and / or network type; or when a terminal device requests access to the 5G core network, the eRG_ID includes the SNN and / or network type. If the first identifier includes authentication information, the first request information does not need to indicate authentication-related information. After receiving the request information, the network device can obtain the authentication information by parsing the first identifier, which reduces resource consumption during information transmission.
[0178] Optionally, in addition to the explicit indication of the core network type mentioned above, an implicit indication method can also be used. Specifically, taking the terminal device requesting access to both a 4G and 5G core network as an example, if the terminal device requests access to the 4G core network, the first identifier is in an unencrypted format; conversely, if the terminal device requests access to the 5G core network, the first identifier is in an encrypted format. As an example, for a first identifier of the SUPI type, encryption algorithms such as the elliptic curve integrated encryption scheme (ECIES) can be used for encryption. In the implicit indication method, the first identifier may not include information indicating the specific network type, and the first request information may also not include information indicating the network type. In this case, the network device distinguishes the core network type requested by the terminal device by whether or not encryption is used. This method can reduce resource consumption and improve signal transmission efficiency and resource utilization.
[0179] S420, the gateway device sends a second request message to the authentication network element, and the authentication network element receives the second request message from the gateway device. This second request message is used to request authentication of the terminal device, and includes a second identifier, which indicates the core network type associated with the first identifier. Optionally, the gateway device can be an ePDG, or a related network device capable of replacing the ePDG's functions.
[0180] It should be understood that the second identifier in the second request information and the first identifier in the first request information can be the same, or the second identifier and the first identifier can be different. For example, the gateway device saves the received first identifier and sends it as the second identifier to the authentication network element. In this case, the second identifier and the first identifier are the same, and both can be eRG_ID. Another example is that the gateway device parses the received first identifier and sends the parsed information (e.g., ANID and / or network type, or SNN and / or network type) as the second identifier to the authentication network element. In this case, the second identifier is different from the first identifier. Yet another example is when the authentication network element includes at least two authentication network elements, each used for authentication processing of a type of core network. In this case, the gateway device sends the second request information to the data management network element corresponding to the core network type. The second identifier does not need to include specific core network type information; in this case, the second identifier is different from the first identifier.
[0181] Regarding authentication network elements, there are two possible scenarios.
[0182] In scenario #1, the authentication network element is used for authentication processing of at least two types of core networks. The at least two types include the type associated with the first identifier and the second identifier is used to indicate the core network type associated with the first identifier.
[0183] In one example, the authentication network element includes two interfaces, one for 4G and the other for 5G core network access. When a terminal device requests access to the core network, it selects the corresponding interface type to transmit authentication-related information. The authentication network element can be an AAA server or an AUSF server. The AAA server can also use an AAA proxy to assist in executing the corresponding procedures.
[0184] In another example, the authentication network element includes an interface for accessing the 4G or 5G core network. When the core network type requested by the terminal device does not match the type supported by the interface, a new interface associated with the core network type requested by the terminal device is created to receive authentication-related information from the terminal device.
[0185] For example, taking the AAA server as an authentication network element, the AAA server and the gateway device use a point-to-point interface, also known as a peer-to-peer interface. The peer-to-peer interface establishes a direct communication connection between two points, enabling data transmission between two terminal devices or network elements without the need for an intermediate server or central node. This AAA server includes a 4G core network peer-to-peer interface. When the gateway device sends a second request message indicating that the terminal device requests access to the 5G core network, a new interface is established between the gateway device and the AAA server—the 5G core network peer-to-peer interface. The request message is then sent to the AAA server through this 5G core network interface to indicate that the requested network is the 5G core network.
[0186] For example, taking the authentication network element as the AUSF server, the AUSF server and the gateway device use a service-based interface. This service-based interface is specific to a single network element and encapsulates different functional modules into independent services. Interaction and integration between services are achieved through clearly defined interface specifications. The AUSF server includes a 5G core network service-based interface. When the second request information sent by the gateway device indicates that the terminal device requests access to the 4G core network, a new interface is established between the gateway device and the AUSF server—the 4G core network service-based interface. The request information is sent to the AUSF server through this 4G core network interface to indicate that the requested network is the 4G core network.
[0187] It should be understood that the number of interfaces mentioned above is merely an example and not a limitation. For example, the authentication network element may also include multiple peer interfaces or service interfaces corresponding to multiple network types, or the authentication network element may also construct multiple peer interfaces or service interfaces corresponding to multiple network types. This application does not impose specific limitations on this.
[0188] In scenario #2, the authentication network element includes at least two authentication network elements, which correspond one-to-one with at least two core network types. The first authentication network element associated with the first identifier receives the second request information sent by the gateway device.
[0189] In one example, the authentication network element includes at least two authentication network elements, each used for access to different types of networks. When a terminal device requests access to the core network, it selects the corresponding type of authentication network element for authentication processing. For example, if the authentication network element includes two authentication network elements, these two elements could be AAA server and AAA server, AUSF server and AUSF server, or AAA server and AUSF server.
[0190] Another example is that the authentication network element originally includes one authentication network element used for authentication of 4G and 5G core networks. When the type of core network access requested by the terminal device does not match the type associated with the authentication network element, a new authentication network element is created associated with the type of core network access requested by the terminal device to receive authentication-related information from the terminal device. For example, taking the authentication network element as an AAA server, this AAA server is usually used for authentication processing of 4G core network access. When the second request information sent by the gateway device indicates that the terminal device requests access to the 5G core network, a new AAA server is created for 5G core network access authentication. As another example, taking the authentication network element as an AUSF server, this AUSF server is usually used for authentication processing of 5G core network access. When the second request information sent by the gateway device indicates that the terminal device requests access to the 4G core network, a new AUSF server is created for 5G core network access authentication.
[0191] It should be understood that the above scenario is merely an example of a terminal device requesting access to the 4G and 5G core networks. This application is not limited to this; for example, it could also involve a terminal device requesting access to future communication technologies and the 5G core network. By configuring different authentication network element pairs, the operating mode can be adjusted according to different scenarios and network requirements during the terminal device's access to the core network, thereby flexibly accessing different network information. For example, choosing to create a new interface or a new authentication network element can distinguish between access to the 4G and 5G core networks and information reception, avoiding confusion in the selection of security authentication mechanisms and improving the security of non-3GPP network access.
[0192] In some possible embodiments, when the first request information includes an SNN, the gateway device can also parse the SNN to generate an ANID, which is used for the authentication process of the 5G core network. In this case, the second request information sent by the gateway device to the authentication network element includes the SNN, which can be included in the authentication information.
[0193] In addition to the identification information mentioned above, the second request information may also include the authentication information of the terminal device. For example, if the terminal device requests access to the 4G core network, the second request information may also include the access network identifier (ANID) and / or network type. Similarly, if the terminal device requests access to the 5G core network, the second request information may also include the SNN and / or network type. For detailed explanations, please refer to step S410, which will not be repeated here.
[0194] Optionally, the authentication information can be included in the second identifier. For example, if the terminal device requests access to the 4G core network, the eRG_ID includes the ANID and / or network type; or if the terminal device requests access to the 5G core network, the eRG_ID includes the SNN and / or network type. Besides the explicit indication of the core network type, an implicit indication method can also be used. Specifically, taking the terminal device requesting access to the 4G and 5G core networks as examples, if the terminal device requests access to the 4G core network, the second identifier is in an unencrypted format; or if the terminal device requests access to the 5G core network, the second identifier is in an encrypted format.
[0195] S430, the authentication network element sends a third request message to the data management network element, and correspondingly, the data management network element receives the third request message from the authentication network element. This third request message is used to request the first data management network element to authenticate the terminal device. The third request message also includes a third identifier, which indicates the type of core network the terminal device is requesting to access.
[0196] The authentication network element is used for authentication processing in at least two types of core networks, and these at least two types include the type associated with the second identifier. Optionally, the data management network element can be a UDM.
[0197] Specifically, the third identifier in the third request information can be the same as the second identifier in the second request information, or the third identifier and the second identifier can be different. For example, the authentication network element saves the received second identifier and sends it to the authentication network element as the third identifier. In this case, the third identifier and the second identifier are the same, and both can be eRG_ID. Another example is that the gateway device parses the received third identifier and sends the parsed information (e.g., ANID and / or network type, or SNN and / or network type) as the third identifier to the authentication network element. In this case, the third identifier is different from the second identifier. Yet another example is when the data management network element includes at least two data management network elements, each used for the authentication process of a type of core network. In this case, the authentication network element sends the third request information to the data management network element corresponding to the core network type. The third identifier does not need to include specific core network type information; in this case, the third identifier is different from the second identifier.
[0198] Regarding data management network elements, there are two possible scenarios.
[0199] In scenario #1, the data management network element is used for the authentication process of at least two types of core networks, including the type associated with the third identifier, which is used to indicate the core network type associated with the second identifier.
[0200] In one example, the data management network element includes two service interfaces, one for 4G and the other for 5G core network access. When a terminal device requests access to the core network, it selects the corresponding service interface to transmit data management-related information. For instance, the third request information sent by the authentication network element could be a Nudm_eRGAuthentication_Get request. When this request information is received through the 4G core network service interface, the data management network element can determine that the terminal device is requesting access to the 4G core network and generate an authentication vector for accessing the 4G core network.
[0201] In another example, the data management network element includes a service-oriented interface for access to the 4G or 5G core network. When the core network type requested by the terminal device does not match the type supported by this interface, a new interface associated with the core network type requested by the terminal device is created to receive authentication-related information from the terminal device. For example, taking the data management network element as a UDM, the UDM includes a 4G core network service-oriented interface. When the third request information sent by the authentication network element indicates that the terminal device requests access to the 5G core network, a new interface, namely the 5G core network service-oriented interface, is established between the authentication network element and the UDM. The request information is sent to the UDM through this 5G network interface to instruct the generation of an authentication vector of the 5G core network type for the terminal device.
[0202] In scenario #2, the data management network element includes at least two data management network elements, which correspond one-to-one with at least two core network types. The first data management network element associated with the third identifier receives the third request information sent by the gateway device.
[0203] In one example, the data management network element includes two data management network elements, one for 4G and the other for 5G core network access. When a terminal device requests access to the core network, it selects the corresponding type of data management network element to perform the terminal device authentication process. For example, the third request information sent by the authentication network element can be Nudm_eRGAuthentication_Get request. When the data management network element receives this request information, it can determine that the terminal device is requesting access to the 4G core network, and then select the data management network element of the corresponding network type to receive the request information and generate an authentication vector for accessing the 4G core network.
[0204] In another example, a data management network element originally includes one data management network element used for authentication of 4G and 5G core networks. When the core network type requested by a terminal device does not match the type associated with this data management network element, a new data management network element is created that is associated with the core network type requested by the terminal device. This new data management network element is used to receive authentication-related information from the terminal device. For instance, taking a UDM (User Dedicated Provider) as an example, this UDM is typically used for authentication processing of 5G core network access. When the third request information sent by the authentication network element indicates that the terminal device requests access to the 4G core network, a new UDM is created. This new UDM is used to generate an authentication vector of the 4G core network type for the terminal device.
[0205] It should be understood that the above scenario is an example of a terminal device requesting access to the 4G and 5G core networks. This application is not limited to this, and the number of interfaces included in the data management network element is only an example, not a specific limitation.
[0206] By configuring different data management network elements, the working mode can be adjusted according to different scenarios and network requirements during the process of terminal equipment accessing the core network, thereby flexibly accessing different network information. For example, by choosing to create a new interface or a new data management network element, it is possible to distinguish the reception of information of different network types (such as 4G and 5G core networks), avoid confusion of the corresponding network type when generating authentication vectors, and improve the security of non-3GPP network access.
[0207] In some possible embodiments, when the second request information includes an SNN, the authentication network element can also parse the SNN to generate an ANID, which is used in the 5G core network authentication process. In this case, the third request information sent by the gateway device to the authentication network element includes an SNN, which can be included in the authentication information.
[0208] In addition to the aforementioned identification information, the third request information may also include the authentication information of the terminal device. For example, if the terminal device requests access to the 4G core network, the third request information may also include the access network identifier (ANID) and / or network type. Similarly, if the terminal device requests access to the 5G core network, the third request information may also include the SNN and / or network type. For detailed explanations, please refer to step S410, which will not be repeated here.
[0209] Optionally, the aforementioned authentication information may be included in the third identifier. For example, when a terminal device requests access to the 4G core network, the eRG_ID includes the ANID and / or network type; or, when a terminal device requests access to the 5G core network, the eRG_ID includes the SNN and / or network type. Besides the explicit indication of the core network type, an implicit indication method can also be used. Specifically, taking the terminal device requesting access to the 4G and 5G core networks as examples, when the terminal device requests access to the 4G core network, the third identifier is in an unencrypted format; or, when the terminal device requests access to the 5G core network, the third identifier is in an encrypted format.
[0210] S440, the data management network element generates an authentication vector based on the third request information. This authentication vector is used to authenticate terminal devices. The data management network element is used for authentication processing in at least two types of core networks, and these at least two types include those associated with the third identifier.
[0211] Specifically, after receiving the third request information, the data management network element can determine the network type requested by the terminal device and generate an authentication vector based on the authentication-related information (such as a third identifier and / or authentication information). The methods for generating the authentication vector can include the following two examples.
[0212] In one example, the third request information includes authentication information.
[0213] For example, if the authentication information contains an ANID, the data management network element can determine that the network type requested by the terminal device is the 4G core network. In this case, the data management network element generates an authentication vector for accessing the 4G core network through the ANID. This authentication vector is used to authenticate the terminal device's access to the 4G core network.
[0214] For example, if the authentication information includes an SNN, the data management network element can determine that the network type requested by the terminal device is the 5G core network. In this case, the data management network element generates an authentication vector for accessing the 5G core network through the SNN, or the data management network element generates an ANID based on the SNN, and then generates an authentication vector for accessing the 5G core network based on the ANID. This authentication vector is used to authenticate the terminal device's access to the 5G core network.
[0215] For example, if the authentication information includes the network type, the data management network element can determine the network type (4G core network or 5G core network) that the terminal device requests to access. In this case, the data management network element generates an authentication vector corresponding to the core network type through the network type. This authentication vector is used to authenticate the terminal device's access to the core network.
[0216] Another example is that the third request information does not include authentication information.
[0217] For example, the third identifier indicates the network type that the terminal device requests to access. After parsing the third identifier, the data management network element generates an authentication vector corresponding to the core network type based on the obtained information.
[0218] For example, the third identifier does not contain information that explicitly indicates the network type. Instead, it distinguishes the network type by whether it is encrypted or not. In this case, the data management network element can determine whether the format of the third identifier is encrypted or unencrypted. If the third identifier is encrypted, an authentication vector for accessing the 5G core network is generated. If the third identifier is unencrypted, an authentication vector for accessing the 4G core network is generated.
[0219] It should be understood that the above example is based on the scenario where a terminal device requests access to the 4G and 5G core networks, and this application is not limited to this.
[0220] S450, the data management network element sends an authentication vector to the authentication network element, and correspondingly, the authentication vector receives the authentication vector from the data management network element.
[0221] Optionally, the data management network element can send the received authentication information to the authentication network element, and correspondingly, the authentication network element receives the authentication information from the data management network element. The authentication network element stores the authentication vector of the terminal device. Optionally, the authentication network element can also store the identification information (e.g., a third identifier) corresponding to the authentication vector, and associate the identification information with the authentication vector to facilitate information identification.
[0222] S460, the authentication network element authenticates terminal devices.
[0223] Specifically, the authentication network element performs security authentication on the terminal device based on the received authentication-related information. For example, the authentication network element can perform authentication processing based on the authentication vector from the data management network element, or, if the authentication network element already includes an authentication vector, the authentication network element can perform authentication processing based on the second request information from the gateway device.
[0224] In some possible implementations, after the terminal device has sent a first request message including a first identifier (e.g., eRG_ID) to the gateway device, it sends another request message. Upon receiving this request message, the gateway device sends a corresponding second request message to the authentication network element, which includes the corresponding second identifier. When the authentication network element receives the second request message from the gateway device, it identifies the currently stored authentication vector. If the authentication network element has already stored the authentication vector corresponding to the identifier information (e.g., the second identifier) contained in the second request message, it means that the authentication network element has already generated an authentication vector for the terminal device. In this case, the authentication network element does not send a third request message to the data management network element, that is, it does not need to execute steps S430 to S450, and directly proceeds to step S460.
[0225] By storing authentication vectors and associating authentication vectors with identification information through authentication network elements, the authentication process can be adjusted when terminal devices repeatedly send request information and identification information, avoiding redundant steps and reducing unnecessary resource consumption.
[0226] The authentication process of the authentication network element will be explained in detail below with reference to Figures 5 and 6.
[0227] Referring to Figure 5, as an example, Figure 5 is a schematic diagram of a communication method 500 provided in an embodiment of this application. In the communication method 500, the authentication network element can be an AAA server.
[0228] S501, Terminal device and gateway device interface parameter configuration. Specifically, the terminal device and gateway device exchange the first pair of messages, namely the IKE_INIT message, and negotiate the encryption algorithm. In addition, the gateway device configures the interface parameters, which may include, for example, the IKE pre-shared key.
[0229] S502, the terminal device sends a first request message to the gateway device, and the gateway device receives the first request message from the terminal device. This first request message indicates that the terminal device requests access to the core network via a non-3GPP network. The first request message includes a first identifier, which is associated with the type of core network the terminal device requests to access.
[0230] S503, the gateway device sends a second request message to the authentication network element, and the corresponding authentication network element receives the second request message from the gateway device. This second request message is used to request authentication of the terminal device, and includes a second identifier, which indicates the core network type associated with the first identifier.
[0231] S504, the authentication network element sends a third request message to the data management network element, and correspondingly, the data management network element receives the third request message from the authentication network element. This third request message is used to request the first data management network element to authenticate the terminal device. The third request message also includes a third identifier, which indicates the type of core network the terminal device requests to access.
[0232] S505, the data management network element generates an authentication vector based on third request information, and this authentication vector is used to authenticate terminal devices. The data management network element is used for authentication processing in at least two types of core networks, and these at least two types include those associated with the third identifier.
[0233] S506, the data management network element sends an authentication vector to the authentication network element, and correspondingly, the authentication vector receives the authentication vector from the data management network element.
[0234] The specific implementation of steps S502 to S506 is shown in steps S410 to S450 of method 400 in Figure 4, and will not be repeated here.
[0235] S507, the authentication network element sends authentication challenge information to the gateway device, and the corresponding gateway device receives the authentication challenge information from the authentication network element.
[0236] S508, the gateway device sends a first request feedback to the terminal device, and correspondingly, the terminal device receives the first request feedback from the gateway device. The first request feedback can be sent via an IKE_AUTH request, and may include authentication parameters, which are EAP messages (EAP-Response / AKA-Challenge). These authentication parameters are used by the terminal device to respond to the authentication challenge.
[0237] S509, the terminal device responds to the authentication challenge. Specifically, the terminal device checks the authentication parameters and responds to the authentication challenge. If the terminal device requested CERTREQ in step S501, the gateway device should respond with its own identity (i.e., certificate). The terminal device executes the AKA mechanism, confirms the AUTN information, and generates the RES parameter and MSK parameter.
[0238] In S510, the terminal device sends a first authentication response message to the gateway device, and correspondingly, the gateway device receives the first authentication response message from the terminal device. The first authentication response message can be sent via an IKE_AUTH request, which includes an EAP message (EAP-Response / AKA-Challenge) for the terminal device to respond to the authentication challenge.
[0239] S511, the gateway device sends a second authentication response to the authentication network element, and correspondingly, the authentication network element receives the second authentication response from the gateway device. The second authentication response can be sent through an Authentication and Authorization Request (A&A-Request), which may include EAP messages, namely EAP-Response / AKA-Challenge messages.
[0240] S512, the authentication element checks the authentication response. Specifically, the authentication element checks whether the authentication response is correct to confirm the transmission of the next step of information.
[0241] In S513, authentication responses are exchanged between the terminal device, gateway device, and authentication device. If dynamic IP mobility selection is embedded in authentication and authorization, the selected mobility mode can be sent to the terminal device via a Diameter A&A response and an IKE_AUTH message in an AKA-Notification request. The terminal device responds to the request via the IKEv2 protocol, and the gateway device forwards the response to the authentication network element.
[0242] S514, authentication network elements and data management network elements perform retrieval and registration.
[0243] In step S515, the authentication network element sends an authentication response to the gateway device, and correspondingly, the authentication network element receives the authentication response from the gateway device. When all checks are successful, the 3GPP AAA Server sends the final Authentication and Authorization Answer (A&A answer) to the ePDG, carrying a success result code. This code includes relevant service authorization information, EAP success, and key materials. These key materials should consist of the MSK parameters generated by the terminal device during the authentication process.
[0244] S516, the gateway device generates authentication parameters. Specifically, the gateway device uses MSK to generate AUTH parameters to verify the IKE_INIT message.
[0245] S517, the gateway device sends a second request feedback to the terminal device, and correspondingly, the terminal device receives the second request feedback from the gateway device. This second request feedback can be sent via IKE_AUTH Response, and may also include an EAP message.
[0246] In step S518, the terminal device sends authentication parameters to the gateway device, and the gateway device receives the authentication parameters from the terminal device. These authentication parameters can be sent via the IKE_AUTH Response, which also includes AUTH parameters. During this process, the terminal device uses a copy of its own MSK parameters as input to generate AUTH parameters to verify the first IKE_INIT message.
[0247] S519, the gateway device verifies and calculates the authentication parameters. The ePDG verifies the correctness of the AUTH received from the UE. At this time, the terminal device is authenticated, the gateway device calculates the AUTH parameters, and verifies the second IKE_SA_INIT message.
[0248] In S520, the gateway device sends the authentication result to the terminal device, and the terminal device receives the authentication result from the gateway device. This authentication result can be sent via an IKE_AUTH Response, which may also include the AUTH parameter, configuration payload, security associations, and other IKEv2 parameters sent to the terminal device.
[0249] Steps S501, S507 to S520 above are some steps in the EAP-AKA' authentication method. For parts that are not detailed, please refer to the existing protocol.
[0250] Referring to Figure 6, as an example, Figure 6 is a schematic diagram of a communication method 600 provided in an embodiment of this application. In the communication method 600, the authentication network element can be an AUSF server.
[0251] S601, Terminal device and gateway device interface parameter configuration. Specifically, the terminal device and gateway device exchange the first pair of messages, namely the IKE_INIT message, and negotiate the encryption algorithm. In addition, the gateway device configures the interface parameters, which may include, for example, the IKE pre-shared key.
[0252] S602, the terminal device sends a first request message to the gateway device, and the gateway device receives the first request message from the terminal device. This first request message indicates that the terminal device requests access to the core network via a non-3GPP network. The first request message includes a first identifier, which is associated with the type of core network the terminal device requests to access.
[0253] S603, the gateway device sends a second request message to the authentication network element, and the corresponding authentication network element receives the second request message from the gateway device. This second request message is used to request authentication of the terminal device, and includes a second identifier, which indicates the core network type associated with the first identifier.
[0254] S604, the authentication network element sends a third request message to the data management network element, and correspondingly, the data management network element receives the third request message from the authentication network element. This third request message is used to request the first data management network element to authenticate the terminal device. The third request message also includes a third identifier, which indicates the type of core network the terminal device requests to access.
[0255] S605, the data management network element generates an authentication vector based on third request information, and this authentication vector is used to authenticate terminal devices. The data management network element is used for authentication processing in at least two types of core networks, and these at least two types include those associated with the third identifier.
[0256] S606, the data management network element sends an authentication vector to the authentication network element, and correspondingly, the authentication vector receives the authentication vector from the data management network element.
[0257] The specific implementation of steps S602 to S606 is shown in steps S410 to S450 of method 400 in Figure 4, and will not be repeated here.
[0258] S607, the authentication network element sends authentication challenge information to the gateway device, and the gateway device receives the authentication challenge information from the authentication network element. This authentication challenge information may include a DEA message or a DEA_EPC message. In the aforementioned steps, if a 4G or 5G core network interface is established between the gateway device and the authentication network element, the authentication challenge information is transmitted through the corresponding interface.
[0259] S608, the gateway device sends a first request feedback to the terminal device, and correspondingly, the terminal device receives the first request feedback from the gateway device. This first request feedback can be sent via an IKE_AUTH Request, which may include an EAP message, i.e., EAP-Request / AKA'Challenge, and this EAP message may contain an ANID.
[0260] S609, the terminal device responds to the authentication challenge. Specifically, the terminal device confirms the AUTN and calculates the RES information.
[0261] S610, the terminal device sends a first authentication response to the gateway device, and correspondingly, the gateway device receives the first authentication response from the terminal device. This first authentication response can be sent via IKE_AUTH Response, which may include an EAP message.
[0262] S611, the gateway device sends a second authentication response information request to the authentication network element, which may include an EAP message.
[0263] S612, the authentication element checks the authentication response. Specifically, the authentication element, namely the AUSF server, compares RES and XRES to determine whether network authentication was successful.
[0264] S613, the authentication network element sends an authentication response message to the gateway device, and correspondingly, the gateway device receives the authentication response message from the authentication network element. Specifically, the authentication network element, i.e., the AUSF server, sends a response to the gateway device, which includes EAP Success and key material. The key material may contain MSK information.
[0265] S614, the gateway device generates authentication parameters. Specifically, the gateway device uses MSK to generate AUTH parameters to verify the IKE_INIT message.
[0266] S615, the gateway device sends a second request feedback to the terminal device, and correspondingly, the terminal device receives the second request feedback from the gateway device. This second request feedback can be sent via IKE_AUTH Response, and may also include an EAP message.
[0267] S616, the terminal device sends authentication parameters to the gateway device, and correspondingly, the gateway device receives the authentication parameters from the terminal device. These authentication parameters can be sent via the IKE_AUTH Response, which also includes AUTH parameters. During this process, the terminal device uses a copy of its own MSK parameters as input to generate the AUTH parameters to verify the first IKE_INIT message.
[0268] S617, the gateway device verifies and calculates the authentication parameters. The ePDG verifies the correctness of the AUTH received from the UE. At this time, the terminal device is authenticated, the gateway device calculates the AUTH parameters, and verifies the second IKE_SA_INIT message.
[0269] S618, the gateway device sends the authentication result to the terminal device, and the corresponding terminal device receives the authentication result from the gateway device. This authentication result can be sent via an IKE_AUTH Response, which may also include the AUTH parameter, configuration payload, security association, and other IKEv2 parameters sent to the terminal device.
[0270] The steps S614 to S618 described above are the same as steps S516 to S520 in method 500 shown in Figure 5. For details, please refer to the content in Figure 5. For other parts not detailed, please refer to the existing protocol.
[0271] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 4 to 6. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 7 to 9. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.
[0272] Referring to Figure 7, as an example, Figure 7 is a schematic block diagram of a communication device 700 provided in an embodiment of this application.
[0273] The communication device 700 shown in Figure 7 includes a transceiver unit 710 and a processing unit 720. The transceiver unit 710 can communicate with the outside world, and the processing unit 720 is used for data processing. The transceiver unit 710 can also be referred to as a communication interface or a communication unit.
[0274] Optionally, the transceiver unit 710 may include a sending unit and a receiving unit. The sending unit is used to perform the sending operation in the above method embodiments. The receiving unit is used to perform the receiving operation in the above method embodiments.
[0275] It should be noted that the communication device 700 may include a transmitting unit but not a receiving unit. Alternatively, the communication device 700 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme executed by the communication device 700 includes both transmitting and receiving actions.
[0276] Optionally, the communication device 700 may further include a storage unit, which may be used to store instructions and / or data, and the processing unit 720 may read the instructions and / or data in the storage unit.
[0277] One possible design is that the device 700 can implement the steps or processes corresponding to those in the method embodiments described above. Specifically, the transceiver unit 710 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) in the method embodiments described above; the processing unit 720 can be used to perform operations other than transceiver operations (such as operations other than sending and / or receiving data or messages) in the method embodiments described above.
[0278] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.
[0279] It should also be understood that the device 700 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit, electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 700 can specifically be the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.
[0280] The apparatus 700 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, each executing the transceiver operations and related processing operations in each method embodiment.
[0281] In addition, the transceiver unit 710 described above can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.
[0282] Referring to Figure 8, as an example, Figure 8 is a schematic block diagram of a communication device 800 provided in an embodiment of this application.
[0283] The communication device 800 includes a processor 810 coupled to a memory 820 for storing computer programs or instructions and / or data. The processor 810 is used to execute the computer programs or instructions and / or data stored in the memory 820, so that the methods in the above method embodiments are executed.
[0284] Optionally, the communication device 800 may include one or more processors 810.
[0285] Optionally, as shown in FIG8, the communication device 800 may further include a memory 820.
[0286] Optionally, the communication device 800 may include one or more memory 820.
[0287] Alternatively, the memory 820 may be integrated with the processor 810 or set separately.
[0288] Optionally, as shown in FIG8, the communication device 800 may further include a transceiver 830 and / or a communication interface, the transceiver 830 and / or the communication interface being used for receiving and / or transmitting signals. For example, the processor 810 is used to control the transceiver 830 and / or the communication interface to receive and / or transmit signals.
[0289] Optionally, the device in transceiver 830 used to implement the receiving function can be regarded as a receiving module, and the device in transceiver 830 used to implement the transmitting function can be regarded as a transmitting module. That is, transceiver 830 includes a receiver and a transmitter. A transceiver may also be called a transceiver unit, transceiver module, or transceiver circuit, etc. A receiver may also be called a receiver unit, receiving module, or receiving circuit, etc. A transmitter may also be called a transmitter, transmitter module, or transmitting circuit, etc.
[0290] As one option, the device 800 is used to implement the operations performed by the communication device in the various method embodiments described above.
[0291] For example, processor 810 is used to execute computer programs or instructions stored in memory 820 to implement the relevant operations of the communication device in the various method embodiments above.
[0292] Referring to Figure 9, as an example, Figure 9 is a schematic block diagram of a communication device 900 provided in an embodiment of this application. The communication device 900 includes logic circuitry 910 and an input / output interface 920.
[0293] The logic circuit 910 can be a processing circuit in the communication device 900. The logic circuit 910 can be coupled to a memory unit, calling instructions from the memory unit, enabling the communication device 900 to implement the methods and functions of the embodiments of this application. The input / output interface 920 can be an input / output circuit in the communication device 900, outputting processed information or inputting data or signaling information to be processed into the communication device 900 for processing.
[0294] As one approach, the chip system 900 is used to implement the operations performed by the communication device in the various method embodiments described above.
[0295] For example, logic circuit 910 is used to implement processing-related operations performed by the communication device in the above method embodiments; input / output interface 920 is used to implement sending and / or receiving-related operations performed by the communication device in the above method embodiments.
[0296] This application also provides a computer-readable storage medium storing a computer program or instructions for implementing the methods executed by the communication device in the above-described method embodiments. For example, when the computer program or instructions are run on the communication device, the communication device causes the communication device to execute the above-described methods (such as method 400).
[0297] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods performed by the communication device in the above-described method embodiments. For example, when the computer program or instructions are run on the communication device, the communication device performs the above-described methods (such as method 400).
[0298] The explanations and beneficial effects of the relevant content in any of the devices provided above can be referred to the corresponding method embodiments provided above, and will not be repeated here. In the implementation process, each step of the above method can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the method in conjunction with the embodiments of this application can be directly manifested as being executed by the hardware processor, or being executed by a combination of hardware and software modules in the processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.
[0299] It should be understood that the aforementioned communication device can be one or more chips. For example, the communication device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-a-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.
[0300] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.
[0301] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as execution by a hardware decoding processor, or as execution by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.
[0302] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0303] In addition, this application also provides a computer-readable storage medium storing computer instructions, which, when executed on a computer, cause the operations and / or processes performed by the receiving device or the sending device in the various method embodiments of this application to be executed.
[0304] This application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processes performed by the receiving end device or the sending end device in the various method embodiments of this application are executed.
[0305] Furthermore, this application also provides a chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory, such that operations and / or processes performed by a receiving device or a transmitting device in any method embodiment are performed.
[0306] Furthermore, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Furthermore, the chip may also include a memory.
[0307] In addition, this application also provides a communication system, including the transmitting end device and the receiving end device in the embodiments of this application.
[0308] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0309] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0310] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0311] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / mcc> < / mnc> < / username> < / mcc> < / mnc> < / username> < / mcc> < / mnc> < / username> < / networktypex> < / mcc> < / mnc> < / username> < / networktypey> < / mcc> < / mnc> < / username> < / networktypey> < / mcc> < / mnc> < / username> < / networktypey> < / mcc> < / mnc> < / username> < / networktypey> < / mcc> < / mnc> < / username> < / networktype0> < / mcc> < / mnc> < / username> < / networktypey> < / mcc> < / mnc> < / username> < / networktypey>
Claims
1. A communication method, characterized in that, Applied to a gateway device, the method includes: Receive a first request information from a terminal device, the first request information being used to indicate that the terminal device requests access to the core network through a non-3GPP network, the first request information including a first identifier, the first identifier being associated with the type of the core network that the terminal device requests to access; A second request message is sent to the first authentication network element, wherein the second request message is used to request the first authentication network element to authenticate the terminal device. The first authentication network element is the authentication network element associated with the first identifier among at least two authentication network elements, wherein the at least two authentication network elements correspond one-to-one with at least two core network types, and / or, The second request information includes a second identifier, and the first authentication network element is used for authentication processing of at least two types of core networks, the at least two types including the type associated with the first identifier, and the second identifier is used to indicate the core network type associated with the first identifier.
2. The method according to claim 1, characterized in that, When the core network type requested by the terminal device is Evolved Packet Core (EPC), the first identifier is in an unencrypted format. When the core network type requested by the terminal device is 5G core network 5GC, the first identifier is in an encrypted format.
3. The method according to claim 2, characterized in that, When the core network type requested by the terminal device is Evolved Packet Core (EPC), the second identifier is in an unencrypted format. When the core network type requested by the terminal device is 5G core network 5GC, the second identifier is in an encrypted format.
4. The method according to claim 3, characterized in that, The first request information also includes the authentication information of the terminal device, which is used in the authentication process of the terminal device.
5. The method according to claim 4, characterized in that, The second request information also includes the authentication information of the terminal device.
6. A communication method, characterized in that, Applied to authentication network elements, the method includes: The system receives a second request message from a gateway device, wherein the second request message is used to request authentication of a terminal device, the terminal device accessing the core network through a non-3GPP network, the authentication network element is used for authentication processing of at least two types of core networks, the second request message includes a second identifier, the second identifier is used to indicate the type of core network that the terminal device requests to access, and the at least two types include the type associated with the second identifier; The terminal device is authenticated based on the second request information.
7. The method according to claim 6, characterized in that, The method further includes: A third request message is sent to the first data management network element. The third request message is used to request the first data management network element to authenticate the terminal device. The third request message includes a third identifier, which is used to indicate the type of core network that the terminal device requests to access. The first data management network element is a data management network element associated with the second identifier among at least two data management network elements, wherein the at least two data management network elements correspond one-to-one with at least two core network types, and / or, The first data management network element is used for authentication processes of at least two types of core networks, and the third identifier is used to indicate the core network type associated with the second identifier; The system receives an authentication vector sent by the first data management network element, the authentication vector being used to authenticate the terminal device.
8. The method according to claim 7, characterized in that, When the core network type requested by the terminal device is Evolved Packet Core (EPC), the second identifier is in an unencrypted format. When the core network type requested by the terminal device is 5G core network 5GC, the second identifier is in an encrypted format.
9. The method according to claim 8, characterized in that, When the core network type requested by the terminal device is Evolved Packet Core (EPC), the third identifier is in an unencrypted format; When the core network type requested by the terminal device is 5G core network 5GC, the third identifier is in an encrypted format.
10. The method according to claim 9, characterized in that, The second request information also includes the authentication information of the terminal device, which is used in the authentication process of the terminal device.
11. The method according to claim 10, characterized in that, The third request information also includes the authentication information of the terminal device, which is used in the authentication process of the terminal device.
12. A communication method, characterized in that, The method includes: Send a first request message to the gateway device. The first request message is used to instruct the terminal device to request access to the core network through a non-3GPP network. The first request message includes a first identifier, which is associated with the type of core network that the terminal device requests to access.
13. The method according to claim 12, characterized in that, When the core network type requested by the terminal device is Evolved Packet Core (EPC), the first identifier is in an unencrypted format. When the core network type requested by the terminal device is 5G core network 5GC, the first identifier is in an encrypted format.
14. The method according to claim 13, characterized in that, The first request information also includes the authentication information of the terminal device, which is used in the authentication process of the terminal device.
15. A communication method, characterized in that, Applied to data management network elements, the method includes: The authentication network element receives a third request message sent by the authentication network element. The third request message is used for the authentication process of the terminal device. The terminal device accesses the core network through a non-3GPP network. The data management network element is used for the authentication process of at least two types of core networks. The third request message includes a third identifier, which is used to indicate the type of core network that the terminal device requests to access. The at least two types include the type associated with the third identifier. An authentication vector is generated based on the third request information, and the authentication vector is used to authenticate the terminal device. The authentication vector is sent to the authentication network element.
16. The method according to claim 15, characterized in that, When the core network type requested by the terminal device is Evolved Packet Core (EPC), the third identifier is in an unencrypted format; When the core network type requested by the terminal device is 5G core network 5GC, the third identifier is in an encrypted format.
17. The method according to claim 16, characterized in that, The third request information also includes the authentication information of the terminal device, which is used in the authentication process of the terminal device.
18. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 1 to 17.
19. A communication device, characterized in that, Includes a processor for executing computer programs or instructions to cause the apparatus to perform the method of any one of claims 1 to 17.
20. The apparatus according to claim 19, characterized in that, The device further includes a memory and / or a communication interface; The communication interface is coupled to the processor, and the communication interface is used for inputting and / or outputting information; The memory is used to store the computer program or instructions.
21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 17.
22. A computer program product, characterized in that, The computer program product includes a computer program or instructions for performing the method as described in any one of claims 1 to 17.
