WO2022021413A1 - Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau - Google Patents

Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau Download PDF

Info

Publication number
WO2022021413A1
WO2022021413A1 PCT/CN2020/106391 CN2020106391W WO2022021413A1 WO 2022021413 A1 WO2022021413 A1 WO 2022021413A1 CN 2020106391 W CN2020106391 W CN 2020106391W WO 2022021413 A1 WO2022021413 A1 WO 2022021413A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell group
secondary cell
counter information
information
configuration information
Prior art date
Application number
PCT/CN2020/106391
Other languages
English (en)
Chinese (zh)
Inventor
王淑坤
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/106391 priority Critical patent/WO2022021413A1/fr
Priority to CN202080104339.XA priority patent/CN116210336B/zh
Publication of WO2022021413A1 publication Critical patent/WO2022021413A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • 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.
  • 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.
  • RRC Radio Resource Control
  • Embodiments of the present application provide a method and device for generating a key, a terminal device, and a network device.
  • 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 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
  • 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
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart 1 of a key generation method provided by an embodiment of the present application.
  • FIG. 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.
  • FIG. 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.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G communication systems or future communication systems etc.
  • 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.
  • 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 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.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Networks
  • WLAN Wireless Local Area Networks
  • digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal arranged to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal” or “mobile terminal”.
  • 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.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • 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.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal (Device to Device, D2D) communication may be performed between the terminals 120 .
  • 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.
  • New Radio NR
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • 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.
  • 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.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • 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.
  • 5G 3rd Generation Partnership Project
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low-Latency Communications
  • mMTC Massive Machine-Type Communications
  • eMBB still aims at users' access to multimedia content, services and data, and its demand is growing rapidly.
  • eMBB 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.
  • E-UTRA-NR Dual Connectivity E-UTRA-NR Dual Connectivity
  • 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.
  • eNB LTE base station
  • gNB or en-gNB NR base station
  • SN secondary node
  • 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.
  • the NR base station acts as the MN, and the eLTE base station acts as the SN, connecting to the 5GC core network.
  • the eLTE base station acts as the MN, and the NR base station acts as the SN, connecting to the 5GC core network.
  • the NR base station acts as the MN, and the NR base station acts as the SN, connecting to the 5GC core network.
  • 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).
  • MCG includes a primary cell (Primary Cell, PCell) and at least one secondary cell (Secondary Cell, SCell).
  • SCG includes a special cell (Special Cell, SpCell), optionally, one or more SCells.
  • MR-DC Multi-RAT Dual Connectivity
  • RRC_INACTIVE Radio Resource Control
  • RRC_INACTIVE Radio Resource Control
  • 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.
  • 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.
  • 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.
  • the terminal device 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.
  • the indication information corresponds to "restoreSCG" in Table 1 below.
  • the key of the SCG is generated based on the key of the MN and the secondary key count (Secondary Key-Counter, SK-Counter).
  • the SK-Counter can also be called the SCG counter.
  • NCC Next Hop Chaining Counter
  • RRCRelease RRC Release
  • 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.
  • the terminal device 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.
  • the determination of the target SK-Counter information may be implemented in the following manner.
  • 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.
  • the terminal device determines the target SK-Counter The information is the first SK-Counter information.
  • the terminal device determines that the target SK-Counter information is the first SK-Counter information.
  • the terminal device determines that the target SK-Counter information is the second SK-Counter Counter information.
  • the terminal device 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.
  • RRC release RRCRlease
  • 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.
  • RRC recovery request RRCResumeRequest
  • 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.
  • S-NODE MODIFICATION REQUEST a secondary node modification request
  • S-NODE ADDITION REQUEST a secondary node addition request
  • 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.
  • S-NODE MODIFICATION REQUEST ACKNOWLEDGE a secondary node modification request acknowledgment
  • S-NODE ADDITION REQUEST ACKNOWLEDGE secondary node addition request acknowledgment
  • 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.
  • the MN 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.
  • 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.
  • the RRC recovery message carries the first SK-Counter information.
  • the RRC recovery message carries the first SK-Counter information.
  • 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.
  • the RRC recovery message carries the first SK-Counter information.
  • 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.
  • 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.
  • 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.
  • 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.
  • the SN will not add the second SK-Counter information in the RRC reconfiguration message.
  • the second SK-Counter information does not exist in the RRC reconfiguration message.
  • 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.
  • RRC release RRCRlease
  • 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.
  • RRC recovery request RRCResumeRequest
  • 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.
  • S-NODE MODIFICATION REQUEST a secondary node modification request
  • S-NODE ADDITION REQUEST a secondary node addition request
  • 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,
  • 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.
  • S-NODE MODIFICATION REQUEST ACKNOWLEDGE a secondary node modification request acknowledgment
  • S-NODE ADDITION REQUEST ACKNOWLEDGE secondary node addition request acknowledgment
  • 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.
  • RRC recovery RRCResume
  • 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.
  • the RRC recovery message carries the first SK-Counter information and the secondary cell group configuration information
  • 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.
  • the determining unit 602 is configured to determine that the target SK-Counter information is 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.
  • the RRC recovery message carries secondary cell group configuration information
  • 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.
  • 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.
  • the RRC recovery message carries the first SK-Counter information.
  • the RRC recovery message carries the first SK-Counter information.
  • the RRC recovery message carries the first SK-Counter information.
  • 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.
  • 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.
  • the RRC recovery message carries secondary cell group configuration information
  • the secondary cell group configuration information carries second SK-Counter information
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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. .
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • 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
  • 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. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • 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.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • 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.
  • 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.
  • 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.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • 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.
  • 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.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • 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.
  • 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.
  • 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 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil de génération de clé, et un dispositif terminal et un dispositif de réseau. Le procédé comprend les étapes suivantes : un dispositif terminal reçoit un message de récupération de commande de ressources radio (RRC) envoyé par un nœud maître (MN), le message de récupération de RRC comportant des premières informations de compteur de clé secondaire (compteur SK) et/ou des informations de configuration de groupe de cellules secondaires ; et le dispositif terminal détermine des informations de compteur SK cibles sur la base du message de récupération RRC, et calcule une clé d'un groupe de cellules secondaires à l'aide des informations de compteur SK cibles.
