US11240019B2 - Method, device, and system for deriving keys - Google Patents

Method, device, and system for deriving keys Download PDF

Info

Publication number
US11240019B2
US11240019B2 US13/323,840 US201113323840A US11240019B2 US 11240019 B2 US11240019 B2 US 11240019B2 US 201113323840 A US201113323840 A US 201113323840A US 11240019 B2 US11240019 B2 US 11240019B2
Authority
US
United States
Prior art keywords
key
count value
downlink count
handover
nas downlink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US13/323,840
Other languages
English (en)
Other versions
US20120077501A1 (en
Inventor
Aiqin Zhang
Jing Chen
Xiaoyu BI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=43370806&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US11240019(B2) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BI, XIAOYU, CHEN, JING, ZHANG, AIQIN
Publication of US20120077501A1 publication Critical patent/US20120077501A1/en
Priority to US17/583,013 priority Critical patent/US20220150062A1/en
Application granted granted Critical
Publication of US11240019B2 publication Critical patent/US11240019B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0869—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80—Wireless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
    • H04L2463/061—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying further key derivation, e.g. deriving traffic keys from a pair-wise master key
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device, and system for deriving keys.
  • a mobile communication system includes a radio access network.
  • the radio access network include second generation mobile communication network, third generation mobile communication network, and Long Term Evolution (LTE) communication network.
  • LTE Long Term Evolution
  • a key of the target network may be derived from a key of the source network, thereby avoiding a process of authentication and key negotiation.
  • the UE and the target network each generates, through the same key parameter and algorithm, the key eventually used in the target network.
  • UTRAN Universal Terrestrial Radio Access Network
  • CK Ciphering Key
  • IK Integrity Key
  • EUTRAN Evolved UTRAN
  • Kasme root key
  • a base station (BS) originally serving the UE in the EUTRAN (referred to as a source BS below) initiates a network handover process;
  • a Mobility Management Entity (MME) associated with the source BS (referred to as a source MME below), derives a key CK′ ⁇ IK′ of the UE in the target network according to a Key Derivation Function (KDF), an input parameter (i.e. a root key Kasme), and a Non-Access Stratum (NAS) downlink COUNT value in the current security context, and sends the derived key to the target UTRAN.
  • KDF Key Derivation Function
  • NAS Non-Access Stratum
  • the target network decides a security algorithm for the UE and returns the security algorithm to the UE.
  • the UE synchronizes the key with the target network side according to the security algorithm.
  • the handover of the UE to the UTRAN may fail due to the failure of the connection of an air interface radio link, so that the UE is returned to the EUTRAN.
  • the UE initiates a link reestablishment process to the BS currently serving the UE, that is, the BS where the UE currently locates (referred to as a current BS below) and after deciding to perform a handover, the current BS initiates a second handover process.
  • the key derivation on the MME in the second handover process and the key derivation on the MME in the first handover process are both performed according to the root key Kasme and the current NAS downlink COUNT value, and therefore the calculated key CK′ ⁇ IK′ is the same.
  • the keys obtained during the handovers by several Radio Network Controllers (RNC) in a UMTS network through a target Serving GPRS Support Node (SGSN) may be the same. Once a key used on one RNC is obtained, keys on other RNCs can be derived accordingly, resulting in a network security risk.
  • RNC Radio Network Controllers
  • SGSN target Serving GPRS Support Node
  • the present invention is directed to, when a user equipment is handed over from a source radio access network to a target radio access network, a method, a device, and a system for deriving a key for use in the target radio access network.
  • the invention enhances the network security.
  • An embodiment of the present invention provides a key derivation method.
  • the method includes:
  • KDF key derivation function
  • Another embodiment of the present invention provides a key derivation method.
  • the method includes:
  • the Handover Command message includes a random value, using the random value and a root key as input parameters of a KDF to derive a key for the UE in a target radio access network;
  • the Handover Command message includes the random value and a current NAS downlink COUNT value, using the random value, the current NAS downlink COUNT value, and the root key as input parameters of the KDF to derive the key for the UE in the target radio access network.
  • a further embodiment of the present invention provides a key derivation method.
  • the method includes:
  • Yet another embodiment of the present invention provides a key derivation method.
  • the method includes:
  • Yet a further embodiment of the present invention provides a key derivation method.
  • the method includes:
  • the Handover Required message includes a fresh value of a UE
  • An embodiment of the present invention provides a key derivation method.
  • the method includes:
  • RRC Radio Resource Control
  • An embodiment of the present invention provides an MME.
  • the MME includes:
  • a generating unit configured to generate a random value
  • a deriving unit configured to use a root key and the random value generated by the generating unit as input parameters of a KDF to derive a key of a UE for use in a target radio access network; or use the random value, a current NAS downlink COUNT value, and the root key as the input parameters of the KDF to derive the key of the UE for use in the target radio access network.
  • An embodiment of the present invention provides a UE, where the UE includes:
  • a message receiving unit configured to receive a Handover Command message
  • a key deriving unit configured to use a random value and a root key as input parameters of a KDF to derive a key of the UE in a target radio access network if the Handover Command message received by the message receiving unit includes the random value
  • the message receiving unit configured to use the random value, a current NAS downlink COUNT value, and the root key as input parameters of the KDF to derive the key of the UE in the target radio access network if the Handover Command message received by the message receiving unit includes the random value and the current NAS downlink COUNT value.
  • An embodiment of the present invention provides an MME, where the MME includes:
  • a count value obtaining unit configured to obtain a new NAS downlink COUNT value
  • a second deriving unit configured to derive a key of a UE in a target radio access network according to a KDF, a root key, and the new NAS downlink COUNT value obtained by the count value obtaining unit;
  • a handover sending unit configured to send the new NAS downlink COUNT value obtained by the count value obtaining unit to the UE, so that the UE derives the key in the target radio access network.
  • An embodiment of the present invention provides a UE, where the UE includes:
  • a second message receiving unit configured to receive a Handover Command message, in which the Handover Command message includes a new NAS downlink COUNT value;
  • a second key deriving unit configured to derive a key of the UE in a target radio access network according to a KDF, a root key, and the new NAS downlink COUNT value in the Handover Command message received by the second message receiving unit.
  • An embodiment of the present invention provides a communication system, where the communication system includes any one of the above MMEs.
  • the key derivation method, device, and system according to the embodiments of the present invention are applicable to the handover process of the UE from a source radio access network to a target radio access network, and particularly to the handover process from the EUTRAN to the UTRAN.
  • the key derived on the source MME in the first handover process of the UE is different from the key derived on the MME in the second handover process of the UE through changing the input parameters used in the key derivation, such as generating the random value, changing the current NAS downlink COUNT value, and obtaining the fresh value of the UE, so as to prevent the situation in the prior art that once the key used on one RNC is obtained, the keys on other RNCs can be derived accordingly, thereby enhancing the network security.
  • FIG. 1 is a flowchart of a key derivation method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a key derivation method according to Method Embodiment 1 of the present invention
  • FIG. 3 is a flowchart of a key derivation method according to Method Embodiment 2 of the present invention.
  • FIG. 4 is a flowchart of a key derivation method according to Method Embodiment 3 of the present invention.
  • FIG. 5 is a flowchart of a key derivation method according to Method Embodiment 4 of the present invention.
  • FIG. 6 is a flowchart of a key derivation method according to Method Embodiment 5 of the present invention.
  • FIG. 7 is a block diagram of a logic structure of an MME according to Device Embodiment 1 of the present invention.
  • FIG. 8 is a block diagram of a logic structure of a UE according to Device Embodiment 2 of the present invention.
  • FIG. 9 is a block diagram of a logic structure of an MME according to Device Embodiment 3 of the present invention.
  • FIG. 10 is a block diagram of a logic structure of a UE according to Device Embodiment 4 of the present invention.
  • FIG. 11 is a block diagram of a logic structure of an MME according to Device Embodiment 5 of the present invention.
  • FIG. 12 is a block diagram of a logic structure of a BS according to Device Embodiment 6 of the present invention.
  • FIG. 13 is a block diagram of a logic structure of a UE according to Device Embodiment 7 of the present invention.
  • FIG. 14 is a block diagram of a logic structure of an MME according to Device Embodiment 8 of the present invention.
  • the embodiments of the present invention are applicable to the handover process of a UE from an EUTRAN to a UTRAN.
  • the following method is used to enhance the network security in the embodiments of the present invention: an NAS downlink COUNT value used when key derivation is performed on a source MME during a first handover process of the UE is different from the NAS downlink COUNT value used when key derivation is performed on the MME during a second handover process of the UE, so that the keys generated during each handover process of the UE from the EUTRAN to the UTRAN are different, and the keys of the UE used on the RNC and SGSN in the target network are thus different. Therefore, the situation in the prior art that once the key used on one RNC is obtained, the keys used on other RNCs can be derived accordingly is avoided, thereby enhancing the network security.
  • an embodiment of the present invention provides a key derivation method, where the method includes the following steps:
  • Step 10 An MME generates a random value.
  • Step 20 The MME uses the random value and a root key as input parameters of a KDF to derive a key of a UE in a target UTRAN; or uses the random value, a current NAS downlink COUNT value, and the root key as input parameters of the KDF to derive the key of the UE in the target UTRAN.
  • An application scenario of this embodiment is a handover process of a UE from an EUTRAN to a UTRAN.
  • a flowchart of the method according to this embodiment is shown in FIG. 2 , which includes the flowing steps:
  • Step 101 A BS where a UE currently locates, namely a current BS, sends a “Handover Required” message to an MME associated with the current BS, namely a current MME.
  • Step 102 The current MME receives the Handover Required message, generates a random value, and uses the random value and a root key as input parameters of a KDF to derive a key of the UE in a target UTRAN.
  • the current MME may generate a random value at any time when receiving the Handover Required message.
  • the random value i.e. a fresh value of the MME, may be generated by an internal random number generating module of the MME.
  • the current MME may use the fresh value of the MME and the root key as the input parameters of the KDF to derive the key of the UE in the target UTRAN.
  • Step 103 The current MME sends a Relocation Request message to a target RNC through a target SGSN, in which the Relocation Request message includes the key of the UE in the target UTRAN calculated in step 102 , a corresponding KSI, and information such as a security capability of the UE in the UTRAN or GSM/EDGE Radio Access Network (GERAN).
  • the Relocation Request message includes the key of the UE in the target UTRAN calculated in step 102 , a corresponding KSI, and information such as a security capability of the UE in the UTRAN or GSM/EDGE Radio Access Network (GERAN).
  • GERAN GSM/EDGE Radio Access Network
  • Step 104 The target RNC sends a Forward Relocation Response message to the current MME through the target SGSN, in which the Forward Relocation Response message carries an algorithm identifier (ID) selected by the target RNC according to the security capability of the UE.
  • ID algorithm identifier
  • Step 105 The current MME sends the random value obtained in step 102 to the UE through a Handover Command message.
  • the MME may send the Handover Command message to the BS, in which the Handover Command message may include the generated random value, and further include information such as the algorithm ID and the current NAS downlink COUNT value; and the BS then sends information such as the random value, the current NAS downlink COUNT value, and the algorithm ID included in the Handover Command message to the UE through an “handover from EUTRAN” (HO from EUTRAN) command message.
  • EUTRAN HO from EUTRAN
  • Step 106 The UE receives the Handover Command message, derives the key according to the random value through the method in the above step 102 , therefore achieving the synchronization of the key between the UE and the target network, and sends an HO Complete message to the target RNC to complete the network handover. It can be understood that the UE may calculate the specific CK′ or IK′ according to the algorithm ID.
  • the source MME may apply the key derivation method used in the network handover of this embodiment; and after the failure of the first handover of the UE, the MME may also apply the key derivation method of this embodiment to derive the key in the second handover of the UE.
  • the MME may use the random value, the current NAS downlink COUNT value, and the root key as the input parameters of the KDF to derive the key of the UE in the target UTRAN.
  • the MME sends the Handover Command message including the random value and the current NAS downlink COUNT value to the UE, and only four least significant bits of the current NAS downlink COUNT value may be included herein.
  • the UE derives the key according to the random value and the current NAS downlink COUNT value by using the method in step 102 .
  • the source MME may save the key after deriving the key; and when the first handover of the UE succeeds, the saved key may be deleted.
  • the source MME receives a Forward Relocation Complete message sent by the target SGSN after the UE sends the HO Complete message, which indicates that the first handover is successful.
  • the MME determines whether the key of the UE in the target UTRAN is currently saved; if yes, the MME further determines whether the NAS downlink COUNT value corresponding to the currently saved key of the UE in the target UTRAN is consistent with the current NAS downlink COUNT value; and if consistent, the MME obtains a random value.
  • the MME determines that the key of the UE in the target UTRAN is not currently saved, a random value is obtained by using the method of this embodiment, and then the derivation is performed; and if the above consistency determination result is inconsistent, the derivation is performed by using the current derivation method.
  • an NAS process may be performed, and the NAS downlink COUNT value changes, so that when the above determination result is inconsistent, the MME may use the current NAS downlink COUNT value to derive the key, and the key derived in this manner is different from the key derived in the first handover; if the determination result is positive, a random value is obtained.
  • the key derivation method used in the handover of the UE from the EUTRAN to the UTRAN is that: when receiving the Handover Required message, the MME generates a random value, and derives the key of the UE in the target UTRAN according to the KDF, the root key, and the random value.
  • the key derived in the second handover process after the failure of the first handover of the UE is surely different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • a network handover method is provided.
  • An application scenario of this embodiment is that in the handover process of a UE from an EUTRAN to a UTRAN, after a first handover of the UE fails, the UE returns to the original EUTRAN and selects an SGSN for a second handover.
  • a flowchart of the method according to this embodiment is shown in FIG. 3 . The method includes the following steps:
  • Step 201 The UE sends an RRC Connection Reestablishment Request message to a source BS, and performs an RRC connection reestablishment process.
  • the UE may return to a different cell under the source BS, or return to the same cell under the source BS, or return to a BS different from the source BS.
  • the UE returning to the same cell under the source BS is used for illustration.
  • Step 202 After the RRC connection is reestablished, the source BS sends a Handover Required message to a source MME.
  • Step 203 The source MME receives the Handover Required message, and obtains a new NAS downlink COUNT value, in which the new NAS downlink COUNT value is different from a current NAS downlink COUNT value.
  • the source MME may obtain the new NAS downlink COUNT value in following way:
  • adding a certain value to the current NAS downlink COUNT value such as adding 1;
  • NAS message such as an NAS Security Mode Command (SMC) message
  • SMC NAS Security Mode Command
  • Step 204 The source MME derives the key of the UE in a target UTRAN according to a KDF, a root key, and the new NAS downlink COUNT value.
  • Step 205 The source MME sends a Relocation Request message to a target RNC through the target SGSN, in which the Relocation Request message includes the key of the UE in the target UTRAN calculated in step 204 .
  • Step 206 The target RNC sends a Forward Relocation Response message to the source MME through the target SGSN, in which the Forward Relocation Response message carries an algorithm ID selected by the target RNC according to a security capability of the UE.
  • Step 207 The source MME sends the new NAS downlink COUNT value to the UE through a Handover Command message, in which only four least significant bits of the new NAS downlink COUNT value may be sent to the UE.
  • the MME may send the Handover Command message to the BS, in which the Handover Command message may include the new NAS downlink COUNT value, and may also include information such as an algorithm ID; and the BS then sends the new NAS downlink COUNT value to the UE through an HO from EUTRAN command message.
  • the Handover Command message may include the new NAS downlink COUNT value, and may also include information such as an algorithm ID; and the BS then sends the new NAS downlink COUNT value to the UE through an HO from EUTRAN command message.
  • Step 208 The UE receives the Handover Command message, derives the key according to the KDF, the root key, and the new NAS downlink COUNT value by using the method in the above step 204 , therefore achieving the synchronization of the key between the UE and the target network, and sends an HO Complete message to the target RNC to complete the network handover.
  • the source MME may save the key after the key derivation, and when receiving a Forward Relocation Complete message sent by the target SGSN, the source MME may delete the saved key. Therefore, before performing step 203 , the source MME determines whether the key of the UE in the target UTRAN is currently saved; if yes, further determines whether the NAS downlink COUNT value corresponding to the currently saved key of the UE in the target UTRAN is consistent with the current NAS downlink COUNT value; and if consistent, performs step 203 to obtain the new NAS downlink COUNT value.
  • the MME may perform step 203 to obtain the new NAS downlink COUNT value; and if the above consistency determination result is inconsistent, the MME performs the derivation according to the current derivation method.
  • two state machines are set in the source MME, respectively for the key derivation incapable of using the saved NAS downlink COUNT value and the key derivation capable of using the saved NAS downlink COUNT value, and are respectively indicated by State 0 and State 1 .
  • the source MME receives the Handover Required message
  • State 0 is set; and when the MME goes through a certain internal process and satisfies a preset condition, State 1 is set, that is, the key derivation can be performed, in which the preset condition includes: the MME receives a Forward Relocation Complete message, the current NAS downlink COUNT value is added by a certain value, and the MME delivers an NAS message.
  • the key derivation can be performed after the MME receives the Handover Required message and delivers the NAS message.
  • the key derivation method in the second network handover is that, after receiving the Handover Required message, the source MME obtains the new NAS downlink COUNT value different from the current NAS downlink COUNT value, and derives the key of the UE in the target UTRAN according to the KDF, the root key, and the new NAS downlink COUNT value.
  • the key derived in the second handover process is surely different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • An application scenario of this embodiment is that in the handover process of a UE from an EUTRAN to a UTRAN, after a first handover of the UE fails, the UE returns to the original EUTRAN and selects an SGSN for a second handover.
  • FIG. 4 A flowchart of the method is shown in FIG. 4 , which includes the following steps:
  • Step 301 The UE sends an RRC Connection Reestablishment Request message to a BS where the UE currently locates, namely a current BS, to perform an RRC connection reestablishment process.
  • the UE may return to a different cell under a source BS, or return to the same cell under the source BS, or return to a BS different from the source BS.
  • Step 302 After the RRC connection is reestablished, the current BS sends an RRC Connection Reestablishment Complete message to an MME associated with the current BS, namely a current MME.
  • the RRC Connection Reestablishment Complete message may be an HO Notify message, or may be a Path Switch message.
  • the current BS namely the source BS
  • the current MME may indicate that the connection reestablishment is completed
  • the current BS may send the Path Switch message to the current MME.
  • Step 303 The current MME receives the RRC Connection Reestablishment Complete message sent by the current BS, and obtains a new NAS downlink COUNT value, in which the new NAS downlink COUNT value is different from a current NAS downlink COUNT value.
  • the obtaining method is the same as that described in step 203 of Method Embodiment 2, and the details are not described herein again.
  • Step 304 The current BS determines to perform the second handover and sends a Handover Required message to the current MME.
  • Step 305 After receiving the Handover Required message, the current MME derives the key of the UE in the target UTRAN according to a KDF, a root key, and the new NAS downlink COUNT value obtained in step 303 , and sends the derived key to a target RNC.
  • step 303 and step 304 in this embodiment may be performed at the same time, but preferably performed in sequence, and therefore, the network handover process may not be affected, which saves the network handover time.
  • the key derivation method in the embodiment of the present invention is that, during the handover of the UE from the EUTRAN to the UTRAN, after the first handover fails and before the second handover of the UE, the MME obtains the new NAS downlink COUNT value different from the current NAS downlink COUNT value, so that after the MME receives the Handover Required message, the derived and calculated key of the UE in the target UTRAN is surely different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • the network handover may not be affected, and compared with Method Embodiment 1, the network handover time is reduced.
  • An application scenario of this embodiment is that in the handover process of a UE from an EUTRAN to a UTRAN, after a first handover of the UE fails, the UE returns to the original EUTRAN for a second handover.
  • a flowchart of the method is shown in FIG. 5 , which includes the following steps:
  • Step 401 The UE sends an RRC Connection Reestablishment Request message to a BS where the UE currently locates, namely a current BS, in which the RRC Connection Reestablishment Request message may include a 2-bit spare to carry a fresh value of the UE, namely a random value.
  • Step 402 After receiving the RRC Connection Reestablishment Request message, the current BS determines to perform the second handover of the UE, and sends, through a Handover Required message, the fresh value of the UE to the MME associated with the current BS, namely the current MME, to derive the key of the UE in the target UTRAN.
  • Step 403 After receiving the Handover Required message, the current MME uses the fresh value of the UE included in the Handover Required message and a root key as input parameters of a KDF to derive the key of the UE in the target UTRAN.
  • Step 404 The current MME sends a Relocation Request message to a target RNC through a target SGSN, in which the Relocation Request message includes the key of the UE in the target UTRAN calculated in step 403 .
  • Step 405 The target RNC sends a Forward Relocation Response message to the current MME through the target SGSN, in which the Forward Relocation Response message carries an algorithm ID selected by the target RNC according to a security capability of the UE.
  • Step 406 The current MME sends a Handover Command message to the BS, in which the Handover Command message may include the current NAS downlink COUNT value, and may further include information such as an algorithm ID; and then the BS sends the Handover Command message to the UE, in which the Handover Command message may include the current NAS downlink COUNT value.
  • Step 407 The UE receives the Handover Command message, and derives the key according to the fresh value of the UE through the method in the above step 403 , therefore achieving the synchronization of the key between the UE and the target network.
  • the MME may use the fresh value of the UE, the current NAS downlink COUNT value, and the root key as the input parameters of the KDF to derive the key of the UE in the target UTRAN.
  • the source MME may save the key after the key derivation, and when receiving a Forward Relocation Complete message sent by the target SGSN, the source MME may delete the saved key. Therefore, after receiving the Handover Required message, the current MME determines whether the key of the UE in the target UTRAN is currently saved; if yes, further determines whether the NAS downlink COUNT value corresponding to the currently saved key of the UE in the target UTRAN is consistent with the current NAS downlink COUNT value; and if consistent, the key derivation is performed according to the method of this embodiment.
  • the derivation is performed according to the method of this embodiment; and if the above consistency determination result is inconsistent, the derivation is performed according to the derivation method in the prior art.
  • the key derivation method in the embodiment of the present invention is that, in the handover process of the UE from the EUTRAN to the UTRAN, when the UE performs the second handover after the first handover fails, the UE calculates a fresh value, and sends the fresh value to the current MME through the current BS; after receiving the Handover Required message, the current MME derives the key of the UE in the target UTRAN according to the fresh value of the UE, the KDF, the root key, and the current NAS downlink COUNT value included in the Handover Required message.
  • the key derived in the second handover process is different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • An application scenario of this embodiment is that in the handover process of a UE from an EUTRAN to a UTRAN, a BS in the original EUTRAN of the UE, namely a source BS, initiates a network handover.
  • a flow chart of the method is shown in FIG. 6 , which includes the following steps.
  • Step 501 The source BS sends a Handover Required message to a source MME.
  • Step 502 The source MME derives CK′ ⁇ IK′ according to a KDF, a root key Kasme, and an NAS downlink COUNT value in a current security context.
  • Step 503 The source MME sends a Relocation Request message to a target RNC through a target SGSN, in which the Relocation Request message includes CK′ ⁇ IK′, KSI, and information such as a security capability of the UTRAN/GERAN of the UE.
  • Step 504 The target RNC sends a Forward Relocation Response message to the source MME through the target SGSN, in which the Forward Relocation Response message carries an algorithm ID of the security capability of the UE.
  • Step 505 The source MME completes a handover preparation process, and sends a Handover Command message to the UE through the source BS, in which the Handover Command message carries the current NAS downlink COUNT value and the algorithm ID of the security capability.
  • Step 506 The source MME changes the current NAS downlink COUNT value, for example, adding a certain value to the current NAS downlink COUNT value, such as adding 1, and saves the changed NAS downlink COUNT value; the changed NAS downlink COUNT value is used to derive the key of the UE in the target UTRAN.
  • Step 507 After receiving the Handover Command message, the UE derives and calculates the key CK′ ⁇ IK′ according to the KDF and the NAS downlink COUNT value that is included in the Handover Command message, so that the key of the UE and the target network is synchronized, and an HO Complete message is sent to the target RNC.
  • the NAS downlink COUNT value is changed, so that after the first handover of the UE fails, the NAS downlink COUNT value saved in step 506 and used by the MME for the key derivation in the second handover is surely different from the NAS downlink COUNT value used in the first handover, and therefore the keys derived and calculated in the two handovers are different, which achieves the purpose of enhancing the network security.
  • a physical device i.e. a network entity called Mobility Management Entity (MME) is provided.
  • MME Mobility Management Entity
  • FIG. 7 A block diagram of the MME is shown in FIG. 7 , which includes a generating unit 10 , a deriving unit 11 , and a sending unit 12 .
  • the generating unit 10 is configured to generate a random value.
  • the deriving unit 11 is configured to use a root key and the random value that is generated by the generating unit 10 as input parameters of a KDF to derive a key of a UE in a target UTRAN.
  • the sending unit 12 is configured to send the random value generated by the generating unit 10 to the UE, so that the UE derives the key in the target UTRAN according to the random value.
  • the deriving unit 11 is further configured to use a current NAS downlink COUNT value, the root key, and the random value generated by the generating unit 10 as the input parameters of the KDF to derive the key of the UE in the target UTRAN; and the sending unit 12 is configured to send the current NAS downlink COUNT value and the random value generated by the generating unit 10 to the UE, so that the UE derives the key in the target UTRAN according to the random value and the current NAS downlink COUNT value.
  • the generating unit 10 of the MME generates a random value, and the deriving unit 11 derives the key according to the random value, so that in the handover process of the UE from the EUTRAN to the UTRAN, after the first handover fails, the key derived by the MME in the second handover process is surely different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • a UE is provided.
  • a block diagram of the UE is shown in FIG. 8 , which includes a message receiving unit 20 and a key deriving unit 21 .
  • the message receiving unit 20 is configured to receive a Handover Command message.
  • the key deriving unit 21 is configured to use a random value and a root key as input parameters of a KDF to derive the key of the UE in a target UTRAN if the Handover Command message received by the message receiving unit 20 includes the random value; and configured to use the random value, a current NAS downlink COUNT value, and the root key as the input parameters of the KDF to derive the key of the UE in the target UTRAN if the Handover Command message received by the message receiving unit 20 includes the random value and the current NAS downlink COUNT value.
  • An MME is provided.
  • a block diagram of the MME is shown in FIG. 9 , which includes a count value obtaining unit 31 , a second deriving unit 32 , and a handover sending unit 33 .
  • the count value obtaining unit 31 is configured to obtain a new NAS downlink COUNT value.
  • an NAS message may be sent to a UE, such as an NAS SMC message, so that the currently saved NAS downlink COUNT value may be added by 1, and the NAS downlink COUNT value after the NAS message is sent may be used as the new NAS downlink COUNT value.
  • a certain value, such as 1, may be added to the current NAS downlink COUNT value.
  • the second deriving unit 32 is configured to derive a key of the UE in a target UTRAN according to a KDF, a root key, and the new NAS downlink COUNT value that is obtained by the count value obtaining unit 31 .
  • the handover sending unit 33 is configured to send the new NAS downlink COUNT value obtained by the count value obtaining unit 31 to the UE through a BS where the UE currently locates, so that the UE derives the key in the target UTRAN.
  • the MME may further include: a determination unit 34 , configured to determine whether the key of the UE in the target UTRAN is currently saved; and if yes, further determine whether the NAS downlink COUNT value corresponding to the currently saved key of the UE in the target UTRAN is consistent with the current NAS downlink COUNT value.
  • a determination unit 34 configured to determine whether the key of the UE in the target UTRAN is currently saved; and if yes, further determine whether the NAS downlink COUNT value corresponding to the currently saved key of the UE in the target UTRAN is consistent with the current NAS downlink COUNT value.
  • the count value obtaining unit 31 obtains the new NAS downlink COUNT value.
  • the count value obtaining unit 31 in the MME obtains the new NAS downlink COUNT value different from the current NAS downlink COUNT value; and finally the second deriving unit 32 derives the key of the UE in the target UTRAN according to the KDF, the root key, and the new NAS downlink COUNT value, and the handover sending unit 33 sends the new NAS downlink COUNT value to the UE.
  • the key derived by the MME in the second handover process is surely different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • the MME further includes the determination unit 34 for consistency determination. If the consistency determination result is inconsistent, the current NAS downlink COUNT value may be used to derive the key; if the consistency determination result is positive, the key is derived after the count value obtaining unit 31 obtains the new NAS downlink COUNT value. Therefore, the obtaining of the new NAS downlink COUNT value is reduced when the consistency determination result is inconsistent, thereby saving the load of the MME.
  • a UE is provided.
  • a block diagram of the UE is shown in FIG. 10 , which includes a second message receiving unit 40 and a second key deriving unit 41 .
  • the second message receiving unit 40 is configured to receive a Handover Command message, in which the Handover Command message includes a new NAS downlink COUNT value.
  • the second key deriving unit 41 is configured to derive a key of the UE in a target UTRAN according to a KDF, a root key, and the new NAS downlink COUNT value in the Handover Command message received by the second message receiving unit 40 .
  • An MME is provided.
  • a block diagram of the MME is shown in FIG. 11 , which includes a handover receiving unit 50 and a third deriving unit 51 .
  • the handover receiving unit 50 is configured to receive a Handover Required message, in which the Handover Required message includes a fresh value of a UE.
  • the third deriving unit 51 is configured to use a root key and the fresh value of the UE in the Handover Required message received by the handover receiving unit 50 as input parameters of a KDF to derive the key of the UE in a target UTRAN, or use a current NAS downlink COUNT value, the root key, and the fresh value of the UE in the Handover Required message received by the handover receiving unit 50 as the input parameters of the KDF to derive the key of the UE in the target UTRAN.
  • the third deriving unit 51 derives the key according to the fresh value of the UE included in the Handover Required message, so that in the handover process of the UE from the EUTRAN to the UTRAN, after the first handover fails, the key derived by the MME in the second handover process is surely different from the key derived in the first handover process, therefore avoiding the situation in the prior art and enhancing the network security.
  • a BS is provided.
  • a block diagram of the BS is shown in FIG. 12 , which includes a reestablishment receiving unit 60 and a sending and deriving unit 61 .
  • the reestablishment receiving unit 60 is configured to receive an RRC Connection Reestablishment Request message, in which the RRC Connection Reestablishment Request message includes a fresh value of a UE.
  • the sending and deriving unit 61 is configured to send the fresh value of the UE included in the RRC Connection Reestablishment Request message received by the reestablishment receiving unit 60 to an MME through a Handover Required message when a second handover of the UE is determined, so as to facilitate the MME to derive the key of the UE in the target UTRAN.
  • a UE is provided.
  • a block diagram of the UE is shown in FIG. 13 , which includes a reestablishment sending unit 71 and a third key deriving unit 72 .
  • the reestablishment sending unit 71 is configured to send an RRC Connection Reestablishment Request message, in which RRC Connection Reestablishment Request message includes a fresh value of a UE.
  • the third key deriving unit 72 is configured to use the fresh value of the UE and a root key as input parameters of a KDF to derive the key of the UE in a target UTRAN when receiving a Handover Command message, and to use the fresh value of the UE, a current NAS downlink COUNT value, and the root key as the input parameters of the KDF to derive the key of the UE in the target UTRAN if the Handover Command message includes the current NAS downlink COUNT value.
  • An MME is provided.
  • a block diagram of the MME is shown in FIG. 14 , which includes a message receiving unit 81 and a count value changing unit 82 .
  • the message receiving unit 81 is configured to receive a Forward Relocation Response message sent by a target SGSN.
  • the count value changing unit 82 is configured to change a current NAS downlink COUNT value and save the changed NAS downlink COUNT value after sending a Handover Command message to a UE, in which the changed NAS downlink COUNT value is used to derive a key of the UE in a target UTRAN.
  • the handover can be performed.
  • the count value changing unit 82 sends the Handover Command message, the current NAS downlink COUNT value is changed.
  • the MME uses the NAS downlink COUNT value saved in the MME for deriving the key, which guarantees that the NAS downlink COUNT value is different from the NAS downlink COUNT value used in the first handover, so that the keys derived and calculated in the two handovers are different. Therefore, the purpose of enhancing the network security is achieved.
  • a communication system which includes an MME.
  • the MME is similar to any one of the MMEs in Device Embodiments 1, 3, 5 and 8, and the key derivation method according to the above embodiments may be performed.
  • the communication system further includes other devices such as a UE and a BS, and the network security can be enhanced through the communication between the UE and the BS.
  • the key derivation method, device, and system according to the embodiments of the present invention are applicable to the handover process of the UE from the EUTRAN to the UTRAN. From the failure of the first handover to the second handover, it is guaranteed that the key derived on the source MME in the first handover process of the UE is different from the key derived on the MME in the second handover process of the UE by changing the input parameters used in the key derivation by the MME, such as generating the random value, changing the current NAS downlink COUNT value, and obtaining the fresh value of the UE, so as to prevent the situation in the prior art that once the key used on one RNC is obtained, the keys on other RNCs can be derived accordingly, thereby enhancing the network security.
  • the program may be stored in a computer readable storage medium, such as a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
  • ROM Read Only Memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
US13/323,840 2009-06-26 2011-12-13 Method, device, and system for deriving keys Active US11240019B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/583,013 US20220150062A1 (en) 2009-06-26 2022-01-24 Method, device, and system for deriving keys

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN200910148423.7 2009-06-26
CN2009101484237A CN101931951B (zh) 2009-06-26 2009-06-26 密钥推演方法、设备及系统
PCT/CN2010/074559 WO2010149083A1 (zh) 2009-06-26 2010-06-26 密钥推演方法、设备及系统

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/074559 Continuation WO2010149083A1 (zh) 2009-06-26 2010-06-26 密钥推演方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/583,013 Continuation US20220150062A1 (en) 2009-06-26 2022-01-24 Method, device, and system for deriving keys

Publications (2)

Publication Number Publication Date
US20120077501A1 US20120077501A1 (en) 2012-03-29
US11240019B2 true US11240019B2 (en) 2022-02-01

Family

ID=43370806

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/323,840 Active US11240019B2 (en) 2009-06-26 2011-12-13 Method, device, and system for deriving keys
US17/583,013 Pending US20220150062A1 (en) 2009-06-26 2022-01-24 Method, device, and system for deriving keys

Family Applications After (1)

Application Number Title Priority Date Filing Date
US17/583,013 Pending US20220150062A1 (en) 2009-06-26 2022-01-24 Method, device, and system for deriving keys

Country Status (9)

Country Link
US (2) US11240019B2 (es)
EP (4) EP2658300B1 (es)
CN (1) CN101931951B (es)
AU (1) AU2010265281B2 (es)
BR (1) BR112012000658B1 (es)
ES (1) ES2436552T5 (es)
PL (1) PL3651490T3 (es)
RU (1) RU2517410C2 (es)
WO (1) WO2010149083A1 (es)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220150062A1 (en) * 2009-06-26 2022-05-12 Huawei Technologies Co., Ltd. Method, device, and system for deriving keys

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2472580A (en) * 2009-08-10 2011-02-16 Nec Corp A system to ensure that the input parameter to security and integrity keys is different for successive LTE to UMTS handovers
CN101835152A (zh) * 2010-04-16 2010-09-15 中兴通讯股份有限公司 终端移动到增强utran时建立增强密钥的方法及系统
CN101841810B (zh) * 2010-06-07 2016-01-20 中兴通讯股份有限公司 空中接口密钥的更新方法、核心网节点及无线接入系统
CN102625300B (zh) 2011-01-28 2015-07-08 华为技术有限公司 密钥生成方法和设备
CN102790965B (zh) * 2011-05-18 2016-09-14 华为技术有限公司 切换方法、基站、用户设备和移动管理实体
JP6135878B2 (ja) 2012-05-04 2017-05-31 ▲ホア▼▲ウェイ▼技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ネットワークスイッチング中におけるセキュリティ処理方法およびシステム
CN104322089A (zh) 2012-05-23 2015-01-28 诺基亚公司 用于蜂窝网络的控制下的本地接入的密钥导出方法和设备
US9088408B2 (en) * 2012-06-28 2015-07-21 Certicom Corp. Key agreement using a key derivation key
CN104737570B (zh) 2012-10-19 2018-08-31 诺基亚技术有限公司 生成用于第一用户设备和第二用户设备之间的设备对设备通信的密钥的方法和设备
CN103906049B (zh) 2012-12-28 2019-09-24 北京三星通信技术研究有限公司 一种同步辅小区和ue之间加密信息的方法
DE102013227087A1 (de) * 2013-12-23 2015-06-25 Siemens Aktiengesellschaft Gesichertes Bereitstellen eines Schlüssels
EP3248404B1 (en) * 2015-01-19 2020-07-22 Telefonaktiebolaget L M Ericsson (publ) Method and apparatus for direct communication key establishment
CN106134231B (zh) * 2015-02-28 2019-10-01 华为技术有限公司 密钥生成方法、设备及系统
US10602411B2 (en) * 2015-07-02 2020-03-24 Qualcomm Incorporated Redirection in a neutral-host network
KR102437619B1 (ko) * 2016-04-01 2022-08-29 삼성전자주식회사 보안 키를 생성하기 위한 장치 및 방법
US10462837B2 (en) * 2016-11-04 2019-10-29 Qualcomm Incorporated Method, apparatus, and system for reestablishing radio communication links due to radio link failure
KR102163343B1 (ko) 2017-01-30 2020-10-08 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) 유휴 모드 동안의 5g에서의 보안 콘텍스트 취급
WO2018137824A1 (en) 2017-01-30 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses, computer programs and carriers for security management before handover from 5g to 4g system
US10542428B2 (en) 2017-11-20 2020-01-21 Telefonaktiebolaget Lm Ericsson (Publ) Security context handling in 5G during handover
JP2021524167A (ja) * 2018-01-12 2021-09-09 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ 複数の登録のための方法および装置
US11553381B2 (en) * 2018-01-12 2023-01-10 Qualcomm Incorporated Method and apparatus for multiple registrations
CN110769417B (zh) * 2018-07-25 2021-03-23 华为技术有限公司 一种密钥生成方法及装置
CN111465012B (zh) * 2019-01-21 2021-12-10 华为技术有限公司 通信方法和相关产品

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6918035B1 (en) 1998-07-31 2005-07-12 Lucent Technologies Inc. Method for two-party authentication and key agreement
WO2006120316A1 (fr) 2005-05-13 2006-11-16 France Telecom Procede de communication pour reseaux sans fil par trames de gestion comportant une signature electronique
US20070192594A1 (en) 2005-01-11 2007-08-16 Ji-Cheol Lee Apparatus and method for ciphering/deciphering a signal in a communication system
US7260721B2 (en) * 2001-02-09 2007-08-21 Sony Corporation Information processing method, information processing apparatus and recording medium
CN101094065A (zh) 2006-06-23 2007-12-26 华为技术有限公司 无线通信网络中的密钥分发方法和系统
US20080137853A1 (en) * 2006-12-08 2008-06-12 Mizikovsky Semyon B Method of providing fresh keys for message authentication
CN101232731A (zh) 2008-02-04 2008-07-30 中兴通讯股份有限公司 用于ue从utran切换到eutran的密钥生成方法和系统
CN101232736A (zh) 2008-02-22 2008-07-30 中兴通讯股份有限公司 用于不同接入系统之间密钥生存计数器的初始化设置方法
CN101304311A (zh) 2008-06-12 2008-11-12 中兴通讯股份有限公司 密钥生成方法和系统
US20090022103A1 (en) * 2007-07-17 2009-01-22 Research In Motion Limited Dual-mode device and method for handover of session from voip interface to cellular interface
US20090025060A1 (en) * 2007-07-18 2009-01-22 Interdigital Technology Corporation Method and apparatus to implement security in a long term evolution wireless device
CN101355507A (zh) 2008-09-12 2009-01-28 中兴通讯股份有限公司 更新跟踪区时的密钥生成方法及系统
US20090111428A1 (en) * 2007-10-29 2009-04-30 Nokia Corporation System and Method for Authenticating a Context Transfer
RU2373653C2 (ru) 2003-09-12 2009-11-20 Сикьюред Имэйл Гетеборг Аб Безопасность сообщений
US20100098247A1 (en) * 2008-10-20 2010-04-22 Nokia Corporation Method, Apparatus And Computer Program Product For Generating An Encryption Key And An Authentication Code Key Utilizing A Generic Key Counter
US20110092213A1 (en) * 2008-06-13 2011-04-21 Nokia Corporation Methods, apparatuses, and computer program products for providing fresh security context during intersystem mobility

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7875396B2 (en) † 2006-06-29 2011-01-25 GM Global Technology Operations LLC Membrane humidifier for a fuel cell
US9769852B2 (en) * 2009-04-23 2017-09-19 Telefonaktiebolaget Lm Ericsson (Publ) Maintaining current cell location information in a cellular access network
CN101931951B (zh) * 2009-06-26 2012-11-07 华为技术有限公司 密钥推演方法、设备及系统

