Wireless communication methods and communication devices

Abstract

Provided are wireless communication methods and communication devices. A method comprises: a first device receiving first information, wherein the first information is used for indicating whether a first terminal device supports a first-type algorithm, which is a 256-bit encryption algorithm; and the first device determining a first algorithm on the basis of the first information, wherein the first algorithm is an encryption algorithm used between the first device and the first terminal device. In the present application, the first device can determine, on the basis of the first information, whether the first terminal device supports the 256-bit encryption algorithm. On this basis, the first device can realize encryption algorithm negotiation with the first terminal device, facilitating parallel support of different encryption algorithm strengths by a communication system.

Description

Wireless communication method and communication device Technical Field

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

[0002] In wireless communication systems, to combat quantum attacks, 256-bit encryption algorithms may be used for symmetric encryption between communicating devices. Consequently, different devices may support encryption algorithms of varying strengths. The challenge of how these devices negotiate these algorithms remains unresolved.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and a communication device. The following introduces various aspects involved in the present application.

[0005] In a first aspect, a wireless communication method is provided, including: a first device receives first information, the first information being used to indicate whether a first terminal device supports a first type of algorithm, the first type of algorithm being a 256-bit encryption algorithm; the first device determines a first algorithm based on the first information, the first algorithm being an encryption algorithm used between the first device and the first terminal device.

[0006] According to a second aspect, a wireless communication method is provided, including: a first terminal device receives a first message sent by a first device, the first message including indication information of a first algorithm, the first algorithm being an encryption algorithm used between the first device and the first terminal device; wherein the first algorithm is determined based on the first information, the first information is used to indicate whether the first terminal device supports a first type of algorithm, and the first type of algorithm is a 256-bit encryption algorithm.

[0007] According to a third aspect, a communication device is provided, which is a first device, and includes: a receiving module for receiving first information, wherein the first information is used to indicate whether the first terminal device supports a first type of algorithm, and the first type of algorithm is a 256-bit encryption algorithm; and a determination module for determining a first algorithm based on the first information, and the first algorithm is an encryption algorithm used between the first device and the first terminal device.

[0008] In a fourth aspect, a communication device is provided, which is a first terminal device, and the communication device includes: a receiving module for receiving a first message sent by a first device, the first message including indication information of a first algorithm, and the first algorithm is an encryption algorithm used between the first device and the first terminal device; wherein the first algorithm is determined based on the first information, and the first information is used to indicate whether the first terminal device supports a first type of algorithm, and the first type of algorithm is a 256-bit encryption algorithm.

[0009] In a fifth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method described in the first aspect.

[0010] In a sixth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the network device executes the method described in the second aspect.

[0011] In a seventh aspect, a device is provided, comprising a processor for calling a program from a memory so that the device executes the method as described in the first aspect or the second aspect.

[0012] In an eighth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect or the second aspect.

[0013] In a ninth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0014] In a tenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0015] In an eleventh aspect, a computer program is provided, wherein the computer program enables a computer to execute the method as described in the first aspect or the second aspect.

[0016] In this application, the first device can determine whether the first terminal device supports a 256-bit encryption algorithm based on the first information. Based on this, the first device can implement encryption algorithm negotiation with the first terminal device, which helps the communication system achieve parallel support of different encryption algorithm strengths. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a schematic structural diagram of a wireless communication system to which an embodiment of the present application is applicable.

[0018] FIG2 is a schematic flowchart of the key generation process in the 5G security key architecture.

[0019] FIG3 is a schematic flow chart of the NAS security mode command process.

[0020] FIG4 is a schematic flow chart of the AS security mode command process.

[0021] FIG5 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application.

[0022] 6A-6B are schematic flow charts of a wireless communication method provided in another embodiment of the present application.

[0023] FIG7 is a schematic flowchart of a wireless communication method provided in Embodiment 1 of the present application.

[0024] FIG8 is a schematic flowchart of a wireless communication method provided in Embodiment 3 of the present application.

[0025] 9A-9B are schematic flow charts of a wireless communication method provided in Embodiment 5 of the present application.

[0026] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0027] FIG11 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0028] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The technical solution in this application will be described below with reference to the accompanying drawings.

[0030] Communication system architecture

[0031] Figure 1 is a schematic diagram of a communication system architecture applicable to an embodiment of the present application. The network architecture may include terminal equipment, access network (AN) network elements, and core network network elements.

[0032] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: sixth generation (6G) communication systems, fifth generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as sixth generation mobile communication systems, satellite communication systems, and the like.

[0033] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity that provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0034] An access network element can be an access network device. This device is used by terminals to wirelessly access the network architecture and is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. An access network device can also be referred to as a radio access network (RAN) device. For example, an access network device can be a base station. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the access network device.

[0035] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0036] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device may include a CU and a DU. The gNB may also include an AAU.

[0037] The types of core network elements may include user plane function (UPF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, application function (AF), data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management function (UDM), network exposure function (NEF), network repository function (NRF), and network slice-specific authentication and authorization function (NSSAAF). In addition, some networks (such as 5G networks) have added a network data analytics function (NWDAF) to the core network. NWDAF can be further divided into analytics logical function (AnLF) and model training logical function (MTLF). In some communication systems (such as 5G systems), core network elements may also be referred to as network functions (NFs).

[0038] The network elements in Figure 1 can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions implemented on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0039] Those skilled in the art will appreciate that the network architecture shown in FIG1 does not limit the network architecture. In a specific implementation, the network architecture may include more or fewer network elements than shown, or may combine certain network elements. It should be understood that in FIG1 , the AN or RAN is represented by (R)AN.

[0040] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which network devices and terminal devices are located.

[0041] Symmetric encryption algorithm (ciphering algorithm) and key architecture

[0042] Symmetric encryption algorithms used in 5G security include 128-NEA1, 128-NEA2, and 128-NEA-3. These three symmetric encryption algorithms correspond to Snow 3G, the Advanced Encryption Standard (AES), and the Zu Chongzhi (ZUC) algorithm, respectively. Details of these three symmetric encryption algorithms are shown in Table 1. The fourth generation (4G) also uses these three symmetric encryption algorithms, named 128-EEA1, 128-EEA2, and 128-EEA3.

[0043] Table 1 Symmetric encryption algorithm table

[0044] In the 5G security key architecture, the length of the generated key can be shown in Figure 2. As shown in Figure 2, the length of the key used to protect the session (i.e., to protect the security of the NAS and AS layers) is 128 bits.

[0045] NAS algorithm negotiation

[0046] Each AMF can configure a list of algorithms allowed to be used through network management, namely a list of NAS integrity algorithms and a list of NAS encryption algorithms, which should be sorted according to the priority determined by the operator. In order to establish a NAS security context, the AMF can select a NAS encryption algorithm and a NAS integrity protection algorithm. The AMF can then initiate the NAS security mode command process and include the selected algorithm and UE security capabilities in the message sent to the UE (to detect attackers modifying the UE security capabilities). The AMF can select the NAS algorithm with the highest priority based on the list sorting.

[0047] The NAS security mode command process can be shown in Figure 3, including steps S310 to S360. In step S310, the AMF enables integrity protection. The AMF can select the corresponding security algorithm (encryption algorithm and integrity algorithm) to enable integrity protection based on the UE security capabilities and the locally configured algorithm list. In step S320, the AMF sends a NAS security mode command (SMC) message to the UE. The NAS SMC may include the algorithm selected by the AMF and the UE security capabilities, as well as a NAS key change indication (e.g., K_AMF_change_flag), a NAS key set identifier (ngKSI), an Anti-Bidding down Between Architectures (ABBA) parameter, a request initial NAS message flag, a NAS message authentication code (MAC), etc.

[0048] In step S330, the UE can verify the integrity of the NAS SMC message, and if successful, it can enable uplink encryption, downlink decryption and integrity protection. The UE can verify the integrity of the NAS SMC message to confirm that the message has not been tampered with, and then confirm that it has not been subjected to a price reduction attack by checking the UE security capabilities returned by the AMF. After the UE verification is successful, the encryption and integrity protection of the NAS layer can be enabled using the algorithm selected by the AMF. In step S340, the AMF can enable uplink decryption. In step S350, the UE can send a NAS security mode complete message to the AMF, which may include a complete initial NAS message in the NAS container and a NAS MAC, etc. In step S360, the AMF enables downlink encryption.

[0049] If a change of AMF occurs, such as an N2 handover or a mobile registration update, the source AMF may send the UE security capabilities to the target AMF, which may then send the selected algorithms to the UE. In the case of an N2 handover, the target AMF may send this information to the UE via the source AMF using a NAS container. In the case of a mobile registration update, the target AMF may use a NAS SMC procedure to activate the selected algorithms between the target AMF and the UE.

[0050] AS algorithm negotiation

[0051] Each gNB / ng-eNB can be configured through network management with a list of allowed algorithms: an integrity algorithm list and a cipher algorithm list. These lists can be ordered according to operator-determined priorities. When establishing an AS security context between a gNB / ng-eNB and a UE, the AMF can send the UE's 5G security capabilities to the gNB / ng-eNB. The gNB / ng-eNB selects the algorithm with the highest priority from its configured list that is also present in the UE's 5G security capabilities. The selected algorithm can be indicated to the UE during the AS SMC procedure. The selected cipher algorithm can be used for ciphering user plane data and radio resource control (RRC) signaling. The selected integrity algorithm can be used for integrity protection of user plane data and RRC signaling.

[0052] The AS security mode command process may be as shown in Figure 4, including steps S410 to S470. In step S410, the gNB or ng-eNB enables RRC integrity protection. The gNB or ng-eNB may select the corresponding RRC and user plane (UP) protection security algorithms based on the UE security capabilities and the locally configured algorithm list to enable RRC integrity protection. In step S420, the gNB or ng-eNB may send an AS SMC message to the UE. The AS SMC message may include the algorithm selected by the gNB or ng-eNB, the UE security capabilities, and message authentication code-integrity (MAC-I) information. In step S430, the gNB or ng-eNB may enable RRC downlink encryption. In step S440, the UE verifies the integrity of the AS SMC message and, if successful, enables RRC integrity protection and RRC downlink decryption. The UE can verify the integrity of the message using the MAC-I to confirm that it has not been tampered with. It can also verify that it has not been subjected to a price reduction attack by checking the UE security capabilities returned by the gNB or ng-eNB. After successful verification, the UE can enable RRC layer encryption and integrity protection, as well as downlink decryption, using the algorithm selected by the gNB or ng-eNB. In step S450, the UE can send an AS SMC message to the gNB or ng-eNB, which may include the MAC-I. In step S460, the UE can enable RRC uplink encryption. In step S470, the gNB or ng-eNB can enable RRC uplink decryption.

[0053] For the Xn handover process, the UE switches from the source base station to the target base station. The source base station can send the UE's security capabilities and the security algorithm used by the source cell to the target base station. The target base station can select an algorithm based on the UE security capabilities and the locally configured algorithm list. If a different algorithm is selected, the target base station can carry the selected algorithm in the handover command message sent by the source base station to the UE. When switching between a 4G base station and a 5G base station, the algorithm selected by the target base station must be carried. The target base station must send the UE security capabilities to the AMF for AMF verification. If it is inconsistent with the locally stored UE security capabilities, the path switch acknowledgement message sent by the AMF to the target base station carries the UE security capabilities. After the target base station reselects the algorithm, it uses intra-cell handover and UE update algorithms.

[0054] For N2 handover, the source AMF may send the UE's security capabilities to the target AMF, and the target AMF may send an NGAP HANDOVER REQUEST message to the target base station, which includes the UE's security capabilities. The source base station may send a source to target transparent container to the target base station, which includes the algorithm used by the source cell. The target base station may select an algorithm based on the UE's security capabilities and the locally configured algorithm list. If a different algorithm is selected, the target base station shall carry the selected algorithm in the handover command message sent to the UE.

[0055] Quantum-safe algorithms

[0056] A quantum computer is a device that exploits quantum mechanical phenomena (superposition and entanglement) to perform calculations and manipulate data. The security foundation of currently popular cryptographic algorithms rests on intractable mathematical problems. Due to the inherent parallel nature of quantum computers, some quantum algorithms can solve difficult mathematical problems more efficiently than classical algorithms, posing a serious and present security threat to contemporary cryptography. An attacker could use the Grover algorithm on a quantum computer to halve the effective key size, thereby halving the security strength of symmetric key algorithms. Therefore, to achieve quantum attack resistance, the key size of symmetric key algorithms must be doubled. 128-bit symmetric key algorithms such as AES-128, SNOW 3G, and ZUC-128 are fundamental to the security of NAS signaling, RRC signaling, and UP data. To mitigate quantum attacks, the introduction of 256-bit symmetric key algorithms into the system is a viable option. Whether a longer MAC is necessary requires further study.

[0057] As mentioned above, the encryption algorithms used in NAS signaling, RRC signaling, and user data in 4G and 5G systems are all 128-bit symmetric algorithms. As the algorithm capabilities of terminals, radio access network equipment (e.g., gNBs and ng-eNBs), and core network equipment (e.g., AMFs) increase, these communication entities may gradually enhance their algorithm capabilities to support 256-bit algorithms to mitigate quantum attacks. For example, 6G communication systems deploy communication entities supporting high-strength algorithms. Therefore, the communication system inevitably contains entities supporting different encryption algorithm strengths. Therefore, it is necessary to design algorithm negotiation methods between these entities to enable the phased introduction and parallel support of 128-bit and 256-bit encryption algorithms.

[0058] Based on this, the method of an embodiment of the present application is described in detail below. In this application, the first device can determine whether the first terminal device supports a 256-bit encryption algorithm based on the first information. Based on this, the first device can implement encryption algorithm negotiation with the first terminal device, which helps the communication system achieve parallel support of different encryption algorithm strengths.

[0059] As shown in Figure 5, an embodiment of the present application provides a wireless communication method that can be performed by a first device and a first terminal device. The first device can be the access network device described above, such as a gNB. The first device can also be the core network element (or "core network device") described above, such as an AMF. The first terminal device can be any of the terminal devices described above, and the first terminal device can establish a connection with the first device.

[0060] The method shown in Figure 5 may include steps S510 to S520. In step S510, the first device receives first information. The first information can be used to indicate whether the first terminal device supports a first type of algorithm, which is a 256-bit encryption algorithm. That is, the first device can determine whether the first terminal device supports a 256-bit algorithm based on the first information. In step S520, the first device can determine a first algorithm based on the first information, which is an encryption algorithm used between the first device and the first terminal device. That is, the first device can determine the encryption algorithm between the first terminal device and the first terminal device based on whether the first terminal device supports a 256-bit algorithm to achieve algorithm negotiation. It is worth noting that the 256-bit algorithm in the embodiment of the present application may refer to a Snow 3G 256-based algorithm, an AES 256-based algorithm, or a ZUC 256-based algorithm. The encryption in the embodiment of the present application may refer to authenticated encryption, and the 256-bit algorithm in the embodiment of the present application may be used for authenticated encryption. Authenticated encryption is a combined algorithm that can perform encryption and / or integrity protection in a single process. Authenticated encryption can perform encryption and / or integrity protection accordingly based on the input of the algorithm.

[0061] The first information is described in detail below. The first information may include one or more of the following: one or more first identifiers; first indication information; and second indication information.

[0062] As an example, if the first terminal device supports a first type of algorithm, the first information may include one or more first identifiers, and the one or more first identifiers may be used to indicate one or more first type of algorithms supported by the first terminal device. If the first terminal device supports a 256-bit encryption algorithm, the first information may include a first identifier to indicate the 256 algorithm supported by the first terminal device. If the first terminal device does not support a 256-bit encryption algorithm, the first information may not include the first identifier. That is, one or more first identifiers may constitute a list of 256-bit algorithms supported by the first terminal device, and the first information may include the algorithm list. Among them, the first identifier may be an algorithm identifier. For example, identifier 256-NEA1 can be used to represent the snow 5G 256bits algorithm, identifier 256-NEA2 can be used to represent the AES256bits algorithm, and identifier 256-NEA3 can be used to represent the ZUC 256bits algorithm. Based on the first identifier, it helps the first device to clarify the 256-bit encryption algorithm supported by the first terminal device.

[0063] As another example, the first information may include first indication information, and the first indication information may be used to indicate whether the first terminal device supports the first type of algorithm. In the present application, the form of the first indication information may not be limited. For example, the first indication information may occupy one bit. When the value of the first indication information is the first value, it may indicate that the first terminal device supports the 256-bit encryption algorithm. When the value of the first indication information is the second value, it may indicate that the first terminal device does not support the 256-bit encryption algorithm. Alternatively, when the first information includes this bit, it may indicate that the first terminal device supports the 256-bit encryption algorithm. When the first information does not include this bit, it may indicate that the first terminal device does not support the 256-bit encryption algorithm. Based on the first indication information, it helps the first device to quickly determine whether the first terminal device supports the 256-bit encryption algorithm.

[0064] As another example, if the first terminal device supports a first type of algorithm, the first information may include second indication information, which may be used to indicate the use of the first type of algorithm as the first algorithm. That is, if the first terminal device supports a 256-bit encryption algorithm, the first information may include second indication information to instruct the first device to use the 256-bit encryption algorithm as the encryption algorithm between the first device and the first terminal device. In this application, the form of the second indication information is not limited. For example, the second indication information may occupy one bit. When the value of the second indication information is the first value, it may indicate that the 256-bit encryption algorithm is used as the encryption algorithm between the first device and the first terminal device. When the value of the second indication information is the second value, it may indicate that the 256-bit encryption algorithm is not used as the encryption algorithm between the first device and the first terminal device. Alternatively, when the first information includes this bit, it may indicate that the 256-bit encryption algorithm is used as the encryption algorithm between the first device and the first terminal device. When the first information does not include this bit, it may indicate that the 256-bit encryption algorithm is not used as the encryption algorithm between the first device and the first terminal device. Based on the second indication information, the first device is helped to determine the first algorithm more efficiently.

[0065] It is worth noting that the first information may also include multiple types of the above information, which will not be described in detail here.

[0066] In some implementations, the first information may further include third indication information, which may be used to indicate that the first type of algorithm is used to perform encryption and / or integrity protection. If the first type of algorithm is used to perform encryption, it indicates that the first type of algorithm can be used to perform the encryption behavior in the authenticated encryption described above. If the first type of algorithm is used to perform integrity protection, it indicates that the first type of algorithm can be used to perform the integrity protection behavior in the authenticated encryption described above. Furthermore, the third indication information may be carried in the first indication information or the second indication information.

[0067] The first information can be carried in the first capability information, and the first capability information can be used to indicate the security capabilities of the first terminal device. That is, the first capability information can be the security capability information of the first terminal device, and the first device can determine whether the first terminal device supports 256-bit encryption algorithms based on the security capability information of the first terminal device. The first capability information can be sent by the first terminal device to the first device, or the first capability information can be sent by a core network device (such as an AMF) to the first device, or the first capability information can be sent by another first device to the first device. For example, when the first terminal device initially accesses the first device, the first terminal device can report its own security capability information to the first device. For another example, when the first terminal device initially accesses the first device, the core network device can also send the security capability information of the first terminal device to the first device (in this case, the first device is an access network device). For another example, when the first terminal device changes during the connection with the first device due to handover or mobile registration update, the source first device can send the security capability information of the first terminal device to the target first device. Based on the first capability information, the first device can determine the encryption algorithm used between the first device and the first terminal device.

[0068] The following describes in detail how the first device determines the first algorithm. Exemplarily, the first device may determine the first algorithm based on the first information in different scenarios. In one scenario, if the first terminal device supports a first-type algorithm and the first device also supports the first-type algorithm, the first device may prioritize the first-type algorithm as the first algorithm. That is, if both the first terminal device and the first device support a 256-bit encryption algorithm, the first device prioritizes the 256-bit encryption algorithm as the encryption algorithm used between them. In another scenario, if the first terminal device supports the first-type algorithm but the first device does not, the first device may prioritize the second-type algorithm as the first algorithm, where the second-type algorithm is a 128-bit encryption algorithm. That is, if the first terminal device supports a 256-bit encryption algorithm but the first device does not support a 256-bit encryption algorithm, the first device may prioritize the 128-bit encryption algorithm as the encryption algorithm used between them. In another scenario, if the first terminal device does not support the first-type algorithm, the first device may prioritize the second-type algorithm as the first algorithm. That is, when the first terminal device does not support a 256-bit encryption algorithm, the first device can select a 128-bit encryption algorithm as the encryption algorithm used between the two. Based on this, it is helpful to achieve coordination of the encryption algorithms between the first terminal device and the first device.

[0069] Furthermore, an example is given of how the first device uses the first algorithm. As an example, the first device is a core network device. If the core network device determines to use the first type of algorithm based on the first information, the core network device can directly use a 256-bit key for NAS encryption (which can be authenticated encryption). If the core network device determines to use the second type of algorithm based on the first information, the core network device can use the Trunc function (i.e., truncation method) on the generated 256-bit key KNASenc to generate a 128-bit key for NAS encryption (which can be authenticated encryption). As another example, the first device is an access network device. When the access network device determines to use the first type of algorithm based on the first information, the access network device can directly use a 256-bit key for AS encryption (which can be authenticated encryption). When the access network device determines to use the second type of algorithm based on the first information, the access network device can use the Trunc function on the keys KRRCenc and KUPenc to generate 128-bit keys, respectively, for protecting the RRC layer and the UP (user) plane (which can be authenticated encryption).

[0070] In some implementations, after the first device determines the first algorithm based on the first information, it can send a first message to the first terminal device, where the first message includes indication information that may include the first algorithm. That is, after the first device determines the first algorithm based on the first information, it can indicate the first algorithm to the first terminal device, which helps to implement encryption algorithm negotiation between the device and the first terminal device. After the first terminal device determines the first algorithm based on the first message, the use of the first algorithm can be as follows. If the first terminal device determines to use the first type of algorithm based on the first message, the first terminal device can directly use a 256-bit key for encryption with the first device (which can be authenticated encryption). If the first terminal device determines to use the second type of algorithm based on the first message, the first terminal device can use the Trunc function (i.e., truncation method) on the generated 256-bit key KNASenc to generate a 128-bit key for encryption with the first device (which can be authenticated encryption).

[0071] In some implementations, as shown in FIG6A , the wireless communication method of the embodiment of the present application may further include step S630. In step S630, the first device sends second information to the second device, and the second information may be used to indicate a second algorithm. The second algorithm may be an encryption algorithm used between the second device and the first terminal device, and the second algorithm may be determined by the first device based on the first information. That is, the first device may negotiate the encryption algorithm used between the second device and the first terminal device based on the first information. For example, in a dual-connection scenario, the first device may be a master node (MN) (also known as a primary base station), and the second device may be a secondary node (SN) (also known as a secondary base station). When the SN is switched, the MN may negotiate the encryption algorithm used between the SN and the terminal device based on the first information. Based on this, it is helpful to achieve coordination of the encryption algorithms between the first terminal device and the second device.

[0072] In some other implementations, as shown in FIG6B , the wireless communication method of the embodiment of the present application may further include step S630. In step S630, the first device sends first information to the second device, and the first information can be used by the second device to determine a second algorithm, and the second algorithm can be an encryption algorithm between the second device and the first terminal device. That is, the first device can send the first information to the second device to help the second device determine the encryption algorithm between the second device and the first terminal device. For example, in a dual-connection scenario, the first device may be an MN, and the second device may be an SN. When the SN switches, the MN may send the first information to the SN so that the SN can negotiate the encryption algorithm used between the SN and the terminal device. Based on this, it helps to achieve coordination of the encryption algorithms between the first terminal device and the second device.

[0073] The wireless communication method of the embodiments of the present application is described in detail below in conjunction with Examples 1 to 5. Among them, Example 1 and Example 2 take the first device being the core network device AMF as an example, and Example 3 to Example 5 take the first device being the access network device gNB / ng-eNB as an example. Exemplarily, the first information in each of the following embodiments is carried by the UE security capability. The UE security capability may include a 256-bit algorithm identifier supported by the UE (i.e., one or more first identifiers) / an indication of the UE supporting a 256-bit algorithm (i.e., the first indication information) / an indication of using a 256-bit algorithm (i.e., the second indication information).

[0074] Example 1

[0075] Referring to Figure 7 , in Embodiment 1, algorithm negotiation is performed between the UE and the AMF during the initial access process. In step S710, the UE sends an NAS message to the AMF. The NAS message may include the UE's security capabilities, which may include identifiers of 256-bit algorithms supported by the UE or an indication that the UE supports 256-bit algorithms. In step S720, the AMF enables integrity protection. Based on the UE's security capabilities and the locally configured algorithm list, the AMF selects the corresponding security algorithms (encryption and integrity algorithms) to enable integrity protection. It is worth noting that in the AMF's locally configured algorithm list that supports 256-bit algorithms, supported 256-bit algorithms have a higher priority than supported 128-bit algorithms. If the AMF also supports the 256-bit algorithm, the AMF may prioritize the 256-bit algorithm. If the AMF does not support the 256-bit algorithm, the AMF may select the 128-bit algorithm. In step S730, the AMF sends a NAS SMC message to the UE. The NAS SMC message may include the algorithm selected by the AMF and the UE's security capabilities. The remaining steps are the same as the NAS algorithm negotiation process shown in FIG3 and are not described again here.

[0076] Example 2

[0077] In embodiment 2, algorithm negotiation is performed between the UE and the AMF in a handover or mobile registration update scenario. In a handover or mobile registration update scenario, the AMF serving the UE changes. When the UE switches from the source AMF to the target AMF, the source AMF may send the UE security capabilities to the target AMF, which may include a 256-bit algorithm identifier supported by the UE or an indication that the UE supports a 256-bit algorithm. Alternatively, the UE may send a NAS message containing the UE security capabilities to the target AMF, which may include a 256-bit algorithm identifier supported by the UE or an indication that the UE supports a 256-bit algorithm or an indication that a 256-bit algorithm is used between the AMF and the UE. The AMF may select the corresponding security algorithm (encryption algorithm and integrity algorithm) to enable integrity protection based on the UE security capabilities and the locally configured algorithm list. The remaining steps will not be repeated here.

[0078] When the communication system requires NAS security protection to use a 256-bit algorithm and a core network device with 256-bit capability is deployed, based on Embodiment 1 and Embodiment 2, algorithm negotiation can be achieved between the UE and the core network device, which facilitates the phased introduction and parallel support of 128-bit and 256-bit encryption algorithms.

[0079] Example 3

[0080] Referring to Figure 8 , in Example 3, algorithm negotiation is performed between the UE and the gNB / ng-eNB during the initial access process. In step S810, the gNB / ng-eNB obtains the UE's security capabilities, which may include identifiers of 256-bit algorithms supported by the UE or an indication that the UE supports 256-bit algorithms. The gNB / ng-eNB obtains the UE's security capabilities through UE reporting or AMF transmission. In step S820, the gNB / ng-eNB enables integrity protection. The gNB / ng-eNB may select the corresponding security algorithm for RRC and UP protection based on the UE's security capabilities and the locally configured algorithm list. Note that, in the locally configured algorithm list for a gNB / ng-eNB that supports 256-bit algorithms, supported 256-bit algorithms have higher priority than supported 128-bit algorithms. If the gNB / ng-eNB also supports 256-bit algorithms, the gNB / ng-eNB may prioritize the 256-bit algorithms. If the gNB / ng-eNB does not support the 256-bit algorithm, it may select a 128-bit algorithm. In step S830, the gNB / ng-eNB sends an AS SMC message to the UE. The AS SMC message may include the algorithm selected by the gNB / ng-eNB and the UE's security capabilities. The remaining steps are identical to the AS algorithm negotiation process shown in Figure 4 and are not further described here.

[0081] Example 4

[0082] In the fourth embodiment, algorithm negotiation is performed between the UE and the gNB / ng-eNB in ​​an Xn handover or N2 handover scenario. In an Xn handover or N2 handover scenario, the gNB / ng-eNB serving the UE changes. When the UE switches from a source base station to a target base station, the source base station may send the target base station the UE's security capabilities and the security algorithm used by the source cell. The UE's security capabilities may include a 256-bit algorithm identifier supported by the UE or an indication that the UE supports 256-bit algorithms. The target base station may select an algorithm based on the UE's security capabilities and a locally configured algorithm list. Note that in the locally configured algorithm list for a gNB / ng-eNB that supports 256-bit algorithms, supported 256-bit algorithms have higher priority than supported 128-bit algorithms. If the gNB / ng-eNB also supports the 256-bit algorithm, the gNB / ng-eNB may prioritize the 256-bit algorithm. If the gNB / ng-eNB does not support the 256-bit algorithm, the gNB / ng-eNB may select the 128-bit algorithm.

[0083] If the target base station selects a different algorithm, for example, in a system interoperability scenario, a UE supporting the 256-bit algorithm switches from a base station with a low algorithm strength to a base station with a high algorithm strength, the target base station can carry the selected 256-bit algorithm in the handover command message sent to the UE by the source base station.

[0084] The target base station needs to send the UE security capabilities to the AMF for AMF verification. If they are inconsistent with the locally stored UE security capabilities, the AMF carries the UE security capabilities in the path switch acknowledge message sent to the target base station. After the target base station reselects the algorithm, it uses the intra-cell switching and UE update algorithm.

[0085] Example 5

[0086] In the fifth embodiment, algorithm negotiation is performed in a dual-connectivity handover scenario between a UE and a gNB / ng-eNB. In a dual-connectivity scenario, there is a primary base station (MN) and a secondary base station (SN). Possible base station handover scenarios include: 1. MN handover with unchanged SN; 2. MN handover with SN handover; and 3. MN handover with unchanged SN handover. When a MN handover occurs, the algorithm negotiation between the MN and the UE is the same as in the third embodiment.

[0087] When the MN remains unchanged but the SN switches, as shown in Figure 9A , the MN can send the UE's security capabilities to the target SN for algorithm negotiation between the UE and the SN. Alternatively, as shown in Figure 9B , the MN can negotiate a security algorithm between the UE and the SN based on the list of algorithms supported by the SN sent by the local / SN and the UE's security capabilities. The UE's security capabilities can include a 256-bit identifier of the algorithms supported by the UE, or an indication that the UE supports a 256-bit algorithm.

[0088] When the communication system requires the use of a 256-bit algorithm for AS security protection and an access network device with 256-bit capabilities is deployed, based on Examples 3 to 5, algorithm negotiation can be achieved between the UE and the access network device, which facilitates the phased introduction and parallel support of 128-bit and 256-bit encryption algorithms.

[0089] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 9 . The device embodiment of the present application is described in detail below in conjunction with Figures 10 to 12 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0090] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1000 shown in Figure 10 is a first device. Communication device 1000 may include a receiving module 1010 and a determining module 1020. Receiving module 1010 may be configured to receive first information, which may indicate whether a first terminal device supports a first type of algorithm, which may be a 256-bit encryption algorithm. Determining module 1020 may be configured to determine a first algorithm based on the first information, which may be an encryption algorithm used between the first device and the first terminal device.

[0091] In some implementations, if the first terminal device supports the first type of algorithm, the first information may include one or more first identifiers, and the one or more first identifiers may be used to indicate the one or more first type of algorithms supported by the first terminal device.

[0092] In some implementations, the first information may include first indication information, and the first indication information may be used to indicate whether the first terminal device supports the first type of algorithm.

[0093] In some implementations, if the first terminal device supports the first type of algorithm, the first information may include second indication information, and the second indication information may be used to instruct the first device to use the first type of algorithm as the first algorithm.

[0094] In some implementations, the first information may be carried in first capability information, and the first capability information may be used to indicate the security capability of the first terminal device.

[0095] In some implementations, the first device determining the first algorithm based on the first information may include: if the first terminal device supports the first type of algorithm and the first device supports the first type of algorithm, the first device may preferentially select the first type of algorithm as the first algorithm; if the first terminal device supports the first type of algorithm but the first device does not support the first type of algorithm, the first device may select the second type of algorithm as the first algorithm, where the second type of algorithm is a 128-bit encryption algorithm. If the first terminal device does not support the first type of algorithm, the first device may select the second type of algorithm as the first algorithm.

[0096] In some implementations, the communication device 1000 may further include a first sending module 1030. The sending module 1030 may be configured to send second information to the second device. The second information may be configured to indicate a second algorithm. The second algorithm may be an encryption algorithm between the second device and the first terminal device. The second algorithm may be determined by the first device based on the first information.

[0097] In some implementations, the communication device 1000 may further include a second sending module 1040. The sending module 1040 may be configured to send first information to the second device, where the first information may be used by the second device to determine a second algorithm, which is an encryption algorithm between the second device and the first terminal device.

[0098] In some implementations, the first device may be an access network device.

[0099] In some implementations, the first device may be a core network device.

[0100] Figure 11 is a schematic diagram of the structure of a communication device provided in another embodiment of the present application. The communication device 1100 shown in Figure 11 is a first terminal device, and the communication device 1100 may include a receiving module 1110 and a using module 1120. The receiving module 1110 may be used to receive a first message sent by a first device, and the first message may include indication information of a first algorithm, and the first algorithm may be an encryption algorithm used between the first device and the first terminal device; the using module 1120 may be used to use the first algorithm to perform encryption with the first device; wherein the first algorithm may be determined based on the first information, and the first information may be used to indicate whether the first terminal device supports a first type of algorithm, and the first type of algorithm is a 256-bit encryption algorithm.

[0101] In some implementations, if the first terminal device supports the first type of algorithm, the first information may include one or more first identifiers, and the one or more first identifiers may be used to indicate the one or more first type of algorithms supported by the first terminal device.

[0102] In some implementations, the first information may include first indication information, and the first indication information may be used to indicate whether the first terminal device supports the first type of algorithm.

[0103] In some implementations, if the first terminal device supports the first type of algorithm, the first information may include second indication information, and the second indication information may be used to instruct the first device to use the first type of algorithm as the first algorithm.

[0104] In some implementations, if the first terminal device supports a first type of algorithm and the first device supports a first type of algorithm, the first algorithm may be an algorithm of the first type.

[0105] In some implementations, if the first terminal device supports a first type of algorithm but the first device does not support the first type of algorithm, the first algorithm may be a second type of algorithm, which is a 128-bit encryption algorithm.

[0106] In some implementations, if the first terminal device does not support the first type of algorithm, the first algorithm may be the second type of algorithm.

[0107] In some implementations, the communication device may further include a sending module 1130. The sending module 1130 may be configured to send the first information to the first device before the first terminal device receives the first message sent by the first device.

[0108] In some implementations, the first information is carried in first capability information, and the first capability information can be used to indicate the security capability of the first terminal device.

[0109] In some implementations, the first device may be an access network device or a core network device.

[0110] Figure 12 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The dashed lines in Figure 12 indicate that the unit or module is optional. Apparatus 1200 may be used to implement the method described in the above method embodiment. Apparatus 1200 may be a chip, a terminal device, or a network device.

[0111] The apparatus 1200 may include one or more processors 1210. The processor 1210 may support the apparatus 1200 in implementing the methods described in the method embodiments above. The processor 1210 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor. The apparatus 1200 may also include one or more memories 1220. The memories 1220 store programs that can be executed by the processor 1210, causing the processor 1210 to perform the methods described in the method embodiments above. The memory 1220 may be independent of the processor 1210 or integrated into the processor 1210. The apparatus 1200 may also include a transceiver 1230. The processor 1210 may communicate with other devices or chips through the transceiver 1230. For example, the processor 1210 may transmit and receive data with other devices or chips through the transceiver 1230.

[0112] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method in each embodiment of the present invention.

[0113] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program enables a computer to execute the method in each embodiment of the present application.

[0114] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the methods in the various embodiments of the present application.

[0115] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0116] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0117] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0118] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0119] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0120] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0121] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0122] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0123] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0124] 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 the units is merely a logical functional division. In actual implementation, other division methods may be used, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection between devices or units, and can be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate, and 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 according to actual needs to achieve the purpose of the present embodiment. In addition, the functional units in the various embodiments of this application can be integrated into a processing unit, each unit can exist physically separately, or two or more units can be integrated into a single unit.

[0125] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A wireless communication method, characterized in that: include: The first device receives first information, where the first information is used to indicate whether the first terminal device supports a first type of algorithm, where the first type of algorithm is a 256-bit encryption algorithm; The first device determines a first algorithm based on the first information, where the first algorithm is an encryption algorithm used between the first device and the first terminal device.

2. The method according to claim 1, characterized in that If the first terminal device supports the first type of algorithm, the first information includes one or more first identifiers, and the one or more first identifiers are used to indicate the one or more first type of algorithms supported by the first terminal device.

3. The method according to claim 1 or 2, characterized in that The first information includes first indication information, and the first indication information is used to indicate whether the first terminal device supports the first type of algorithm.

4. The method according to claim 1 or 2, characterized in that If the first terminal device supports the first type of algorithm, the first information includes second indication information, and the second indication information is used to instruct the first device to use the first type of algorithm as the first algorithm.

5. The method according to any one of claims 1 to 4, characterized in that The first information is carried in first capability information, and the first capability information is used to indicate the security capability of the first terminal device.

6. The method according to any one of claims 1 to 5, characterized in that The first device determining a first algorithm based on the first information includes: If the first terminal device supports the first type of algorithm and the first device supports the first type of algorithm, the first device preferentially selects the first type of algorithm as the first algorithm; If the first terminal device supports the first type of algorithm but the first device does not support the first type of algorithm, the first device selects a second type of algorithm as the first algorithm, where the second type of algorithm is a 128-bit encryption algorithm; If the first terminal device does not support the first type of algorithm, the first device selects the second type of algorithm as the first algorithm.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first device sends second information to the second device, where the second information is used to indicate a second algorithm. The second algorithm is an encryption algorithm used between the second device and the first terminal device, and the second algorithm is determined by the first device based on the first information.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The first device sends the first information to the second device, where the first information is used by the second device to determine a second algorithm, where the second algorithm is an encryption algorithm between the second device and the first terminal device.

9. The method according to any one of claims 1 to 8, characterized in that The first device is an access network device.

10. The method according to any one of claims 1 to 6, characterized in that The first device is a core network device.

11. A wireless communication method, characterized in that: include: The first terminal device receives a first message sent by a first device, where the first message includes indication information of a first algorithm, where the first algorithm is an encryption algorithm used between the first device and the first terminal device; The first terminal device uses the first algorithm to perform encryption between the first terminal device and the first device; The first algorithm is determined based on first information, and the first information is used to indicate whether the first terminal device supports a first type of algorithm, and the first type of algorithm is a 256-bit encryption algorithm.

12. The method according to claim 11, characterized in that If the first terminal device supports the first type of algorithm, the first information includes one or more first identifiers, and the one or more first identifiers are used to indicate the one or more first type of algorithms supported by the first terminal device.

13. The method according to claim 11 or 12, characterized in that The first information includes first indication information, and the first indication information is used to indicate whether the first terminal device supports the first type of algorithm.

14. The method according to claim 11 or 12, characterized in that If the first terminal device supports the first type of algorithm, the first information includes second indication information, and the second indication information is used to instruct the first device to use the first type of algorithm as the first algorithm.

15. The method according to any one of claims 11 to 14, characterized in that If the first terminal device supports the first type of algorithm and the first device supports the first type of algorithm, the first algorithm is the first type of algorithm.

16. The method according to any one of claims 11 to 15, characterized in that If the first terminal device supports the first type of algorithm, but the first device does not support the first type of algorithm, the first algorithm is the second type of algorithm, and the second type of algorithm is a 128-bit encryption algorithm.

17. The method according to any one of claims 11 to 16, characterized in that If the first terminal device does not support the first type of algorithm, the first algorithm is the second type of algorithm.

18. The method according to any one of claims 11 to 17, characterized in that Before the first terminal device receives the first message sent by the first device, the method further includes: The first terminal device sends the first information to the first device.

19. The method according to claim 18, characterized in that The first information is carried in first capability information, and the first capability information is used to indicate the security capability of the first terminal device.

20. The method according to any one of claims 11 to 19, characterized in that The first device is an access network device or a core network device.

21. A communication device, characterized in that: The communication device is a first device, and the communication device includes: A receiving module, configured to receive first information, where the first information is used to indicate whether the first terminal device supports a first type of algorithm, where the first type of algorithm is a 256-bit encryption algorithm; A determination module is used to determine a first algorithm based on the first information, where the first algorithm is an encryption algorithm used between the first device and the first terminal device.

22. The communication device according to claim 21, wherein: If the first terminal device supports the first type of algorithm, the first information includes one or more first identifiers, and the one or more first identifiers are used to indicate the one or more first type of algorithms supported by the first terminal device.

23. The communication device according to claim 21 or 22, characterized in that The first information includes first indication information, and the first indication information is used to indicate whether the first terminal device supports the first type of algorithm.

24. The communication device according to claim 21 or 22, characterized in that If the first terminal device supports the first type of algorithm, the first information includes second indication information, and the second indication information is used to instruct the first device to use the first type of algorithm as the first algorithm.

25. The communication device according to any one of claims 21 to 24, characterized in that The first information is carried in first capability information, and the first capability information is used to indicate the security capability of the first terminal device.

26. The communication device according to any one of claims 21 to 25, characterized in that The first device determining a first algorithm based on the first information includes: If the first terminal device supports the first type of algorithm and the first device supports the first type of algorithm, the first device preferentially selects the first type of algorithm as the first algorithm; If the first terminal device supports the first type of algorithm but the first device does not support the first type of algorithm, the first device selects a second type of algorithm as the first algorithm, where the second type of algorithm is a 128-bit encryption algorithm; If the first terminal device does not support the first type of algorithm, the first device selects the second type of algorithm as the first algorithm.

27. The communication device according to any one of claims 21 to 26, characterized in that: The communication device further includes: The first sending module is used to send second information to the second device, where the second information is used to indicate a second algorithm. The second algorithm is an encryption algorithm used between the second device and the first terminal device, and the second algorithm is determined by the first device based on the first information.

28. The communication device according to any one of claims 21 to 26, characterized in that The communication device further includes: The second sending module is used to send the first information to the second device, where the first information is used by the second device to determine a second algorithm, where the second algorithm is an encryption algorithm between the second device and the first terminal device.

29. The communication device according to any one of claims 21 to 28, characterized in that The first device is an access network device.

30. The communication device according to any one of claims 21 to 26, characterized in that The first device is a core network device.

31. A communication device, characterized in that: The communication device is a first terminal device, and the communication device includes: a receiving module, configured to receive a first message sent by a first device, where the first message includes indication information of a first algorithm, where the first algorithm is an encryption algorithm used between the first device and the first terminal device; A using module, configured to use the first algorithm to perform encryption with the first device; The first algorithm is determined based on first information, and the first information is used to indicate whether the first terminal device supports a first type of algorithm, and the first type of algorithm is a 256-bit encryption algorithm.

32. The communication device according to claim 31, wherein If the first terminal device supports the first type of algorithm, the first information includes one or more first identifiers, and the one or more first identifiers are used to indicate the one or more first type of algorithms supported by the first terminal device.

33. The communication device according to claim 31 or 32, characterized in that The first information includes first indication information, and the first indication information is used to indicate whether the first terminal device supports the first type of algorithm.

34. The communication device according to claim 31 or 32, characterized in that If the first terminal device supports the first type of algorithm, the first information includes second indication information, and the second indication information is used to instruct the first device to use the first type of algorithm as the first algorithm.

35. The communication device according to any one of claims 31 to 34, characterized in that If the first terminal device supports the first type of algorithm and the first device supports the first type of algorithm, the first algorithm is the first type of algorithm.

36. The communication device according to any one of claims 31 to 35, characterized in that If the first terminal device supports the first type of algorithm, but the first device does not support the first type of algorithm, the first algorithm is the second type of algorithm, and the second type of algorithm is a 128-bit encryption algorithm.

37. The communication device according to any one of claims 31 to 36, characterized in that If the first terminal device does not support the first type of algorithm, the first algorithm is the second type of algorithm.

38. The communication device according to any one of claims 31 to 37, characterized in that The communication device further includes: The sending module is configured to send the first message sent by the first device to the first device before the first terminal device receives the first message sent by the first device. Describe the first information.

39. The communication device according to claim 38, wherein The first information is carried in first capability information, and the first capability information is used to indicate the security capability of the first terminal device.

40. The communication device according to any one of claims 31 to 39, characterized in that The first device is an access network device or a core network device.

41. A communication device, characterized in that The communication device comprises a transceiver, a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send a signal, so that the communication device executes the method according to any one of claims 1 to 10.

42. A communication device, characterized in that The communication device comprises a transceiver, a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send a signal, so that the communication device executes the method according to any one of claims 11 to 20.

43. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to cause the device to execute the method according to any one of claims 1 to 10 or 11 to 20.

44. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 10 or 11 to 20.

45. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1-10 or 11-20.

46. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 10 or 11 to 20.

47. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 10 or 11 to 20.

Images