Key management method and apparatus

Abstract

Disclosed in the embodiments of the present application are a key management method and apparatus. The method comprises: sending to a terminal device pre-configuration information of a plurality of candidate cells and first key information, wherein the first key information is used for deriving a key for communication between the terminal device and an access network device; and sending a first key to a second access network device to which a target cell to which the terminal device is switched belongs, wherein the first key is a key for communication between the terminal device and the second access network device, and the plurality of candidate cells comprise the target cell. The method can support subsequent switching and effectively manage keys.

Description

A method and device for key management

[0001] This application claims priority to the Chinese patent application with application number 202311288620.5 filed with the State Intellectual Property Office of China on September 28, 2023, and priority to the Chinese patent application with the invention name “A method and device for key management”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communication technologies, and in particular to a method and apparatus for key management. Background Art

[0003] In mobile communication systems, the movement of a terminal device can cause changes in the communication link between the terminal device and the access network device. For example, the access network device can instruct the terminal device to switch cells or access network devices based on the terminal device's movement. When an access network device switch occurs, the terminal device typically needs to change its key. This means that different keys are used for data encryption, integrity protection, and other processing when communicating with the source and target access network devices to ensure secure communication.

[0004] Currently, some handover methods can pre-configure multiple candidate cells for terminal devices to support subsequent handovers of the terminal device (i.e., multiple handovers between multiple candidate cells). However, the current handover methods that support subsequent handovers do not have an effective key management mechanism, making it difficult to ensure communication security.

[0005] Summary of the Invention

[0006] The embodiments of the present application disclose a method and apparatus for key management, which can support subsequent switching and effectively manage keys.

[0007] The present application is introduced below from different aspects. It should be understood that the implementation methods and beneficial effects of the following different aspects can be referenced to each other.

[0008] In the first aspect, the present application discloses a method for key management, which can be executed by a first access network device or a module (for example, a chip) in the first access network device. The method may include: sending pre-configuration information and first key information of multiple candidate cells to a terminal device; the first key information is used to deduce the key for communication between the terminal device and the access network device; sending the first key to the second access network device to which the target cell to which the terminal device switches belongs, the first key being the key for communication between the terminal device and the second access network device, and the multiple candidate cells including the target cell.

[0009] In an embodiment of the present application, the first access network device can send pre-configuration information of multiple candidate cells to the terminal device to support the terminal device in subsequent switching (i.e., switching once or multiple times among multiple candidate cells), and the terminal device does not need to perform the steps of obtaining pre-configuration information multiple times during subsequent cell switching. The first access network device sends the first key information used to deduce the key for this switching to the terminal device, which can ensure the key security of this switching. In this method, the first key information and the pre-configuration information are two independent parameters, which can support the terminal device to use other key information when using the above-mentioned pre-configuration information in subsequent switching after this switching (i.e., accessing the above-mentioned target cell), and can effectively manage the key to ensure communication security.

[0010] In combination with the first aspect, in a possible implementation, pre-configuration information of multiple candidate cells is used for a terminal device to perform one or more handovers among the multiple candidate cells.

[0011] In an embodiment of the present application, the first access network device can send pre-configuration information of multiple candidate cells to the terminal device to support the terminal device to switch once or multiple times among multiple candidate cells. The terminal device does not need to perform multiple steps to obtain pre-configuration information during subsequent cell switching.

[0012] With reference to the first aspect, in a possible implementation, the pre-configuration information does not include the first key information.

[0013] In an embodiment of the present application, the pre-configuration information does not include the first key information. Then, the terminal device can re-acquire the key information to align with the key of the access network device to be accessed when switching between multiple candidate cells. Different key information can also be used to avoid key duplication in subsequent switching processes. This method provides an effective key management mechanism to ensure communication security.

[0014] Exemplarily, the first key information may be a next hop chaining count (NCC), which is used to derive the first key; it may be a KgNB in ​​new radio NR (newradio) communication, where the UE and gNB utilize KgNB to further derive the key Kup used for user plane data and the key Krrc used for radio resource control (RRC) layer signaling. The UE and gNB use Kup to perform security processing such as encryption and integrity protection on user plane data, and the UE and gNB use Krrc to perform security processing such as encryption and integrity protection on RRC signaling. In an embodiment of the present application, the terminal device may use a different NCC in each subsequent handover. Since the KgNBs generated by different NCCs are different, the Kup and Krrc derived based on different KgNBs are also different. This method can avoid the problem of key reuse during subsequent handovers and ensure communication security.

[0015] With reference to the first aspect, in a possible implementation, the multiple candidate cells belong to one or more access network devices.

[0016] In the embodiment of the present application, multiple candidate cells may be managed by one or more access network devices to support terminal devices switching between different cells or different access network devices.

[0017] In conjunction with the first aspect, in a possible implementation, sending the first key to a second access network device to which a target cell to which the terminal device is handed over belongs includes:

[0018] After determining the target cell, the first key is sent to the second access network device.

[0019] In an embodiment of the present application, the target cell to which the terminal device switches can be determined by the serving base station of the terminal device (i.e., the first access network device), and the first access network device can send the first key used for this switch to the second access network device after determining the target cell. It should be understood that if key interaction is performed in the pre-configuration stage, it will lead to a strong binding relationship between the key and the pre-configuration, making the key difficult to change; and, since the target cell is not determined in the pre-configuration stage, if keys are sent to multiple candidate access network devices at this time, additional data transmission will be added, resulting in key insecurity. In this method, the first access network device does not send the first key to the second access network device when obtaining the pre-configuration information of the cell it manages from the second access network device (referred to as the pre-configuration stage), but sends the first key after determining the target cell. This can protect the key and support key changes during subsequent switching of the terminal device, thereby ensuring switching security.

[0020] In combination with the first aspect, in a possible implementation, the first key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling, or the first key information is carried by a switching command, which is used to indicate switching to a target cell.

[0021] In combination with the first aspect, in a possible implementation, before sending the first key to the second access network device to which the target cell to which the terminal device is switched belongs, the method further includes: receiving a first message sent by the terminal device, the first message being used to indicate switching to the target cell.

[0022] In an embodiment of the present application, the target cell to which the terminal device switches may be determined by the terminal device, and this switching may be triggered by the terminal device.

[0023] In combination with the first aspect, in a possible implementation, sending a first key to a second access network device to which a target cell to which a terminal device switches belongs includes: receiving a request message sent by the second access network device, the request message being used to request a key for communication between the terminal device and the second access network device; and sending the first key to the second access network device in response to the request message.

[0024] In an embodiment of the present application, the first access network device can send a first key to the second access network device in response to a request message sent by the second access network device. This method does not require notifying the second access network device of the first key after the terminal device communicates with the first access network device to determine the target cell, and can ensure that the terminal device successfully accesses the target cell when the wireless link between the terminal device and the first access network device fails.

[0025] In combination with the first aspect, in a possible implementation, the request message also includes an integrity message authentication code, and sending the first key to the second access network device includes: after the request message is verified based on the integrity message authentication code, sending the first key to the second access network device.

[0026] In the embodiment of the present application, the second access network device can be verified through an integrity message authentication code to ensure the security of the first key.

[0027] In combination with the first aspect, in a possible implementation, the method also includes: sending a switching request message to the second access network device, the switching request message is used to request the pre-configuration information of the cell corresponding to the second access network device; receiving a response message sent by the second access network device, the response message includes the pre-configuration message of the target cell.

[0028] In the second aspect, the present application discloses a method for key management, which can be executed by a terminal device or a module (for example, a chip) in the terminal device, and the method may include: receiving pre-configuration information and first key information of multiple candidate cells; the first key information is used to deduce the key for communication between the terminal device and the access network device; after receiving the switching command, deducing based on the first key information to obtain the first key corresponding to the first cell; the switching command is used to indicate switching to the first cell, the first cell belongs to the second access network device, and the first key is the key for communication between the terminal device and the second access network device.

[0029] In an embodiment of the present application, a terminal device can receive pre-configuration information of multiple candidate cells to support the terminal device in performing subsequent handovers (i.e., performing one or more handovers among multiple candidate cells) after the current handover (i.e., switching to the above-mentioned first cell). The terminal device does not need to perform the step of obtaining the pre-configuration information multiple times during subsequent cell handovers. In this method, the first key information and the pre-configuration information are two independent parameters, which can support the terminal device to use other key information when using the above-mentioned pre-configuration information in subsequent handovers, and can effectively manage the key to ensure communication security.

[0030] In combination with the second aspect, in a possible implementation, pre-configuration information of multiple candidate cells is used for a terminal device to perform one or more handovers among the multiple candidate cells.

[0031] In combination with the second aspect, in a possible implementation, the pre-configuration information does not include the first key information.

[0032] In combination with the second aspect, in a possible implementation, the first key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling, or the first key information is carried by a handover command.

[0033] In combination with the second aspect, in a possible implementation, the multiple candidate cells belong to one or more access network devices.

[0034] In conjunction with the second aspect, in one possible implementation, the method further includes:

[0035] When it is determined that the handover of the first cell fails or the radio link fails, determining a second cell from a plurality of candidate cells, where the second cell belongs to a third access network device;

[0036] A second message is sent to the third access network device, where the second message is used to request access to the second cell.

[0037] In an embodiment of the present application, upon determining a handover failure or radio link failure, a terminal device can determine a second cell from multiple candidate cells and initiate access to a third access network device corresponding to the second cell. This method can ensure that the terminal device successfully accesses another cell when a handover failure or radio link failure occurs.

[0038] In combination with the second aspect, in a possible implementation, the second message further includes an integrity message authentication code and / or an identifier of the terminal device.

[0039] In a third aspect, the present application discloses a method for key management, which can be executed by a terminal device or a module (for example, a chip) in the terminal device, and the method may include: receiving pre-configuration information and first key information of multiple candidate cells; sending a first message to a first access network device, the first message being used to indicate switching to the first cell; the first cell belongs to a second access network device; multiple candidate cells include the first cell; deducing based on the first key information to obtain a first key corresponding to the first cell; the first key is a key for communication between the terminal device and the second access network device; receiving second key information from the second access network device; sending a second message to the second access network device, the second message being used to indicate switching to the second cell; the second cell belongs to a third access network device; multiple candidate cells include the second cell; deducing based on the second key information to obtain a second key corresponding to the second cell; the second key is a key for communication between the terminal device and the third access network device.

[0040] In an embodiment of the present application, the terminal device re-acquires key information to deduce different keys each time the cell is switched, such as deducing the first key corresponding to the first cell through the first key information, and deducing the second key corresponding to the second cell through the second key information. This method can avoid the situation where the terminal device switches multiple times between multiple candidate cells and repeats the key, thereby ensuring key security.

[0041] In combination with the third aspect, in a possible implementation, the method further includes: determining the first cell and / or the second cell from the multiple candidate cells based on pre-configuration information of the multiple candidate cells.

[0042] In combination with the third aspect, in a possible implementation, the multiple candidate cells belong to one or more access network devices.

[0043] In combination with the third aspect, in a possible implementation manner, the first key information and / or the second key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling.

[0044] In combination with the third aspect, in a possible implementation, the method also includes: when it is determined that switching the second cell fails or the wireless link fails, determining a third cell from multiple candidate cells, the third cell belongs to a fourth access network device; sending a third message to the fourth access network device, the third message is used to request access to the third cell.

[0045] In combination with the third aspect, in a possible implementation, the third message further includes an integrity message authentication code and / or an identifier of the terminal device.

[0046] In a fourth aspect, the present application provides a communication device, which may be a first device or a chip / circuit therein. The communication device is configured to perform the method of the first aspect or any possible implementation of the first aspect. The communication device includes a unit capable of performing the method of the first aspect or any possible implementation of the first aspect.

[0047] In a fifth aspect, the present application provides a communication device, which may be a second device or a chip / circuit therein. The communication device is configured to perform the method of the second aspect, the third aspect, or any possible implementation thereof. The communication device includes a unit having a function of performing the method of the second aspect, the third aspect, or any possible implementation thereof.

[0048] In the fourth or fifth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments shown below. The beneficial effects of the fourth to fifth aspects may be described with reference to the relevant descriptions of the first to third aspects, and are not further elaborated here.

[0049] In a sixth aspect, the present application discloses a method for key management, which can be executed by a first access network device or a module (for example, a chip) in the first access network device. The method may include: deducing based on the initial key of the first access network device to obtain a first key corresponding to the first access network device; the first key is a key for communication between the terminal device and the first access network device; sending first key information to the terminal device; the first key information is used to deduce a second key for communication between the terminal device and the second access network device; deducing based on the second key information of the first access network device to obtain a third key corresponding to the first access network device; the third key is a key for communication between the terminal device and the first access network device; the first key is different from the second key.

[0050] In the embodiment of the present application, the first access network device can independently derive the key for communication with the terminal device, and use different key information to derive a different key each time the terminal device accesses. This method can avoid the problem of key reuse and ensure communication security.

[0051] In conjunction with the sixth aspect, in one possible implementation, the terminal device stores pre-configured information for multiple candidate cells. The method can support subsequent handover of the terminal device. Exemplarily, the terminal device can store pre-configured information for cells managed by the first access network device and the second access network device.

[0052] In combination with the sixth aspect, in a possible implementation, the first access network device may deduce the first key or the third key after receiving an access request from the terminal device.

[0053] In combination with the sixth aspect, in a possible implementation, the method also includes: sending a path switching request to the core network; receiving a response message from the core network, the response message including first key information and second key information, the first key information and the second key information corresponding to the first access network device, the first key information is used to deduce the key when the terminal device accesses the first access network device, and the second key information is used to deduce the key from the first access network device.

[0054] In the seventh aspect, the present application discloses a method for key management, which may include: deducing based on the initial key of the first access network device to obtain a first key corresponding to the first access network device; the first key is the key for communication between the terminal device and the first access network device; receiving first key information sent by the first access network device; the first key information is used to deduce a second key for communication between the terminal device and the second access network device; deducing based on the second key information to obtain a third key corresponding to the first access network device; the third key is the key for communication between the terminal device and the first access network device; the first key is different from the second key.

[0055] In the embodiment of the present application, the first access network device can independently derive the key for communication with the terminal device, and use different key information to derive a different key each time the terminal device accesses. This method can avoid the problem of key reuse and ensure communication security.

[0056] In conjunction with the seventh aspect, in one possible implementation, the terminal device stores pre-configured information for multiple candidate cells. The method can support subsequent handover of the terminal device. Exemplarily, the terminal device can store pre-configured information for cells managed by the first access network device and the second access network device.

[0057] In conjunction with the seventh aspect, in one possible implementation, the terminal device may obtain pre-configured information of cells managed by the first access network device and the second access network device from a source cell; and derive the first key upon receiving a handover command sent by the source cell or determining a target cell for handover. The handover command is used to instruct handover to the cell managed by the first access network device; and the target cell is a cell managed by the first access network device.

[0058] In an eighth aspect, the present application provides a communication device, which may be the sixth device or a chip / circuit therein. The communication device is configured to perform the method of the sixth aspect or any possible implementation of the sixth aspect. The communication device includes a unit configured to perform the method of the sixth aspect or any possible implementation of the sixth aspect.

[0059] In a ninth aspect, the present application provides a communication device, which may be the seventh device or a chip / circuit therein. The communication device is configured to perform the method of the seventh aspect or any possible implementation of the seventh aspect. The communication device includes a unit configured to perform the method of the seventh aspect or any possible implementation of the seventh aspect.

[0060] In the eighth or ninth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments shown below. The beneficial effects of the eighth to ninth aspects may be described with reference to the relevant descriptions of the sixth to seventh aspects, and are not repeated here.

[0061] In a tenth aspect, the present application provides a communication device, which may include a processor and an interface circuit, and the processor is connected to the interface circuit. Wherein, the interface circuit is used to interact (or receive and send or input and output) information or data, and the processor is used to run program instructions so that the communication device executes the method described in any possible implementation of the first aspect, or the second aspect, or the third aspect, or the sixth aspect, or the seventh aspect, or any of the aspects above. Wherein, the interface circuit may be a communication interface, or a transceiver. The transceiver may be a radio frequency module in a communication device, or a combination of a radio frequency module and an antenna, or an input and output interface of a chip or circuit.

[0062] In the eleventh aspect, the present application provides a readable storage medium having program instructions stored thereon, which, when executed on a computer, enables the computer to execute the method described in any possible implementation of the first aspect, the second aspect, the third aspect, the sixth aspect, the seventh aspect, or any one of them.

[0063] In the twelfth aspect, the present application provides a program product comprising program instructions, which, when executed, enables the method described in any possible implementation of the first aspect, or the second aspect, or the third aspect, or the sixth aspect, or the seventh aspect, or any one of them to be executed.

[0064] In a thirteenth aspect, the present application provides a device, which can be implemented in the form of a chip or in the form of a device, and the device includes a processor. The processor is used to read and execute a program stored in a memory to execute one or more of the above-mentioned first aspect, or the above-mentioned second aspect, or the above-mentioned third aspect, or the above-mentioned sixth aspect, or the above-mentioned seventh aspect, or the information interaction method provided by one or more of any possible implementation methods of any aspect thereof. Optionally, the device also includes a memory, which is connected to the processor via a circuit. Further optionally, the device also includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive information to be processed, and the processor obtains the information from the communication interface, processes the information, and outputs the processing results through the communication interface. The communication interface can be an input and output interface.

[0065] In a possible implementation, the processor and memory may be physically independent units, or the memory may be integrated with the processor.

[0066] In the fourteenth aspect, the present application provides a communication system, which includes a first access network device and a terminal device; the first access network device is used to execute the method described in the first aspect, the sixth aspect or any possible implementation of any aspect therein, and the terminal device is used to execute the method described in the second aspect, the third aspect, the seventh aspect or any possible implementation of any aspect therein.

[0067] The technical effects achieved in the above-mentioned aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] FIG1A is a schematic diagram of a switching scenario provided by an embodiment of the present application;

[0069] FIG1B is a schematic flow chart of a switching method provided in an embodiment of the present application;

[0070] FIG2 is a schematic flow chart of a switching method provided in an embodiment of the present application;

[0071] FIG3 is a schematic diagram of a network architecture of a communication system provided in an embodiment of the present application;

[0072] FIG4 is a flow chart of a key management method provided in an embodiment of the present application;

[0073] FIG5 is a flow chart of another key management method provided in an embodiment of the present application;

[0074] FIG6 is a flow chart of another key management method provided in an embodiment of the present application;

[0075] FIG7 is a flow chart of another key management method provided in an embodiment of the present application;

[0076] FIG8 is a flow chart of another key management method provided in an embodiment of the present application;

[0077] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0078] FIG10 is another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0079] FIG11 is another structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0080] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0081] In the description of this application, words such as "first" and "second" are only used to distinguish different objects, and do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different. For example, the first information and the second information, the first PDC type and the second PDC type, etc. are only used to distinguish different information, and do not limit their order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.

[0082] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one (item)", "the following one (item) or more (items)" or similar expressions refer to any combination of these items, including any combination of single or plural items (items). For example, at least one item (item) of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a, b, and c. Among them, a, b, and c can be single or multiple.

[0083] In the description of this application, words such as "exemplary" or "for example" are used to indicate an example, illustration, or description. Any embodiment or design described in this application as "exemplary," "for example," or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete way.

[0084] It should be understood that in the description of this application, the terms "when," "if," and "if" all refer to the device performing a corresponding action under certain objective circumstances. They do not limit the time, do not require the device to perform a judgment action during implementation, and do not imply any other limitations. Specifically, "the device performing a corresponding action under certain objective circumstances" includes: the device performing the corresponding action under certain objective circumstances can perform the corresponding action only if the objective circumstances are met; or the device performing the corresponding action can perform the corresponding action only if the objective circumstances and other circumstances are met.

[0085] The term "simultaneously" in this application may be understood as at the same time point, within a period of time, or within the same cycle, and may be understood in conjunction with the context.

[0086] Elements used in the singular herein are intended to mean "one or more" rather than "one and only one" unless specifically stated otherwise.

[0087] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0088] It should be understood that in the various embodiments of the present application, "A corresponds to B," "A corresponds to B," "A corresponds to B," or similar expressions indicate that B is associated with A and B can be determined based on A. Determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.

[0089] Currently, handover technologies such as Layer 3 Handover and Conditional Handover only target the handover process of a single cell handover. This means that each handover requires executing the handover request and handover request response process between the source and target base stations. For ease of description, this embodiment of the present application refers to this handover technology as a one-time handover technology.

[0090] The following describes the one-time handover technology using L3 Handover as an example.

[0091] FIG1A is a schematic diagram of a switching scenario exemplarily provided in an embodiment of the present application.

[0092] As shown in Figure 1A, the user equipment (UE) initially serves Cell 1 (and gNB 1), using Key 1 for encrypted communication with the serving cell / gNB. As the UE moves, it switches to Cell 2 / gNB 2, where it uses Key 2 for communication. Because L3 handover is a one-time process, this handover is considered complete. The UE then moves to Cell 1 / gNB 1 and repeats the above process, switching to Key 3 for encrypted communication with Cell 1 / gNB 1. The detailed process for these two handovers can be seen in Figure 1B. The above keys Key1, Key2, and Key3 can be KgNB in ​​new radio NR (new radio) communication. The UE and gNB use KgNB to further derive the key Kup used for user plane data and the key Krrc used for radio resource control (RRC) layer signaling. The UE and gNB use Kup to perform security processing such as encryption and integrity protection of user plane data, and use Krrc to perform security processing such as encryption and integrity protection of RRC signaling.

[0093] FIG1B is a flow chart of a switching method provided by the present application. The method may include some or all of the following steps:

[0094] S101: UE communicates with gNB1 based on Key1.

[0095] It should be understood that the UE's serving cell in this handover is Cell1, which is managed by gNB1. Therefore, gNB1 is also referred to as the serving gNB. The UE can use Key1 for encryption and integrity protection of communication data and signaling. Optionally, when encrypting data and signaling, the UE may use Key1 as a parameter to further generate a user plane processing key Kup and an RRC layer processing key Krrc. Kup is used for encryption and integrity protection of user plane data, while Krrc is used for encryption and integrity protection of RRC signaling. Similarly, gNB1 can also use Key1 as a parameter to further generate a user plane processing key Kup and a radio resource control layer processing key Krrc. Kup is used for encryption and integrity protection of user plane data, while Krrc is used for encryption and integrity protection of RRC signaling.