PCT/CN2020/106391 2020-07-31 2020-07-31 Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau WO2022021413A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/106391 WO2022021413A1 (fr) 2020-07-31 2020-07-31 Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau
CN202080104339.XA CN116210336B (zh) 2020-07-31 2020-07-31 一种密钥生成方法及装置、终端设备、网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/106391 WO2022021413A1 (fr) 2020-07-31 2020-07-31 Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau

Publications (1)

Publication Number Publication Date
WO2022021413A1 true WO2022021413A1 (fr) 2022-02-03

Family

ID=80036973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/106391 WO2022021413A1 (fr) 2020-07-31 2020-07-31 Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN116210336B (fr)
WO (1) WO2022021413A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066844A1 (fr) * 2022-09-29 2024-04-04 大唐移动通信设备有限公司 Procédé, dispositif et appareil de détermination de clé de sécurité côté scg, et support de stockage

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018171583A1 (fr) * 2017-03-23 2018-09-27 华为技术有限公司 Procédé, appareil, et système de configuration
WO2020029165A1 (fr) * 2018-08-09 2020-02-13 Zte Corporation Techniques de génération de clé de sécurité
WO2020065622A1 (fr) * 2018-09-27 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Reprise et reconfigurations flexibles dans des scénarios autonomes ou à double connectivité multi-rat
CN111225443A (zh) * 2018-11-27 2020-06-02 华硕电脑股份有限公司 释放无线通信中预配置的上行链路资源配置的方法和设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016042766A1 (fr) * 2014-09-19 2016-03-24 Nec Corporation Appareil pour double connectivité
EP3422799B1 (fr) * 2017-06-27 2020-08-05 Nokia Solutions and Networks Oy Procédure d'interfonctionnement lte-nr pour des configurations de porteuse partagée scg
RU2739063C1 (ru) * 2017-11-16 2020-12-21 Телефонактиеболагет Лм Эрикссон (Пабл) Полная конфигурация rrc в en-dc
US10667185B2 (en) * 2018-03-28 2020-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Method for avoiding unnecessary actions in resume procedure
CN110557849B (zh) * 2018-05-30 2021-06-22 华为技术有限公司 一种通信方法及装置
CN111373783A (zh) * 2018-08-17 2020-07-03 Oppo广东移动通信有限公司 一种信息传输方法及装置、通信设备
CN112703770B (zh) * 2019-01-11 2023-11-10 Oppo广东移动通信有限公司 一种rrc连接重建方法及装置、网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018171583A1 (fr) * 2017-03-23 2018-09-27 华为技术有限公司 Procédé, appareil, et système de configuration
WO2020029165A1 (fr) * 2018-08-09 2020-02-13 Zte Corporation Techniques de génération de clé de sécurité
WO2020065622A1 (fr) * 2018-09-27 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Reprise et reconfigurations flexibles dans des scénarios autonomes ou à double connectivité multi-rat
CN111225443A (zh) * 2018-11-27 2020-06-02 华硕电脑股份有限公司 释放无线通信中预配置的上行链路资源配置的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: ""sk-counter presence in RRC(Connection)Reconfiguration"", 3GPP TSG-RAN WG2 MEETING#107BIS, R2-1913614, 18 October 2019 (2019-10-18), XP051791607 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066844A1 (fr) * 2022-09-29 2024-04-04 大唐移动通信设备有限公司 Procédé, dispositif et appareil de détermination de clé de sécurité côté scg, et support de stockage

Also Published As

Publication number Publication date
CN116210336B (zh) 2024-07-26
CN116210336A (zh) 2023-06-02

Similar Documents

Publication Publication Date Title
WO2021203310A1 (fr) Procédé et appareil de transmission de données et équipement terminal
WO2021092860A1 (fr) Procédé et appareil de configuration de cellule, dispositif terminal et dispositif réseau
WO2020154925A1 (fr) Procédé et appareil permettant de coordonner une configuration de mesure, dispositif de réseau et terminal
WO2021087678A1 (fr) Procédé et appareil de gestion d'état de cellule, dispositif terminal et dispositif réseau
WO2020227870A1 (fr) Procédé et appareil de commutation, et dispositif de communication
WO2020258192A1 (fr) Procédé et appareil de transmission de données, ainsi que terminal
WO2022061872A1 (fr) Procédé et appareil de transmission de petites données et dispositif de terminal
WO2021114206A1 (fr) Procédé et appareil de mesure de cli, dispositif terminal et dispositif de réseau
WO2020258191A1 (fr) Procédé et appareil de contrôle d'accès et terminal
WO2020227860A1 (fr) Procédé et dispositif de détermination de fonctionnalités de terminal, et terminal
US11805563B2 (en) Wireless communication method and base station
WO2020082248A1 (fr) Procédé et dispositif de commande de mobilité d'un terminal, et terminal
WO2021212258A1 (fr) Procédé et appareil permettant de rapporter des informations d'indication, dispositif terminal et dispositif réseau
WO2022021413A1 (fr) Procédé et appareil de génération de clé, et dispositif terminal et dispositif de réseau
WO2021026717A1 (fr) Procédé et appareil de coordination de ressources, et dispositif terminal
WO2021087898A1 (fr) Procédé et appareil de conversion d'état, et dispositif de communication
WO2020061995A1 (fr) Procédé et appareil de transmission d'informations, terminal et dispositif de réseau
TW202007199A (zh) 一種核心網選擇方法及裝置、終端設備、網路設備
WO2022236835A1 (fr) Procédé et appareil de détermination d'un comportement d'un dispositif terminal, dispositif terminal et dispositif de réseau
WO2022109955A1 (fr) Procédé et appareil d'indication d'informations, dispositif terminal et dispositif de réseau
WO2022183336A1 (fr) Procédé et appareil de détermination d'intervalle de mesure, et dispositif terminal
WO2022205374A1 (fr) Procédé et appareil de traitement de défaillance de liaison radio, et dispositif de communication
WO2021092755A1 (fr) Procédé et appareil permettant de rapporter des informations auxiliaires, dispositif terminal et dispositif de réseau
WO2022021023A1 (fr) Procédé et appareil d'indication d'informations, dispositif terminal et dispositif de réseau
WO2020258182A1 (fr) Procédé de transmission de données, appareil, et dispositif de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20947629

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20947629

Country of ref document: EP

Kind code of ref document: A1