Patent Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6918035B1 (en) 1998-07-31 2005-07-12 Lucent Technologies Inc. Method for two-party authentication and key agreement
US7260721B2 (en) * 2001-02-09 2007-08-21 Sony Corporation Information processing method, information processing apparatus and recording medium
RU2373653C2 (ru) 2003-09-12 2009-11-20 Сикьюред Имэйл Гетеборг Аб Безопасность сообщений
RU2007126323A (ru) 2005-01-11 2009-01-20 Самсунг Электроникс Ко., Лтд. (KR) Устройство и способ для шифрования/дешифрования сигнала в системе связи
US20070192594A1 (en) 2005-01-11 2007-08-16 Ji-Cheol Lee Apparatus and method for ciphering/deciphering a signal in a communication system
WO2006120316A1 (fr) 2005-05-13 2006-11-16 France Telecom Procede de communication pour reseaux sans fil par trames de gestion comportant une signature electronique
CN101094065A (zh) 2006-06-23 2007-12-26 华为技术有限公司 无线通信网络中的密钥分发方法和系统
US20080137853A1 (en) * 2006-12-08 2008-06-12 Mizikovsky Semyon B Method of providing fresh keys for message authentication
US20090022103A1 (en) * 2007-07-17 2009-01-22 Research In Motion Limited Dual-mode device and method for handover of session from voip interface to cellular interface
US20090025060A1 (en) * 2007-07-18 2009-01-22 Interdigital Technology Corporation Method and apparatus to implement security in a long term evolution wireless device
US20090111428A1 (en) * 2007-10-29 2009-04-30 Nokia Corporation System and Method for Authenticating a Context Transfer
WO2009056938A2 (en) 2007-10-29 2009-05-07 Nokia Corporation System and method for authenticating a context transfer
CN101232731A (zh) 2008-02-04 2008-07-30 中兴通讯股份有限公司 用于ue从utran切换到eutran的密钥生成方法和系统
CN101232736A (zh) 2008-02-22 2008-07-30 中兴通讯股份有限公司 用于不同接入系统之间密钥生存计数器的初始化设置方法
CN101304311A (zh) 2008-06-12 2008-11-12 中兴通讯股份有限公司 密钥生成方法和系统
EP2293609A1 (en) 2008-06-12 2011-03-09 ZTE Corporation Method and system for generating keys
US20110222690A1 (en) * 2008-06-12 2011-09-15 Zte Corporation Method and system for deriving keys
US20110092213A1 (en) * 2008-06-13 2011-04-21 Nokia Corporation Methods, apparatuses, and computer program products for providing fresh security context during intersystem mobility
CN101355507A (zh) 2008-09-12 2009-01-28 中兴通讯股份有限公司 更新跟踪区时的密钥生成方法及系统
US20100098247A1 (en) * 2008-10-20 2010-04-22 Nokia Corporation Method, Apparatus And Computer Program Product For Generating An Encryption Key And An Authentication Code Key Utilizing A Generic Key Counter

