WO2022088029A1 - 密钥获取方法和通信装置 - Google Patents

密钥获取方法和通信装置 Download PDF

Info

Publication number
WO2022088029A1
WO2022088029A1 PCT/CN2020/125224 CN2020125224W WO2022088029A1 WO 2022088029 A1 WO2022088029 A1 WO 2022088029A1 CN 2020125224 W CN2020125224 W CN 2020125224W WO 2022088029 A1 WO2022088029 A1 WO 2022088029A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
network element
identifier
key
remote
Prior art date
Application number
PCT/CN2020/125224
Other languages
English (en)
French (fr)
Inventor
吴义壮
Original Assignee
华为技术有限公司
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CA3197006A priority Critical patent/CA3197006A1/en
Priority to EP20959191.6A priority patent/EP4224777A4/en
Priority to PCT/CN2020/125224 priority patent/WO2022088029A1/zh
Priority to CN202080106820.2A priority patent/CN116458109A/zh
Publication of WO2022088029A1 publication Critical patent/WO2022088029A1/zh
Priority to US18/309,567 priority patent/US20230319556A1/en

Links

Images

Classifications

    • 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/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431—Key distribution or pre-distribution; Key agreement
    • 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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/75—Temporary identity
    • 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/42—Anonymization, e.g. involving pseudonyms
    • 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/76—Proxy, i.e. using intermediary entity to perform cryptographic operations
    • 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
    • H04L2209/805—Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption

Definitions

  • the present application relates to the field of communications, and in particular, to a key acquisition method and a communication device.
  • D2D communication allows direct communication between terminal devices, and can share spectrum resources with cell users under the control of a cell network, thereby effectively improving the utilization rate of spectrum resources.
  • the remote terminal equipment can use the relay terminal equipment (Relay UE).
  • Auxiliary communication that is, establishing a PC5 connection between the remote terminal equipment and the relay terminal equipment, establishing a connection between the relay terminal equipment and the mobile network, and realizing the connection between the remote terminal equipment and the mobile network through the PC5 connection and the relay terminal equipment. Get service.
  • a secure connection needs to be established between the remote terminal device and the relay terminal device, that is, the data transmitted between the remote terminal device and the relay terminal device is encrypted and protected. / or integrity protection. Since the indirect communication connection is dynamically established on demand, the shared security information (such as keys) cannot be preconfigured between the remote terminal device and the relay terminal device, and the remote terminal device cannot be established based on the preconfigured shared security information. Secure connection to relay end devices.
  • Embodiments of the present application provide a key acquisition method and a communication device, which are used to share a key between a remote terminal device and a relay terminal device.
  • a method for obtaining a key including: a remote terminal device sends a first identifier and a relay service code to a relay terminal device, and the first identifier is a remote terminal device corresponding to the relay service code.
  • the identifier or the first identifier is an anonymous identifier of the remote terminal device; the remote terminal device generates the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter
  • the root key of communication, the remote authentication service function network element is the authentication service function network element serving the remote terminal device, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element.
  • the remote terminal device sends a first identifier and a relay service code to the relay terminal device, where the first identifier is the identifier of the remote terminal device corresponding to the relay service code or the first identifier. It is the anonymous identifier of the remote terminal device.
  • the remote terminal device generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter.
  • the first identifier is used for the remote AUSF network element to determine the corresponding first shared key, or for the PKMF network element to determine the corresponding second shared key, and the second shared key is also determined by the first shared key and/or relay service code generation, so that the remote terminal device and the remote AUSF network element or PKMF network element can use the same method to generate the root key for the communication between the remote terminal device and the relay terminal device, so that the remote terminal device can communicate with the relay terminal device.
  • the key is shared between the terminal device and the relay terminal device.
  • the first identifier is the subscription hidden identifier SUCI of the remote terminal device.
  • the SUPI of the remote terminal device will not be exposed during the air interface transmission.
  • the method further includes: acquiring the first identifier by the remote terminal device.
  • acquiring the first identifier by the remote terminal device includes: sending the relay service code by the remote terminal device; and receiving the first identifier corresponding to the relay service code by the remote terminal device.
  • the first identifier corresponding to the relay service code may be acquired from the remote AUSF network element.
  • the method further includes: the remote terminal device generates a temporary identifier according to the first shared key and the relay service code; and the remote terminal device obtains the first identifier according to the temporary identifier.
  • This embodiment discloses one way of generating the first identification.
  • the remote terminal device generates the temporary identifier according to the first shared key and the relay service code, including: the remote terminal device generates the temporary identifier according to the first shared key, the relay service code and the second freshness parameter to generate a temporary ID.
  • This embodiment discloses a way of generating a temporary identification.
  • acquiring the first identifier by the remote terminal device includes: the remote terminal device generates the first identifier according to the second freshness parameter, the routing indication and the home network identifier. This embodiment discloses one way of generating the first identification.
  • the method further includes: the remote terminal device sends a relay service code; and the remote terminal device receives a second freshness parameter corresponding to the relay service code.
  • the second freshness parameter may come from the remote AUSF network element and is used to generate the first identifier, and the second freshness parameter may be a random number generated by the remote AUSF network element or a value of a counter maintained locally by the remote AUSF network element.
  • the second freshness parameter is the value of a counter maintained locally by the remote terminal device.
  • the same initial value and counting rule are used to keep the values of the two counters consistent.
  • the first identifier includes a routing indication and a home network identifier. It is convenient for the PKMF network element to determine the UDM network element or the remote AUSF network element through the routing instruction and the home network identifier.
  • the method further includes: the remote terminal device sends first verification information to the relay terminal device, where the first verification information consists of a first temporary key, and all or all of the messages carrying the first verification information or Part of the cell is generated, and the first temporary key is generated from the first shared key.
  • the first verification information is used to send to the remote AUSF network element.
  • the remote AUSF network element After receiving the first verification information, the remote AUSF network element generates third verification information in the same manner as the remote terminal device, and the remote AUSF network element compares the first verification information. information and third verification information to verify the remote terminal device and verify whether the remote terminal device is authorized to access the network through the relay terminal device to obtain services.
  • the first temporary key is composed of at least one of the relay service code, the third freshness parameter, the second identifier of the remote terminal device, and the first identifier, and the first shared secret key.
  • key generation wherein the third freshness parameter is generated by the remote terminal device.
  • the method further includes: the remote terminal device sends second verification information to the relay terminal device, where the second verification information is generated from the first freshness parameter, the relay service code and the first shared key.
  • the second verification information is used for sending to the PKMF network element.
  • the PKMF network element After receiving the second verification information, the PKMF network element generates fourth verification information in the same manner as the remote terminal device, and the PKMF network element compares the second verification information with the fourth verification information In order to verify the remote terminal equipment, it is verified whether the remote terminal equipment is authorized to access the network through the relay terminal equipment to obtain services.
  • the at least one first freshness parameter includes a first random number, and further includes: the remote terminal device sends the first random number to the relay terminal device.
  • the first random number is sent to the remote AUSF network element or the PKMF network element.
  • the at least one first freshness parameter includes a second random number, and further includes: the remote terminal device receives the second random number from the relay terminal device.
  • the second random number may come from a remote AUSF network element or a PKMF network element.
  • the at least one first freshness parameter is the value of a counter maintained locally by the remote terminal device.
  • the same initial value and counting rule are used to keep the values of the two counters consistent.
  • the first shared key is the key Kausf (or another key generated by the key) negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • the remote terminal device generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter , including: the remote terminal device generates a second shared key according to the first shared key and the relay service code, and generates a root key according to the second shared key and at least one first freshness parameter, and the second shared key It is the key shared by the remote terminal device and the adjacent service key management function network element.
  • the remote terminal device and the PKMF network element generate the root key in the same way.
  • a method for obtaining a key including: a network element with a remote authentication service function obtains one of a first identifier or a second identifier of a remote terminal device, and a relay service code; the second identifier is The permanent identity identifier of the remote terminal device, the first identifier is the identifier corresponding to the relay service code of the remote terminal device; the remote authentication service function network element obtains the first shared key corresponding to the first identifier or the second identifier; The first shared key is a key shared by the remote terminal device and the remote authentication service function network element; the remote authentication service function network element is based on the first shared key, the relay service code, and at least one first freshness parameters to generate the root key for communication between the remote terminal device and the relay terminal device; the remote authentication service function network element sends the root key.
  • the remote AUSF network element acquires one of the first identifier or the second identifier of the remote terminal device, and the relay service code; the second identifier is the permanent identifier of the remote terminal device.
  • the first identifier is the identifier corresponding to the relay service code of the remote terminal device; the remote AUSF network element obtains the first shared key corresponding to the first identifier or the second identifier; the first shared key is the remote The key shared by the terminal device and the remote AUSF network element; the remote AUSF network element generates the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter The root key of the communication; the remote AUSF sends the root key.
  • the first identifier is used by the remote AUSF network element to determine the corresponding first shared key, so that the remote terminal device and the remote AUSF network element can use the same method to generate the root of the communication between the remote terminal device and the relay terminal device.
  • the key is shared between the remote terminal device and the relay terminal device.
  • the remote authentication service function network element acquiring one of the first identifier or the second identifier of the remote terminal device includes: the remote authentication service function network element receiving the first identifier of the remote terminal device. one of the ID or the second ID.
  • One of the first identification or the second identification of the remote terminal equipment may come from the remote terminal equipment or a PKMF network element.
  • the remote authentication service function network element acquiring one of the first identifier or the second identifier of the remote terminal device includes: the remote authentication service function network element according to the first shared key, the middle Following the service code, a temporary identification is generated; the network element of the remote authentication service function generates a first identification according to the temporary identification.
  • This embodiment discloses one way of generating the first identification. After the first identifier is generated, it can be sent to the remote terminal device.
  • the network element of the remote authentication service function generates the temporary identifier according to the first shared key and the relay service code, including: the remote terminal device according to the first shared key, the relay service code and the The second freshness parameter generates a temporary identifier.
  • This embodiment discloses a way of generating a temporary identification.
  • the remote authentication service function network element acquiring one of the first identifier or the second identifier of the remote terminal device includes: the remote authentication service function network element according to the second freshness parameter, route Indicates and the home network identifier of the remote terminal device to generate the first identifier.
  • This embodiment discloses one way of generating the first identification. After the first identifier is generated, it can be sent to the remote terminal device.
  • the second freshness parameter is a value of a counter maintained locally by the remote authentication service function network element.
  • the remote AUSF network element and the remote terminal device maintain their respective counters locally, the same initial value and counting rule are used to keep the values of the two counters consistent.
  • the method further includes: the remote authentication service function network element receives the relay service code; and the remote authentication service function network element sends the second freshness parameter.
  • the second freshness parameter may be sent to the remote terminal device for generating the first identifier, and the second freshness parameter may be a random number generated by the remote AUSF network element or a value of a counter maintained locally by the remote AUSF network element.
  • the method further includes: the remote authentication service function network element receives the relay service code; and the remote authentication service function network element sends the first identifier.
  • the relay service code comes from the remote terminal device, and the first identifier is used for sending to the remote terminal device.
  • the first identifier includes a routing indication and a home network identifier. It is convenient for the PKMF network element to determine the UDM network element or the remote AUSF network element through the routing instruction and the home network identifier.
  • the method further includes: the remote authentication service function network element receives the first verification information; the remote authentication service function network element generates a first temporary key according to the first shared key; The temporary key, and all or part of the information elements of the message carrying the first verification information, obtain the third verification information; the remote authentication service function network element compares the first verification information and the third verification information to perform verification on the remote terminal equipment. verify. That is, it is verified whether the remote terminal device is authorized to access the network through the relay terminal device to obtain services.
  • the remote authentication service function network element generates the first temporary key according to the first shared key, including: the remote authentication service function network element generates the first temporary key according to the relay service code, the third freshness parameter , at least one of the second identifier and the first identifier of the remote terminal device, and the first shared key to generate the first temporary key, and the third freshness parameter is generated for the remote terminal device.
  • This embodiment discloses one way of generating the first temporary key.
  • the at least one first freshness parameter includes a first random number, and further includes: the remote authentication service function network element receiving the first random number.
  • the first random number comes from the remote terminal device.
  • the at least one first freshness parameter includes a second random number, and further includes: sending the second random number by the remote authentication service function network element. The second random number is sent to the remote terminal device.
  • the at least one first freshness parameter is the value of a counter maintained locally by the remote authentication service function network element.
  • the remote AUSF network element and the remote terminal device maintain their respective counters locally, the same initial value and counting rule are used to keep the values of the two counters consistent.
  • the method further includes: the remote authentication service function network element sends the first identifier to the unified data management network element. It is used for other network elements (eg, PKMF network elements) to obtain the remote AUSF network element instance identifier and/or the SUPI of the remote terminal equipment from the UDM network element.
  • the remote AUSF network element instance identifier is used to determine the remote AUSF network element serving the remote terminal equipment.
  • the first shared key is the key Kausf (or another key generated by the key) negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • a method for obtaining a key comprising: a network element with a key management function of a nearby service receives a first identifier and a relay service code of a remote terminal device, and the first identifier is the connection between the remote terminal device and the relay.
  • the identifier corresponding to the service code or the first identifier is the anonymous identifier of the remote terminal device; the adjacent service key management function network element obtains the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, and the root key is determined by The first shared key, the relay service code, and at least one first freshness parameter are generated, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element; adjacent service key management The functional network element sends the root key.
  • the PKMF network element receives the first identifier and the relay service code of the remote terminal device, and the first identifier is the identifier of the remote terminal device corresponding to the relay service code or the first identifier is the anonymous identifier of the remote terminal device; the PKMF network element obtains the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, and the root key consists of the first shared key, the relay service code, and at least A first freshness parameter is generated, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element; the PKMF network element sends the root key.
  • the first identifier is used by the PKMF network element to determine the corresponding second shared key, so that the remote terminal device and the PKMF network element can use the same method to generate the root key for the communication between the remote terminal device and the relay terminal device, so as to realize The key is shared between the remote terminal equipment and the relay terminal equipment.
  • the network element of the adjacent service key management function obtains the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, including: the adjacent service key management function network element to the unified data
  • the management function network element sends the first identification; the adjacent service key management function network element receives the identification information of the remote authentication service function network element from the unified data management function network element; the adjacent service key management function network element sends the corresponding identification information to the corresponding network element.
  • the remote authentication service function network element sends the first identifier; the adjacent service key management function network element receives the root key from the remote authentication service function network element.
  • the network element of the adjacent service key management function obtains the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, including: the adjacent service key management function network element to the unified data
  • the management function network element sends the first identification; the adjacent service key management function network element receives the identification information of the remote authentication service function network element and the permanent identification of the remote terminal equipment from the unified data management function network element; the adjacent service key management The functional network element sends the permanent identity identifier of the remote terminal device to the corresponding remote authentication service functional network element according to the identification information; the adjacent service key management functional network element receives the root key from the remote authentication service functional network element.
  • This embodiment discloses a way for the PKMF network element to obtain the root key.
  • the network element of the adjacent service key management function obtains the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, including: The authentication service function network element receives at least one second shared key, the second shared key is the key shared by the remote terminal device and the adjacent service key management function network element, and the second shared key consists of the first shared key and the The relay service code is generated; the adjacent service key management function network element generates a root key for the communication between the remote terminal device and the relay terminal device according to the second shared key corresponding to the first identifier and at least one first freshness parameter key.
  • This embodiment discloses a way for the PKMF network element to obtain the root key.
  • the method further includes: the adjacent service key management function network element receives the second verification information; the adjacent service key management function network element generates the fourth verification information according to the first freshness parameter and the second shared key. Verification information; the adjacent service key management function network element compares the second verification information and the fourth verification secret information to verify the remote terminal device. That is, it is verified whether the remote terminal device is authorized to access the network through the relay terminal device to obtain services.
  • the at least one first freshness parameter includes a first random number, and further includes: receiving the first random number by an adjacent service key management function network element.
  • the first random number comes from the remote terminal device.
  • the at least one first freshness parameter includes a second random number, and further includes: sending the second random number by an adjacent service key management function network element. The second random number is sent to the remote terminal device.
  • the at least one first freshness parameter is the value of a counter maintained locally by the network element of the adjacent service key management function.
  • the same initial value and counting rule are used to keep the values of the two counters consistent.
  • the first shared key is the key Kausf (or another key generated by the key) negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • a communication device including a transceiver module and a processing module; the transceiver module is used to send a first identifier and a relay service code to a relay terminal device, and the first identifier is a connection between the remote terminal device and the relay.
  • the identifier corresponding to the service code or the first identifier is the anonymous identifier of the remote terminal device; the processing module is configured to generate the remote terminal device according to the first shared key, the relay service code, and at least one first freshness parameter
  • the root key for communicating with the relay terminal device, the remote authentication service function network element is the authentication service function network element serving the remote terminal device, and the first shared key is shared by the remote terminal device and the remote authentication service function network element 's key.
  • the first identifier is the SUCI of the remote terminal device.
  • the processing module and the transceiver module are further configured to acquire the first identifier.
  • the transceiver module is further configured to send a relay service code; and receive a first identifier corresponding to the relay service code.
  • the processing module is further configured to generate a temporary identification according to the first shared key and the relay service code; and obtain the first identification according to the temporary identification.
  • the processing module is further configured to generate a temporary identifier according to the first shared key, the relay service code and the second freshness parameter.
  • the processing module is further configured to generate the first identifier according to the second freshness parameter, the routing indication and the home network identifier.
  • the transceiver module is further configured to send a relay service code; and receive a second freshness parameter corresponding to the relay service code.
  • the second freshness parameter is the value of a counter maintained locally by the remote terminal device.
  • the first identifier includes a routing indication and a home network identifier.
  • the transceiver module is further configured to send first verification information to the relay terminal device, where the first verification information consists of the first temporary key, and all or part of the information of the message carrying the first verification information meta-generated, the first temporary key is generated from the first shared key.
  • the first temporary key is composed of at least one of the relay service code, the third freshness parameter, the second identifier of the remote terminal device, and the first identifier, and the first shared secret key.
  • key generation wherein the third freshness parameter is generated by the remote terminal device.
  • the transceiver module is further configured to send second verification information to the relay terminal device, where the second verification information is generated from the first freshness parameter, the relay service code and the first shared key.
  • the at least one first freshness parameter includes a first random number
  • the transceiver module is further configured to send the first random number to the relay terminal device.
  • the first random number is sent to the remote AUSF network element or the PKMF network element.
  • the at least one first freshness parameter includes a second random number
  • the transceiver module is further configured to receive the second random number from the relay terminal device.
  • the second random number may come from a remote AUSF network element or a PKMF network element.
  • the at least one first freshness parameter is the value of a counter maintained locally by the remote terminal device.
  • the first shared key is the key Kausf negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • the processing module is further configured to generate a second shared key according to the first shared key and the relay service code, and generate a root key according to the second shared key and the at least one first freshness parameter
  • the second shared key is the key shared by the remote terminal device and the adjacent service key management function network element.
  • a communication device comprising a transceiver module and a processing module; the processing module is used to obtain one of a first identification or a second identification of a remote terminal device, and a relay service code; the second identification is The permanent identity identifier of the remote terminal device, the first identifier is the identifier corresponding to the relay service code of the remote terminal device; the processing module is further configured to obtain the first shared key corresponding to the first identifier or the second identifier; the first identifier
  • the shared key is a key shared by the remote terminal device and the remote authentication service function network element; the remote authentication service function network element, according to the first shared key, the relay service code, and at least one first freshness parameter,
  • the root key for communication between the remote terminal device and the relay terminal device is generated; the transceiver module is used for sending the root key.
  • the transceiver module is further configured to receive one of the first identifier or the second identifier of the remote terminal device.
  • the processing module is further configured to generate a temporary identifier according to the first shared key and the relay service code; the remote authentication service function network element generates the first identifier according to the temporary identifier.
  • the processing module is further configured to generate a temporary identifier according to the first shared key, the relay service code and the second freshness parameter.
  • the processing module is further configured to generate the first identifier according to the second freshness parameter, the routing indication and the home network identifier of the remote terminal device.
  • the second freshness parameter is a value of a counter maintained locally by the remote authentication service function network element.
  • the transceiver module is further configured to receive the relay service code and send the second freshness parameter.
  • the transceiver module is further configured to receive the relay service code; and send the first identifier.
  • the first identifier includes a routing indication and a home network identifier.
  • the transceiver module is further configured to receive the first verification information; the processing module is further configured to generate a first temporary key according to the first shared key; and according to the first temporary key, and carry All or part of the information elements of the message of the first verification information, obtain the third verification information; compare the first verification information and the third verification information to verify the remote terminal device.
  • the processing module is further configured to, according to at least one of the relay service code, the third freshness parameter, the second identifier, and the first identifier of the remote terminal device, and the first shared secret key to generate the first temporary key, and the third freshness parameter is generated for the remote terminal device.
  • the at least one first freshness parameter includes a first random number
  • the transceiver module is further configured to receive the first random number
  • the at least one first freshness parameter includes a second random number
  • the transceiver module is further configured to send the second random number
  • the at least one first freshness parameter is the value of a counter maintained locally by the remote authentication service function network element.
  • the transceiver module is further configured to send the first identifier to the unified data management network element.
  • the first shared key is the key Kausf negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • a communication device including a transceiver module and a processing module; the transceiver module is used to receive a first identifier and a relay service code of a remote terminal device, and the first identifier is a relay service of the remote terminal device.
  • the identifier corresponding to the code or the first identifier is the anonymous identifier of the remote terminal device; the processing module is used to obtain the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, and the root key is determined by the first shared key.
  • a relay service code, and at least one first freshness parameter is generated, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element; the transceiver module is also used for sending the root key.
  • the transceiver module is further configured to send the first identification to the unified data management function network element; receive identification information of the remote authentication service function network element from the unified data management function network element; The corresponding remote authentication service function network element sends the first identifier; and the root key is received from the remote authentication service function network element.
  • the transceiver module is further configured to send the first identification to the unified data management function network element; receive the identification information of the remote authentication service function network element and the identification information of the remote terminal equipment from the unified data management function network element Permanent identification; according to the identification information, send the permanent identification of the remote terminal device to the corresponding remote authentication service function network element; receive the root key from the remote authentication service function network element.
  • the transceiver module is further configured to receive at least one second shared key from the remote authentication service function network element, where the second shared key is the remote terminal device and the adjacent service key management function network element shared key, the second shared key is generated by the first shared key and the relay service code; the processing module is further configured to, according to the second shared key corresponding to the first identifier, and at least one first freshness parameter, Generate a root key for communication between the remote terminal device and the relay terminal device.
  • the method further includes: the transceiver module is further configured to receive second verification information; the processing module is further configured to generate fourth verification information according to the first freshness parameter and the second shared key; The verification information and the fourth verification secret information are used to verify the remote terminal device.
  • the at least one first freshness parameter includes a first random number
  • the transceiver module is further configured to receive the first random number
  • the at least one first freshness parameter includes a second random number
  • the transceiver module is further configured to send the second random number
  • the at least one first freshness parameter is the value of a counter maintained locally by the network element of the adjacent service key management function.
  • the first shared key is the key Kausf negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • a communication device comprising a processor, the processor is connected to a memory, the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory, so that the communication device performs the first aspect and its The method of any embodiment.
  • a communication device comprising a processor, the processor is connected to a memory, the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory, so that the communication device performs the second aspect and its The method of any one of the embodiments.
  • a communication device including a processor, the processor is connected to a memory, the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory, so that the communication device performs the third aspect and its The method of any one of the embodiments.
  • a computer-readable storage medium is provided, and a computer program is stored in the computer-readable storage medium, which, when executed on a computer, causes the computer to execute the first aspect and any one of the embodiments thereof. method.
  • a computer-readable storage medium is provided, and a computer program is stored in the computer-readable storage medium, which, when executed on a computer, causes the computer to execute as described in the second aspect and any one of the embodiments thereof Methods.
  • a twelfth aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, which, when executed on a computer, causes the computer to execute the method described in the third aspect and any one of the embodiments thereof Methods.
  • a thirteenth aspect provides a computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to perform the method of the first aspect and any one of the embodiments.
  • a fourteenth aspect provides a computer program product comprising instructions which, when executed on a computer or processor, cause the computer or processor to perform the method of the second aspect and any one of the embodiments thereof.
  • a fifteenth aspect provides a computer program product comprising instructions that, when executed on a computer or processor, cause the computer or processor to perform the method of the third aspect and any one of the embodiments thereof.
  • a sixteenth aspect provides a communication system, including the communication device according to the fourth aspect and any one thereof, the communication device according to the fifth aspect and any one thereof, and the sixth aspect and The communication device according to any one thereof; or, including the communication device according to the seventh aspect, the communication device according to the eighth aspect and any one thereof, and the ninth aspect and any one thereof the communication device described.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart 1 of a method for obtaining a key provided by an embodiment of the present application
  • FIG. 3 is a second schematic flowchart of a method for obtaining a key provided by an embodiment of the present application
  • FIG. 4 is a schematic flowchart three of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 5 is a fourth schematic flowchart of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart five of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 7 is a sixth schematic flowchart of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 8 is a seventh schematic flowchart of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart eight of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 10 is a ninth schematic flowchart of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart tenth of a method for obtaining a key provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram 1 of a communication device according to an embodiment of the present application.
  • FIG. 13 is a second schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 14 is a third schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 15 is a fourth schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 16 is a fifth schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 17 is a sixth schematic structural diagram of a communication device according to an embodiment of the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • TDD time division duplexing
  • FDD frequency division duplexing
  • Figure 1 provides a 5G communication system architecture, including an access network and a core network.
  • the access network is used to implement functions related to wireless access, and the access network includes a 3GPP access network and a non-3GPP access network.
  • the communication system includes: a terminal device 101, a (radio) access network ((R)AN) network element 102, a user plane function (UPF) network element 103, a data network (data network) , DN) 104, access and mobility management function (AMF) network element 105, session management function (session management function, SMF) network element 106, policy control network element (policy control function, PCF) Network element 107, unified data management (UDM) network element 108, application function (AF) network element 109, authentication server function (authentication server function, AUSF) network element 110, and network slice selection A network slice selection function (NSSF) network element 111, a network exposure function (NEF) network element 112, a network function repository (NRF) network element 113,
  • the name of the interface between each network element in FIG. 1 is just an example, and the name of the interface may be other names in specific implementation, which is not limited.
  • the interface between the terminal device 101 and the AMF network element 105 may be the N1 interface
  • the interface between the (R)AN network element 102 and the AMF network element 105 may be the N2 interface
  • the (R)AN network element 102 and the UPF network element The interface between the elements 103 may be the N3 interface
  • the interface between the UPF network element 103 and the SMF network element 106 may be the N4 interface
  • the interface between the UPF network element 103 and the DN 104 may be the N6 interface.
  • the terminal device 101 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem; it may also include subscriber units, cellular phones , smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer (laptop computer), cordless Telephone (cordless phone) or wireless local loop (wireless local loop, WLL) station, machine type communication (machine type communication, MTC) terminal, user equipment (user equipment, UE), mobile station (mobile station, MS), terminal device (terminal device) or relay user equipment, etc.
  • the relay user equipment may be a 5G home gateway (residential gateway, RG).
  • the devices mentioned above may be collectively referred to as terminal devices.
  • a remote terminal device may access the 3GPP network through a relay terminal device (relay UE), and perform indirect communication with the network device and the application server.
  • AN network element 102 is a device that provides wireless access for terminal equipment 101, including RAN network element and AN network element, wherein the RAN network element is mainly a 3GPP network wireless network device, and the AN network element can be defined by non-3GPP access network equipment.
  • This application takes the RAN network element as an example, but it is not intended to be limited to this.
  • the RAN network element is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side. It may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small cells), relay stations, access points, and the like. In systems using different radio access technologies, the names of devices with base station functions may be different.
  • NodeB in a long term evolution (LTE) system, it is called an evolved NodeB (evolved NodeB, eNB or eNodeB); in a 3rd generation (3G) communication system, it is called a Node B ( Node B) etc.
  • LTE long term evolution
  • eNB evolved NodeB
  • 3G 3rd generation
  • the AN network element allows the terminal equipment and the 3GPP core network to use non-3GPP technology for interconnection and intercommunication, wherein the non-3GPP technology includes, for example: Wireless Fidelity (Wi-Fi), worldwide interoperability for microwave access, WiMAX), code division multiple access (code division multiple access, CDMA) networks, etc.
  • Wi-Fi Wireless Fidelity
  • WiMAX worldwide interoperability for microwave access
  • CDMA code division multiple access
  • the UPF network element 103 is mainly responsible for processing user packets, such as forwarding and charging.
  • the user data can be received from the data network and transmitted to the terminal equipment through the RAN network element; the UPF network element can also receive user data from the terminal equipment through the RAN network element and forward it to the DN.
  • the transmission resources and scheduling functions that provide services for terminal equipment in the UPF network element are managed and controlled by the SMF network element.
  • DN 104 refers to a network that provides data transmission services for users, such as IP multimedia services (IP multi-media service, IMS), the Internet (Internet), and the like.
  • the terminal device 101 accesses the DN 104 by establishing a protocol data unit (protocol data unit, PDU) session between the terminal device, the RAN network element 102, the UPF network element 103, and the DN 104.
  • PDU protocol data unit
  • the path of the user plane is: the terminal device to the (R)AN network element, to the UPF network element, and then to the DN.
  • the AMF network element 105 is mainly responsible for mobility management in the mobile network, such as user location update, user registration in the network, user handover, and the like.
  • the SMF network element 106 is mainly responsible for session management in the mobile network, such as session establishment, modification, and release.
  • specific functions include: assigning IP addresses to users, selecting UPF network elements that provide packet forwarding functions, and the like.
  • the PCF network element 107 provides a unified policy framework to control network behavior, and provides policy rules to control layer network functions, such as QoS policies, slice selection policies, and the like. At the same time, it is responsible for obtaining user subscription information related to policy decisions.
  • the UDM network element 108 is used for generating authentication credential, user identification processing (such as storing and managing user permanent identity, etc.), access authorization control and contract data management, and the like.
  • the AF network element 109 may also be called a server, and is responsible for interacting with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some services of a third party to the network side.
  • the AUSF network element 110 is used to authenticate and authorize users.
  • the NSSF network element 111 is used to centrally manage the slicing function.
  • the NEF network element 112 is responsible for the isolation of internal and external networks, and is used to support the opening of capabilities and events, including open monitoring (Monitoring) capabilities, policy/billing capabilities, and analysis and reporting capabilities.
  • the NRF network element 113 is responsible for maintaining the text of the available network function instances and the services supported by the network function for other network function network elements to perform service discovery or network function network element discovery.
  • the NSSAAF network element 114 is used to support network slice-specific authentication and authorization procedures, and can communicate with an AAA (authentication, authorization and accounting, authentication, authorization and accounting) server or an AAA proxy.
  • AAA authentication, authorization and accounting, authentication, authorization and accounting
  • the SCP network element 115 is used for supporting indirect communication, proxy discovery, sending routing messages to the target network function network element or the next hop SCP, and the like.
  • DDNMF 5G direct discovery name management function
  • the indirect communication connection establishment process based on layer 3 (for IP-type PDU sessions, the relay terminal device forwards data based on the IP address) includes:
  • the remote terminal device and the relay terminal device are respectively registered to the network, and obtain authorization information from the network side.
  • the obtained authorization information includes:
  • Indication information used to indicate whether to authorize access to the 5GC through the relay terminal device.
  • Parameters used for ProSe Relay Discovery are used to enable the establishment of connections with relay terminal equipment, including, for example, relay service code (relay service code), PDU session parameters (such as data network name ( data network name, DNN), single setwork slice selection assistance information (S-NSSAI), access type preference, PDU session type, session and business continuity mode).
  • relay service code relay service code
  • PDU session parameters such as data network name (data network name, DNN), single setwork slice selection assistance information (S-NSSAI), access type preference, PDU session type, session and business continuity mode.
  • the obtained authorization information includes:
  • PLMN public land mobile network
  • Parameters used for ProSe Relay Discovery including: indication information, used to indicate authorization as a relay (UE-to-Network relay) between the UE and the network; relay service code, PDU session parameters (eg DNN, S-NSSAI, Access Type Preference, PDU Session Type, Session and Service Continuity Mode).
  • indication information used to indicate authorization as a relay (UE-to-Network relay) between the UE and the network
  • relay service code eg DNN, S-NSSAI, Access Type Preference, PDU Session Type, Session and Service Continuity Mode.
  • the relay terminal device establishes a PDU session.
  • the session can be a PDU session dedicated to serving remote terminal equipment; for an IP type PDU session, the SMF network element on the network side assigns an IP address (which can be an IPv4 address or an IPv6 prefix, etc.) to the PDU session, and the relay terminal equipment uses this PDU sessions transmit data for remote end devices.
  • IP address which can be an IPv4 address or an IPv6 prefix, etc.
  • This step is optional.
  • the remote terminal device discovers the relay terminal device through the relay discovery process.
  • the remote terminal device establishes a PC5 communication link with the relay terminal device.
  • the relay terminal equipment If the PDU session established by the relay terminal equipment cannot meet the session requirements of the remote terminal equipment (such as DNN, S-NSSAI, etc.), the relay terminal equipment establishes a new PDU session for the remote terminal equipment, and the PDU session is used for the remote terminal equipment. The transmission data between the terminal device and the application server. Or if the relay terminal device does not establish a PDU session for transmitting the service of the remote terminal device, a new PDU session is established, and the PDU session is used for data transmission between the remote terminal device and the application server.
  • the remote terminal equipment such as DNN, S-NSSAI, etc.
  • the relay terminal device allocates an IP address for PC5 communication to the remote terminal device.
  • the relay terminal device sends the ID and IP information (IP info) of the remote terminal device to the AMF network element and the SMF network element.
  • the IP information is an address allocated by the relay terminal device to the remote terminal device for network-side communication.
  • This step may be performed through a PDU session modification procedure.
  • the SMF network element assigns the IP address to the relay terminal equipment as IPv4
  • the IP information is expressed as a specific port number (TCP/UDP port), which means that the relay terminal equipment uses the IPv4 address and the specific port number Transmission of data from remote terminal equipment.
  • IPv6 prefix IPv6 prefix
  • the IP information is represented as a longer IPv6 prefix, which means that the relay terminal device uses the longer IPv6 prefix to transmit the data of the remote terminal device .
  • the relay terminal device forwards the uplink and downlink data of the remote terminal device according to the IP address.
  • the IP address used by the remote terminal device on the PC5 communication link is IP3, the IP address corresponding to the PDU session of the relay terminal device is IP1, and the IP information (IP info) allocated by the relay terminal device to the remote terminal device for IP1-1. Then the remote terminal device transmits data to the server by using IP3, the server transmits data to the remote terminal device by using IP1-1, and the relay terminal device needs to bind the association relationship between IP3 and IP1-1.
  • the relay terminal device receives the IP1-1 data packet from the UPF network element, learns that the data belongs to the remote terminal, and then modifies the IP address to IP3, and sends it to the remote terminal device through the PC5 link.
  • the relay terminal device modifies the IP address to IP1-1, sends it to the UPF network element through the PDU session, and then sends it to the server.
  • a secure connection needs to be established between the remote terminal device and the relay terminal device, that is, the data transmitted between the remote terminal device and the relay terminal device is encrypted and protected and/or integrity protection. Since the indirect communication connection is dynamically established on demand, shared security information (such as a key) cannot be preconfigured between the remote terminal device and the relay terminal device, and then the remote terminal device and the relay terminal device can be established based on the preconfigured shared security information. A secure connection between relay end devices. Therefore, it is necessary to dynamically establish shared security information (eg keys) between the remote terminal equipment and the relay terminal equipment.
  • shared security information eg keys
  • An embodiment of the present application provides a method for obtaining a key, as shown in FIG. 3 , including:
  • the remote terminal device accesses the 3GPP network and obtains the relay discovery and key material; the relay terminal device accesses the 3GPP network and obtains the discovery and key material.
  • the remote terminal device sends a key request to the AUSF network element through the AMF network element.
  • the key request includes the remote access indication of the adjacent service, the 5G Globally Unique Temporary Identity (GUTI) or the User Concealed Identifier (SUCI).
  • GUI 5G Globally Unique Temporary Identity
  • SUCI User Concealed Identifier
  • the AUSF network element sends an authentication request to the UDM network element.
  • the authentication request includes the remote access indication of the proximity service, 5G-GUTI or SUCI.
  • the UDM network element sends an authentication response to the AUSF network element.
  • the authentication response includes the user's subscription permanent identifier (SUPI).
  • SUPI subscription permanent identifier
  • the AUSF network element generates a root key (REAR Key) using the latest key (Kausf) shared between the remote terminal device and the AUSF network element.
  • RRR Key root key
  • Kausf latest key
  • the AUSF network element sends a key response to the remote terminal device.
  • the key response includes the root key and the identifier of the relay terminal device.
  • the remote terminal device discovers the relay terminal device.
  • the remote terminal device sends a direct communication request to the relay terminal device.
  • the direct communication request includes the relay service code, 5G-GUTI and message authentication code (MAC).
  • the relay terminal device sends a key request to the AUSF network element.
  • the key request includes the relay service code, 5G-GUTI and MAC.
  • the AUSF network element performs authentication and authorization checking.
  • the AUSF network element After authorization, the AUSF network element generates the key K NR_ProSe of the remote terminal device.
  • K NR_ProSe KDF (root key REAR key, 5G-GUTI, relay service code or service identifier, freshness parameter, other possible parameters).
  • KDF key derivation function
  • the AUSF network element sends a key response to the relay terminal device.
  • the key response includes KNR_ProSe and freshness parameters.
  • the relay terminal device sends a direct security mode command to the remote terminal device.
  • the direct security mode command includes a freshness parameter to generate K NR_ProSe .
  • the remote terminal device generates the key K NR_ProSe according to the direct security mode command.
  • the remote terminal device sends a direct security mode command completion message to the relay terminal device according to the direct security mode command.
  • the identifier of the relay terminal device is used in the key derivation process, but since there are one or more terminal devices that can provide relay services, the network cannot obtain the relay terminal device before the remote terminal device discovers the relay terminal device. The identity of the terminal device that is serving the service cannot be derived, so the corresponding key cannot be deduced. In addition, it is not defined how to determine the AUSF network element for deriving the key, nor how the relay terminal device discovers the AUSF network element for which the remote terminal device deduces the key. If the relay terminal device arbitrarily selects an AUSF network element, if the AUSF network element does not store the key obtained by the remote terminal device, the MAC generated by the remote terminal device cannot be verified.
  • the embodiment of the present application provides a method for obtaining a key, as shown in FIG. 4 , including:
  • the remote terminal equipment interacts with the proximity service (ProSe) function network element to obtain the relay discovery parameters and the address of the proximity service key management function (ProSe key management function, PKMF) network element.
  • ProSe proximity service
  • PKMF proximity service key management function
  • the remote terminal device obtains the discovery key material from the relayed PKMF network element.
  • the relay terminal equipment interacts with the Proximity Service (ProSe) function network element to obtain the relay discovery parameters and the address of the PKMF network element.
  • ProSe Proximity Service
  • the relay terminal device obtains the network element discovery key material from the PKMF.
  • the remote terminal device sends a key request to the PKMF network element.
  • the key request includes indication information for requesting the relay communication key.
  • indication information for requesting the relay communication key.
  • the PKMF network element sends a response message to the remote terminal device, and the response message includes the PRUK and the corresponding PRUK Id.
  • the remote terminal device discovers the relay terminal device.
  • the remote terminal device sends a direct communication request to the relay terminal device.
  • the direct communication request includes one of a PRUK ID or an international mobile subscriber identity (IMSI), and a relay service code.
  • IMSI international mobile subscriber identity
  • the relay terminal device sends a key request to the PKMF network element.
  • the key request includes one of PRUK ID or IMSI, relay service code and first random number.
  • the PKMF network element identifies the terminal device according to the PRUK ID or IMSI, and performs authorization check.
  • the PKMF network element determines whether the remote terminal device needs a new PRUK. If necessary, the PKMF network element interacts with the home subscriber server (HSS) network element to obtain the user's generic bootstrapping information (GPI) (generic bootstrapping architecture (GBA)) push information (Push Info) ), GBA push information) or authentication vector.
  • HSS home subscriber server
  • the PKMF network element sends a key response to the relay terminal device.
  • the key response includes the key Kd, the random number for generating the key Kd, the GPI, and the identifier of the remote terminal device.
  • the relay terminal device sends a direct security mode command to the remote terminal device.
  • the direct security mode command includes the random number and GPI of the generated key Kd.
  • the remote terminal device sends the direct security mode completion to the relay terminal device.
  • the solution is based on the 4G communication system, and the key deduction is based on the GBA mechanism.
  • 5G does not support the GBA mechanism.
  • the remote terminal device may use the user's permanent identity identifier (ie, IMSI) when communicating with the relay terminal device, which may cause the user's privacy to be leaked.
  • IMSI user's permanent identity identifier
  • the embodiment of the present application provides another key acquisition method.
  • the remote terminal device and the relay terminal device can establish a communication root key.
  • the relay terminal device can obtain the root key for establishing the security of the PC5 interface under the condition of ensuring user privacy.
  • the remote AUSF network element refers to the AUSF network element serving the remote terminal equipment, and the remote AUSF network element stores a key shared with the remote terminal equipment.
  • the relay AUSF network element refers to the AUSF network element serving the relay terminal equipment.
  • the remote AMF network element refers to the AMF network element serving the remote terminal equipment, and the relay AMF network element refers to the AMF network element serving the relay terminal equipment.
  • the remote PCF network element refers to the PCF network element serving the remote terminal equipment, and the relay PCF network element refers to the PCF network element serving the relay terminal equipment.
  • the remote NRF network element refers to the NRF network element that serves the remote terminal equipment.
  • the remote UDM network element refers to the UDM network element that serves the remote terminal equipment.
  • generating a certain identifier, a certain key or certain verification information according to the parameter A refers to inputting a certain algorithm (such as a key derivation function (KDF)
  • KDF key derivation function
  • PKMF network element is a new functional module, which can be deployed independently or co-located with other functional network elements.
  • the PKMF network element is used to manage the security information of adjacent services, such as obtaining the shared key between the remote terminal device and the relay terminal device, and performing functions such as authorization checking.
  • the key acquisition method on the terminal side includes:
  • the remote terminal device sends the first identifier of the remote terminal device and the relay service code to the relay terminal device.
  • the remote terminal device sends the first verification information to the relay terminal device.
  • the remote terminal device sends the second verification information to the relay terminal device.
  • the above information may be carried in the same message (eg, direct communication request) or in different messages, and is finally forwarded by the relay terminal device to the remote AUSF network element, the relay AUSF network element or the PKMF network element.
  • connection service Used to identify a connection service that provides services for relays to connect to applications.
  • the same terminal device can be configured with different relay service codes to access different applications or services.
  • the first identifier may be the identifier (for example, P-KID) of the remote terminal equipment corresponding to the relay service code (for example, the format may be Username@realm), or the first identifier may be the anonymous identifier of the remote terminal equipment (for example, SUCI), so that the permanent identity of the remote terminal device (such as SUPI) will not be exposed during air interface transmission.
  • the first identifier may be in one-to-one correspondence with the relay service code, that is, for different relay service codes, the remote terminal device may use different first identifiers for communication.
  • the first identifier of the remote terminal device is used for the AUSF network element or the PKMF network element to determine the corresponding remote terminal device, thereby determining the corresponding first shared key, Alternatively, determine other identifiers of the remote terminal device (for example, SUPI), and the first shared key is the key shared by the remote terminal device and the remote AUSF network element (or other keys generated by the key).
  • the first shared key may be Kausf, and the key Kausf is negotiated and shared in advance with the remote AUSF network element when the remote terminal device accesses the network.
  • the first shared key may be a key for ProSe communication further deduced according to Kausf.
  • the remote terminal device can obtain the first identifier in the following ways:
  • the remote terminal device can send at least one relay service code to the remote authentication service function network element through the remote AMF network element;
  • the end AMF network element sends the first identifier to the remote terminal device; correspondingly, the remote terminal device receives the first identifier corresponding to the relay service code from the remote authentication service function network element.
  • Manner 2 The remote terminal device generates a temporary identifier according to the first shared key (eg Kausf) and the relay service code, and then obtains the first identifier according to the temporary identifier.
  • the first shared key eg Kausf
  • the manner in which the remote terminal device generates the temporary identifier according to the first shared key (such as Kausf) and the relay service code includes:
  • a first shared key eg Kausf
  • a relay service code are input into a certain algorithm (eg, key derivation function (KDF)), and a temporary identifier is obtained by calculation.
  • KDF key derivation function
  • the remote terminal device may also generate a temporary identifier according to at least one of the second freshness parameter, the SUPI of the remote terminal device, the first shared key (eg Kausf), and the relay service code. That is, the input parameters for calculating the above-mentioned temporary identification may also include the second freshness parameter or other parameters (eg, SUPI of the remote terminal device, etc.).
  • the remote terminal device generates an adjacent service root key according to the first shared key, and then generates a temporary identifier according to the adjacent service root key and the relay service code.
  • the remote terminal device first deduces an adjacent service root key according to the first shared key (eg Kausf).
  • the input parameters of the algorithm for generating the proximity service root key may include the character string "ProSe", the SUPI of the remote terminal device, and the like. Then, the remote terminal device uses the adjacent service root key and the relay service code as the input of the KDF to generate the temporary identification.
  • the remote terminal device may also generate a temporary identifier according to at least one of the second freshness parameter, the SUPI of the remote terminal device, the proximity service root key, and the relay service code. That is, the input parameters for calculating the above-mentioned temporary identification may also include the second freshness parameter or other parameters (eg, SUPI of the remote terminal device, etc.). That is, the manner in which the remote terminal device obtains the first identifier according to the temporary identifier includes:
  • the remote terminal device generates a first identifier according to the temporary identifier, the routing indication and the home network identifier of the remote terminal device, and the first identifier may include the routing instruction and the home network identifier.
  • the temporary identifier, the routing instruction and the home network identifier of the remote terminal device can be combined to obtain a character string as the temporary identifier.
  • the Username in the first identifier Username@realm can be Including temporary identification and routing indication, realm may include the home network identification of the remote terminal equipment.
  • the remote terminal device uses the above temporary identifier as the first identifier.
  • the remote terminal device generates the first identifier according to the second freshness parameter, the routing indication and the home network identifier of the remote terminal device, and the first identifier may include the routing indication and the home network identifier.
  • a string can be obtained by combining the second freshness parameter, the routing indication and the home network identifier of the remote terminal device as a temporary identifier.
  • the first identifier in Username@realm The Username may include the second freshness parameter and the routing indication, and the realm may include the home network identifier of the remote terminal device.
  • Mode 4 The remote terminal device generates a second shared key according to the first shared key (such as Kausf) and the relay service code, and the second shared key is the key Kp shared by the remote terminal device and the PKMF network element; The end terminal device then generates the first identifier according to the second shared key Kp and the second freshness parameter.
  • first shared key such as Kausf
  • the relay service code is used to generate a key based on the granularity of the relay service code to ensure that different relay service codes (services) correspond to different temporary identifiers, thereby preventing attackers from using the same
  • the first identifier of is associated with two different services being performed by a terminal device.
  • the second freshness parameter is used to ensure that the same relay service code is used at different times.
  • the network can generate different The temporary identifier is used to prevent an attacker from associating a terminal device with the same first identifier on the air interface to perform the same service at different times.
  • the second freshness parameter may include the values of the counters maintained locally by the remote terminal device and the remote AUSF network element respectively.
  • the remote terminal device and the remote AUSF network element maintain their respective counters locally, the same initial value and count are used. rules to keep the values of these two counters consistent.
  • the remote AUSF network element does not need to send the second freshness parameter to the remote terminal device.
  • the remote terminal device may send the relay service code to the remote AUSF network element; the remote AUSF network element generates the first identifier according to the second freshness parameter for the relay service code, and sends the first identifier to the remote terminal device.
  • Two freshness parameters correspondingly, the remote terminal device receives the second freshness parameter corresponding to the relay service code from the remote AUSF network element.
  • the second freshness parameter may include a random value generated by the remote AUSF network element or a value of a counter maintained locally by the remote AUSF network element, and the specific generation method is not limited.
  • the first verification information is generated from the first temporary key and all or part of the information elements of a message (eg, a direct communication request) carrying the first verification information.
  • the first temporary key is generated by the first shared key (eg Kausf). Specifically, the first temporary key can be deduced directly according to Kausf, or an intermediate key can be deduced according to Kausf, and the first temporary key can be further deduced based on the intermediate key.
  • the first temporary key consists of at least one of the relay service code, the third freshness parameter, the second identifier (for example, SUPI) of the remote terminal device, and the first identifier, and the first shared key.
  • the third freshness parameter is generated by the remote terminal device, and may be, for example, a third random number.
  • the first temporary key Kt is obtained by calculating an algorithm.
  • the first verification information is used to send to the remote AUSF network element.
  • the remote AUSF network element After receiving the first verification information, the remote AUSF network element generates third verification information in the same manner as the remote terminal device, and the remote AUSF network element compares the first verification information. information and third verification information to verify the remote terminal device and verify whether the remote terminal device is authorized to access the network through the relay terminal device to obtain services.
  • the second verification information is generated from the first freshness parameter, the relay service code and the first shared key (eg Kausf).
  • the remote terminal device generates the second shared key Kp according to the relay service code and the first shared key (eg Kausf), and then generates the second verification information according to the first freshness parameter and the second shared key Kp .
  • the remote terminal device generates the second ID according to the second identifier (for example, SUPI) of the remote terminal device, at least one of the proximity service (ProSe) characters, the relay service code, and the first shared key (for example, Kausf). Two shared keys Kp.
  • the remote terminal device generates the second shared key Kp according to the first shared key (eg Kausf) and other parameters, and then generates the second shared key Kp according to the first freshness parameter, the relay service code and the second shared key Kp. 2. Verification information.
  • the second verification information is used for sending to the PKMF network element.
  • the PKMF network element After receiving the second verification information, the PKMF network element generates fourth verification information in the same manner as the remote terminal device, and the PKMF network element compares the second verification information with the fourth verification information In order to verify the remote terminal equipment, it is verified whether the remote terminal equipment is authorized to access the network through the relay terminal equipment to obtain services.
  • the remote terminal device generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key (eg Kausf), the relay service code, and at least one first freshness parameter.
  • the first shared key eg Kausf
  • the relay service code e.g., the relay service code
  • the relay service code For example, using the first shared key (eg Kausf), the relay service code, and, at least one first freshness parameter, as the input of the key derivation function KDF, output the root of the communication between the remote terminal device and the relay terminal device key.
  • the first shared key eg Kausf
  • the relay service code e.g. Kausf
  • at least one first freshness parameter as the input of the key derivation function KDF, output the root of the communication between the remote terminal device and the relay terminal device key.
  • the first shared key eg Kausf
  • the relay service code e.g., the relay service code
  • at least one first freshness parameter, etc. the root key for the communication between the remote terminal device and the relay terminal device is output.
  • the remote terminal device can also generate the second shared key Kp according to the first shared key (eg Kausf) and the relay service code, and then generate the remote terminal according to the second shared key Kp and at least one first freshness parameter.
  • the root key for the device to communicate with the relay terminal device.
  • the remote terminal device may also generate a second shared key Kp according to the first shared key (eg Kausf), and then generate the remote terminal according to the relay service code, the second shared key Kp and at least one first freshness parameter.
  • the root key for the device to communicate with the relay terminal device.
  • the at least one first freshness parameter may include a value of a counter maintained locally by one of the remote AUSF network element or PKMF network element and the terminal device, and one of the remote AUSF network element or PKMF network element and the terminal device.
  • the device maintains its own counters locally, it adopts the same initial value and counting rules to keep the values of the two counters consistent.
  • one of the remote AUSF network element or the PKMF network element and the terminal device separately maintain counters for each relay server code.
  • the at least one first freshness parameter includes a first random number.
  • the remote terminal device may also send the first random number to the relay terminal device. The first random number is finally sent to the remote AUSF network element or the PKMF network element, and correspondingly, the remote AUSF network element or the PKMF network element receives the first random number.
  • the at least one first freshness parameter includes a second random number
  • the remote terminal device may also receive the second random number from the relay terminal device.
  • the second random number may come from the remote AUSF network element or the PKMF network element, that is, the remote AUSF network element or the PKMF network element may send the second random number.
  • the remote terminal device sends a first identifier and a relay service code to the relay terminal device, where the first identifier is the identifier of the remote terminal device corresponding to the relay service code or the first identifier. It is the anonymous identifier of the remote terminal device.
  • the remote terminal device generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter.
  • the first identifier is used for the remote AUSF network element to determine the corresponding first shared key, or for the PKMF network element to determine the corresponding second shared key, and the second shared key is also determined by the first shared key and/or relay service code generation, so that the remote terminal device and the remote AUSF network element or PKMF network element can use the same method to generate the root key for the communication between the remote terminal device and the relay terminal device, so that the remote terminal device can communicate with the relay terminal device.
  • the key is shared between the terminal device and the relay terminal device.
  • the steps performed by the remote AUSF network element in the key acquisition method on the network side include:
  • the remote AUSF network element acquires one of the first identifier or the second identifier of the remote terminal device, and the relay service code.
  • the remote AUSF network element receives the first random number.
  • the remote AUSF network element may also receive the first verification information.
  • first verification information reference is made to the foregoing description, which will not be repeated here.
  • the second identifier may be a permanent identity identifier (eg, SUPI) of the remote terminal device
  • the first identifier may be an identifier (eg, P-KID) of the remote terminal device corresponding to the relay service code.
  • the remote AUSF network element can receive the relay service code from the remote terminal equipment, and forward it through, for example, the remote AMF network element, the relay terminal equipment, and the PKMF network element. See the previous description for the relay service code, which will not be repeated here.
  • the remote AUSF network element obtains one of the first identifier or the second identifier of the remote terminal device, including the following methods:
  • the remote AUSF network element receives one of the first identifier or the second identifier of the remote terminal device.
  • the remote AUSF network element may receive one of the first identification or the second identification of the remote terminal device from the PKMF network element.
  • the method further includes: the remote AUSF network element may adopt the same method as the remote terminal equipment in step S501 (for example, the second method and the third method). ) to generate the first identifier.
  • the remote AUSF network element may generate the first identifier in the same manner as the remote terminal device in step S501 (eg, manner 2 and manner 3).
  • the remote AUSF network element may generate a temporary identifier according to the first shared key and the relay service code; and then generate the first identifier according to the temporary identifier.
  • the remote terminal device may generate the first identifier in the second manner of step S501.
  • the remote AUSF network element Similar to the remote terminal equipment, the remote AUSF network element generates a temporary identifier according to the first shared key and the relay service code, which may include: the remote terminal equipment according to the first shared key, the relay service code and the second The freshness parameter, which generates a temporary identifier.
  • the remote terminal device For details, refer to how the remote terminal device generates the temporary identifier in the second method of step S501.
  • the remote AUSF network element may generate the first identifier according to the second freshness parameter, the routing indication, and the home network identifier of the remote terminal device.
  • the second freshness parameter please refer to the above description, which will not be repeated here.
  • the remote AUSF network element may send the second freshness parameter, and forward it to the remote terminal device through the relay terminal device, so that the remote terminal device receives the second freshness parameter.
  • the remote AUSF network element After the remote AUSF network element generates the first identifier, it can send the first identifier corresponding to the relay service code to the relay terminal device, and the relay terminal device forwards it to the remote terminal device, so that the remote terminal device obtains the first identifier.
  • the identifier corresponds to the first method of obtaining the first identifier by the remote terminal device in step S501.
  • the remote AUSF network element may also send the first identifier to the UDM network element for other network elements (eg PKMF network element) to obtain the remote AUSF network element instance identifier and/or the SUPI of the remote terminal device from the UDM network element.
  • the remote AUSF network element instance identifier is used to determine the remote AUSF network element serving the remote terminal equipment.
  • the remote AUSF network element obtains the first shared key corresponding to the first identifier or the second identifier.
  • the remote AUSF network element can locally query the first shared key corresponding to the first identifier or the second identifier.
  • the remote AUSF network element generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter.
  • the first freshness parameter here may be the value of a counter maintained locally by the remote terminal device and the remote AUSF network element.
  • the remote AUSF network element can generate the root key in the same manner as the remote terminal device. For details, refer to the relevant description in step S502, which is not repeated here.
  • a first temporary key may be generated according to the first shared key; and according to the first temporary key, And, all or part of the information elements of the message carrying the first verification information are obtained to obtain the third verification information; by comparing the first verification information and the third verification information to verify the remote terminal equipment, the root key can be generated after the verification is passed. .
  • the remote AUSF network element performs verification reference may be made to the foregoing description of the first verification information, which will not be repeated here.
  • the remote AUSF network element can be based on at least one of the relay service code, the third freshness parameter, the second identifier, and the first identifier of the remote terminal equipment, and the first A shared key is generated to generate a first temporary key.
  • the remote terminal device refers to the relevant description of the remote terminal device, which will not be repeated here.
  • the remote AUSF network element generates the second shared key Kp in the same manner as the remote terminal device.
  • the second shared key Kp is generated, and the second shared key Kp is sent to the PKMF network element.
  • the remote terminal device generates the second shared key Kp.
  • the remote AUSF network element sends the root key.
  • the remote AUSF network element can send the root key to the PKMF network element, and send the root key to the relay terminal device through the PKMF network element.
  • the remote AUSF network element may also send at least one first freshness parameter for generating the root key.
  • the at least one first freshness parameter includes a second random number, and the remote AUSF network element may send the second random number, which is forwarded to the remote terminal device through the relay remote device.
  • the remote AUSF network element acquires one of the first identifier or the second identifier of the remote terminal device, and the relay service code; the second identifier is the permanent identifier of the remote terminal device.
  • the first identifier is the identifier corresponding to the relay service code of the remote terminal device; the remote AUSF network element obtains the first shared key corresponding to the first identifier or the second identifier; the first shared key is the remote The key shared by the terminal device and the remote AUSF network element; the remote AUSF network element generates the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter The root key of the communication; the remote AUSF sends the root key.
  • the first identifier is used by the remote AUSF network element to determine the corresponding first shared key, so that the remote terminal device and the remote AUSF network element can use the same method to generate the root of the communication between the remote terminal device and the relay terminal device.
  • the key is shared between the remote terminal device and the relay terminal device.
  • the steps performed by the PKMF network element in the key acquisition method on the network side include:
  • the PKMF network element receives the first identifier and the relay service code of the remote terminal device.
  • the PKMF network element receives the first random number.
  • the PKMF network element receives the second verification information.
  • the second verification information see the foregoing description, which will not be repeated here.
  • the first identifier may be an identifier of the remote terminal device corresponding to the relay service code (eg, P-KID), or the first identifier may be an anonymous identifier (eg, SUCI) of the remote terminal device.
  • the PKMF network element may receive the first identifier and the relay service code from the remote terminal device through the relay terminal device.
  • the PKMF network element acquires the root key for communication between the remote terminal device and the relay terminal device according to the first identifier.
  • the PKMF network element sends the first identification to the UDM network element; correspondingly receives the identification information of the remote AUSF (for example, the remote AUSF network element instance identification) from the UDM network element; the PKMF network element according to the identification information, send the first identifier to the corresponding remote AUSF network element; correspondingly, receive the root key from the remote AUSF network element.
  • the identification information of the remote AUSF for example, the remote AUSF network element instance identification
  • the PKMF network element sends the first identifier to the UDM network element; correspondingly, the identifier information of the remote AUSF network element and the permanent identity identifier of the remote terminal device (for example, SUPI) are received from the UDM network element. ); the PKMF network element sends the permanent identity of the remote terminal device to the corresponding remote AUSF network element according to the identification information; correspondingly, receives the root key from the remote AUSF network element.
  • the above two embodiments correspond to the step S601 in which the remote AUSF network element obtains one of the first identifier or the second identifier of the remote terminal device.
  • the PKMF network element receives at least one second shared key from the remote AUSF network element; the PKMF network element corresponds to the second shared key according to the first identifier, and at least one first fresh key properties parameters to generate the root key for the communication between the remote terminal device and the relay terminal device.
  • the PKMF network element generates a root key for communication between the remote terminal device and the relay terminal device according to the relay service code, the second shared key corresponding to the first identifier, and at least one first freshness parameter.
  • the fourth verification information can be generated according to the first freshness parameter and the second shared key;
  • the verification information and the third verification information are used to verify the remote terminal device, and the root key can be generated after the verification is passed.
  • the PKMF network element performs verification reference may be made to the foregoing description of the second verification information, which will not be repeated here.
  • the first freshness parameter here may be the value of a counter maintained locally by the remote terminal device and the PKMF network element.
  • the PKMF network element sends the root key.
  • the PKMF network element may also send at least one first freshness parameter for generating the root key.
  • at least one of the first freshness parameters includes a second random number, and the PKMF network element may send the second random number and forward it to the remote terminal device through the relay remote device.
  • the PKMF network element receives the first identifier and the relay service code of the remote terminal device, and the first identifier is the identifier of the remote terminal device corresponding to the relay service code or the first identifier is the anonymous identifier of the remote terminal device; the PKMF network element obtains the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, and the root key consists of the first shared key, the relay service code, and at least A first freshness parameter is generated, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element; the PKMF network element sends the root key.
  • the first identifier is used by the PKMF network element to determine the corresponding second shared key, so that the remote terminal device and the PKMF network element can use the same method to generate the root key for the communication between the remote terminal device and the relay terminal device, so as to realize The key is shared between the remote terminal equipment and the relay terminal equipment.
  • the embodiment of the present application provides another key acquisition method.
  • the remote terminal device actively requests the remote AUSF network element for the first identifier corresponding to the relay service code, so that the remote AUSF network element can generate the corresponding key according to the relay service code.
  • a first identifier where the first identifier is used to discover the remote UDM network element, and the generated first identifier is stored in the remote UDM network element.
  • the remote terminal device initiates a direct communication request to the relay terminal device, and the direct communication request includes the first identifier.
  • the relay terminal device initiates a key request containing the first identifier to the network side through signaling.
  • the PKMF network element determines the remote AUSF network element corresponding to the first identifier through the remote UDM network element, and obtains the remote AUSF network element from the remote AUSF network element.
  • the key acquisition method includes:
  • a remote terminal device accesses a network, and acquires information for communicating through a relay terminal device from a remote PCF network element or other related network elements.
  • the above information includes: indication information for indicating whether the terminal device is authorized to access the 5GC through the relay (that is, the terminal device acts as a remote terminal device); relay service code and the like.
  • the relay terminal device accesses the network, and obtains information for providing communication as the relay terminal device from the relay PCF network element or other related network elements.
  • the above information includes: indication information used to indicate whether the terminal device is authorized to act as a relay; relay service code and the like.
  • steps S801 and S802 are not limited.
  • the remote terminal device sends a key request to the remote AUSF network element through the remote AMF network element.
  • the key request includes at least one relay service code.
  • the remote AMF network element performs an authorization check to check whether the remote terminal device is authorized to act as the remote terminal device of the relay terminal device or whether the remote terminal device is authorized to obtain the corresponding relay service code through the relay terminal device.
  • an authorization check to check whether the remote terminal device is authorized to act as the remote terminal device of the relay terminal device or whether the remote terminal device is authorized to obtain the corresponding relay service code through the relay terminal device.
  • the remote AUSF network element generates a first identifier (eg, P-KID) of the remote terminal device corresponding to each relay service code.
  • the remote AUSF network element sends the first identifier of the remote terminal device to the remote UDM network element.
  • the remote UDM network element stores the first identifier of the remote terminal device locally as the context of the remote terminal device.
  • the remote UDM network element stores the context of the remote terminal device in the unified data repository (unified data repository, UDR) network element
  • the first identifier of the remote terminal device is also stored in the terminal device context of the UDR network element.
  • the remote AUSF network element sends a key request response to the remote terminal device through the remote AMF network element.
  • the key request response includes: a first identifier corresponding to the relay service code, or a second freshness parameter used to generate the first identifier.
  • the remote terminal device receives the first identifier corresponding to the relay service code from the remote AUSF network element through the remote AMF network element, or the second freshness parameter used to generate the first identifier.
  • the key request response may include the first identification corresponding to the relay service code, or the second freshness parameter used to generate the first identification . If the second freshness parameter is not used in the process of generating the first identifier, the key request response includes the first identifier corresponding to the relay service code.
  • the key request response may also include multiple first identifiers (or second fresh identifiers). properties parameter) respectively corresponding to multiple relay service codes, that is, the first identifier (or the second freshness parameter) in the key request response corresponds to the relay service code one-to-one; or, the key request response includes multiple first An identifier (or the second freshness parameter), which is not corresponding to the relay service code, is freely selected by the remote terminal device and corresponds.
  • the remote terminal device acquires the first identifier.
  • step S806 the remote terminal device directly stores it.
  • the remote terminal device If the second freshness parameter is received in step S806, the remote terminal device generates the first identifier in the same manner as the remote AUSF network element, for example, according to the second or third manner in step S501 to generate the first identifier. It should be noted that the process of generating the first identifier by the remote terminal device may be performed before step S809.
  • the remote terminal device performs a discovery process to discover the relay terminal device.
  • the remote terminal device sends a direct communication request to the relay terminal device.
  • the direct communication request includes the first identification (eg P-KID) of the remote terminal device and the relay service code. If there are multiple relay service codes, the remote terminal device can determine the corresponding first identifier through the relay service codes.
  • the direct communication request may further include a first random number (Nonce 1).
  • the direct communication request may further include first verification information.
  • step S501 for how to generate the first verification information.
  • the relay terminal device sends a key request to the relay AMF network element.
  • the key request includes a first identifier (eg P-KID) and a relay service code.
  • the key request may further include the first random number.
  • the key request may further include first verification information (eg MAC-I).
  • first verification information eg MAC-I
  • the relay AMF network element selects a relay AUSF network element, and sends a proximity service key request to the relay AUSF network element.
  • the proximity service key request includes the first identifier (for example, P-KID), the relay service code, and the identifier (relay UE ID) of the relay terminal device (for example, SUPI).
  • the adjacent service key request may further include a first random number.
  • the proximity service key request may further include first verification information (eg MAC-I).
  • first verification information eg MAC-I
  • the relay AMF network element performs authorization checking, that is, checking whether the relay terminal device is authorized to act as the relay terminal device or whether the relay terminal device is authorized to provide the connection service corresponding to the relay service code to the remote terminal device.
  • the relay AUSF network element selects a PKMF network element, and sends a proximity service key request to the PKMF network element.
  • the information carried in the adjacent service key request is the same as the information carried in the adjacent service key request in step S811.
  • the PKMF network element selects a remote UDM network element according to the first identifier (eg P-KID) in the proximity service key request, and sends a network element discovery request to the remote UDM network element.
  • the first identifier eg P-KID
  • the network element discovery request includes a first identifier (eg P-KID).
  • the remote UDM network element acquires the remote AUSF network element instance identifier according to the first identifier (eg P-KID), and sends the identifier to the PKMF network element.
  • the AUSF network instance identifier can be an identifier that can uniquely identify the remote AUSF, such as a fully qualified domain name (FQDN) or an AUSF address, which is not limited here.
  • the PKMF network element may also acquire the second identifier (for example, SUPI) of the remote terminal device.
  • SUPI the second identifier
  • the PKMF network element authorizes the remote terminal device and the relay terminal device.
  • the PKMF network element determines whether to authorize the remote terminal device to pass through the relay terminal according to the second identifier (such as SUPI) of the remote terminal device and the relay service code.
  • the device obtains the service corresponding to the relay service code.
  • the PKMF network element judges whether the relay terminal device is authorized to provide the service corresponding to the relay service code as a relay according to the identifier of the relay terminal device (relay UE ID, such as SUPI) and the relay service code. If the authorization is passed, the follow-up process will continue, otherwise, the rejection process will be initiated.
  • relay UE ID such as SUPI
  • PKMF authorization process is optional, and may occur after step S815.
  • the PKMF network element sends an adjacent service key request to the remote AUSF network element.
  • the proximity service key request includes the second identifier (for example, SUPI) or the first identifier of the remote terminal device, and the relay service code.
  • the adjacent service key request may further include a first random number.
  • the proximity service key request may further include first verification information (eg MAC-I).
  • first verification information eg MAC-I
  • the remote AUSF network element generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter.
  • the at least one first freshness parameter here may include the first random number (Nonce 1), or may include the second random number (Nonce 2) generated by the remote AUSF network element, or may include the first random number and the first random number.
  • Two random numbers or can include the value of the counter maintained locally by the remote AUSF network element.
  • the counter maintained locally by the remote AUSF network element adopts the same initial value and counting rule as the counter maintained locally by the remote terminal device, so that the The values of the two counters remain the same.
  • the specific implementation manner of the first freshness parameter is not limited.
  • the remote AUSF network element if the adjacent service key request includes the first verification information, the remote AUSF network element generates the third verification information in the same manner as the terminal device, and performs verification by comparing the first verification information and the third verification information. . After the verification is passed, the root key is generated.
  • the remote AUSF network element sends a proximity service key response to the PKMF network element.
  • the adjacent service key response may include a root key, and optionally, a second random number.
  • the PKMF network element sends an adjacent service key response to the relay AUSF network element.
  • the adjacent service key response may include a root key, and optionally, a second random number.
  • the relay AUSF network element sends a proximity service key response to the relay terminal device through the relay AMF network element.
  • the adjacent service key response may include a root key, and optionally, a second random number.
  • the relay terminal device sends a security mode command to the remote terminal device.
  • the security mode command includes a second random number.
  • the relay terminal device generates a fourth random number, and includes the fourth random number in the security mode command message.
  • the remote terminal device uses the same method as the remote AUSF network element to generate the root key.
  • the relay terminal device may generate a session key between the relay terminal device and the remote terminal device according to the received root key. Further optionally, the relay terminal device may generate an encryption key and/or an integrity protection key for the signaling plane and/or the user plane according to the session key.
  • the relay terminal device may generate an encryption key and/or an integrity protection key for the signaling plane and/or the user plane according to the received root key.
  • the security mode command message includes a message verification code, and the message verification code is generated according to the integrity protection key of the signaling plane.
  • the remote terminal device sends a complete message of the security mode command to the relay terminal device.
  • the remote terminal device acquires the first identifier corresponding to the relay service code, and through the first identifier, the relay terminal device can obtain the remote terminal device and the relay from the network side through the signaling plane.
  • the root key for end-device communication.
  • the PKMF network element first performs authorization checking on the remote terminal device and the relay terminal device to ensure that only authorized terminal devices acquire the root key.
  • the root key is generated according to parameters such as the first shared key Kausf and the relay service code.
  • the embodiment of the present application provides another key acquisition method.
  • the remote terminal device actively requests the remote AUSF network element for the first identifier corresponding to the relay service code, so that the remote AUSF network element can generate the corresponding key according to the relay service code.
  • the first identifier and the second shared key are sent to the PKMF network element.
  • the remote terminal device initiates a direct communication request to the relay terminal device, and the direct communication request includes the first identifier.
  • the relay terminal device initiates a key request including the first identifier to the network side through signaling, and the PKMF network element obtains the corresponding second shared key Kp according to the first identifier, and generates a communication between the remote terminal device and the relay terminal device. root key.
  • the remote AUSF network element pushes the first identifier and the second shared key Kp of the remote terminal device to the PKMF network element in advance. Or the remote AUSF network element pushes the second shared key Kp to the PKMF network element in advance, and the PKMF generates the first identifier of the remote terminal device.
  • the key acquisition method includes:
  • a remote terminal device accesses a network, and acquires information for communicating through a relay terminal device from a remote PCF network element or other related network elements.
  • step S801 This step is the same as step S801 and will not be repeated here.
  • the relay terminal device accesses the network, and obtains information for providing communication as the relay terminal device from the relay PCF network element or other related network elements.
  • step S802 This step is the same as step S802 and will not be repeated here.
  • the remote terminal device sends a key request to the remote AUSF network element through the remote AMF network element.
  • step S803 This step is the same as step S803 and will not be repeated here.
  • the remote AUSF network element generates a second shared key Kp.
  • step S603 for the process of generating the second shared key Kp.
  • the remote AUSF network element generates a first identifier (eg, P-KID) of the terminal device corresponding to each relay service code.
  • a first identifier eg, P-KID
  • the process of generating the first identifier refer to step S601.
  • the remote AUSF network element selects the PKMF network element, and sends a near service information provision message to the PKMF network element.
  • the way for the remote AUSF network element to select the PKMF network element includes but is not limited to the following possible ways:
  • the remote AUSF network element determines the PKMF network element according to the relay service code. For example, the remote AUSF network element sends the relay service code to the remote NRF network element or the remote PCF network element to obtain the corresponding relay service code. PKMF network element. Or the relay service code includes routing information, and the remote AUSF network element selects the PKMF network element according to the routing information.
  • the remote terminal device includes the discovery information of the PKMF network element in the key request (obtaining the information from the remote PCF network element or other related network elements in step S901), and forwards it to the remote terminal by the remote AMF network element. end AUSF network element.
  • the remote AMF network element includes the discovery information of the PKMF network element in the key request (the information is obtained from the remote PCF network element or other related network elements in step S901).
  • the above-mentioned discovery information of the PKMF network element is used for the AUSF network element to determine the PKMF network element, and the discovery information of the PKMF network element may be routing information, address information of the PKMF network element, or an identifier of the PKMF network element.
  • the proximity service information providing message includes the second identifier (eg, SUPI) of the remote terminal device, the second shared key Kp, and optionally, the relay service code and the first identifier of the remote terminal device.
  • the PKMF network element stores the received second identifier of the remote terminal device (for example, SUPI), the first identifier of the remote terminal device (if received), and the second shared key Kp, and optionally, the relay can also be stored. service code.
  • the PKMF network element may store the above information after judging that the remote terminal device is authorized to obtain the relay service code.
  • the PKMF network element if the proximity service information providing message does not contain the first identifier, the PKMF network element generates the first identifier. In this case, optionally, the PKMF network element sends the generated first identifier or the second freshness parameter to the remote AUSF network element.
  • the remote AUSF network element sends a key request response to the remote terminal device through the remote AMF network element.
  • This step is the same as step S806.
  • the remote terminal device acquires the first identifier.
  • step S807 This step is the same as step S807. It should be noted that the process of generating the first identifier by the remote terminal device may be performed before step S909.
  • the remote terminal device performs a discovery process to discover the relay terminal device.
  • This step is the same as step S808.
  • the remote terminal device sends a direct communication request to the relay terminal device.
  • step S809 The difference between this step and step S809 is that the remote terminal device may generate the second verification information instead of the first verification information, and the process of generating the second verification information refers to step S501. And the direct communication request optionally includes the second verification information instead of the first verification information. Other content is the same.
  • the relay terminal device sends a key request to the relay AMF network element.
  • step S810 The difference between this step and step S810 is that the key request optionally includes the second verification information instead of the first verification information. Other content is the same.
  • the relay AMF network element selects a relay AUSF network element, and sends a proximity service key request to the relay AUSF network element.
  • step S811 The difference between this step and step S811 is that the adjacent service key request optionally includes the second verification information instead of the first verification information. Other content is the same.
  • the relay AUSF network element selects a PKMF network element, and sends a proximity service key request to the PKMF network element.
  • step S812 The difference between this step and step S812 is that the method of selecting the PKMF network element by the relay AUSF network element is the same as the method of selecting the PKMF network element by the remote AUSF network element in step S905; verification information, instead of including the first verification information. Other content is the same.
  • the PKMF network element authorizes the remote terminal equipment and the relay terminal equipment.
  • This step is the same as step S814. This step is optional.
  • the PKMF network element generates a root key for communication between the remote terminal device and the relay terminal device according to the second shared key Kp and at least one first freshness parameter.
  • the first freshness parameter here may include a first random number (Nonce 1), or, may include a second random number (Nonce 2) generated by PKMF, or, include a first random number and a second random number, or, It can include the values of the counters maintained locally by the remote terminal device and the PKMF network element respectively.
  • the remote terminal device and the PKMF network element maintain their respective counters locally, they use the same initial value and counting rule, so that the two counters are equal to each other. The value remains the same.
  • step S702 For the process of generating the root key, refer to step S702.
  • the PKMF network element if the proximity service key request includes the second verification information, the PKMF network element generates the fourth verification information in the same manner as the terminal device, and performs verification by comparing the second verification information with the fourth verification information. After the verification is passed, the root key is generated.
  • step S913 is not limited.
  • the PKMF network element sends an adjacent service key response to the relay AUSF network element.
  • This step is the same as step S818.
  • the relay AUSF network element sends a proximity service key response to the relay terminal device through the relay AMF network element.
  • This step is the same as step S819.
  • the relay terminal device sends a security mode command to the remote terminal device.
  • This step is the same as step S820.
  • the remote terminal device sends a complete message of the security mode command to the relay terminal device.
  • This step is the same as step S821.
  • the remote terminal device acquires the first identifier corresponding to the relay service code, and through the first identifier, the relay terminal device can obtain the remote terminal device and the relay from the network side through the signaling plane.
  • the root key for end-device communication.
  • the PKMF network element first performs authorization checking on the remote terminal device and the relay terminal device to ensure that only authorized terminal devices acquire the root key.
  • the root key is generated according to parameters such as the first shared key Kausf and the relay service code.
  • the embodiment of this application provides another key acquisition method.
  • the remote terminal device actively requests the PKMF network element for the first identifier corresponding to the relay service code through the remote AMF network element, and then the PKMF network element sends the remote AUSF network element to the remote AUSF network element.
  • the first identifier is requested, so that the remote AUSF network element can generate the corresponding first identifier and the second shared key according to the relay service code, and send them to the PKMF network element.
  • the remote terminal device initiates a direct communication request to the relay terminal device, and the direct communication request includes the first identifier.
  • the relay terminal device initiates a key request containing the first identifier to the network side through signaling, and the PKMF network element obtains the corresponding second shared key according to the first identifier, and generates the root of the communication between the remote terminal device and the relay terminal device. key.
  • the difference from Figure 9 is that the remote AMF network element communicates directly with the PKMF network element.
  • the key acquisition method includes:
  • a remote terminal device accesses a network, and acquires information for communicating through a relay terminal device from a remote PCF network element or other related network elements.
  • step S801 This step is the same as step S801 and will not be repeated here.
  • the relay terminal device accesses the network, and obtains information for providing communication as the relay terminal device from the relay PCF network element or other related network elements.
  • step S802 This step is the same as step S802 and will not be repeated here.
  • the remote terminal device sends a key request to the remote AMF network element.
  • the key request includes at least one relay service code.
  • the remote AMF network element performs an authorization check, that is, to check whether the remote terminal device is authorized to act as the remote terminal device of the relay terminal device, or to check whether the remote terminal device is authorized to obtain the corresponding relay service code through the relay terminal device. service.
  • the remote AMF network element selects a PKMF network element, and sends a key request to the PKMF network element.
  • the manner in which the remote AMF network element selects the PKMF network element is the same as the manner in which the remote AUSF network element selects the PKMF network element in step S905.
  • the key request includes the relay service code, the remote AUSF network element instance identifier, and the second identifier (for example, SUPI) of the remote terminal device.
  • step S1003 If the key request in step S1003 includes multiple relay service codes and corresponds to different PKMF network elements, the remote AMF network element sends the key request to each PKMF network element respectively.
  • the PKMF network element sends an adjacent service security information request to the remote AUSF network element.
  • the request includes the second identifier (for example, SUPI) of the remote terminal device and the relay service code.
  • SUPI the second identifier
  • the PKMF network element determines whether to authorize the remote terminal device to obtain the service corresponding to the relay service code through the relay terminal device according to the second identifier (for example, SUPI) of the remote terminal device and the relay service code. .
  • SUPI the second identifier
  • the remote AUSF network element generates a first identifier (eg, P-KID) of the terminal device corresponding to each relay service code, and generates a second shared key Kp.
  • a first identifier eg, P-KID
  • This step is the same as step S904.
  • the remote AUSF network element sends a proximity service security information response to the PKMF network element.
  • the proximity service security information response includes the second shared key Kp, and optionally, the relay service code, the second identifier (eg, SUPI) of the remote terminal device, and the first identifier of the remote terminal device.
  • the PKMF network element sends a key request response to the remote terminal device through the remote AMF network element.
  • step S806 For the information included in the key request response, reference may be made to step S806, which will not be repeated here.
  • the remote terminal device acquires the first identifier.
  • step S807 This step is the same as step S807. It should be noted that, the process of generating the first identifier by the remote terminal device may be performed before step S1011.
  • the remote terminal device performs a discovery process to discover the relay terminal device.
  • This step is the same as step S808.
  • the remote terminal device sends a direct communication request to the relay terminal device.
  • step S909 This step is the same as step S909.
  • the relay terminal device sends a key request to the relay AMF network element.
  • step S910 This step is the same as step S910.
  • the relay AMF network element selects a PKMF network element, and sends a proximity service key request to the PKMF network element.
  • the manner in which the relay AMF network element selects the PKMF network element is the same as the manner in which the remote AMF network element selects the PKMF network element in step S1004.
  • the information carried in the adjacent service key request is the same as the information carried in the adjacent service key request in step S912.
  • the relay AMF network element performs authorization check, that is, to check whether the relay terminal device is authorized to act as the relay terminal device of the remote relay device or to check whether the relay terminal device is authorized to provide the relay service code to the remote terminal device.
  • authorization check that is, to check whether the relay terminal device is authorized to act as the relay terminal device of the remote relay device or to check whether the relay terminal device is authorized to provide the relay service code to the remote terminal device.
  • the corresponding connection service is
  • the PKMF network element authorizes the remote terminal device and the relay terminal device.
  • This step is the same as step S814.
  • the PKMF network element generates a root key for communication between the remote terminal device and the relay terminal device according to the second shared key Kp and at least one first freshness parameter.
  • This step is the same as step S914.
  • the PKMF network element sends a proximity service key response to the relay terminal device through the relay AMF network element.
  • the information carried in the adjacent service key response is the same as the information carried in the adjacent service key response in step S818.
  • the relay terminal device sends a security mode command to the remote terminal device.
  • This step is the same as step S820.
  • This step is the same as step S821.
  • the remote terminal device acquires the first identifier corresponding to the relay service code, and through the first identifier, the relay terminal device can obtain the remote terminal device and the relay from the network side through the signaling plane.
  • the root key for end-device communication.
  • the PKMF network element first performs authorization checking on the remote terminal device and the relay terminal device to ensure that only authorized terminal devices acquire the root key.
  • the root key is generated according to parameters such as the first shared key Kausf and the relay service code.
  • the embodiment of the present application provides another key acquisition method.
  • the remote terminal device initiates a direct communication request to the relay terminal device, and the direct communication request includes the SUCI of the remote terminal device.
  • the relay terminal device initiates a key request containing SUCI to the network side through signaling.
  • the PKMF network element determines the remote AUSF network element corresponding to the SUCI through the remote UDM network element, and obtains the remote terminal equipment and the intermediate network element from the remote AUSF network element.
  • the root key for communication between end devices is that the PKMF network element determines the remote AUSF network element through the SUCI of the remote terminal device.
  • the key acquisition method includes:
  • a remote terminal device accesses a network, and acquires information for communicating through a relay terminal device from a remote PCF network element or other related network elements.
  • step S801 This step is the same as step S801 and will not be repeated here.
  • the relay terminal device accesses the network, and obtains information for providing communication as the relay terminal device from the relay PCF network element or other related network elements.
  • step S802 This step is the same as step S802 and will not be repeated here.
  • the remote terminal device performs a discovery process to discover the relay terminal device.
  • This step is the same as step S808.
  • S1104 The remote terminal device sends a direct communication request to the relay terminal device.
  • step S809 The difference between this step and step S809 is that the first identifier in the direct communication request may be the SUCI of the remote terminal device.
  • the relay terminal device sends a key request to the relay AMF network element.
  • step S810 The difference between this step and step S810 is that the first identifier in the key request may be the SUCI of the remote terminal device.
  • the relay AMF network element selects a relay AUSF network element, and sends a proximity service key request to the relay AUSF network element.
  • step S811 The difference between this step and step S811 is that the first identifier in the proximity service key request may be the SUCI of the remote terminal device.
  • the relay AUSF network element selects a PKMF network element, and sends a proximity service key request to the PKMF network element.
  • step S812 The difference between this step and step S812 is that the first identifier in the proximity service key request may be the SUCI of the remote terminal device.
  • the PKMF network element selects the remote UDM network element according to the first identifier (for example, SUCI) in the adjacent service key request, and sends a terminal equipment identifier (UE ID) request to the remote UDM network element.
  • the first identifier for example, SUCI
  • UE ID terminal equipment identifier
  • the terminal equipment identification request includes a first identification (eg SUCI).
  • the remote UDM network element obtains the second identifier (eg SUPI) of the remote terminal device and the instance identifier of the remote AUSF network element serving the remote terminal device according to the first identifier (eg SUCI), and sends them to the PKMF network element.
  • the second identifier eg SUPI
  • the instance identifier of the remote AUSF network element serving the remote terminal device eg SUCI
  • the PKMF network element authorizes the remote terminal device and the relay terminal device.
  • This step is the same as step S814.
  • the PKMF network element sends a request for a proximity service key to the remote AUSF network element.
  • This step is the same as step S815.
  • the remote AUSF network element generates a root key for communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter.
  • This step is the same as step S816.
  • the remote AUSF network element sends a proximity service key response to the PKMF network element.
  • This step is the same as step S817.
  • the PKMF network element sends an adjacent service key response to the relay AUSF network element.
  • This step is the same as step S818.
  • the relay AUSF network element sends a proximity service key response to the relay terminal device through the relay AMF network element.
  • This step is the same as step S819.
  • the relay terminal device sends a security mode command to the remote terminal device.
  • This step is the same as step S820.
  • S1116 The remote terminal device sends a complete message of the security mode command to the relay terminal device.
  • This step is the same as step S821.
  • steps S811 and S812 are optional, and the remote AMF network element can directly select the PKMF network element and send the adjacent service key request to the PKMF network element.
  • the content carried in the adjacent service key request is the same as that in step S811.
  • the information carried in the adjacent service key request is the same.
  • the remote terminal device generates SUCI, so that the relay terminal device can use the SUCI to acquire the root key of the communication between the remote terminal device and the relay terminal device from the PKMF network element.
  • the PKMF network element can determine the remote AUSF network element according to the SUCI, and obtains the root key of the communication between the remote terminal device and the relay terminal device from the remote AUSF network element.
  • an embodiment of the present application further provides a communication device, where the communication device is used to implement the above-mentioned various methods.
  • the communication apparatus may be the remote terminal equipment in the above method embodiments, or an apparatus including the above-mentioned remote terminal equipment, or a chip or a functional module in the remote terminal equipment.
  • the communication device may be the remote AUSF network element in the foregoing method embodiments, or a device including the foregoing remote AUSF network element, or a chip or functional module in the remote AUSF network element.
  • the communication device may be the PKMF network element in the foregoing method embodiments, or a device including the foregoing PKMF network element, or a chip or functional module in the PKMF network element.
  • the communication apparatus includes corresponding hardware structures and/or software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the communication device may be divided into functional modules according to the foregoing method embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 12 shows a schematic structural diagram of a communication device 120 .
  • the communication apparatus 120 may be the remote terminal device in FIG. 1 .
  • the communication device 120 includes a processing module 1201 and a transceiver module 1202 .
  • the processing module 1201 may also be called a processing unit, and is used to implement the processing function of the remote terminal device in the foregoing method embodiments. For example, step S502 in FIG. 5 is performed, and the processing functions of the remote terminal device in FIG. 8 to FIG. 11 are performed.
  • the transceiver module 1202 which may also be referred to as a transceiver unit, is used to implement the transceiver function of the remote terminal device in the foregoing method embodiments. For example, step S501 in FIG. 5 is performed, and the sending and receiving functions of the remote terminal equipment in FIG. 8 to FIG. 11 are performed.
  • the transceiver module 1202 may be referred to as a transceiver circuit, a transceiver, a transceiver, or a communication interface.
  • the transceiver module 1202 is configured to send a first identifier and a relay service code to the relay terminal device, where the first identifier is the identifier of the remote terminal device corresponding to the relay service code or the first identifier is the remote terminal.
  • the anonymous identification of the device; the processing module 1201 is configured to generate a root key for the communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter, and the remote terminal device communicates with the relay terminal device.
  • the terminal authentication service function network element is the authentication service function network element serving the remote terminal device, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element.
  • the first identifier is the SUCI of the remote terminal device.
  • the processing module 1201 and the transceiver module 1202 are further configured to acquire the first identifier.
  • the transceiver module 1202 is further configured to send a relay service code; and receive a first identifier corresponding to the relay service code.
  • the processing module 1201 is further configured to generate a temporary identification according to the first shared key and the relay service code; and obtain the first identification according to the temporary identification.
  • the processing module 1201 is further configured to generate a temporary identifier according to the first shared key, the relay service code and the second freshness parameter.
  • the processing module 1201 is further configured to generate the first identifier according to the second freshness parameter, the routing indication and the home network identifier.
  • the transceiver module 1202 is further configured to send a relay service code; and receive a second freshness parameter corresponding to the relay service code.
  • the second freshness parameter is the value of a counter maintained locally by the remote terminal device.
  • the first identifier includes a routing indication and a home network identifier.
  • the transceiver module 1202 is further configured to send the first verification information to the relay terminal device, where the first verification information consists of the first temporary key, and all or part of the message carrying the first verification information Cells are generated, and the first temporary key is generated from the first shared key.
  • the first temporary key is composed of at least one of the relay service code, the third freshness parameter, the second identifier of the remote terminal device, and the first identifier, and the first shared secret key.
  • key generation wherein the third freshness parameter is generated by the remote terminal device.
  • the transceiver module 1202 is further configured to send second verification information to the relay terminal device, where the second verification information is generated from the first freshness parameter, the relay service code and the first shared key.
  • the at least one first freshness parameter includes a first random number
  • the transceiver module 1202 is further configured to send the first random number to the relay terminal device.
  • the first random number is sent to the remote AUSF network element or the PKMF network element.
  • the at least one first freshness parameter includes a second random number
  • the transceiver module 1202 is further configured to receive the second random number from the relay terminal device.
  • the second random number may come from a remote AUSF network element or a PKMF network element.
  • the at least one first freshness parameter is the value of a counter maintained locally by the remote terminal device.
  • the first shared key is the key Kausf negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • the processing module 1201 is further configured to generate a second shared key according to the first shared key and the relay service code, and generate a root root according to the second shared key and the at least one first freshness parameter key, and the second shared key is the key shared by the remote terminal device and the adjacent service key management function network element.
  • FIG. 13 shows a schematic structural diagram of a communication device 130 .
  • the communication apparatus 130 may be the AUSF network element in FIG. 1 .
  • the communication device 130 includes a processing module 1301 and a transceiver module 1302 .
  • the processing module 1301 may also be referred to as a processing unit, and is used to implement the processing function of the remote AUSF network element in the above method embodiments, and the processing function of the remote AUSF network element in FIG. 8 to FIG. 11 . For example, steps S601-S603 in FIG. 6 are performed.
  • the transceiver module 1302 which may also be referred to as a transceiver unit, is used to implement the transceiver function of the remote AUSF network element in the above method embodiments. For example, steps S601 and S604 in FIG. 6 are performed, and the sending and receiving functions of the remote AUSF network elements in FIG. 8 to FIG. 11 are performed.
  • the transceiver module 1302 may be referred to as a transceiver circuit, a transceiver, a transceiver, or a communication interface.
  • the processing module 1301 is configured to obtain one of the first identifier or the second identifier of the remote terminal device, and the relay service code; the second identifier is the permanent identifier of the remote terminal device, and the first identifier is The identifier corresponding to the relay service code of the remote terminal device; the processing module 1301 is further configured to obtain the first shared key corresponding to the first identifier or the second identifier; the first shared key is the remote terminal device and the remote authentication The key shared by the service function network element; the remote authentication service function network element generates a communication between the remote terminal device and the relay terminal device according to the first shared key, the relay service code, and at least one first freshness parameter. Root key; the transceiver module 1302 is used to send the root key.
  • the transceiver module 1302 is further configured to receive one of the first identifier or the second identifier of the remote terminal device.
  • the processing module 1301 is further configured to generate a temporary identifier according to the first shared key and the relay service code; the remote authentication service function network element generates the first identifier according to the temporary identifier.
  • the processing module 1301 is further configured to generate a temporary identifier according to the first shared key, the relay service code and the second freshness parameter.
  • the processing module 1301 is further configured to generate the first identifier according to the second freshness parameter, the routing indication and the home network identifier of the remote terminal device.
  • the second freshness parameter is a value of a counter maintained locally by the remote authentication service function network element.
  • the transceiver module 1302 is further configured to receive the relay service code and send the second freshness parameter.
  • the transceiver module 1302 is further configured to receive a relay service code; and send the first identifier.
  • the first identifier includes a routing indication and a home network identifier.
  • the transceiver module 1302 is further configured to receive the first verification information; the processing module 1301 is further configured to generate a first temporary key according to the first shared key; and according to the first temporary key, and , all or part of the information elements of the message carrying the first verification information are obtained to obtain the third verification information; the first verification information and the third verification information are compared to verify the remote terminal device.
  • the processing module 1301 is further configured to, according to at least one of the relay service code, the third freshness parameter, the second identifier, and the first identifier of the remote terminal device, and the first shared The key is to generate the first temporary key, and the third freshness parameter is generated for the remote terminal device.
  • the at least one first freshness parameter includes a first random number
  • the transceiver module 1302 is further configured to receive the first random number
  • the at least one first freshness parameter includes a second random number
  • the transceiver module 1302 is further configured to send the second random number
  • the at least one first freshness parameter is the value of a counter maintained locally by the remote authentication service function network element.
  • the transceiver module 1302 is further configured to send the first identifier to the unified data management network element.
  • the first shared key is the key Kausf negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • FIG. 14 shows a schematic structural diagram of a communication device 140 .
  • the communication device 140 includes a processing module 1401 and a transceiver module 1402 .
  • the processing module 1401 may also be called a processing unit, and is used to implement the processing function of the PKMF network element in the above method embodiments.
  • step S702 in FIG. 7 is executed, and the processing function of the PKMF network element in FIG. 8 to FIG. 11 is performed.
  • the transceiver module 1402 which may also be called a transceiver unit, is used to implement the transceiver function of the PKMF network element in the above method embodiments.
  • the transceiver module 1402 may be referred to as a transceiver circuit, a transceiver, a transceiver, or a communication interface.
  • the transceiver module 1402 is configured to receive the first identifier and the relay service code of the remote terminal device, where the first identifier is the identifier of the remote terminal device corresponding to the relay service code or the first identifier is the remote terminal device.
  • the anonymous identifier the processing module 1401 is configured to obtain the root key of the communication between the remote terminal device and the relay terminal device according to the first identifier, and the root key consists of the first shared key, the relay service code, and at least one first The freshness parameter is generated, and the first shared key is the key shared by the remote terminal device and the remote authentication service function network element; the transceiver module 1402 is further configured to send the root key.
  • the transceiver module 1402 is further configured to send the first identification to the unified data management function network element; receive identification information of the remote authentication service function network element from the unified data management function network element; according to the identification information, Send the first identifier to the corresponding remote authentication service function network element; receive the root key from the remote authentication service function network element.
  • the transceiver module 1402 is further configured to send the first identification to the unified data management function network element; receive the identification information of the remote authentication service function network element and the remote terminal equipment from the unified data management function network element According to the identification information, send the permanent identity of the remote terminal device to the corresponding remote authentication service function network element; receive the root key from the remote authentication service function network element.
  • the transceiver module 1402 is further configured to receive at least one second shared key from the remote authentication service function network element, where the second shared key is the remote terminal device and the adjacent service key management function network meta-shared key, the second shared key is generated from the first shared key and the relay service code; the processing module 1401 is further configured to correspond to the second shared key according to the first identifier, and at least one first freshness parameter to generate the root key for the communication between the remote terminal device and the relay terminal device.
  • the method further includes: the transceiver module 1402 is further configured to receive second verification information; the processing module 1401 is further configured to generate fourth verification information according to the first freshness parameter and the second shared key; compare The second verification information and the fourth verification secret information are used to verify the remote terminal device.
  • the at least one first freshness parameter includes a first random number
  • the transceiver module 1402 is further configured to receive the first random number
  • the at least one first freshness parameter includes a second random number
  • the transceiver module 1402 is further configured to send the second random number
  • the at least one first freshness parameter is the value of a counter maintained locally by the network element of the adjacent service key management function.
  • the first shared key is the key Kausf negotiated with the remote authentication service function network element when the remote terminal device accesses the network.
  • Module herein may refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and/or other device that may provide the functions described above.
  • the function/implementation process of the processing module may be implemented by the processor in the communication device calling the computer-executed instructions stored in the memory.
  • the function/implementation process of the transceiver module can be implemented through a transceiver or a communication interface in the communication device.
  • an embodiment of the present application further provides a communication device.
  • the communication device 150 includes a processor 1501 , a memory 1502 and a transceiver 1503 .
  • the processor 1501 is coupled to the memory 1502 .
  • the processor 1501 executes the memory 1502
  • the methods corresponding to the remote terminal equipment in FIG. 2-FIG. 11 are executed.
  • an embodiment of the present application further provides a communication device.
  • the communication device 160 includes a processor 1601, a memory 1602, and a communication interface 1603.
  • the processor 1601 is coupled to the memory 1602. When the processor 1601 executes the memory 1602
  • the method corresponding to the AUSF network element eg, the remote AUSF network element, the relay AUSF network element in FIG. 2-FIG. 11 is executed.
  • an embodiment of the present application further provides a communication device.
  • the communication device 170 includes a processor 1701, a memory 1702, and a communication interface 1703.
  • the processor 1701 is coupled to the memory 1702.
  • the processor 1701 executes the memory 1702
  • the method corresponding to the PKMF network element in FIG. 2-FIG. 11 is executed.
  • Embodiments of the present application also provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when it runs on a computer or a processor, the computer or the processor causes the computer or the processor to execute the programs in FIGS. 2 to 11 .
  • Embodiments of the present application also provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when it runs on a computer or a processor, the computer or the processor causes the computer or the processor to execute the programs in FIGS. 2 to 11 .
  • Methods corresponding to AUSF network elements eg, remote AUSF network elements, relay AUSF network elements).
  • Embodiments of the present application also provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when it runs on a computer or a processor, the computer or the processor causes the computer or the processor to execute the programs in FIGS. 2 to 11 .
  • Embodiments of the present application also provide a computer program product containing instructions, when the instructions are executed on a computer or processor, the computer or processor can execute the methods corresponding to the remote terminal devices in FIG. 2-FIG. 11 .
  • the embodiment of the present application also provides a computer program product containing instructions, when the instructions are run on a computer or a processor, the computer or processor is made to execute the AUSF network elements in FIG. 2-FIG. 11 (for example, a remote AUSF network element, Relay AUSF network element) corresponding method.
  • a remote AUSF network element for example, a remote AUSF network element, Relay AUSF network element
  • Embodiments of the present application also provide a computer program product containing instructions, when the instructions are run on a computer or processor, the computer or processor can execute the methods corresponding to the PKMF network elements in FIG. 2-FIG. 11 .
  • An embodiment of the present application provides a chip system, where the chip system includes a processor, which is used for the communication device to execute the method corresponding to the remote terminal device in FIG. 2 to FIG. 11 , or to execute the AUSF network element ( For example, the method corresponding to the remote AUSF network element, the relay AUSF network element), or the method corresponding to the PKMF network element in FIG. 2-FIG. 11 is performed.
  • the chip system includes a processor, which is used for the communication device to execute the method corresponding to the remote terminal device in FIG. 2 to FIG. 11 , or to execute the AUSF network element ( For example, the method corresponding to the remote AUSF network element, the relay AUSF network element), or the method corresponding to the PKMF network element in FIG. 2-FIG. 11 is performed.
  • the chip system further includes a memory for storing necessary program instructions and data.
  • the chip system may include chips, integrated circuits, or chips and other discrete devices, which are not specifically limited in this embodiment of the present application.
  • the communication device, chip, computer storage medium, computer program product or chip system provided in this application are all used to execute the method described above, therefore, the beneficial effects that can be achieved can refer to the embodiments provided above The beneficial effects of , will not be repeated here.
  • the processor involved in the embodiments of the present application may be a chip.
  • it can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a central processing unit.
  • It can be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (MCU) , it can also be a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processing circuit
  • MCU microcontroller
  • PLD programmable logic device
  • the memory involved in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed systems, devices and methods may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, optical fiber, Digital Subscriber Line, DSL) or wireless (eg infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer, or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium eg, a Solid State Disk (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种密钥获取方法和通信装置，涉及通信领域，用于在远端终端设备与中继终端设备之间共享密钥。密钥获取方法包括：远端终端设备向中继终端设备发送第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；远端终端设备根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥，远端认证服务功能网元为服务远端终端设备的认证服务功能网元，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥。

Description

密钥获取方法和通信装置 技术领域
本申请涉及通信领域，尤其涉及一种密钥获取方法和通信装置。
背景技术
随着移动通信的高速发展，新业务类型，如视频聊天、虚拟现实(virtual reality，VR)等数据业务的普遍使用提高了用户对带宽的需求。设备到设备(device-to-device，D2D)通信允许终端设备之间直接进行通信，可以在小区网络的控制下与小区用户共享频谱资源，有效的提高频谱资源的利用率。
当终端设备处于网络覆盖之外或与无线接入网络(radio access network，RAN)网元之间通信信号不好时，远端终端设备(Remote UE)可以通过中继终端设备(Relay UE)进行辅助通信，即远端终端设备与中继终端设备之间建立PC5连接，中继终端设备与移动网络建立连接，进而实现远端终端设备通过PC5连接和中继终端设备与移动网络建立连接，并获得服务。
在非直接通信连接建立过程中，为了保证通信的安全，远端终端设备与中继终端设备之间需要建立安全连接，即远端终端设备与中继终端设备之间传输的数据被加密保护和/或完整性保护。由于非直接通信连接是按需动态建立的，远端终端设备与中继终端设备之间无法预配置共享的安全信息(如密钥)，进而无法基于预配置的共享安全信息建立远端终端设备与中继终端设备的之间的安全连接。
发明内容
本申请实施例提供一种密钥获取方法和通信装置，用于在远端终端设备与中继终端设备之间共享密钥。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种密钥获取方法，包括：远端终端设备向中继终端设备发送第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；远端终端设备根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥，远端认证服务功能网元为服务远端终端设备的认证服务功能网元，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥。
本申请实施例提供的密钥获取方法，远端终端设备向中继终端设备发送第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识。远端终端设备根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。其中的第一标识用于远端AUSF网元确定对应的第一共享密钥，或者用于PKMF网元确定对应的第二共享密钥，而第二共享密钥同样是由第一共享密钥和/或中继服务码生成，使得远端终端设备与远端AUSF网元或PKMF网元能够采用相同的方式生成远端终端设备与中继终端设备通信的根密钥，实现了在远端终端设备与中继终端设备之间共享密钥。
在一种可能的实施方式中，第一标识为远端终端设备的订阅隐藏标识SUCI。在空口传输过程中不会暴露远端终端设备的SUPI。
在一种可能的实施方式中，还包括：远端终端设备获取第一标识。
在一种可能的实施方式中，远端终端设备获取第一标识，包括：远端终端设备发送中继服务码；远端终端设备接收与中继服务码对应的第一标识。可以从远端AUSF网元获取与中继服务码对应的第一标识。
在一种可能的实施方式中，还包括：远端终端设备根据第一共享密钥、中继服务码，生成临时标识；远端终端设备根据临时标识获取第一标识。该实施方式公开了生成第一标识的一种方式。
在一种可能的实施方式中，远端终端设备根据第一共享密钥、中继服务码生成临时标识，包括：远端终端设备根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。该实施方式公开了生成临时标识的一种方式。
在一种可能的实施方式中，远端终端设备获取第一标识，包括：远端终端设备根据第二新鲜性参数、路由指示和家乡网络标识，生成第一标识。该实施方式公开了生成第一标识的一种方式。
在一种可能的实施方式中，还包括：远端终端设备发送中继服务码；远端终端设备接收中继服务码对应的第二新鲜性参数。第二新鲜性参数可以来自远端AUSF网元，用于生成第一标识，第二新鲜性参数可以是远端AUSF网元生成的随机数或者远端AUSF网元本地维护的计数器的值。
在一种可能的实施方式中，第二新鲜性参数为远端终端设备本地维护的计数器的值。远端AUSF网元与远端终端设备分别本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。
在一种可能的实施方式中，第一标识包括路由指示和家乡网络标识。便于PKMF网元通过路由指示和家乡网络标识确定UDM网元或远端AUSF网元。
在一种可能的实施方式中，还包括：远端终端设备向中继终端设备发送第一验证信息，第一验证信息由第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元生成，第一临时密钥由第一共享密钥生成。第一验证信息用于发送给远端AUSF网元，远端AUSF网元接收第一验证信息后，按照与远端终端设备相同的方式生成第三验证信息，远端AUSF网元比较第一验证信息和第三验证信息以对远端终端设备进行验证，验证是否授权远端终端设备通过中继终端设备接入网络获取业务。
在一种可能的实施方式中，第一临时密钥由中继服务码、第三新鲜性参数、远端终端设备的第二标识以及第一标识中的至少一项，以及，第一共享密钥生成，其中，第三新鲜性参数为远端终端设备生成。该实施方式公开了生成第一临时密钥的一种方式。
在一种可能的实施方式中，还包括：远端终端设备向中继终端设备发送第二验证信息，第二验证信息由第一新鲜性参数、中继服务码和第一共享密钥生成。第二验证信息用于发送给PKMF网元，PKMF网元接收第二验证信息后，按照与远端终端设备相同的方式生成第四验证信息，PKMF网元比较第二验证信息和第四验证信息以对远端终端设备进行验证，验证是否授权远端终端设备通过中继终端设备接入网络获取业 务。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，还包括：远端终端设备向中继终端设备发送第一随机数。第一随机数发送给远端AUSF网元或PKMF网元。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，还包括：远端终端设备从中继终端设备接收第二随机数。第二随机数可以来自远端AUSF网元或PKMF网元。
在一种可能的实施方式中，至少一个第一新鲜性参数为远端终端设备本地维护的计数器的值。远端AUSF网元或PKMF网元中的一个与终端设备在本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf(或由该密钥生成的其他密钥)。
在一种可能的实施方式中，远端终端设备根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥，包括：远端终端设备根据第一共享密钥和中继服务码生成第二共享密钥，根据第二共享密钥以及至少一个第一新鲜性参数，生成根密钥，第二共享密钥为远端终端设备与临近业务密钥管理功能网元共享的密钥。远端终端设备和PKMF网元采用相同的方式生成根密钥。
第二方面，提供了一种密钥获取方法，包括：远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码；第二标识为远端终端设备的永久身份标识，第一标识为远端终端设备的与中继服务码对应的标识；远端认证服务功能网元获取第一标识或第二标识对应的第一共享密钥；第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；远端认证服务功能网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥；远端认证服务功能网元发送根密钥。
本申请实施例提供的密钥获取方法，远端AUSF网元获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码；第二标识为远端终端设备的永久身份标识，第一标识为远端终端设备的与中继服务码对应的标识；远端AUSF网元获取第一标识或第二标识对应的第一共享密钥；第一共享密钥为远端终端设备与远端AUSF网元共享的密钥；远端AUSF网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥；远端AUSF发送根密钥。其中的第一标识用于远端AUSF网元确定对应的第一共享密钥，使得远端终端设备和远端AUSF网元能够采用相同的方式生成远端终端设备与中继终端设备通信的根密钥，实现了在远端终端设备与中继终端设备之间共享密钥。
在一种可能的实施方式中，远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，包括：远端认证服务功能网元接收远端终端设备的第一标识或第二标识中的一个。远端终端设备的第一标识或第二标识中的一个可以来自远端终端设备或PKMF网元。
在一种可能的实施方式中，远端认证服务功能网元获取远端终端设备的第一标识 或第二标识中的一个，包括：远端认证服务功能网元根据第一共享密钥、中继服务码，生成临时标识；远端认证服务功能网元根据临时标识生成第一标识。该实施方式公开了生成第一标识的一种方式。生成第一标识之后，可以发送给远端终端设备。
在一种可能的实施方式中，远端认证服务功能网元根据第一共享密钥、中继服务码，生成临时标识，包括：远端终端设备根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。该实施方式公开了生成临时标识的一种方式。
在一种可能的实施方式中，远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，包括：远端认证服务功能网元根据第二新鲜性参数、路由指示和远端终端设备的家乡网络标识，生成第一标识。该实施方式公开了生成第一标识的一种方式。生成第一标识之后，可以发送给远端终端设备。
在一种可能的实施方式中，第二新鲜性参数为远端认证服务功能网元本地维护的计数器的值。远端AUSF网元与远端终端设备分别本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。
在一种可能的实施方式中，还包括：远端认证服务功能网元接收中继服务码；远端认证服务功能网元发送第二新鲜性参数。第二新鲜性参数可以发送给远端终端设备，用于生成第一标识，第二新鲜性参数可以是远端AUSF网元生成的随机数或者远端AUSF网元本地维护的计数器的值。
在一种可能的实施方式中，还包括：远端认证服务功能网元接收中继服务码；远端认证服务功能网元发送第一标识。中继服务码来自远端终端设备，第一标识用于发送给远端终端设备。
在一种可能的实施方式中，第一标识包括路由指示和家乡网络标识。便于PKMF网元通过路由指示和家乡网络标识确定UDM网元或远端AUSF网元。
在一种可能的实施方式中，还包括：远端认证服务功能网元接收第一验证信息；远端认证服务功能网元根据第一共享密钥，生成第一临时密钥；并根据第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元，得到第三验证信息；远端认证服务功能网元比较第一验证信息和第三验证信息以对远端终端设备进行验证。即验证是否授权远端终端设备通过中继终端设备接入网络获取业务。
在一种可能的实施方式中，远端认证服务功能网元根据第一共享密钥，生成第一临时密钥，包括：远端认证服务功能网元根据中继服务码、第三新鲜性参数、第二标识以及远端终端设备的第一标识中的至少一项，以及，第一共享密钥，生成第一临时密钥，第三新鲜性参数为远端终端设备生成。该实施方式公开了生成第一临时密钥的一种方式。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，还包括：远端认证服务功能网元接收第一随机数。第一随机数来自远端终端设备。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，还包括：远端认证服务功能网元发送第二随机数。第二随机数发送给远端终端设备。
在一种可能的实施方式中，至少一个第一新鲜性参数为远端认证服务功能网元本地维护的计数器的值。远端AUSF网元与远端终端设备分别本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。
在一种可能的实施方式中，还包括：远端认证服务功能网元向统一数据管理网元发送第一标识。用于其他网元(例如PKMF网元)从UDM网元获取远端AUSF网元实例标识和/或远端终端设备的SUPI。远端AUSF网元实例标识用于确定服务远端终端设备的远端AUSF网元。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf(或由该密钥生成的其他密钥)。
第三方面，提供了一种密钥获取方法，包括：临近业务密钥管理功能网元接收远端终端设备的第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；临近业务密钥管理功能网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥，根密钥由第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数生成，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；临近业务密钥管理功能网元发送根密钥。
本申请实施例提供的密钥获取方法，PKMF网元接收远端终端设备的第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；PKMF网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥，根密钥由第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数生成，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；PKMF网元发送根密钥。其中的第一标识用于PKMF网元确定对应的第二共享密钥，使得远端终端设备和PKMF网元能够采用相同的方式生成远端终端设备与中继终端设备通信的根密钥，实现了在远端终端设备与中继终端设备之间共享密钥。
在一种可能的实施方式中，临近业务密钥管理功能网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥，包括：临近业务密钥管理功能网元向统一数据管理功能网元发送第一标识；临近业务密钥管理功能网元从统一数据管理功能网元接收远端认证服务功能网元的标识信息；临近业务密钥管理功能网元根据标识信息，向对应的远端认证服务功能网元发送第一标识；临近业务密钥管理功能网元从远端认证服务功能网元接收根密钥。该实施方式公开了PKMF网元获取根密钥的一种方式。
在一种可能的实施方式中，临近业务密钥管理功能网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥，包括：临近业务密钥管理功能网元向统一数据管理功能网元发送第一标识；临近业务密钥管理功能网元从统一数据管理功能网元接收远端认证服务功能网元的标识信息以及远端终端设备的永久身份标识；临近业务密钥管理功能网元根据标识信息，向对应的远端认证服务功能网元发送远端终端设备的永久身份标识；临近业务密钥管理功能网元从远端认证服务功能网元接收根密钥。该实施方式公开了PKMF网元获取根密钥的一种方式。
在一种可能的实施方式中，临近业务密钥管理功能网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥，包括：临近业务密钥管理功能网元从远端认证服务功能网元接收至少一个第二共享密钥，第二共享密钥为远端终端设备与临近业务密钥管理功能网元共享的密钥，第二共享密钥由第一共享密钥和中继服务码生成；临近业务密钥管理功能网元根据第一标识对应的第二共享密钥，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。该实施方式公开了PKMF 网元获取根密钥的一种方式。
在一种可能的实施方式中，还包括：临近业务密钥管理功能网元接收第二验证信息；临近业务密钥管理功能网元根据第一新鲜性参数和第二共享密钥，生成第四验证信息；临近业务密钥管理功能网元比较第二验证信息和第四验证密信息以对远端终端设备进行验证。即验证是否授权远端终端设备通过中继终端设备接入网络获取业务。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，还包括：临近业务密钥管理功能网元接收第一随机数。第一随机数来自远端终端设备。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，还包括：临近业务密钥管理功能网元发送第二随机数。第二随机数发送给远端终端设备。
在一种可能的实施方式中，至少一个第一新鲜性参数为临近业务密钥管理功能网元本地维护的计数器的值。PKMF网元与远端终端设备分别本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf(或由该密钥生成的其他密钥)。
第四方面，提供了一种通信装置，包括收发模块和处理模块；收发模块，用于向中继终端设备发送第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；处理模块，用于根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥，远端认证服务功能网元为服务远端终端设备的认证服务功能网元，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥。
在一种可能的实施方式中，第一标识为远端终端设备的SUCI。
在一种可能的实施方式中，处理模块和收发模块还用于获取第一标识。
在一种可能的实施方式中，收发模块还用于发送中继服务码；接收与中继服务码对应的第一标识。
在一种可能的实施方式中，处理模块还用于根据第一共享密钥、中继服务码，生成临时标识；根据临时标识获取第一标识。
在一种可能的实施方式中，处理模块还用于根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。
在一种可能的实施方式中，处理模块还用于根据第二新鲜性参数、路由指示和家乡网络标识，生成第一标识。
在一种可能的实施方式中，收发模块还用于发送中继服务码；接收中继服务码对应的第二新鲜性参数。
在一种可能的实施方式中，第二新鲜性参数为远端终端设备本地维护的计数器的值。
在一种可能的实施方式中，第一标识包括路由指示和家乡网络标识。
在一种可能的实施方式中，收发模块还用于向中继终端设备发送第一验证信息，第一验证信息由第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元生成，第一临时密钥由第一共享密钥生成。
在一种可能的实施方式中，第一临时密钥由中继服务码、第三新鲜性参数、远端 终端设备的第二标识以及第一标识中的至少一项，以及，第一共享密钥生成，其中，第三新鲜性参数为远端终端设备生成。该实施方式公开了生成第一临时密钥的一种方式。
在一种可能的实施方式中，收发模块还用于向中继终端设备发送第二验证信息，第二验证信息由第一新鲜性参数、中继服务码和第一共享密钥生成。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，收发模块还用于向中继终端设备发送第一随机数。第一随机数发送给远端AUSF网元或PKMF网元。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，收发模块还用于从中继终端设备接收第二随机数。第二随机数可以来自远端AUSF网元或PKMF网元。
在一种可能的实施方式中，至少一个第一新鲜性参数为远端终端设备本地维护的计数器的值。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf。
在一种可能的实施方式中，处理模块还用于根据第一共享密钥和中继服务码生成第二共享密钥，根据第二共享密钥以及至少一个第一新鲜性参数，生成根密钥，第二共享密钥为远端终端设备与临近业务密钥管理功能网元共享的密钥。
第五方面，提供了一种通信装置，包括收发模块和处理模块；处理模块用于获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码；第二标识为远端终端设备的永久身份标识，第一标识为远端终端设备的与中继服务码对应的标识；处理模块还用于获取第一标识或第二标识对应的第一共享密钥；第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；远端认证服务功能网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥；收发模块用于发送根密钥。
在一种可能的实施方式中，收发模块还用于接收远端终端设备的第一标识或第二标识中的一个。
在一种可能的实施方式中，处理模块还用于根据第一共享密钥、中继服务码，生成临时标识；远端认证服务功能网元根据临时标识生成第一标识。
在一种可能的实施方式中，处理模块还用于根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。
在一种可能的实施方式中，处理模块还用于根据第二新鲜性参数、路由指示和远端终端设备的家乡网络标识，生成第一标识。
在一种可能的实施方式中，第二新鲜性参数为远端认证服务功能网元本地维护的计数器的值。
在一种可能的实施方式中，收发模块还用于接收中继服务码；发送第二新鲜性参数。
在一种可能的实施方式中，收发模块还用于接收中继服务码；发送第一标识。
在一种可能的实施方式中，第一标识包括路由指示和家乡网络标识。
在一种可能的实施方式中，收发模块还用于接收第一验证信息；处理模块还用于根据第一共享密钥，生成第一临时密钥；并根据第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元，得到第三验证信息；比较第一验证信息和第三验证信息以对远端终端设备进行验证。
在一种可能的实施方式中，处理模块还用于根据中继服务码、第三新鲜性参数、第二标识以及远端终端设备的第一标识中的至少一项，以及，第一共享密钥，生成第一临时密钥，第三新鲜性参数为远端终端设备生成。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，收发模块还用于接收第一随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，收发模块还用于发送第二随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数为远端认证服务功能网元本地维护的计数器的值。
在一种可能的实施方式中，收发模块还用于向统一数据管理网元发送第一标识。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf。
第六方面，提供了一种通信装置，包括收发模块和处理模块；收发模块用于接收远端终端设备的第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；处理模块用于根据第一标识获取远端终端设备与中继终端设备通信的根密钥，根密钥由第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数生成，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；收发模块还用于发送根密钥。
在一种可能的实施方式中，收发模块还用于向统一数据管理功能网元发送第一标识；从统一数据管理功能网元接收远端认证服务功能网元的标识信息；根据标识信息，向对应的远端认证服务功能网元发送第一标识；从远端认证服务功能网元接收根密钥。
在一种可能的实施方式中，收发模块还用于向统一数据管理功能网元发送第一标识；从统一数据管理功能网元接收远端认证服务功能网元的标识信息以及远端终端设备的永久身份标识；根据标识信息，向对应的远端认证服务功能网元发送远端终端设备的永久身份标识；从远端认证服务功能网元接收根密钥。
在一种可能的实施方式中，收发模块还用于从远端认证服务功能网元接收至少一个第二共享密钥，第二共享密钥为远端终端设备与临近业务密钥管理功能网元共享的密钥，第二共享密钥由第一共享密钥和中继服务码生成；处理模块还用于根据第一标识对应的第二共享密钥，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
在一种可能的实施方式中，还包括：收发模块还用于接收第二验证信息；处理模块还用于根据第一新鲜性参数和第二共享密钥，生成第四验证信息；比较第二验证信息和第四验证密信息以对远端终端设备进行验证。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，收发模块还用于接收第一随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，收发模块还用于发送第二随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数为临近业务密钥管理功能网元本地维护的计数器的值。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf。
第七方面，提供了一种通信装置，包括处理器，处理器与存储器相连，存储器用于存储计算机程序，处理器用于执行存储器中存储的计算机程序，以使得通信装置执行如第一方面及其任一项实施方式的方法。
第八方面，提供了一种通信装置，包括处理器，处理器与存储器相连，存储器用于存储计算机程序，处理器用于执行存储器中存储的计算机程序，以使得通信装置执行如第二方面及其任一项实施方式所述的方法。
第九方面，提供了一种通信装置，包括处理器，处理器与存储器相连，存储器用于存储计算机程序，处理器用于执行存储器中存储的计算机程序，以使得通信装置执行如第三方面及其任一项实施方式所述的方法。
第十方面，提供了一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序，当其在计算机上运行时，使得计算机执行如第一方面及其任一项实施方式所述的方法。
第十一方面，提供了一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序，当其在计算机上运行时，使得计算机执行如第二方面及其任一项实施方式所述的方法。
第十二方面，提供了一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序，当其在计算机上运行时，使得计算机执行如第三方面及其任一项实施方式所述的方法。
第十三方面，提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行如第一方面及任一项实施方式所述的方法。
第十四方面，提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器，执行如第二方面及其任一项实施方式所述的方法。
第十五方面，提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器，执行如第三方面及其任一项实施方式所述的方法。
第十六方面，提供了一种通信系统，包括如第四方面及其任一项所述的通信装置、如第五方面及其任一项所述的通信装置，以及，如第六方面及其任一项所述的通信装置；或者，包括如第七方面所述的通信装置、如第八方面及其任一项所述的通信装置，以及，如第九方面及其任一项所述的通信装置。
第四方面到第十六方面的技术效果参照第一方面至第三方面的内容，在此不再重复。
附图说明
图1为本申请实施例提供的一种通信系统的架构示意图；
图2为本申请实施例提供的一种密钥获取方法的流程示意图一；
图3为本申请实施例提供的一种密钥获取方法的流程示意图二；
图4为本申请实施例提供的一种密钥获取方法的流程示意图三；
图5为本申请实施例提供的一种密钥获取方法的流程示意图四；
图6为本申请实施例提供的一种密钥获取方法的流程示意图五；
图7为本申请实施例提供的一种密钥获取方法的流程示意图六；
图8为本申请实施例提供的一种密钥获取方法的流程示意图七；
图9为本申请实施例提供的一种密钥获取方法的流程示意图八；
图10为本申请实施例提供的一种密钥获取方法的流程示意图九；
图11为本申请实施例提供的一种密钥获取方法的流程示意图十；
图12为本申请实施例提供的一种通信装置的结构示意图一；
图13为本申请实施例提供的一种通信装置的结构示意图二；
图14为本申请实施例提供的一种通信装置的结构示意图三；
图15为本申请实施例提供的一种通信装置的结构示意图四；
图16为本申请实施例提供的一种通信装置的结构示意图五；
图17为本申请实施例提供的一种通信装置的结构示意图六。
具体实施方式
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中，“/”表示该符号前后两者是“或”的关系。
本申请实施例既可以应用于时分双工(time division duplexing，TDD)的场景，也可以适用于频分双工(frequency division duplexing，FDD)的场景，不予限制。
本申请实施例依托无线通信网络中5G网络的场景进行说明，应当指出的是，本申请实施例中的方案还可以应用于其他无线通信网络中，相应的名称也可以用其他无线通信网络中的对应功能的名称进行替代。
图1提供了一种5G通信系统架构，包括接入网和核心网。接入网用于实现无线接入有关的功能，接入网包括3GPP接入网和non-3GPP的接入网。该通信系统包括：终端设备101、(无线)接入网((radio)access network，(R)AN)网元102、用户面功能(user plane function，UPF)网元103、数据网络(data network，DN)104、接入和移动性管理功能(access and mobility management function，AMF)网元105、会话管理功能(session management function，SMF)网元106、策略控制网元(policy control function，PCF)网元107、统一数据管理网元(unified data management，UDM)网元108、应用功能(application function，AF)网元109、鉴权服务器功能(authentication server function，AUSF)网元110以及网络切片选择功能(network slice selection function，NSSF)网元111、网络开放功能(network exposure function，NEF)网元112、网络功能库(network function repository function，NRF)网元113、网络切片特定认证和授权功能(network slice specific authentication and authorization function，NSSAAF)114和服务通信代理(service communication proxy，SCP)115。
需要说明的是，图1中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，不予限制。例如，终端设备101与AMF网元105之间的接口可以为N1接口，(R)AN网元102与AMF网元105之间的接口可以为N2接口，(R)AN网元102与UPF网元103之间的接口可以为N3接口，UPF网元103与SMF网元106之间的接口可以为N4接口，UPF网元103与DN 104之间的接口可以为N6接口。AMF网元105向网络提供的服务接口Namf，SMF网元106向网络提供的服务接口Nsmf，PCF网元107向网络提供的服务接口Npcf，UDM网元108向网络提供的服务接口Nudm，AF网元向网络提供的服务接口Naf，AUSF网元110向网络提供的服务接口Nausf，NSSF网元111向网络提供的服务接口Nnssf，NEF网元112向网络提供的服务接口Nnef，NRF网元113向网络提供的服务接口Nnrf，NSSAAF网元114向网络提供的服务接口Nnssaaf。
终端设备101与(R)AN网元102之间采用某种空口技术相互通信。终端设备101可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)、移动台(mobile station，MS)、终端设备(terminal device)或者中继用户设备等。其中，中继用户设备可以是5G家庭网关(residential gateway，RG)。为方便描述，上面提到的设备可以统称为终端设备。
本申请实施例中远端终端设备(远端UE)可以通过中继终端设备(中继UE)接入到3GPP网络，并与网络设备和应用服务器进行非直接通信。
(R)AN网元102为终端设备101提供无线接入的设备，包括RAN网元和AN网元，其中，RAN网元主要是3GPP网络无线网络设备，AN网元可以是non-3GPP定义的接入网设备。本申请以RAN网元为例，但不意在限定于此。
其中，RAN网元主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。其可以包括各种形式的基站，例如：宏基站、微基站(也称为小站)、中继站、接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在第五代(5th generation，5G)通信系统中，称为RAN网元或者gNB(5G NodeB)；在长期演进(long term evolution，LTE)系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)通信系统中，称为节点B(Node B)等。
AN网元允许终端设备和3GPP核心网之间采用非3GPP技术互连互通，其中，非3GPP技术包括例如：无线保真(Wireless Fidelity，Wi-Fi)、全球微波互联接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)网络等。
UPF网元103主要负责对用户报文进行处理，如转发、计费等。可以从数据网络接收用户数据，通过RAN网元传输给终端设备；UPF网元还可以通过RAN网元从终 端设备接收用户数据，转发到DN。UPF网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制。
DN 104指的是为用户提供数据传输服务的网络，如IP多媒体业务(IP multi-media service，IMS)、互联网(Internet)等。终端设备101通过建立终端设备、RAN网元102、UPF网元103以及DN 104之间的协议数据单元(protocol data unit，PDU)会话来访问DN 104。其中用户面的路径为：终端设备到(R)AN网元，到UPF网元，再到DN。
AMF网元105主要负责移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。
SMF网元106主要负责移动网络中的会话管理，如会话建立、修改、释放。例如，具体功能包括：为用户分配IP地址、选择提供报文转发功能的UPF网元等。
PCF网元107提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，例如QoS策略、切片选择策略等。同时负责获取与策略决策相关的用户签约信息。
UDM网元108用于生成认证信任状，用户标识处理(如存储和管理用户永久身份等)，接入授权控制和签约数据管理等。
AF网元109也可以称为服务器，负责与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务等。
AUSF网元110用于对用户进行鉴权和授权。
NSSF网元111用于对切片功能进行集中管理。
NEF网元112负责内外部网络隔离，用于支持能力和事件的开放，包括开放监控(Monitoring)能力、策略/计费能力和分析报告能力等。
NRF网元113负责维护可用的网络功能实例的文本和网络功能支持的服务，用于其他网络功能网元进行服务发现或网络功能网元发现。
NSSAAF网元114用于支持网络切片特定的认证和授权流程，可以和AAA(authentication，authorization and accounting，认证授权和计费)服务器或AAA代理通信。
SCP网元115用于支持非直接通信、代理发现以及向目标网络功能网元或下一跳SCP发送路由消息等。
在临近业务(Proximity-based Services，ProSe)的课题研究中，为了支持临近业务通信，还引入了5G直接发现名称管理功能(direct discovery name management Function，DDNMF)网元，用于分配和处理ProSe应用标识和ProSe应用码映射。
如图2所示，在5G通信系统中的非直接通信中，基于层3(对于IP类型的PDU会话，中继终端设备基于IP地址转发数据)的非直接通信连接建立流程包括：
S201、远端终端设备和中继终端设备分别注册到网络，并从网络侧获取授权信息。
对于远端终端设备，获取的授权信息包括：
指示信息，用于指示是否授权通过中继终端设备接入5GC。
用于临近业务中继发现(ProSe Relay Discovery)的参数，这些参数用于使能与中继终端设备建立连接，包括例如中继服务码(relay service code)、PDU会话参数(例 如数据网络名称(data network name，DNN)、单网络切片选择辅助信息(single setwork slice selection assistance information，S-NSSAI)、接入类型偏好、PDU会话类型、会话和业务连续性模式)。
基于中继服务码的用于临近业务中继发现(ProSe Relay Discovery)的安全相关内容。
对于中继终端设备，获取的授权信息包括：
作为中继终端设备的授权策略，包括授权为远端终端设备提供中继业务的公共陆地移动网络(public land mobile network，PLMN)。
用于临近业务中继发现(ProSe Relay Discovery)的参数，包括：指示信息，用于指示授权作为UE与网络之间的中继(UE-to-Network relay)；中继服务码、PDU会话参数(例如DNN、S-NSSAI、接入类型偏好、PDU会话类型、会话和业务连续性模式)。
基于中继服务码的用于临近业务中继发现(ProSe Relay Discovery)的安全相关内容。
S202、中继终端设备建立PDU会话。
该会话可以是专为远端终端设备服务的PDU会话；对于IP类型的PDU会话，网络侧SMF网元为PDU会话分配IP地址(可以为IPv4地址或IPv6前缀等)，中继终端设备利用该PDU会话为远端终端设备传输数据。
该步骤是可选的。
S203、远端终端设备通过中继发现流程发现中继终端设备。
S204、远端终端设备与中继终端设备建立PC5通信链接。
如果中继终端设备已经建立的PDU会话不能满足远端终端设备的会话需求(如DNN、S-NSSAI等)，中继终端设备为远端终端设备建立新的PDU会话，该PDU会话用于远端终端设备与应用服务器之间的传输数据。或者若中继终端设备未建立用于传输远端终端设备的业务的PDU会话，则会建立新的PDU会话，该PDU会话用于远端终端设备与应用服务器之间的传输数据。
S205、中继终端设备为远端终端设备分配用于PC5通信的IP地址。
S206、中继终端设备将远端终端设备的ID和IP信息(IP info)发送给AMF网元和SMF网元。
该IP信息是中继终端设备为远端终端设备分配的用于网络侧通信的地址。
该步骤可以通过PDU会话修改流程进行。例如，若SMF网元为中继终端终端设备分配IP地址为IPv4，则IP信息表示为特定的端口号(TCP/UDP port)，意味着中继终端设备利用该IPv4地址和该特定的端口号传输远端终端设备的数据。若SMF网元为中继终端设备分配的IP地址为IPv6前缀(IPv6prefix)，则IP信息表示为更长的IPv6前缀，意味着中继终端设备利用更长的IPv6前缀传输远端终端设备的数据。
S207、中继终端设备根据IP地址转发远端终端设备的上下行数据。
例如，远端终端设备在PC5通信链路上使用的IP地址为IP3，中继终端设备的PDU会话对应的IP地址为IP1，中继终端设备为远端终端设备分配的IP信息(IP info)为IP1-1。则远端终端设备利用IP3向服务器传输数据，服务器利用IP1-1向远端终端设备传输数据，中继终端设备要绑定IP3和IP1-1的关联关系。
在下行方向，中继终端设备从UPF网元接收到IP1-1数据包，获知数据为远端终端的，再修改IP地址为IP3，通过PC5链路发送给远端终端设备。
在上行方向，中继终端设备接收到IP3数据包后，再修改IP地址为IP1-1，通过PDU会话发送给UPF网元，进而发送到服务器。
在上述非直接通信连接建立过程中，为了保证通信的安全，远端终端设备和中继终端设备之间需要建立安全连接，即远端终端设备和中继终端设备之间传输的数据被加密保护和/或完整性保护。由于非直接通信连接是按需动态建立的，远端终端设备和中继终端设备之间无法预配置共享的安全信息(例如密钥)，进而基于预配置的共享安全信息建立远端终端设备和中继终端设备的之间的安全连接。因此需要动态建立远端终端设备和中继终端设备之间的共享安全信息(例如密钥)。
本申请实施例提供了一种密钥获取方法，如图3所示，包括：
S301、远端终端设备接入3GPP网络并获取中继发现和密钥素材；中继终端设备接入3GPP网络并获取发现和密钥素材。
S302、远端终端设备通过AMF网元向AUSF网元发送密钥请求。
该密钥请求中包括临近业务远端接入指示、5G全球唯一临时标识(globally unique temporary identity，GUTI)或用户隐藏标识(subscription concealed identifier，SUCI)。
S303、AUSF网元向UDM网元发送认证请求。
该认证请求中包括临近业务远端接入指示、5G-GUTI或SUCI。
S304、UDM网元向AUSF网元发送认证响应。
该认证响应中包括用户的永久身份标识(subscription permanent identifier，SUPI)。
S305、AUSF网元使用最新的远端终端设备与AUSF网元之间共享的密钥(Kausf)生成根密钥(REAR Key)。
S306、AUSF网元向远端终端设备发送密钥响应。
该密钥响应中包括根密钥和中继终端设备的标识。
S307、远端终端设备发现中继终端设备。
S308、远端终端设备向中继终端设备发送直接通信请求。
该直接通信请求中包括中继服务码、5G-GUTI和消息验证码(message authentication code，MAC)。
S309、中继终端设备向AUSF网元发送密钥请求。
该密钥请求中包括中继服务码、5G-GUTI和MAC。
S310、AUSF网元执行认证和授权检查。
S311、授权之后，AUSF网元生成远端终端设备的密钥K NR_ProSe。
K NR_ProSe＝KDF(根密钥REAR密钥,5G-GUTI,中继服务码或服务标识,新鲜性参数,其他可能的参数)。其中，密钥推演函数(key derivation function，KDF)是一种生成密钥的算法。
S312、AUSF网元向中继终端设备发送密钥响应。
该密钥响应中包括KNR_ProSe和新鲜性参数。
S313、中继终端设备向远端终端设备发送直接安全模式命令。
该直接安全模式命令中包括生成K NR_ProSe的新鲜性参数。
S314、远端终端设备根据直接安全模式命令生成密钥K NR_ProSe。
S315、远端终端设备根据直接安全模式命令向中继终端设备发送直接安全模式命令完成消息。
该方案中，密钥推演过程中使用了中继终端设备的标识，但是由于存在一个或多个终端设备能够提供中继服务，在远端终端设备发现中继终端设备之前，网络无法获取提供中继服务的终端设备的标识，因此无法推演对应的密钥。此外，未定义推演密钥的AUSF网元如何确定，也未定义中继终端设备如何发现远端终端设备推演密钥的AUSF网元。若中继终端设备任意选择AUSF网元，如果该AUSF网元未存储远端终端设备获取的密钥，则无法验证远端终端设备生成的MAC。
本申请实施例提供了一种密钥获取方法，如图4所示，包括：
S401、远端终端设备和中继终端设备分别获取发现密钥素材。
具体的，包括：
远端终端设备与临近业务(ProSe)功能网元交互以获取中继发现参数和临近业务密钥管理功能(ProSe key management function，PKMF)网元的地址。
远端终端设备从中继的PKMF网元获取发现密钥素材。
中继终端设备与临近业务(ProSe)功能网元交互以获取中继发现参数和PKMF网元的地址。
中继终端设备从PKMF获取网元发现密钥素材。
S402、远端终端设备向PKMF网元发送密钥请求。
该密钥请求中包括指示信息，用于请求中继通信密钥。可选的包括之前获取的密钥的密钥标识——临近业务中继用户密钥(ProSe relay user key，PRUK)ID。
相应地，PKMF网元向远端终端设备发送响应消息，该响应消息中包括PRUK和对应的PRUK Id。
S403、远端终端设备发现中继终端设备。
S404、远端终端设备向中继终端设备发送直接通信请求。
该直接通信请求中包括PRUK ID或国际移动用户识别码(international mobile subscriber identity，IMSI)中的一个、中继服务码。
S405、中继终端设备向PKMF网元发送密钥请求。
该密钥请求中包括PRUK ID或IMSI中的一个、中继服务码和第一随机数。
S406、PKMF网元根据PRUK ID或IMSI识别终端设备，并执行授权检查。
授权检查通过后，PKMF网元确定远端终端设备是否需要新的PRUK。若需要，PKMF网元与归属用户服务器(home subscriber server，HSS)网元交互以获取用户的通用引导信息(generic bootstrapping information，GPI)(通用引导架构(generic bootstrapping architecture，GBA)推送信息(Push Info)、GBA推送信息)或认证向量。
S407、PKMF网元向中继终端设备发送密钥响应。
该密钥响应中包括密钥Kd、生成密钥Kd的随机数、GPI、远端终端设备标识。
S408、中继终端设备向远端终端设备发送直接安全模式命令。
该直接安全模式命令中包括生成密钥Kd的随机数、GPI。
相应地，远端终端设备向中继终端设备发送直接安全模式完成。
该方案是基于4G通信系统的，密钥的推演基于GBA机制，当前5G不支持GBA机制。远端终端设备在与中继终端设备通信时可能会使用用户的永久身份标识(即IMSI)，这可能会造成用户隐私被泄露。
为此，本申请实施例提供了另一种密钥获取方法，一方面，通过使用远端终端设备与3GPP网络之间建立共享的密钥，使得远端终端设备和中继终端设备建立通信的根密钥。另一方面，通过使用远端终端设备的临时标识或匿名标识SUCI来获取根密钥，保证了用户隐私的情况下，使得中继终端设备能够获得用于建立PC5接口安全的根密钥。
本申请实施例中，远端AUSF网元指服务远端终端设备的AUSF网元，远端AUSF网元存储有与远端终端设备共享的密钥。中继AUSF网元指服务中继终端设备的AUSF网元。远端AMF网元指服务远端终端设备的AMF网元，中继AMF网元指服务中继终端设备的AMF网元。远端PCF网元指服务远端终端设备的PCF网元，中继PCF网元指服务中继终端设备的PCF网元。远端NRF网元指服务远端终端设备的NRF网元。远端UDM网元指服务远端终端设备的UDM网元。
本申请实施例中，如无特别说明，根据参数A生成某一标识、某一密钥或某一验证信息，指的是向某种算法(例如密钥推演函数(key derivation function，KDF)输入参数A，计算得到某一标识、某一密钥或某一验证信息。
PKMF网元为新的功能模块，可以独立部署或与其他功能网元合设。PKMF网元用于管理临近业务的安全信息，例如获取远端终端设备与中继终端设备之间的共享的密钥，执行授权检查等功能。
如图5所示，在终端侧该密钥获取方法包括：
S501、远端终端设备向中继终端设备发送远端终端设备的第一标识和中继服务码。
可选的，远端终端设备向中继终端设备发送第一验证信息。
可选的，远端终端设备向中继终端设备发送第二验证信息。
上述信息可以携带在同一消息(例如直接通信请求)或不同消息中，由中继终端设备最终转发给远端AUSF网元、中继AUSF网元或PKMF网元。
下面对涉及的几个信息进行说明：
中继服务码
用于标识一个连接服务，该连接服务为中继提供连接到应用的服务。同一个终端设备可以配置不同的中继服务码，用于接入到不同的应用或业务。
第一标识
第一标识可以为远端终端设备的与中继服务码对应的标识(例如P-KID)(例如格式可以是Username@realm)，或者，第一标识可以为远端终端设备的匿名标识(例如SUCI)，从而在空口传递时不会暴露远端终端设备的永久身份标识(例如SUPI)。第一标识可以与中继服务码一一对应，即针对不同的中继服务码远端终端设备可以使用不同的第一标识进行通信。
由于AUSF网元或PKMF网元可以服务多个终端设备，远端终端设备的第一标识用于AUSF网元或PKMF网元确定对应的远端终端设备，从而确定对应的第一共享密 钥，或者，确定远端终端设备的其他标识(例如SUPI)，第一共享密钥为远端终端设备与远端AUSF网元共享的密钥(或由该密钥生成的其他密钥)。第一共享密钥可以是Kausf，该密钥Kausf由远端终端设备接入网络时与远端AUSF网元事先协商共享。或者，第一共享密钥可以为根据Kausf进一步推演的用于临近业务通信的密钥。
对于第一标识为远端终端设备的与中继服务码对应的标识来说，远端终端设备可以通过以下几种方式获取第一标识：
方式一、远端终端设备可以通过远端AMF网元向远端认证服务功能网元发送至少一个中继服务码；远端AUSF网元生成与中继服务码对应的第一标识，并通过远端AMF网元向远端终端设备发送第一标识；相应地，远端终端设备从远端认证服务功能网元接收与中继服务码对应的第一标识。
方式二、远端终端设备根据第一共享密钥(例如Kausf)、中继服务码生成临时标识，再根据临时标识获取第一标识。
远端终端设备根据第一共享密钥(例如Kausf)、中继服务码生成临时标识的方式包括：
在一种可能的实施方式中，向某种算法(例如密钥推演函数(key derivation function，KDF)输入第一共享密钥(例如Kausf)和中继服务码，计算得到一个临时标识。
可选的，远端终端设备还可以根据第二新鲜性参数、远端终端设备的SUPI中的至少一个，以及，第一共享密钥(例如Kausf)、中继服务码生成临时标识。即计算上述临时标识的输入参数还可以包括第二新鲜性参数或其他参数(例如远端终端设备的SUPI等)。
或者，在另一种可能的实施方式中，远端终端设备根据第一共享密钥生成临近业务根密钥，再根据临近业务根密钥和中继服务码生成临时标识。
例如，远端终端设备首先根据第一共享密钥(例如Kausf)推演一个临近业务根密钥。可选的，生成临近业务根密钥的算法的输入参数可以包含字符串“ProSe”、远端终端设备的SUPI等。然后，远端终端设备使用临近业务根密钥和中继服务码作为KDF的输入生成临时标识。
可选的，远端终端设备还可以根据第二新鲜性参数、远端终端设备的SUPI中的至少一个，以及，临近业务根密钥、中继服务码生成临时标识。即计算上述临时标识的输入参数还可以包括第二新鲜性参数或其他参数(例如远端终端设备的SUPI等)。即远端终端设备根据临时标识获取第一标识的方式包括：
在一种可能的实施方式中，远端终端设备根据上述临时标识、路由指示和远端终端设备的家乡网络标识生成第一标识，第一标识可以包括路由指示和家乡网络标识。例如，可以对临时标识、路由指示和远端终端设备的家乡网络标识进行组合得到字符串作为临时标识，以第一标识的格式为Username@realm为例，第一标识Username@realm中的Username可以包括临时标识和路由指示，realm可以包括远端终端设备的家乡网络标识。
或者，在另一种可能的实施方式中，远端终端设备将上述临时标识作为第一标识。
方式三、远端终端设备根据第二新鲜性参数、路由指示和远端终端设备的家乡网络标识生成第一标识，第一标识可以包括路由指示和家乡网络标识。例如，可以对第 二新鲜性参数、路由指示和远端终端设备的家乡网络标识进行组合得到字符串作为临时标识，以第一标识的格式为Username@realm为例，第一标识Username@realm中的Username可以包括第二新鲜性参数和路由指示，realm可以包括远端终端设备的家乡网络标识。
方式四、远端终端设备根据第一共享密钥(例如Kausf)和中继服务码生成第二共享密钥，第二共享密钥为远端终端设备与PKMF网元共享的密钥Kp；远端终端设备再根据第二共享密钥Kp和第二新鲜性参数生成第一标识。
生成第一标识的过程中，使用中继服务码是为了生成基于中继服务码粒度的密钥，保证不同的中继服务码(业务)对应不同的临时标识，从而防止攻击者在空口根据相同的第一标识关联一个终端设备正在进行的两个不同的业务。
生成第一标识的过程中，使用第二新鲜性参数是为了保证不同的时刻针对同一个中继服务码，当没有发生新的主认证生成新的密钥(例如Kausf)时，网络可以生成不同的临时标识，从而防止攻击者根据空口上的同一个第一标识关联一个终端设备在不同的时刻进行同一个业务。
第二新鲜性参数
第二新鲜性参数可以包括远端终端设备和远端AUSF网元分别本地维护的计数器的值，远端终端设备和远端AUSF网元在本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。此时，远端AUSF网元不必向远端终端设备发送第二新鲜性参数。
或者，远端终端设备可以向远端AUSF网元发送中继服务码；远端AUSF网元针对该中继服务码，根据第二新鲜性参数生成第一标识，并向远端终端设备发送第二新鲜性参数；相应地，远端终端设备从远端AUSF网元接收与中继服务码对应的第二新鲜性参数。第二新鲜性参数可以包括远端AUSF网元生成的随机值或者远端AUSF网元本地维护的计数器的值，具体生成方式不作限定。
第一验证信息
第一验证信息由第一临时密钥，以及，携带第一验证信息的消息(例如直接通信请求)的全部或部分信元生成。第一临时密钥由第一共享密钥(例如Kausf)生成。具体的可以直接根据Kausf推演第一临时密钥，或根据Kausf推演一个中间密钥，基于中间密钥进一步推演第一临时密钥。
可选的，第一临时密钥由中继服务码、第三新鲜性参数、远端终端设备的第二标识(例如SUPI)以及第一标识中的至少一项，以及，第一共享密钥(例如Kausf)计算得到。其中，第三新鲜性参数为远端终端设备生成，例如可以为第三随机数。例如，输入中继服务码、第三新鲜性参数、远端终端设备的第二标识以及远端终端设备的第一标识中的至少一个，以及，第一共享密钥(例如Kausf)，通过某种算法计算得到第一临时密钥Kt。
第一验证信息用于发送给远端AUSF网元，远端AUSF网元接收第一验证信息后，按照与远端终端设备相同的方式生成第三验证信息，远端AUSF网元比较第一验证信息和第三验证信息以对远端终端设备进行验证，验证是否授权远端终端设备通过中继终端设备接入网络获取业务。
第二验证信息
第二验证信息由第一新鲜性参数、中继服务码和第一共享密钥(例如Kausf)生成。例如，远端终端设备根据中继服务码和第一共享密钥(例如Kausf)，生成第二共享密钥Kp，再根据第一新鲜性参数和第二共享密钥Kp，生成第二验证信息。
可选的，远端终端设备根据远端终端设备的第二标识(例如SUPI)、临近业务(ProSe)字符中的至少一个、中继服务码和第一共享密钥(例如Kausf)，生成第二共享密钥Kp。或者，远端终端设备根据第一共享密钥(例如Kausf)和其他参数，生成第二共享密钥Kp，再根据第一新鲜性参数、中继服务码和第二共享密钥Kp，生成第二验证信息。
第二验证信息用于发送给PKMF网元，PKMF网元接收第二验证信息后，按照与远端终端设备相同的方式生成第四验证信息，PKMF网元比较第二验证信息和第四验证信息以对远端终端设备进行验证，验证是否授权远端终端设备通过中继终端设备接入网络获取业务。
S502、远端终端设备根据第一共享密钥(例如Kausf)、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
例如，使用第一共享密钥(例如Kausf)、中继服务码，以及，至少一个第一新鲜性参数，作为密钥推演函数KDF的输入，输出远端终端设备与中继终端设备通信的根密钥。
或者，使用第一共享密钥(例如Kausf)作为KDF的输入，输出一个中间密钥。进一步地，使用该中间密钥、中继服务码，以及，至少一个第一新鲜性参数等作为KDF的输入，输出远端终端设备与中继终端设备通信的根密钥。
远端终端设备也可以根据第一共享密钥(例如Kausf)和中继服务码生成第二共享密钥Kp，再根据第二共享密钥Kp以及至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
远端终端设备还可以根据第一共享密钥(例如Kausf)生成第二共享密钥Kp，再根据中继服务码、第二共享密钥Kp以及至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
第一新鲜性参数
可选的，至少一个第一新鲜性参数可以包括远端AUSF网元或PKMF网元中的一个与终端设备分别本地维护的计数器的值，远端AUSF网元或PKMF网元中的一个与终端设备在本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。可选的，远端AUSF网元或PKMF网元中的一个与终端设备针对每一个中继服务器码分别维护计数器。
可选的，至少一个第一新鲜性参数包括第一随机数，可选的，远端终端设备还可以向中继终端设备发送第一随机数。第一随机数最终发往远端AUSF网元或PKMF网元，相应地，远端AUSF网元或PKMF网元接收第一随机数。
可选的，至少一个第一新鲜性参数包括第二随机数，远端终端设备还可以从中继终端设备接收第二随机数。第二随机数可以来自远端AUSF网元或PKMF网元，即远端AUSF网元或PKMF网元可以发送第二随机数。
本申请实施例提供的密钥获取方法，远端终端设备向中继终端设备发送第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识。远端终端设备根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。其中的第一标识用于远端AUSF网元确定对应的第一共享密钥，或者用于PKMF网元确定对应的第二共享密钥，而第二共享密钥同样是由第一共享密钥和/或中继服务码生成，使得远端终端设备与远端AUSF网元或PKMF网元能够采用相同的方式生成远端终端设备与中继终端设备通信的根密钥，实现了在远端终端设备与中继终端设备之间共享密钥。
如图6所示，在网络侧该密钥获取方法由远端AUSF网元执行的步骤包括：
S601、远端AUSF网元获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码。
可选的，远端AUSF网元接收第一随机数。
可选的，远端AUSF网元还可以接收第一验证信息。关于第一验证信息参照前面描述，在此不再重复。
如前文所述的，第二标识可以为远端终端设备的永久身份标识(例如SUPI)，第一标识可以为远端终端设备的与中继服务码对应的标识(例如P-KID)。
远端AUSF网元可以接收来自远端终端设备的中继服务码，中间通过例如远端AMF网元、中继终端设备、PKMF网元等转发。关于中继服务码见前面描述，在此不再重复。
远端AUSF网元获取远端终端设备的第一标识或第二标识中的一个，包括以下几种方式：
在一种可能的实施方式中，远端AUSF网元接收远端终端设备的第一标识或第二标识中的一个。例如远端AUSF网元可以从PKMF网元接收远端终端设备的第一标识或第二标识中的一个。
在远端AUSF网元接收远端终端设设备的第一标识的情况下，该方法还包括：远端AUSF网元可以采用步骤S501中与远端终端设备相同的方式(例如方式二、方式三)，生成第一标识。
在另一种可能的实施方式中，远端AUSF网元可以采用步骤S501中与远端终端设备相同的方式(例如方式二、方式三)，生成第一标识。
例如，远端AUSF网元可以根据第一共享密钥、中继服务码，生成临时标识；再根据临时标识生成第一标识。具体可以参照前面步骤S501的方式二中远端终端设备如何生成第一标识。
与远端终端设备类似的，远端AUSF网元根据第一共享密钥、中继服务码，生成临时标识，可以包括：远端终端设备根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。具体可以参照前面步骤S501的方式二中远端终端设备如何生成临时标识。
再例如，远端AUSF网元可以根据第二新鲜性参数、路由指示和远端终端设备的家乡网络标识，生成第一标识。具体可以参照前面步骤S501的方式三中远端终端设备如何生成第一标识。关于第二新鲜性参数见前面描述，在此不再重复。
另外，远端AUSF网元可以发送第二新鲜性参数，通过中继终端设备转发至远端终端设备，使远端终端设备接收第二新鲜性参数。
远端AUSF网元在生成第一标识之后，可以向中继终端设备发送与中继服务码对应的第一标识，由中继终端设备转发给远端终端设备，使得远端终端设备获取第一标识，即对应于步骤S501中远端终端设备获取第一标识的方式一。
远端AUSF网元还可以向UDM网元发送第一标识，用于其他网元(例如PKMF网元)从UDM网元获取远端AUSF网元实例标识和/或远端终端设备的SUPI。远端AUSF网元实例标识用于确定服务远端终端设备的远端AUSF网元。
S602、远端AUSF网元获取第一标识或第二标识对应的第一共享密钥。
关于第一共享密钥见前面描述，在此不再重复。
远端AUSF网元可以通过本地查询第一标识或第二标识对应的第一共享密钥。
S603、远端AUSF网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
关于第一新鲜性参数的描述见前面描述，在此不再重复。需要说明的是，此处的第一新鲜性参数可以是远端终端设备和远端AUSF网元各自在本地维护的计数器的值。
远端AUSF网元可以采用与远端终端设备相同的方式来生成根密钥，具体参照步骤S502中的相关描述，在此不再重复。
远端AUSF网元接收到第一验证信息之后，在生成根密钥之前，与远端终端设备类似地，可以根据第一共享密钥生成第一临时密钥；并根据第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元，得到第三验证信息；通过比较第一验证信息和第三验证信息以对远端终端设备进行验证，验证通过即可以生成根密钥。关于远端AUSF网元如何进行验证可以参照前面关于第一验证信息的描述，在此不再重复。
同样地，与远端终端设备类似地，远端AUSF网元可以根据中继服务码、第三新鲜性参数、第二标识以及远端终端设备的第一标识中的至少一项，以及，第一共享密钥，生成第一临时密钥。具体参照远端终端设备的相关描述，在此不再重复。
可选的，远端AUSF网元按照与远端终端设备相同的方式生成第二共享密钥Kp。例如，根据中继服务码和第一共享密钥(例如Kausf)，生成第二共享密钥Kp，并向PKMF网元发送第二共享密钥Kp。具体参照前文远端终端设备生成第二共享密钥Kp的方式。
S604、远端AUSF网元发送根密钥。
远端AUSF网元可以向PKMF网元发送根密钥，通过PKMF网元向中继终端设备发送根密钥。
可选的，远端AUSF网元还可以发送生成根密钥的至少一个第一新鲜性参数。例如，至少一个第一新鲜性参数包括第二随机数，远端AUSF网元可以发送第二随机数，经过中继远端设备转发给远端终端设备。
本申请实施例提供的密钥获取方法，远端AUSF网元获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码；第二标识为远端终端设备的永久身份标识，第一标识为远端终端设备的与中继服务码对应的标识；远端AUSF网元获取第一标识或第二标识对应的第一共享密钥；第一共享密钥为远端终端设备与远端AUSF网 元共享的密钥；远端AUSF网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥；远端AUSF发送根密钥。其中的第一标识用于远端AUSF网元确定对应的第一共享密钥，使得远端终端设备和远端AUSF网元能够采用相同的方式生成远端终端设备与中继终端设备通信的根密钥，实现了在远端终端设备与中继终端设备之间共享密钥。
如图7所示，在网络侧该密钥获取方法由PKMF网元执行的步骤包括：
S701、PKMF网元接收远端终端设备的第一标识和中继服务码。
可选的，PKMF网元接收第一随机数。
可选的，PKMF网元接收第二验证信息。关于第二验证信息见前面描述，在此不再重复。
第一标识可以为远端终端设备的与中继服务码对应的标识(例如P-KID)，或者，第一标识可以为远端终端设备的匿名标识(例如SUCI)。
在一种可能的实施方式中，PKMF网元可以通过中继终端设备从远端终端设备接收第一标识和中继服务码。
S702、PKMF网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥。
在一种可能的实施方式中，PKMF网元向UDM网元发送第一标识；相应地从UDM网元接收远端AUSF的标识信息(例如远端AUSF网元实例标识)；PKMF网元根据标识信息，向对应的远端AUSF网元发送第一标识；相应地，从远端AUSF网元接收根密钥。
在另一种可能的实施方式中，PKMF网元向UDM网元发送第一标识；相应地，从UDM网元接收远端AUSF网元的标识信息以及远端终端设备的永久身份标识(例如SUPI)；PKMF网元根据标识信息，向对应的远端AUSF网元发送远端终端设备的永久身份标识；相应地，从远端AUSF网元接收根密钥。
上述两种实施方式对应于步骤S601中远端AUSF网元获取远端终端设备的第一标识或第二标识中的一个。
在又一种可能的实施方式中，PKMF网元从远端AUSF网元接收至少一个第二共享密钥；PKMF网元根据第一标识对应的第二共享密钥，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。可选的，PKMF网元根据中继服务码、第一标识对应的第二共享密钥，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
PKMF网元接收到第二验证信息之后，在生成根密钥之前，与远端终端设备类似地，可以根据第一新鲜性参数和第二共享密钥，生成第四验证信息；通过比较第一验证信息和第三验证信息以对远端终端设备进行验证，验证通过即可以生成根密钥。PKMF网元如何进行验证可以参照前面关于第二验证信息的描述，在此不再重复。
关于第一新鲜性参数的描述见前面描述，在此不再重复。需要说明的是，此处的第一新鲜性参数可以是远端终端设备和PKMF网元各自在本地维护的计数器的值。
S703、PKMF网元发送根密钥。
可选的，PKMF网元还可以发送生成根密钥的至少一个第一新鲜性参数。例如，至少一个第一新鲜性参数包括第二随机数，PKMF网元可以发送第二随机数，经过中 继远端设备转发给远端终端设备。
本申请实施例提供的密钥获取方法，PKMF网元接收远端终端设备的第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；PKMF网元根据第一标识获取远端终端设备与中继终端设备通信的根密钥，根密钥由第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数生成，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；PKMF网元发送根密钥。其中的第一标识用于PKMF网元确定对应的第二共享密钥，使得远端终端设备和PKMF网元能够采用相同的方式生成远端终端设备与中继终端设备通信的根密钥，实现了在远端终端设备与中继终端设备之间共享密钥。
本申请实施例提供另一种密钥获取方法，远端终端设备主动向远端AUSF网元请求中继服务码对应的第一标识，使得远端AUSF网元能够根据中继服务码生成对应的第一标识，该第一标识用于发现远端UDM网元，并将生成的第一标识存储在远端UDM网元中。在非直接通信过程中，远端终端设备向中继终端设备发起直接通信请求，直接通信请求中包括第一标识。中继终端设备通过信令面向网络侧发起包含第一标识的密钥请求，PKMF网元通过远端UDM网元确定第一标识对应的远端AUSF网元，从远端AUSF网元获取远端终端设备与中继终端设备通信的根密钥。
如图8所示，该密钥获取方法包括：
S801、远端终端设备接入网络，从远端PCF网元或其他相关网元获取用于通过中继终端设备通信的信息。
上述信息包括：用于指示是否授权该终端设备通过中继接入5GC(即该终端设备作为远端终端设备)的指示信息；中继服务码等。
S802、中继终端设备接入网络，从中继PCF网元或其他相关网元获取作为中继终端设备提供通信的信息。
上述信息包括：用于指示是否授权该终端设备作为中继的指示信息；中继服务码等。
需要说明的是，步骤S801和S802的执行顺序不限。
S803、远端终端设备通过远端AMF网元向远端AUSF网元发送密钥请求。
该密钥请求中包括至少一个中继服务码。
可选的，远端AMF网元执行授权检查，检查是否授权远端终端设备作为中继终端设备的远端终端设备或者检查是否授权远端终端设备通过中继终端设备获取中继服务码对应的服务。
S804、远端AUSF网元生成远端终端设备的与各个中继服务码对应的第一标识(例如P-KID)。
生成第一标识的过程参照步骤S601。
S805、远端AUSF网元向远端UDM网元发送远端终端设备的第一标识。
远端UDM网元将远端终端设备的第一标识作为远端终端设备的上下文存储在本地，可选的，如果远端UDM网元将远端终端设备的上下文存储在统一数据存储库(unified data repository，UDR)网元中，则远端终端设备的第一标识也被存储在UDR网元的终端设备上下文中。
S806、远端AUSF网元通过远端AMF网元向远端终端设备发送密钥请求响应。
该密钥请求响应中包括：与中继服务码对应的第一标识，或者，用于生成第一标识的第二新鲜性参数。
相应地，远端终端设备通过远端AMF网元从远端AUSF网元接收与中继服务码对应的第一标识，或者，用于生成第一标识的第二新鲜性参数。
如果在生成第一标识的过程中使用了第二新鲜性参数，则密钥请求响应中可以包括与中继服务码对应的第一标识，或者，用于生成第一标识的第二新鲜性参数。如果在生成第一标识的过程中未使用第二新鲜性参数，则密钥请求响应中包括与中继服务码对应的第一标识。
可选的，如果在接收的密钥请求中包括多个中继服务码，即请求的第一标识也有多个，则密钥请求响应中还可以包括与多个第一标识(或第二新鲜性参数)分别对应的多个中继服务码，即密钥请求响应中第一标识(或第二新鲜性参数)和中继服务码一一对应；或者，密钥请求响应中包括多个第一标识(或第二新鲜性参数)，而不与中继服务码相对应，由远端终端设备从中自由选择并进行对应。
S807、远端终端设备获取第一标识。
如果在步骤S806中接收到第一标识，则远端终端设备直接进行存储。
如果在步骤S806中接收到第二新鲜性参数，则远端终端设备采用与远端AUSF网元相同的方式生成第一标识，例如按照步骤S501中方式二或方式三的方式生成第一标识。需要说明的是，远端终端设备生成第一标识的过程在步骤S809之前执行即可。
S808、远端终端设备执行发现流程以发现中继终端设备。
S809、远端终端设备向中继终端设备发送直接通信请求。
该直接通信请求中包括远端终端设备的第一标识(例如P-KID)、中继服务码。如果有多个中继服务码，则远端终端设备可以通过中继服务码确定对应的第一标识。
可选的，该直接通信请求中还可以包括第一随机数(Nonce 1)。
可选的，该直接通信请求中还可以包括第一验证信息。
关于如何生成第一验证信息参照步骤S501。
S810、中继终端设备向中继AMF网元发送密钥请求。
该密钥请求中包括第一标识(例如P-KID)、中继服务码。
可选的，该密钥请求中还可以包括第一随机数。
可选的，该密钥请求中还可以包括第一验证信息(例如MAC-I)。
S811、中继AMF网元选择中继AUSF网元，并向中继AUSF网元发送临近业务密钥请求。
该临近业务密钥请求中包括第一标识(例如P-KID)、中继服务码、中继终端设备的标识(relay UE ID)(例如SUPI)。
可选的，该临近业务密钥请求中还可以包括第一随机数。
可选的，该临近业务密钥请求中还可以包括第一验证信息(例如MAC-I)。
可选的，中继AMF网元执行授权检查，即检查是否授权中继终端设备作为中继终端设备或者检查是否授权中继终端设备向远端终端设备提供中继服务码对应的连接服务。
S812、中继AUSF网元选择PKMF网元，并向PKMF网元发送临近业务密钥请求。
临近业务密钥请求中携带的信息与步骤S811的临近业务密钥请求中携带的信息相同。
S813、PKMF网元根据临近业务密钥请求中的第一标识(例如P-KID)选择远端UDM网元，并向远端UDM网元发送网元发现请求。
该网元发现请求中包括第一标识(例如P-KID)。
远端UDM网元根据第一标识(例如P-KID)获取远端AUSF网元实例标识，并发送给PKMF网元。AUSF网络实例标识可以为全量域名(fully qualified domain name，FQDN)或AUSF的地址等能唯一识别远端AUSF的标识，这里不做限制。
可选的，PKMF网元还可以获取远端终端设备的第二标识(例如SUPI)。
S814、PKMF网元对远端终端设备和中继终端设备进行授权。
若步骤S813中PKMF网元获取了远端终端设备的第二标识，PKMF网元根据远端终端设备的第二标识(例如SUPI)和中继服务码判断是否授权远端终端设备通过中继终端设备获取中继服务码对应的服务。
PKMF网元根据中继终端设备的标识(relay UE ID，例如SUPI)和中继服务码判断是否授权中继终端设备作为中继提供中继服务码对应的服务。授权通过则继续执行后续流程，否则发起拒绝流程。
需要说明的是，上述PKMF的授权过程是可选的，并且可以发生在步骤S815之后。
S815、PKMF网元向远端AUSF网元发送临近业务密钥请求。
该临近业务密钥请求中包括远端终端设备的第二标识(例如SUPI)或第一标识、中继服务码。
可选的，该临近业务密钥请求中还可以包括第一随机数。
可选的，该临近业务密钥请求中还可以包括第一验证信息(例如MAC-I)。
S816、远端AUSF网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
此处的至少一个第一新鲜性参数可以包括第一随机数(Nonce 1)，或者，可以包括远端AUSF网元生成的第二随机数(Nonce 2)，或者，包括第一随机数和第二随机数，或者，可以包括远端AUSF网元本地维护的计数器的值，远端AUSF网元本地维护的计数器与远端终端设备本地维护的计数器采用相同的初始值和计数规则，以使这两个计数器的值保持一致。具体的第一新鲜性参数的实现方式不限制。
生成根密钥的过程参照步骤S603。
需要说明的是，如果临近业务密钥请求中包括第一验证信息，远端AUSF网元按照与终端设备相同的方式生成第三验证信息，通过对比第一验证信息和第三验证信息来进行验证。验证通过后再生成根密钥。
S817、远端AUSF网元向PKMF网元发送临近业务密钥响应。
该临近业务密钥响应中可以包括根密钥，可选的，还可以包括第二随机数。
S818、PKMF网元向中继AUSF网元发送临近业务密钥响应。
该临近业务密钥响应中可以包括根密钥，可选的，还可以包括第二随机数。
S819、中继AUSF网元通过中继AMF网元向中继终端设备发送临近业务密钥响应。
该临近业务密钥响应中可以包括根密钥，可选的，还可以包括第二随机数。
S820、中继终端设备向远端终端设备发送安全模式命令。
可选的，该安全模式命令中包括第二随机数。
可选的，中继终端设备产生第四随机数，并在安全模式命令消息中包括该第四随机数。
远端终端设备采用与远端AUSF网元相同的方法生成根密钥。
可选的，中继终端设备可以根据接收到的根密钥生成中继终端设备与远端终端设备之间的会话密钥。进一步可选的，中继终端设备可以根据该会话密钥生成信令面和/或用户面的加密密钥和/或完整性保护密钥。
或者，可选的，中继终端设备可以根据接收到的根密钥生成信令面和/或用户面的加密密钥和/或完整性保护密钥。
可选的，安全模式命令消息中包括消息验证码，消息验证码为根据信令面的完整性保护密钥生成。
S821、远端终端设备向中继终端设备发送安全模式命令完整消息。
上述密钥获取方法中，远端终端设备获取与中继服务码对应的第一标识，通过该第一标识，使得中继终端设备能够通过信令面从网络侧获取远端终端设备与中继终端设备通信的根密钥。可选的，PKMF网元在获取根密钥之前先对远端终端设备和中继终端设备执行授权检查，保证只有授权的终端设备获取根密钥。其中，根密钥是根据第一共享密钥Kausf和中继服务码等参数生成。
本申请实施例提供另一种密钥获取方法，远端终端设备主动向远端AUSF网元请求中继服务码对应的第一标识，使得远端AUSF网元能够根据中继服务码生成对应的第一标识以及第二共享密钥，并发送给PKMF网元。在非直接通信过程中，远端终端设备向中继终端设备发起直接通信请求，直接通信请求中包括第一标识。中继终端设备通过信令面向网络侧发起包含第一标识的密钥请求，PKMF网元根据第一标识获取对应的第二共享密钥Kp，并生成远端终端设备与中继终端设备通信的根密钥。与图8的区别在于，远端AUSF网元将远端终端设备的第一标识和第二共享密钥Kp提前推送给PKMF网元。或者远端AUSF网元将第二共享密钥Kp提前推送给PKMF网元，由PKMF生成远端终端设备的第一标识。
如图9所示，该密钥获取方法包括：
S901、远端终端设备接入网络，从远端PCF网元或其他相关网元获取用于通过中继终端设备通信的信息。
该步骤与步骤S801相同，在此不再重复。
S902、中继终端设备接入网络，从中继PCF网元或其他相关网元获取作为中继终端设备提供通信的信息。
该步骤与步骤S802相同，在此不再重复。
S903、远端终端设备通过远端AMF网元向远端AUSF网元发送密钥请求。
该步骤与步骤S803相同，在此不再重复。
S904、远端AUSF网元生成第二共享密钥Kp。
生成第二共享密钥Kp的过程参照步骤S603。
可选的，远端AUSF网元生成终端设备的与各个中继服务码对应的第一标识(例如P-KID)。生成第一标识的过程参照步骤S601。
S905、远端AUSF网元选择PKMF网元，并向PKMF网元发送临近业务信息提供消息。
远端AUSF网元选择PKMF网元的方式包括但不限于以下几种可能的方式：
方式一、远端AUSF网元根据中继服务码确定PKMF网元，例如远端AUSF网元向远端NRF网元或远端PCF网元发送中继服务码，以获取该中继服务码对应的PKMF网元。或者中继服务码中包括路由信息，远端AUSF网元根据路由信息选择PKMF网元。
方式二、远端终端设备在密钥请求中包括PKMF网元的发现信息(在步骤S901中从远端PCF网元或其他相关网元得到该信息)，并由远端AMF网元转发给远端AUSF网元。
方式三、远端AMF网元在密钥请求中包括PKMF网元的发现信息(在步骤S901中从远端PCF网元或其他相关网元得到该信息)。
上述PKMF网元的发现信息用于AUSF网元确定PKMF网元，PKMF网元的发现信息可以为路由信息或PKMF网元的地址信息或PKMF网元的标识等。
临近业务信息提供消息中包括远端终端设备的第二标识(例如SUPI)、第二共享密钥Kp，可选的，还可以包括中继服务码、远端终端设备的第一标识。
PKMF网元存储接收到的远端终端设备的第二标识(例如SUPI)、远端终端设备的第一标识(若接收到)、第二共享密钥Kp，可选的，还可以存储中继服务码。
可选的，PKMF网元可以在判断授权远端终端设备获取中继服务码之后才存储上述信息。
可选的，若临近业务信息提供消息中不包含第一标识，则由PKMF网元生成第一标识。这种情况下，可选的，PKMF网元向远端AUSF网元发送生成的第一标识或第二新鲜性参数。
S906、远端AUSF网元通过远端AMF网元向远端终端设备发送密钥请求响应。
该步骤与步骤S806相同。
S907、远端终端设备获取第一标识。
该步骤与步骤S807相同。需要说明的是，远端终端设备生成第一标识的过程在步骤S909之前执行即可。
S908、远端终端设备执行发现流程以发现中继终端设备。
该步骤与步骤S808相同。
S909、远端终端设备向中继终端设备发送直接通信请求。
该步骤与步骤S809的区别在于远端终端设备可以生成第二验证信息而不是第一验证信息，生成第二验证信息的过程参照步骤S501。并且直接通信请求中可选的包括第二验证信息，而不是包括第一验证信息。其他内容相同。
S910、中继终端设备向中继AMF网元发送密钥请求。
该步骤与步骤S810的区别在于密钥请求中可选的包括第二验证信息，而不是包括第一验证信息。其他内容相同。
S911、中继AMF网元选择中继AUSF网元，并向中继AUSF网元发送临近业务密钥请求。
该步骤与步骤S811的区别在于临近业务密钥请求中可选的包括第二验证信息，而不是包括第一验证信息。其他内容相同。
S912、中继AUSF网元选择PKMF网元，并向PKMF网元发送临近业务密钥请求。
该步骤与步骤S812的区别在于中继AUSF网元选择PKMF网元的方式与步骤S905中远端AUSF网元选择PKMF网元的方式相同；另外，临近业务密钥请求中可选的包括第二验证信息，而不是包括第一验证信息。其他内容相同。
S913、PKMF网元对远端终端设备和中继终端设备进行授权。
该步骤与步骤S814相同。该步骤是可选的。
S914、PKMF网元根据第二共享密钥Kp，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
此处的第一新鲜性参数可以包括第一随机数(Nonce 1)，或者，可以包括PKMF生成的第二随机数(Nonce 2)，或者，包括第一随机数和第二随机数，或者，可以包括远端终端设备和PKMF网元分别本地维护的计数器的值，远端终端设备和PKMF网元在本地维护各自的计数器时，采用相同的初始值和计数规则，以使这两个计数器的值保持一致。
生成根密钥的过程参照步骤S702。
需要说明的是，如果该临近业务密钥请求中包括第二验证信息，PKMF网元按照与终端设备相同的方式生成第四验证信息，通过对比第二验证信息和第四验证信息来进行验证。验证通过后再生成根密钥。
需要说明的是，上述验证过程与步骤S913的执行顺序不限。
S915、PKMF网元向中继AUSF网元发送临近业务密钥响应。
该步骤与步骤S818相同。
S916、中继AUSF网元通过中继AMF网元向中继终端设备发送临近业务密钥响应。
该步骤与步骤S819相同。
S917、中继终端设备向远端终端设备发送安全模式命令。
该步骤与步骤S820相同。
S918、远端终端设备向中继终端设备发送安全模式命令完整消息。
该步骤与步骤S821相同。
上述密钥获取方法中，远端终端设备获取与中继服务码对应的第一标识，通过该第一标识，使得中继终端设备能够通过信令面从网络侧获取远端终端设备与中继终端设备通信的根密钥。进一步的，PKMF网元在获取根密钥之前先对远端终端设备和中继终端设备执行授权检查，保证只有授权的终端设备获取根密钥。其中，根密钥是根据第一共享密钥Kausf和中继服务码等参数生成。
本申请实施例提供另一种密钥获取方法，远端终端设备通过远端AMF网元主动 向PKMF网元请求中继服务码对应的第一标识，再由PKMF网元向远端AUSF网元请求第一标识，使得远端AUSF网元能够根据中继服务码生成对应的第一标识以及第二共享密钥，并发送给PKMF网元。在非直接通信过程中，远端终端设备向中继终端设备发起直接通信请求，直接通信请求中包括第一标识。中继终端设备通过信令面向网络侧发起包含第一标识的密钥请求，PKMF网元根据第一标识获取对应的第二共享密钥，并生成远端终端设备与中继终端设备通信的根密钥。与图9的区别在于，远端AMF网元直接与PKMF网元通信。
如图10所示，该密钥获取方法包括：
S1001、远端终端设备接入网络，从远端PCF网元或其他相关网元获取用于通过中继终端设备通信的信息。
该步骤与步骤S801相同，在此不再重复。
S1002、中继终端设备接入网络，从中继PCF网元或其他相关网元获取作为中继终端设备提供通信的信息。
该步骤与步骤S802相同，在此不再重复。
S1003、远端终端设备向远端AMF网元发送密钥请求。
该密钥请求中包括至少一个中继服务码。
可选的，远端AMF网元执行授权检查，即检查是否授权远端终端设备作为中继终端设备的远端终端设备或者检查是否授权远端终端设备通过中继终端设备获取中继服务码对应的服务。
S1004、远端AMF网元选择PKMF网元，并向PKMF网元发送密钥请求。
远端AMF网元选择PKMF网元的方式与步骤S905中远端AUSF网元选择PKMF网元的方式相同。
该密钥请求中包括中继服务码、远端AUSF网元实例标识、远端终端设备的第二标识(例如SUPI)。
若步骤S1003的密钥请求中包括多个中继服务码，且对应不同的PKMF网元，则远端AMF网元分别向每个PKMF网元发送密钥请求。
S1005、PKMF网元向远端AUSF网元发送临近业务安全信息请求。
该请求中包括远端终端设备的第二标识(例如SUPI)、中继服务码。
可选的，在发送消息前，PKMF网元根据远端终端设备的第二标识(例如SUPI)和中继服务码判断是否授权远端终端设备通过中继终端设备获取中继服务码对应的服务。
S1006、远端AUSF网元生成终端设备的与各个中继服务码对应的第一标识(例如P-KID)，以及，生成第二共享密钥Kp。
该步骤与步骤S904相同。
S1007、远端AUSF网元向PKMF网元发送临近业务安全信息响应。
临近业务安全信息响应中包括第二共享密钥Kp，可选的，还可以包括中继服务码、远端终端设备的第二标识(例如SUPI)和远端终端设备的第一标识。
S1008、PKMF网元通过远端AMF网元向远端终端设备发送密钥请求响应。
关于密钥请求响应包括的信息可以参照步骤S806，在此不再重复。
S1009、远端终端设备获取第一标识。
该步骤与步骤S807相同。需要说明的是，远端终端设备生成第一标识的过程在步骤S1011之前执行即可。
S1010、远端终端设备执行发现流程以发现中继终端设备。
该步骤与步骤S808相同。
S1011、远端终端设备向中继终端设备发送直接通信请求。
该步骤与步骤S909相同。
S1012、中继终端设备向中继AMF网元发送密钥请求。
该步骤与步骤S910相同。
S1013、中继AMF网元选择PKMF网元，并向PKMF网元发送临近业务密钥请求。
中继AMF网元选择PKMF网元的方式与步骤S1004中远端AMF网元选择PKMF网元的方式相同。
临近业务密钥请求中携带的信息与步骤S912的临近业务密钥请求中携带的信息相同。
可选的，中继AMF网元执行授权检查，即检查是否授权中继终端设备作为远端中继设备的中继终端设备或者检查是否授权中继终端设备向远端终端设备提供中继服务码对应的连接服务。
S1014、可选的，PKMF网元对远端终端设备和中继终端设备进行授权。
该步骤与步骤S814相同。
S1015、PKMF网元根据第二共享密钥Kp，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
该步骤与步骤S914相同。
S1016、PKMF网元通过中继AMF网元向中继终端设备发送临近业务密钥响应。
临近业务密钥响应携带的信息与步骤S818中临近业务密钥响应携带信息相同。
S1017、中继终端设备向远端终端设备发送安全模式命令。
该步骤与步骤S820相同。
S1018、远端终端设备向中继终端设备发送安全模式命令完整消息。
该步骤与步骤S821相同。
上述密钥获取方法中，远端终端设备获取与中继服务码对应的第一标识，通过该第一标识，使得中继终端设备能够通过信令面从网络侧获取远端终端设备与中继终端设备通信的根密钥。进一步的，PKMF网元在获取根密钥之前先对远端终端设备和中继终端设备执行授权检查，保证只有授权的终端设备获取根密钥。其中，根密钥是根据第一共享密钥Kausf和中继服务码等参数生成。
本申请实施例提供另一种密钥获取方法，在非直接通信过程中，远端终端设备向中继终端设备发起直接通信请求，直接通信请求中包括远端终端设备的SUCI。中继终端设备通过信令面向网络侧发起包含SUCI的密钥请求，PKMF网元通过远端UDM网元确定SUCI对应的远端AUSF网元，从远端AUSF网元获取远端终端设备与中继终端设备通信的根密钥。与图8的区别在于，PKMF网元通过远端终端设备的SUCI确定远端AUSF网元。
如图11所示，该密钥获取方法包括：
S1101、远端终端设备接入网络，从远端PCF网元或其他相关网元获取用于通过中继终端设备通信的信息。
该步骤与步骤S801相同，在此不再重复。
S1102、中继终端设备接入网络，从中继PCF网元或其他相关网元获取作为中继终端设备提供通信的信息。
该步骤与步骤S802相同，在此不再重复。
S1103、远端终端设备执行发现流程以发现中继终端设备。
该步骤与步骤S808相同。
S1104、远端终端设备向中继终端设备发送直接通信请求。
该步骤与步骤S809的区别在于，直接通信请求中的第一标识可以为远端终端设备的SUCI。
S1105、中继终端设备向中继AMF网元发送密钥请求。
该步骤与步骤S810的区别在于，密钥请求中的第一标识可以为远端终端设备的SUCI。
S1106、中继AMF网元选择中继AUSF网元，并向中继AUSF网元发送临近业务密钥请求。
该步骤与步骤S811的区别在于，临近业务密钥请求中的第一标识可以为远端终端设备的SUCI。
S1107、中继AUSF网元选择PKMF网元，并向PKMF网元发送临近业务密钥请求。
该步骤与步骤S812的区别在于，临近业务密钥请求中的第一标识可以为远端终端设备的SUCI。
S1108、PKMF网元根据临近业务密钥请求中的第一标识(例如SUCI)选择远端UDM网元，并向远端UDM网元发送终端设备标识(UE ID)请求。
该终端设备标识请求中包括第一标识(例如SUCI)。
远端UDM网元根据第一标识(例如SUCI)获取远端终端设备的第二标识(例如SUPI)，以及服务远端终端设备的远端AUSF网元实例标识，并发送给PKMF网元。
S1109、PKMF网元对远端终端设备和中继终端设备进行授权。
该步骤与步骤S814相同。
S1110、PKMF网元向远端AUSF网元发送临近业务密钥请求。
该步骤与步骤S815相同。
S1111、远端AUSF网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
该步骤与步骤S816相同。
S1112、远端AUSF网元向PKMF网元发送临近业务密钥响应。
该步骤与步骤S817相同。
S1113、PKMF网元向中继AUSF网元发送临近业务密钥响应。
该步骤与步骤S818相同。
S1114、中继AUSF网元通过中继AMF网元向中继终端设备发送临近业务密钥响应。
该步骤与步骤S819相同。
S1115、中继终端设备向远端终端设备发送安全模式命令。
该步骤与步骤S820相同。
S1116、远端终端设备向中继终端设备发送安全模式命令完整消息。
该步骤与步骤S821相同。
需要说明的是，步骤S811和S812是可选的，远端AMF网元可以直接选择PKMF网元并向PKMF网元发送临近业务密钥请求，临近业务密钥请求中携带的内容与步骤S811的临近业务密钥请求中携带的信息相同。
上述密钥获取方法，远端终端设备生成SUCI，使得中继终端设备能够使用SUCI从PKMF网元获取远端终端设备与中继终端设备通信的根密钥。具体的，PKMF网元根据SUCI能够确定远端AUSF网元，从远端AUSF网元获取远端终端设备与中继终端设备通信的根密钥。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置用于实现上述各种方法。该通信装置可以为上述方法实施例中的远端终端设备，或者包含上述远端终端设备的装置，或者为远端终端设备内的芯片或功能模块。或者，该通信装置可以为上述方法实施例中的远端AUSF网元，或者包含上述远端AUSF网元的装置，或者为远端AUSF网元内的芯片或功能模块。或者，该通信装置可以为上述方法实施例中的PKMF网元，或者包含上述PKMF网元的装置，或者为PKMF网元内的芯片或功能模块。
可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以通信装置为上述方法实施例中的远端终端设备为例。图12示出了一种通信装置120的结构示意图。该通信装置120可以为图1中的远端终端设备。该通信装置120包括处理模块1201和收发模块1202。处理模块1201也可以称为处理单元，用以实现上述方法实施例中远端终端设备的处理功能。例如执行图5中的步骤S502，图8-图11中远端终端设备的处理功能。收发模块1202，也可以称为收发单元，用以实现上述方法实施例中远端终端设备的收发功能。例如执行图5中的步骤S501，图8-图11中远端终端设备的收发功能。收发模块1202可以称为收发电路、收发机、收发器 或者通信接口。
示例性的，收发模块1202，用于向中继终端设备发送第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；处理模块1201，用于根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥，远端认证服务功能网元为服务远端终端设备的认证服务功能网元，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥。
在一种可能的实施方式中，第一标识为远端终端设备的SUCI。
在一种可能的实施方式中，处理模块1201和收发模块1202还用于获取第一标识。
在一种可能的实施方式中，收发模块1202还用于发送中继服务码；接收与中继服务码对应的第一标识。
在一种可能的实施方式中，处理模块1201还用于根据第一共享密钥、中继服务码，生成临时标识；根据临时标识获取第一标识。
在一种可能的实施方式中，处理模块1201还用于根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。
在一种可能的实施方式中，处理模块1201还用于根据第二新鲜性参数、路由指示和家乡网络标识，生成第一标识。
在一种可能的实施方式中，收发模块1202还用于发送中继服务码；接收中继服务码对应的第二新鲜性参数。
在一种可能的实施方式中，第二新鲜性参数为远端终端设备本地维护的计数器的值。
在一种可能的实施方式中，第一标识包括路由指示和家乡网络标识。
在一种可能的实施方式中，收发模块1202还用于向中继终端设备发送第一验证信息，第一验证信息由第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元生成，第一临时密钥由第一共享密钥生成。
在一种可能的实施方式中，第一临时密钥由中继服务码、第三新鲜性参数、远端终端设备的第二标识以及第一标识中的至少一项，以及，第一共享密钥生成，其中，第三新鲜性参数为远端终端设备生成。该实施方式公开了生成第一临时密钥的一种方式。
在一种可能的实施方式中，收发模块1202还用于向中继终端设备发送第二验证信息，第二验证信息由第一新鲜性参数、中继服务码和第一共享密钥生成。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，收发模块1202还用于向中继终端设备发送第一随机数。第一随机数发送给远端AUSF网元或PKMF网元。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，收发模块1202还用于从中继终端设备接收第二随机数。第二随机数可以来自远端AUSF网元或PKMF网元。
在一种可能的实施方式中，至少一个第一新鲜性参数为远端终端设备本地维护的计数器的值。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf。
在一种可能的实施方式中，处理模块1201还用于根据第一共享密钥和中继服务码生成第二共享密钥，根据第二共享密钥以及至少一个第一新鲜性参数，生成根密钥，第二共享密钥为远端终端设备与临近业务密钥管理功能网元共享的密钥。
比如，以通信装置为上述方法实施例中的远端AUSF网元为例。图13示出了一种通信装置130的结构示意图。该通信装置130可以为图1中的AUSF网元。该通信装置130包括处理模块1301和收发模块1302。处理模块1301也可以称为处理单元，用以实现上述方法实施例中远端AUSF网元的处理功能，图8-图11中远端AUSF网元的处理功能。例如执行图6中的步骤S601-S603。收发模块1302，也可以称为收发单元，用以实现上述方法实施例中远端AUSF网元的收发功能。例如执行图6中的步骤S601、S604，图8-图11中远端AUSF网元的收发功能。收发模块1302可以称为收发电路、收发机、收发器或者通信接口。
示例性的，处理模块1301用于获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码；第二标识为远端终端设备的永久身份标识，第一标识为远端终端设备的与中继服务码对应的标识；处理模块1301还用于获取第一标识或第二标识对应的第一共享密钥；第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；远端认证服务功能网元根据第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥；收发模块1302用于发送根密钥。
在一种可能的实施方式中，收发模块1302还用于接收远端终端设备的第一标识或第二标识中的一个。
在一种可能的实施方式中，处理模块1301还用于根据第一共享密钥、中继服务码，生成临时标识；远端认证服务功能网元根据临时标识生成第一标识。
在一种可能的实施方式中，处理模块1301还用于根据第一共享密钥、中继服务码和第二新鲜性参数，生成临时标识。
在一种可能的实施方式中，处理模块1301还用于根据第二新鲜性参数、路由指示和远端终端设备的家乡网络标识，生成第一标识。
在一种可能的实施方式中，第二新鲜性参数为远端认证服务功能网元本地维护的计数器的值。
在一种可能的实施方式中，收发模块1302还用于接收中继服务码；发送第二新鲜性参数。
在一种可能的实施方式中，收发模块1302还用于接收中继服务码；发送第一标识。
在一种可能的实施方式中，第一标识包括路由指示和家乡网络标识。
在一种可能的实施方式中，收发模块1302还用于接收第一验证信息；处理模块1301还用于根据第一共享密钥，生成第一临时密钥；并根据第一临时密钥，以及，携带第一验证信息的消息的全部或部分信元，得到第三验证信息；比较第一验证信息和第三验证信息以对远端终端设备进行验证。
在一种可能的实施方式中，处理模块1301还用于根据中继服务码、第三新鲜性参 数、第二标识以及远端终端设备的第一标识中的至少一项，以及，第一共享密钥，生成第一临时密钥，第三新鲜性参数为远端终端设备生成。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，收发模块1302还用于接收第一随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，收发模块1302还用于发送第二随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数为远端认证服务功能网元本地维护的计数器的值。
在一种可能的实施方式中，收发模块1302还用于向统一数据管理网元发送第一标识。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf。
比如，以通信装置为上述方法实施例中的PKMF网元为例。图14示出了一种通信装置140的结构示意图。该通信装置140包括处理模块1401和收发模块1402。处理模块1401也可以称为处理单元，用以实现上述方法实施例中PKMF网元的处理功能。例如执行图7中的步骤S702，图8-图11中PKMF网元的处理功能。收发模块1402，也可以称为收发单元，用以实现上述方法实施例中PKMF网元的收发功能。例如执行图7中的步骤S701-S703，图8-图11中PKMF网元的收发功能。收发模块1402可以称为收发电路、收发机、收发器或者通信接口。
示例性的，收发模块1402用于接收远端终端设备的第一标识和中继服务码，第一标识为远端终端设备的与中继服务码对应的标识或者第一标识为远端终端设备的匿名标识；处理模块1401用于根据第一标识获取远端终端设备与中继终端设备通信的根密钥，根密钥由第一共享密钥、中继服务码，以及，至少一个第一新鲜性参数生成，第一共享密钥为远端终端设备与远端认证服务功能网元共享的密钥；收发模块1402还用于发送根密钥。
在一种可能的实施方式中，收发模块1402还用于向统一数据管理功能网元发送第一标识；从统一数据管理功能网元接收远端认证服务功能网元的标识信息；根据标识信息，向对应的远端认证服务功能网元发送第一标识；从远端认证服务功能网元接收根密钥。
在一种可能的实施方式中，收发模块1402还用于向统一数据管理功能网元发送第一标识；从统一数据管理功能网元接收远端认证服务功能网元的标识信息以及远端终端设备的永久身份标识；根据标识信息，向对应的远端认证服务功能网元发送远端终端设备的永久身份标识；从远端认证服务功能网元接收根密钥。
在一种可能的实施方式中，收发模块1402还用于从远端认证服务功能网元接收至少一个第二共享密钥，第二共享密钥为远端终端设备与临近业务密钥管理功能网元共享的密钥，第二共享密钥由第一共享密钥和中继服务码生成；处理模块1401还用于根据第一标识对应的第二共享密钥，以及，至少一个第一新鲜性参数，生成远端终端设备与中继终端设备通信的根密钥。
在一种可能的实施方式中，还包括：收发模块1402还用于接收第二验证信息；处 理模块1401还用于根据第一新鲜性参数和第二共享密钥，生成第四验证信息；比较第二验证信息和第四验证密信息以对远端终端设备进行验证。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第一随机数，收发模块1402还用于接收第一随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数包括第二随机数，收发模块1402还用于发送第二随机数。
在一种可能的实施方式中，至少一个第一新鲜性参数为临近业务密钥管理功能网元本地维护的计数器的值。
在一种可能的实施方式中，第一共享密钥为远端终端设备接入网络时与远端认证服务功能网元协商的密钥Kausf。
在本实施例中，上述通信装置以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
具体的，处理模块的功能/实现过程可以通过通信装置中的处理器调用存储器中存储的计算机执行指令来实现。收发模块的功能/实现过程可以通过通信设备中的收发器或通信接口来实现。
由于本实施例提供的通信装置可执行上述方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
如图15所示，本申请实施例还提供了一种通信装置，该通信装置150包括处理器1501、存储器1502和收发器1503，处理器1501与存储器1502耦合，当处理器1501执行存储器1502中的计算机程序或指令时，图2-图11中远端终端设备对应的方法被执行。
如图16所示，本申请实施例还提供了一种通信装置，该通信装置160包括处理器1601、存储器1602和通信接口1603，处理器1601与存储器1602耦合，当处理器1601执行存储器1602中的计算机程序或指令时，图2-图11中AUSF网元(例如远端AUSF网元、中继AUSF网元)对应的方法被执行。
如图17所示，本申请实施例还提供了一种通信装置，该通信装置170包括处理器1701、存储器1702和通信接口1703，处理器1701与存储器1702耦合，当处理器1701执行存储器1702中的计算机程序或指令时，图2-图11中PKMF网元对应的方法被执行。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，当其在计算机或处理器上运行时，使得计算机或处理器执行图2-图11中远端终端设备对应的方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，当其在计算机或处理器上运行时，使得计算机或处理器执行图2-图11中AUSF网元(例如远端AUSF网元、中继AUSF网元)对应的方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，当其在计算机或处理器上运行时，使得计算机或处理器执行图2-图11中PKMF网元对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图2-图11中远端终端设备对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图2-图11中AUSF网元(例如远端AUSF网元、中继AUSF网元)对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图2-图11中PKMF网元对应的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于通信装置执行图2-图11中远端终端设备对应的方法，或者，执行图2-图11中AUSF网元(例如远端AUSF网元、中继AUSF网元)对应的方法，或者，执行图2-图11中PKMF网元对应的方法。
在一种可能的设计中，该芯片系统还包括存储器，该存储器，用于保存必要的程序指令和数据。该芯片系统，可以包括芯片，集成电路，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
其中，本申请提供的通信装置、芯片、计算机存储介质、计算机程序产品或芯片系统均用于执行上文所述的方法，因此，其所能达到的有益效果可参考上文所提供的实施方式中的有益效果，此处不再赘述。
本申请实施例涉及的处理器可以是一个芯片。例如，可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例涉及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的 实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (46)

  1. 一种密钥获取方法，其特征在于，包括：
    远端终端设备向中继终端设备发送第一标识和中继服务码，所述第一标识为所述远端终端设备的与所述中继服务码对应的标识或者所述第一标识为所述远端终端设备的匿名标识；
    所述远端终端设备根据第一共享密钥、所述中继服务码，以及，至少一个第一新鲜性参数，生成所述远端终端设备与所述中继终端设备通信的根密钥，所述远端认证服务功能网元为服务所述远端终端设备的认证服务功能网元，所述第一共享密钥为所述远端终端设备与所述远端认证服务功能网元共享的密钥。
  2. 根据权利要求1所述的方法，其特征在于，所述第一标识为所述远端终端设备的订阅隐藏标识SUCI。
  3. 根据权利要求1所述的方法，其特征在于，还包括：
    所述远端终端设备获取所述第一标识。
  4. 根据权利要求3所述的方法，其特征在于，所述远端终端设备获取所述第一标识，包括：
    所述远端终端设备发送所述中继服务码；
    所述远端终端设备接收与所述中继服务码对应的所述第一标识。
  5. 根据权利要求3所述的方法，其特征在于，还包括：
    所述远端终端设备根据所述第一共享密钥、所述中继服务码，生成临时标识；
    所述远端终端设备根据所述临时标识获取所述第一标识。
  6. 根据权利要求5所述的方法，其特征在于，所述远端终端设备根据所述第一共享密钥、所述中继服务码生成临时标识，包括：
    所述远端终端设备根据所述第一共享密钥、所述中继服务码和第二新鲜性参数，生成所述临时标识。
  7. 根据权利要求3所述的方法，其特征在于，所述远端终端设备获取所述第一标识，包括：
    所述远端终端设备根据第二新鲜性参数、路由指示和家乡网络标识，生成所述第一标识。
  8. 根据权利要求6或7所述的方法，其特征在于，还包括：
    所述远端终端设备发送所述中继服务码；
    所述远端终端设备接收所述中继服务码对应的所述第二新鲜性参数。
  9. 根据权利要求6或7所述的方法，其特征在于，所述第二新鲜性参数为所述远端终端设备本地维护的计数器的值。
  10. 根据权利要求3-9任一项所述的方法，其特征在于，所述第一标识包括路由指示和家乡网络标识。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，还包括：
    所述远端终端设备向所述中继终端设备发送第一验证信息，所述第一验证信息由第一临时密钥，以及，携带所述第一验证信息的消息的全部或部分信元生成，所述第一临时密钥由所述第一共享密钥生成。
  12. 根据权利要求11所述的方法，其特征在于，所述第一临时密钥由所述中继服务码、第三新鲜性参数、所述远端终端设备的第二标识以及所述第一标识中的至少一项，以及，所述第一共享密钥生成，其中，所述第三新鲜性参数为所述远端终端设备生成。
  13. 根据权利要求1-12任一项所述的方法，其特征在于，还包括：
    所述远端终端设备向所述中继终端设备发送第二验证信息，所述第二验证信息由所述第一新鲜性参数、所述中继服务码和所述第一共享密钥生成。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数包括第一随机数，还包括：
    所述远端终端设备向所述中继终端设备发送所述第一随机数。
  15. 根据权利要求1-14任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数包括第二随机数，还包括：
    所述远端终端设备从所述中继终端设备接收所述第二随机数。
  16. 根据权利要求1-13任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数为所述远端终端设备本地维护的计数器的值。
  17. 根据权利要求1-16任一项所述的方法，其特征在于，所述第一共享密钥为所述远端终端设备接入网络时与所述远端认证服务功能网元协商的密钥Kausf。
  18. 根据权利要求1-17任一项所述的方法，其特征在于，所述远端终端设备根据第一共享密钥、所述中继服务码，以及，至少一个第一新鲜性参数，生成所述远端终端设备与所述中继终端设备通信的根密钥，包括：
    所述远端终端设备根据所述第一共享密钥和所述中继服务码生成第二共享密钥，根据所述第二共享密钥以及所述至少一个第一新鲜性参数，生成所述根密钥，所述第二共享密钥为所述远端终端设备与临近业务密钥管理功能网元共享的密钥。
  19. 一种密钥获取方法，其特征在于，包括：
    远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，以及，中继服务码；所述第二标识为所述远端终端设备的永久身份标识，所述第一标识为所述远端终端设备的与所述中继服务码对应的标识；
    所述远端认证服务功能网元获取所述第一标识或所述第二标识对应的第一共享密钥；所述第一共享密钥为所述远端终端设备与所述远端认证服务功能网元共享的密钥；
    所述远端认证服务功能网元根据所述第一共享密钥、所述中继服务码，以及，至少一个第一新鲜性参数，生成所述远端终端设备与中继终端设备通信的根密钥；
    所述远端认证服务功能网元发送所述根密钥。
  20. 根据权利要求19所述的方法，其特征在于，所述远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，包括：
    所述远端认证服务功能网元接收所述远端终端设备的第一标识或第二标识中的一个。
  21. 根据权利要求19所述的方法，其特征在于，所述远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，包括：
    所述远端认证服务功能网元根据所述第一共享密钥、所述中继服务码，生成临时 标识；
    所述远端认证服务功能网元根据所述临时标识生成所述第一标识。
  22. 根据权利要求21所述的方法，其特征在于，所述远端认证服务功能网元根据所述第一共享密钥、所述中继服务码，生成临时标识，包括：
    所述远端终端设备根据所述第一共享密钥、所述中继服务码和第二新鲜性参数，生成所述临时标识。
  23. 根据权利要求19所述的方法，其特征在于，所述远端认证服务功能网元获取远端终端设备的第一标识或第二标识中的一个，包括：
    所述远端认证服务功能网元根据第二新鲜性参数、路由指示和所述远端终端设备的家乡网络标识，生成所述第一标识。
  24. 根据权利要求22或23所述的方法，其特征在于，所述第二新鲜性参数为所述远端认证服务功能网元本地维护的计数器的值。
  25. 根据权利要求22或23所述的方法，其特征在于，还包括：
    所述远端认证服务功能网元接收所述中继服务码；
    所述远端认证服务功能网元发送所述第二新鲜性参数。
  26. 根据权利要求19-25任一项所述的方法，其特征在于，还包括：
    所述远端认证服务功能网元接收所述中继服务码；
    所述远端认证服务功能网元发送所述第一标识。
  27. 根据权利要求19-26任一项所述的方法，其特征在于，所述第一标识包括路由指示和家乡网络标识。
  28. 根据权利要求19-27任一项所述的方法，其特征在于，还包括：
    所述远端认证服务功能网元接收第一验证信息；
    所述远端认证服务功能网元根据所述第一共享密钥，生成第一临时密钥；并根据所述第一临时密钥，以及，携带所述第一验证信息的消息的全部或部分信元，得到第三验证信息；
    所述远端认证服务功能网元比较所述第一验证信息和所述第三验证信息以对所述远端终端设备进行验证。
  29. 根据权利要求28所述的方法，其特征在于，所述远端认证服务功能网元根据所述第一共享密钥，生成第一临时密钥，包括：
    所述远端认证服务功能网元根据所述中继服务码、第三新鲜性参数、所述第二标识以及所述远端终端设备的第一标识中的至少一项，以及，所述第一共享密钥，生成所述第一临时密钥，所述第三新鲜性参数为所述远端终端设备生成。
  30. 根据权利要求19-29任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数包括第一随机数，还包括：
    所述远端认证服务功能网元接收所述第一随机数。
  31. 根据权利要求19-30任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数包括第二随机数，还包括：
    所述远端认证服务功能网元发送所述第二随机数。
  32. 根据权利要求19-30任一项所述的方法，其特征在于，所述至少一个第一新 鲜性参数为所述远端认证服务功能网元本地维护的计数器的值。
  33. 根据权利要求19-32任一项所述的方法，其特征在于，还包括：
    所述远端认证服务功能网元向统一数据管理网元发送所述第一标识。
  34. 根据权利要求19-33任一项所述的方法，其特征在于，所述第一共享密钥为所述远端终端设备接入网络时与所述远端认证服务功能网元协商的密钥Kausf。
  35. 一种密钥获取方法，其特征在于，包括：
    临近业务密钥管理功能网元接收远端终端设备的第一标识和中继服务码，所述第一标识为所述远端终端设备的与所述中继服务码对应的标识或者所述第一标识为所述远端终端设备的匿名标识；
    所述临近业务密钥管理功能网元根据所述第一标识获取所述远端终端设备与所述中继终端设备通信的根密钥，所述根密钥由第一共享密钥、所述中继服务码，以及，至少一个第一新鲜性参数生成，所述第一共享密钥为所述远端终端设备与远端认证服务功能网元共享的密钥；
    所述临近业务密钥管理功能网元发送所述根密钥。
  36. 根据权利要求35所述的方法，其特征在于，所述临近业务密钥管理功能网元根据所述第一标识获取所述远端终端设备与所述中继终端设备通信的根密钥，包括：
    所述临近业务密钥管理功能网元向统一数据管理功能网元发送所述第一标识；
    所述临近业务密钥管理功能网元从所述统一数据管理功能网元接收所述远端认证服务功能网元的标识信息；
    所述临近业务密钥管理功能网元根据所述标识信息，向对应的所述远端认证服务功能网元发送所述第一标识；
    所述临近业务密钥管理功能网元从所述远端认证服务功能网元接收所述根密钥。
  37. 根据权利要求35所述的方法，其特征在于，所述临近业务密钥管理功能网元根据所述第一标识获取所述远端终端设备与所述中继终端设备通信的根密钥，包括：
    所述临近业务密钥管理功能网元向统一数据管理功能网元发送所述第一标识；
    所述临近业务密钥管理功能网元从所述统一数据管理功能网元接收所述远端认证服务功能网元的标识信息以及所述远端终端设备的永久身份标识；
    所述临近业务密钥管理功能网元根据所述标识信息，向对应的所述远端认证服务功能网元发送所述远端终端设备的永久身份标识；
    所述临近业务密钥管理功能网元从所述远端认证服务功能网元接收所述根密钥。
  38. 根据权利要求35所述的方法，其特征在于，所述临近业务密钥管理功能网元根据所述第一标识获取所述远端终端设备与所述中继终端设备通信的根密钥，包括：
    所述临近业务密钥管理功能网元从远端认证服务功能网元接收至少一个第二共享密钥，所述第二共享密钥为所述远端终端设备与所述临近业务密钥管理功能网元共享的密钥，所述第二共享密钥由所述第一共享密钥和所述中继服务码生成；
    所述临近业务密钥管理功能网元根据所述第一标识对应的所述第二共享密钥，以及，至少一个第一新鲜性参数，生成所述远端终端设备与中继终端设备通信的根密钥。
  39. 根据权利要求38所述的方法，其特征在于，还包括：
    所述临近业务密钥管理功能网元接收第二验证信息；
    所述临近业务密钥管理功能网元根据所述第一新鲜性参数和所述第二共享密钥，生成第四验证信息；
    所述临近业务密钥管理功能网元比较所述第二验证信息和所述第四验证密信息以对所述远端终端设备进行验证。
  40. 根据权利要求35-39任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数包括第一随机数，还包括：
    所述临近业务密钥管理功能网元接收所述第一随机数。
  41. 根据权利要求35-40任一项所述的方法，其特征在一地，所述至少一个第一新鲜性参数包括第二随机数，还包括：
    所述临近业务密钥管理功能网元发送所述第二随机数。
  42. 根据权利要求35-39任一项所述的方法，其特征在于，所述至少一个第一新鲜性参数为所述临近业务密钥管理功能网元本地维护的计数器的值。
  43. 根据权利要求35-42任一项所述的方法，其特征在于，所述第一共享密钥为所述远端终端设备接入网络时与所述远端认证服务功能网元协商的密钥Kausf。
  44. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器相连，所述存储器用于存储计算机程序，所述处理器用于执行存储器中存储的计算机程序，以使得所述通信装置执行如权利要求1-18任一项所述的方法。
  45. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器相连，所述存储器用于存储计算机程序，所述处理器用于执行存储器中存储的计算机程序，以使得所述通信装置执行如权利要求19-34任一项所述的方法。
  46. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器相连，所述存储器用于存储计算机程序，所述处理器用于执行存储器中存储的计算机程序，以使得所述通信装置执行如权利要求35-43任一项所述的方法。
PCT/CN2020/125224 2020-10-30 2020-10-30 密钥获取方法和通信装置 WO2022088029A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CA3197006A CA3197006A1 (en) 2020-10-30 2020-10-30 Key obtaining method and communication apparatus
EP20959191.6A EP4224777A4 (en) 2020-10-30 2020-10-30 KEY ACQUISITION METHOD AND COMMUNICATION APPARATUS
PCT/CN2020/125224 WO2022088029A1 (zh) 2020-10-30 2020-10-30 密钥获取方法和通信装置
CN202080106820.2A CN116458109A (zh) 2020-10-30 2020-10-30 密钥获取方法和通信装置
US18/309,567 US20230319556A1 (en) 2020-10-30 2023-04-28 Key obtaining method and communication apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/125224 WO2022088029A1 (zh) 2020-10-30 2020-10-30 密钥获取方法和通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/309,567 Continuation US20230319556A1 (en) 2020-10-30 2023-04-28 Key obtaining method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2022088029A1 true WO2022088029A1 (zh) 2022-05-05

Family

ID=81383491

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/125224 WO2022088029A1 (zh) 2020-10-30 2020-10-30 密钥获取方法和通信装置

Country Status (5)

Country Link
US (1) US20230319556A1 (zh)
EP (1) EP4224777A4 (zh)
CN (1) CN116458109A (zh)
CA (1) CA3197006A1 (zh)
WO (1) WO2022088029A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023216932A1 (zh) * 2022-05-13 2023-11-16 华为技术有限公司 通信方法和装置
WO2023216081A1 (zh) * 2022-05-09 2023-11-16 北京小米移动软件有限公司 一种通信方法、装置及存储介质
WO2024001086A1 (zh) * 2022-06-27 2024-01-04 中国电信股份有限公司 一种基于共享密钥进行数据通信的方法、装置、设备和介质
WO2024020868A1 (zh) * 2022-07-27 2024-02-01 北京小米移动软件有限公司 密钥生成方法及装置、通信设备及存储介质
WO2024066667A1 (zh) * 2022-09-30 2024-04-04 大唐移动通信设备有限公司 密钥管理方法、装置及设备
WO2024065549A1 (zh) * 2022-09-29 2024-04-04 北京小米移动软件有限公司 直连通信密钥生成方法及装置
WO2024087071A1 (zh) * 2022-10-26 2024-05-02 华为技术有限公司 一种通信方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109716810A (zh) * 2017-01-06 2019-05-03 华为技术有限公司 授权验证方法和装置
CN109842880A (zh) * 2018-08-23 2019-06-04 华为技术有限公司 路由方法、装置及系统
US20190223063A1 (en) * 2018-01-12 2019-07-18 Qualcomm Incorporated Method and apparatus for multiple registrations

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109716810A (zh) * 2017-01-06 2019-05-03 华为技术有限公司 授权验证方法和装置
US20190223063A1 (en) * 2018-01-12 2019-07-18 Qualcomm Incorporated Method and apparatus for multiple registrations
CN109842880A (zh) * 2018-08-23 2019-06-04 华为技术有限公司 路由方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4224777A4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023216081A1 (zh) * 2022-05-09 2023-11-16 北京小米移动软件有限公司 一种通信方法、装置及存储介质
WO2023216932A1 (zh) * 2022-05-13 2023-11-16 华为技术有限公司 通信方法和装置
WO2024001086A1 (zh) * 2022-06-27 2024-01-04 中国电信股份有限公司 一种基于共享密钥进行数据通信的方法、装置、设备和介质
WO2024020868A1 (zh) * 2022-07-27 2024-02-01 北京小米移动软件有限公司 密钥生成方法及装置、通信设备及存储介质
WO2024065549A1 (zh) * 2022-09-29 2024-04-04 北京小米移动软件有限公司 直连通信密钥生成方法及装置
WO2024066667A1 (zh) * 2022-09-30 2024-04-04 大唐移动通信设备有限公司 密钥管理方法、装置及设备
WO2024087071A1 (zh) * 2022-10-26 2024-05-02 华为技术有限公司 一种通信方法、装置及系统

Also Published As

Publication number Publication date
US20230319556A1 (en) 2023-10-05
CA3197006A1 (en) 2022-05-05
EP4224777A1 (en) 2023-08-09
EP4224777A4 (en) 2023-11-01
CN116458109A (zh) 2023-07-18

Similar Documents

Publication Publication Date Title
WO2022088029A1 (zh) 密钥获取方法和通信装置
US11743970B2 (en) Session establishment method and apparatus, and packet sending method and apparatus
JP7035163B2 (ja) ネットワークセキュリティ管理方法および装置
WO2020029938A1 (zh) 安全会话方法和装置
WO2020048512A1 (zh) 通信方法和装置
US11375367B2 (en) System and method for deriving a profile for a target endpoint device
CN112534851B (zh) 委托数据连接
EP3304856A1 (en) Unified authentication for integrated small cell and wi-fi networks
KR102094216B1 (ko) 이동 통신 시스템 환경에서 프락시미티 기반 서비스 단말 간 발견 및 통신을 지원하기 위한 보안 방안 및 시스템
WO2021208861A1 (zh) 授权方法、策略控制功能设备和接入和移动管理功能设备
WO2020253701A1 (zh) 管理背景数据传输策略的方法、装置和系统
CN112566149A (zh) 配置业务的方法、通信装置和通信系统
EP4221005A1 (en) Multipath transmission method and communication apparatus
EP4262257A1 (en) Secure communication method and device
CN113811025A (zh) 一种释放中继连接的方法、设备及系统
CN113938911A (zh) 一种通信方法、设备及系统
EP4181542A1 (en) Proximity service communication method, management network element, terminal device, and communication system
CN116723507B (zh) 针对边缘网络的终端安全方法及装置
WO2020253408A1 (zh) 二级认证的方法和装置
CN116567620A (zh) 通信方法及装置
WO2020221019A1 (zh) 一种密钥协商方法及装置
WO2023160390A1 (zh) 通信方法与装置
WO2024092624A1 (en) Encryption key transfer method and device for roaming users in communication networks
WO2024032218A1 (zh) 通信方法和通信装置
CN113412679B (zh) 通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20959191

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3197006

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 202080106820.2

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2020959191

Country of ref document: EP

Effective date: 20230505

NENP Non-entry into the national phase

Ref country code: DE