Communication methods, communication device, communication system, storage medium and program product

Abstract

The present disclosure relates to communication methods, a communication device, a communication system, a storage medium and a program product. A communication method comprises: sending a first message to a second network element, wherein the first message is used for implementing distribution of a first key, the first key is a key for the second network element, a first network element is a CU in an access network device, and the second network element is a DU in the access network device. The solution of the present disclosure can implement security protection between a terminal and an access network device.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] Security protection for signaling and data transmission in communication systems is essential. In some scenarios, signaling and data transmission between terminals and the network side is often achieved through the air interface. This makes the security of communication between the terminal and the network side particularly important. Summary of the Invention

[0003] In communication systems, the security of communication between terminals and access network equipment is often subject to significant challenges.

[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0005] According to a first aspect of the present disclosure, a communication method is provided. The method is executed by a first network element. The method includes: sending a first message to a second network element, wherein the first message is used to distribute a first key, the first key being a key specific to the second network element; wherein the first network element is a central unit (CU) in an access network device, and the second network element is a distributed unit (DU) in the access network device.

[0006] According to a second aspect of the present disclosure, a communication method is provided. The method is executed by a second network element. The method includes: receiving a first message sent by a first network element, wherein the first message is used to distribute a first key, the first key being a key specific to the second network element; wherein the first network element is a CU in an access network device, and the second network element is a DU in the access network device.

[0007] According to a third aspect of the present disclosure, a communication method is provided. The method is executed by a terminal. The method includes: receiving a second message sent by a second network element, wherein the second message is used to trigger the terminal to perform a deduction of a first key, the first key being a key specific to the second network element; wherein the second network element is a DU in an access network device.

[0008] According to a fourth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in any one of the first to third aspects.

[0009] According to a fifth aspect of the present disclosure, a communication system is provided. The communication system includes a first network element, a second network element, and a terminal. The first network element is configured to perform the communication method as described in the first aspect. The second network element is configured to perform the communication method as described in the second aspect. The terminal is configured to perform the communication method as described in the third aspect.

[0010] According to a sixth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any one of the first to third aspects.

[0011] According to a seventh aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any one of the first to third aspects.

[0012] According to an eighth aspect of the present disclosure, a computer program is provided. When this computer program is run on a computer, it causes the computer to perform the communication method as described in any one of the first to third aspects.

[0013] According to a ninth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in any one of the first to third aspects.

[0014] According to embodiments of this disclosure, security protection between the terminal and the access network device can be achieved.

[0015] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0017] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0018] Figure 2A is an exemplary schematic diagram of the NG-RAN architecture.

[0019] Figure 2B is an exemplary schematic diagram of a scenario employing a CU-DU separation architecture.

[0020] Figure 2C is an exemplary schematic diagram of the CU-DU separation architecture.

[0021] Figure 3A is an exemplary schematic diagram of key hierarchy generation in a 5G system.

[0022] Figure 3B is an exemplary schematic diagram of the MAC security key derivation hierarchy.

[0023] Figure 3C is an exemplary schematic diagram of a MAC security key derivation hierarchy based on the QKD mechanism.

[0024] Figure 4 is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0025] Figure 5 is an exemplary schematic diagram generated according to the key hierarchy structure provided in the embodiments of this disclosure.

[0026] Figure 6A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0027] Figure 6B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0028] Figure 7 is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0029] Figure 8 is an exemplary schematic diagram of a communication device provided according to an embodiment of the present disclosure.

[0030] Figure 9A is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0031] Figure 9B is an exemplary structural diagram of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0032] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0033] In a first aspect, embodiments of this disclosure provide a communication method. The method is executed by a first network element. The method includes: sending a first message to a second network element, wherein the first message is used to distribute a first key, the first key being a key specific to the second network element; wherein the first network element is a CU in an access network device, and the second network element is a DU in the access network device.

[0034] In the above embodiments, the first network element provides the first key to the second network element, enabling the second network element to achieve security based on the first key. Further, if the second network element is a DU (Distribution Unit), then the first key can be used to implement DU security.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the first key can support the security of communication between the second network element and the terminal.

[0036] In the above embodiments, the first key can support the security of communication between the second network element and the terminal. The first key used to implement the security of communication between the DU and the terminal can be distributed from the first network element to the second network element. In this way, secure communication between different protocol layers between the access network device with CU-DU separation and the terminal can be achieved.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first message may include at least one of the following: first indication information for instructing the terminal to deduce a first key; a first count value, which is a count value of the terminal's movement across DUs in the access network device; and the first key.

[0038] In the above embodiments, the first message may include a first key to distribute the first key to the second network element. Furthermore, the first message may include first indication information and / or a first count value. The first indication information may be used to explicitly instruct the terminal to perform first key derivation. Alternatively, the first count value may be used to implicitly instruct the terminal to perform first key derivation. Thus, the first indication information and / or the first count value can be used to trigger the terminal to perform first key derivation, and the derivation of the first key can be used to achieve communication security with the second network element.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the first message may include a second message, which is used to trigger the terminal to perform a deduction of the first key; wherein the first indication information and / or the first count value are included in the second message.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the second message may be a safe mode command message.

[0041] In the above embodiments, the security mode command message can ensure the integrity of information transmission between the terminal and the first network element. Thus, through the security mode command message, it can be ensured that the first indication information and / or the first count value are completely sent to the terminal, thereby triggering the derivation of the first key, further enhancing the communication security between the terminal and the second network element.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the first message may include a first key; wherein, the above method further includes: determining the first key based on a second key, wherein the second key is a key for the access network device, and the second key supports the security of communication between the access network device and the terminal.

[0043] In the above embodiments, the first key can be determined based on a second key for the access network device. The second key supports the security of communication between the access network device and the terminal, particularly between the first network element and the terminal. Thus, the first key provides a different level of communication security than the second key, achieving security at the protocol layer outside the first network element within the access network device.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the first message may be a user equipment (UE) context establishment request message.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include at least one of the following: receiving a first confirmation message sent by a second network element, wherein the first confirmation message is used to confirm that the second network element uses a first key; receiving a second confirmation message sent by a terminal, wherein the second confirmation message is used to confirm that the terminal uses the first key.

[0046] In the above embodiments, the first network element can receive a first confirmation message from the second network element to confirm that the second network element uses the first key. Furthermore, the first network element can also receive a second confirmation message from the terminal to confirm that the terminal uses the first key. Therefore, the first network element can confirm that the second network element and / or the terminal have obtained the first key, and the communication security between the second network element and the terminal is guaranteed based on the first key.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: receiving a second key sent by a third network element; triggering the derivation of a first key based on the second key; wherein the second key is a key for the access network device, and the second key supports the security of communication between the access network device and the terminal.

[0048] In the above embodiments, the first network element can obtain the second key from the third network element. Whenever the third network element provides the first network element with a new or updated second key, the first network element can update the first key and distribute it. In this way, timely refresh and synchronization of the first key are achieved, further ensuring the communication security between the second network element and the terminal.

[0049] In a second aspect, embodiments of this disclosure provide a communication method. The method is executed by a second network element. The method includes: receiving a first message sent by a first network element, wherein the first message is used to distribute a first key, the first key being a key specific to the second network element; wherein the first network element is a CU in an access network device, and the second network element is a DU in the access network device.

[0050] In the above embodiments, the first network element can send a first message to the second network element to enable the second network element to achieve security based on the first key. Further, if the second network element is a DU, then the first key is used to implement DU security.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the first key can support the security of communication between the second network element and the terminal.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the first message may include at least one of the following: first indication information for instructing the terminal to deduce the first key; a first count value for the terminal's movement across DUs in the access network device; and the first key.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes first indication information and / or a first count value; wherein, the above method further includes: sending a second message to the terminal, wherein the second message is used to trigger the terminal to perform deduction of the first key, and the second message includes the first indication information and / or the first count value.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the first message may include the second message.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the second message may be a safe mode command message.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving a second confirmation message sent by a terminal; sending a second confirmation message to a first network element; wherein the second confirmation message is used to confirm that the terminal uses the first key.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: performing security key derivation for communication between the second network element and the terminal based on the first key.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the security key derivation for communication between the second network element and the terminal includes MAC security key derivation; wherein, based on the first key, the operation of performing the security key derivation for communication between the second network element and the terminal may include: based on the first key, determining at least one of the following: CAK in the MAC security key derivation, CKN in the MAC security key derivation.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: sending a first confirmation message to a first network element, wherein the first confirmation message is used to confirm that the second network element uses the first key.

[0060] In a third aspect, embodiments of this disclosure provide a communication method. This method is executed by a terminal. The method includes: receiving a second message sent by a second network element, wherein the second message is used to trigger the terminal to perform a deduction of a first key, the first key being a key specific to the second network element; wherein the second network element is a DU in an access network device.

[0061] In the above embodiments, the second message can trigger the terminal to perform the deduction of the first key, thereby achieving security between the terminal and the second network element based on the first key.

[0062] In conjunction with some embodiments of the third aspect, in some embodiments, the first key supports the security of communication between the second network element and the terminal.

[0063] In conjunction with some embodiments of the third aspect, in some embodiments, the second message includes at least one of the following: a first indication information for instructing the terminal to deduce the first key; and a first count value for the terminal's movement across DUs in the access network device.

[0064] In conjunction with some embodiments of the third aspect, in some embodiments, the second message may be a safe mode command message.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: triggering the derivation of a first key based on a first indication information or a first count value in a second message; determining the first key based on a second key, wherein the second key is a key for the access network device, and the second key supports the security of communication between the access network device and the terminal.

[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: determining the security key derivation for communication between the second network element and the terminal based on the first key.

[0067] In conjunction with some embodiments of the third aspect, in some embodiments, the security key derivation for communication between the second network element and the terminal may include MAC security key derivation; wherein, the operation of determining the security key derivation for communication between the second network element and the terminal based on the first key may include: determining at least one of the following based on the first key: CAK in the MAC security key derivation and CKN in the MAC security key derivation.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: sending a second confirmation message to a second network element, wherein the second confirmation message is used to confirm that the terminal uses the first key.

[0069] In a fourth aspect, embodiments of this disclosure provide a communication device. The communication device is a first network element. The communication device includes a transceiver module. The transceiver module is configured to send a first message to a second network element, wherein the first message is used to distribute a first key, the first key being a key specific to the second network element; wherein the first network element is a CU in an access network device, and the second network element is a DU in the access network device.

[0070] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first key can support the security of communication between the second network element and the terminal.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first message may include at least one of the following: first indication information for instructing the terminal to deduce a first key; a first count value for the terminal's movement across DUs in the access network device; and the first key.

[0072] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first message may include a second message, which is used to trigger the terminal to perform a deduction of the first key; wherein the first indication information and / or the first count value are included in the second message.

[0073] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second message may be a safe mode command message.

[0074] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first message may include a first key; wherein, the above-mentioned apparatus further includes an extended processing module, the processing module being configured to: determine the first key based on a second key, wherein the second key is a key for the access network device, and the second key supports the security of communication between the access network device and the terminal.

[0075] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first message may be a user equipment (UE) context establishment request message.

[0076] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may be configured to perform at least one of the following: receiving a first confirmation message sent by a second network element, wherein the first confirmation message is used to confirm that the second network element uses a first key; receiving a second confirmation message sent by a terminal, wherein the second confirmation message is used to confirm that the terminal uses a first key.

[0077] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to: receive a second key sent by a third network element; trigger the derivation of a first key based on the second key; wherein the second key is a key for the access network device, and the second key supports the security of communication between the access network device and the terminal.

[0078] In a fifth aspect, embodiments of this disclosure provide a communication device. The communication device is a second network element. The communication device includes a transceiver module. The transceiver module is configured to: receive a first message sent by a first network element, wherein the first message is used to distribute a first key, the first key being a key for the second network element; wherein the first network element is a CU in an access network device, and the second network element is a DU in the access network device.

[0079] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first key can support the security of communication between the second network element and the terminal.

[0080] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first message may include at least one of the following: first indication information for instructing the terminal to deduce the first key; a first count value for the terminal's movement across DUs in the access network device; and the first key.

[0081] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first message includes first indication information and / or a first count value; wherein, the transceiver module may also be configured to: send a second message to the terminal, wherein the second message is used to trigger the terminal to perform a deduction of the first key, and the second message includes the first indication information and / or the first count value.

[0082] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first message may include the second message.

[0083] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second message may be a safe mode command message.

[0084] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: receive a second confirmation message sent by the terminal; send a second confirmation message to the first network element; wherein the second confirmation message is used to confirm that the terminal uses the first key.

[0085] In conjunction with some embodiments of the fifth aspect, in some embodiments, the above-described apparatus may further include a processing module configured to: perform security key derivation for communication between the second network element and the terminal based on the first key.

[0086] In conjunction with some embodiments of the fifth aspect, in some embodiments, the security key derivation for communication between the second network element and the terminal includes MAC security key derivation; wherein, based on the first key, the operation of performing the security key derivation for communication between the second network element and the terminal may include: based on the first key, determining at least one of the following: CAK in the MAC security key derivation, CKN in the MAC security key derivation.

[0087] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: send a first confirmation message to the first network element, wherein the first confirmation message is used to confirm that the second network element uses the first key.

[0088] In a sixth aspect, embodiments of this disclosure provide a communication device. The communication device is a terminal. The communication device includes a transceiver module. The transceiver module is configured to: receive a second message sent by a second network element, wherein the second message is used to trigger the terminal to perform a deduction of a first key, the first key being a key specific to the second network element; wherein the second network element is a DU in an access network device.

[0089] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first key supports the security of communication between the second network element and the terminal.

[0090] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second message includes at least one of the following: first indication information for instructing the terminal to deduce the first key; and a first count value for the terminal's movement across DUs in the access network device.

[0091] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second message may be a safe mode command message.

[0092] In conjunction with some embodiments of the sixth aspect, in some embodiments, the above-described apparatus may further include a processing module. The processing module is configured to: trigger the derivation of a first key based on a first indication information or a first count value in a second message; and determine the first key based on a second key, wherein the second key is a key specific to the access network device, and the second key supports the security of communication between the access network device and the terminal.

[0093] In conjunction with some embodiments of the sixth aspect, in some embodiments, the processing module may also be configured to: determine the security key derivation for communication between the second network element and the terminal based on the first key.

[0094] In conjunction with some embodiments of the sixth aspect, in some embodiments, the security key derivation for communication between the second network element and the terminal may include MAC security key derivation; wherein, the processing module may be configured to: determine at least one of the following based on the first key: CAK in the MAC security key derivation and CKN in the MAC security key derivation.

[0095] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module can be configured to send a second confirmation message to a second network element, wherein the second confirmation message is used to confirm that the terminal uses the first key.

[0096] In a seventh aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0097] In an eighth aspect, embodiments of this disclosure provide a communication system. The communication system includes a first network element, a second network element, and a terminal. The first network element is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The second network element is configured to perform the communication method as described in any of the second aspect and its possible embodiments. The terminal is configured to perform the communication method as described in any of the third aspect and its possible embodiments.

[0098] In a ninth aspect, embodiments of this disclosure provide a storage medium. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first, second, third, and possible embodiments thereof.

[0099] In a tenth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any of the first, second, third, and possible embodiments thereof.

[0100] In an eleventh aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0101] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0102] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0103] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, node, terminal, network device, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

[0104] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0105] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0106] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0107] In the embodiments of this disclosure, unless otherwise stated, elements expressed in the singular form, such as “a,” “one,” “a kind,” “the,” “the,” “the,” “the,” “the,” “the,” “the,” “the,” “this,” etc., can mean “one and only one,” or “one or more,” “at least one,” etc. For example, when articles such as “a,” “an,” and “the” are used in translation, the noun following the article can be understood as either a singular or a plural expression.

[0108] In the embodiments of this disclosure, "a plurality of" means two or more.

[0109] In some embodiments, terms such as “at least one (at least one, at least one item, at least one)” and “one or more” can be used interchangeably.

[0110] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0111] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0112] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. As another example, if the object being described is "information", then "second information" and "first information" can be the same information or different information, and their content can be the same or different.

[0113] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0114] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0115] In some embodiments, the terms "greater than", "more than", "higher than", and "exceeding" can be used interchangeably. In some embodiments, the terms "greater than or equal to", "not less than", "more than or equal to", "not less than", "higher than or equal to", "not lower than", and "above" can be used interchangeably. In some embodiments, the terms "less than", "less than", and "lower than" can be used interchangeably. In some embodiments, the terms "less than or equal to", "not greater than", "less than or equal to", "not more than", "lower than or equal to", "not higher than", and "below" can be used interchangeably.

[0116] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0117] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0118] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0119] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0120] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0121] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0122] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0123] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0124] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0125] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.

[0126] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0127] In some embodiments, the access network device 102 is, for example, a node or device that connects the terminal 101 to a wireless network. In some embodiments, the access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation evolved Node B (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0128] In some embodiments, the technical solutions of this disclosure can be applied to Open Radio Access Network (Open RAN) architectures. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0129] In some embodiments, the access network device 102 may include a first network element 1021 and a second network element 1022. In some embodiments, the first network element 1021 may be a central unit (CU) 1021. In some embodiments, the second network element 1022 may be a distributed unit (DU) 1022. In some embodiments, the CU may also be called a control unit. By adopting a CU-DU structure, the protocol layer of the access network device can be separated, with some protocol layer functions centrally controlled by the CU, and the remaining part or all of the protocol layer functions distributed in the DU, which is centrally controlled by the CU, but this is not limited to this.

[0130] In some embodiments, the core network device 103 may be a single device, including a third network element 1031, or it may be multiple devices or a group of devices, each including all or part of the third network elements 1033, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0131] In some embodiments, the third network element 1031 is, for example, an access and mobility management function (AMF).

[0132] In some embodiments, the third network element 1031 is used to be responsible for registration management, connection management, mobility management, access verification, access authorization, etc.

[0133] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0134] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0135] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0136] With the rapid development of communication technologies, in order to overcome the explosive increase in traffic usage, communication systems such as 5G are using higher frequency bands than previous communication systems (e.g., LTE). Due to the inverse relationship between frequency and cell coverage, coverage becomes a challenge. Typically, for mobile users, smaller coverage cells lead to more frequent handovers, which can negatively impact experience quality without proper management. If the number of cells managed by each individual base station (e.g., gNB) can be increased, more handovers can be handled through intra-gNB mobility. Intra-gNB mobility has a significantly smaller impact compared to inter-gNB mobility because the anchor points of the equipment are the same. By separating this function from the DU and centralizing it in the CU, the number of cells managed by each CU can be increased, thus maximizing the ratio between intra-gNB and inter-gNB handovers.

[0137] Meanwhile, higher frequency bands also allow for the use of carriers with greater bandwidth, and gNBs therefore require significantly more traffic processing capacity than eNBs in LTE. When dual connectivity is widely used in 5G networks, devices can connect to two different gNBs, but only one of the two gNBs (the anchor DU) is responsible for processing the separated data streams (via the packet data convergence protocol, PDCP). Therefore, the PDCP load is concentrated on the PDCP anchor DU, leading to load imbalance and inefficient resource utilization between the PDCP anchor DU (overused) and non-anchor DUs (underused). To improve this load imbalance, PDCP aggregation needs to be off-loaded to CUs in a more centralized location, where pooling or resource sharing can efficiently handle the tasks.

[0138] In some embodiments, in the deployment of communication systems such as 5G, gNBs with an internal structure divided into CU and DU parts can provide better service. The CU and DU can be connected via a new interface called F1.

[0139] Figure 2A is an exemplary schematic diagram of the NG-RAN architecture. As shown in Figure 2A, in a 5G network, the 5G core network (5GC) can connect to the NG-RAN via the NG interface. The NG-RAN can include a series of gNBs. These gNBs are connected to the 5GC via the NG interface. In the NG-RAN, gNBs can be connected to each other via the Xn interface. In some embodiments, a gNB can include a gNB-CU (i.e., CU) and one or more gNB-DUs (i.e., DU). The gNB-CU and gNB-DU can be connected to each other via the F1 interface. In some embodiments, a gNB-DU can only be connected to one gNB-CU.

[0140] Figure 2B is an exemplary schematic diagram of a scenario employing a CU-DU separation architecture. As shown in Figure 2B, the AMF and UPF can be located in the core network, and the gNB can be located in the access network. The AMF and gNB can communicate in the control plane via the NG interface (e.g., NG-C). The UPF and gNB can communicate in the user plane via the NG interface (e.g., NG-U). The gNB can be divided into gNB-CU and gNB-DU. The gNB-CU can connect to multiple gNB-DUs via the F1 interface.

[0141] In some embodiments, the functionality of the gNB is separated into gNB-CU and gNB-DU. Some functions of the gNB can be implemented by gNB-CU, and some functions of the gNB can be implemented by gNB-DU. It is understood that there may or may not be overlap between the functions of gNB-CU and gNB-DU.

[0142] In some embodiments, the protocol stack defined in the RAN may include multiple layers. In some embodiments, the protocol stack may include, from top to bottom, the following layers: radio resource control (RRC) layer, PDCP layer, radio link control (RLC) layer, MAC layer, physical (PHY) layer, and radio frequency (RF) layer.

[0143] In some embodiments, the functional split between the CU and DU can take several forms. In one example, the RRC can be located in the CU, while the PDCP, RLC, MAC, physical layer, and RF can be located in the DU. This approach is similar to the 1A architecture in dual-connectivity and can therefore be called 1A-type split. In another example, the RRC and PDCP can be located in the CU, while the RLC, MAC, physical layer, and RF can be located in the DU. This approach is similar to the 3C architecture in dual-connectivity and can therefore be called 3C-type split. In another example, the low RLC (i.e., part of the RLC functionality), MAC, physical layer, and RF can be located in the DU, while the PDCP and high RLC (i.e., the remaining RLC functionality) can be located in the CU. This approach can be called RLC-MAC split. In another example, the MAC, physical layer, and RF can be located in the DU, while the PDCP and RLC can be located in the CU. This approach can be called MAC-MAC split. In yet another example, the RF, physical layer, and a portion of the MAC layer (e.g., HARQ) can be located in the DU, while the remaining portions of the PDCP, RLC, and MAC layer can be located in the CU. This approach can be called MAC-internal split. In one example, the physical layer and RF can be located in the DU, while PDCP, RLC, and MAC can be located in the CU. This approach can be called MAC-PHY separation. In another example, a portion of the physical layer functionality and RF can be located in the DU, while PDCP, RLC, MAC, and other parts of the physical layer functionality can be located in the CU. This approach can be called intra-PHY separation. In yet another example, the RF functionality is located in the DU, while PDCP, RLC, MAC, and the physical layer can be located in the CU. This approach can be called PHY-RF separation.

[0144] Figure 2C is an exemplary schematic diagram of a CU-DU separation architecture. As shown in Figure 2C, the gNB-CU and gNB-DU can be separated in a 3C-type manner. In this case, RRC and PDCP can be located in the gNB-CU, while RLC, MAC, physical layer, and RF can be located in the gNB-DU.

[0145] In some embodiments, within the RAN security architecture, access stratum (AS) security terminates at and is handled by the PDCP layer of the gNB. In most decoupled configurations, since only the CU portion of the gNB supports the PDCP layer, AS security can only terminate at the CU portion, making the DU portion transparent to security protection. That is, protocol layers supported by the DU portion, such as RLC, MAC, and physical layer, are irrelevant to security-related processing.

[0146] In some embodiments, for layer 1 / layer 2 triggered mobility (LTM), media access control control element (MAC CE) messages can be used to carry security-related parameters. MAC CE messages carry radio-related information but are not protected. The protection of MAC CE messages, especially when carrying security-related information, is an important and unavoidable issue.

[0147] In some embodiments, one function of the DU portion of the gNB is to support lower layers in the protocol stack. It is understood that lower and higher layers (or lower and upper layers) can be relative. In some embodiments, one or more layers implemented in the DU portion of the protocol stack can be referred to as lower layers, and one or more layers implemented in the CU portion can be referred to as higher layers. For example, in a Class 1A separation approach, higher layers may include RRC, and lower layers may include PDCP, RLC, MAC, physical layer, and RF. For example, in a Class 3C separation approach, higher layers may include RRC and PDCP, and lower layers may include RLC, MAC, physical layer, and RF. For example, in an RLC-MAC separation approach, higher layers may include RRC, PDCP, and RLC, and lower layers may include MAC, physical layer, and RF.

[0148] In some embodiments, when a gNB supports higher-level security in the CU and lower-level security in the DU, the correlation between higher-level and lower-level security within a single gNB needs to be considered. For example, when a gNB supports PDCP layer security in the CU and MAC layer security in the DU, the correlation between PDCP layer security and MAC layer security within a single gNB needs to be considered.

[0149] Therefore, how to achieve low-level security in DU is an urgent problem to be solved.

[0150] Here, important concepts and terms involved in the embodiments of this disclosure are explained.

[0151] 1. Key hierarchy

[0152] The key hierarchy in a 5G system consists of multiple keys. These keys can be used for authentication, encryption, and integrity protection.

[0153] Figure 3A is an exemplary schematic diagram of key hierarchy generation in a 5G system. As shown in Figure 3A, the key hierarchy may include multiple keys, such as K AUSF K SEAF KAMF K N3IWF K NASint K NASenc K gNB K RRCint K RRCenc K UPint and K UPenc These keys are involved in authentication, non-access stratum (NAS) signaling protection, access stratum (AS) signaling protection, and user plane traffic protection. The arrows in the diagram indicate the direction of key generation. For example, based on K... AUSF K can be deduced SEAF For example, based on K SEAF K can be deduced AMF For example, based on K AMF K can be deduced N3IWF K NASint K NASenc K gNB For example, based on K gNB K can be deduced RRCint K RRCenc K UPint K UPenc .

[0154] In some embodiments, K serves as a key for NG-RAN. gNB It is composed of mobile entity (ME) and AMF from K AMF The derived key. In some embodiments, K gNB It can be further derived from ME and source gNB.

[0155] In some embodiments, K serves as a key for user plane traffic. UPenc It is from K by ME and gNB gNB The derived key. In one example, K UPenc It can be used solely for the protection of user plane traffic that uses specific encryption algorithms.

[0156] In some embodiments, K serves as a key for user plane traffic. UPint It is from K by ME and gNB gNB The derived key. In one example, K UPint It can be used solely for the protection of user plane traffic between ME and gNB using specific integrity algorithms.

[0157] In some embodiments, K serves as the key for RRC signaling. RRCint It is from K by ME and gNB gNB The derived key. In one example, KRRCint It can be used solely for the protection of RRC signaling that employs a specific integrity algorithm.

[0158] In some embodiments, K serves as the key for RRC signaling. RRCenc It is from K by ME and gNB gNB The derived key. In one example, K RRCenc It can be used solely for the protection of RRC signaling that uses a specific encryption algorithm.

[0159] K gNB K RRCint K RRCenc K UPint and K UPenc These are parameters for AS security processed at the PDCP layer. K RRCint and K RRCenc It is the key used to protect RRC messages on the control plane. K UPint and K UPenc It is a key used to protect Service Data Adaptation Protocol (SDAP) messages and / or Session Description Protocol (SDP) messages on the user plane. RRC messages and SDAP / SDP messages are both messages that run above the PDCP layer, therefore their security can be handled at the PDCP layer.

[0160] 2. MAC Security (MACsec)

[0161] MAC security is a secure communication method used to ensure the security protection between devices on an Ethernet link. MAC security can be based on IEEE 802.1AE and IEEE 802.1X standards. MAC security provides functions such as data encryption, integrity checks, and replay protection.

[0162] MAC security operates at the data link layer, which is the Ethernet MAC layer, and is used for end-to-end links between the interfaces of two devices, such as the gNB-DU and UE. The gNB-DU and UE can use MAC security keys to encrypt and decrypt data packets. The MACsec key agreement (MKA) provides key negotiation, as well as the establishment and management of secure channels. A long-lived connectivity association key (CAK) along with its corresponding connectivity association key name (CKN) is configured on the device.

[0163] Figure 3B is an exemplary schematic diagram of the MAC security key derivation hierarchy. As shown in Figure 3B, based on CAK and CKN, a secure association key (SAK), a key encryption key (KEK), and an integrity check key (ICK) can be obtained. In some embodiments, CAK can be used to generate a short-lived SAK to protect data transferred between devices. Data encryption is performed based on the SAK. The SAK can be updated regularly based on the number of data packets sent to make communication more secure. MAC security can not only encrypt data but also provide integrity through an integrity check value (ICV). ICV is a cryptographic digest function that depends on the data and the SAK.

[0164] 3. Quantum Key Distribution (QKD)

[0165] Quantum key distribution (QKD) is a secure communication protocol based on the principles of quantum mechanics. QKD allows two users to create and share a secure key over an insecure communication channel. This key can then be used to encrypt and decrypt information to ensure the confidentiality of the communication.

[0166] Figure 3C is an exemplary schematic diagram of a MAC security key derivation hierarchy based on the QKD mechanism. As shown in Figure 3C, user 1 and user 2 can distribute keys through the QKD mechanism. In some embodiments, the QKD between user 1 and user 2 can be implemented using continuous variable (CV) QKD protocol, discrete variable (DV) QKD protocol, satellite QKD, etc. The key distributed to user 1 and user 2 through QKD can serve as the MSK in MAC security. Based on the MSK, other keys can be obtained through key derivation functions (KDF), such as CAK and CKN in MAC security, and further ICK, SAK, KEK, etc.

[0167] In some embodiments, the KDF used for key derivation in Figure 3C may conform to the NIST 800-108 standard, formally known as "Recommendation for Key Derivation Using Pseudorandom Functions," which provides technical specifications for deriving additional key material from a secret key using pseudorandom functions. These KDFs can be used to derive additional keys from an established cryptographic key.

[0168] It is understood that the KDF used in the MAC security key derivation hierarchy can also be other KDFs, and this disclosure does not specifically limit this.

[0169] Figure 4 is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 4, the communication method of this embodiment includes steps S401 to S413.

[0170] In step S401, terminal 101 interacts with the first network element 1021.

[0171] In some embodiments, terminal 101 can interact with first network element 1021 through second network element 1022. In some embodiments, terminal 101, first network element 1021, and second network element 1022 can send and receive signaling and / or messages.

[0172] In some embodiments, the terminal 101 and the first network element 1021 can establish and exchange radio resource control (RRC) messages through the second network element 1022.

[0173] In some embodiments, step S401 can be performed during the UE initial access process. In some embodiments, during the UE initial access process of terminal 101, step S401 can be performed, and at least one of the subsequent steps S402 to S403 can be performed.

[0174] In some embodiments, in step S401, the second network element 1022 can allocate a cell radio network temporary identifier (C-RNTI) to the terminal 101. The allocated C-RNTI can be provided to the terminal 101 and the first network element 1021. In some embodiments, step S401 may include: the second network element 1022 sending the C-RNTI to the terminal 101; the second network element 1022 sending the C-RNTI to the first network element 1021.

[0175] In step S402, the first network element 1021 sends a third message to the third network element 1031.

[0176] In some embodiments, the first network element 1021 may send a third message. In some embodiments, the third message may be sent by the first network element 1021, but is not limited thereto, and may also be sent by other entities.

[0177] In some embodiments, the third network element 1031 can receive a third message. In some embodiments, the third message can be received by the third network element 1031, but is not limited thereto, and can also be received by other entities.

[0178] In some embodiments, a third message may be used to trigger the attachment process of a non-access stratum (NAS).

[0179] In some embodiments, the third message may be an initial UE message.

[0180] In some embodiments, the third message may include the initial NAS message of terminal 101.

[0181] In some embodiments, the third message may be used to convey information and capabilities of terminal 101.

[0182] In step S403, the third network element 1031 sends a fourth message to the first network element 1021.

[0183] In some embodiments, the third network element 1031 sends a fourth message. In some embodiments, the fourth message may be sent by the third network element 1031, but is not limited thereto, and may also be sent by other entities.

[0184] In some embodiments, the first network element 1021 may receive a fourth message. In some embodiments, the fourth message may be received by the first network element 1021, but is not limited thereto, and may also be received by other entities.

[0185] In some embodiments, the fourth message can be used to establish the initial context of terminal 101 on access network device 102.

[0186] In some embodiments, the fourth message may be an Initial Context Setup Request message.

[0187] In some embodiments, the fourth message may include a second key. In some embodiments, the second key may be determined by the third network element 1031. In this case, the third network element 1031 may carry the second key in the fourth message.

[0188] In some embodiments, the second key may be a key used for security of communication between access network device 102 and terminal 101. In some embodiments, the second key may be K. gNB In some embodiments, the second key may be K. eNB It is understood that the second key can also be other keys, and this disclosure does not specifically limit this type of key.

[0189] In step S404, the first network element 1021 determines the first key.

[0190] In some embodiments, the first network element 1021 can trigger a deduction of the first key based on the second key according to the fourth message. In some embodiments, the first network element 1021 can obtain the second key through the fourth message. Upon obtaining the second key, the first network element 1021 can trigger a deduction of the first key based on the second key.

[0191] In some embodiments, the first network element 1021 may obtain a new second key. In this case, the first network element 1021 does not have a second key before obtaining the new second key.

[0192] In some embodiments, the first network element 1021 may obtain an updated second key. In this case, the first network element 1021 may have an old second key before obtaining the updated second key. For example, the old second key may be one that the first network element 1021 obtained previously. In some embodiments, the updated second key and the old second key may be different.

[0193] In some embodiments, after obtaining the second key, the first network element 1021 can determine the first key based on the second key.

[0194] In some embodiments, when the first network element 1021 determines that there is a security requirement between the second network element 1022 and the terminal 101, the first network element 1021 may determine the first key based on the second key. For example, the first network element 1021 may determine the security requirement between the second network element 1022 and the terminal 101 based on operations administration and management (OAM) configuration, operator policies, and / or local configuration.

[0195] In some embodiments, the second key may be a key for access network device 102. In some embodiments, the second key may support the security of communication between access network device 102 and terminal 101. In some embodiments, the second key may be a key for first network element 1021. In some embodiments, the second key may support the security of communication between first network element 1021 and terminal 101.

[0196] In some embodiments, the second key can be used for the security of upper-layer communication, and the first key can be used for the security of lower-layer communication.

[0197] In some embodiments, the first network element 1021 may include RRC, and the second network element 1022 may include PDCP, RLC, MAC, physical layer, and RF. In one example, the second key may be used for the security of RRC. In one example, the first key may be used for the security of at least one of PDCP, RLC, and MAC.

[0198] In some embodiments, the first network element 1021 may include RRC and PDCP, and the second network element 1022 may include RLC, MAC, physical layer, and RF. In one example, the second key may be used for the security of at least one of RRC and PDCP. In one example, the first key may be used for the security of at least one of RLC and MAC.

[0199] In some embodiments, the first network element 1021 may include PDCP and high RLC, and the second network element 1022 may include low RLC, MAC, physical layer, and RF. In one example, the second key may be used for the security of at least one of PDCP and high RLC. In one example, the first key may be used for the security of at least one of low RLC and MAC.

[0200] In some embodiments, the first network element 1021 may include PDCP and RLC, and the second network element 1022 may include MAC, physical layer, and RF. In one example, the second key may be used for the security of at least one of PDCP and RLC. In one example, the first key may be used for the security of MAC.

[0201] In some embodiments, the access network device 102 may be a gNB, and the second key may be a K gNB In one example, the second key could be a 256-bit K. gNB It is understandable that access network device 102 can be other types of access network devices, such as an eNB. In this case, the second key can be K. eNB .

[0202] In some embodiments, the second key may be obtained by the first network element 1021 from other network elements. For example, the first network element 1021 may receive a second key sent by another network element. In some embodiments, the first network element 1021 may be an access and mobility management function (AMF). For example, the second key may be obtained by the AMF based on K. AMF This can be deduced.

[0203] Figure 5 is an exemplary schematic diagram generated according to the key hierarchy structure provided in the embodiments of this disclosure. As shown in Figure 5, the first key for the second network element 1022 may include K. DU K DU It can be a key for the DU in access network device 102. K DU It can be based on K gNB It was deduced.

[0204] In some embodiments, a second key can be input into the KDF. The KDF can derive a first key based on the input second key.

[0205] In some embodiments, step S401 may include: the first network element 1021 determining a first key based on a second key and according to a first parameter. In some embodiments, the first key may be derived from the second key and according to the first parameter.

[0206] In some embodiments, the first parameter can be used as input to the KDF. The KDF can derive the first key based on the input second key and the first parameter.

[0207] In some embodiments, the first parameter may include at least one of the following: first identification information, first length, first count value, second length, second identification information, and third length. It should be noted that the first parameter may also include other information, which is not specifically limited in this embodiment.

[0208] In some embodiments, the first identification information can be used to uniquely identify the terminal 101 in the access network device 102. In some embodiments, the first identification information can be used to identify the terminal 101 in the access network device 102. In some embodiments, the first identification information can be used to identify the terminal 101 in the first network element 1021.

[0209] In some embodiments, the first identification information corresponding to each terminal 101 in the access network device 102 may be unique. In some embodiments, different terminals 101 in the access network device 102 may correspond to different first identification information.

[0210] In some embodiments, the first identification information may include a C-RNTI. The C-RNTI may be an identifier used to uniquely identify terminal 101 within a cell. In some embodiments, the C-RNTI may be valid for terminal 101 in a connected state.

[0211] In some embodiments, the first identification information may be shared between the terminal 101 and the access network device 102.

[0212] In some embodiments, the first identification information may be assigned by the first network element 1021. In some embodiments, the C-RNTI may be assigned to the terminal 101 by the second network element 1022 during the initial access process of the terminal 101.

[0213] In some embodiments, the first identification information may be allocated by the second network element 1022. In some embodiments, the C-RNTI may be allocated to the terminal 101 by the first network element 1021 during the UE context establishment process.

[0214] In some embodiments, the first identification information may be transmitted via an E1 interface or an F1 interface.

[0215] In some embodiments, the first length may be the length of the first identification information.

[0216] In some embodiments, the first length may be the number of bits occupied by the first identification information.

[0217] In some embodiments, the first count value may be the count value of the terminal 101 moving across DUs in the access network device 102.

[0218] In some embodiments, terminal 101 may migrate between DUs in access network device 102. For example, terminal 101 may initially access one DU of access network device 102. For example, terminal 101 may move from one DU of access network device 102 to another DU. Such cross-DU movement causes a change in a first count value. For example, the first count value may change each time a cross-DU movement occurs.

[0219] In some embodiments, the first count value may be a positive integer.

[0220] In some embodiments, the first count value may also be referred to as the DU counter.

[0221] In some embodiments, the first count value may belong to a first count range. In some embodiments, the first count range may be determined based on the configuration of the second network element 1022 in the access network device 102. In some embodiments, the first count range may be determined based on the configuration of the second network element 1022 in the first network element 1021.

[0222] In some embodiments, the first counting range may also be referred to as the counter pool.

[0223] In some embodiments, the first counting range may be configured for the first network element 1021. In some embodiments, all second network elements 1022 under the first network element 1021 may share the first counting range. In one example, the first counting range may be an integer from 1 to N1, where N1 is a positive integer.

[0224] In some embodiments, the first counting range can be configured for the second network element 1022. In some embodiments, each second network element 1022 under the first network element 1021 can adopt an independent first counting range. In some embodiments, under the first network element 1021, different second network elements 1022 can have the same or different first counting ranges. For example, all second network elements 1022 under the first network element 1021 can have the same first counting range. For example, the first counting range of all second network elements 1022 can be an integer from 1 to N2, where N2 is a positive integer. In some embodiments, at least two second network elements 1022 under the first network element 1021 can have different first counting ranges. For example, the first counting range of one second network element 1022 can be an integer from 1 to N2, and the first counting range of another second network element 1022 can be an integer from 1 to N3, where N3 is a positive integer and N3 is not equal to N2.

[0225] In some embodiments, step S404 may include: the first network element 1021 determining a first counting range; and selecting a first counting value from the first counting range. In some embodiments, the first counting value may be an initial counting value.

[0226] In some embodiments, as terminal 101 moves between DUs in access network device 102, the first count value may change sequentially. In one example, the first count value may be incremented by 1 each time terminal 101 moves from one DU to another. In another example, the first count value may be decremented by 1 each time terminal 101 moves from one DU to another.

[0227] In some embodiments, as terminal 101 moves between DUs in access network device 102, the first count value can be determined by random generation. In one example, the first count value can be randomly generated whenever terminal 101 moves from one DU to another.

[0228] In some embodiments, the same first count value is not reused as the terminal 101 moves. In some embodiments, the terminal 101 may leave a DU and return to the DU after one or more moves. In this case, the first count value determined for the DU on two separate occasions is different. In some embodiments, the first count value determined for different DUs may be different.

[0229] In some embodiments, the first count value may be determined by the first network element 1021.

[0230] In some embodiments, the second length may be the length of the first count value.

[0231] In some embodiments, the second length may be the number of bits occupied by the first count value.

[0232] In some embodiments, the second identification information may be used to identify the cell to which the terminal 101 is attached.

[0233] In some embodiments, the second identification information may be used to identify the target cell to which the terminal 101 will attach during the handover process.

[0234] In some embodiments, the first network element 1021 can connect to one or more second network elements 1022, and each second network element 1022 can have one or more cells. Each cell can be identified by identification information. In some embodiments, the terminal 101 can reside in a cell. In other words, the terminal 101 can be attached to a cell. The cell to which the terminal 101 is attached can be identified by second identification information.

[0235] In some embodiments, the second identification information may include the cell ID of the cell to which the terminal 101 is attached.

[0236] In some embodiments, the second identification information may include the cell identifier of the target cell to which the terminal 101 will attach during the handover process.

[0237] In some embodiments, the third length may be the length of the second identification information.

[0238] In some embodiments, the third length may be the number of bits occupied by the second identification information.

[0239] In some embodiments, the first parameter may include first identification information. In some embodiments, the first network element 1021 may determine the first key based on the second key and the first identification information. In one example, the first network element 1021 may input the second key and the first identification information into the KDF to deduce the first key.

[0240] In some embodiments, the first parameter may include first identification information and a first length. In some embodiments, the first network element 1021 may determine the first key based on the second key, the first identification information, and the first length. In one example, the first network element 1021 may input the second key, the first identification information, and the first length into the KDF to derive the first key.

[0241] In some embodiments, the first parameter may include a first count value. In some embodiments, the first network element 1021 may determine the first key based on the second key and the first count value. In one example, the first network element 1021 may input the second key and the first count value into the KDF to derive the first key.

[0242] In some embodiments, the first parameter may include a first count value and a second length. In some embodiments, the first network element 1021 may determine the first key based on the second key, the first count value, and the second length. In one example, the first network element 1021 may input the second key, the first count value, and the second length into the KDF to derive the first key.

[0243] In some embodiments, the first parameter may include second identification information. In some embodiments, the first network element 1021 may determine the first key based on the second key and the second identification information. In one example, the first network element 1021 may input the second key and the second identification information into the KDF to deduce the first key.

[0244] In some embodiments, the first parameter may include second identification information and a third length. In some embodiments, the first network element 1021 may determine the first key based on the second key, the second identification information, and the third length. In one example, the first network element 1021 may input the second key, the second identification information, and the third length into the KDF to derive the first key.

[0245] In some embodiments, the first parameter may include first identification information and a first count value. In some embodiments, the first network element 1021 may determine the first key based on the second key, the first identification information, and the first count value. In one example, the first network element 1021 may input the second key, the first identification information, and the first count value into the KDF to deduce the first key.

[0246] In some embodiments, the first parameter may include first identification information, a first length, a first count value, and a second length. In some embodiments, the first network element 1021 may determine the first key based on the second key, according to the first identification information, the first length, the first count value, and the second length. In one example, the first network element 1021 may input the second key, the first identification information, the first length, the first count value, and the second length into the KDF to derive the first key.

[0247] In some embodiments, the first parameter may include a first count value and second identification information. In some embodiments, the first network element 1021 may determine the first key based on the second key, the first count value, and the second identification information. In one example, the first network element 1021 may input the second key, the first count value, and the second identification information into the KDF to deduce the first key.

[0248] In some embodiments, the first parameter may include a first count value, a second length, second identification information, and a third length. In some embodiments, the first network element 1021 may determine the first key based on the second key, according to the first count value, the second length, the second identification information, and the third length. In one example, the first network element 1021 may input the second key, the first count value, the second length, the second identification information, and the third length into the KDF to derive the first key.

[0249] In some embodiments, the first parameter may include first identification information and second identification information. In some embodiments, the first network element 1021 may determine the first key based on the second key and the first identification information and the second identification information. In one example, the first network element 1021 may input the second key, the first identification information and the second identification information into the KDF to derive the first key.

[0250] In some embodiments, the first parameter may include first identification information, a first length, second identification information, and a third length. In some embodiments, the first network element 1021 may determine the first key based on the second key, according to the first identification information, the first length, the second identification information, and the third length. In one example, the first network element 1021 may input the second key, the first identification information, the first length, the second identification information, and the third length into the KDF to derive the first key.

[0251] In some embodiments, when terminal 101 first accesses the network, the first network element 1021 can determine the first key based on the second key. In this case, step S404 can be executed.

[0252] In some embodiments, during each inter-base station handover or intra-base station handover, once the second key is refreshed, the first network element 1021 can determine the first key again based on the second key. In this case, step S404 can be executed.

[0253] In step S405, the first network element 1021 sends a first message to the second network element 1022.

[0254] In some embodiments, the first network element 1021 can send a first message. In some embodiments, the first message can be sent by the first network element 1021, but is not limited to this, and can also be sent by other entities.

[0255] In some embodiments, the second network element 1022 can receive the first message. In some embodiments, the first message can be received by the second network element 1022, but is not limited thereto, and can also be received by other entities.

[0256] In some embodiments, the first message can be used to distribute the first key. In some embodiments, the first message can be used to provide the determined first key to the second network element 1022. In some embodiments, the first message can be used to instruct the use of the first key to ensure the security of communication between the terminal 101 and the second network element 1022.

[0257] In some embodiments, the first message may be a UE context establishment request message.

[0258] In some embodiments, the first message may include at least one of the following: first indication information, first count value, and first key.

[0259] In some embodiments, the first indication information may be used to instruct terminal 101 to deduce a first key. In some embodiments, the first indication information may be used to trigger terminal 101 to deduce a first key. In some embodiments, the first indication information may be used to instruct terminal 101 to conduct secure communication with the second network element 1022.

[0260] In some embodiments, the first message may include a first key. In some embodiments, the first message may include a first key and first indication information. In some embodiments, the first message may include a first key and a first count value. In some embodiments, the first message may include first indication information, a first count value, and a first key.

[0261] In some embodiments, the first message may include a second message. The second message may be used to send a message to terminal 101. In some embodiments, the second message may be encapsulated within the first message.

[0262] In some embodiments, the second message may be a SecurityModeCommand message.

[0263] In some embodiments, the second message may include first indication information and / or a first count value.

[0264] In some embodiments, the first message may include a first key and a second message. In some embodiments, the second message may include first indication information and / or a first count value.

[0265] In some embodiments, where the first message contains a first count value but not a first indication information, the first count value can be used to trigger terminal 101 to deduce the first key. In other words, the first count value can be used as the first indication information.

[0266] In step S406, the second network element 1022 performs security key derivation.

[0267] In some embodiments, the second network element 1022 may perform security key derivation based on the first key.

[0268] In some embodiments, security key derivation can be used to achieve secure communication between the second network element 1022 and the terminal 101. In some embodiments, one or more of PDCP, RLC, MAC, physical layer, and RF can be deployed on the second network element 1022. Security key derivation can be for at least one of PDCP, RLC, and MAC. In one example, a first key can be used for security key derivation for PDCP. In one example, a first key can be used for security key derivation for RLC. In one example, a first key can be used for security key derivation for MAC.

[0269] In some embodiments, PDCP can be deployed on the first network element 1021, and MAC can be deployed on the second network element 1022. In one example, the second key can support the security of PDCP. In another example, the first key can support the security of MAC.

[0270] In some embodiments, the security key derivation for communication between the second network element 1022 and the terminal 101 may include MAC security key derivation.

[0271] In some embodiments, the operation of the second network element 1022 performing MAC security key derivation may include determining the CAK and CKN in the MAC security key derivation. Thus, the determined CAK and CKN can be used to ensure the security of the MAC layer.

[0272] In some embodiments, the second network element 1022 can determine the first key as CAK. In other words, the second key provided by the first network element 1021 to the second network element 1022 can be directly used as CAK in the MAC security key derivation.

[0273] In some embodiments, the second network element 1022 can determine the first identification information as CKN. It is understood that the first identification information can be used as a parameter in the first key derivation process, meaning that the first key and the first identification information can be associated. Therefore, the first identification information can be used as the CKN associated with CAK.

[0274] In some embodiments, the second network element 1022 can identify C-RNTI as CKN.

[0275] In some embodiments, the second network element 1022 can determine the first key as the MSK in the QKD mechanism, and determine the CAK and CKN based on the MSK. In some embodiments, the second network element 1022 can support QKD-based KDF. In this case, the first key can be used as the MSK in the QKD mechanism. Based on the MSK, the second network element 1022 can dynamically generate the CAK and CKN using KDF.

[0276] In some embodiments, the second network element 1022 may use a QKD-supporting KDF during the process of determining CAK and CKN using the QKD mechanism. For example, the KDF used by the second network element 1022 may be a KDF conforming to the NIST 800-108 standard.

[0277] In some embodiments, whenever the second network element 1022 receives a new first key, the second network element 1022 can determine a new key for security key derivation based on the new first key. This ensures that the key in the security key derivation is updated, avoiding conflicts caused by the new first key and the old first key.

[0278] In step S407, the second network element 1022 sends a second message to the terminal 101.

[0279] In some embodiments, the second network element 1022 can send a second message. In some embodiments, the second message can be sent by the second network element 1022, but is not limited thereto, and can also be sent by other entities.

[0280] In some embodiments, terminal 101 may receive a second message. In some embodiments, the second message may be received by terminal 101, but is not limited thereto, and may also be received by other entities.

[0281] In some embodiments, the second network element 1022 can send the second message carried in the first message to the terminal 101.

[0282] In some embodiments, the first message may not carry the second message. In this case, the second network element 1022 can send the second message to the terminal 101 based on the first message. For example, the first message may carry a first key, then the second network element 1022 can send the second message to the terminal 101, the second message including first indication information. For example, the first message may carry a first key, as well as first indication information and / or a first count value, then the second network element 1022 can send the second message to the terminal 101, the second message including first indication information and / or a first count value.

[0283] In step S408, the second network element 1022 sends a first confirmation message to the first network element 1021.

[0284] In some embodiments, the second network element 1022 may send a first confirmation message. In some embodiments, the first confirmation message may be sent by the second network element 1022, but is not limited thereto, and may also be sent by other entities.

[0285] In some embodiments, the first network element 1021 may receive a first confirmation message. In some embodiments, the first confirmation message may be received by the first network element 1021, but is not limited thereto, and may also be received by other entities.

[0286] In some embodiments, the first confirmation message can be used to confirm that the first key has been used. In some embodiments, when the second network element 1022 uses the first key, the first confirmation message can be sent to the first network element 1021.

[0287] In some embodiments, the first confirmation message may be a UE context setup response (UE CONTEXT SETUP RESPONSE) message.

[0288] In step S409, terminal 101 determines the first key.

[0289] The optional implementation of step S409 can be found in the optional implementation of step S404 in Figure 4, as well as other related parts in the embodiments involved in Figure 4, which will not be repeated here.

[0290] In some embodiments, upon receiving a second message, terminal 101 may perform a deduction of the first key based on the first indication information and / or the first count value in the second message.

[0291] It is understandable that the method by which terminal 101 determines the first key can be the same as the method by which the first network element 1021 determines the first key, and will not be elaborated here.

[0292] In step S410, terminal 101 performs security key derivation.

[0293] The optional implementation of step S410 can be found in the optional implementation of step S406 in Figure 4, as well as other related parts in the embodiments involved in Figure 4, which will not be repeated here.

[0294] In some embodiments, terminal 101 may perform security key derivation based on the first key.

[0295] It is understandable that the way terminal 101 performs security key deduction and the way the second network element 1022 performs security key deduction can be the same, and will not be elaborated here.

[0296] In step S411, terminal 101 sends a second confirmation message to first network element 1021.

[0297] In some embodiments, terminal 101 may send a second confirmation message. In some embodiments, the second confirmation message may be sent by terminal 101, but is not limited thereto, and may also be sent by other entities.

[0298] In some embodiments, the first network element 1021 may receive a second confirmation message. In some embodiments, the second confirmation message may be received by the first network element 1021, but is not limited thereto, and may also be received by other entities.

[0299] In some embodiments, the second confirmation message can be used to confirm that terminal 101 uses the first key. In some embodiments, if terminal 101 determines and uses the first key, the second confirmation message can be sent to the first network element 1021.

[0300] In some embodiments, the second confirmation message may be a SecurityModeComplete message.

[0301] In some embodiments, the second confirmation message may be a different message from the security mode completion message.

[0302] In some embodiments, the second confirmation message can be sent from the second network element 1022 to the first network element 1021. In some embodiments, the second network element 1022 can forward or transparently transmit the second confirmation message to the first network element 1021.

[0303] In step S412, terminal 101 interacts with the first network element 1021.

[0304] In some embodiments, terminal 101 can interact with first network element 1021 through second network element 1022. In some embodiments, terminal 101, first network element 1021, and second network element 1022 can send and receive signaling and / or messages.

[0305] In some embodiments, terminal 101 and first network element 1021 can exchange RRC reconfiguration messages via second network element 1022. In some embodiments, first network element 1021 can trigger an RRC reconfiguration process with terminal 101. During the RRC reconfiguration process, terminal 101 and second network element 1022 can exchange signaling and / or messages.

[0306] In step S413, the first network element 1021 sends a fifth message to the third network element 1031.

[0307] In some embodiments, the first network element 1021 may send a fifth message. In some embodiments, the fifth message may be sent by the first network element 1021, but is not limited thereto, and may also be sent by other entities.

[0308] In some embodiments, the third network element 1031 can receive the fifth message. In some embodiments, the fifth message can be received by the third network element 1031, but is not limited thereto, and can also be received by other entities.

[0309] In some embodiments, the fifth message may be a response message to the fourth message.

[0310] In some embodiments, the fifth message may be an Initial Context Setup Response message.

[0311] The communication method of this embodiment can be implemented through steps S401 to S413.

[0312] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0313] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0314] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0315] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0316] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0317] In some embodiments, if the arrows in the interaction diagram representing the sending of information, signaling, etc., from one subject to another pass through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects. For example, in step S404, the first information can be sent directly to the terminal 101 by the first network element 1021, or it can be sent to the terminal 101 by the first network element 1021 through the second network element 1022.

[0318] In some embodiments, terms such as “derivation,” “inference,” and “derive” can be used interchangeably.

[0319] The communication method involved in the embodiments of this disclosure may include at least one of steps S401 to S413. For example, step S405 may be implemented as a standalone embodiment. For example, step S407 may be implemented as a standalone embodiment. For example, a combination of steps S404 and S405 may be implemented as a standalone embodiment. For example, a combination of steps S405 and S406 may be implemented as a standalone embodiment. For example, a combination of steps S405 and S407 may be implemented as a standalone embodiment. For example, a combination of steps S407 and S409 may be implemented as a standalone embodiment. For example, a combination of steps S404, S405, and S406 may be implemented as a standalone embodiment. For example, a combination of steps S404, S405, and S407 may be implemented as a standalone embodiment. For example, a combination of steps S407, S408, and S409 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments composed of one or more steps in steps S401 and S413 are not limited thereto.

[0320] In some embodiments, at least two steps in steps S401 to S413 may be executed simultaneously or in a different order. For example, steps S406 and S407 may be executed simultaneously or in a different order. For example, steps S407 and S408 may be executed simultaneously or in a different order. For example, steps S408 and S409 may be executed simultaneously or in a different order.

[0321] In some embodiments, steps S401, S402, S403, S404, S406, S407, S408, S409, S410, S411, S412, and S413 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0322] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0323] Figure 6A is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 6A, the method includes step S6101.

[0324] In step S6101, the first network element 1021 sends a first message to the second network element 1022.

[0325] In some embodiments, the second network element 1022 may perform security key derivation based on the first key carried in the first message.

[0326] In some embodiments, the second network element 1022 may send a second message to the terminal 101 based on the first message.

[0327] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0328] Figure 6B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 6B, the method includes step S6201.

[0329] In step S6201, the second network element 1022 sends a second message to the terminal 101.

[0330] In some embodiments, the second message may trigger terminal 101 to perform the derivation and use of the first key.

[0331] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0332] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.

[0333] In some embodiments, to support MAC layer security, from K gNB The root key (e.g., called K) used for MAC security by gNB-DU is derived. DU And stored in gNB-DU. Therefore, the new key hierarchy in gNB and ME can be shown in Figure 5.

[0334] In some embodiments, K DUGenerated by gNB-CU, distributed to gNB-DU, and stored in gNB-DU. From K in gNB and ME. gNB Derivation of K DU When the following parameters can be used as input S of KDF:

[0335] -FC = TBD (to be continued, pending);

[0336] -P0 = Service / Target Cell Identifier;

[0337] -L0 = length of P0;

[0338] -P1 = the value of the DU counter (a non-negative integer);

[0339] -L1 = length of P1.

[0340] During initial UE access, P0 is the identifier of the cell to which the UE is attached (camp), supported by the serving gNB-DU. During UE mobility, P0 is the identifier of the target cell to which the UE is handover, supported by the target gNB-DU.

[0341] P1 can be in each K DU The derivation of the counters is handled by the gNB-CU, which allocates and passes them to the UE. The gNB-CU configures the DU counter pool.

[0342] In some embodiments, P0 can also be any type of RAN UE ID shared between the UE and gNB, such as a C-RNTI assigned to the UE by the gNB-DU during the UE's initial joining process, or assigned to the UE by the gNB-CU during UE context establishment. P0 can be transmitted via the E1 and F1 interfaces. The RAN UE ID is unique within the gNB. Regardless of when the RAN UE ID is refreshed, K... DU Also refreshed.

[0343] In some embodiments, from K in gNB and ME gNB Derivation of K DU When the following parameters can be used as input S of KDF:

[0344] -FC = TBD;

[0345] -P0 = RAN UE ID (e.g., C-RNTI);

[0346] -L0 = P0 length.

[0347] In some embodiments, the input key is a 256-bit K gNB .

[0348] In some embodiments, during each inter-gNB or intra-gNB handover, once K gNB Refreshed, from the refreshed K gNB Similarly, regenerate K. DU .

[0349] Figure 7 is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. This implementation relates to the distribution of the root key and deduced input parameters during initial access of the UE.

[0350] In some embodiments, K DU Generated by gNB-CU and needing to be distributed to gNB-DU. Furthermore, derivation data (e.g., C-RNTI, DU counters) also needs to be usable in both the UE and gNB-CU for derivation K. DU At the same time, the UE needs to be notified to trigger the generation of K in the same manner. DU So that K DU It can be shared between UE and gNB-DU.

[0351] In some embodiments, as the UE accesses the network and moves within the network, K DU The distribution of key-derived input parameters can be performed. DU The key derivation input parameters can be distributed during the UE's initial access process, as shown in Figure 7.

[0352] Referring to Figure 7, the communication method may include steps S701 to S712.

[0353] In step S701, the UE (i.e., the terminal) and gNB-CU (i.e., the first network element) exchange RRC establishment messages via gNB-DU (i.e., the second network element). During this process, the C-RNTI allocated by the gNB-DU is sent to the gNB-CU and can be obtained by the UE.

[0354] In step S702, gNB-CU sends an initial UE message to AMF (i.e., the third network element).

[0355] In step S703, the AMF sends an initial context establishment request message to the gNB-CU.

[0356] In step S704, when the initial context establishment request message contains K gNB When using the second key, if (e.g., based on local policy) gNB-DU is required to support lower-level security, gNB-CU determines to use K. gNB Derivation of K DU (i.e., the first key).

[0357] In some embodiments, the key derivation input parameters may be the identifier of the cell to which the UE is attached (i.e., the second identification information), or the C-RNTI (i.e., the first identification information) sent by the gNB-DU in step S702. The gNB-CU generates a DU counter pool (i.e., a first counting range) and selects an initial DU counter to deduce K. DU .

[0358] In step S705, the gNB-CU then sends a UE context establishment request message to establish a UE context in the gNB-DU. This message may also encapsulate a security mode command message.

[0359] In some embodiments, if K is derived in step S705 DU Then gNB-CU can also K DU This is included in the UE context establishment request message. Since the security mode command message is protected for integrity between the gNB-CU and the UE, the gNB-CU may also include the DU counter (i.e., the first count value) and / or key derivation indication (i.e., the first indication information) in the security mode command message.

[0360] In some embodiments, the key derivation indicator is used to trigger the UE to deduce the security key of the lower layer (e.g., K). DU (Deduction Indication). Since the DU is also included in the security mode command message, the counter can also be used as a key deduction indication for the UE, so a separate indication is not required.

[0361] In step S706, gNB-DU obtains K from the UE context establishment request message. DU .

[0362] In some embodiments, gNB-DU can be transferred from K during this step. DU Derivation of CAK / CKN, or K DU Specify CAK.

[0363] In some embodiments, before the gNB-DU triggers the lower-layer security establishment in a subsequent step, the gNB-DU can access the K... DU Derivation of CAK / CKN, or K DU Specify CAK.

[0364] In step S707, gNB-DU forwards the security mode command message from gNB-CU to UE.

[0365] In step S708, the gNB-DU sends a UE context establishment response message to the gNB-CU. In some embodiments, this response may include K DU Confirmation of usage.

[0366] In step S709, if the UE obtains the DU counter and / or key derivation indication from the security mode command message, the UE determines from K gNB Derivation of K DU .

[0367] In some embodiments, the UE may, in this step, transfer data from K. DU Derivation of CAK / CKN, or K DU Specify CAK.

[0368] In some embodiments, before receiving a low-layer security establishment request from the gNB-DU in subsequent steps, the UE can access the K... DU Derivation of CAK / CKN, or K DU Specify CAK.

[0369] In step S710, the UE sends a security mode completion message to the gNB-CU via the gNB-DU as a response.

[0370] In some embodiments, the security mode completion message may include K DU The confirmation of its use is sent to gNB-CU.

[0371] In some embodiments, the UE sends K to the gNB-DU in parallel with the security mode completion message. DU Confirmation of usage.

[0372] In step S711, gNB-CU triggers the RRC reconfiguration process with the UE via gNB-DU.

[0373] In step S712, gNB-CU sends an initial context establishment response message to AMF.

[0374] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0375] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the terminal in any of the above methods. For example, this disclosure proposes another apparatus including units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0376] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0377] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0378] Figure 8 is an exemplary schematic diagram of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 8, the communication device 800 may include at least one of the following: a transceiver module 801 and a processing module 802.

[0379] In some embodiments, the communication device 800 may be a first network element. In some embodiments, the transceiver module 801 may be configured to send a first message to a second network element, wherein the first message is used to distribute a first key, and the first key is a key for the second network element; wherein the first network element is a CU in the access network device, and the second network element is a DU in the access network device. Optionally, the transceiver module 801 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first network element in any of the above methods (e.g., steps S401, S402, S403, S405, S408, S411, S412, S413, but not limited thereto), which will not be elaborated here. Optionally, the processing module 802 may be configured to perform at least one of the other steps performed by the first network element in any of the above methods besides the communication steps such as sending and receiving (e.g., step S404, but not limited thereto).

[0380] In some embodiments, the communication device 800 may be a second network element. In some embodiments, the transceiver module 801 may be configured to: receive a first message sent by a first network element, wherein the first message is used to distribute a first key, and the first key is a key for the second network element; wherein the first network element is a CU in the access network device, and the second network element is a DU in the access network device. Optionally, the transceiver module 801 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second network element in any of the above methods (e.g., steps S401, S405, S407, S408, S411, but not limited thereto), which will not be elaborated here.

[0381] In some embodiments, the communication device 800 may be a terminal. In some embodiments, the transceiver module 801 may be configured to: receive a second message sent by a second network element, wherein the second message is used to trigger the terminal to perform a deduction of a first key, the first key being a key for the second network element; wherein the second network element is a DU in the access network device. Optionally, the transceiver module 801 may be configured to perform at least one of the communication steps (e.g., steps S401, S407, S411, S412, but not limited thereto) performed by the first network element in any of the above methods, which will not be elaborated here. Optionally, the processing module 802 may be configured to perform at least one of the other steps (e.g., steps S409, S410, but not limited thereto) performed by the first network element in any of the above methods, excluding the communication steps such as sending and receiving.

[0382] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0383] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0384] Figure 9A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 9100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 9100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0385] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. Optionally, the communication device 9100 can be used to execute any of the above methods. Optionally, one or more processors 9101 can be used to invoke instructions to cause the communication device 9100 to execute any of the above methods.

[0386] In some embodiments, the communication device 9100 further includes one or more transceivers 9102. When the communication device 9100 includes one or more transceivers 9102, the transceiver 9102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S401, S402, S403, S405, S407, S408, S411, S412, S413, but not limited thereto), and the processor 9101 performs at least one of other steps (e.g., steps S404, S406, S409, S410, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0387] In some embodiments, the communication device 9100 further includes one or more memories 9103 for storing data. Optionally, all or part of the memories 9103 may be located outside the communication device 9100. In optional embodiments, the communication device 9100 may include one or more interface circuits 9104. Optionally, the interface circuits 9104 are connected to the memories 9103 and can be used to receive data from the memories 9103 or other devices, and to send data to the memories 9103 or other devices. For example, the interface circuits 9104 can read data stored in the memories 9103 and send that data to the processor 9101.

[0388] The communication device 9100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 9100 described in this disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0389] Figure 9B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the chip 9200 shown in Figure 9B, but it is not limited thereto.

[0390] Chip 9200 includes one or more processors 9201. Chip 9200 is used to perform any of the methods described above.

[0391] In some embodiments, chip 9200 further includes one or more interface circuits 9202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 9200 further includes one or more memories 9203 for storing data. Optionally, all or part of the memories 9203 may be located outside chip 9200. Optionally, interface circuit 9202 is connected to memory 9203, and interface circuit 9202 can be used to receive data from memory 9203 or other devices, and interface circuit 9202 can be used to send data to memory 9203 or other devices. For example, interface circuit 9202 can read data stored in memory 9203 and send the data to processor 9201.

[0392] In some embodiments, the interface circuit 9202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S401, S402, S403, S405, S407, S408, S411, S412, S413, but not limited thereto). The interface circuit 9202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 9202 performing data interaction between the processor 9201, the chip 9200, the memory 9203, or the transceiver device. In some embodiments, the processor 9201 performs at least one of other steps (e.g., steps S404, S406, S409, S410, but not limited thereto).

[0393] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0394] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 9100, cause the communication device 9100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0395] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 9100, cause the communication device 9100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0396] This disclosure also provides a program product that, when executed by a communication device 9100, causes the communication device 9100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0397] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0398] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only.

[0399] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, executed by a first network element, wherein, The method includes: Send a first message to the second network element, wherein the first message is used to distribute a first key, and the first key is a key for the second network element; Wherein, the first network element is a centralized unit (CU) in the access network device, and the second network element is a distributed unit (DU) in the access network device.

2. The method according to claim 1, wherein, The first key supports the security of communication between the second network element and the terminal.

3. The method according to claim 1 or 2, wherein, The first message includes at least one of the following: The first instruction information is used to instruct the terminal to deduce the first key; The first count value is the count value of the terminal moving across DU in the access network equipment; The first key.

4. The method according to claim 3, wherein, The first message includes a second message, which is used to trigger the terminal to perform a deduction of the first key; The first indication information and / or the first count value are included in the second message.

5. The method according to claim 4, wherein, The second message is a safe mode command message.

6. The method according to any one of claims 3 to 5, wherein, The first message includes the first key; The method further includes: The first key is determined based on the second key, wherein the second key is a key for the access network device and supports the security of communication between the access network device and the terminal.

7. The method according to any one of claims 1 to 6, wherein, The first message is a User Equipment (UE) Context Establishment Request message.

8. The method according to any one of claims 1 to 7, wherein, The method further includes at least one of the following: Receive a first confirmation message sent by the second network element, wherein the first confirmation message is used to confirm that the second network element uses the first key; The receiving terminal sends a second confirmation message, wherein the second confirmation message is used to confirm that the terminal uses the first key.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: Receive the second key sent by the third network element; Triggering a derivation of the first key based on the second key; The second key is a key specific to the access network device, and the second key supports the security of communication between the access network device and the terminal.

10. A communication method, executed by a second network element, wherein, The method includes: Receive a first message sent by a first network element, wherein the first message is used to distribute a first key, and the first key is a key for the second network element; Wherein, the first network element is a centralized unit (CU) in the access network device, and the second network element is a distributed unit (DU) in the access network device.

11. The method according to claim 10, wherein, The first key supports the security of communication between the second network element and the terminal.

12. The method according to claim 10 or 11, wherein, The first message includes at least one of the following: The first instruction information is used to instruct the terminal to deduce the first key; The first count value is the count value of the terminal moving across DU in the access network equipment; The first key.

13. The method according to claim 12, wherein, The first message includes the first indication information and / or the first count value; The method further includes: A second message is sent to the terminal, wherein the second message is used to trigger the terminal to perform a deduction of the first key, and the second message includes the first indication information and / or the first count value.

14. The method according to claim 12 or 13, wherein, The first message includes the second message.

15. The method according to claim 13 or 14, wherein, The second message is a safe mode command message.

16. The method according to claim 13, wherein, The method further includes: Receive the second confirmation message sent by the terminal; Send the second confirmation message to the first network element; The second confirmation message is used to confirm that the terminal uses the first key.

17. The method according to any one of claims 10 to 16, wherein, The method further includes: Based on the first key, security key derivation is performed for communication between the second network element and the terminal.

18. The method according to claim 17, wherein, The security key derivation for communication between the second network element and the terminal includes the Media Access Control (MAC) security key derivation. The step of performing security key derivation for communication between the second network element and the terminal based on the first key includes: Based on the first key, at least one of the following is determined: the connectivity association key CAK in the MAC security key derivation, and the connectivity key name CKN in the MAC security key derivation.

19. The method according to any one of claims 10 to 17, wherein, The method further includes: A first confirmation message is sent to the first network element, wherein the first confirmation message is used to confirm that the second network element uses the first key.

20. A communication method, executed by a terminal, wherein, The method includes: The terminal receives a second message sent by a second network element, wherein the second message is used to trigger the terminal to perform a deduction of the first key, and the first key is a key for the second network element; The second network element is the distribution unit (DU) in the access network device.

21. The method according to claim 20, wherein, The first key supports the security of communication between the second network element and the terminal.

22. The method according to claim 20 or 21, wherein, The second message includes at least one of the following: The first instruction information is used to instruct the terminal to deduce the first key; The first count value is the count value of the terminal's movement across DUs in the access network device.

23. The method according to any one of claims 20 to 22, wherein, The second message is a safe mode command message.

24. The method according to any one of claims 20 to 23, wherein, The method further includes: Based on the first indication information or the first count value in the second message, the derivation of the first key is triggered; The first key is determined based on the second key, wherein the second key is a key for the access network device and supports the security of communication between the access network device and the terminal.

25. The method according to claim 24, wherein, The method further includes: Based on the first key, the security key derivation for communication between the second network element and the terminal is determined.

26. The method of claim 25, wherein, The security key derivation for communication between the second network element and the terminal includes the Media Access Control (MAC) security key derivation. The step of determining the security key derivation for communication between the second network element and the terminal based on the first key includes: Based on the first key, at least one of the following is determined: the connectivity association key CAK in the MAC security key derivation, and the connectivity key name CKN in the MAC security key derivation.

27. The method according to any one of claims 20 to 26, wherein, The method further includes: A second confirmation message is sent to the second network element, wherein the second confirmation message is used to confirm that the terminal uses the first key.

28. A communication device, characterized in that, The communication device is used to perform the communication method as described in any one of claims 1 to 9, 10 to 19, and 20 to 27.

29. A communication system, characterized in that, The system includes a terminal, a first network element, and a second network element, wherein the terminal is configured to implement the communication method as described in any one of claims 1 to 9, the first network element is configured to implement the communication method as described in any one of claims 10 to 19, and the second network element is configured to implement the communication method as described in any one of claims 20 to 27.

30. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 9, 10 to 19, and 20 to 27.

31. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method as described in any one of claims 1 to 9, 10 to 19, and 20 to 27.

Images