Non-Patent Citations (22)

* Cited by examiner, † Cited by third party
Title
200910148423.7 Search report (the same as the first Chinese office action for Chinese application No. 200910148423.7, dated Jul. 1, 2011), 7 pages total.
3GPP TS 23.216 V8.0.0,3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Single Radio Voice Call Continuity (SRVCC);Stage 2(Release 8),Jun. 2008,total 20 pages.
3GPP TS 23.216 V8.2.0 Release 8, 3rd Generation Partnership Project; Digital Cellular Telecommunications System (phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Single Radio Voice Call Continuity (SRVCC); Jan. 2009; pp. 17-19. *
3GPP TS 24.301 V8.0.0,3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Non-Access-Stratum (NAS) protocolfor Evolved Packet System (EPS);Stage 3(Release 8),Dec. 2008, total 221 pages.
3GPP TS 24.301 V8.2.1,3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS);Stage 3(Release 8),Jun. 2009,total 252 pages.
3GPP TS 33.401 V8.3.1, "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE): Security architecture; (Release 8)," Mar. 2009,total 61 pages.
3GPP TS 33.401 V8.4.0: "3rd Generation Partnership Project; Specification Group Services and System Aspects 3GPP System Architecture Evolution (SAE): Security architecture; (Release 8)", Jun. 2009, 95 pages total.
3GPP TSG SA WG3 Security-S3#52 S3-080840, Change Request, "IRAT key freshness from UTRAN to E-UTRAN",Nokia Corporation,Jun. 23-27, 2008,total 7 pages.
3GPP TSG-SA WG3 Meeting S3#55 meeting,S3-091060,"Correction of EPS AS/NAS Security Context definition", Shanghai, P.R. China, Apr. 11-15, 2009,5 pages total.
3GPP TSG-SA3 (Security),S3-091070,Meeting SA3#55, May 11-15, 2009, Shanghai, China,"Rules on concurrent runs of security procedures",Meeting SA3#55, May 11-15, 2009, Shanghai, China,2 pages total.
Chinese office action for Chinese application No. 200910148423.7, dated Jul. 1, 2011,and an English translation thereof,total 11 pages.
Cover page of issued Chinese patent CN 101931951B wherein the references are cited in item 56, Nov. 7, 2012, 1 page only.
Gan Lu, Method and System For Generating A Key, Nov. 12, 2008, English Translation of Chinese Patent Application 200810120667.1, pp. 5-7. *
International search report for International application No. PCT/CN2010/074559, dated Oct. 28, 2010, total 4 pages.
Nokia Corporation et al., 3GPP TSG SA WG3 Security—S3#52, S3-080838: "Key freshness during mobility from E-UTRAN to UTRAN/GERAN," Sophia-Antipolis, France, Jun. 23-27, 2008, 8 pages total.
Nokia Corporation,3GPP 33.401 CR, Sep. 24, 2008, 3GPP TSG-SA WG3 Meeting #52bis. *
Office action issued in corresponding Australia application No. 2010265281,dated May 10, 2013,total 3 pages.
Office action issued in corresponding Russian application No. 2012102647, dated Feb. 5, 2013, and English translation thereof, total 15 pages.
Qualcomm Europe, 3GPP TSG SA WG3 Security—SA3 ad hoc, S3-091729: "Ensuring key freshness at handover from E-UTRAN to UTRAN/GERAN (Rel-9)," Sophia Antipolis, France, Sep. 28-30, 2009, 6 pages total.
Qualcomm Europe, 3GPP TSG SA3 (Security), S3-091477: "Key freshness at E-UTRAN to UTRAN handover," Seattle, USA, Jul. 6-10, 2009, 1 page only.
Search report of corresponding European Patent Application No. EP10791589.4, dated May 2, 2012, 9 pages total.
Written opinion of corresponding PCT Patent Application No. PCT/CN2010/074559, dated Sep. 26, 2010, 3 pages total.

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220150062A1 (en) * 2009-06-26 2022-05-12 Huawei Technologies Co., Ltd. Method, device, and system for deriving keys

