Key negotiation method and device, equipment and storage medium

CN119032582AActive Publication Date: 2024-11-26BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202380008705.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-03-24
Publication Date
2024-11-26
Estimated Expiration
2043-03-24

AI Technical Summary

Technical Problem

In the communication system, it is difficult to negotiate between the user equipment (UE) and the core network equipment to generate the OSCORE master key, which affects communication security.

Method used

By receiving the key negotiation request sent by the UE, the target information is determined to indicate the target key, and the target key is indicated to the UE to ensure that the UE and the core network device can negotiate and generate the OSCORE master key.

Benefits of technology

It realizes secure communication between UE and core network equipment, ensuring the security and stability of wireless communication and the success of key negotiation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032582A_ABST
    Figure CN119032582A_ABST
Patent Text Reader

Abstract

The present disclosure proposes a key negotiation method, apparatus and device, and a storage medium, the method comprising: receiving a key negotiation request sent by a user equipment (UE), the key negotiation request comprising a key identifier and / or key indication information respectively corresponding to at least one key supported by the UE for generating an OSCORE master key; target information is determined based on at least one key identifier and / or at least one key indication information in the key negotiation request, the target information is used for indicating a target key, and the target key is a key used for generating an OSCORE master key; the target key is indicated to the UE based on the target information. The embodiment of the invention provides a key negotiation method, which is used for negotiating which key is specifically used to generate an OSCORE master key between UE and a first entity, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, ensuring that secure communication based on the OSCORE master key can be realized between the UE and the first entity, and ensuring the security and stability of wireless communication.
Need to check novelty before this filing date? Find Prior Art

Description

A key negotiation method, device, equipment and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a key negotiation method, apparatus, device, and storage medium. Background Art

[0002] In a communication system, user equipment (UE) and core network equipment usually need to generate an OSCORE master secret for constrained representational state transfer environments (OSCORE) respectively, so that they can establish an OSCORE secure connection based on the OSCORE master secret to ensure communication security.

[0003] Summary of the Invention

[0004] The present disclosure provides a key negotiation method, apparatus, device, and storage medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a key negotiation method, including:

[0006] Receiving a key agreement request sent by a user equipment UE, the key agreement request including: key identifiers and / or key indication information corresponding to at least one key supported by the UE for generating an object security OSCORE master key (OSCORE master secret) of a restricted representation state transfer environment;

[0007] Determining target information based on at least one key identifier and / or at least one key indication information in the key agreement request, where the target information is used to indicate a target key, where the target key is a key used to generate an OSCORE master key;

[0008] The target key is indicated to the UE based on the target information.

[0009] In a second aspect, an embodiment of the present disclosure provides a key negotiation method, including:

[0010] Sending a key agreement request to the first entity, where the key agreement request includes a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key;

[0011] A target key is determined based on the indication of the first entity.

[0012] In a third aspect, an embodiment of the present disclosure provides a communication device, including:

[0013] a transceiver module, configured to receive a key agreement request sent by a UE, the key agreement request comprising: a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an object security OSCORE master key (OSCORE master secret) of a restricted representation state transfer environment;

[0014] a processing module, configured to determine target information based on at least one key identifier and / or at least one key indication information in the key agreement request, wherein the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key;

[0015] A transceiver module is used to indicate the target key to the UE based on the target information.

[0016] In a fourth aspect, an embodiment of the present disclosure provides a communication device, including:

[0017] a transceiver module, configured to send a key agreement request to the first entity, where the key agreement request includes a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key;

[0018] A processing module is configured to determine a target key based on an instruction from the first entity.

[0019] In a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first or second aspect is executed.

[0020] In a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first or second aspect above.

[0021] In the seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first or second aspect above.

[0022] In an eighth aspect, an embodiment of the present disclosure provides a communication system, which includes the communication device described in aspects three to four, or the system includes the communication device described in aspect five, or the system includes the communication device described in aspect six, or the system includes the communication device described in aspect seven.

[0023] In a ninth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions for the above-mentioned network device, and when the instructions are executed, the terminal executes the method described in the first or second aspect above.

[0024] In a tenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first or second aspect above.

[0025] In an eleventh aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a network device in implementing the functions described in the first or second aspects, such as determining or processing at least one of the data and information involved in the aforementioned methods. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the source slave node. The chip system may consist of a chip or may include a chip and other discrete components.

[0026] In a twelfth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first or second aspect above.

[0027] In the thirteenth aspect, the present disclosure provides a communication system, characterized in that it includes a UE and a core network device; wherein the core network device is configured to implement the key negotiation method described in the first aspect above, and the UE is configured to implement the key negotiation method described in the second aspect above.

[0028] In a fourteenth aspect, the present disclosure provides a communication method, applied to a communication system, the method comprising:

[0029] The UE sends a key negotiation request to the core network device, where the key negotiation request includes: a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key;

[0030] The core network device determines target information based on at least one key identifier and / or at least one key indication information in the key agreement request, where the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key;

[0031] The core network device indicates the target key to the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0033] FIG1 is a schematic diagram of the architecture of some communication systems provided by embodiments of the present disclosure;

[0034] FIG2 is a schematic diagram of a flow chart of a key agreement method provided by another embodiment of the present disclosure;

[0035] FIG3 is a schematic diagram of a flow chart of a key agreement method provided in yet another embodiment of the present disclosure;

[0036] FIG4 is a schematic diagram of a flow chart of a key agreement method provided in yet another embodiment of the present disclosure;

[0037] FIG5 is a schematic diagram of a flow chart of a key agreement method provided in yet another embodiment of the present disclosure;

[0038] FIG6 is a schematic diagram of a flow chart of a key agreement method provided in yet another embodiment of the present disclosure;

[0039] FIG7 is a schematic diagram of a flow chart of a key agreement method provided in yet another embodiment of the present disclosure;

[0040] 8a-8c are flowcharts of a key agreement method provided in yet another embodiment of the present disclosure;

[0041] FIG9 is an interactive flow chart of a key agreement method provided in yet another embodiment of the present disclosure;

[0042] FIG10 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0043] FIG11 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0044] FIG12 is a block diagram of a communication device provided by one embodiment of the present disclosure;

[0045] FIG13 is a schematic structural diagram of a chip provided in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION

[0046] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0047] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0048] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0049] The embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be understood as limiting the present disclosure.

[0050] In the related technology, the OSCORE master key can be generated based on the Generic Bootstrapping Architecture (GBA) related key or the Authentication and Key management for Applications (AKMA) related key based on the 3rd Generation Partnership Project (3GPP) certificate. That is, there can be multiple keys for generating the OSCORE master key. Therefore, the UE and the core network equipment need to negotiate which key to use to generate the OSCORE master key, and a key negotiation method is urgently needed.

[0051] In order to better understand a key negotiation method disclosed in an embodiment of the present disclosure, the following first describes a communication system to which the embodiment of the present disclosure is applicable.

[0052] Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, at least one core network device and at least one UE. The number and form of devices shown in Figure 1 are for example purposes only and do not limit the embodiments of the present disclosure. An application may include one or more core network devices, or one or more UEs. The communication system shown in Figure 1 includes one core network device and one UE as an example.

[0053] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0054] The core network device in the embodiment of the present disclosure may be a device deployed in the core network. The function of the core network device is mainly to provide user connection, user management, and service bearer, and to provide an interface to the external network as a bearer network. For example, the core network device in the 5G NR system may include at least one of an application function (AF), a network application function (NAF), an authentication and key management for applications anchor function (AAnF), a bootstrapping server function (BSF), an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), and a mobility management entity (MME).

[0055] The UE in the embodiments of the present disclosure can be an entity on the user side for receiving or transmitting signals, such as a mobile phone. UE can also be called a terminal, terminal equipment, mobile station (MS), mobile terminal (MT), etc. UE can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the UE.

[0056] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0057] In addition, in order to facilitate understanding of the embodiments of the present disclosure, the following points are explained.

[0058] First, in the present disclosure, unless there is any contradiction, each step in any embodiment or example can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment or example can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment or example can be arbitrarily exchanged. In addition, the optional methods or optional examples in a certain embodiment or example can be arbitrarily combined; in addition, the various embodiments or examples can be arbitrarily combined. For example, some or all steps of different embodiments or examples can be arbitrarily combined, and a certain embodiment or example can be arbitrarily combined with the optional methods or optional examples of other embodiments or examples.

[0059] Second, regarding the description methods of the present disclosure such as "A or B", "A and / or B", "at least one of A and B", "A in one case, B in another case", "in response to one case A, in response to another case B", etc., at least one of the following schemes may be included according to the situation: executing A independently of B, that is, A in some embodiments; executing B independently of A, that is, B in some embodiments; selectively executing A and B, that is, selecting to execute from A and B in some embodiments; executing both A and B, that is, A and B in some embodiments.

[0060] Third, each element, each row, or each column in the table involved in the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0061] Fourth, in some implementation modes or examples, “including A”, “comprising A”, “used to indicate A” and “carrying A” in this disclosure can be interpreted as directly carrying A or indirectly indicating A.

[0062] Fifth, in some implementation modes or examples, "in response to...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. in the present disclosure can be replaced with each other.

[0063] FIG2 is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is performed by a first entity. As shown in FIG2 , the key negotiation method may include the following steps:

[0064] Step 201: Receive a key negotiation request sent by a UE.

[0065] Optionally, in an embodiment of the present disclosure, the first entity may be a core network device. For example, the first entity may be an application function (AF) or a network application function (NAF).

[0066] Optionally, in an embodiment of the present disclosure, the key agreement request may be sent via a Constrained Application Protocol (CoAP) request message.

[0067] Optionally, in one embodiment of the present disclosure, the key agreement request may include: key identifiers and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key (OSCORE master secret).

[0068] Optionally, in one embodiment of the present disclosure, the above-mentioned “at least one key for generating the OSCORE master key” may include at least one of the following:

[0069] GBA related keys;

[0070] AKMA related.

[0071] Optionally, the above-mentioned GBA-related key may include a first key and a second key. The first key may be, for example, Ks_int_NAF, and the second key may be, for example, Ks_ext_NAF.

[0072] Optionally, the above AKMA related key may be, for example, an AKMA application key (AKMAApplicationkey, K AF ).

[0073] Optionally, in one embodiment of the present disclosure, different UEs may support different keys for generating the OSCORE master key. For example, UE#1 may support using AKMA-related keys to generate the OSCORE master key, UE#2 may support using the first key and the second key among GBA-related keys to generate the OSCORE master key, and UE#3 may support using the first key among AKMA-related keys and GBA-related keys to generate the OSCORE master key. Therefore, in one embodiment of the present disclosure, the key agreement request sent by the UE to the first entity may include key identifiers and / or key indication information corresponding to at least one key supported by the UE for generating the OSCORE master key, so that the first entity can determine which keys supported by the UE for generating the OSCORE master key based on the at least one key identifier and / or at least one key indication information, and ultimately determine which key among these keys to use to generate the OSCORE master key.

[0074] Optionally, in an embodiment of the present disclosure, the at least one key identifier included in the key agreement request may include at least one of the following:

[0075] Authentication and Key management for ApplicationsKey Identifier (A-KID) corresponding to the AKMA-related key;

[0076] Bootstrapping Transaction Identifier (B-TID) corresponding to the GBA related key.

[0077] Optionally, in one embodiment of the present disclosure, the above-mentioned A-KID may indicate that the keys supported by the UE for generating the OSCORE master key include: AKMA-related keys. Optionally, in one embodiment of the present disclosure, when the UE supports the use of AKMA-related keys to generate the OSCORE master key, the UE may include the A-KID in the key agreement request to indicate to the first entity that the UE supports the use of AKMA-related keys to generate the OSCORE master key.

[0078] Optionally, in one embodiment of the present disclosure, the B-TID may indicate that the keys supported by the UE for generating the OSCORE master key include: GBA-related keys. Optionally, in one embodiment of the present disclosure, when the UE supports using GBA-related keys to generate the OSCORE master key, the UE may include the B-TID in the key agreement request to indicate to the first entity that the UE supports using GBA-related keys to generate the OSCORE master key.

[0079] It should be noted that, in one embodiment of the present disclosure, as can be seen from the foregoing content, there are multiple GBA-related keys (i.e., the first key and the second key mentioned above). Therefore, when the key agreement request includes a B-TID (i.e., when the key agreement request indicates that the UE supports the use of GBA-related keys to generate the OSCORE master key), the UE needs to further indicate to the first entity through the key agreement request which one or more of the GBA-related keys the UE supports for generating the OSCORE master key. Optionally, the UE can indicate to the first entity which one or more of the GBA-related keys it supports for generating the OSCORE master key through at least one of the following methods.

[0080] First, the key agreement request includes a B-TID, and the B-TID may further include a first key prompt. The first key prompt may include first key indication information corresponding to the first key and / or second key indication information corresponding to the second key.

[0081] Optionally, in one embodiment of the present disclosure, the first key indication information may indicate that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information may indicate that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

[0082] Optionally, in one embodiment of the present disclosure, when the first key prompt includes first key indication information, it means that the key supported by the UE for generating the OSCORE master key includes the first key in the GBA-related keys; when the first key prompt includes second key indication information, it means that the key supported by the UE for generating the OSCORE master key includes the second key in the GBA-related keys; when the first key prompt includes first key indication information and second key indication information, it means that the key supported by the UE for generating the OSCORE master key includes the first key and the second key in the GBA-related keys.

[0083] Optionally, in one embodiment of the present disclosure, the format of the B-TID including the first key prompt may be as follows:

[0084] Or as follows:

[0085] Optionally, the RAND is an authentication random number, the BSF_servers_domain_name is a server domain name, and the Key hint is the first key hint.

[0086] Optionally, the above-mentioned "CBOR Array" can be used to introduce how to read the B-TID specifically. For example, the CBOR Array in the above-mentioned B-TID can be an indication: the text before the colon in each line of the B-TID represents the item recorded in the line (for example, the recorded item may be RAND, BSF_servers_domain_nam or Key hint), and the text after the colon represents the specific parameter corresponding to the item, wherein the above-mentioned tstr and bstr are used to indicate the recording format of the specific parameter, such as, tstr (textstring) indicates that it is recorded in text format, and bstr (byte string) indicates that it is recorded in byte format.

[0087] Thus, the first entity can know which one or several GBA-related keys the UE supports for generating the OSCORE master key by identifying the Key hint in the above-mentioned B-TID. Optionally, when the Key hint in the B-TID includes first key indication information, it means that the UE supports using the first key in the GBA-related keys to generate the OSCORE master key; when the Key hint in the B-TID includes second key indication information, it means that the UE supports using the second key in the GBA-related keys to generate the OSCORE master key; when the Key hint in the B-TID includes first key indication information and second key indication information, it means that the UE supports using the first key and second key in the GBA-related keys to generate the OSCORE master key.

[0088] Second, the key negotiation request includes the B-TID and may further include a first key prompt. For a detailed introduction to the first key prompt, please refer to the content of the first method mentioned above.

[0089] Optionally, the second method differs from the first method in that the first method includes the first key hint in the B-TID, while the second method does not include the first key hint in the B-TID but includes it in the key agreement request.

[0090] Optionally, in an embodiment of the present disclosure, the format of the key agreement request including the first key prompt may be as follows:

[0091] Or it can be expressed in the following format:

[0092] Optionally, when the first key hint is not included in the B-TID but is included in the key agreement request, the format of the B-TID in the key agreement request may be:

[0093] Optionally, the "N1, NAF-SID, and OSC-INP" parameters in the key agreement request are existing parameters and are not described in detail. Furthermore, the "Key hint" in the key agreement request is the aforementioned first key hint. For an introduction to the "CBOR Array" and other parameters, refer to the introduction to the first method.

[0094] Optionally, the first entity can know which one or several keys of the GBA-related keys the UE supports for generating the OSCORE master key by identifying the Key hint in the above-mentioned key agreement request. Optionally, when the Key hint in the key agreement request includes first key indication information, it means that the UE supports using the first key among the GBA-related keys to generate the OSCORE master key; when the Key hint in the key agreement request includes second key indication information, it means that the UE supports using the second key among the GBA-related keys to generate the OSCORE master key; when the Key hint in the key agreement request includes first key indication information and second key indication information, it means that the UE supports using the first key and second key among the GBA-related keys to generate the OSCORE master key.

[0095] From the above content, it can be seen that when the key agreement request sent by the UE to the first entity includes B-TID (that is, the key agreement request indicates that the UE supports the use of GBA-related keys to generate the OSCORE master key), the UE can carry the first key prompt through the above two methods, so as to use the first key prompt to further indicate to the first entity which one or several GBA-related keys the UE supports to generate the OSCORE master key.

[0096] Optionally, in one embodiment of the present disclosure, the above-mentioned key agreement request may be triggered by the UE and sent to the first entity, or may be triggered by a CoAP client (CoAP client) in the UE and sent to the first entity, wherein the CoAP client may be located in a Universal Integrated Circuit Card (UICC) of the UE, or in a mobile equipment (ME) of the UE.

[0097] Optionally, the above-mentioned "sending the key agreement request triggered by the UE" can be understood as: the UE decides to send the key agreement request to the first entity. For example, the UE decides to use its own transmission module to send the key agreement request to the first entity, or the UE instructs the CoAP client to send the key agreement request to the first entity. For example, the UE can send an instruction to the CoAP client, which instructs the CoAP client to send the key agreement request to the first entity.

[0098] Optionally, the above-mentioned "sending the key negotiation request triggered by the CoAP client" can be understood as: the CoAP client decides to send the key negotiation request to the first entity. For example, the CoAP client may decide to send the key negotiation request to the first entity by itself, or the CoAP client may instruct the UE's transmission module to send the key negotiation request to the first entity. For example, the CoAP client may send an instruction to the UE's transmission module, which instructs the UE's transmission module to send the key negotiation request to the first entity.

[0099] It should be noted that in one embodiment of the present disclosure, when the triggering method of the key negotiation request is different, the content that the key negotiation request can include will be different, and when the key negotiation request is triggered and sent by the CoAP client of the UE, if the location of the CoAP client in the UE is different, the content that the key negotiation request can include will also be different.

[0100] Optionally, for the case where "the key agreement request is triggered and sent by the CoAP client of the UE", in one embodiment of the present disclosure, when the CoAP client is located in the UICC of the UE, the key agreement request triggered and sent by the CoAP client may include at least one of the A-TID, the B-TID, and the first key indication information (i.e., the key indication information corresponding to Ks_int_NAF), but cannot include the second key indication information (i.e., the key indication information corresponding to Ks_ext_NAF). When the CoAP client is located in the ME of the UE, the key agreement request triggered and sent by the CoAP client may include at least one of the A-TID, the B-TID, and the second key indication information (i.e., the key indication information corresponding to Ks_ext_NAF), but cannot include the first key indication information (i.e., the key indication information corresponding to Ks_int_NAF).

[0101] The following introduces the reasons why "when the CoAP client is located in the UICC of the UE, the key agreement request triggered by the CoAP client cannot include the second key indication information, and when the CoAP client is located in the ME of the UE, the key agreement request triggered by the CoAP client cannot include the first key indication information."

[0102] Optionally, since the UICC is used to derive Ks_int_NAF (i.e., the aforementioned first key) and cannot derive Ks_ext_NAF (i.e., the aforementioned second key), when the CoAP client is located in the UICC, the CoAP client cannot obtain the second key, and thus the key agreement request triggered and sent by the CoAP client cannot include the second key indication information corresponding to the second key. Also, since the ME is used to derive Ks_ext_NAF (i.e., the aforementioned second key) and cannot derive Ks_int_NAF (i.e., the aforementioned first key), when the CoAP client is located in the ME, the CoAP client cannot obtain the first key, and thus the key agreement request triggered and sent by the CoAP client cannot include the first key indication information corresponding to the first key.

[0103] Optionally, for the case where "the key agreement request is triggered and sent by the UE", the key agreement request triggered and sent by the UE may include at least one of A-TID, B-TID, first key indication information (i.e., key indication information corresponding to Ks_int_NAF), and second key indication information (i.e., key indication information corresponding to Ks_ext_NAF).

[0104] The following introduces the reason why “when the key negotiation request is triggered to be sent by the UE, the key negotiation request triggered to be sent by the UE can include both the first key indication information and the second key indication information”.

[0105] Optionally, since the UE includes the above-mentioned UICC and ME, the UE can obtain the first key derived from the UICC and the second key derived from the ME. Therefore, the key agreement request triggered by the UE can include both the first key indication information corresponding to the first key and the second key indication information corresponding to the second key.