[0096] S102: gNB1 derives the key Key2 of the target cell / target gNB.

[0097] In this handover, gNB1 can be called the source gNB, Cell1 can be called the source cell; gNB2 can be called the target gNB, and Cell2 can be called the target cell.

[0098] S103: gNB1 sends a handover request message to gNB2, which includes Key2 and NCC2.

[0099] NCC2 is a next hop chaining count (NCC) provided by the access and mobility management function (AMF) to gNB1 for the UE to derive Key2. Key2 is the key used by the UE when communicating with Cell2 / gNB2.

[0100] S104: gNB2 sends a handover request response message to gNB1, which includes the configuration information of the target cell (i.e., Cell2) and NCC2.

[0101] S105: gNB1 sends a handover command to the UE, which includes the configuration information of the target cell (i.e., Cell2) and NCC2.

[0102] S106: The UE performs handover according to the handover command and uses NCC2 to perform key derivation to obtain Key2.

[0103] It should be understood that when the UE performs encryption processing on data and signaling, it can use Key2 as a parameter to further generate a user plane processing key Kup and an RRC layer processing key Krrc.

[0104] S107: UE accesses Cell2 / gNB2.

[0105] S108: gNB2 sends a path switch request message to the AMF to request the core network to switch the downlink path between the user plane function network element and the base station for the UE from gNB1 to gNB2.

[0106] S109: The AMF sends a path switch request response message to gNB2 to respond to whether the path switch is successful or not.

[0107] Furthermore, the response message includes NH and NCC3. NH is the next hop parameter, which is used by gNB2 to derive Key3 during the next handover; NCC3 is used by the UE to derive Key3 during the next handover.

[0108] Through S101 to S109, the UE completes a handover from Cell 1 / gNB 1 to Cell 2 / gNB 2 (referred to as the first handover). For subsequent handovers, the UE, source cell / source gNB, and target cell / target gNB must follow the same process as for the first handover. The following example illustrates the next handover. For example, if the next handover is from Cell 2 / gNB 2 to Cell 1 / gNB 1, Cell 2 / gNB 2 is referred to as the source cell / source gNB, and Cell 1 / gNB 1 is referred to as the target cell / target gNB. The specific process of the next handover is described in S110 to S117.

[0109] S110: gNB2 derives Key3.

[0110] The derivation process of step S110 is similar to that of step S102. Specifically, gNB2 uses the cell identity information of NH and Cell1 obtained in step S109 to derive Key3.

[0111] S111: gNB1 sends a handover request message to gNB2, which includes Key3 and NCC3.

[0112] The specific implementation of step S111 is similar to that of step S103.

[0113] S112: gNB2 sends a handover request response message to gNB1, which includes the configuration information of the target cell (i.e., Cell1) and NCC3.

[0114] The specific implementation of step S112 is similar to that of step S104.

[0115] S113: gNB1 sends a handover command to the UE, which includes the configuration information of the target cell Cell1 and NCC3.

[0116] The specific implementation of step S113 is similar to that of step S105.

[0117] S114: The UE performs handover according to the handover command and uses NCC3 to perform key derivation to obtain Key3.

[0118] The specific implementation of step S114 is similar to that of step S106.

[0119] S115: UE accesses Cell1 / gNB1.

[0120] The specific implementation of step S115 is similar to that of step S107.

[0121] Steps S116 and S117 are similar to steps S108 and S109, but are not shown in FIG1B.

[0122] Through S110 to S117: the UE completes a switching process from Cell2 / gNB2 to Cell1 / gNB1.

[0123] It can be seen that the above-mentioned one-time handover technology requires the handover preparation process to be repeated for the next handover (for example, the handover request and handover request response in steps S103 and S104 in Figure 1B), and the keys used by the UE and the target cell are aligned through the handover preparation process and the handover command. The above-mentioned method does not support subsequent handovers of the terminal device.

[0124] The following exemplifies a handover method supporting subsequent handover by taking Figure 2 as an example. Supporting subsequent handover means pre-configuring multiple candidate cells for a terminal device to support multiple handovers of the terminal device between the multiple candidate cells.

[0125] Please refer to Figure 2, which is a flowchart of a switching method provided by this application. The method may include some or all of the following steps:

[0126] S201: UE communicates with gNB1 based on Key1.

[0127] For example, the source cell is Cell1 and the source gNB is gNB1.

[0128] S202: gNB1 sends a handover request message to the candidate gNB. The handover request message is used to request the L1 / L2 triggered mobility management (LTM) pre-configuration information of the candidate cell. The handover request message includes the key corresponding to the candidate gNB (such as Key2 corresponding to gNB2 or Key3 corresponding to gNB3) and the NCC used by the UE for the next handover (i.e., NCC2).

[0129] For example, FIG2 shows that the candidate gNBs include gNB2 and gNB3. gNB1 may send a handover request message including Key2 and NCC2 to gNB2; gNB1 may send a handover request message including Key3 and NCC2 to gNB3.

[0130] It should be understood that gNB1 only obtains a pair of {NH, NCC} from the core network, so the NCC that gNB1 gives to gNB2 and gNB3 is the same, both are NCC2. NCC2 is the key information used by the UE for the next handover, and NCC2 corresponds to NH2.

[0131] S203: The candidate gNB sends a handover request response message to gNB1. The handover request response message is used to provide pre-configuration information of the candidate cell. The handover request response message includes the NCC2 used by the UE for the next handover.

[0132] S204: gNB1 sends pre-configuration information of candidate cells to the UE, where the pre-configuration information includes NCC2.

[0133] S205: gNB1 sends a handover command to the UE, where the handover command is used to instruct the UE to switch to Cell2, which is managed by gNB2.

[0134] This handover is explained using the example of the target cell being Cell2 and the target base station being gNB2.

[0135] The switching command includes identification information corresponding to Cell2.

[0136] S206: gNB1 sends a notification message to gNB2, which is used to instruct the UE to access.

[0137] S207: The UE derives the key Key2 of Cell2 based on NCC2.

[0138] S208: The UE accesses Cell 2.

[0139] S209: gNB2 sends a path switch request message to the AMF to request the core network to switch the downlink path between the user plane function network element and the base station for the UE from gNB1 to gNB2.

[0140] S210: The AMF sends a path switch request response message to gNB2 to respond to whether the path switch is successful or not.

[0141] Through S201 to S210, the UE completes a handover process from Cell1 / gNB1 to Cell2 / gNB2 (referred to as the first handover). For subsequent handovers, the UE, source cell / source gNB, and target cell / target gNB do not need to follow the same process as the first handover. The following example illustrates the next handover, for example, if the next handover (referred to as the second handover) is from Cell2 / gNB2 to Cell3 / gNB3, Cell2 / gNB2 is referred to as the source cell / source gNB, and Cell3 / gNB3 is referred to as the target cell / target gNB. The specific process is described in S211 to S214 below.

[0142] S211: gNB2 sends a handover command to the UE, where the handover command is used to instruct the UE to switch to Cell3, which is managed by gNB3.

[0143] S212: gNB2 sends a notification message to the target gNB (i.e., gNB3), which is used to instruct the UE to access.

[0144] S213: The UE derives the key of the target cell based on NCC2 and obtains Key4.

[0145] S214: The UE accesses the target cell (ie, Cell3).

[0146] In step S202, gNB3 obtains Key3, which is derived by gNB1 based on Key1. In step S213, the UE derives Key4 based on Key1 and NCC2. Key3 and Key4 differ (i.e., the keys for the second handover are misaligned). Therefore, the method shown in Figure 2 can lead to key misalignment during subsequent handovers to other candidate gNBs. Furthermore, if the UE successfully hands over to another cell and then switches back to Cell1, gNB1 will still use Key1, leading to key reuse.

[0147] It can be seen that the above-mentioned switching method that supports subsequent switching does not have an effective key management mechanism and is difficult to ensure communication security.

[0148] In view of this, an embodiment of the present application provides a key management method and related devices. In this method, the UE re-acquires key information each time a switch is made, ensuring that the key for each switch is different. This can ensure key alignment between the terminal device and the target access network device and that the key is not reused in subsequent switches, providing an effective key management mechanism to ensure communication security.

[0149] Based on the above, in order to better understand the key management method and related devices proposed in this application, the network architecture applied in the embodiment of this application is described below.

[0150] Please refer to Figure 3, which is a schematic diagram of the network architecture of a communication system provided in an embodiment of the present application.

[0151] As shown in Figure 3, the network architecture may include a first access network device 101, a second access network device 102, and a terminal device 103. It should be understood that Figure 3 only exemplifies two access network devices, and the network architecture may also include other access network devices. The embodiment of the present application does not limit the number of access network devices.

[0152] Among them, the terminal device 103 can switch in the cell of the first access network device 101 or the second access network device 102 based on the key management method provided in the embodiment of the present application.

[0153] The terminal device 103 can be connected to the first access network device 101 or the second access network device 102 in a wireless manner, and can be accessed to the core network through the first access network device 101 or the second access network device 102. The terminal device 103 can be fixed or mobile.

[0154] The first access network device 101 and the second access network device 102 can be entities for transmitting or receiving signals, and can be devices for communicating with the terminal device 103. The network device can be a base transceiver station (BTS) in a global system for mobile communications (GSM) system or a code division multiple access (CDMA) system, or a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolved NodeB (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device can be a relay station, an access point, an in-vehicle device, a wearable device, a network device in a 5G network, or a network device in a future evolved PLMN network, etc., and the embodiment of the present application is not limited. The network device can be a device in a wireless network, such as a radio access network (RAN) node that connects the terminal device 103 to the wireless network. Currently, some examples of RAN nodes include base stations, next-generation base stations (gNBs), transmission reception points (TRPs), evolved Node Bs (eNBs), home base stations, baseband units (BBUs), or access points (APs) in Wi-Fi systems. In one network architecture, network equipment may include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN equipment including CU nodes and DU nodes. In an O-RAN system, the CU may also be referred to as an O-CU, and the DU may also be referred to as an O-DU.

[0155] The terminal device 103 is an entity on the user side for receiving or transmitting signals, and is mainly used to realize the function of wireless communication with the first access network device 101.

[0156] For example, terminal device 103 can be an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The terminal device 103 may also be a mobile phone, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), a terminal device in a 5G network, or a future-evolved public land mobile communication network. The terminal device 103 may be a terminal device in a wireless network (PLMN), etc., and the embodiments of the present application do not limit this. The terminal device 103 may be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted, or may be deployed on water (such as ships, etc.), or may be deployed in the air (such as airplanes, balloons and satellites, etc.). In the embodiments of the present application, the terminal device 103 may be a legacy UE, or may be an RB-level partial frequency hopping (RPFS) UE that supports SRS coverage and capacity enhancement, or may be other UEs. The present application does not limit the type of the terminal device 103. Among them, legacy UE refers to user equipment that supports existing mechanisms, for example, user equipment that supports release-15 and release-16.

