WO2022021413A1 - Key generation method and apparatus, and terminal device and network device - Google Patents

Abstract

Provided are a key generation method and apparatus, and a terminal device and a network device. The method comprises: a terminal device receiving a radio resource control (RRC) recovery message sent by a master node (MN), wherein the RRC recovery message carries first secondary key counter (SK-Counter) information and/or secondary cell group configuration information; and the terminal device determining target SK-Counter information on the basis of the RRC recovery message, and calculating a key of a secondary cell group by using the target SK-Counter information.

Description

A kind of key generation method and apparatus, terminal equipment, network equipment technical field

The embodiments of the present application relate to the field of mobile communication technologies, and in particular, to a method and apparatus for generating a key, a terminal device, and a network device.

Background technique

At present, the secondary key count (Secondary Key-Counter, SK-Counter) is configured in the Radio Resource Control (Radio Resource Control, RRC) recovery message, and the SK-Counter is also configured in the secondary cell group configuration information (mrdc-SecondaryCellGroup) , how to use or how to configure these two SK-Counters is a problem that needs to be clarified.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a method and device for generating a key, a terminal device, and a network device.

The key generation method provided by the embodiment of the present application includes:

The terminal device receives an RRC recovery message sent by the MN, where the RRC recovery message carries the first SK-Counter information and/or the configuration information of the secondary cell group;

The terminal device determines target SK-Counter information based on the RRC recovery message, and uses the target SK-Counter information to calculate the key of the secondary cell group.

The key generation method provided by the embodiment of the present application includes:

The MN sends an RRC recovery message to the terminal device, where the RRC recovery message is used to determine one SK-Counter information, and the one SK-Counter information is used by the terminal device to calculate the key of the secondary cell group.

The key generation device provided by the embodiment of the present application is applied to a terminal device, and the device includes:

a receiving unit, configured to receive an RRC recovery message sent by the MN, where the RRC recovery message carries the first SK-Counter information and/or the configuration information of the secondary cell group;

a determining unit, configured to determine target SK-Counter information based on the RRC recovery message;

A processing unit, configured to calculate the key of the secondary cell group by using the target SK-Counter information.

The key generation device provided by the embodiment of the present application is applied to network equipment, and the device includes:

A sending unit, configured to send an RRC recovery message to the terminal device, where the RRC recovery message is used to determine one SK-Counter information, and the one SK-Counter information is used for the terminal device to calculate the key of the secondary cell group.

The terminal device provided by the embodiments of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above key generation method.

The network device provided by the embodiments of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above key generation method.

The chip provided by the embodiment of the present application is used to implement the above key generation method.

Specifically, the chip includes: a processor for invoking and running a computer program from the memory, so that the device on which the chip is installed executes the above-mentioned key generation method.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned key generation method.

The computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned key generation method.

The computer program provided by the embodiment of the present application, when it runs on a computer, causes the computer to execute the above-mentioned key generation method.

Through the above technical solutions, on the one hand, it is clarified how the terminal device uses the SK-Counter configured on the network side, and on the other hand, how to configure the SK-Counter on the network side, so that the keys used by the terminal device and the network side are consistent. Provide guarantee for subsequent normal communication.

Description of drawings

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

2 is a schematic flowchart 1 of a key generation method provided by an embodiment of the present application;

3 is a second schematic flowchart of a key generation method provided by an embodiment of the present application;

FIG. 4 is a schematic flowchart three of a key generation method provided by an embodiment of the present application;

5 is a fourth schematic flowchart of a key generation method provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram 1 of a key generation device provided by an embodiment of the present application;

FIG. 7 is a schematic diagram 2 of the structure and composition of a key generation device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a chip according to an embodiment of the present application;

FIG. 10 is a schematic block diagram of a communication system provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (Long Term Evolution, LTE) system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (Time Division Duplex) , TDD), systems, 5G communication systems or future communication systems, etc.

Exemplarily, a communication system 100 to which this embodiment of the present application is applied is shown in FIG. 1 . The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal). The network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the The network device can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system.

The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110 . "Terminal" as used herein includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connections; and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device of another terminal configured to receive/transmit a communication signal; and/or an Internet of Things (IoT) device. A terminal arranged to communicate through a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radio telephones with data processing, facsimile, and data communication capabilities; may include radio telephones, pagers, Internet/Intranet PDAs with networking access, web browsers, memo pads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or others including radiotelephone transceivers electronic device. A terminal may refer to an access terminal, user equipment (UE), subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.

Optionally, direct terminal (Device to Device, D2D) communication may be performed between the terminals 120 .

Optionally, the 5G communication system or the 5G network may also be referred to as a new radio (New Radio, NR) system or an NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices, and the coverage of each network device may include other numbers of terminals. This embodiment of the present application This is not limited.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; The device may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

With people's pursuit of speed, delay, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the ^3rd Generation Partnership Project (3GPP) international standards organization began to develop 5G . The main application scenarios of 5G are: Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), Massive Machine-Type Communications (mMTC) ).

On the one hand, eMBB still aims at users' access to multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety assurance, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of the module.

In the early deployment of NR, complete NR coverage is difficult to obtain, so typical network coverage is wide-area LTE coverage and NR island coverage mode. And a lot of LTE is deployed in sub-6GHz, and there is very little sub-6GHz spectrum available for 5G. Therefore, NR must study the spectrum application above 6GHz, while the high frequency band has limited coverage and fast signal fading. At the same time, in order to protect the early investment of mobile operators in LTE, a working mode of tight interworking between LTE and NR is proposed.

双连接(Dual Connectivity，DC)架构

Dual Connectivity (DC) architecture

In order to realize 5G network deployment and commercial applications as soon as possible, the 3rd Generation Partnership Project (3GPP) first completed the first 5G version, namely E-UTRA and NR Dual Connectivity (E-UTRA-NR Dual Connectivity, EN-DC). In EN-DC, an LTE base station (eNB) acts as a master node (Master Node, MN), and an NR base station (gNB or en-gNB) acts as a secondary node (Secondary Node, SN), connecting to the EPC core network. Later in R15, other DC modes will be supported, including NR and E-UTRA Dual Connectivity (NR-E-UTRA Dual Connectivity, NE-DC), 5GC-EN-DC, NR DC. In NE-DC, the NR base station acts as the MN, and the eLTE base station acts as the SN, connecting to the 5GC core network. In 5GC-EN-DC, the eLTE base station acts as the MN, and the NR base station acts as the SN, connecting to the 5GC core network. In NR DC, the NR base station acts as the MN, and the NR base station acts as the SN, connecting to the 5GC core network.

In the dual-connection architecture, the cell group on the MN side is called the Master Cell Group (MCG), and the cell group on the SN side is called the Secondary Cell Group (SCG). The MCG includes a primary cell (Primary Cell, PCell) and at least one secondary cell (Secondary Cell, SCell). The SCG includes a special cell (Special Cell, SpCell), optionally, one or more SCells.

The technical solutions of the embodiments of the present application may be applied to a dual-connectivity architecture, such as a Multi-RAT Dual Connectivity (MR-DC) architecture.

RRC状态

RRC status

5G defines a new Radio Resource Control (RRC) state, that is, RRC_INACTIVE state, in order to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state. in,

1) RRC_IDLE state (referred to as idle state): mobility is based on terminal device cell selection and reselection, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN. There is no terminal device context and no RRC connection on the base station side.

2) RRC_CONNECTED state (referred to as connected (connected) state for short): there is an RRC connection, and a terminal device context exists on the base station side and the terminal device side. The network side knows that the location of the terminal equipment is at the specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the terminal equipment and the base station.

3) RRC_INACTIVE state (referred to as inactive state): mobility is based on terminal equipment cell selection reselection, there is a connection between CN-NR, terminal equipment context exists on a certain base station, paging is triggered by RAN , the RAN-based paging area is managed by the RAN, and the network side knows the location of the terminal device is based on the RAN-based paging area level.

When the terminal device configured with the MR-DC enters the inactive state, the terminal device keeps the configuration information of the MR-DC, but releases the SCG configuration when the terminal device initializes the RRC connection recovery. By adding an indication information in the RRC resume (RRCResume) message, indicating that the terminal device can restore the previous SCG configuration, the indication information corresponds to "restoreSCG" in Table 1 below.

Table 1

In MR-DC, the key of the SCG is generated based on the key of the MN and the secondary key count (Secondary Key-Counter, SK-Counter). Here, the SK-Counter can also be called the SCG counter. During the RRC connection recovery process, the terminal device will use the Next Hop Chaining Counter (NCC) configured in the RRC Release (RRCRelease) message to generate a key for MSG4 and all subsequent uplink and downlink messages and data. Currently, the SK-Counter is configured in the RRC recovery message, and the SK-Counter is also configured in the secondary cell group configuration information (mrdc-SecondaryCellGroup). How to use or configure the two SK-Counters is a problem that needs to be clarified.

FIG. 2 is a schematic flowchart 1 of a key generation method provided by an embodiment of the present application. As shown in FIG. 2 , the key generation method includes the following steps:

Step 201: The terminal device receives an RRC recovery message sent by the MN, where the RRC recovery message carries first SK-Counter information and/or secondary cell group configuration information.

In this embodiment of the present application, before the terminal device receives the RRC recovery message sent by the MN, the terminal device sends an RRC recovery request message to the MN.

Step 202: The terminal device determines target SK-Counter information based on the RRC recovery message, and uses the target SK-Counter information to calculate the key of the secondary cell group.

In this embodiment of the present application, the determination of the target SK-Counter information may be implemented in the following manner.

●Method 1

When the RRC recovery message carries the first SK-Counter information and the secondary cell group configuration information, and the secondary cell group configuration information carries the second SK-Counter information, 1) the terminal device determines the target SK-Counter The Counter information is the second SK-Counter information; or, 2) the terminal device determines that the target SK-Counter information is the first SK-Counter information.

●Method 2

In the case where the RRC recovery message carries the first SK-Counter information and the secondary cell group configuration information, and the secondary cell group configuration information does not carry the second SK-Counter information, the terminal device determines the target SK-Counter The information is the first SK-Counter information.

●Method three

In the case that the RRC recovery message carries the first SK-Counter information, the terminal device determines that the target SK-Counter information is the first SK-Counter information.

●Method four

When the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information, the terminal device determines that the target SK-Counter information is the second SK-Counter Counter information.

In the embodiment of the present application, after the terminal device receives the RRC recovery message sent by the MN, or after the terminal device calculates the key of the secondary cell group, the terminal device sends an RRC recovery complete message to the MN.

FIG. 3 is a second schematic flowchart of a key generation method provided by an embodiment of the present application. As shown in FIG. 3 , the key generation method includes the following steps:

Step 301: The UE receives an RRC release (RRCRlease) message sent by the MN.

Here, the UE configured with MR-DC enters the inactive state after receiving the RRC release message.

Step 302: The UE initiates an RRC connection recovery process, and sends an RRC recovery request (RRCResumeRequest) message to the MN.

Step 303: The MN sends a secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node addition request (S-NODE ADDITION REQUEST) message to the SN.

Step 304: The SN sends a secondary node modification request acknowledgment (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node addition request acknowledgment (S-NODE ADDITION REQUEST ACKNOWLEDGE) message to the MN.

Step 305: The UE receives an RRC resume (RRCResume) message sent by the MN, where the RRC resume message carries two information elements, the first SK-Counter and the mrdc-SecondaryCellGroup. The second SK-Counter is carried in the mrdc-SecondaryCellGroup information element.

Step 306: The UE uses the second SK-Counter to calculate the key of the SCG and ignores the first SK-Counter. Alternatively, the UE uses the first SK-Counter to calculate the key of the SCG and ignores the second SK-Counter.

Step 307: The UE sends an RRC recovery complete (RRCResumeComplte) message to the MN.

FIG. 4 is a schematic flow chart 3 of a key generation method provided by an embodiment of the present application. As shown in FIG. 4 , the key generation method includes the following steps:

Step 401: The MN sends an RRC recovery message to the terminal equipment, where the RRC recovery message is used to determine a piece of SK-Counter information, and the piece of SK-Counter information is used by the terminal equipment to calculate the key of the secondary cell group.

In the embodiment of the present application, before the MN sends the RRC recovery message to the terminal device, the MN receives the RRC recovery request message sent by the terminal device. After the MN sends the RRC recovery message to the terminal device, the MN receives the RRC recovery complete message sent by the terminal device.

In the embodiment of the present application, the RRC recovery message is used to determine a piece of SK-Counter information. In this way, the ambiguity of the SK-Counter information for the terminal equipment can be avoided, and the SK-Counter information can be directly used to calculate the key of the secondary cell group. The network side can ensure that only one SK-Counter information can be determined in the RRC recovery message in the following manner.

●Method 1

The RRC recovery message carries the first SK-Counter information.

In an optional manner, in the case that the key of at least one bearer is set as the secondary key, and the secondary cell group configuration information is not configured, the RRC recovery message carries the first SK-Counter information.

Specifically, the network side carries the first SK-Counter in the RRC recovery message only when the KeyToUse information element of at least one RB is set to secondary and the mrdc-SecondaryCellGroup is not configured.

In another optional manner, in the case where the key of at least one bearer is set as the secondary key, or the secondary cell group configuration information is configured, the RRC recovery message carries the first SK-Counter information.

Specifically, the network side carries the first SK-Counter in the RRC recovery message only when the KeyToUse information element of at least one RB is set to secondary and the mrdc-SecondaryCellGroup is configured.

●Method 2

The RRC recovery message carries the first SK-Counter information and the first secondary cell group configuration information, the first secondary cell group configuration information does not carry the second SK-Counter information, and the first secondary cell group configuration information is: The RRC reconfiguration message generated by the first secondary cell group.

Specifically, the RRC reconfiguration message includes second secondary cell group configuration information or secondary cell group configuration information, and in the case where the second secondary cell group or secondary cell group configuration information is configured, the second secondary cell group The RRC reconfiguration message where the configuration information or the secondary cell group configuration information is located does not carry the second SK-Counter information.

For example, when the network side sets the RRC reconfiguration message, if there is secondaryCellGroup information or mrdc-SecondaryCellGroupConfig information in the RRC reconfiguration message, the second SK-Counter information is not configured in the RRC reconfiguration message, that is, the second SK-Counter information is not configured in the RRC reconfiguration message. Two SK-Counter information is missing in the RRC reconfiguration message.

For example, if there is secondaryCellGroup information in the RRC reconfiguration message, the SN will not add the second SK-Counter information in the RRC reconfiguration message. Alternatively, if the RRC reconfiguration message is generated by the SN, the second SK-Counter information does not exist in the RRC reconfiguration message.

●Method three

The RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information.

FIG. 5 is a fourth schematic flowchart of a key generation method provided by an embodiment of the present application. As shown in FIG. 5 , the key generation method includes the following steps:

Step 501: The UE receives an RRC release (RRCRlease) message sent by the MN.

Here, the UE configured with MR-DC enters the inactive state after receiving the RRC release message.

Step 502: The UE initiates an RRC connection recovery process, and sends an RRC recovery request (RRCResumeRequest) message to the MN.

Step 503: The MN sends a secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node addition request (S-NODE ADDITION REQUEST) message to the SN.

Step 504:

A) The MN determines that in the RRC recovery message only when the KeyToUse information element of at least one bearer is set to secondary (that is, the key of at least one bearer is set to the secondary key) and the mrdc-SecondaryCellGroup information element is not configured Carry the first SK-Counter. or,

B) When the SN sets the RRC reconfiguration (RRCReconfiguration) message, if the SCG or mrdc-SecondaryCellGroup is configured, the second SK-Counter is not configured in the RRC reconfiguration message, that is, the second SK-Counter is processed as missing (absent).

Here, the RRC reconfiguration message corresponds to the mrdc-SecondaryCellGroup information element, that is, the second SK-Counter does not exist in the mrdc-SecondaryCellGroup information element.

Step 505: The SN sends a secondary node modification request acknowledgment (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node addition request acknowledgment (S-NODE ADDITION REQUEST ACKNOWLEDGE) message to the MN.

Step 506: The UE receives an RRC recovery (RRCResume) message sent by the MN, and the RRC recovery message carries the first SK-Counter, or carries two information elements of the first SK-Counter and mrdc-SecondaryCellGroup, wherein the mrdc-SecondaryCellGroup information element A second SK-Counte is not carried.

Step 507: The UE uses the first SK-Counter carried in the RRC recovery message to calculate the key of the SCG.

Step 508: The UE sends an RRC recovery complete (RRCResumeComplte) message to the MN.

FIG. 6 is a schematic structural diagram 1 of a key generation apparatus provided by an embodiment of the present application, which is applied to a terminal device. As shown in FIG. 6 , the key generation apparatus includes:

A receiving unit 601, configured to receive an RRC recovery message sent by the MN, where the RRC recovery message carries first SK-Counter information and/or secondary cell group configuration information;

a determining unit 602, configured to determine target SK-Counter information based on the RRC recovery message;

The processing unit 603 is configured to calculate the key of the secondary cell group by using the target SK-Counter information.

In an optional manner, when the RRC recovery message carries the first SK-Counter information and the secondary cell group configuration information, and the secondary cell group configuration information carries the second SK-Counter information,

The determining unit 602 is configured to determine that the target SK-Counter information is the second SK-Counter information; or, determine that the target SK-Counter information is the first SK-Counter information.

In an optional manner, when the RRC recovery message carries the first SK-Counter information and the secondary cell group configuration information, and the secondary cell group configuration information does not carry the second SK-Counter information,

The determining unit 602 is configured to determine that the target SK-Counter information is the first SK-Counter information.

In an optional manner, in the case that the RRC recovery message carries the first SK-Counter information,

The determining unit 602 is configured to determine that the target SK-Counter information is the first SK-Counter information.

In an optional manner, when the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries the second SK-Counter information,

The determining unit 602 is configured to determine that the target SK-Counter information is the second SK-Counter information.

It should be understood by those skilled in the art that the relevant description of the above-mentioned key generation apparatus in the embodiment of the present application can be understood with reference to the relevant description of the key generation method in the embodiment of the present application.

FIG. 7 is a schematic structural diagram 2 of a key generation apparatus provided by an embodiment of the present application, which is applied to a network device. As shown in FIG. 7 , the key generation apparatus includes:

The sending unit 701 is configured to send an RRC recovery message to a terminal device, where the RRC recovery message is used to determine one SK-Counter information, and the one SK-Counter information is used for the terminal device to calculate the key of the secondary cell group.

In an optional manner, the RRC recovery message carries the first SK-Counter information.

In an optional manner, in the case that the key of at least one bearer is set as the secondary key, and the secondary cell group configuration information is not configured, the RRC recovery message carries the first SK-Counter information.

In an optional manner, in the case where the key of at least one bearer is set as the secondary key, or the secondary cell group configuration information is configured, the RRC recovery message carries the first SK-Counter information.

In an optional manner, the RRC recovery message carries first SK-Counter information and first secondary cell group configuration information, the first secondary cell group configuration information does not carry second SK-Counter information, and the first secondary cell group configuration information does not carry the second SK-Counter information. The configuration information of the first secondary cell group is an RRC reconfiguration message generated by the first secondary cell group.

In an optional manner, the RRC reconfiguration message includes second secondary cell group configuration information or secondary cell group configuration information, if the second secondary cell group or secondary cell group configuration information is configured, the The second secondary cell group configuration information or the RRC reconfiguration message where the secondary cell group configuration information is located does not carry the second SK-Counter information.

In an optional manner, the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information.

Those skilled in the art should understand that the relevant description of the above-mentioned key generation apparatus in the embodiment of the present application can be understood with reference to the relevant description of the key generation method in the embodiment of the present application

FIG. 8 is a schematic structural diagram of a communication device 800 provided by an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 800 shown in FIG. 8 includes a processor 810, and the processor 810 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in FIG. 8 , the communication device 800 may further include a memory 820 . The processor 810 may call and run a computer program from the memory 820 to implement the methods in the embodiments of the present application.

The memory 820 may be a separate device independent of the processor 810 , or may be integrated in the processor 810 .

Optionally, as shown in FIG. 8 , the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by a device.

Among them, the transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include antennas, and the number of the antennas may be one or more.

Optionally, the communication device 800 may specifically be the network device in this embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For brevity, details are not repeated here. .

Optionally, the communication device 800 may specifically be the mobile terminal/terminal device in the embodiments of the present application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present application. , and will not be repeated here.

FIG. 9 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 9 , the chip 900 may further include a memory 920 . The processor 910 may call and run a computer program from the memory 920 to implement the methods in the embodiments of the present application.

The memory 920 may be a separate device independent of the processor 910 , or may be integrated in the processor 910 .

Optionally, the chip 900 may further include an input interface 930 . The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Optionally, the chip 900 may further include an output interface 940 . The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. For brevity, here No longer.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

FIG. 10 is a schematic block diagram of a communication system 1000 provided by an embodiment of the present application. As shown in FIG. 10 , the communication system 1000 includes a terminal device 1010 and a network device 1020 .

The terminal device 1010 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1020 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .

It should be understood that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.

Embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.

The embodiments of the present application also provide a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (34)

A key generation method, the method includes: The terminal device receives a radio resource control RRC recovery message sent by the master node MN, where the RRC recovery message carries the first secondary key count SK-Counter information and/or secondary cell group configuration information; The terminal device determines target SK-Counter information based on the RRC recovery message, and uses the target SK-Counter information to calculate the key of the secondary cell group. The method according to claim 1, wherein, when the RRC recovery message carries first SK-Counter information and secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information, The terminal device determines that the target SK-Counter information is the second SK-Counter information; or, The terminal device determines that the target SK-Counter information is the first SK-Counter information. The method of claim 1, wherein the RRC recovery message carries first SK-Counter information and secondary cell group configuration information, and the secondary cell group configuration information does not carry second SK-Counter information, The terminal device determines that the target SK-Counter information is the first SK-Counter information. The method according to claim 1, wherein, when the RRC recovery message carries the first SK-Counter information, The terminal device determines that the target SK-Counter information is the first SK-Counter information. The method according to claim 1, wherein, when the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information, The terminal device determines that the target SK-Counter information is the second SK-Counter information. A key generation method, the method includes: The MN sends an RRC recovery message to the terminal device, where the RRC recovery message is used to determine one SK-Counter information, and the one SK-Counter information is used by the terminal device to calculate the key of the secondary cell group. The method according to claim 6, wherein the RRC recovery message carries first SK-Counter information. The method according to claim 7, wherein the RRC recovery message carries the first SK in the case that the key of at least one bearer is set as the secondary key and the secondary cell group configuration information is not configured -Counter information. The method according to claim 7, wherein the RRC recovery message carries the first SK- Counter information. The method according to claim 6, wherein the RRC recovery message carries first SK-Counter information and first secondary cell group configuration information, and the first secondary cell group configuration information does not carry second SK-Counter information , the configuration information of the first secondary cell group is an RRC reconfiguration message generated by the first secondary cell group. The method according to claim 10, wherein the RRC reconfiguration message includes second secondary cell group configuration information or secondary cell group configuration information, and when the second secondary cell group or secondary cell group configuration information is configured , the second secondary cell group configuration information or the RRC reconfiguration message where the secondary cell group configuration information is located does not carry the second SK-Counter information. The method according to claim 6, wherein the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information. An apparatus for generating a key, applied to a terminal device, the apparatus comprising: a receiving unit, configured to receive an RRC recovery message sent by the MN, where the RRC recovery message carries the first SK-Counter information and/or the configuration information of the secondary cell group; a determining unit, configured to determine target SK-Counter information based on the RRC recovery message; A processing unit, configured to calculate the key of the secondary cell group by using the target SK-Counter information. The apparatus according to claim 13, wherein, when the RRC recovery message carries first SK-Counter information and secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information, The determining unit is configured to determine that the target SK-Counter information is the second SK-Counter information; or, determine that the target SK-Counter information is the first SK-Counter information. The apparatus according to claim 13, wherein the RRC recovery message carries first SK-Counter information and secondary cell group configuration information, and the secondary cell group configuration information does not carry second SK-Counter information, The determining unit is configured to determine that the target SK-Counter information is the first SK-Counter information. The apparatus according to claim 13, wherein, when the RRC recovery message carries the first SK-Counter information, The determining unit is configured to determine that the target SK-Counter information is the first SK-Counter information. The apparatus according to claim 13, wherein, when the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information, The determining unit is configured to determine that the target SK-Counter information is the second SK-Counter information. A key generation device, applied to network equipment, the device includes: A sending unit, configured to send an RRC recovery message to the terminal device, where the RRC recovery message is used to determine one SK-Counter information, and the one SK-Counter information is used for the terminal device to calculate the key of the secondary cell group. The apparatus according to claim 18, wherein the RRC recovery message carries first SK-Counter information. The apparatus according to claim 19, wherein the RRC recovery message carries the first SK in the case that the key of at least one bearer is set as the secondary key and the secondary cell group configuration information is not configured -Counter information. The apparatus according to claim 19, wherein in the case where the key of at least one bearer is set as a secondary key, or the secondary cell group configuration information is configured, the RRC recovery message carries the first SK- Counter information. The apparatus according to claim 18, wherein the RRC recovery message carries first SK-Counter information and first secondary cell group configuration information, and the first secondary cell group configuration information does not carry second SK-Counter information , the configuration information of the first secondary cell group is an RRC reconfiguration message generated by the first secondary cell group. The apparatus of claim 22, wherein the RRC reconfiguration message includes second secondary cell group configuration information or secondary cell group configuration information, if the second secondary cell group or secondary cell group configuration information is configured Next, the second secondary cell group configuration information or the RRC reconfiguration message where the secondary cell group configuration information is located does not carry the second SK-Counter information. The apparatus according to claim 18, wherein the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information. A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the program according to any one of claims 1 to 5 Methods. A network device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and executes any one of claims 6 to 12. Methods. A chip, comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 1 to 5. A chip, comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 6 to 12. A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 1 to 5. A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 6 to 12. A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 5. A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 6 to 12. A computer program that causes a computer to perform the method of any one of claims 1 to 5. A computer program that causes a computer to perform the method of any one of claims 6 to 12.

Images