[0106] Step 202: Determine target information based on at least one key identifier and / or at least one key indication information in the key agreement request.

[0107] Optionally, in one embodiment of the present disclosure, the target information may be used to indicate a target key. The target key may be a key determined by the first entity for generating an OSCORE master key. Optionally, the target key may be one of the at least one keys indicated in the key agreement request. Furthermore, the target information may be a key identifier and / or key indication information corresponding to the target key.

[0108] Optionally, in one embodiment of the present disclosure, the method for the first entity to determine the target information based on at least one key identifier and / or at least one key indication information in the key agreement request may include the following steps:

[0109] In the first step, based on the capability of the first entity and / or a local priority policy, a target key is selected from at least one key indicated in the key agreement request.

[0110] Optionally, in one embodiment of the present disclosure, the capability of the first entity may be used to indicate: a key supported by the first entity for generating an OSCORE master key.

[0111] Optionally, in one embodiment of the present disclosure, the key supported by the first entity can be determined from at least one key indicated by the key negotiation request based on the capabilities of the first entity. When the number of keys supported by the first entity is determined to be one, the one key can be directly determined as the target key; when the number of keys supported by the first entity is determined to be multiple, a key can be selected from the multiple keys as the target key based on the local policy of the first entity. Optionally, the local policy can be a local priority policy (i.e., selection based on key usage priority) or a random selection policy. That is, in one embodiment of the present disclosure, the first entity can select a key from the multiple keys as the target key based on the usage priority of different keys. Optionally, the usage priority of the different keys can be configured by other core network devices, or can be agreed upon by the protocol. Alternatively, in another embodiment of the present disclosure, the first entity can also randomly select a key from the multiple keys as the target key.

[0112] For example, assuming that a key agreement request received by a first entity includes: an A-KID, a B-TID, first key indication information, and second key indication information, then the at least one key indicated in the key agreement request is: an AKMA-related key, a first key, and a second key. If the keys supported by the first entity for generating the OSCORE master key include: an AKMA-related key and a first key, then the first entity supports two of the at least one key indicated in the key agreement request, namely, the AKMA-related key and the first key. The first entity must select one of the AKMA-related key and the first key as the target key. The first entity may select the key with a higher priority from the AKMA-related key and the first key as the target key based on the key usage priority. For example, if the key usage priority is: the AKMA-related key has a higher priority than the GBA-related key, and the first key has a higher priority than the second key, then the first entity may select the AKMA-related key with a higher priority as the target key based on the key usage priority. Alternatively, the first entity may randomly select a key from the AKMA-related key and the first key as the target key, for example, the first entity may randomly select the AKMA-related key as the target key.

[0113] The second step is to determine the key identifier and / or key indication information corresponding to the selected target key as the above-mentioned target information.

[0114] Optionally, in one embodiment of the present disclosure, when the target key selected by the first entity is: AKMA-related key, the key identifier "A-KID" corresponding to the AKMA-related key can be determined as the target information; when the target key selected by the first entity is: the first key, the key identifier "B-TID" corresponding to the first key and the first key indication information corresponding to the first key can be determined as the target information; when the target key selected by the first entity is: the second key, the key identifier "B-TID" corresponding to the second key and the second key indication information corresponding to the second key can be determined as the target information.

[0115] In addition, it should be noted that in one embodiment of the present disclosure, there may be a situation where "at least one key indicated by the key negotiation request does not include a key supported by the first entity". When this situation occurs, it indicates that the key negotiation between the first entity and the UE has failed. At this time, the target information determined in this step 202 can be used to indicate the failure of the key negotiation.

[0116] Step 203: Indicate the target key to the UE based on the target information.

[0117] Optionally, in one embodiment of the present disclosure, the above-mentioned "indicating the target key identifier to the UE" may include: sending a key negotiation response to the UE, optionally, the key negotiation response may be sent, for example, via a CoAP response message, and the key negotiation response may include a second key prompt, the second key prompt may be determined based on the target information, and the second key prompt may indicate the target key.

[0118] Optionally, the method in which the second key prompt indicates the target key may include at least one of the following:

[0119] The second key hint indicates the target key by including target information;

[0120] The second key hint indicates the target key by indicating the target information. Optionally, at least one key identifier and / or at least one key indication information included in the key agreement request may correspond to different indexes and / or sequence numbers. Based on this, the second key hint may indicate the target information by carrying the index and / or sequence number corresponding to the target information, thereby indicating the target key. For example, assume that the key agreement request received by the first entity in step 201 includes: A-KID, B-TID, and first key indication information; wherein the indexes of the A-KID, B-TID, and first key indication information are: index #1, index #2, and index #3, respectively. Also, assume that the target information determined by the first entity in step 202 is: B-TID and first key indication information. Then, in step 203, the second key hint sent by the first entity to the UE may carry index #2 and index #3. Thus, based on the second key hint, the UE can know that the target information determined by the first entity is: B-TID and first key indication information, and further know that the target key determined by the first entity is: first key.

[0121] Optionally, the format of the key agreement response including the second key prompt may be as follows:

[0122] Or it can be expressed in the following format:

[0123] Optionally, the "N2, UE-SID" in the key agreement response is an existing parameter and will not be described in detail. Furthermore, the "Information about the selected key" in the key agreement request is the aforementioned second key hint. For an introduction to the "CBOR Array" and other parameters, refer to the preceding content.

[0124] Therefore, in one embodiment of the present disclosure, the first entity indicates the target key to the UE through the above-mentioned "Information about the selected key", so that the UE can determine the target key based on the indication of the first entity, and further generate the OSCORE master key based on the target key, so that the UE can achieve secure communication with the first entity based on the generated OSCORE master key, thereby ensuring the security and stability of wireless communication.

[0125] It should be noted that, in one embodiment of the present disclosure, when the first entity determines that the key negotiation has failed in step 202 above, the target key will not be indicated to the UE based on the target information in step 203, but the key negotiation failure will be indicated to the UE. Optionally, the first entity may send a key negotiation response to the UE. The key negotiation response may be sent, for example, via a CoAP response message, and the key negotiation response may include a second key prompt, which may be used to indicate the key negotiation failure and / or the cause of the key negotiation failure. The format of the key negotiation response may be described below, where "failure cause" is used to indicate the cause of the key negotiation failure.

[0126] Or it can be expressed in the following format:

[0127] For a detailed introduction to the above parameters, please refer to the description of the aforementioned embodiments.

[0128] In summary, in the key negotiation method provided by the embodiment of the present disclosure, the first entity will receive a key negotiation request sent by the UE, and the key negotiation request includes: a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating the OSCORE master key; thereafter, the first entity will determine the target information based on the at least one key identifier and / or at least one key indication information in the key negotiation request, and the target information is used to indicate the target key, and the target key is the key selected by the first entity from the keys indicated by at least one key identifier and / or at least one key indication information in the key negotiation request for generating the OSCORE master key; and the first entity will also indicate the target key to the UE based on the target information. It can be seen from this that the embodiment of the present disclosure provides a key negotiation method for negotiating between the UE and the first entity which key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, and the security and stability of wireless communication can be ensured.

[0129] FIG3 is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is performed by a first entity. As shown in FIG3 , the key negotiation method may include the following steps:

[0130] Step 301: Obtain a target key based on target information.

[0131] Optionally, in one embodiment of the present disclosure, after the first entity executes the aforementioned step 202 (i.e., after determining the target information), the first entity may obtain the target key corresponding to the target information from other core network devices based on the target information, so as to further generate the above-mentioned OSCORE master key based on the target key. Wherein, when the target information selected by the first entity is different, the first entity will obtain the corresponding target key from different core network devices.

[0132] Optionally, in one embodiment of the present disclosure, in response to the target information including A-KID, it is indicated that the target key selected by the first entity is: AKMA related key (ie: K AF ), the first entity can obtain the AKMA-related key K from the application layer authentication and key management anchor function (Authentication and Key management for Applications Anchor Function, AAnF) based on the target information (ie, A-KID) AF Optionally, the first entity may send a first request to the AAnF, wherein the first request carries the A-KID, and the AAnF may send the corresponding AKMA-related key K to the AAnF based on the A-KID in the first request. AF Sent to the first entity.

[0133] Optionally, in another embodiment of the present disclosure, when the target information includes the B-TID and the first key indication information, it indicates that the target key selected by the first entity is the first key (i.e., Ks_int_NAF). In this case, the first entity may obtain the first key from the BSF based on the B-TID and the first key indication information. Optionally, the first entity may send a second request to the BSF, the second request carrying the B-TID and the first key indication information, and the BSF may send the first key to the first entity based on the B-TID and the first key indication information in the second request.

[0134] Optionally, in another embodiment of the present disclosure, when the target information includes the B-TID and the second key indication information, it indicates that the target key selected by the first entity is the second key (i.e., Ks_ext_NAF). In this case, the first entity may obtain the second key from the BSF based on the B-TID and the second key indication information. Optionally, the first entity may send a third request to the BSF, the third request carrying the B-TID and the second key indication information, and the BSF may send the second key to the first entity based on the B-TID and the second key indication information in the third request.

[0135] Optionally, in one embodiment of the present disclosure, the first entity obtains the target key from other core network devices so that the first entity can ultimately generate an OSCORE master key based on the target key, so that the first entity can achieve secure communication with the UE based on the generated OSCORE master key, thereby ensuring the security and stability of wireless communication.

[0136] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0137] FIG4 is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is performed by a first entity. As shown in FIG4 , the key negotiation method may include the following steps:

[0138] Step 401: In response to a key negotiation request being triggered and sent by a CoAP client, and the CoAP client is located in a UICC of a UE, the key negotiation request includes at least one of an A-KID, a B-TID, and first key indication information.

[0139] For a detailed description of step 401 , please refer to the description of the aforementioned embodiment.

[0140] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0141] FIG5 is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is performed by a first entity. As shown in FIG5 , the key negotiation method may include the following steps:

[0142] Step 501: In response to a key negotiation request triggered by a CoAP client, the CoAP client is located in the ME of a UE. The key negotiation request includes at least one of an A-KID, a B-TID, and second key indication information.

[0143] For a detailed description of step 501 , please refer to the description of the aforementioned embodiment.

[0144] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0145] FIG6 is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is performed by a first entity. As shown in FIG6 , the key negotiation method may include the following steps:

[0146] Step 601: Generate an OSCORE master key based on the target key.

[0147] Optionally, in one embodiment of the present disclosure, the first entity may derive the OSCORE master key based on the target key, or the first entity may directly set the target key as the OSCORE master key.

[0148] Step 602: Communicate with the UE based on the OSCORE master key.

[0149] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0150] FIG7 is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is executed by a UE. As shown in FIG7 , the key negotiation method may include the following steps:

[0151] Step 701: Send a key agreement request to a first entity, where the key agreement request includes a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key.

[0152] Optionally, the at least one key identifier includes at least one of the following:

[0153] An A-KID corresponding to an AKMA-related key, wherein the A-KID indicates that the keys supported by the UE for generating an OSCORE master key include: an AKMA-related key;

[0154] The B-TID corresponding to the GBA related key, where the B-TID indicates that the key supported by the UE for generating the OSCORE master key includes: the GBA related key.

[0155] Optionally, the GBA-related keys include a first key and a second key, the key negotiation request includes a B-TID, the B-TID also includes a first key prompt, the first key prompt includes first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the first key in the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key in the GBA-related keys.

[0156] Optionally, the GBA-related keys include a first key and a second key, the key negotiation request includes a B-TID, and the key negotiation request also includes a first key prompt, the first key prompt includes first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the first key in the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key in the GBA-related keys.

[0157] Optionally, the key agreement request is triggered and sent by a CoAP client in the UE;

[0158] In response to the CoAP client being located in the UICC of the UE, the first key prompt includes first key indication information;

[0159] In response to the CoAP client being located in the ME of the UE, the first key prompt includes second key indication information.

[0160] Optionally, the key agreement request is sent via a CoAP request message.

[0161] Step 702: Determine a target key based on an instruction from the first entity.

[0162] Optionally, in one embodiment of the present disclosure, the determining of the target key based on the instruction of the first entity may include:

[0163] A key agreement response is received from the UE, the key agreement response including a second key prompt, the second key prompt indicating a target key; for an introduction to the second key prompt, reference can be made to the above embodiment. Furthermore, the terminal device may determine target information based on the second key prompt, and then generate a corresponding target key based on the target information.

[0164] Optionally, in an embodiment of the present disclosure, the UE may also determine that the key negotiation fails based on an instruction from the first entity.

[0165] In addition, for a detailed description of steps 701 - 702 , reference may be made to the description of the aforementioned embodiment.

[0166] In summary, in the key negotiation method provided by the embodiment of the present disclosure, the UE will send a key negotiation request to the first entity, and the key negotiation request includes the key identifier and / or key indication information corresponding to at least one key supported by the UE for generating the OSCORE master key. Afterwards, the target key is determined based on the indication of the first entity, and the target key is the key for generating the OSCORE master key selected by the first entity from the keys indicated by at least one key identifier and / or at least one key indication information in the key negotiation request. It can be seen that the embodiment of the present disclosure provides a key negotiation method for negotiating between the UE and the first entity which key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, and the security and stability of wireless communication can be ensured.

[0167] FIG8a is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is executed by a UE. As shown in FIG8a , the key negotiation method may include the following steps:

[0168] Step 801a: Generate an OSCORE master key based on the target key;

[0169] Step 802a: Communicate with the first entity based on the OSCORE master key.

[0170] For a detailed description of steps 801a-802a, please refer to the description of the aforementioned embodiment.

[0171] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0172] FIG8b is a flow chart of a key negotiation method provided by an embodiment of the present disclosure. The method is executed by a UE. As shown in FIG8b , the key negotiation method may include the following steps:

[0173] Step 801b: In response to a key agreement request being triggered and sent by the CoAP client, and the CoAP client is located in the UICC of the UE, the key agreement request includes at least one of the A-KID, the B-TID, and the first key indication information.

[0174] For a detailed description of step 801b, please refer to the description of the aforementioned embodiment.

[0175] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0176] FIG8c is a flow chart of a key negotiation method provided in an embodiment of the present disclosure. The method is executed by a UE. As shown in FIG8c , the key negotiation method may include the following steps:

[0177] Step 801c: In response to the key agreement request being triggered and sent by the CoAP client, and the CoAP client is located in the ME of the UE, the key agreement request includes at least one of the A-KID, the B-TID, and the second key indication information.

[0178] For a detailed description of step 801c, please refer to the description of the aforementioned embodiment.

[0179] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0180] FIG9 is an interactive flow chart of a key negotiation method provided by an embodiment of the present disclosure. As shown in FIG9 , the key negotiation method may include the following steps:

[0181] Step 1: The UE or the CoAP client in the UE sends a CoAP request message to the AF or NAF. The CoAP request message includes a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating the OSCORE master key.

[0182] Step 2: The AF or NAF determines target information based on at least one key identifier and / or at least one key indication information. The target information is used to indicate a target key or to indicate a key agreement failure. The target key is a key determined by the first entity for generating the OSCORE master key. When the target information indicates a target key, steps 3-4, 5a, and 6-8 may be performed subsequently. When the target information indicates a key agreement failure, step 5b may be performed subsequently.

[0183] Step 3: The AF or NAF requests the AAnF or BSF to obtain the target key based on the target information.

[0184] Step 4: AF or NAF receives the target key sent by AAnF or BSF.

[0185] Step 5a: The AF or NAF sends a CoAP response message to the UE, where the CoAP response message indicates a target key.

[0186] Step 5b: The AF or NAF sends a CoAP response message to the UE, where the CoAP response message is used to indicate that the key negotiation has failed.

[0187] Step 6: The UE determines the target key based on the instruction of the AF or NAF.

[0188] Step 7: The AF or NAF and the UE generate an OSCORE master key based on the target key.

[0189] Step 8: The AF or NAF and the UE communicate based on the OSCORE master key.

[0190] For a detailed description of steps 1 to 8, please refer to the description of the aforementioned embodiment.

[0191] Optionally, in one embodiment of the present disclosure, the above steps 3-4 and step 5a can be performed simultaneously, or step 5a can be performed first and then step 3-4, or 3-4 can be performed first and then step 5a. The embodiment of the present disclosure is not limited to this.

[0192] To sum up, among the key negotiation methods provided in the embodiments of the present disclosure, a key negotiation method is provided, which is used for negotiating between the UE and the first entity which specific key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, ensuring the security and stability of wireless communication.

[0193] Optionally, in one embodiment of the present disclosure, a communication system is further provided, which may include a UE and a core network device, and the core network device may include an AF or a NAF (that is, the core network device can be understood as the first entity described above). The core network device is configured to implement the key negotiation method described in the embodiments of Figures 2-6 above, and the UE is configured to implement the key negotiation method described in the embodiments of Figures 7-8c above.

[0194] Optionally, in one embodiment of the present disclosure, a key agreement method is further provided, which is applied to the above communication system. The method may include:

[0195] The UE sends a key negotiation request to the core network device, where the key negotiation request includes: a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key;

[0196] The core network device determines target information based on at least one key identifier and / or at least one key indication information in the key agreement request, where the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key;

[0197] The core network device indicates the target key to the UE.

[0198] For a detailed description of the above method, please refer to the aforementioned embodiment description.

[0199] FIG10 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in FIG10 , the device may include:

[0200] a transceiver module, configured to receive a key agreement request sent by a UE, the key agreement request comprising: a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an object security OSCORE master key (OSCORE master secret) of a restricted representation state transfer environment;

[0201] a processing module, configured to determine target information based on at least one key identifier and / or at least one key indication information in the key agreement request, wherein the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key;

[0202] A transceiver module is used to indicate the target key to the UE based on the target information.

[0203] In summary, in the communication device provided by the embodiment of the present disclosure, the first entity will receive a key negotiation request sent by the UE, and the key negotiation request includes: a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating the OSCORE master key; thereafter, the first entity will determine the target information based on the at least one key identifier and / or at least one key indication information in the key negotiation request, and the target information is used to indicate the target key, and the target key is the key selected by the first entity from the keys indicated by at least one key identifier and / or at least one key indication information in the key negotiation request for generating the OSCORE master key; and the first entity will also indicate the target key to the UE based on the target information. It can be seen from this that the embodiment of the present disclosure provides a key negotiation method for negotiating between the UE and the first entity which key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, and the security and stability of wireless communication can be ensured.

[0204] Optionally, in one embodiment of the present disclosure, the at least one key identifier includes at least one of the following:

[0205] An application authentication and key management key identifier A-KID corresponding to an application authentication and key management AKMA related key, wherein the A-KID indicates that the keys supported by the UE for generating an OSCORE master key include: an AKMA related key;

[0206] A bootstrapping transaction identifier B-TID corresponding to a general bootstrapping architecture GBA related key, wherein the B-TID indicates that the key supported by the UE for generating an OSCORE master key includes: a GBA related key.

[0207] Optionally, in one embodiment of the present disclosure, the GBA-related key includes a first key and a second key;

[0208] The key agreement request includes a B-TID, and the B-TID also includes a first key prompt, the first key prompt including first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicating that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information indicating that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

[0209] Optionally, in one embodiment of the present disclosure, the GBA-related key includes a first key and a second key;

[0210] The key agreement request includes a B-TID, and the key agreement request also includes a first key prompt, the first key prompt including first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicating that the key supported by the UE for generating the OSCORE master key includes the first key in the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key in the GBA-related keys.

[0211] Optionally, in one embodiment of the present disclosure, the key agreement request is triggered and sent by a restricted application layer protocol CoAP client (CoAP client) in the UE;

[0212] In response to the CoAP client being located in a universal integrated circuit card (UICC) of the UE, the first key prompt includes first key indication information;

[0213] In response to the CoAP client being located in the mobile equipment ME of the UE, the first key prompt includes second key indication information.

[0214] Optionally, in one embodiment of the present disclosure, the processing module is further configured to:

[0215] selecting, based on capabilities and / or a local priority policy of the first entity, a target key from at least one key indicated by the key agreement request;

[0216] The key identifier and / or key indication information corresponding to the target key is determined as the target information.

[0217] Optionally, in one embodiment of the present disclosure, the target information includes an A-KID, and the target information is used to indicate an AKMA-related key; or

[0218] The target information includes a B-TID and first key indication information, where the target information is used to indicate the first key; or

[0219] The target information includes a B-TID and second key indication information, and the target information is used to indicate the second key.

[0220] Optionally, in one embodiment of the present disclosure, the apparatus is further configured to:

[0221] obtaining the target key based on the target information;

[0222] The step of obtaining the target key based on the target information includes:

[0223] In response to the target information including the A-KID, obtaining the AKMA-related key: KAF from the AKMA anchor function AAnF based on the target information;

[0224] In response to the target information including the B-TID and the first key indication information or in response to the target information including the B-TID and the second key indication information, the first key or the second key is acquired from a bootstrapping server function (BSF) based on the target information.

[0225] Optionally, in one embodiment of the present disclosure, the transceiver module is further configured to:

[0226] A key negotiation response is sent to the UE, where the key negotiation response includes a second key prompt, where the second key prompt is determined based on the target information, and where the second key prompt indicates the target key.

[0227] Optionally, in one embodiment of the present disclosure, the apparatus is further configured to:

[0228] Generate an OSCORE master key based on the target key;

[0229] Communicate with the UE based on the OSCORE master key.

[0230] Optionally, in an embodiment of the present disclosure, the key agreement request is sent via a CoAP request message.

[0231] Optionally, in an embodiment of the present disclosure, the key negotiation response is sent via a CoAP response message.

[0232] FIG11 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in FIG11 , the device may include:

[0233] a transceiver module, configured to send a key agreement request to the first entity, where the key agreement request includes a key identifier and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key;

[0234] A processing module is configured to determine a target key based on an instruction from the first entity.

[0235] In summary, in the communication device provided by the embodiment of the present disclosure, the UE will send a key negotiation request to the first entity, and the key negotiation request includes the key identifier and / or key indication information corresponding to at least one key supported by the UE for generating the OSCORE master key. Afterwards, the target key is determined based on the indication of the first entity, and the target key is the key for generating the OSCORE master key selected by the first entity from the keys indicated by at least one key identifier and / or at least one key indication information in the key negotiation request. It can be seen that the embodiment of the present disclosure provides a key negotiation method for negotiating between the UE and the first entity which key to use to generate the OSCORE master key, thereby ensuring that the UE and the first entity can successfully generate the OSCORE master key, so that secure communication based on the OSCORE master key can be achieved between the UE and the first entity, and the security and stability of wireless communication can be ensured.

[0236] Optionally, in one embodiment of the present disclosure, the at least one key identifier includes at least one of the following:

[0237] An A-KID corresponding to an AKMA-related key, wherein the A-KID indicates that the keys supported by the UE for generating an OSCORE master key include: an AKMA-related key;

[0238] The B-TID corresponding to the GBA related key, where the B-TID indicates that the key supported by the UE for generating the OSCORE master key includes: the GBA related key.

[0239] Optionally, in one embodiment of the present disclosure, the GBA-related key includes a first key and a second key;

[0240] The key agreement request includes a B-TID, and the B-TID also includes a first key prompt, the first key prompt including first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicating that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information indicating that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

[0241] Optionally, in one embodiment of the present disclosure, the GBA-related key includes a first key and a second key;

[0242] The key agreement request includes a B-TID, and the key agreement request also includes a first key prompt, the first key prompt including first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicating that the key supported by the UE for generating the OSCORE master key includes the first key in the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key in the GBA-related keys.

[0243] Optionally, in one embodiment of the present disclosure, the key agreement request is triggered and sent by a CoAP client in the UE;

[0244] In response to the CoAP client being located in the UICC of the UE, the first key prompt includes first key indication information;

[0245] In response to the CoAP client being located in the ME of the UE, the first key prompt includes second key indication information.

[0246] Optionally, in one embodiment of the present disclosure, the apparatus is further configured to:

[0247] Generate an OSCORE master key based on the target key;

[0248] Communicating with the first entity based on the OSCORE master key.

[0249] Optionally, in an embodiment of the present disclosure, the key agreement request is sent via a CoAP request message.

[0250] Optionally, in one embodiment of the present disclosure, the processing module is further configured to:

[0251] receiving a key negotiation response sent by the UE, where the key negotiation response includes a second key prompt, where the second key prompt indicates the target key;

[0252] The target key is determined based on the second key hint.

[0253] Optionally, in an embodiment of the present disclosure, the key negotiation response is sent via a CoAP response message.

[0254] Please refer to Figure 12, which is a schematic diagram of the structure of a communication device 1200 provided in an embodiment of the present disclosure. Communication device 1200 can be a base station or a terminal, or a chip, chip system, or processor that supports a base station in implementing the above-mentioned method. It can also be a chip, chip system, or processor that supports a terminal in implementing the above-mentioned method. This device can be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0255] The communication device 1200 may include one or more processors 1201. The processor 1201 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU or a CU, etc.), execute computer programs, and process computer program data.

[0256] Optionally, the communication device 1200 may further include one or more memories 1202, on which a computer program 1204 may be stored. The processor 1201 executes the computer program 1204 to cause the communication device 1200 to perform the method described in the above method embodiment. Optionally, the memory 1202 may also store data. The communication device 1200 and the memory 1202 may be provided separately or integrated together.

[0257] Optionally, the communication device 1200 may further include a transceiver 1205 and an antenna 1206. The transceiver 1205 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 1205 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0258] Optionally, the communication device 1200 may further include one or more interface circuits 1207. The interface circuit 1207 is configured to receive code instructions and transmit the code instructions to the processor 1201. The processor 1201 executes the code instructions to enable the communication device 1200 to perform the method described in the above method embodiment.

[0259] In one implementation, processor 1201 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0260] In one implementation, processor 1201 may store a computer program 1203. Computer program 1203, when executed on processor 1201, enables communication device 1200 to perform the method described in the above method embodiment. Computer program 1203 may be embedded in processor 1201, in which case processor 1201 may be implemented by hardware.

[0261] In one implementation, the communication device 1200 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0262] The communication device described in the above embodiments may be a base station or a terminal, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited to FIG12. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0263] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0264] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0265] (3) ASIC, such as modem;

[0266] (4) Modules that can be embedded in other devices;

[0267] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, base stations, cloud devices, artificial intelligence devices, etc.;

[0268] (6)Others, etc.

[0269] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 13. The chip shown in Figure 13 includes a processor 1301 and an interface 1302. The number of processors 1301 can be one or more, and the number of interfaces 1302 can be multiple.

[0270] Optionally, the chip further includes a memory 1303, which is used to store necessary computer programs and data.

[0271] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0272] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0273] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

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

[0275] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0276] The at least one in the present disclosure can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0277] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters may also adopt other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

[0278] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0279] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0280] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

Claims

1. A key negotiation method, It is characterized in that The method is performed by a first entity, and comprises: Receiving a key negotiation request sent by a user equipment UE, the key negotiation request comprising: key identifiers and / or key indication information respectively corresponding to at least one key supported by the UE for generating an object security OSCORE master secret for a restricted representation state transfer environment; Determine target information based on at least one key identifier and / or at least one key indication information in the key agreement request, wherein the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key; The target key is indicated to the UE based on the target information.