[0157] In an embodiment of the present application, any one of the first access network device 101, the second access network device 102, and the terminal device 103 may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system can be any one or more computer operating systems that implement service processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as a browser, an address book, word processing software, and instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application. As long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application, for example, the execution subject of the method provided in the embodiments of the present application can be any one of the first access network device 101, the second access network device 102 and the terminal device 103, or it can be a functional module in any one of the first access network device 101, the second access network device 102 and the terminal device 103 that can call and execute the program.

[0158] It should be noted that the number and type of terminal devices 103 included in the network architecture shown in FIG3 are merely examples, and embodiments of the present application are not limited thereto. For example, more or fewer terminal devices 103 communicating with access network devices may be included. For the sake of simplicity, they are not described one by one in the accompanying drawings.

[0159] In addition, in the network architecture shown in Figure 3, although any one of the first access network device 101, the second access network device 102 and the terminal device 103 is shown, the application scenario may not be limited to including any one of the first access network device 101, the second access network device 102 and the terminal device 103. For example, it may also include a core network device or a device for carrying virtualized network functions, etc., wherein the core network device communicates with the terminal device 103 through the first access network device 101.

[0160] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR) and future communication systems, etc., without limitation here.

[0161] In combination with the above network architecture, a key management method provided in an embodiment of the present application is described below.

[0162] Please refer to Figure 4, which is a flow chart of a key management method provided in an embodiment of the present application. The functions performed by the terminal device in this embodiment can also be performed by a module (e.g., a chip) in the terminal device. The functions performed by the access network device in this application can also be performed by a module (e.g., a chip) in the access network device. For example, the functions performed by the first access network device in this application can also be performed by a module (e.g., a chip) in the first access network device.

[0163] As shown in FIG4 , the key management method may include the following steps:

[0164] Step S401: The first access network device sends pre-configuration information and first key information of multiple candidate cells to the terminal device.

[0165] Correspondingly, the terminal device receives pre-configuration information and first key information of multiple candidate cells from the first access network device.

[0166] Optionally, the pre-configuration information of the multiple candidate cells is used for the terminal device to perform one or more handovers among the multiple candidate cells. Exemplarily, the pre-configuration information of the candidate cells may include physical channel configuration information, reference signal configuration information, etc. of the candidate cells.

[0167] Optionally, the preconfiguration information does not include the first key information. Exemplarily, the first key information may be a next hop chaining count (NCC).

[0168] Optionally, the pre-configuration information of the multiple candidate cells may include pre-configuration information of the cell managed by the first access network device.

[0169] Optionally, the first key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling. Exemplarily, the L3 signaling may be an RRC message, the L2 signaling may be a Media Access Control Control Element (MAC CE), and the L1 signaling may be downlink control information (DCI). Alternatively, the first key information is carried by a handover command, which is used to indicate handover to a target cell. For example, in LTM, the first access network device may send a handover command to the terminal device after determining the target cell to which the terminal device is to handover, the handover command being used to indicate handover to the target cell, and the handover command may include the above-mentioned first key information.

[0170] It should be understood that the cell corresponding to the pre-configuration information obtained by the first access network device can be called a candidate cell. If the candidate cell is determined to be the cell to which the terminal device is about to switch, the candidate cell can be called a target cell.

[0171] Optionally, the multiple candidate cells belong to one or more access network devices, or in other words, the multiple candidate cells are managed by one or more access network devices.

[0172] In one implementation, before executing step S401, the first access network device may obtain pre-configuration information of candidate cells from one or more candidate access network devices to obtain pre-configuration information of the plurality of candidate cells. For example, the first access network device may obtain pre-configuration information of candidate cells as described in steps S502 and S503 of the embodiments below.

[0173] For example, if the candidate access network device includes a second access network device, the first access network device may send a handover request message to the second access network device, the handover request message being used to request pre-configuration information of cells managed by the second access network device, where the cells managed by the second access network device include a target cell; and receive a response message from the second access network device, the response message including pre-configuration information of the target cell. The handover request message does not include the first key information and the first key, and the response message does not include the first key information.

[0174] It should be understood that the embodiments of the present application can be applicable to switching technologies triggered by terminal devices (such as CHO) and switching technologies triggered by access network devices (such as LTM). Optionally, the specific content of the pre-configuration information can be related to the switching technology adopted. For example, the pre-configuration information can be L1 / L2 triggered mobility management (L1 / L2 Triggered Mobility, LTM) pre-configuration information, or conditional handover (CHO) pre-configuration information. The embodiments of the present application do not limit the switching technology adopted and the specific content of the pre-configuration information.

[0175] Step S402: The first access network device sends a first key to the second access network device to which the target cell to which the terminal device switches belongs. The first key is a key for communication between the terminal device and the second access network device. The multiple candidate cells include the target cell.

[0176] Correspondingly, the second access network device receives the first key from the first access network device. Exemplarily, in the NR communication system, the first key may be KgNB, which may be used to further derive Kup and Krrc.

[0177] In one implementation, after determining the target cell, the first access network device may send the first key to the second access network device. For example, the first access network device may send a notification message to the second access network device, the notification message being used to indicate that the terminal device will access the cell, and the notification message may carry the first key.

[0178] In another implementation, a first access network device may receive a first message sent by a terminal device, the first message being used to indicate a handover to a target cell, where the target cell belongs to a second access network device. Furthermore, the first access network device may send a first key to the second access network device. For example, the first access network device may send a notification message to the second access network device, the notification message carrying the first key.

[0179] Optionally, the notification message does not carry the first key information.

[0180] In another implementation, the first access network device may receive a request message sent by the second access network device, where the request message is used to request a key for communication between the terminal device and the second access network device; and in response to the request message, send the first key to the second access network device.

[0181] Optionally, the request message further includes an integrity message authentication code; the first access network device may send the first key to the second access network device after successfully verifying the request message based on the integrity message authentication code.

[0182] For example, upon determining a handover failure or radio link failure, the terminal device may determine a target cell from multiple candidate cells, where the target cell belongs to a second access network device. The terminal device may then send a second message to the second access network device, requesting access to the target cell. The second access network device may then send the second message to the first access network device to obtain the first key. After accessing the target cell, the terminal device may communicate with the target cell based on the first key. Optionally, the second message also includes an integrity message authentication code and / or a terminal device identifier.

[0183] Step S403: The terminal device deduce the first key based on the first key information to obtain the first key corresponding to the target cell.

[0184] In some embodiments, the terminal device may derive the first key based on the first key information and the cell information of the target cell (such as downlink frequency information, etc.), and then access the target cell and communicate with the target cell based on the first key.

[0185] In other embodiments of the present application, when the terminal device fails to switch to the above-mentioned target cell or the wireless link fails, it can determine a second cell from multiple candidate cells; assuming that the second cell belongs to a third access network device, the terminal device can send a third message to the third access network device, and the third message is used to request access to the second cell; the third access network device can send the above-mentioned third message to the first access network device to obtain a second key. The terminal device can deduce the second key based on the first key information and the cell information of the second cell; further, after accessing the second cell, the terminal device can communicate with the second cell based on the second key. Optionally, the third message also includes an integrity message authentication code and / or an identifier of the terminal device.

[0186] It should be understood that the embodiments of the present application do not limit the method for key deduction of access network devices and terminal devices. For examples, please refer to the relevant description below.

[0187] The method embodiment shown in Figure 4 above includes many possible implementation schemes. Some of the implementation schemes are illustrated below in conjunction with Figures 5 to 8. It should be noted that the relevant concepts, operations or logical relationships not explained in Figures 5 to 8 can refer to the corresponding descriptions in the embodiment shown in Figure 4.

[0188] The method embodiment shown in Figure 4 is applicable to handover technology triggered by an access network device, i.e., the access network device sends a handover command to the terminal device, triggering the access network device to perform a handover. For example, in LTM handover technology, the terminal device can first obtain LTM pre-configured information for multiple candidate cells. The terminal device then measures and reports the reference signals of the candidate cells, and the access network device issues a handover command, instructing the terminal device to switch to a specific candidate cell. The specific process can be seen in the embodiment shown in Figure 5.

[0189] FIG5 is a flow chart of another key management method provided in an embodiment of the present application.

[0190] Among them, the key management method provided in the embodiment of this application is introduced in detail by taking the terminal device as UE, the source access network device of the terminal device (that is, the above-mentioned first access network device) as gNB1, the target access network device for the terminal device switching (that is, the above-mentioned second access network device) as gNB2, and the core network device as AMF as an example.

[0191] As shown in FIG5 , the key management method may include some or all of the following steps:

[0192] S501: UE communicates with gNB1 based on Key1.

[0193] For example, the UE's serving cell (or source cell) is Cell1, which is managed by gNB1. Therefore, gNB1 can also be referred to as the serving gNB or source gNB. The UE can use Key1 to encrypt and perform integrity protection on communication data and signaling. It should be understood that when encrypting data and signaling, the UE can use Key1 as a parameter to further generate the user plane processing key Kup and the RRC layer processing key Krrc.

[0194] S502: gNB1 sends a handover request message to candidate gNBs (such as gNB2 and gNB3), which is used to request LTM pre-configuration information.

[0195] Figure 5 uses gNB2 and gNB3 as candidate gNBs and gNB1 as the source gNB for illustration. As shown in Figure 5, gNB1 can send a handover request message to gNB2 and gNB3, respectively, requesting LTM pre-configuration information for the candidate cells.

[0196] It should be understood that, unlike the method shown in FIG. 2 , in the embodiment of the present application, the message does not need to carry the key to be used when the candidate cell / target cell communicates with the UE, nor does it need to carry the corresponding NCC.

[0197] In an embodiment of the present application, when a candidate cell is determined to be a cell to which a terminal device is to switch, the candidate cell may be referred to as a target cell, and the candidate gNB that manages the target cell may be referred to as a target gNB.

[0198] S503: The candidate gNB sends a handover request response message to gNB1, carrying the LTM pre-configuration information.

[0199] As shown in Figure 5, gNB2 and gNB3 can respectively send a handover request response message to gNB1, which can carry the LTM pre-configuration information of the cells managed by the gNB (i.e., multiple candidate cells).

[0200] Exemplarily, the message may carry LTM pre-configuration information for cells managed by gNB2 and gNB3. That is, the multiple candidate cells include cells managed by gNB2 and gNB3.

[0201] Optionally, the message may also carry LTM pre-configuration information of cells managed by gNB1 (i.e., multiple candidate cells). That is, the multiple candidate cells include the cells managed by gNB1.

[0202] It should be understood that the embodiment of the present application is different from FIG. 2 in that the handover request response message in step S503 of the embodiment of the present application does not need to carry the NCC.

[0203] S504: gNB1 sends LTM pre-configuration information to the UE.

[0204] For example, gNB1 may send LTM pre-configuration information of cells managed by gNB2 and gNB3 to the UE.

[0205] It should be understood that the embodiment of the present application is different from FIG. 2 in that the pre-configuration information in step S504 of the embodiment of the present application does not include the NCC corresponding to the candidate cell.

[0206] S505: gNB1 sends NCC2 to UE.

[0207] Among them, NCC2 is the key information used by the UE when switching cells this time, and is used by the UE to deduce the key for the UE's current switching.

[0208] It should be understood that when the UE receives NCC2, if the switching execution process has not yet been started, NCC2 is used by the UE to deduce the key for the UE's next switching; when the UE receives NCC2, it has been determined to start the switching execution process, then NCC2 is used by the UE to deduce the key for the UE's current switching.

[0209] Optionally, gNB1 may send NCC2 to the UE before determining the target cell for this handover.

[0210] In one implementation, gNB1 may send NCC2 to the UE via L3 / L2 / L1 signaling for the UE to derive the key of the target cell.

[0211] For example, L3 signaling may be an RRC message, L2 signaling may be a MAC CE, and L1 signaling may be a DCI. NCC2 may be received by gNB1 from the AMF, a process not shown in FIG5 .

[0212] Optionally, after receiving NCC2, the UE may store the value of NCC2 and not immediately use it for key derivation or replace the previously stored NCC. For example, before step S505, the UE stores NCC1. After step S505, the UE may store both NCC1 and NCC2.

[0213] In a possible implementation, the NCC2 sent in step S505 may be sent through the switching command in step S507. In this case, step S505 and step S507 may be considered to be combined into one step.

[0214] S506: gNB1 derives the key Key2 corresponding to the first cell, which belongs to gNB2.

[0215] In some embodiments, gNB1 may derive Key2 based on parameters such as the target cell's physical cell ID (PCI) and downlink frequency, in combination with NH2 corresponding to NCC2 or Key1. NCC2 and NH2 are key information obtained by gNB1 from the core network. This embodiment of the application does not limit the method by which the gNB and UE derive the key.

[0216] Exemplarily, gNB1 can determine the deduction method based on NCC2 and NH2, where the deduction method includes vertical deduction and horizontal deduction; further, when the deduction method is determined to be vertical deduction, gNB1 can deduce Key2 based on NH2 and parameters such as the PCI and downlink frequency of the first cell; when the deduction method is determined to be horizontal deduction, gNB1 can deduce Key2 based on Key1 and parameters such as the PCI and downlink frequency of the first cell.

[0217] When gNB1 has an unused pair of {NH, NCC} parameters (i.e., a new NCC and new NH have been received), gNB1 may use vertical derivation. When the source gNB does not have an unused pair of {NH, NCC} parameters (i.e., both the stored NH and NCC have been used), the source gNB uses horizontal derivation. The pair of {NH, NCC} parameters may be provided to gNB1 by the AMF. It should be understood that the used stored NH and NCC may be used during intra-site handover.

[0218] S507: gNB1 sends a handover command to the UE, where the handover command is used to instruct handover to the first cell.

[0219] The first cell is the target cell of this handover. The handover command may also be referred to as an LTM command (CMD), namely, LTMCMD.

[0220] It should be noted that FIG5 takes the LTM handover command as an example, and the handover command may be an L1 / L2 message; in other handover technologies, the handover command may be an L1 / L2 / L3 message.

[0221] The handover command may include identification information corresponding to the target cell. For example, the identification information may be a pre-configured identification, indicating which set of pre-configurations received in step S504 the UE uses.

[0222] S508: gNB1 sends a notification message to gNB2, carrying Key2.

[0223] The notification message includes key information (eg, Key2) that should be used when the target cell (ie, the first cell) communicates with the UE, and does not need to include the NCC.

[0224] In addition, the notification message may also include one or more of the following: UE identity information, target cell identity information, and target gNB identity information.

[0225] It should be noted that the embodiment of the present application does not limit the order in which step S507 and step S508 occur, nor does it limit the order in which step S507 and step S506 occur.

[0226] S509: The UE derives Key2 based on NCC2.

[0227] In some embodiments, the UE may determine the PCI and downlink frequency information of the target cell based on the target cell identity indicated in step S507; and then, in combination with the NCC2 received in step S505, deduce the key (eg, Key2) of the target cell.

[0228] In one implementation, the UE may compare the newly received NCC (ie, NCC2) with the previously received and stored NCC value, and if they are the same, perform horizontal deduction; if they are different, perform vertical deduction.

[0229] S510: The UE accesses the first cell.

[0230] In some embodiments, the UE may apply the target cell pre-configuration information received in step S504 to access the target cell.

[0231] S511: gNB2 sends a path switch request message to the AMF to request the core network to switch the downlink path between the user plane function network element and the base station for the UE from gNB1 to gNB2.

[0232] S512: AMF sends a path switch request response message (carrying NH3 and NCC3) to gNB2.

[0233] Optionally, the path switch request response message may further carry indication information indicating whether the path switch is successful.

[0234] Steps S501 to S512 describe the specific process of the first handover (UE handover from gNB1 to gNB2). The following also illustrates some steps (e.g., steps S513 to S518) for the second handover (UE handover from gNB2 to gNB3). It should be understood that a cell handover after the first handover may be referred to as a subsequent handover, and the LTM pre-configured information of the multiple candidate cells received by the UE may be used in subsequent handovers of the UE after the first handover.

[0235] S513: gNB2 sends NCC3 to UE.

[0236] Among them, NCC3 is the key information during the second handover, which is used by the UE to deduce the key of the target cell of the second handover.

[0237] S514: gNB2 derives the key Key3 corresponding to the second cell based on NH3. The second cell belongs to gNB3.

[0238] S515: gNB2 sends a handover command to the UE, indicating handover to the second cell.

[0239] S516: gNB2 sends a notification message to gNB3, carrying Key3.

[0240] S517: The UE derives Key3 based on NCC3.

[0241] It should be understood that the above-mentioned keys Key1, Key2 and Key3 can be KgNB in ​​NR communication. The UE and gNB use KgNB to further derive the key Kup used for user plane data and the key Krrc used for RRC layer signaling. The UE and gNB use Kup to encrypt user plane data, perform integrity protection and other security processing, and the UE and gNB use Krrc to encrypt RRC signaling and perform integrity protection and other security processing.

[0242] S518: The UE accesses the second cell.

[0243] In the method shown in Figure 5, during the second handover, gNB2 sends the NCC3 used in this handover to the UE. The UE can derive Key3 based on NCC3. The UE also sends Key3 derived from NH3 corresponding to NCC3 to gNB3, ensuring key alignment between the UE and gNB3.

[0244] After step S518, the second handover may also include gNB3 obtaining NH4 and NCC4 from AMF and sending NCC4 to UE. For details, please refer to steps S511 to S513, which are not shown in Figure 5.

[0245] Assume that the third handover is from the second cell of gNB3 to the first cell of gNB2. Since the key information used for the first handover to the first cell is NCC2 and the key information used for the third handover to the first cell is NCC4, the UE uses NCC2 to derive the key when it first hands over to the first cell and uses NCC4 to derive the key when it third hands over to the first cell. The obtained keys are different. Therefore, although the first and third handovers are to the same cell, key reuse can be avoided, thereby ensuring communication security.

[0246] In some embodiments of the present application, before step S505, the UE stores NCC1, which is the NCC corresponding to the key of the service cell of the current UE; after step S505, the UE stores two values, NCC1 and NCC2, and NCC2 is the NCC corresponding to the key of the target cell of LTM switching.

[0247] After step S505, if the source gNB triggers an L3 handover (for example, the handover shown in Figure 1A, or a key change in the same cell), if NCC3 is indicated in the handover command or key reconfiguration command of this L3 handover, the UE performs this L3 handover or key update, and updates the previously stored value of NCC1 to the value of NCC3 (if NCC1=NCC3, the update process can also be understood as maintaining the value of NCC1), and updates the previously stored value of NCC2 to the value of NCC3 (if NCC2=NCC3, the update process can also be understood as maintaining the value of NCC1).

[0248] The above technology can ensure that when LTM switching and L3 switching (or key change in the same cell) coexist, the subsequent key deduction results of the UE and the base station are consistent, avoiding the situation where the UE and the base station deduce different keys and avoid communication failure.

[0249] The method embodiment shown in FIG4 can also be applied to switching technologies triggered by terminal devices (such as CHO switching technology). Exemplarily, in the CHO switching technology, the access network device can provide the terminal device with the configuration of multiple candidate cells and corresponding trigger conditions. For example, the trigger condition can be that the reference signal of a candidate cell is higher than the reference signal received power (RSRP) of the reference signal of the serving cell by a preset decibel (dB); then, when the terminal device determines that the trigger condition corresponding to a candidate cell is met, it selects the cell as the target cell and accesses the target cell. In switching technologies triggered by terminal devices such as CHO, there is no need for the access network device to issue a switching command to indicate the target cell to the terminal device. The specific process can be seen in the embodiment shown in FIG6.

[0250] FIG6 is a flow chart of another key management method provided in an embodiment of the present application.

[0251] Among them, the key management method provided in the embodiment of this application is introduced in detail by taking the terminal device as UE, the source access network device of the terminal device (that is, the above-mentioned first access network device) as gNB1, the target access network device for the terminal device switching (that is, the above-mentioned second access network device) as gNB2, and the core network device as AMF as an example.

[0252] As shown in FIG6 , the key management method may include some or all of the following steps:

[0253] S601: UE communicates with gNB1 based on Key1.

[0254] S602: gNB1 sends a handover request message to candidate gNBs (such as gNB2 and gNB3), which is used to request CHO pre-configuration information.

[0255] S603: The candidate gNB sends a handover request response message to gNB1, carrying the CHO pre-configuration information.

[0256] Exemplarily, the message may carry LTM pre-configuration information for cells managed by gNB2 and gNB3. That is, the multiple candidate cells include cells managed by gNB2 and gNB3.

[0257] Optionally, the message may also carry LTM pre-configuration information of cells managed by gNB1 (i.e., multiple candidate cells). That is, the multiple candidate cells include the cells managed by gNB1.

[0258] S604: gNB1 sends CHO pre-configuration information to the UE.

[0259] S605: gNB1 sends NCC2 to UE.

[0260] S606: The UE determines that the first cell is the target cell, and the first cell belongs to gNB2.

[0261] In some embodiments, the UE may select a candidate cell as a target cell upon evaluating and determining that the candidate cell meets the handover triggering condition. For example, the first cell managed by gNB2 is the candidate cell. The UE evaluates and determines that the first cell meets the handover triggering condition and selects the first cell as the target cell.

[0262] S607: The UE sends a first message to gNB1 to indicate switching to the first cell.

[0263] Among them, the first message may include at least one of the following information: identification information corresponding to the target cell selected by the UE (i.e., the first cell), and identification information corresponding to the target gNB selected by the UE (i.e., gNB2).

[0264] In the embodiment of the present application, the first message may also be referred to as a farewell message (Goodbye message), and the present application does not limit the naming of the first message.

[0265] S608: gNB1 derives Key2.

[0266] In some embodiments, gNB1 may perform key derivation based on the identification information corresponding to the target cell or target gNB in ​​the first message.

[0267] S609: gNB1 sends a notification message to gNB2, carrying Key2.

[0268] In some embodiments, gNB1 determines that the target gNB is gNB2 based on the identification information corresponding to the target cell (i.e., the first cell) or the target gNB (i.e., gNB2) indicated in the first message, and sends a notification message to gNB2. In the embodiments of the present application, the first message may also be referred to as a CHO Notification, and this application does not limit the naming of the first message.

[0269] Optionally, the notification message can be used to indicate that a terminal device will access the cell managed by gNB2.

[0270] S610: The UE derives Key2 based on NCC2.

[0271] S611: The UE accesses the first cell.

[0272] S612: gNB1 sends a path switch request message to the AMF to request the core network to switch the downlink path between the user plane function network element and the base station for the UE from gNB1 to gNB2.

[0273] S613: The AMF sends a path switch request response message to gNB1, which carries NH3 and NCC3.

[0274] Among them, NH3 and NCC3 are both used to deduce the key for communication between terminal equipment and access network equipment.

[0275] Optionally, the path switch request response message may further carry indication information indicating whether the path switch is successful.

[0276] Steps S601 to S612 describe the specific process of the first handover (UE handover from gNB1 to gNB2). The following also illustrates some steps (e.g., steps S613 to S618) for the second handover (UE handover from gNB2 to gNB3). It should be understood that a cell handover after the first handover can be referred to as a subsequent handover, and the CHO pre-configuration information of the multiple candidate cells received by the UE can be used in subsequent handovers after the first handover.

[0277] S614: gNB2 sends NCC3 to UE.

[0278] S615: The UE determines that the second cell is the target cell, and the second cell belongs to gNB3.

[0279] gNB2 derives the key Key3 corresponding to the second cell, which belongs to gNB3.

[0280] S616: The UE sends a second message to gNB2 to indicate switching to the second cell.

[0281] S617: gNB1 derives Key3 based on NH3.

[0282] S618: gNB1 sends a notification message to gNB3, carrying Key3.

[0283] S619: The UE derives Key3 based on NCC3.

[0284] It should be understood that the above-mentioned keys Key1, Key2 and Key3 can be KgNB in ​​NR communication. The UE and gNB use KgNB to further derive the key Kup used for user plane data and the key Krrc used for RRC layer signaling. The UE and gNB use Kup to encrypt user plane data, perform integrity protection and other security processing, and the UE and gNB use Krrc to encrypt RRC signaling and perform integrity protection and other security processing.

[0285] S620: The UE accesses the second cell.

[0286] The specific implementation of some steps in the embodiment of the present application (such as step S601 can refer to step S501) can be found in the relevant content of Figure 5, and will not be repeated here.

[0287] In the method shown in Figure 6, during the second handover, gNB2 sends the NCC3 used in this handover to the UE. The UE can derive Key3 based on NCC3. The UE also sends Key3 derived from NH3 corresponding to NCC3 to gNB3, ensuring key alignment between the UE and gNB3.

[0288] After step S620, the second handover may also include gNB3 obtaining NH4 and NCC4 from AMF and sending NCC4 to the UE. For details, please refer to steps S612 to S614, which are not shown in Figure 6.

[0289] Assume that the third handover is from the second cell of gNB3 to the first cell of gNB2. Since the key information used for the first handover to the first cell is NCC2 and the key information used for the third handover to the first cell is NCC4, the UE uses NCC2 to derive the key when it first hands over to the first cell and uses NCC4 to derive the key when it third hands over to the first cell. The obtained keys are different. Therefore, although the first and third handovers are to the same cell, key reuse can be avoided, thereby ensuring communication security.

[0290] During the execution of Figures 5 and 6 above, a handover failure may occur, for example, the UE fails to successfully access the first cell or the second cell. This embodiment of the present application provides another key management method, which can be applied after a handover failure or a source base station communication failure, as shown in Figure 7.

[0291] Figure 7 is a flowchart of another key management method provided by an embodiment of the present application. As shown in Figure 7, the key management method may include some or all of the following steps:

[0292] S701: The UE fails to access the first cell or a radio link failure occurs in the source cell.

[0293] For example, a handover failure occurs to the UE, such as in the above-mentioned steps S510 or S611, the UE cannot successfully switch to the first cell managed by gNB2.

[0294] In a possible implementation, after receiving the handover command, the UE starts a timer; when the timer times out, if the UE still fails to switch successfully, the UE determines that the handover has failed and performs a cell selection operation, namely step S702.

[0295] In another example, if the UE detects a radio link failure in the source cell, the UE may execute step S702.

[0296] S702: The UE determines the second cell as the target cell from multiple candidate cells, and the second cell belongs to gNB3.

[0297] In some embodiments, if the cell selected by the UE is a candidate cell that has been pre-configured previously, the UE may access the cell through subsequent steps S703 and S704.

[0298] S703: The UE derives Key3 based on NCC2.

[0299] In some embodiments, the UE may deduce Key3 based on NCC2 and cell information of the second cell (such as PCI, etc.).

[0300] S704: The UE initiates access to the second cell, carrying at least one of the following information: source cell ID, UE ID, and MAC-I.

[0301] Among them, the source cell ID can be the identification information corresponding to the source cell / source gNB, the UE ID is the identity identification information of the UE, and the MAC-I is the integrity message authentication code (MAC-I) generated by the UE using the key of the source cell for the uplink message processing.

[0302] In some embodiments, the UE sends an uplink message to the second cell / gNB3. The uplink message may carry the source cell ID. Optionally, the uplink message may also carry the UE ID and MAC-I.

[0303] In a possible implementation, the MAC-I is a short version of the MAC-I, that is, a portion of bits of the complete MAC-I are truncated.

[0304] S705: gNB3 sends a request message to gNB1 to request the key that the UE should use. The request message carries at least one of the following information: source cell ID, UE ID, and MAC-I.

[0305] In some embodiments, gNB3 may determine to send the request message to gNB1 through the identification information corresponding to the source cell / gNB in ​​the message of step S704.

[0306] Optionally, the request message may carry the MAC-I in step E, which is used by gNB1 to verify whether the request is legal.

[0307] Optionally, the request message carries the UE's identity information, which is used by gNB1 to determine for which UE the key derivation is performed.

[0308] S706: gNB1 derives Key3.

[0309] Optionally, gNB1 derives Key3 after successful verification based on MAC-I.

[0310] S707: gNB3 sends Key3 to gNB1.

[0311] It should be understood that the above-mentioned keys Key1, Key2 and Key3 can be KgNB in ​​NR communication. The UE and gNB use KgNB to further derive the key Kup used for user plane data and the key Krrc used for RRC layer signaling. The UE and gNB use Kup to encrypt user plane data, perform integrity protection and other security processing, and the UE and gNB use Krrc to encrypt RRC signaling and perform integrity protection and other security processing.

[0312] In this embodiment of the present application, a UE can perform cell selection upon handover failure. If the selected cell is still a previously configured candidate cell, the UE can send an uplink message to the cell / gNB upon accessing the cell, informing it of the source gNB from which to obtain key information. This method ensures that after a handover failure, the UE can select a candidate cell for access while still ensuring key alignment between the UE and the selected cell / gNB, thereby improving the robustness of the solution.

[0313] Please refer to Figure 8, which is a flow chart of another key management method provided in an embodiment of the present application.

[0314] This method can be applied to switching technologies triggered by terminal devices (such as CHO) and switching technologies triggered by access network devices (such as LTM). In an embodiment of the present application, the target access network device to which the terminal device switches can deduce the key to be used by itself without the need for notification from the source access network device of the terminal device. Among them, the key management method provided in the embodiment of the present application is described in detail by taking the terminal device as UE, the source access network device of the terminal device (that is, the above-mentioned first access network device) as gNB1, the target access network device to which the terminal device switches (that is, the above-mentioned second access network device) as gNB2, and the core network device as AMF as an example.

[0315] As shown in FIG8 , taking LTM switching as an example, the key management method may include some or all of the following steps:

[0316] S81: The UE obtains the initial key of the candidate access network device.

[0317] Figure 8 uses gNB2 and gNB3 as examples for explanation.

[0318] In some embodiments, the AMF may provide initial keys to gNB2 and gNB3, denoted as Root key2 and Root key3, respectively. For example, if the currently serving gNB is gNB1, the initial key used may be Root key1.

[0319] In one possible implementation method, the AMF may provide Root key2 and Root key3 to gNB1, which in turn provides them to gNB2 and gNB3.

[0320] In another possible implementation method, gNB2 and gNB3 each request the initial key from the AMF, and the AMF sends the initial key to gNB2 and gNB3 respectively.

[0321] Optionally, the AMF can calculate Root key 1 based on the two parameters K_AMF and NAS UPLINK COUNTER maintained by itself, calculate Root key 2 based on the two parameters K_AMF and NAS UPLINK COUNTER+1, and calculate Root key 3 based on the two parameters K_AMF and NAS UPLINK COUNTER+2. Among them, K_AMF is the key corresponding to the AMF, and NAS UPLINK COUNTER is the uplink counter value of the non-access stratum (NAS).

[0322] It should be understood that the UE side also maintains the two parameters K_AMF and NAS UPLINK COUNTER, and can calculate Root key1, Root key2 and Root key3 according to the above principles.

[0323] Exemplarily, as shown in FIG8 , S81 may include some or all of the following steps:

[0324] S811: AMF sends Root key2 corresponding to gNB2 and Root key3 corresponding to gNB3.

[0325] S812: UE communicates with gNB1 based on Key1.

[0326] S813: gNB1 sends a handover request message to gNB2. The handover request message is used to request LTM pre-configuration information. The handover request message carries Root key2.

[0327] For a detailed description of LTM pre-configuration information, please refer to the relevant content above and will not be repeated here.

[0328] S814: gNB1 sends a handover request message to gNB3. The handover request message is used to request LTM pre-configuration information. The handover request message carries Root key3.

[0329] S815: gNB2 sends a handover request response message to gNB1. The handover request response message carries the LTM pre-configuration information of the candidate cells managed by gNB2.

[0330] S816: gNB3 sends a handover request response message to gNB1. The handover request response message carries the LTM pre-configuration information of the candidate cells managed by gNB3.

[0331] S817: gNB1 sends LTM pre-configuration information to the UE.

[0332] Exemplarily, gNB1 sends the LTM pre-configuration information of the candidate cells managed by gNB2 and the LTM pre-configuration information of the candidate cells managed by gNB3 to the UE.

[0333] S818: UE deduce Root key2 and Root key3.

[0334] S82: The UE switches to the first cell for the first time, and the first cell belongs to gNB2.

[0335] In some embodiments, when the UE switches to the target cell / gNB for the first time (gNB2 in Figure 8), it can use the root key corresponding to the target cell / gNB and combine it with the PCI and downlink frequency information of the target cell to generate the key to be used.

[0336] Exemplarily, as shown in FIG8 , S82 may include some or all of the following steps:

[0337] S821: gNB1 sends a handover command to the UE, indicating handover to the first cell, which belongs to gNB2.

[0338] S822: The UE derives Key2-1 based on Root key2.

[0339] This is the UE's first handover to gNB2. The UE uses Root Key2, combined with the PCI and frequency information of the first cell, to generate Key2-1. The 2-1 in Key2-1 represents gNB2, while the 1 represents the first access to gNB2.

[0340] S823: The UE accesses the first cell.

[0341] S824: gNB2 derives Key2-1.

[0342] In one implementation, gNB2, like the UE described above, also uses Root key2 and the PCI and frequency information of the first cell to generate Key2-1.

[0343] S825: gNB2 sends a path switch request message to the AMF to request the core network to switch the downlink path between the user plane function network element and the base station for the UE from gNB1 to gNB2.

[0344] S826: The AMF sends a path switch request response message to gNB2. The message may carry NH for gNB2 and NCC for gNB2.

[0345] Among them, the NH is used when gNB2 derives Key2-2 the next time the UE switches to gNB2 (i.e., the second switch described below); the NCC is used when the UE derives Key2-2 the next time the UE switches to gNB2 (i.e., the second switch described below).

[0346] Optionally, the path switch request response message may further carry indication information indicating whether the path switch is successful.

[0347] S827: gNB2 sends NCC for gNB2 to the UE.

[0348] In one implementation, gNB2 may send the NCC corresponding to gNB2 to the UE via L1 / L2 / L3 signaling, where the signaling includes the NCC value and, optionally, the identity identifier (or preconfigured identifier) ​​corresponding to gNB2.

[0349] S83: The UE switches to the second cell for the first time, and the second cell belongs to gNB3.

[0350] In some embodiments, when the UE switches to the second cell or gNB3 for the first time, it can use the root key corresponding to the second cell / gNB3 and combine the PCI and downlink frequency information of the second cell to generate the key to be used.

[0351] Similar to step S82, the UE and gNB3 respectively deduce Key3-1, where 3-1 in Key3-1 means: 3 identifies gNB3; 1 indicates the first handover to gNB3.

[0352] Exemplarily, as shown in FIG8 , S83 may include some or all of the following steps:

[0353] S831: gNB2 sends a handover command to the UE, indicating handover to the second cell, which belongs to gNB3.

[0354] S832: The UE derives Key3-1 based on Root key3.

[0355] S833: The UE accesses the second cell.

[0356] S834: gNB3 derives Key3-1.

[0357] It should be noted that after step S834, gNB3 can obtain the NH and NCC corresponding to gNB3 from AMF, and send the NCC corresponding to gNB3 to UE. For details, please refer to steps S825, S826 and S827, which are not shown in Figure 8.

[0358] S84: The UE switches to the second cell for the second time.

[0359] In some embodiments, when the UE switches to the first cell / gNB2 for the second time, it can calculate and deduce Key2-2 based on the NCC for gNB2, the PCI of the second cell, and the downlink frequency information. The meaning of 2-2 is: the first 2 represents gNB2, and the second 2 represents the second handover to gNB2; gNB2 can calculate and deduce Key2-2 based on the NH for gNB2, the PCI of the first cell, and the downlink frequency information.

[0360] Exemplarily, as shown in FIG8 , S84 may include some or all of the following steps:

[0361] S841: gNB3 sends a handover command to the UE, indicating handover to the first cell.

[0362] The handover command may include an identifier of the first cell.

[0363] S842: The UE derives Key2-2 based on the NCC for gNB2.

[0364] In some embodiments, the UE performs key derivation based on parameters such as the NCC for gNB2, the PCI of the first cell, and the downlink frequency to obtain Key2-2.

[0365] S843: The UE accesses the first cell.

[0366] S844: gNB2 derives Key2-2 based on NH for gNB2.

[0367] It should be noted that after step S834, gNB3 can obtain the NH and NCC corresponding to gNB3 from AMF, and send the NH and NCC corresponding to gNB3 to UE. For details, please refer to steps S825, S826 and S827, which are not shown in Figure 8.

[0368] In some embodiments, when gNB2 monitors that the UE accesses the first cell, it can perform key derivation based on NH for gNB2 to obtain Key2-2; and communicate with the UE based on Key2-2.

[0369] It should be understood that the above-mentioned keys Key1, Key2 and Key3 can be KgNB in ​​NR communication. The UE and gNB use KgNB to further derive the key Kup used for user plane data and the key Krrc used for RRC layer signaling. The UE and gNB use Kup to encrypt user plane data, perform integrity protection and other security processing, and the UE and gNB use Krrc to encrypt RRC signaling and perform integrity protection and other security processing.

[0370] It should be understood that the above Figure 8 is illustrated using LTM switching as an example. The method flow of CHO switching can refer to the method flow of Figure 8 above. When CHO switching is performed, the switching judgment in the flow of Figure 8 above needs to be changed to UE judgment, that is, the above steps S821, S831 and S841 are changed to UE determining the first cell.

[0371] The above content elaborates on the method provided by the present application. In order to facilitate the implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides corresponding devices or equipment.

[0372] The present application divides the functional modules of the first access network device and the terminal device according to the above-mentioned method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in this application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The communication device of the embodiment of the present application will be described in detail below with reference to Figures 9 to 11.

[0373] 9 , which is a schematic diagram of a structure of a communication device provided in an embodiment of the present application. As shown in FIG9 , the communication device may include a transceiver unit 10 and a processing unit 20 .

[0374] In some embodiments of the present application, the communication device may be the first access network device shown above or a chip or circuit provided in the first access network device. That is, the communication device may be used to execute the steps or functions performed by the first access network device in the above method embodiments.

[0375] In one design, the transceiver unit 10 is used to: send pre-configuration information and first key information of multiple candidate cells to the terminal device; the first key information is used to deduce the key for communication between the terminal device and the access network device; send the first key to the second access network device to which the target cell to which the terminal device switches belongs, the first key being the key for communication between the terminal device and the second access network device, and the multiple candidate cells include the target cell.

[0376] Exemplarily, the pre-configuration information of multiple candidate cells is used for the terminal device to perform one or more handovers among the multiple candidate cells.

[0377] Exemplarily, the pre-configuration information does not include the first key information.

[0378] Exemplarily, the multiple candidate cells belong to one or more access network devices.

[0379] In a possible implementation, the transceiver unit 10 is specifically configured to: after determining the target cell, send the first key to the second access network device.

[0380] Exemplarily, the first key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling, or the first key information is carried by a handover command, and the handover command is used to instruct handover to a target cell.

[0381] In a possible implementation, before sending the first key to the second access network device to which the target cell to which the terminal device is switched belongs, the transceiver unit 10 is further used to: receive a first message sent by the terminal device, where the first message is used to indicate switching to the target cell.

[0382] In a possible implementation, the transceiver unit 10 is specifically configured to: receive a request message sent by the second access network device, where the request message is used to request a key for communication between the terminal device and the second access network device;

[0383] In response to the request message, the first key is sent to the second access network device.

[0384] In a possible implementation, the transceiver unit 10 is specifically configured to: after the request message is verified based on the integrity message authentication code, send the first key to the second access network device.

[0385] In a possible implementation, the transceiver unit 10 is further configured to: send a handover request message to the second access network device, where the handover request message is used to request pre-configuration information of a cell corresponding to the second access network device;

[0386] A response message sent by the second access network device is received, where the response message includes a pre-configuration message of the target cell.

[0387] In the embodiment of the present application, the description of the first key, pre-configuration information and first key information, etc. can be referred to the introduction in the method embodiments shown in Figures 4 to 7 above, and will not be described in detail here.

[0388] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiments of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiments shown in Figures 4 to 7 above, and no further details will be given here. Furthermore, the technical effects of the embodiments of the present application refer to the technical effects of the method embodiments shown in Figures 4 to 7 above, and for the sake of brevity, no further details will be given here.

[0389] Reusing Figure 9, in some other embodiments of the present application, the communication device may be the terminal device shown above or a chip or circuit provided in the terminal device. That is, the communication device may be used to execute the steps or functions performed by the terminal device in the above method embodiments.

[0390] In one design, the transceiver unit 10 is configured to: receive pre-configured information and first key information of a plurality of candidate cells; the first key information is used to derive a key for communication between the terminal device and the access network device;

[0391] The processing unit 20 is used to: after receiving the switching command, deduce based on the first key information to obtain the first key corresponding to the first cell; the switching command is used to indicate switching to the first cell, the first cell belongs to the second access network device, and the first key is the key for communication between the terminal device and the second access network device.

[0392] Exemplarily, the pre-configuration information of multiple candidate cells is used for the terminal device to perform one or more handovers among the multiple candidate cells.

[0393] Exemplarily, the pre-configuration information does not include the first key information.

[0394] Exemplarily, the first key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling, or the first key information is carried by a handover command.

[0395] Exemplarily, the multiple candidate cells belong to one or more access network devices.

[0396] In one possible implementation, the processing unit 20 is also used to: when it is determined that the switching of the first cell fails or the wireless link fails, determine a second cell from multiple candidate cells, and the second cell belongs to a third access network device; the transceiver unit 10 is also used to: send a second message to the third access network device, and the second message is used to request access to the second cell.

[0397] Exemplarily, the second message also includes an integrity message authentication code and / or an identifier of the terminal device.

[0398] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiments of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiments shown in Figures 4, 5, and 7 above, and no further details will be given here. Furthermore, the technical effects of the embodiments of the present application refer to the technical effects of the method embodiments shown in Figures 4, 5, and 7 above, and for the sake of brevity, no further details will be given here.

[0399] Reusing Figure 9, in some other embodiments of the present application, the communication device may be the terminal device shown above or a chip or circuit provided in the terminal device. That is, the communication device may be used to execute the steps or functions performed by the terminal device in the above method embodiments.

[0400] In one design, the transceiver unit 10 is configured to: receive pre-configured information and first key information of a plurality of candidate cells; send a first message to a first access network device, the first message being used to indicate a handover to the first cell; the first cell belongs to a second access network device; the plurality of candidate cells includes the first cell;

[0401] The processing unit 20 is configured to: deduce based on the first key information to obtain a first key corresponding to the first cell; the first key is a key for communication between the terminal device and the second access network device;

[0402] The transceiver unit 10 is configured to: receive second key information from a second access network device; send a second message to the second access network device, the second message being used to instruct handover to a second cell; the second cell belongs to a third access network device; and the plurality of candidate cells include the second cell;

[0403] The processing unit 20 is used to: deduce based on the second key information to obtain a second key corresponding to the second cell; the second key is a key for communication between the terminal device and the third access network device.

[0404] In a possible implementation, the processing unit 20 is further configured to: determine the first cell and / or the second cell from the multiple candidate cells based on pre-configured information of the multiple candidate cells.

[0405] Exemplarily, the multiple candidate cells belong to one or more access network devices.

[0406] Exemplarily, the first key information and / or the second key information is carried by one of layer 1 signaling, layer 2 signaling, and layer 3 signaling.

[0407] In one possible implementation, the processing unit 20 is also used to: when it is determined that switching the second cell fails or the wireless link fails, determine a third cell from multiple candidate cells, and the third cell belongs to a fourth access network device; the transceiver unit 10 is also used to: send a third message to the fourth access network device, and the third message is used to request access to the third cell.

[0408] Exemplarily, the third message also includes an integrity message authentication code and / or an identifier of the terminal device.

[0409] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiments of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiments shown in Figures 4, 6, and 7 above, and will not be described in detail here. Furthermore, the technical effects of the embodiments of the present application refer to the technical effects of the method embodiments shown in Figures 4, 6, and 7 above, and for the sake of brevity, they will not be repeated here.

[0410] The above describes the first access network device and terminal device according to the embodiments of the present application. The following describes possible product forms of the first access network device and terminal device. It should be understood that any product having the functions of the first access network device or terminal device described in FIG. 9 falls within the scope of protection of the embodiments of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the communication devices according to the embodiments of the present application to these examples.