Also Published As

Publication number Publication date
EP2416598A4 (en) 2012-05-30
ES2436552T3 (es) 2014-01-02
EP3654684B1 (en) 2022-01-19
EP3651490B1 (en) 2021-08-04
RU2517410C2 (ru) 2014-05-27
EP2416598B2 (en) 2020-07-29
EP3654684A1 (en) 2020-05-20
US20220150062A1 (en) 2022-05-12
EP2658300A3 (en) 2014-01-22
PL3651490T3 (pl) 2022-01-10
CN101931951B (zh) 2012-11-07
CN101931951A (zh) 2010-12-29
EP2658300B1 (en) 2019-09-18
BR112012000658A2 (pt) 2016-11-16
BR112012000658B1 (pt) 2021-06-22
EP2416598B1 (en) 2013-08-28
WO2010149083A1 (zh) 2010-12-29
AU2010265281A1 (en) 2011-12-01
EP3651490A1 (en) 2020-05-13
EP2658300A2 (en) 2013-10-30
AU2010265281B2 (en) 2013-10-31
EP2416598A1 (en) 2012-02-08
ES2436552T5 (es) 2021-04-08
RU2012102647A (ru) 2013-08-10
US20120077501A1 (en) 2012-03-29

Similar Documents

Publication Publication Date Title
US20220150062A1 (en) Method, device, and system for deriving keys
US11632670B2 (en) Method and arrangement in a telecommunication system
EP3917187A1 (en) Security implementation method and related apparatus
EP2461626B1 (en) Key derivation
US8656169B2 (en) Method, system and device for negotiating security capability when terminal moves
US20170359719A1 (en) Key generation method, device, and system
US8452007B2 (en) Security key generating method, device and system
US8750515B2 (en) Method and system for generating an identifier of a key
US20100172500A1 (en) Method of handling inter-system handover security in wireless communications system and related communication device
US9398510B2 (en) Handover method, base station, user equipment, and mobility management entity
CN103139771A (zh) 切换过程中密钥生成方法及系统
CN103379564B (zh) 一种小区内切换方法及装置
CN101645877A (zh) 密钥衍生函数的协商方法、系统及网络节点
CN114642014B (zh) 一种通信方法、装置及设备
CN102917350A (zh) 启用安全密钥的方法，接入网节点、用户设备和系统
WO2010105442A1 (zh) 密钥推演参数的生成方法、装置和系统
CN102595397B (zh) 防止网络安全失步的方法和装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHANG, AIQIN;CHEN, JING;BI, XIAOYU;REEL/FRAME:027377/0357

Effective date: 20110924

STCV Information on status: appeal procedure

Free format text: NOTICE OF APPEAL FILED

STCV Information on status: appeal procedure

Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER

STCV Information on status: appeal procedure

Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: TC RETURN OF APPEAL

STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION

STCV Information on status: appeal procedure

Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS

STCV Information on status: appeal procedure

Free format text: BOARD OF APPEALS DECISION RENDERED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE