Security protection method and device for NAS (Network Attached Storage) message and storage medium
By using NAS integrity protection key and encryption key to securely process NAS messages in NAS security function entities, the problem of insufficient security protection of NAS messages after RAN service is solved, and the integrity and confidentiality protection of NAS messages is achieved.
Patent Information
- Application Number
- CN202311267633.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-27
- Publication Date
- 2025-03-28
AI Technical Summary
After the service of the wireless access network (RAN), the prior art does not have a NAS message security protection method based on RAN service, and it is impossible to effectively protect NAS messages between the core network NF and RAN.
By introducing a new security protection method in NAS security function entities, the uplink and downlink NAS messages are leveraged to verify, decrypt, encrypt and integrity protection for uplink and downlink NAS messages through the introduction of new security protection methods in NAS security function entities, ensuring the security of messages during transmission.
The NAS message security protection based on RAN service is realized, ensuring the integrity and confidentiality of NAS messages during transmission, and solving the problem of insufficient security protection in the prior art.
Smart Images

Figure CN119729457A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method, device and storage medium for security protection of Non-Access Stratum (NAS) messages. Background Art
[0002] At present, the encryption and integrity protection of the NAS protocol are completed by the Access and Mobility Management Function (AMF), which is responsible for the encryption and decryption, integrity protection and other security functions of the NAS messages of each core network network function (NF) and the transmission of NAS messages. After the Radio Access Network (RAN) is service-oriented, the core network NF and RAN can interact directly, but there is currently no NAS message security protection method based on RAN service-oriented. Summary of the invention
[0003] The present application provides a method, device and storage medium for security protection of NAS messages, which implement security protection of NAS messages based on RAN service.
[0004] In a first aspect, an embodiment of the present application provides a security protection method for a non-access layer NAS message, which is applied to a NAS security function entity, where the NAS security function entity is a functional entity other than an access mobility management function entity AMF; the method includes:
[0005] Receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity-verified and decrypted uplink NAS message to a NAS network function entity NF;
[0006] and / or
[0007] receiving a downlink NAS message sent by the NAS NF, encrypting the downlink NAS message using a NAS encryption key, performing integrity protection on the downlink NAS message using a NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE;
[0008] The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity.
[0009] In one implementation, the method further includes:
[0010] Activate NAS integrity protection;
[0011] Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key;
[0012] Activate NAS uplink decryption;
[0013] Receiving a NAS security mode completion message sent by the UE;
[0014] Activate NAS downlink encryption.
[0015] In one implementation, activating NAS integrity protection includes:
[0016] The downlink NAS message is received, and NAS integrity protection is activated.
[0017] In one implementation, the method further includes:
[0018] Receiving an initial NAS message sent by the UE;
[0019] Sending the decrypted and integrity-verified initial NAS message to the NAS NF;
[0020] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0021] In one implementation, the method further includes:
[0022] Receiving an initial NAS message sent by the UE;
[0023] Initiating an authentication process with the UE;
[0024] Sending an initial NAS message to the NAS NF;
[0025] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0026] In one implementation, the NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF, or a custom network function entity.
[0027] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key, and the NAS security function entity key is derived by a security anchor function entity SEAF.
[0028] In one implementation, the NAS security function entity includes a SEAF.
[0029] In one implementation, the NAS security function entity is further used to derive keys for untrusted non-3GPP access and gNB keys.
[0030] In a second aspect, the present application provides a non-access layer NAS message security protection method, which is applied to a NAS network function entity NF, and the method includes:
[0031] Receiving an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or
[0032] Sending downlink NAS messages to the UE via the NAS security function entity;
[0033] The NAS security function entity is a functional entity other than the access mobility management function entity AMF, and the NAS security function entity is used to derive a NAS integrity protection key and a NAS encryption key.
[0034] In a third aspect, the present application provides a security protection method for a non-access layer NAS message, which is applied to a NAS security function entity, and the method includes:
[0035] Export NAS integrity protection keys and NAS encryption keys;
[0036] The NAS integrity protection key and the NAS encryption key are sent to a NAS network function entity NF, wherein the NAS integrity protection key is used to perform integrity verification on an uplink NAS message and to perform integrity protection on a downlink NAS message; and the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
[0037] In one implementation, the NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
[0038] In a fourth aspect, the present application provides a security protection method for a non-access layer NAS message, which is applied to a NAS network function entity NF, and the method includes:
[0039] receiving an uplink NAS message from the UE, performing integrity verification on the uplink NAS message using the NAS integrity protection key, and decrypting the uplink NAS message using the NAS encryption key;
[0040] and / or
[0041] Encrypting a downlink NAS message using the NAS encryption key, and integrity protecting the downlink NAS message using the NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE;
[0042] The NAS integrity protection key and the NAS encryption key are sent to the NAS NF by a NAS security function entity; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NAS NF is other functional entities other than the access mobility management function entity AMF.
[0043] In one implementation, the method further includes:
[0044] Activate NAS integrity protection;
[0045] Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key;
[0046] Activate NAS uplink decryption;
[0047] Receiving a NAS security mode completion message sent by the UE;
[0048] Activate NAS downlink encryption.
[0049] In one implementation, the method further includes:
[0050] receiving an initial NAS message from the UE;
[0051] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0052] In one implementation, the method further includes:
[0053] receiving an initial NAS message from the UE;
[0054] Initiating an authentication process with the UE;
[0055] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0056] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on a NAS NF key, and the NAS NF key is derived by a security anchor function entity SEAF.
[0057] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by a security anchor function entity SEAF, and the NAS security function entity is a functional entity outside the SEAF.
[0058] In one implementation, the NAS security function entity includes a security anchor function entity SEAF.
[0059] In one implementation, the NAS security function entity is further used to derive keys for untrusted non-3GPP access and gNB keys.
[0060] In a fifth aspect, the present application provides a security protection device for a non-access layer NAS message, which is applied to a NAS security function entity, wherein the NAS security function entity is a functional entity other than an access mobility management function entity AMF; the device includes:
[0061] An uplink processing module is configured to receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity verified and decrypted uplink NAS message to a NAS network function entity NF;
[0062] and / or
[0063] A downlink processing module, configured to receive a downlink NAS message sent by the NAS NF, encrypt the downlink NAS message using a NAS encryption key, perform integrity protection on the downlink NAS message using a NAS integrity protection key, and send the encrypted and integrity protected downlink NAS message to the UE;
[0064] The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity.
[0065] In one implementation, the system further includes an activation module, configured to:
[0066] Activate NAS integrity protection;
[0067] Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key;
[0068] Activate NAS uplink decryption;
[0069] Receiving a NAS security mode completion message sent by the UE;
[0070] Activate NAS downlink encryption.
[0071] In one implementation, the activation module is used to:
[0072] The downlink NAS message is received, and NAS integrity protection is activated.
[0073] In one implementation, the first initial message protection module is further included, configured to:
[0074] Receiving an initial NAS message sent by the UE;
[0075] Sending the decrypted and integrity-verified initial NAS message to the NAS NF;
[0076] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0077] In one implementation, the device further includes a second initial message protection module, configured to:
[0078] Receiving an initial NAS message sent by the UE;
[0079] Initiating an authentication process with the UE;
[0080] Sending an initial NAS message to the NAS NF;
[0081] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0082] In one implementation, the NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF, or a custom network function entity.
[0083] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key, and the NAS security function entity key is derived by a security anchor function entity SEAF.
[0084] In one implementation, the NAS security function entity includes a SEAF.
[0085] In one implementation, the NAS security function entity is further used to derive keys for untrusted non-3GPP access and gNB keys.
[0086] In a sixth aspect, the present application provides a security protection device for a non-access layer NAS message, which is applied to a NAS network function entity NF, and the device includes:
[0087] a receiving module, configured to receive an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or
[0088] A sending module, used for sending a downlink NAS message to the UE through the NAS security function entity;
[0089] The NAS security function entity is a functional entity other than the access mobility management function entity AMF, and the NAS security function entity is used to derive a NAS integrity protection key and a NAS encryption key.
[0090] In a seventh aspect, the present application provides a security protection device for a non-access layer NAS message, which is applied to a NAS security function entity, and the device includes:
[0091] An export module, used to export NAS integrity protection keys and NAS encryption keys;
[0092] A sending module, configured to send the NAS integrity protection key and the NAS encryption key to a NAS network function entity NF, wherein the NAS integrity protection key is used to perform integrity verification on an uplink NAS message and to perform integrity protection on a downlink NAS message; and the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
[0093] In one implementation, the NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
[0094] In an eighth aspect, the present application provides a security protection device for a non-access layer NAS message, which is applied to a NAS network function entity NF, and the device includes:
[0095] an uplink processing module, configured to receive an uplink NAS message from a UE, perform integrity verification on the uplink NAS message using the NAS integrity protection key, and decrypt the uplink NAS message using the NAS encryption key;
[0096] and / or
[0097] a downlink processing module, configured to encrypt a downlink NAS message using the NAS encryption key, perform integrity protection on the downlink NAS message using the NAS integrity protection key, and send the encrypted and integrity protected downlink NAS message to the UE;
[0098] The NAS integrity protection key and the NAS encryption key are sent to the NAS NF by a NAS security function entity; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NAS NF is other functional entities other than the access mobility management function entity AMF.
[0099] In one implementation, the system further includes an activation module, configured to:
[0100] Activate NAS integrity protection;
[0101] Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key;
[0102] Activate NAS uplink decryption;
[0103] Receiving a NAS security mode completion message sent by the UE;
[0104] Activate NAS downlink encryption.
[0105] In one implementation, the first initial message protection module is further included, configured to:
[0106] receiving an initial NAS message from the UE;
[0107] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0108] In one implementation, the device further includes a second initial message protection module, configured to:
[0109] receiving an initial NAS message from the UE;
[0110] Initiating an authentication process with the UE;
[0111] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0112] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on a NAS NF key, and the NAS NF key is derived by a security anchor function entity SEAF.
[0113] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by a security anchor function entity SEAF, and the NAS security function entity is a functional entity outside the SEAF.
[0114] In one implementation, the NAS security function entity includes a security anchor function entity SEAF.
[0115] In one implementation, the NAS security function entity is further used to derive keys for untrusted non-3GPP access and gNB keys.
[0116] In a ninth aspect, the present application provides a security protection device for a non-access layer NAS message, wherein the device is a NAS security function entity, and the NAS security function entity is a functional entity other than an access mobility management function entity AMF; the device includes a memory, a transceiver, and a processor:
[0117] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0118] Receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity-verified and decrypted uplink NAS message to a NAS network function entity NF;
[0119] and / or
[0120] receiving a downlink NAS message sent by the NAS NF, encrypting the downlink NAS message using a NAS encryption key, performing integrity protection on the downlink NAS message using a NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE;
[0121] The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity.
[0122] In one implementation, the processor is configured to perform the following operations:
[0123] Activate NAS integrity protection;
[0124] Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key;
[0125] Activate NAS uplink decryption;
[0126] Receiving a NAS security mode completion message sent by the UE;
[0127] Activate NAS downlink encryption.
[0128] In one implementation, activating NAS integrity protection includes:
[0129] The downlink NAS message is received, and NAS integrity protection is activated.
[0130] In one implementation, the processor is configured to perform the following operations:
[0131] Receiving an initial NAS message sent by the UE;
[0132] Sending the decrypted and integrity-verified initial NAS message to the NAS NF;
[0133] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0134] In one implementation, the processor is configured to perform the following operations:
[0135] Receiving an initial NAS message sent by the UE;
[0136] Initiating an authentication process with the UE;
[0137] Sending an initial NAS message to the NAS NF;
[0138] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0139] In one implementation, the NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF, or a custom network function entity.
[0140] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key, and the NAS security function entity key is derived by a security anchor function entity SEAF.
[0141] In one implementation, the NAS security function entity includes a SEAF.
[0142] In one implementation, the NAS security function entity is further used to derive keys for untrusted non-3GPP access and gNB keys.
[0143] In a tenth aspect, the present application provides a security protection device for a non-access layer NAS message, the device being a NAS network function entity NF, the device comprising a memory, a transceiver, and a processor:
[0144] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0145] Receiving an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or
[0146] Sending downlink NAS messages to the UE via the NAS security function entity;
[0147] The NAS security function entity is a functional entity other than the access mobility management function entity AMF, and the NAS security function entity is used to derive a NAS integrity protection key and a NAS encryption key.
[0148] In an eleventh aspect, the present application provides a security protection device for a non-access layer NAS message, the device being a NAS security function entity, the device comprising a memory, a transceiver, and a processor:
[0149] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0150] Export NAS integrity protection keys and NAS encryption keys;
[0151] The NAS integrity protection key and the NAS encryption key are sent to a NAS network function entity NF, wherein the NAS integrity protection key is used to perform integrity verification on an uplink NAS message and to perform integrity protection on a downlink NAS message; and the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
[0152] In one implementation, the NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
[0153] In a twelfth aspect, the present application provides a security protection device for non-access layer NAS messages, the device being a NAS network function entity NF, the device comprising a memory, a transceiver, and a processor:
[0154] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0155] receiving an uplink NAS message from the UE, performing integrity verification on the uplink NAS message using the NAS integrity protection key, and decrypting the uplink NAS message using the NAS encryption key;
[0156] and / or
[0157] Encrypting a downlink NAS message using the NAS encryption key, and integrity protecting the downlink NAS message using the NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE;
[0158] The NAS integrity protection key and the NAS encryption key are sent to the NAS NF by a NAS security function entity; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NAS NF is other functional entities other than the access mobility management function entity AMF.
[0159] In one implementation, the processor is configured to perform the following operations:
[0160] Activate NAS integrity protection;
[0161] Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key;
[0162] Activate NAS uplink decryption;
[0163] Receiving a NAS security mode completion message sent by the UE;
[0164] Activate NAS downlink encryption.
[0165] In one implementation, the processor is configured to perform the following operations:
[0166] receiving an initial NAS message from the UE;
[0167] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0168] In one implementation, the processor is configured to perform the following operations:
[0169] receiving an initial NAS message from the UE;
[0170] Initiating an authentication process with the UE;
[0171] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
[0172] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on a NAS NF key, and the NAS NF key is derived by a security anchor function entity SEAF.
[0173] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by a security anchor function entity SEAF, and the NAS security function entity is a functional entity outside the SEAF.
[0174] In one implementation, the NAS security function entity includes a security anchor function entity SEAF.
[0175] In one implementation, the NAS security function entity is further used to derive keys for untrusted non-3GPP access and gNB keys.
[0176] In a thirteenth aspect, the present application provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method described in the first aspect.
[0177] In a fourteenth aspect, the present application provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method described in the second aspect.
[0178] In a fifteenth aspect, the present application provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method described in the third aspect.
[0179] In a sixteenth aspect, the present application provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method described in the fourth aspect.
[0180] It should be understood that the contents described in the above summary of the invention are not intended to limit the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0181] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0182] Figure 1 is a schematic diagram of a key derivation mechanism in the related art;
[0183] Figure 2 This is a flow diagram of a NAS message security protection method provided by an embodiment of the present application. Figure 1 ;
[0184] Figure 3 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 1 ;
[0185] Figure 4 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 2 ;
[0186] Figure 5 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 3 ;
[0187] Figure 6 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 4 ;
[0188] Figure 7 This is a schematic diagram of a NAS SMC process provided in an embodiment of the present application. Figure 1 ;
[0189] Figure 8 This is a schematic diagram of an initial NAS message protection process provided by an embodiment of the present application Figure 1 ;
[0190] Fig. 9 This is a flow diagram of a NAS message security protection method provided by an embodiment of the present application. Figure 2 ;
[0191] Fig.10 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 5 ;
[0192] Fig.11 This is a schematic diagram of a NAS SMC process provided in an embodiment of the present application. Figure 2 ;
[0193] Fig.12 This is a schematic diagram of an initial NAS message protection process provided by an embodiment of the present application Figure 2 ;
[0194] Fig.13 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 1 ;
[0195] Fig.14 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 2 ;
[0196] Fig.15 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 3 ;
[0197] Fig.16 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 4 ;
[0198] Fig.17 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 5 ;
[0199] Fig.18 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 6 ;
[0200] Fig.19 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 7 ;
[0201] Fig. 20 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 8 . DETAILED DESCRIPTION
[0202] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.
[0203] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.
[0204] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0205] The embodiments of the present application provide a method and apparatus for protecting the security of NAS messages, so as to implement the security protection of NAS messages based on RAN service.
[0206] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.
[0207] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.
[0208] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.
[0209] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.
[0210] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.
[0211] In the related art, the keys involved in the encryption, decryption and integrity protection of NAS messages are derived by AMF. Figure 1 It is a schematic diagram of a key derivation mechanism in the related art. Figure 1 As can be seen from the figure, the UE side and the network side each generate a series of keys. The network side is generated by the unified data management function entity (UDM) / Authentication Credential Repository and Processing Function (ARPF), Authentication Server Function (AUSF), Security Anchor Function (SEAF), AMF, Non-3GPP InterWorking Function (N3IWF), gNB and other network elements. The UE side is generated by the Universal Subscriber Identity Module (USIM) and the mobile equipment (ME). This series of keys includes K AUSF , K SEAF , K AMF , K NASint , K NASenc , K N3IWF , K gNB , K RRCint , K RRCenc , K UPint and K UPenc Among them, the NAS integrity protection key K on the network side NASint and NAS encryption key K NASenc By AMF based on the AMF key K AMF Export.
[0212] In the transmission of NAS messages, the UE's uplink NAS message is sent to the AMF via the RAN. The AMF uses the NAS integrity protection key K NASint and NAS encryption key K NASenc After integrity verification and decryption of the uplink NAS message, it is sent to the NAS NF, which is the core network NF corresponding to the uplink NAS message; for the NASNF that needs to send a downlink NAS message, the NAS NF sends the downlink NAS message to the AMF, which is protected by the NAS integrity key K. NASint and NAS encryption key K NASenc After the uplink NAS message is encrypted and integrity protected, it is sent to the UE through the RAN. In other words, the uplink and downlink transmission of NAS messages between the NAS NF and the UE depends on the AMF.
[0213] After RAN service-oriented, the core network NF and RAN can interact directly. Therefore, the security protection of NAS messages can be completed by the core network NF other than AMF. The following describes the security protection method of NAS messages based on RAN service-oriented in conjunction with the embodiment.
[0214] Figure 2 This is a flow diagram of a NAS message security protection method provided by an embodiment of the present application. Figure 1 .like Figure 2 As shown, the method includes:
[0215] S201. A NAS security function (NAS Security Function, NASSF) receives an uplink NAS message sent by a user equipment UE.
[0216] The NASSF in this embodiment is a network element used to complete NAS message encryption and decryption and integrity protection. It should be noted that NASSF is not limited to a specific network element. NASSF can be an existing network element in the relevant technology, or a newly added network element for implementing the security protection function of NAS messages. The name of NASSF is not limited to this. This is only used as an illustration in the embodiments of the present application. For example, NASSF may include any of the following: Session Management Function (SMF), Location Management Function (LMF), Policy Control Function (PCF), Short Message Service Function (SMSF), SEAF or a custom network function entity.
[0217] In the embodiment of the present application, the security protection function of the NAS message is implemented by the NASSF. Therefore, the uplink NAS message sent by the UE is sent to the NASSF through the RAN, wherein the uplink NAS message sent by the UE is encrypted by the NAS encryption key on the UE side and integrity protected by the NAS integrity protection key on the UE side.
[0218] S202. The NASSF uses a NAS integrity protection key to perform integrity verification on the uplink NAS message, and uses a NAS encryption key to decrypt the uplink NAS message.
[0219] Among them, the NAS integrity protection key and NAS encryption key are derived by NASSF.
[0220] S203. NASSF sends the integrity-verified and decrypted uplink NAS message to NAS NF.
[0221] After receiving the uplink NAS message, NASSF uses the NAS integrity protection key derived from the NASSF side to verify the integrity of the uplink NAS message. After the verification is successful, it uses the NAS encryption key to decrypt the uplink NAS message to obtain the uplink NAS message and send it to NAS NF. NAS NF receives the uplink NAS message of the UE sent by NASSF, thus realizing the transmission of the uplink NAS message.
[0222] S204. NASSF receives the downlink NAS message sent by NAS NF.
[0223] S205. The NASSF encrypts the downlink NAS message using the NAS encryption key, and performs integrity protection on the downlink NAS message using the NAS integrity protection key.
[0224] Among them, the NAS integrity protection key and NAS encryption key are derived by NASSF.
[0225] S206. NASSF sends the encrypted and integrity-protected downlink NAS message to the UE.
[0226] In the embodiment of the present application, the security protection function of the NAS message is implemented by NASSF. The NAS NF sends a downlink NAS message to the UE through the NASSF. The NASSF uses the NAS encryption key derived from the NASSF side to encrypt the downlink NAS message sent by the NAS NF, and uses the NAS integrity protection key derived from the NASSF side to protect the integrity of the downlink NAS message, and sends the encrypted and integrity-protected downlink NAS message to the UE, thereby completing the transmission of the downlink NAS message.
[0227] The above S201-S203 are steps for uplink NAS message transmission, and S204-S206 are steps for downlink NAS message transmission. It should be noted that the embodiment of the present application does not limit the need to execute both uplink and downlink NAS message transmission. For example, only S201-S203 may be executed to implement uplink NAS message transmission, or only S204-S206 may be executed to implement downlink NAS message transmission, or both S201-S203 and S204-S206 may be executed to implement uplink and downlink NAS message transmission, wherein the order of S201-S203 and S204-S206 is not limited.
[0228] In the embodiment of the present application, the NAS encryption key and the NAS integrity protection key are derived by the NASSF, and the NASSF encrypts and decrypts the NAS message and performs integrity protection, thereby realizing security protection of the NAS message based on RAN service.
[0229] The following Figure 2 The NASSF in the illustrated embodiment derives NAS encryption keys and NAS integrity protection keys for illustration.
[0230] Figure 3 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 1 .like Figure 3 As shown, the NAS integrity protection key and the NAS encryption key are generated by the NASSF based on the NASSF key K NASSF Export, NASSF key K NASSF By SEAF based on SEAF key K SEAF Export. NASSF may include any of the following: SMF, LMF, PCF, SMS or custom network function entity. NASSF is also used to export the key K for untrusted non-3GPP access N31WF and gNB key K gNB .
[0231] Figure 4 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 2 .like Figure 4 As shown, the NAS integrity protection key and the NAS encryption key are generated by the NASSF based on the NASSF key K NASSF Export, NASSF key K NASSF By SEAF based on SEAF key K SEAF In this embodiment, the non-trusted non-3GPP access key K N31WF and gNB key K gNB Still by AMF based on the AMF key K AMF Export, AMF key K AMFBy SEAF based on SEAF key K SEAF Export.
[0232] Figure 5 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 3 In this embodiment, NASSF is SEAF, such as Figure 5 As shown, the NAS integrity protection key and NAS encryption key are generated by SEAF based on the SEAF key K SEAF In addition, the untrusted non-3GPP access key K N31WF and gNB key K gNB Also by SEAF based on the SEAF key K SEAF Export.
[0233] Figure 6 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 4 In this embodiment, NASSF is SEAF, such as Figure 6 As shown, the NAS integrity protection key and NAS encryption key are generated by SEAF based on the SEAF key K SEAF The key K for untrusted non-3GPP access is derived. N31WF and gNB key K gNB Still by AMF based on the AMF key K AMF Export, AMF key K AMF By SEAF based on SEAF key K SEAF Export.
[0234] exist Figure 2 Before the uplink and downlink NAS message transmission is performed, the method of the embodiment of the present application may further include a NAS security mode command (Securituy Mode Command, SMC) process and an initial NAS message protection process.
[0235] Figure 7 This is a schematic diagram of a NAS SMC process provided in an embodiment of the present application. Figure 1 The NASSF in this embodiment can be the aforementioned Figure 2 The NASSF in the illustrated embodiment, for example, NASSF may be SMF, LMF, PCF, SMSF, SEAF or a custom network function entity. Figure 7 As shown, the process includes:
[0236] 1. NAS NF sends a downlink NAS message (Nnassf_xx_xx) to NASSF.
[0237] 1a.NASSF activates NAS integrity protection.
[0238] 1b. NASSF sends a NAS security mode command message (NAS Security Mode Command) to the UE. The NAS Security Mode Command is integrity protected by the NAS integrity protection key but is not encrypted.
[0239] 1c.NASSF activates NAS uplink decryption.
[0240] 2a.UE performs integrity verification on the NAS Security Mode Command and, if verification is successful, starts NAS integrity protection and encryption / decryption.
[0241] 2b.UE sends a NAS security mode completion message (NAS Security Mode Complete) to NASSF. NAS Security Mode Complete is encrypted and integrity protected.
[0242] 1d.NASSF activates NAS downlink encryption.
[0243] It should be noted that step 1 is one of the factors that trigger the subsequent NAS SMC process, that is, the NASSF receives a downlink NAS message and activates NAS integrity protection. In addition, the NAS SMC process can also be triggered in the initial NAS message protection process, which will be explained in the subsequent embodiments.
[0244] Figure 8 This is a schematic diagram of an initial NAS message protection process provided by an embodiment of the present application Figure 1 .like Figure 8 As shown, the process includes:
[0245] 1. NASSF receives the initial NAS message sent by the UE.
[0246] If the UE does not have a NAS security context, the initial NAS message contains only a plaintext information element (IE). If the UE has a NAS security context, the initial NAS message sent by the UE in step 1 is encrypted and integrity protected, and if the NASSF also has the same NAS security context, the subsequent steps 2 to 4 are not performed.
[0247] 2. NASSF initiates the authentication process with the UE.
[0248] If the NASSF cannot find the NAS security context locally or the integrity verification fails, the NASSF initiates the authentication process with the UE to obtain the NAS security context.
[0249] 3. NASSF sends a NAS security mode command message (NAS Security Mode Command) to the UE, and the NAS Security Mode Command is integrity protected by the NAS integrity protection key.
[0250] If the initial NAS message is protected but does not pass integrity verification or the NASSF cannot decrypt the complete initial NAS message, the NASSF may carry a flag in the NAS Security Mode Command to instruct the UE to send the complete initial NAS message in the NAS Security Mode Complete message.
[0251] 4.UE sends NAS Security Mode Complete to NASSF, and NAS Security Mode Complete is encrypted and integrity protected.
[0252] Steps 3 and 4 are the NAS SMC process, please refer to Figure 7 In steps 1a to 1d of the illustrated embodiment, the NASSF activation of NAS integrity protection, activation of NAS uplink decryption, activation of NAS downlink ciphering, and UE initiation of NAS integrity protection and encryption and decryption are not illustrated.
[0253] 5. NASSF sends the initial NAS message to NAS NF.
[0254] 6. The NASSF sends an initial NAS message response to the UE, where the initial NAS message response is encrypted using the NAS encryption key and integrity protected using the NAS integrity protection key.
[0255] The above embodiments illustrate the scenario in which the NAS integrity protection key and the NAS encryption key are derived by the NASSF, and the NASSF performs encryption and decryption of NAS messages and integrity protection. In another feasible implementation, the encryption and decryption of NAS messages and integrity protection may be performed by the NAS NF, and the NAS integrity protection key and the NAS encryption key may be derived by the NASSF and sent to the NAS NF, or may be derived by the NAS NF itself, which is described below in conjunction with the embodiments.
[0256] Fig. 9 This is a flow diagram of a NAS message security protection method provided by an embodiment of the present application. Figure 2 .like Fig. 9 As shown, the method includes:
[0257] S901. NAS NF receives an uplink NAS message from UE.
[0258] S902. The NAS NF uses the NAS integrity protection key to verify the integrity of the uplink NAS message, and uses the NAS encryption key to decrypt the uplink NAS message.
[0259] S903. The NAS NF uses the NAS encryption key to encrypt the downlink NAS message, and uses the NAS integrity protection key to perform integrity protection on the downlink NAS message.
[0260] S904. NAS NF sends the encrypted and integrity-protected downlink NAS message to the UE.
[0261] The NAS integrity protection key and the NAS encryption key are sent by the NASSF to the NAS NF; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NAS NF is other functional entities other than the access mobility management functional entity AMF.
[0262] The above S901-S902 are steps for uplink NAS message transmission, and S903-S904 are steps for downlink NAS message transmission. It should be noted that the embodiment of the present application does not limit the need to execute both uplink and downlink NAS message transmission. For example, only S901-S902 may be executed to implement uplink NAS message transmission, or only S903-S904 may be executed to implement downlink NAS message transmission, or S901-S902 and S903-S904 may be executed to implement uplink and downlink NAS message transmission, wherein the order of S901-S902 and S903-S904 is not limited.
[0263] In the embodiment of the present application, when the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, the NASNF may include any of the following: SMF, LMF, PCF, and SMSF, and each NAS NF may derive its own NAS integrity protection key and NAS encryption key. In this case, the AMF may still derive the NAS integrity protection key and NAS encryption key of the AMF. In addition, when the NAS integrity protection key and the NAS encryption key are sent by the NASSF to the NAS NF, the NASNF may include any of the following: AMF, SMF, LMF, PCF, and SMSF.
[0264] In the embodiment of the present application, the NAS encryption key and the NAS integrity protection key are derived by the NASSF or the NAS NF, and the NAS message is encrypted and decrypted and integrity protected by the NAS NF, thereby realizing security protection of the NAS message based on RAN service.
[0265] Fig.10 This is a schematic diagram of a key derivation mechanism provided in an embodiment of the present application. Figure 5 Among them, the NAS integrity protection key and NAS encryption key are derived by NAS NF based on the NAS NF key, and the NAS NF key is derived by SEAF based on the SEAF key K SEAF Export. Optionally, NAS NF may include SMF, LMF, PCF and SMSF. Each NAS NF establishes a separate NAS security context with the UE, and each NAS security context adds a parameter that identifies the NAS type. The NAS integrity protection key and NAS encryption key exported by each NAS NF may be the same or different. Each NAS NF performs security functions and transmission such as encryption and decryption and integrity protection of the corresponding NAS message. In addition, AMF can still export the NAS integrity protection key and NAS encryption key of AMF for untrusted non-3GPP access key K N31WF and gNB key K gNB Still by AMF based on the AMF key K AMF Export, AMF key K AMF By SEAF based on SEAF key K SEAF Export.
[0266] In a scenario where the NAS integrity protection key and the NAS encryption key are derived by the NASSF based on the NASSF key and sent to the NASNF, the NASSF derives the NAS integrity protection key and the NAS encryption key, and sends the NAS integrity protection key and the NAS encryption key to the NAS NF, wherein the NAS integrity protection key is used to perform integrity verification on uplink NAS messages and integrity protection on downlink NAS messages; the NAS encryption key is used to decrypt uplink NAS messages and encrypt downlink NAS messages. The schematic diagram of NASSF deriving the NAS integrity protection key and the NAS encryption key can be referred to in the foregoing embodiment. Figures 3 to 6 NASSF can be a functional entity other than SEAF, such as SMF, LMF, PCF, SMSF or a custom network functional entity, and the NASSF key is derived by SEAF. Alternatively, NASSF can be SEAF. In addition, NASSF can also be AMF. For each NAS NF, the NAS integrity protection key and NAS encryption key derived by NASSF can be the same or different.
[0267] exist Fig. 9 Before the uplink and downlink NAS message transmission is performed, the method of the embodiment of the present application may further include a NASSMC process and an initial NAS message protection process.
[0268] Fig.11 This is a schematic diagram of a NAS SMC process provided in an embodiment of the present application. Figure 2 .like Fig.11 As shown, the process includes:
[0269] 1a.NAS NF activates NAS integrity protection.
[0270] 1b.NAS NF sends a NAS Security Mode Command message to the UE. The NAS Security Mode Command is integrity protected by the NAS integrity protection key but is not encrypted.
[0271] 1c.NAS NF activates NAS uplink decryption.
[0272] 2a.UE performs integrity verification on the NAS Security Mode Command and, if verification is successful, starts NAS integrity protection and encryption / decryption.
[0273] 2b.UE sends a NAS Security Mode Complete message to NAS NF. NAS Security Mode Complete is protected by encryption and integrity.
[0274] 1d.NAS NF activates NAS downlink encryption.
[0275] It should be noted that NAS SMC can be triggered when NAS NF needs to send a downlink NAS message, that is, NAS NF activates NAS integrity protection when it needs to send a downlink NAS message. In addition, the NAS SMC process can also be triggered in the initial NAS message protection process, which will be explained in subsequent embodiments.
[0276] Fig.12 This is a schematic diagram of an initial NAS message protection process provided by an embodiment of the present application Figure 2 .like Fig.12 As shown, the process includes:
[0277] 1. NAS NF receives the initial NAS message sent by the UE.
[0278] If the UE does not have a NAS security context, the initial NAS message only contains a plaintext information element (IE). If the UE has a NAS security context, the initial NAS message sent by the UE in step 1 is encrypted and integrity protected, and if the NAS NF also has the same NAS security context, the subsequent steps 2 to 4 are not performed.
[0279] 2. NAS NF starts the authentication process with the UE.
[0280] If the NAS NF cannot find the NAS security context locally or the integrity verification fails, the NAS NF initiates the authentication process with the UE to obtain the NAS security context.
[0281] 3. NAS NF sends a NAS security mode command message (NAS Security Mode Command) to the UE, and the NAS Security Mode Command is integrity protected by the NAS integrity protection key.
[0282] If the initial NAS message is protected but does not pass integrity verification or the NAS NF cannot decrypt the complete initial NAS message, the NAS NF may carry a flag in the NAS Security Mode Command to instruct the UE to send the complete initial NAS message in the NAS Security Mode Complete message.
[0283] 4.UE sends NAS Security Mode Complete to NAS NF, and NAS Security Mode Complete is encrypted and integrity protected.
[0284] Steps 3 and 4 are the NAS SMC process, please refer to Fig.11 In steps 1a to 1d of the illustrated embodiment, the NAS NF activation of NAS integrity protection, activation of NAS uplink decryption, activation of NAS downlink encryption, and UE initiation of NAS integrity protection and encryption and decryption are not illustrated.
[0285] 5. The NAS NF sends an initial NAS message response to the UE, where the initial NAS message response is encrypted using the NAS encryption key and integrity protected using the NAS integrity protection key.
[0286] In the above embodiment, the NAS integrity protection key and the NAS encryption key are derived by the NASSF or the NAS NF, and the encryption and decryption and integrity protection of the NAS message are performed by the NAS NF, thereby realizing the security protection of the NAS message based on RAN service.
[0287] Fig.13 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 1 The device is NASSF, such as Fig.13 As shown, the security protection device for NAS messages includes a processor 1310 , a memory 1320 , and a transceiver 1330 .
[0288] Among them, Fig.13 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1310 and various circuits of the memory represented by the memory 1320 are linked together. The bus architecture 1330 may be a plurality of elements, namely, a transmitter and a receiver, and a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, etc. The processor 1310 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1310 when performing operations.
[0289] The processor 1310 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0290] The memory 1320 is used to store computer programs; the transceiver 1330 is used to send and receive data under the control of the processor 1310; the processor 1310 is used to read the computer program in the memory 1320 and perform the following operations:
[0291] Receive an uplink NAS message sent by a user equipment UE, use a NAS integrity protection key to perform integrity verification on the uplink NAS message, and use a NAS encryption key to decrypt the uplink NAS message, and send the integrity verified and decrypted uplink NAS message to a NAS network function entity NF;
[0292] and / or
[0293] Receive a downlink NAS message sent by the NAS NF, encrypt the downlink NAS message using a NAS encryption key, perform integrity protection on the downlink NAS message using a NAS integrity protection key, and send the encrypted and integrity-protected downlink NAS message to the UE;
[0294] Among them, the NAS integrity protection key and NAS encryption key are derived by the NAS security function entity.
[0295] In one implementation, the processor 1310 is configured to perform the following operations:
[0296] Activate NAS integrity protection;
[0297] Send a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected using the NAS integrity protection key;
[0298] Activate NAS uplink decryption;
[0299] Receive a NAS security mode completion message sent by the UE;
[0300] Activate NAS downlink encryption.
[0301] In one implementation, activating NAS integrity protection includes:
[0302] Receive downlink NAS message and activate NAS integrity protection.
[0303] In one implementation, the processor 1310 is configured to perform the following operations:
[0304] Receive an initial NAS message sent by the UE;
[0305] Send the decrypted and integrity-verified initial NAS message to the NAS NF;
[0306] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0307] In one implementation, the processor 1310 is configured to perform the following operations:
[0308] Receive an initial NAS message sent by the UE;
[0309] Start the authentication process with the UE;
[0310] Send the initial NAS message to the NAS NF;
[0311] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0312] In one implementation, the NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF, or a custom network function entity.
[0313] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on the NAS security function entity key, and the NAS security function entity key is derived by the security anchor function entity SEAF.
[0314] In one implementation, the NAS security function entity includes a SEAF.
[0315] In one implementation, the NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
[0316] Fig.14 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 2 The device is a NAS NF, such as Fig.14 As shown, the security protection device for NAS messages includes: a processor 1410 , a memory 1420 , and a transceiver 1430 .
[0317] Among them, Fig.14 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1410 and various circuits of memory represented by memory 1420 are linked together. Bus architecture 1430 may be multiple components, namely, a transmitter and a receiver, and a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, etc. Processor 1410 is responsible for managing the bus architecture and general processing, and memory 1420 may store data used by processor 1410 when performing operations.
[0318] The processor 1410 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0319] The memory 1420 is used to store computer programs; the transceiver 1430 is used to send and receive data under the control of the processor 1410; the processor 1410 is used to read the computer program in the memory 1420 and perform the following operations:
[0320] Receiving an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or
[0321] Sending downlink NAS messages to the UE via the NAS security function entity;
[0322] Among them, the NAS security function entity is other functional entities other than the access mobility management function entity AMF, and the NAS security function entity is used to derive NAS integrity protection keys and NAS encryption keys.
[0323] Fig.15 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 3 The device is NASSF, such as Fig.15 As shown, the security protection device for NAS messages includes: a processor 1510 , a memory 1520 , and a transceiver 1530 .
[0324] Among them, Fig.15 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1510 and various circuits of memory represented by memory 1520 are linked together. Bus architecture 1530 may be multiple components, namely, a transmitter and a receiver, and a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, etc. Processor 1510 is responsible for managing the bus architecture and general processing, and memory 1520 may store data used by processor 1510 when performing operations.
[0325] The processor 1510 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0326] The memory 1520 is used to store computer programs; the transceiver 1530 is used to send and receive data under the control of the processor 1510; the processor 1510 is used to read the computer program in the memory 1520 and perform the following operations:
[0327] Export NAS integrity protection keys and NAS encryption keys;
[0328] The NAS integrity protection key and NAS encryption key are sent to the NAS network function entity NF, where the NAS integrity protection key is used to verify the integrity of the uplink NAS message and to protect the integrity of the downlink NAS message; the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
[0329] In one implementation, the NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
[0330] Fig.16 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 4 The device is a NAS NF, such as Fig.16 As shown, the security protection device for NAS messages includes: a processor 1610 , a memory 1620 and a transceiver 1630 .
[0331] Among them, Fig.16 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1610 and various circuits of memory represented by memory 1620 are linked together. Bus architecture 1630 may be multiple components, namely, a transmitter and a receiver, and a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, etc. Processor 1610 is responsible for managing the bus architecture and general processing, and memory 1620 may store data used by processor 1610 when performing operations.
[0332] The processor 1610 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0333] The memory 1620 is used to store computer programs; the transceiver 1630 is used to send and receive data under the control of the processor 1610; the processor 1610 is used to read the computer program in the memory 1620 and perform the following operations:
[0334] Receive uplink NAS messages from the UE, verify the integrity of the uplink NAS messages using the NAS integrity protection key, and decrypt the uplink NAS messages using the NAS encryption key;
[0335] and / or
[0336] Encrypt the downlink NAS message using the NAS encryption key, and integrity protect the downlink NAS message using the NAS integrity protection key, and send the encrypted and integrity-protected downlink NAS message to the UE;
[0337] The NAS integrity protection key and the NAS encryption key are sent by the NAS security function entity to the NAS NF; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NAS NF is other functional entities other than the access mobility management function entity AMF.
[0338] In one implementation, the processor 1610 is configured to perform the following operations:
[0339] Activate NAS integrity protection;
[0340] Send a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected using the NAS integrity protection key;
[0341] Activate NAS uplink decryption;
[0342] Receive a NAS security mode completion message sent by the UE;
[0343] Activate NAS downlink encryption.
[0344] In one implementation, the processor 1610 is configured to perform the following operations:
[0345] Receive an initial NAS message from the UE;
[0346] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0347] In one implementation, the processor 1610 is configured to perform the following operations:
[0348] Receive an initial NAS message from the UE;
[0349] Start the authentication process with the UE;
[0350] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0351] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on the NAS NF key, and the NAS NF key is derived by the security anchor function entity SEAF.
[0352] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on the NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by the security anchor function entity SEAF. The NAS security function entity is a functional entity outside the SEAF.
[0353] In one implementation, the NAS security function entity includes a security anchor function entity SEAF.
[0354] In one implementation, the NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
[0355] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0356] Fig.17 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 5 The device is applied to NAS security function entity, which is other function entity other than access mobility management function entity AMF. The security protection device of NAS message includes:
[0357] The uplink processing module 1701 is configured to receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity verified and decrypted uplink NAS message to a NAS network function entity NF;
[0358] and / or
[0359] The downlink processing module 1702 is configured to receive a downlink NAS message sent by the NAS NF, encrypt the downlink NAS message using a NAS encryption key, perform integrity protection on the downlink NAS message using a NAS integrity protection key, and send the encrypted and integrity protected downlink NAS message to the UE;
[0360] Among them, the NAS integrity protection key and NAS encryption key are derived by the NAS security function entity.
[0361] In one implementation, the system further includes an activation module, configured to:
[0362] Activate NAS integrity protection;
[0363] Send a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected using the NAS integrity protection key;
[0364] Activate NAS uplink decryption;
[0365] Receive a NAS security mode completion message sent by the UE;
[0366] Activate NAS downlink encryption.
[0367] In one implementation, the activation module is used to:
[0368] Receive downlink NAS message and activate NAS integrity protection.
[0369] In one implementation, the first initial message protection module is further included, configured to:
[0370] Receive an initial NAS message sent by the UE;
[0371] Send the decrypted and integrity-verified initial NAS message to the NAS NF;
[0372] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0373] In one implementation, the device further includes a second initial message protection module, configured to:
[0374] Receive an initial NAS message sent by the UE;
[0375] Start the authentication process with the UE;
[0376] Send the initial NAS message to the NAS NF;
[0377] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0378] In one implementation, the NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF, or a custom network function entity.
[0379] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on the NAS security function entity key, and the NAS security function entity key is derived by the security anchor function entity SEAF.
[0380] In one implementation, the NAS security function entity includes a SEAF.
[0381] In one implementation, the NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
[0382] Fig.18 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 6 The device is applied to the NAS network function entity NF. The security protection device of the NAS message includes:
[0383] The receiving module 1801 is configured to receive an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or
[0384] The sending module 1802 is configured to send a downlink NAS message to the UE through the NAS security function entity;
[0385] Among them, the NAS security function entity is other functional entities other than the access mobility management function entity AMF, and the NAS security function entity is used to derive NAS integrity protection keys and NAS encryption keys.
[0386] Fig.19 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 7 The device is applied to the NAS security function entity. The security protection device of the NAS message includes:
[0387] An export module 1901, configured to export a NAS integrity protection key and a NAS encryption key;
[0388] The sending module 1902 is used to send the NAS integrity protection key and the NAS encryption key to the NAS network function entity NF, wherein the NAS integrity protection key is used to verify the integrity of the uplink NAS message and to perform integrity protection on the downlink NAS message; the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
[0389] In one implementation, the NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
[0390] Fig. 20 This is a schematic diagram of the structure of a NAS message security protection device provided in an embodiment of the present application. Figure 8 The device is applied to a NAS network function entity NF, and includes:
[0391] The uplink processing module 2001 is used to receive an uplink NAS message from the UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key;
[0392] and / or
[0393] The downlink processing module 2002 is configured to encrypt a downlink NAS message using a NAS encryption key, and perform integrity protection on the downlink NAS message using a NAS integrity protection key, and send the encrypted and integrity protected downlink NAS message to the UE;
[0394] The NAS integrity protection key and the NAS encryption key are sent by the NAS security function entity to the NAS NF; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NAS NF is other functional entities other than the access mobility management function entity AMF.
[0395] In one implementation, the system further includes an activation module, configured to:
[0396] Activate NAS integrity protection;
[0397] Send a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected using the NAS integrity protection key;
[0398] Activate NAS uplink decryption;
[0399] Receive a NAS security mode completion message sent by the UE;
[0400] Activate NAS downlink encryption.
[0401] In one implementation, the first initial message protection module is further included, configured to:
[0402] Receive an initial NAS message from the UE;
[0403] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0404] In one implementation, the device further includes a second initial message protection module, configured to:
[0405] Receive an initial NAS message from the UE;
[0406] Start the authentication process with the UE;
[0407] An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted using a NAS encryption key and integrity protected using a NAS integrity protection key.
[0408] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on the NAS NF key, and the NAS NF key is derived by the security anchor function entity SEAF.
[0409] In one implementation, the NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on the NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by the security anchor function entity SEAF. The NAS security function entity is a functional entity outside the SEAF.
[0410] In one implementation, the NAS security function entity includes a security anchor function entity SEAF.
[0411] In one implementation, the NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
[0412] It should be noted that the division of modules / units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module / unit in each embodiment of the present application may be integrated into a processing module / unit, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one module / unit. The above-mentioned integrated modules / units may be implemented in the form of hardware or in the form of software functional units.
[0413] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.
[0414] It should be noted here that the above-mentioned device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0415] An embodiment of the present application provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the method executed by any of the above-mentioned devices.
[0416] The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.
[0417] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0418] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0419] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0420] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0421] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A method for protecting the security of non-access layer NAS messages, characterized in that: Applied to a NAS security function entity, the NAS security function entity is another function entity other than the access mobility management function entity AMF; the method comprises: Receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity-verified and decrypted uplink NAS message to a NAS network function entity NF; and / or receiving a downlink NAS message sent by the NAS NF, encrypting the downlink NAS message using a NAS encryption key, performing integrity protection on the downlink NAS message using a NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE; The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity.
2. The method according to claim 1, characterized in that Also includes: Activate NAS integrity protection; Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key; Activate NAS uplink decryption; Receiving a NAS security mode completion message sent by the UE; Activate NAS downlink encryption.
3. The method according to claim 2, characterized in that The activating NAS integrity protection includes: The downlink NAS message is received, and NAS integrity protection is activated.
4. The method according to claim 1, characterized in that: Also includes: Receiving an initial NAS message sent by the UE; Sending the decrypted and integrity-verified initial NAS message to the NAS NF; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
5. The method according to claim 2, characterized in that: Also includes: Receiving an initial NAS message sent by the UE; Initiating an authentication process with the UE; Sending an initial NAS message to the NAS NF; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
6. The method according to claim 1, characterized in that The NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF or a custom network function entity.
7. The method according to claim 6, characterized in that The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key, and the NAS security function entity key is derived by a security anchor function entity SEAF.
8. The method according to claim 1, characterized in that The NAS security function entity includes SEAF.
9. The method according to any one of claims 6 to 8, characterized in that: The NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
10. A method for protecting the security of non-access layer NAS messages, characterized in that: Applied in a NAS network function entity NF, the method comprises: Receiving an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or Sending downlink NAS messages to the UE via the NAS security function entity; The NAS security function entity is a functional entity other than the access mobility management function entity AMF, and the NAS security function entity is used to derive a NAS integrity protection key and a NAS encryption key.
11. A method for protecting the security of non-access layer NAS messages, characterized in that: Applied to a NAS security function entity, the method comprises: Export NAS integrity protection keys and NAS encryption keys; The NAS integrity protection key and the NAS encryption key are sent to a NAS network function entity NF, wherein the NAS integrity protection key is used to perform integrity verification on an uplink NAS message and to perform integrity protection on a downlink NAS message; and the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
12. The method according to claim 11, characterized in that The NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
13. A method for protecting the security of non-access layer NAS messages, characterized in that: Applied in a NAS network function entity NF, the method comprises: receiving an uplink NAS message from the UE, performing integrity verification on the uplink NAS message using the NAS integrity protection key, and decrypting the uplink NAS message using the NAS encryption key; and / or Encrypting a downlink NAS message using the NAS encryption key, and integrity protecting the downlink NAS message using the NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE; The NAS integrity protection key and the NAS encryption key are sent to the NAS NF by a NAS security function entity; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NASNF is a functional entity other than an access mobility management function entity AMF.
14. The method according to claim 13, characterized in that Also includes: Activate NAS integrity protection; Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key; Activate NAS uplink decryption; Receiving a NAS security mode completion message sent by the UE; Activate NAS downlink encryption.
15. The method according to claim 13, characterized in that Also includes: receiving an initial NAS message from the UE; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
16. The method according to claim 14, characterized in that Also includes: receiving an initial NAS message from the UE; Initiating an authentication process with the UE; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
17. The method according to claim 13, characterized in that The NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on a NAS NF key, and the NAS NF key is derived by a security anchor function entity SEAF.
18. The method according to claim 13, characterized in that The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by a security anchor function entity SEAF. The NAS security function entity is a functional entity outside the SEAF.
19. The method according to claim 13, characterized in that The NAS security function entity includes a security anchor function entity SEAF.
20. The method according to claim 18 or 19, characterized in that The NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
21. A security protection device for non-access layer NAS messages, characterized in that: Applied to a NAS security function entity, the NAS security function entity is another function entity other than the access mobility management function entity AMF; the device comprises: An uplink processing module is configured to receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity verified and decrypted uplink NAS message to a NAS network function entity NF; and / or A downlink processing module, configured to receive a downlink NAS message sent by the NAS NF, encrypt the downlink NAS message using a NAS encryption key, perform integrity protection on the downlink NAS message using a NAS integrity protection key, and send the encrypted and integrity protected downlink NAS message to the UE; The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity.
22. A security protection device for non-access layer NAS messages, characterized in that: Applied in a NAS network function entity NF, the device comprises: a receiving module, configured to receive an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or A sending module, used for sending a downlink NAS message to the UE through the NAS security function entity; The NAS security function entity is a functional entity other than the access mobility management function entity AMF, and the NAS security function entity is used to derive a NAS integrity protection key and a NAS encryption key.
23. A security protection device for non-access layer NAS messages, characterized in that: Applied to a NAS security function entity, the device comprises: An export module, used to export NAS integrity protection keys and NAS encryption keys; A sending module, configured to send the NAS integrity protection key and the NAS encryption key to a NAS network function entity NF, wherein the NAS integrity protection key is used to perform integrity verification on an uplink NAS message and to perform integrity protection on a downlink NAS message; and the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
24. A security protection device for non-access layer NAS messages, characterized in that: Applied in a NAS network function entity NF, the device comprises: an uplink processing module, configured to receive an uplink NAS message from a UE, perform integrity verification on the uplink NAS message using the NAS integrity protection key, and decrypt the uplink NAS message using the NAS encryption key; and / or a downlink processing module, configured to encrypt a downlink NAS message using the NAS encryption key, perform integrity protection on the downlink NAS message using the NAS integrity protection key, and send the encrypted and integrity protected downlink NAS message to the UE; The NAS integrity protection key and the NAS encryption key are sent to the NAS NF by a NAS security function entity; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NASNF is a functional entity other than an access mobility management function entity AMF.
25. A security protection device for non-access layer NAS messages, characterized in that: The device is a NAS security function entity, which is a function entity other than the access mobility management function entity AMF; the device includes a memory, a transceiver, and a processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Receive an uplink NAS message sent by a user equipment UE, perform integrity verification on the uplink NAS message using a NAS integrity protection key, and decrypt the uplink NAS message using a NAS encryption key, and send the integrity-verified and decrypted uplink NAS message to a NAS network function entity NF; and / or receiving a downlink NAS message sent by the NAS NF, encrypting the downlink NAS message using a NAS encryption key, performing integrity protection on the downlink NAS message using a NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE; The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity.
26. The device according to claim 25, characterized in that The processor is configured to perform the following operations: Activate NAS integrity protection; Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key; Activate NAS uplink decryption; Receiving a NAS security mode completion message sent by the UE; Activate NAS downlink encryption.
27. The device according to claim 26, characterized in that The activating NAS integrity protection includes: The downlink NAS message is received, and NAS integrity protection is activated.
28. The device according to claim 25, characterized in that The processor is configured to perform the following operations: Receiving an initial NAS message sent by the UE; Sending the decrypted and integrity-verified initial NAS message to the NAS NF; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
29. The device according to claim 26, characterized in that The processor is configured to perform the following operations: Receiving an initial NAS message sent by the UE; Initiating an authentication process with the UE; Sending an initial NAS message to the NAS NF; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
30. The device according to claim 25, characterized in that The NAS security function entity includes any one of the following: a session management function entity SMF, a location management function entity LMF, a policy control function entity PCF, a short message service function entity SMSF or a custom network function entity.
31. The device according to claim 30, characterized in that The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key, and the NAS security function entity key is derived by a security anchor function entity SEAF.
32. The device according to claim 25, characterized in that The NAS security function entity includes SEAF.
33. The device according to any one of claims 30 to 32, characterized in that The NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
34. A security protection device for non-access layer NAS messages, characterized in that: The device is a NAS network function entity NF, and the device includes a memory, a transceiver, and a processor: a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Receiving an uplink NAS message of a user equipment UE sent by a NAS security function entity; and / or Sending downlink NAS messages to the UE via the NAS security function entity; The NAS security function entity is a functional entity other than the access mobility management function entity AMF, and the NAS security function entity is used to derive a NAS integrity protection key and a NAS encryption key.
35. A security protection device for non-access layer NAS messages, characterized in that: The device is a NAS security function entity, and the device includes a memory, a transceiver, and a processor: a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Export NAS integrity protection keys and NAS encryption keys; The NAS integrity protection key and the NAS encryption key are sent to a NAS network function entity NF, wherein the NAS integrity protection key is used to perform integrity verification on an uplink NAS message and to perform integrity protection on a downlink NAS message; and the NAS encryption key is used to decrypt the uplink NAS message and to encrypt the downlink NAS message.
36. The device according to claim 35, characterized in that The NAS security function entity includes any one of the following: access and mobility management function AMF, session management function entity SMF, location management function entity LMF, policy control function entity PCF, short message service function entity SMSF, security anchor function entity SEAF or custom network function entity.
37. A security protection device for non-access layer NAS messages, characterized in that: The device is a NAS network function entity NF, and the device includes a memory, a transceiver, and a processor: a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: receiving an uplink NAS message from the UE, performing integrity verification on the uplink NAS message using the NAS integrity protection key, and decrypting the uplink NAS message using the NAS encryption key; and / or Encrypting a downlink NAS message using the NAS encryption key, and integrity protecting the downlink NAS message using the NAS integrity protection key, and sending the encrypted and integrity protected downlink NAS message to the UE; The NAS integrity protection key and the NAS encryption key are sent to the NAS NF by a NAS security function entity; or, the NAS integrity protection key and the NAS encryption key are derived by the NAS NF, and the NASNF is a functional entity other than an access mobility management function entity AMF.
38. The device according to claim 37, characterized in that The processor is configured to perform the following operations: Activate NAS integrity protection; Sending a NAS security mode command message to the UE, where the NAS security mode command message is integrity protected by the NAS integrity protection key; Activate NAS uplink decryption; Receiving a NAS security mode completion message sent by the UE; Activate NAS downlink encryption.
39. The device according to claim 37, characterized in that The processor is configured to perform the following operations: receiving an initial NAS message from the UE; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
40. The device according to claim 38, characterized in that The processor is configured to perform the following operations: receiving an initial NAS message from the UE; Initiating an authentication process with the UE; An initial NAS message response is sent to the UE, where the initial NAS message response is encrypted by the NAS encryption key and integrity protected by the NAS integrity protection key.
41. The device according to claim 37, characterized in that The NAS integrity protection key and the NAS encryption key are derived by the NAS NF based on a NAS NF key, and the NAS NF key is derived by a security anchor function entity SEAF.
42. The device according to claim 37, characterized in that The NAS integrity protection key and the NAS encryption key are derived by the NAS security function entity based on a NAS security function entity key and sent to the NAS NF. The NAS security function entity key is derived by a security anchor function entity SEAF. The NAS security function entity is a functional entity outside the SEAF.
43. The device according to claim 37, characterized in that The NAS security function entity includes a security anchor function entity SEAF.
44. The device according to claim 42 or 43, characterized in that The NAS security function entity is also used to derive keys for untrusted non-3GPP access and gNB keys.
45. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method according to any one of claims 1 to 9.
46. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method of claim 10.
47. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method of claim 11 or 12.
48. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method according to any one of claims 13 to 20.