2. The method according to claim 1, It is characterized in that The at least one key identifier includes at least one of the following: An application authentication and key management key identifier A-KID corresponding to an application authentication and key management AKMA related key, wherein the A-KID indicates that the keys supported by the UE for generating an OSCORE master key include: an AKMA related key; A bootstrapping transaction identifier B-TID corresponding to a general bootstrapping architecture GBA related key, wherein the B-TID indicates that the keys supported by the UE for generating an OSCORE master key include: a GBA related key.

3. The method according to claim 2, It is characterized in that The GBA related keys include a first key and a second key; The key negotiation request includes a B-TID, and the B-TID also includes a first key prompt, the first key prompt includes first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

4. The method according to claim 2, It is characterized in that The GBA related keys include a first key and a second key; The key negotiation request includes a B-TID, and the key negotiation request also includes a first key prompt, the first key prompt includes first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

5. The method according to claim 3 or 4, It is characterized in that The key agreement request is triggered and sent by a restricted application layer protocol CoAP client (CoAP client) in the UE; In response to the CoAP client being located in a universal integrated circuit card UICC of the UE, the first key prompt includes first key indication information; In response to the CoAP client being located in the mobile equipment ME of the UE, the first key prompt includes second key indication information.

6. The method according to any one of claims 2 to 5, It is characterized in that The determining the target information based on at least one key identifier and / or at least one key indication information in the key agreement request includes: selecting, based on capabilities and / or a local priority policy of the first entity, a target key from at least one key indicated by the key agreement request; The key identifier and / or key indication information corresponding to the target key is determined as the target information.

7. The method according to claim 6, It is characterized in that The target information includes A-KID, and the target information is used to indicate an AKMA-related key; or The target information includes a B-TID and first key indication information, and the target information is used to indicate the first key; or The target information includes a B-TID and second key indication information, and the target information is used to indicate the second key.

8. The method according to any one of claims 2 to 7, It is characterized in that The method further comprises: Acquire the target key based on the target information; Wherein, obtaining the target key based on the target information includes: In response to the target information including A-KID, obtaining the AKMA-related key K from the AKMA anchor function AAnF based on the target information AF ; In response to the target information including the B-TID and the first key indication information or in response to the target information including the B-TID and the second key indication information, and obtaining the first key or the second key from a bootstrap server function BSF based on the target information.

9. The method according to any one of claims 2 to 8, It is characterized in that The indicating the target key to the UE based on the target information includes: A key negotiation response is sent to the UE, where the key negotiation response includes a second key prompt, where the second key prompt is determined based on the target information, and where the second key prompt indicates the target key.

10. The method according to claim 8, It is characterized in that The method further comprises: Generate an OSCORE master key based on the target key; Communicate with the UE based on the OSCORE master key.

11. The method according to any one of claims 1 to 10, It is characterized in that The key negotiation request is sent via a CoAP request message.

12. The method according to claim 9, It is characterized in that The key negotiation response is sent via a CoAP response message.

13. A key negotiation method, It is characterized in that The method is performed by a UE, and the method includes: Sending a key negotiation request to the first entity, the key negotiation request including key identifiers and / or key indication information respectively corresponding to at least one key supported by the UE for generating an OSCORE master key; A target key is determined based on the indication of the first entity.

14. The method according to claim 13, It is characterized in that The at least one key identifier includes at least one of the following: An A-KID corresponding to an AKMA-related key, wherein the A-KID indicates that the keys supported by the UE for generating an OSCORE master key include: an AKMA-related key; The B-TID corresponding to the GBA-related key, the B-TID indicating that the key supported by the UE for generating the OSCORE master key includes: the GBA-related key.

15. The method of claim 14, It is characterized in that The GBA related keys include a first key and a second key; The key negotiation request includes a B-TID, and the B-TID also includes a first key prompt, the first key prompt includes first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

16. The method of claim 14, It is characterized in that The GBA related keys include a first key and a second key; The key negotiation request includes a B-TID, and the key negotiation request also includes a first key prompt, the first key prompt includes first key indication information corresponding to the first key and / or second key indication information corresponding to the second key, the first key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the first key among the GBA-related keys, and the second key indication information indicates that the key supported by the UE for generating the OSCORE master key includes the second key among the GBA-related keys.

17. The method according to claim 15 or 16, It is characterized in that The key agreement request is triggered and sent by the CoAP client in the UE; In response to the CoAP client being located in the UICC of the UE, the first key prompt includes first key indication information; In response to the CoAP client being located in the ME of the UE, the first key prompt includes second key indication information.

18. The method according to any one of claims 13 to 17, It is characterized in that The method further comprises: Generate an OSCORE master key based on the target key; Communicating with the first entity based on the OSCORE master key.

19. The method according to any one of claims 13 or 18, It is characterized in that The key negotiation request is sent via a CoAP request message.

20. The method according to any one of claims 13 to 19, It is characterized in that The determining the target key based on the instruction of the first entity comprises: receiving a key negotiation response sent by the UE, where the key negotiation response includes a second key prompt, where the second key prompt indicates the target key; The target key is determined based on the second key hint.

21. The method of claim 20, It is characterized in that The key negotiation response is sent via a CoAP response message.

22. A communication device, include: A transceiver module, configured to receive a key negotiation request sent by a UE, wherein the key negotiation request includes: key identifiers and / or key indication information respectively corresponding to at least one key supported by the UE for generating an object security OSCORE master secret for a restricted representation state transfer environment; A processing module, configured to determine target information based on at least one key identifier and / or at least one key indication information in the key negotiation request, wherein the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key; A transceiver module is used to indicate the target key to the UE based on the target information.

23. A communication device, include: A transceiver module, configured to send a key negotiation request to the first entity, wherein the key negotiation request includes a key identifier and / or key indication information respectively corresponding to at least one key supported by the UE for generating an OSCORE master key; A processing module is used to determine a target key based on the indication of the first entity.

24. A communication device, It is characterized in that The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 1 to 12, or the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 13 to 21.

25. A communication device, It is characterized in that include: processor and interface circuitry, wherein The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method according to any one of claims 1 to 12, or execute the code instructions to perform the method according to any one of claims 13 to 21.

26. A communication system, It is characterized in that It comprises a UE and a core network device; wherein the core network device is configured to implement the key negotiation method described in any one of claims 1 to 12, and the UE is configured to implement the key negotiation method described in any one of claims 13 to 21.

27. A communication method, It is characterized in that Applied to a communication system, the method comprises: The UE sends a key negotiation request to the core network device, where the key negotiation request includes: key identifiers and / or key indication information corresponding to at least one key supported by the UE for generating an OSCORE master key; The core network device determines target information based on at least one key identifier and / or at least one key indication information in the key negotiation request, where the target information is used to indicate a target key, and the target key is a key used to generate an OSCORE master key; The core network device indicates the target key to the UE.

28. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 1 to 12 to be implemented, or, when executed, enable the method according to any one of claims 13 to 21 to be implemented.

Citation Information

Patent Citations

  • Key acquisition method and device

    CN113225176A

  • Key determination method and device

    CN114726520A

  • Method to authenticate a user at a service provider

    EP3726873A1