CN116210336A

CN116210336A - Key generation method and device, terminal equipment and network equipment

Info

Publication number: CN116210336A
Application number: CN202080104339.XA
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2023-06-02
Also published as: WO2022021413A1

Abstract

The embodiment of the application provides a key generation method and device, terminal equipment and network equipment, wherein the method comprises the following steps: the method comprises the steps that terminal equipment receives a Radio Resource Control (RRC) recovery message sent by a Master Node (MN), wherein the RRC recovery message carries first auxiliary key count (SK-Counter) information and/or auxiliary cell group configuration information; and the terminal equipment determines target SK-Counter information based on the RRC recovery message, and calculates a key of the secondary cell group by using the target SK-Counter information.

Description

Key generation method and device, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a key generation method and device, terminal equipment and network equipment.

Background

Currently, a Secondary Key-Counter (SK-Counter) is configured in a radio resource control (Radio Resource Control, RRC) recovery message, and an SK-Counter is also configured in Secondary cell group configuration information (mrdc-Secondary cell group), how to use or how to configure the two SK-counters is a problem that needs to be clarified.

Disclosure of Invention

The embodiment of the application provides a key generation method and device, terminal equipment and network equipment.

The key generation method provided by the embodiment of the application comprises the following steps:

the method comprises the steps that a terminal device receives RRC recovery information sent by an MN, wherein the RRC recovery information carries first SK-Counter information and/or auxiliary cell group configuration information;

and the terminal equipment determines target SK-Counter information based on the RRC recovery message, and calculates a key of the secondary cell group by using the target SK-Counter information.

the MN sends an RRC recovery message to the terminal equipment, wherein the RRC recovery message is used for determining one piece of SK-Counter information, and the one piece of SK-Counter information is used for the terminal equipment to calculate the key of the secondary cell group.

The key generation device provided by the embodiment of the application is applied to terminal equipment, and the device comprises:

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

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

and the processing unit is used for calculating the key of the secondary cell group by using the target SK-Counter information.

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

and the sending unit is used for sending an RRC recovery message to the terminal equipment, wherein the RRC recovery message is used for determining one piece of SK-Counter information, and the one piece of SK-Counter information is used for the terminal equipment to calculate the key of the secondary cell group.

The terminal equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the key generation method.

The network device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the key generation method.

The chip provided by the embodiment of the application is used for realizing the key generation method.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the key generation method.

The computer readable storage medium provided in the embodiments of the present application is used for storing a computer program, where the computer program makes a computer execute the above-mentioned key generation method.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the key generation method.

The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the key generation method.

By the technical scheme, on one hand, how the terminal equipment uses the SK-Counter configured by the network side is clarified, and on the other hand, how the network side configures the SK-Counter is clarified, so that the secret keys used by the terminal equipment and the network side are consistent, and guarantee is provided for subsequent normal communication.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

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

fig. 2 is a schematic flow chart of a key generation method according to an embodiment of the present application;

fig. 3 is a second flowchart of a key generation method according to an embodiment of the present application;

fig. 4 is a flowchart of a key generation method according to an embodiment of the present application;

Fig. 5 is a flowchart of a key generation method provided in an embodiment of the present application;

fig. 6 is a schematic diagram of the structural composition of the key generating device provided in the embodiment of the present application;

fig. 7 is a schematic diagram II of the structural composition of the key generating device according to the embodiment of the present application;

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

FIG. 9 is a schematic block diagram of a chip of an embodiment of the present application;

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

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), systems, 5G communication systems, future communication systems, or the like.

Exemplary, a communication system 100 to which embodiments of the present application apply 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, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle 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, etc.

The communication system 100 further includes at least one terminal 120 located within the coverage area of the network device 110. "terminal" as used herein includes, but is not limited to, connection via wireline, such as via public-switched telephone network (Public Switched Telephone Networks, PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminals arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolved PLMN, etc.

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

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

Fig. 1 illustrates one network device and two terminals, alternatively, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within a coverage area, which is not limited in this embodiment.

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

It should be understood that a device having a communication function in a network/system in an embodiment of the present application 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 communication functions, where the network device 110 and the terminal 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In order to facilitate 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 the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life business, the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced mobile Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).

On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the mobile operators from early investment in LTE, a working mode of tight coupling (tight interworking) between LTE and NR is proposed.

Dual connection (Dual Connectivity, DC) architecture

To enable 5G network deployment and commercial application as soon as possible, the third generation partnership project (3rd Generation Partnership Project,3GPP) first completes the first 5G version, E-UTRA and NR dual connectivity (E-UTRA-NR Dual Connectivity, EN-DC). In EN-DC, an LTE base station (eNB) serves as a Master Node (MN), and an NR base station (gNB or EN-gNB) serves as a Secondary Node (SN), which is connected to an EPC core network. In the later stages of 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, NR base station is used as MN, eLTE base station is used as SN, and is connected with 5GC core network. In 5GC-EN-DC, an eLTE base station is used as MN, an NR base station is used as SN, and a 5GC core network is connected. In NR DC, NR base station is used as MN, NR base station is used as SN, and connected with 5GC core network.

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

The technical scheme of the embodiment of the application can be applied to a dual-connection architecture, such as a Multi-RAT dual-connection (Multi-RAT Dual Connectivity, MR-DC) architecture.

RRC state

5G for the purposes of reducing air interface signaling and fast recovery of radio connections, fast recovery of data traffic, a new radio resource control (Radio Resource Control, RRC) state, namely an RRC INACTIVE (RRC_INACTIVE) state, is defined. This state is different from the RRC IDLE (rrc_idle) state and the RRC ACTIVE (rrc_active) state. Wherein,

1) Rrc_idle state (simply referred to as IDLE state): mobility is cell selection reselection based on terminal equipment, paging is initiated by a Core Network (CN), and paging areas are configured by the CN. The base station side has no terminal equipment context and no RRC connection.

2) Rrc_connected state (CONNECTED state for short): there is an RRC connection and there is a terminal device context at the base station side and the terminal device side. The network side knows that the location of the terminal device is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the terminal device and the base station.

3) Rrc_inactive state (simply referred to as INACTIVE state): mobility is cell selection reselection based on terminal equipment, connection between CN-NR exists, terminal equipment context exists on a certain base station, paging is triggered by RAN, paging area based on RAN is managed by RAN, network side knows that the position of terminal equipment is based on paging area level of RAN.

When the terminal device configured with the MR-DC enters the inactive state, the terminal device maintains the configuration information of the MR-DC, but releases the SCG configuration when the terminal device initiates RRC connection restoration. The terminal device may be instructed to resume the previous SCG configuration by adding an indication information corresponding to "restogcg" in table 1 below in an RRC resume (rrresume) message.

TABLE 1

In MR-DC, the Key of the SCG is generated based on the Key of the MN and a Secondary Key-Counter (SK-Counter), which may also be referred to herein as the SCG Counter. In the RRC connection recovery procedure, the terminal device generates keys for MSG4 and all subsequent uplink and downlink messages and data using the next hop link count (Next hop Chaining Counter, NCC) configured in the RRC release (RRCRelease) message. 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-second cell group), and how to use or configure the two SK-counters is a problem that needs to be clear.

Fig. 2 is a schematic flow chart of a key generation method according to an embodiment of the present application, as shown in fig. 2, the key generation method includes the following steps:

step 201: and the terminal equipment receives the RRC restoration message sent by the MN, wherein the RRC restoration message carries the first SK-Counter information and/or the configuration information of the secondary cell group.

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

Step 202: and the terminal equipment determines target SK-Counter information based on the RRC recovery message, and calculates a key of the secondary cell group by using the target SK-Counter information.

In the embodiment of the application, the determination of the target SK-Counter information can be achieved in the following manner.

● Mode one

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, 1) the terminal equipment determines the target SK-Counter information as the second SK-Counter information; or 2) the terminal equipment determines the target SK-Counter information as the first SK-Counter information.

● Mode two

And under the condition that 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 equipment determines the target SK-Counter information as the first SK-Counter information.

● Mode three

And under the condition that the RRC recovery message carries first SK-Counter information, the terminal equipment determines the target SK-Counter information as the first SK-Counter information.

● Mode four

And under the condition that the RRC recovery message carries secondary cell group configuration information and the secondary cell group configuration information carries second SK-Counter information, the terminal equipment determines the target SK-Counter information as the second SK-Counter information.

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

Fig. 3 is a second flowchart of a key generation method according to an embodiment of the present application, as shown in fig. 3, where the key generation method includes the following steps:

step 301: the UE receives an RRC release (RRCRelease) message sent by the MN.

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

Step 302: the UE initiates an RRC connection recovery procedure 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 acknowledgement (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node addition request acknowledgement (S-NODE ADDITION REQUEST ACKNOWLEDGE) message to the MN.

Step 305: the UE receives an RRC recovery (RRCResume) message sent by the MN, the RRC recovery message carrying the first SK-Counter and the mrdc-second CellGroup two information units. Wherein the mrdc-second cell group information unit carries a second SK-Counter.

Step 306: the UE calculates the key of the SCG using the second SK-Counter and ignores the first SK-Counter. Alternatively, the UE calculates the key of the SCG using the first SK-Counter and ignores the second SK-Counter.

Step 307: the UE sends an RRC restoration complete (rrcresmeecomplte) message to the MN.

Fig. 4 is a flowchart third of a key generation method according to an embodiment of the present application, as shown in fig. 4, where the key generation method includes the following steps:

step 401: the MN sends an RRC recovery message to the terminal equipment, wherein the RRC recovery message is used for determining one piece of SK-Counter information, and the one piece of SK-Counter information is used for the terminal equipment to calculate the key of the secondary cell group.

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

In this embodiment of the present application, the RRC recovery message is used to determine an SK-Counter information, so that ambiguity of the terminal device to the SK-Counter information may be avoided, and the key of the secondary cell group may be calculated directly using the SK-Counter information. The network side can ensure that the RRC recovery message can only determine one SK-Counter information in the following manner.

● Mode one

The RRC recovery message carries first SK-Counter information.

In an alternative manner, when at least one bearer key is set as a secondary key and 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 if there is at least one RB KeyToUse cell set to secondary and mrdc-secondary cell group is not configured.

In another alternative, in a case that at least one bearer key is set as a secondary key or 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 if there is at least one RB KeyToUse cell set to secondary and mrdc-secondary cell group is configured.

● Mode two

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

Specifically, 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 RRC reconfiguration message in which the second secondary cell group configuration information or 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 the second information of the second cell group or the mrdc-second cell group pconfig information exists 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 absent in the RRC reconfiguration message.

For example: if there is second SK-Counter 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 is not present in the RRC reconfiguration message.

● Mode 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 flowchart of a key generation method according to an embodiment of the present application, as shown in fig. 5, where the key generation method includes the following steps:

step 501: the UE receives an RRC release (RRCRelease) message sent by the MN.

Step 502: the UE initiates an RRC connection recovery procedure 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 to carry the first SK-Counter in the RRC recovery message when there is at least one bearer KeyToUse cell set to secondary (i.e., at least one bearer key is set to a secondary key) and the mrdc-second cellgroup information element is not configured. Or,

b) The SN does not configure the second SK-Counter in the RRC reconfiguration message, i.e., the second SK-Counter is treated as absent (absent), if SCG or mrdc-second cellgroup is configured at the time of setting the RRC reconfiguration message.

Here, the RRC reconfiguration message corresponds to the mrdc-second cell group information element, that is, the second SK-Counter is not present in the mrdc-second cell group information element.

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

Step 506: the UE receives an RRC recovery (RRCResume) message sent by the MN, wherein the RRC recovery message carries a first SK-Counter or carries two information units of the first SK-Counter and the mrdc-second cell group, and the mrdc-second cell group information unit does not carry a second SK-Counter.

Step 507: the UE calculates the key of the SCG by using the first SK-Counter carried in the RRC recovery message.

Step 508: the UE sends an RRC restoration complete (rrcresmeecomplte) message to the MN.

Fig. 6 is a schematic structural diagram of a key generating device according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 6, and the key generating device includes:

a receiving unit 601, configured to receive an RRC restoration message sent by the MN, where the RRC restoration 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;

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

In an alternative, 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 602 is configured to determine that the target SK-Counter information is the second SK-Counter information; or determining the target SK-Counter information as the first SK-Counter information.

In an alternative, 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 602 is configured to determine the target SK-Counter information as the first SK-Counter information.

In an alternative, in the case where the RRC recovery message carries first SK-Counter information,

In an alternative, 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 602 is configured to determine the target SK-Counter information as the second SK-Counter information.

It should be understood by those skilled in the art that the above description of the key generation apparatus of the embodiments of the present application may be understood with reference to the description of the key generation method of the embodiments of the present application.

Fig. 7 is a schematic diagram ii of the structural composition of the key generating device provided in the embodiment of the present application, which is applied to a network device, as shown in fig. 7, where the key generating device includes:

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

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

In an alternative manner, in a case that at least one bearer key is set as a secondary key or 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, where the first secondary cell group configuration information does not carry second SK-Counter information, and the first secondary cell group configuration information 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, and if the second secondary cell group or secondary cell group configuration information is configured, the RRC reconfiguration message in which the second secondary cell group configuration information or secondary cell group configuration information is located does not carry the second SK-Counter information.

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

It will be appreciated by those skilled in the art that the above description of the key generation apparatus of the embodiments of the present application may be understood with reference to the description of the key generation method of the embodiments of the present application

Fig. 8 is a schematic structural diagram of a communication device 800 provided in an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 800 shown in fig. 8 includes a processor 810, where the processor 810 may call and execute 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 also include a memory 820. Wherein the processor 810 may call and run a computer program from the memory 820 to implement the methods in embodiments of the present application.

Wherein the memory 820 may be a separate device from the processor 810 or may be integrated into 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, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Among other things, transceiver 830 may include a transmitter and a receiver. Transceiver 830 may further include antennas, the number of which may be one or more.