[0411] In one possible implementation, in the communication device shown in FIG9 , the processing unit 20 may be one or more processors, and the transceiver unit 10 may be a transceiver. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit, wherein the transmitting unit may be a transmitter and the receiving unit may be a receiver, and the transmitting unit and receiving unit are integrated into a single device, such as a transceiver. In embodiments of the present application, the processor and transceiver may be coupled, and the connection method between the processor and transceiver is not limited in this embodiment. During the execution of the above-described method, the process of sending information in the above-described method can be understood as the process of the processor outputting the above-described information. When outputting the above-described information, the processor outputs the above-described information to the transceiver for transmission by the transceiver. After being output by the processor, the above-described information may require further processing before reaching the transceiver. Similarly, the process of receiving information in the above-described method can be understood as the process of the processor receiving the above-described information. When the processor receives the input information, the transceiver receives the above-described information and inputs it into the processor. Furthermore, after the transceiver receives the above-described information, the above-described information may require further processing before being input into the processor.

[0412] Referring to Figure 10, Figure 10 is another structural diagram of the communication device provided in an embodiment of the present application. As shown in Figure 10, the communication device provided in an embodiment of the present application can be used to implement the method described in the above method embodiment, and reference can be made to the description in the above method embodiment. The communication device can be a first access network device, or a terminal device, or a chip therein. Exemplarily, the communication device includes one or more processors 1001 and a transceiver 1002. The communication device may further include a memory 1003. In one implementation, the communication device also includes an input and output device (not shown in Figure 10).

[0413] Processor 1001 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. Memory 1003 is primarily used to store software programs and data. Transceiver 1002 may include control circuitry and an antenna. The control circuitry is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0414] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1001 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0415] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0416] The processor 1001 , the transceiver 1002 , and the memory 1003 may be connected via a communication bus.

[0417] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the first access network device in the embodiment shown in Figure 4 above, the transceiver 1002 can be used to execute steps S401 and S402 in Figure 4, and / or other processes for the technology described herein.

[0418] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the terminal device in the embodiment shown in FIG. 4 above, the processor 1001 can be used to generate step S403 in FIG. 4 , and / or other processes for executing the technology described herein; the transceiver 1002 can be used to execute step S401 in FIG. 4 , and / or other processes for the technology described herein.

[0419] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the first access network device in the embodiment shown in FIG. 8 above, the processor 1001 can be used to execute step S824 in FIG. 8 , and / or to execute other processes of the technology described herein; the transceiver 1002 can be used to execute step S827 in FIG. 8 , and / or to execute other processes of the technology described herein.

[0420] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the terminal device in the embodiment shown in FIG8 above, the processor 1001 can be used to execute steps S818, S822 in FIG8 and / or other processes for executing the technology described herein; the transceiver 1002 can be used to execute steps S812, step S817, step S821, step S823, step S827 in FIG8, and / or other processes for the technology described herein.

[0421] In any of the above implementations, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0422] In any of the above implementations, the processor 1001 may store instructions, which may be computer programs. The computer programs, when executed on the processor 1001, may cause the communication device to perform the methods described in the above method embodiments. The computer programs may be embedded in the processor 1001, in which case the processor 1001 may be implemented by hardware.

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

[0424] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 10, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the description of the method embodiment above.

[0425] In another possible implementation, in the communication device shown in FIG9 , the processing unit 20 may be one or more logic circuits, and the transceiver unit 10 may be an input / output interface, or may be referred to as a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit, the transmitting unit may be an output interface, the receiving unit may be an input interface, and the transmitting unit and the receiving unit may be integrated into one unit, such as an input / output interface.

[0426] Referring to Figure 11, Figure 11 is another structural diagram of a communication device provided in an embodiment of the present application. As shown in Figure 11, the communication device shown in Figure 11 includes a logic circuit 901 and an interface 902. That is, the above-mentioned processing unit 20 can be implemented with a logic circuit 901, and the transceiver unit 10 can be implemented with an interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input and output interface, a pin, etc. Exemplarily, Figure 11 is shown as an example of the above-mentioned communication device as a chip, and the chip includes a logic circuit 901 and an interface 902.

[0427] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0428] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the first access network device in the method embodiment shown in Figure 4 above, the logic circuit 901 is used to determine the first key; the interface 902 is used to send pre-configuration information and first key information of multiple candidate cells; the interface 902 is used to send the first key, and the first key is the key for communication between the terminal device and the second access network device.

[0429] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the terminal device in the method embodiment shown in Figure 4 above, the logic circuit 901 is used to determine the first key corresponding to the target cell by deduction based on the first key information; the interface 902 is used to receive the first key.

[0430] In the embodiment of the present application, the description of the first key, pre-configuration information, and first key information can be referred to the description of the method embodiment shown in FIG4 above, and will not be described in detail here. It is understood that the specific description of the logic circuit 901 and the interface 902 can also refer to the description of the processing unit and the transceiver unit shown in FIG9, and will not be repeated here.

[0431] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0432] For the specific implementation of each embodiment shown in FIG11 , reference may also be made to the above embodiments, which will not be described in detail here.

[0433] An embodiment of the present application also provides a communication system, which includes a first access network device and a terminal device. The first access network device and the terminal device can be used to execute the method in any of the aforementioned method embodiments (Figures 4 to 8).

[0434] In addition, the present application also provides a computer program, which is used to implement the operations and / or processing performed by the first access network device in the method provided by the present application.

[0435] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the terminal device in the method provided by the present application.

[0436] The present application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, it enables the computer to execute the operations and / or processing performed by the first access network device in the method provided by the present application.

[0437] The present application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, the computer executes the operations and / or processing performed by the terminal device in the method provided by the present application.

[0438] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the first access network device in the method provided by the present application are executed.

[0439] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program is run on a computer, the operations and / or processing performed by the terminal device in the method provided by the present application are executed.

[0440] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0441] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0442] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0443] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media that can store program code.

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

Claims

1. A key management method, characterized in that: The method comprises: Sending pre-configuration information of multiple candidate cells and first key information to a terminal device; the first key information is used to deduce a key for communication between the terminal device and an access network device; A first key is sent to a second access network device to which a target cell to which the terminal device switches belongs, where the first key is a key for communication between the terminal device and the second access network device, and the multiple candidate cells include the target cell.

2. The method according to claim 1, characterized in that The pre-configuration information of the multiple candidate cells is used for the terminal device to perform one or more switching among the multiple candidate cells.

3. The method according to claim 1 or 2, characterized in that: The pre-configuration information does not include the first key information.

4. The method according to any one of claims 1 to 3, characterized in that: The multiple candidate cells belong to one or more access network devices.

5. The method according to any one of claims 1 to 4, characterized in that: The sending the first key to the second access network device to which the target cell for handover of the terminal device belongs includes: After determining the target cell, sending the first key to the second access network device.

6. The method according to any one of claims 1 to 5, characterized in that: The first key information is carried by one of layer 1 signaling, layer 2 signaling and layer 3 signaling, or the first key information is carried by a handover command, and the handover command is used to indicate handover to the target cell.

7. The method according to any one of claims 1 to 4, characterized in that: Before sending the first key to the second access network device to which the target cell to which the terminal device is switched belongs, the method further includes: Receive a first message sent by the terminal device, where the first message is used to indicate switching to the target cell.

8. The method according to any one of claims 1 to 4, characterized in that: The sending the first key to the second access network device to which the target cell for handover of the terminal device belongs includes: Receiving a request message sent by the second access network device, where the request message is used to request a key for communication between the terminal device and the second access network device; In response to the request message, the first key is sent to the second access network device.

9. The method according to claim 8, characterized in that The request message further includes an integrity message authentication code, and the sending the first key to the second access network device includes: After the request message is verified based on the integrity message authentication code, the first key is sent to the second access network device.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Sending a handover request message to the second access network device, where the handover request message is used to request pre-configuration information of a cell corresponding to the second access network device; Receive a response message sent by the second access network device, where the response message includes a pre-configuration message of the target cell.

11. A key management method, characterized in that: The method comprises: Receiving pre-configuration information and first key information of a plurality of candidate cells; the first key information is used to deduce a key for communication between a terminal device and an access network device; After receiving the switching command, the first key corresponding to the first cell is deduced based on the first key information; the switching command is used to indicate switching to the first cell, the first cell belongs to the second access network device, and the first key is the key for communication between the terminal device and the second access network device.

12. The method according to claim 11, characterized in that The pre-configuration information of the multiple candidate cells is used for the terminal device to perform one or more switching among the multiple candidate cells.

13. The method according to claim 11 or 12, characterized in that: The pre-configuration information does not include the first key information.

14. The method according to any one of claims 11 to 13, characterized in that: The first key information is carried by one of layer 1 signaling, layer 2 signaling and layer 3 signaling, or the first key information is carried by the handover command.

15. The method according to any one of claims 11 to 14, characterized in that: The multiple candidate cells belong to one or more access network devices.

16. The method according to any one of claims 11 to 15, characterized in that: The method further comprises: When it is determined that the handover of the first cell fails or the radio link fails, determining a second cell from the multiple candidate cells, where the second cell belongs to a third access network device; A second message is sent to the third access network device, where the second message is used to request access to the second cell.

17. The method according to claim 16, characterized in that The second message also includes an integrity message authentication code and / or an identification of the terminal device.

18. A key management method, characterized in that: The method comprises: receiving pre-configuration information and first key information of a plurality of candidate cells; Sending a first message to a first access network device, where the first message is used to indicate switching to a first cell; the first cell belongs to a second access network device; and the multiple candidate cells include the first cell; Deducing based on the first key information, obtaining a first key corresponding to the first cell; the first key is a key for communication between the terminal device and the second access network device; Receiving second key information from the second access network device; Sending a second message to the second access network device, where the second message is used to indicate switching to a second cell; the second cell belongs to a third access network device; and the multiple candidate cells include the second cell; Based on the second key information, deduction is performed to obtain a second key corresponding to the second cell; the second key is a key for communication between the terminal device and the third access network device.

19. The method according to claim 18, characterized in that The method further comprises: Based on the pre-configuration information of the multiple candidate cells, the first cell and / or the second cell is determined from the multiple candidate cells.

20. The method according to claim 18 or 19, characterized in that The multiple candidate cells belong to one or more access network devices.

21. The method according to any one of claims 18 to 20, characterized in that: The first key information and / or the second key information is carried by one of layer 1 signaling, layer 2 signaling and layer 3 signaling.

22. The method according to any one of claims 18 to 21, characterized in that: The method further comprises: When it is determined that the switching of the second cell fails or the radio link fails, determining a third cell from the multiple candidate cells, where the third cell belongs to a fourth access network device; A third message is sent to the fourth access network device, where the third message is used to request access to the third cell.

23. The method according to claim 22, characterized in that The third message also includes an integrity message authentication code and / or an identification of the terminal device.

24. A communication device, characterized in that: Comprising modules or units for executing the method according to any one of claims 1 to 23.

25. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 23 through a logic circuit or executing code instructions.

26. A readable storage medium, characterized in that: Used to store a program, the program being executed by one or more processors so that a device including the one or more processors performs the method according to any one of claims 1 to 23.

27. A communication system, characterized in that: include: A first access network device for executing the method described in any one of claims 1 to 10, and a terminal device for executing the method described in any one of claims 11 to 23.

Images