Optionally, the communication device 800 may be specifically a network device in the embodiment of the present application, and the communication device 800 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 800 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 800 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 9 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 900 shown in fig. 9 includes a processor 910, and the processor 910 may call and execute a computer program from a memory to implement the method in the embodiments of the present application.

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

Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.

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

Optionally, the chip 900 may also include an output interface 940. Wherein the processor 910 may control the output interface 940 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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

Fig. 10 is a schematic block diagram of a communication system 1000 provided in 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 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1020 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may 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 programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware decoding processor or in a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

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

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

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

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A key generation method, the method comprising:

the method comprises the steps that terminal equipment receives a Radio Resource Control (RRC) recovery message sent by a Master Node (MN), wherein the RRC recovery message carries first auxiliary key count (SK-Counter) information and/or auxiliary cell group configuration information;

and the terminal equipment determines target SK-Counter information based on the RRC recovery message, and calculates a key of the secondary cell group by using the target 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 carries second SK-Counter information,

the terminal equipment determines the target SK-Counter information as the second SK-Counter information; or,

the terminal equipment determines the target SK-Counter information as 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 equipment determines the target SK-Counter information as the first SK-Counter information.
The method of claim 1, wherein, in the case where the RRC recovery message carries first SK-Counter information,

the terminal equipment determines the target SK-Counter information as the first SK-Counter information.
The method of claim 1, wherein the RRC recovery message carries secondary cell group configuration information, and the secondary cell group configuration information carries second SK-Counter information,

the terminal equipment determines the target SK-Counter information as the second SK-Counter information.
A key generation method, the method comprising:

the MN sends an RRC recovery message to the terminal equipment, wherein the RRC recovery message is used for determining one piece of SK-Counter information, and the one piece of SK-Counter information is used for the terminal equipment to calculate the key of the secondary cell group.
The method of claim 6, wherein the RRC recovery message carries first SK-Counter information.
The method of claim 7, wherein the RRC recovery message carries the first SK-Counter information in a case where at least one bearer key is set as a secondary key and secondary cell group configuration information is not configured.
The method of claim 7, wherein the RRC recovery message carries the first SK-Counter information if there is at least one bearer key set as a secondary key or secondary cell group configuration information is configured.
The method of claim 6, wherein 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 is an RRC reconfiguration message generated by the first secondary cell group.
The method of claim 10, wherein the RRC reconfiguration message includes second secondary cell group configuration information or secondary cell group configuration information, and in a case where the second secondary cell group or secondary cell group configuration information is configured, the RRC reconfiguration message in which the second secondary cell group configuration information or secondary cell group configuration information is located does not carry the second SK-Counter information.
The method of claim 6, wherein the RRC recovery message carries secondary cell group configuration information that carries second SK-Counter information.
A key generation apparatus applied to a terminal device, the apparatus comprising:

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

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

and the processing unit is used for calculating the key of the secondary cell group by using the target SK-Counter information.
The apparatus of 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 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 determining the target SK-Counter information as the first SK-Counter information.
The apparatus of 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 the target SK-Counter information as the first SK-Counter information.
The apparatus of claim 13, wherein, in the case where the RRC recovery message carries first SK-Counter information,

the determining unit is configured to determine the target SK-Counter information as the first SK-Counter information.
The apparatus of claim 13, wherein 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 the target SK-Counter information as the second SK-Counter information.
A key generation apparatus for use with a network device, the apparatus comprising:

and the sending unit is used for sending an RRC recovery message to the terminal equipment, wherein the RRC recovery message is used for determining one piece of SK-Counter information, and the one piece of SK-Counter information is used for the terminal equipment to calculate the key of the secondary cell group.
The apparatus of claim 18, wherein the RRC recovery message carries first SK-Counter information.
The apparatus of claim 19, wherein the RRC recovery message carries the first SK-Counter information if there is at least one bearer key set as a secondary key and secondary cell group configuration information is not configured.
The apparatus of claim 19, wherein the RRC recovery message carries the first SK-Counter information if there is at least one bearer key set to a secondary key or secondary cell group configuration information is configured.
The apparatus of claim 18, wherein the RRC recovery message carries first SK-Counter information and first secondary cell group configuration information, the first secondary cell group configuration information not carrying second SK-Counter information, the first secondary cell group configuration information being an RRC reconfiguration message generated by a 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, and if the second secondary cell group or secondary cell group configuration information is configured, the RRC reconfiguration message in which the second secondary cell group configuration information or secondary cell group configuration information is located does not carry the second SK-Counter information.
The apparatus of claim 18, wherein the RRC recovery message carries secondary cell group configuration information that carries second SK-Counter information.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to any of claims 1 to 5.
A network device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 6 to 12.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 5.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 6 to 12.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 5.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 6 to 12.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 5.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 6 to 12.
A computer program which causes a computer to perform the method of any one of claims 1 to 5.
A computer program which causes a computer to perform the method of any of claims 6 to 12.