WO2019095240A1 - Procédé et appareil de transmission de données - Google Patents

Procédé et appareil de transmission de données Download PDF

Info

Publication number
WO2019095240A1
WO2019095240A1 PCT/CN2017/111469 CN2017111469W WO2019095240A1 WO 2019095240 A1 WO2019095240 A1 WO 2019095240A1 CN 2017111469 W CN2017111469 W CN 2017111469W WO 2019095240 A1 WO2019095240 A1 WO 2019095240A1
Authority
WO
WIPO (PCT)
Prior art keywords
key
terminal
message
network device
data
Prior art date
Application number
PCT/CN2017/111469
Other languages
English (en)
Chinese (zh)
Inventor
王宏
李秉肇
柴丽
张戬
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/111469 priority Critical patent/WO2019095240A1/fr
Publication of WO2019095240A1 publication Critical patent/WO2019095240A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a data transmission method and apparatus.
  • a terminal when a terminal needs to perform data transmission with a network device (for example, a base station), the terminal and the network The device needs to establish a Radio Resource Control (RRC) connection before the data can be transmitted between the terminal and the network device.
  • RRC Radio Resource Control
  • the terminal establishes a connection with the network device through the control plane, thereby establishing a bearer of the user plane, and then the user plane starts to transmit data.
  • the terminal establishes an RRC connection with the network device for a long time, which causes data to be transmitted in time, which increases the delay of data transmission.
  • EDT Early Data Transmission
  • CP control plane
  • UP user plane
  • RRC connection Release RRC connection Release
  • NCC Next Hop Chaining Count
  • NCC 1 is used by the terminal to generate the key K eNB
  • K RRCint , K RRCenc , K UPint , K UPenc , K Upenc are generated by the K eNB for encryption
  • the key for transmitting the uplink data in the random access process, the RRC connection release message also carries the suspension indication information, which is used to indicate that the terminal enters the RRC connection suspension state (Suspended).
  • the suspension indication information which is used to indicate that the terminal enters the RRC connection suspension state (Suspended).
  • Step 100 The terminal receives a system message sent by the base station, where the system message carries a random access resource configuration for indicating early data transmission.
  • Step 101 The terminal sends a random access preamble (preamble) to the base station according to the received random access resource configuration for indicating early transmission of the data.
  • the preamble is a physical random access channel (PRACH). Or transmitted on a narrowband physical random access channel (NPRACH). This message can also be called message 1 (message1, Msg1).
  • the terminal indicates to the base station that it needs to send uplink data in the random access procedure by sending a random access preamble.
  • PRACH physical random access channel
  • NPRACH narrowband physical random access channel
  • Step 102 The base station sends a random access response (RAR) message to the terminal according to the random access preamble sent by the UE.
  • RAR random access response
  • This message can also be called message 2 (message2, Msg2).
  • the uplink grant (UL Grant) allocated to the terminal in the RAR message is generally 56 bits or 88 bits, and is used for the terminal to send the message 3 (message 3, Msg3).
  • the Msg3 includes an RRC Connection Resume Request message and uplink data, or the Msg3 includes a new RRC message and uplink data introduced for transmitting data in a random access procedure. If the terminal sends uplink data in Msg3, it needs to request more uplink resources in order to make the base station aware. The channel terminal needs to send data in Msg3, and the terminal can indicate it by Preamble code.
  • the Preamble code is divided into two groups, the first group is used to indicate that the data is sent in the Msg3, and the second group is not used to indicate that the data is sent in the Msg3. If the base station detects that the Preamble sent by the terminal belongs to the first group, the base station determines that the terminal needs to be in the The Msg3 sends the data, and then allocates more uplink resources to the terminal in the RAR message.
  • the base station determines that the terminal does not need to send data in the Msg3, and then allocates the data to the terminal in the RAR message.
  • An uplink resource carrying 56 bits or 88 bits of data.
  • step 102 when the terminal receives a large UL Grant, the terminal restores the context configuration information (Context) of the terminal, such as SRB, DRB, UE Security Context, and the like.
  • Context context configuration information
  • the larger UL Grant refers to that the size of the uplink resource scheduled by the UL Grant is not less than the uplink resource size (Size) required by the Msg3.
  • Step 103 When the terminal receives a large UL Grant, the terminal sends the Msg3 including the uplink data to the base station by using the UL Grant.
  • the uplink data is carried on the recovered DRB (ie, DTCH), and is encrypted by using the encryption algorithm and the above K UPenc .
  • the RRC message in the Msg3 is carried on the recovered SRB0 (ie, CCCH), and the uplink data and the RRC message are in the MAC.
  • the layers are multiplexed to form a MAC PDU, Msg3.
  • the RRC message carries the Resume ID, shortResumeMAC-I.
  • the terminal may indicate in the message 3 to the base station whether the uplink data carried in the message 3 is the last data packet. If the terminal indicates that the uplink data carried in the message 3 is the last data packet, the base station may release the RRC connection of the terminal. If the terminal indicates that the uplink data carried in the message 3 is not the last data packet, the base station may establish an RRC connection for the terminal, that is, send an RRC Connection Resume message or an RRC Connection Setup message to the terminal. This situation is generally referred to as Fall back, which is to fall back to the original random access procedure.
  • the uplink data included in Msg3 may be a packet with a small amount of data such as a "heartbeat" packet.
  • the uplink data sent by the terminal is transmitted in a Dedicated Traffic Channel (DTCH) through a Data Radio Bearer (DRB) of the user plane.
  • DTCH Dedicated Traffic Channel
  • DRB Data Radio Bearer
  • Step 104 The base station sends a User Equipment (UE) context recovery request (Context Resume Request) message to the Mobility Management Entity (MME).
  • UE User Equipment
  • MME Mobility Management Entity
  • Step 105 The MME requests the serving gateway (S-GW) to modify the bearer. This step is an optional step.
  • Step 106 The MME sends a UE Context Resume Response (UE Context Resume Response) message to the base station.
  • UE Context Resume Response UE Context Resume Response
  • Step 107 The base station decrypts the received uplink data in the Msg3, and forwards the decrypted uplink data to the S-GW.
  • the base station recovers the context information of the UE according to the received UE uplink and downlink recovery response message, and processes the received uplink data in step 103, for example, processing according to the configuration of the DTCH of the uplink data in the RLC and the PDCP, including the RLC and the PDCP packet header.
  • the PDCP layer performs decryption or the like, and transmits the processed data to the S-GW.
  • Step 108 The S-GW sends downlink data to the base station. This step is an optional step.
  • the S-GW has downlink data to be sent to the terminal, it can be sent to the base station through this step, and the base station sends the terminal to the terminal in the next step.
  • Step 109 The base station sends Msg4 to the terminal.
  • the Msg4 includes a Contention Resolution message and an RRC message. If step 108 has The downlink data is sent to the base station, and Msg4 optionally includes downlink data.
  • the RRC message may be an RRC Connection Release message, indicating that no data needs to be sent after Msg4, or the RRC message may be a new RRC message introduced by data early transmission.
  • the conflict resolution message is a MAC CE, the RRC message is carried in the DCCH, and the downlink data is carried in the DTCH.
  • the step of the step 109 may be that the base station first sends a conflict resolution message to the terminal, and then sends an RRC message and optional downlink data to the terminal, that is, the conflict resolution message is sent to the terminal when the remaining content is different.
  • the terminal sends uplink data to the base station in the message 3 of the random access procedure, thereby reducing the delay of uplink data transmission, reducing power consumption and resource consumption of excessive signaling interaction, and improving resource utilization efficiency.
  • the network side cannot decrypt the uplink data sent by the terminal, so that the terminal fails to send the uplink data.
  • the purpose of the embodiments of the present application is to provide a data transmission method and apparatus, which are used to solve the problem that a terminal fails to send uplink data.
  • an embodiment of the present application provides a data transmission method, including:
  • the terminal receives the first message from the second network device, where the first message is used to release the terminal air interface connection, and the first message includes a first derivation parameter;
  • the terminal initiates a random access procedure to the first network device
  • the terminal receives a second message from the first network device, where the second message is used to restore an air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the terminal performs key update only according to the first derivation parameter sent by the second network device, acquires the first key, and uses the first data encrypted by the first user key to decrypt the first data and
  • the second data is not updated according to the second derivation parameter sent by the first network device, so that the terminal can determine the derivation parameter used for performing the key update when obtaining the first derivation parameter and the second derivation parameter. Therefore, the encryption key used by the terminal does not match the key used by the first network device, and the terminal fails to send data.
  • the first key and the second key are the same.
  • the first data and the second data are the same.
  • the order in which the terminal initiates a random access procedure to the first network device and the terminal acquires the second key is not limited.
  • the terminal ignores the second derivation parameter.
  • the ignoring the second derivation parameter by the terminal may be understood as: after receiving the second derivation parameter, updating the first key without using the second derivation parameter.
  • the second message further includes a first indication, where the first indication is used to indicate that the second derivation parameter is ignored.
  • the first network device instructs the terminal to ignore the second derivation parameter by using the first indication information, and the terminal ignores the second derivation parameter when performing the key update, thereby implementing the encryption key of the encrypted data and the first network device.
  • the key used is matched to improve the success rate of the terminal transmitting uplink data.
  • the acquiring, by the terminal, the first key includes:
  • the terminal acquires the first key if the size of the uplink resource allocated to the terminal in the random access process is greater than a threshold.
  • the threshold may be 56 bits, or 88 bits.
  • the second message further includes a second indication, where the second indication is used to indicate:
  • the partial resetting the current PDCP entity of the terminal may cause the foregoing first data not to be lost.
  • an embodiment of the present application provides a communication apparatus, where the communication apparatus includes a memory, a transceiver, and a processor, wherein: the memory is configured to store an instruction; the processor is configured to perform, according to an instruction to execute the memory storage, and control the transceiver. Signal reception and signal transmission, the communication device is operative to perform the method in any of the possible aspects of the first aspect or the first aspect described above when the processor executes the instruction stored in the memory.
  • the embodiment of the present application provides a communication device, which is used to implement any one of the foregoing first aspect or the first aspect, including a corresponding functional module, for example, including a processing unit, a receiving unit, a sending unit, and the like. Used to implement the steps in the above methods.
  • an embodiment of the present application provides a computer readable storage medium, where the computer storage medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the first Aspect or method of any of the possible aspects of the first aspect.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform the method in any one of the foregoing first aspect or the first aspect.
  • an embodiment of the present application provides a chip, where the chip is connected to a memory, for reading and executing a software program stored in the memory, to implement any of the foregoing first aspect or the first aspect.
  • the method in the design is not limited to:
  • a data transmission method includes:
  • the terminal receives the first message from the second network device, where the terminal stores a second key, the first message is used to release the terminal air interface connection, and the first message includes a first derivation parameter;
  • the terminal initiates a random access procedure to the first network device
  • the terminal receives a second message from the first network device, where the second message is used to restore an air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the terminal performs key update only according to the second derivation parameter sent by the first network device, acquires the first key, and uses the first data encrypted by the first user face key to be deduced by the first key,
  • the key update is not performed according to the first derivation parameter sent by the second network device, so that when the terminal obtains the first derivation parameter and the second derivation parameter, the terminal can determine the derivation parameter used for performing the key update, thereby avoiding the terminal use.
  • Encryption key with first The key used by the network device does not match, causing the terminal to fail to send data.
  • the first key and the second key are the same.
  • the terminal ignores the first derivation parameter.
  • the ignoring the first derivation parameter by the terminal may be understood as: after receiving the first derivation parameter, updating the first key without using the first derivation parameter.
  • the terminal does not send the first data in the random access process, or the terminal does not The first derivation parameter acquires the first key.
  • the threshold may be 56 bits, or 88 bits, or may be the size of message 3, wherein the message 3 includes an RRC message and the first data.
  • an embodiment of the present application provides a communication device, where the communication device includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction; the processor is configured to execute the instruction stored in the memory, and control the transceiver to perform Signal reception and signal transmission, when the processor executes an instruction stored in the memory, the communication device is operative to perform the method in any of the possible aspects of the seventh aspect or the seventh aspect described above.
  • the ninth aspect the embodiment of the present application provides a communication device, which is used to implement any one of the foregoing seventh or seventh aspects, including a corresponding function module, for example, including a processing unit, a receiving unit, a sending unit, and the like. Used to implement the steps in the above methods.
  • the embodiment of the present application provides a computer readable storage medium, where the computer readable medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the seventh Aspect or method of any of the possible aspects of the seventh aspect.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform the method in any one of the seventh aspect or the seventh aspect. .
  • the embodiment of the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, to implement any one of the seventh aspect or the seventh aspect. Possible methods in design.
  • a thirteenth aspect a data transmission method, comprising:
  • the first network device receives, from the second network device, a first key, a first derivation parameter, and a first indication, where the first key is obtained according to the second key and the first derivation parameter, the second The key is a key used by the terminal and the second network device, and the first indication is used to indicate that a key update is required;
  • the first network device sends a second message to the terminal in a random access process, where the second message is used to restore the air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the first network device acquires a third key, and the third key is obtained according to the first key and the second derivation parameter.
  • the first network device After the first network device receives the first key from the second network device, the first network device obtains the third key according to the first key and the second derivation parameter, and instructs the terminal to perform key update, thereby causing the terminal to The encryption key used matches the key used by the first network device to avoid the problem that the terminal fails to send data.
  • the meaning of indicating that the key update needs to be performed may be understood as: the message sent by the second network device to the terminal for releasing the air interface connection of the terminal carries the first derivation parameter.
  • the second message further includes a second indication, where the second indication is used to indicate:
  • the partially resetting the current PDCP entity of the terminal may cause the first data not to be lost.
  • the embodiment of the present application provides a communication apparatus, where the communication apparatus includes a memory, a communication interface, and a processor, wherein: the memory is configured to store an instruction; the processor is configured to control the communication interface according to the instruction for executing the memory storage. Signal reception and signal transmission are performed, and when the processor executes an instruction stored in the memory, the communication device is configured to perform the method in any of the above-described thirteenth or thirteenth aspects.
  • the embodiment of the present application provides a communication device, which is used to implement any one of the thirteenth or thirteenth aspects, including a corresponding functional module, for example, including a processing unit, a receiving unit, and a sending Units and the like are respectively used to implement the steps in the above method.
  • the embodiment of the present application provides a computer readable storage medium, where the computer storage medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the foregoing A method of any of the thirteenth or thirteenth aspects of the possible design.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform the method in any one of the foregoing first aspect or the first aspect. .
  • an embodiment of the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, to implement the thirteenth aspect or the thirteenth aspect.
  • a possible approach in design is possible.
  • a data transmission method includes:
  • the first network device receives, from the second network device, a first key, a first derivation parameter, the first key is obtained according to the second key and the first derivation parameter, and the second key is a terminal a key used with the second network device;
  • the first network device sends a second message to the terminal in a random access process, where the second message is used to restore the air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the first network device acquires a third key, and the third key is obtained according to the first key and the second derivation parameter.
  • the first network device After the first network device receives the first key from the second network device, if the first data is received from the terminal, the third key is obtained according to the first key and the second derivation parameter. Therefore, the encryption key used by the terminal is matched with the key used by the first network device, so as to avoid the problem that the terminal fails to send data.
  • the first network device may send the second message.
  • the first message further includes a first indication, where the first indication is used to indicate:
  • the partially resetting the current PDCP entity of the terminal may cause the first data not to be lost.
  • the embodiment of the present application provides a communication device, where the communication device includes a memory, a communication interface, and a processor, where: the memory is used to store an instruction; the processor is configured to control the communication interface according to the instruction to execute the memory storage. Signal reception and signal transmission are performed, and when the processor executes an instruction stored in the memory, the communication device is configured to perform the method in any of the nineteenth or nineteenth aspects of the above.
  • the embodiment of the present application provides a communication device, which is used to implement any one of the nineteenth or nineteenth aspects, including a corresponding functional module, for example, including a processing unit, a receiving unit, Sending unit Etc., respectively, are used to implement the steps in the above method.
  • the embodiment of the present application provides a computer readable storage medium, where the computer storage medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the above A method of any of the nineteenth or nineteenth aspects of the possible design.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform any one of the nineteenth aspects or the nineteenth aspect.
  • the embodiment of the present application provides a chip, where the chip is connected to a memory, for reading and executing a software program stored in the memory, to implement the above nineteenth aspect or the nineteenth aspect Any of the possible methods in the design.
  • a data transmission method includes:
  • the second network device sends a second message to the terminal, where the second message is used to release the air interface connection of the terminal, the second message includes a first key and a first derivation parameter, and the second key is based on Obtained by the second key and the first derivation parameter, the second key is a key used by the terminal and the second network device;
  • the second network device sends a third key and the first derivation parameter to the target network device, where the third key is obtained according to the first key and the first derivation parameter.
  • the embodiment of the present application provides a communication device, where the communication device includes a memory, a communication interface, and a processor, where: the memory is used to store an instruction; the processor is configured to control the communication according to an instruction to execute the memory storage.
  • the interface performs signal reception and signal transmission, and when the processor executes an instruction stored in the memory, the communication device is configured to perform the method in any of the possible aspects of the twenty-fifth aspect or the twenty-fifth aspect.
  • the embodiment of the present application provides a communication apparatus, which is used to implement any one of the foregoing twenty-fifth aspect or the twenty-fifth aspect, including a corresponding functional module, for example, including a processing unit, and receiving Units, transmitting units, etc., are respectively used to implement the steps in the above method.
  • the embodiment of the present application provides a computer readable storage medium, where the computer storage medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the above A method of any of the possible aspects of the twenty-fifth aspect or the twenty-fifth aspect.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform any one of the foregoing twenty-fifth aspect or the twenty-fifth aspect The method in the design.
  • an embodiment of the present application provides a chip, where the chip is connected to a memory, for reading and executing a software program stored in the memory, to implement the foregoing twenty-fifth aspect or the twenty-fifth aspect Any of the possible methods in the design.
  • FIG. 1 is a schematic diagram of a process of transmitting data by a terminal through a random access procedure in a user plane solution in the prior art
  • FIG. 2 is a schematic diagram of a network architecture applicable to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • NR New Radio
  • LTE Long Term Evolution
  • Advanced long term evolution Advanced long term
  • LTE-A Long Term Evolution
  • eLTE evolved Long Term Evolution
  • FIG. 2 it is a schematic diagram of a network architecture applicable to an embodiment of the present application.
  • the base station 201 there are two terminals in the signal coverage area of the base station 201, which are 202 and 203 respectively, and the base station 201 can provide a wireless data transmission service and the like for the terminal 202 and the terminal 203.
  • the base station 201 can include multiple terminals. The foregoing is only an example, and other details are not described herein.
  • a terminal also called a User Equipment (UE) is a device that provides voice and/or data connectivity to a user, for example, a handheld device with a wireless connection function, an in-vehicle device, and the like.
  • UE User Equipment
  • Common terminals include, for example, mobile phones, tablets, notebook computers, PDAs, mobile internet devices (MIDs), wearable devices such as smart watches, smart bracelets, pedometers, and the like.
  • MIDs mobile internet devices
  • wearable devices such as smart watches, smart bracelets, pedometers, and the like.
  • the network device which may be a common base station (such as a Node B or an eNB), may be a new radio controller (NR controller), may be a gNode B (gNB) in a 5G system, may be centralized
  • a centralized unit which may be a new wireless base station, may be a radio remote module, may be a micro base station, may be a relay, may be a distributed network element, or may be a receiving point (Transmission) A reception point (TRP) or a transmission point (TP) or any other wireless access device, but the embodiment of the present application is not limited thereto.
  • Msg3 message 3
  • the Msg3 may be an L2 message or an L3 message
  • the L2 message may be a Media Access Control (MAC) control cell
  • the L3 message may be an RRC message (eg, an RRC connection setup request, or an RRC connection re-establishment, etc.).
  • the terminal in order to enable the terminal to successfully send the uplink data, the user plane key of the terminal to encrypt the uplink data needs to match the decryption key used by the network side, and the terminal may specifically perform the following processes:
  • the following process corresponds to the process shown in FIG. 3 or FIG. 5, where the first message may refer to the RRC connection release message in the process shown in FIG. 3 or FIG. 5, and the first derivation parameter may refer to The first NCC in the flow shown in FIG. 3 or FIG. 5, the second derivation parameter may refer to the third NCC in the process shown in FIG. 3 or FIG. 5, and the first key may refer to the process shown in FIG.
  • the first key K eNB1 , the second key may refer to the second key K eNB2 in the flow shown in FIG. 3 or FIG. 5 , and the first data may refer to the process shown in FIG. 3 or FIG. 5 .
  • the uplink data in the message 3, the second data may refer to the uplink data in the message 3 or the message 5 in the process shown in FIG. 3 or FIG. 5, and the second message may refer to the process shown in FIG. 3 or FIG.
  • the air interface connection may refer to the RRC connection in the flow shown in FIG. 3 or FIG. 5
  • the first indication may refer to the first indication information in the flow shown in FIG. 3 or FIG. 5
  • the second The indication may refer to the second indication information in the flow shown in FIG. 3 or FIG. 5.
  • the first user plane key may refer to the first user plane key in the flow shown in FIG. 3 or FIG. 5.
  • Step 1 The terminal receives the first message from the second network device, where the first message is used to release the air interface connection of the terminal, and the first message includes a first derivation parameter;
  • Step 2 The terminal initiates a random access procedure to the first network device.
  • Step 3 The terminal acquires a first key, where the first key is obtained according to the second key and the first derivation parameter; wherein the second key is the terminal and the first The key used by the second network device;
  • Step 4 The terminal sends, in the random access procedure, first data encrypted by using the first user plane key derived by the first key;
  • Step 5 The terminal receives a second message from the first network device, where the second message is used to restore an air interface connection of the terminal, and the second message includes a second derivation parameter;
  • Step 6 The terminal sends the second data encrypted by using the first user plane key derived by the first key to the first network device by using the restored air interface connection.
  • the order of execution of the foregoing steps is not limited.
  • the sequence in which the terminal initiates a random access procedure to the first network device and the terminal acquires the second key is not limited.
  • the first key and the second key are the same.
  • the first data and the second data are the same.
  • the terminal ignores the second derivation parameter.
  • the ignoring the second derivation parameter by the terminal may be understood as: after receiving the second derivation parameter, updating the first key without using the second derivation parameter.
  • the second message further includes a first indication, where the first indication is used to indicate that the second derivation parameter is ignored.
  • the acquiring, by the terminal, the first key includes:
  • the terminal acquires the first key if the size of the uplink resource allocated to the terminal in the random access process is greater than a threshold.
  • the threshold may be 56 bits, or 88 bits. Or the size of message 3, where message 3 does not contain upstream data.
  • the uplink data is User Plane Data or Traffic Data.
  • the second message further includes a second indication, where the second indication is used to indicate:
  • the partial resetting the current PDCP entity of the terminal may cause the foregoing first data not to be lost.
  • the terminal can perform the following processes:
  • Step 1 The terminal receives the first message from the second network device, where the terminal stores the second key, the first message is used to release the air interface connection of the terminal, and the first message includes the first derivation parameter. ;
  • Step 2 The terminal initiates a random access procedure to the first network device.
  • Step 3 The terminal receives a second message from the first network device, where the second message is used to restore an air interface connection of the terminal, and the second message includes a second derivation parameter;
  • Step 4 The terminal acquires a first key, where the first key is obtained according to the second key and the second derivation parameter;
  • Step 5 The terminal sends, by using the restored air interface connection, first data encrypted by using the first user plane key derived by the first key to the first network device.
  • the first key and the second key are the same.
  • the terminal ignores the first derivation parameter.
  • the ignoring the first derivation parameter by the terminal may be understood as: after receiving the first derivation parameter, updating the first key without using the first derivation parameter.
  • the terminal does not send the first data in the random access process, or the terminal does not The first derivation parameter acquires the first key.
  • the threshold may be 56 bits, or 88 bits, or may be the size of message 3, wherein the message 3 includes an RRC message and the first data.
  • the RRC message may refer to an RRC Connection Recovery Request message.
  • FIG. 3 it is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • the terminal supports EDT, that is, the terminal supports sending uplink data to the base station through a random access procedure.
  • the terminal When the terminal is in the connected state, it is connected to the second network device.
  • the key on the terminal is K eNB2
  • the key on the second network device is K eNB2 .
  • the second network device suspends the terminal by sending an RRC connection release message to the terminal.
  • the RRC connection release message carries the NCC1, and the terminal updates the K eNB2 according to the NCC to obtain the K eNB1 .
  • the uplink data is sent to the first network device by using a random access procedure, and the NCC update key in the RRC connection release message is used to encrypt the uplink data.
  • the terminal ignores the NCC in the RRC connection recovery message sent by the first network device, and no longer uses the NCC secret in the RRC connection recovery message.
  • the key K eNB1 performs an update so that the user plane key K Upenc1 of the encrypted uplink data is no longer updated according to the key K eNB1 .
  • the first network device when the first network device is not the same device as the second network device, the first network device does not update the key K eNB according to the NCC sent by the second device after receiving the NCC sent by the second device.
  • the user plane key of the terminal to encrypt the uplink data is matched with the decryption key used by the network device.
  • the first network device updates the key K eNB2 according to the current NCC when decrypting the uplink data sent by the terminal, thereby realizing the user face density of the terminal encrypting the uplink data.
  • the key matches the decryption key used by the network device.
  • the method includes:
  • Step 301 The second network device sends a first RRC message to the terminal, where the first RRC message includes the suspension indication information and the first NCC, where the suspension indication information is used to indicate that the terminal performs a suspended state, where the first NCC is used.
  • the first key K eNB1 is derived
  • the first key K eNB1 is used to derive the first user plane key K Upenc1
  • the first user plane key is used to encrypt the uplink data sent by the terminal.
  • the suspension indication information may be rrc-Suspend
  • the first RRC message may be an RRC Connection Release message.
  • the second network device determines to suspend the terminal, and determines that the terminal may send in a random access procedure
  • the second network device sends the first RRC message to the terminal.
  • the second network device sends the first RRC message to the terminal according to other conditions.
  • Step 302 The terminal receives a first RRC message sent by the second network device, where the first RRC message includes the suspension indication information and the first NCC.
  • the first NCC is used by the terminal to determine a first key K eNB1 , where the first key K eNB1 is used to derive a first user plane key, and the first user plane key is used to encrypt uplink data sent by the terminal. .
  • the terminal processes the first NCC in the following two ways:
  • Manner 1 The terminal immediately generates a first key K eNB1 according to the first NCC.
  • the key K eNB is used between the terminal and the network device to protect the communication transmission between them.
  • the key used between the terminal and the network device (referred to as the second network device or the source network device, such as the source base station) connected before the handover is referred to as a first key K eNB1
  • the key used between the connected network device (referred to as the first network device or the target network device, such as the target base station) is referred to as the second key K eNB2 .
  • the key used between the terminal and the network device (also referred to as the second network device or the source network device, such as the source base station) that suspends the terminal connection is referred to as the first key K.
  • a key used between a terminal and a network device (referred to as a first network device or a target network device, such as a target base station) that restores the connection of the terminal is referred to as a second key K eNB2 .
  • the terminal may determine the first key according to the first NCC.
  • the specific process may have the following implementation manner:
  • the terminal may be based on the second key K currently saved in the terminal.
  • the first key K eNB1 is derived horizontally by the eNB2 , the Physical Cell Identifier (PCI), and the E-UTRA Absolute Radio Frequency Channel Number-Down Link (EARFCN-DL).
  • the second NCC currently saved by the terminal can be understood as the NCC saved by the terminal before receiving the first NCC or receiving the first NCC.
  • the terminal saves an NCC.
  • the method for obtaining the PCI and the downlink channel number is not limited in the embodiment of the present application.
  • the specific process of the terminal deriving the first base station key K eNB1 and the first user plane key K UPenc1 may refer to the existing standard. The description in the description will not be repeated here.
  • the terminal determines the next hop according to the first NCC.
  • the next Hop parameter (NH), and the first base station key K eNB1 is vertically derived according to the key K ASME , the NH, PCI, and the downlink channel number.
  • the key K ASME is a key for the terminal to access the security management entity, and the terminal may calculate the NH according to the first NCC and the K ASME, and the NH calculated by the first NCC is the NH associated with the first NCC.
  • the terminal deduces the first base station key K eNB1, storing the second key K eNB2, K eNB2 born by a second key to play the second The user plane key K Upenc2 and the security context of the terminal, or after the terminal derives the first key K eNB1 , delete the previously saved second key K eNB2 , the second user plane key K Upenc2 , and the security of the terminal
  • the context of the present application is not limited thereto.
  • the terminal does not update the key immediately, and saves the first NCC and the currently used second key K eNB2 , the second user plane key K Upenc2 , and the like.
  • the first network device After the terminal is replaced with the first network device, the first network device needs to acquire the first NCC from the second network device, and the context of the terminal and the like.
  • the first network device may determine the first key K eNB1 according to the first NCC, thereby deriving the first user plane key K UPenc1 of the terminal encrypted uplink data according to the first key K eNB1 .
  • the first network device can also obtain the first key K eNB1 and the first user plane key K UPenc1 directly from the second network device.
  • the terminal may send the uplink data to the first network device by using a random access procedure, and specifically refer to the following description:
  • Step 303 The terminal sends a preamble to the first network device on the PRACH.
  • the preamble indicates that the terminal needs to send uplink data to the first network device in message 3.
  • the second network device and the first network device may be the same network device, or may be different network devices.
  • Step 304 The first network device sends a RAR message to the terminal, where the RAR message carries a Timing Advance (TA) and a UL Grant.
  • TA Timing Advance
  • the number of uplink resources scheduled by the UL Grant for the terminal is greater than the number of uplink resources required for the RRC connection recovery request message in the message 3.
  • Step 305 The terminal restores the UE context information (UE context).
  • this step may also be before step 304.
  • step 304 When the step is located after step 304, optionally, when the terminal determines that the received UL Grant is sufficient for transmitting the RRC message and the uplink data in the Msg3, the terminal restores the context information of the terminal; otherwise, the context information of the terminal is not restored. Or when the terminal determines that the amount of data that can be sent by the uplink resource scheduled by the received UL Grant is greater than the size of the RRC message in the Msg3, the terminal restores the context information of the terminal; otherwise, the context information of the terminal is not restored.
  • the context information of the terminal includes bearer information and secure configuration information.
  • the bearer information includes information carried by a Signaling Radio Bearer (SRB) SRB0, SRB1, SRB2, and a Data Radio Bearer (DRB).
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the SRB0 is used to send an RRC Connection Request message, an RRC Connection Setup message, an RRC Connection Resume Request message, and the like, which are generated by the NAS layer or by the NAS layer.
  • the RRC layer is instructed to generate and then directly delivered to the MAC layer for transmission through the PHY layer. Since it does not pass through the PDCP layer, no encryption and integrity protection (referred to as security) is required, and no RLC layer is required, so no segmentation or cascading is required, and there is no RLC layer feedback.
  • SRB0 is the default configuration of the terminal, and SRB1 is established through RRC Connection Setup.
  • the SRB1 is configured to send an RRC Connection Reconfiguration message, an RRC Connection Reconfiguration Complete message, an RRC Connection Release message, an RRC Connection Resume message, an RRC Connection Resume Complete message, and the like.
  • RRC message between other network devices and the terminal.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the SRB2 is used to send a non-access stratum (NAS) message, that is, the message of the NAS layer is delivered to the RRC layer, and the RRC message is generated and sent on the SRB2.
  • NAS non-access stratum
  • SRB2 and DRB are established through the RRC Connection Reconfiguration message.
  • the DRB is used to transmit user plane data of the terminal, and the terminal can configure multiple DRBs at the same time.
  • the MAC service data unit SDU
  • multiple MAC SDUs can be multiplexed in the MAC to generate a MAC protocol data unit (Protocol Data).
  • PDU MAC protocol data unit
  • the MAC PDU is sent to the physical (Physical, PHY) layer for transmission.
  • the MAC SDU that SRB0 submits to the MAC layer is not multiplexed with the SDUs on other bearers.
  • the RRC message transmitted on Msg3 is the RRC Connection Resume Request message or the RRC Connection Request message. These messages are all on SRB0. To support user plane data transmission on Msg3, it is necessary to modify the restriction that SRB0 is not multiplexed, so that these messages can be It is multiplexed with the MAC SDU carrying the uplink data on the DRB, so that the Msg3 can transmit the RRC message and the user face data.
  • the terminal may instruct the PDCP layer of the terminal to use the context of the terminal.
  • the terminal may indicate that the PDCP layer of the terminal continues to use the saved header compression protocol context; or the terminal may instruct the PDCP layer of the terminal to reset the header compression protocol context; or the terminal receives a system message of the first network device, the system message carrying header compression indication information, the header compression indication information indicating whether to continue to use the saved header compression protocol context, and the terminal according to the header compression indication broadcast by the first network device in the system message The information determines whether the PDCP layer of the terminal continues to use the saved header compression protocol context.
  • the terminal saves the first NCC in step 302 and does not perform key update according to the first NCC
  • the terminal determines that the received uplink resource of the UL Grant scheduling is sufficient for sending the Msg3.
  • the terminal performs key update according to the first NCC to generate the first key K eNB1 .
  • the terminal determines that the amount of data that can be sent by the uplink resource scheduled by the received UL Grant is greater than the size of the RRC message in the Msg3, the terminal performs key update according to the first NCC to generate the first key K eNB1 .
  • the terminal may also determine the first secret according to the first NCC at this time.
  • the key K eNB1 and the first user plane key K UPenc1 are the first secret according to the first NCC at this time.
  • Step 306 The terminal sends a message 3 to the first network device, where the message 3 includes uplink data.
  • the uplink data is sent by the uplink resource scheduled by the UL Grant carried in the RAR, and the uplink data is encrypted by using the first user plane key K UPenc1 .
  • Step 307 The first network device receives the message 3 sent by the terminal, and sends an RRC connection recovery message to the terminal.
  • the RRC connection recovery message is sent after the first network device determines that the RRC connection of the terminal needs to be restored, and the RRC connection recovery message includes the third NCC.
  • the reason for the decryption failure may be determined, and the reason for the failure may be an algorithm and a terminal for the first network device to encrypt/decrypt the user plane data.
  • the algorithm for adding/decrypting the user plane data is inconsistent, and the uplink data sent by the terminal cannot be decrypted, or the first network device fails to decrypt the uplink data.
  • the first network device restores the RRC connection of the terminal, that is, performs the rollback process.
  • the first network device successfully decrypts the uplink data, and determines that the terminal needs to transmit more uplink data or needs to transmit downlink data to the terminal, the RRC connection of the terminal is restored, that is, back. Exit the process. It is also possible that the first network device sends an RRC connection recovery message to the terminal, which is not limited in this embodiment.
  • the RRC connection recovery message may carry the first indication information, which is used to indicate that the terminal does not update the first key, or is used to indicate that the terminal does not update the first key according to the third NCC. .
  • the first network device instructs the terminal not to update the first key according to the third NCC, and the key saved in the terminal is the first key K eNB1 and the first user plane key K Upenc1 , and the first network device saves The key is the first key K eNB1 and the first user plane key K UPenc1 .
  • the first network device can decrypt the uplink data encrypted by the terminal.
  • the RRC connection recovery message may implicitly indicate that the terminal does not update the first key, that is, after the first network device sends a sufficient UL Grant to the terminal, the first network device sends an RRC connection recovery message to the terminal, and may indicate The out terminal does not update the first key, that is, ignores the third NCC, and keeps the first key unchanged; when the terminal sends the uplink data in Msg3 and then receives the RRC connection recovery message, the terminal determines that the terminal does not need to The first key is updated according to the third NCC.
  • the RRC connection recovery message may also explicitly indicate that the terminal does not update the first key.
  • the RRC connection recovery message includes first indication information, where the first indication information is used to indicate that the terminal does not use the first key.
  • the key is updated, ie the third NCC is ignored and the first key is kept unchanged.
  • the RRC connection recovery message may further include second indication information, where the second indication information is used to indicate whether the terminal re-establishes a PDCP entity.
  • the second indication information may indicate that the terminal is in the Before the message 3 is sent, the PDCP entity has been reconstructed, and the PDCP entity is not reconstructed when the RRC connection recovery message is received.
  • the RRC connection recovery message may further include third indication information, where the third indication information is used to indicate that the terminal reserves the uplink data buffered in the PDCP entity, that is, the reserved PDCP SDU, in the PDCP entity.
  • the rest of the section can be reset.
  • the RRC connection recovery message may further include retransmission indication information, where the retransmission indication information is used to instruct the terminal to retransmit the Upstream data in message 3.
  • Step 308 The terminal receives an RRC connection recovery message sent by the first network device.
  • the third NCC is included in the RRC connection recovery message.
  • the third NCC is actually the same as the first NCC sent by the second network device to the first network device. To distinguish the NCC carried in different messages, the first NCC and the third NCC are used to distinguish. Does not mean other meanings.
  • the terminal determines, according to the RRC connection recovery message, that the first key is not updated, and ignores the third NCC in the RRC connection recovery message, and keeps the first key unchanged.
  • the terminal does not re-establish the PDCP entity.
  • the terminal reserves, according to the third indication information, uplink data buffered in the PDCP entity, that is, a reserved PDCP SDU, and other parts in the PDCP entity. Can be reset.
  • Step 309 The terminal sends a message 5 (message 5, Msg5) to the first network device.
  • the message 5 includes an RRC Connection Resume Complete message.
  • the message 5 includes the uplink data in the message 3.
  • the first network device After receiving the message 5, the first network device sends the uplink data to the serving gateway.
  • the terminal sends the uplink data in the Msg3, and when the first network device decides to fall back to the RRC connection recovery process, the first network device instructs the terminal to ignore the third NCC in the RRC connection recovery message, and maintains the first key.
  • the terminal determines that the user plane key used for encrypting the uplink data is the same as the user plane key used by the first network device, so that the terminal encrypts the user plane key of the uplink data and the key of the first network device to decrypt the uplink data.
  • the matching enables the data transmission between the first network device and the terminal to be successful, thereby reducing the data transmission failure caused by the key mismatch, thereby reducing the uplink data transmission delay of the terminal and reducing excessive resource consumption.
  • the terminal saves the first NCC in step 302, the key update is not performed according to the first NCC.
  • the terminal determines that the uplink resource scheduled by the received UL Grant is only sufficient for transmitting the RRC message (RRC Connection Recovery Request message) in the Msg3, and is unable to transmit the uplink data, the terminal does not perform the key update according to the first NCC.
  • step 308 after receiving the RRC connection recovery message sent by the first network device, the terminal determines that the third NCC in the RRC connection recovery message is the same as the first NCC in the RRC connection release message, the K eNB2 second key stored in the terminal, PCI, downlink channel number to deduce the level of the first key K eNB1.
  • the key stored in the terminal is the first key K eNB1 and the first user plane key K Upenc1
  • the key saved by the first network device is the first key K eNB1 and the first user plane key K.
  • UPenc1 in the case that the security encryption algorithm is consistent, the first network device can decrypt the uplink data encrypted by the terminal.
  • the first network device or the second network device when the terminal performs the key update, the first network device or the second network device also needs to perform the synchronous update of the key.
  • the first network device may perform the following processes:
  • the following process corresponds to the process shown in FIG. 4, where the first message may refer to the RRC connection release message in the process shown in FIG. 4, and the first derivation parameter may refer to the process shown in FIG.
  • the first NCC in the second NCC, the second derivation parameter may refer to the third NCC in the flow shown in FIG. 4, and the first key may refer to the first key K eNB1 in the flow shown in FIG.
  • the key may refer to the second key K eNB2 in the flow shown in FIG. 4
  • the first data may refer to the uplink data in the message 3 in the flow shown in FIG. 4
  • the second data may refer to the data shown in FIG.
  • the second message may refer to the RRC connection recovery message in the flow shown in FIG. 4, and the air interface connection may refer to the RRC connection in the flow shown in FIG.
  • An indication may refer to the first indication information in the flow shown in FIG. 4, and the second indication may refer to the second indication information in the flow shown in FIG. 4.
  • the first user plane key may refer to the first user plane key in the flow shown in FIG.
  • Step 1 The first network device receives, from the second network device, a first key, a first derivation parameter, and a first indication, where the first key is obtained according to the second key and the first derivation parameter, where The second key is a key used by the terminal and the second network device, and the first indication is used to indicate that a key update is required;
  • Step 2 The first network device sends a second message to the terminal in a random access process, where the second message is used to restore the air interface connection of the terminal, and the second message includes a second derivation parameter;
  • Step 3 The first network device acquires a third key, and the third key is obtained according to the first key and the second derivation parameter.
  • the meaning of indicating that the key update needs to be performed may be understood as: the message sent by the second network device to the terminal for releasing the air interface connection of the terminal carries the first derivation parameter.
  • the second message further includes a second indication, where the second indication is used to indicate:
  • the partially resetting the current PDCP entity of the terminal may cause the first data not to be lost.
  • the first network device can perform the following processes:
  • the first network device receives, from the second network device, a first key, a first derivation parameter, the first key is obtained according to the second key and the first derivation parameter, and the second key is a terminal Density used with the second network device key;
  • the first network device sends a second message to the terminal in a random access process, where the second message is used to restore the air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the first network device acquires a third key, and the third key is obtained according to the first key and the second derivation parameter.
  • the first network device may send the second message.
  • the first message further includes a first indication, where the first indication is used to indicate:
  • the partially resetting the current PDCP entity of the terminal may cause the first data not to be lost.
  • the first network device may also instruct the terminal to determine the third key K eNB3 according to the third NCC in the RRC connection recovery message.
  • the first method the first network device updates the key according to the first NCC sent by the second device, so that the user plane key of the terminal encrypted uplink data matches the decryption key used by the network device.
  • the key update process may be performed when the first network device receives the first NCC sent by the second device, or may also occur before the first network device sends the RRC connection recovery message to the terminal. This example does not limit this.
  • the second network device updates the key according to the first NCC when the terminal is suspended, so that the user plane key of the terminal encrypted uplink data matches the decryption key used by the network device.
  • the key update process may be performed when the second network device determines to suspend the terminal or before the second network device sends the RRC connection recovery message to the terminal.
  • FIG. 4 it is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • the method includes:
  • Step 400 The second network device sends an RRC connection release message to the terminal.
  • Step 401 The terminal receives the RRC connection release message sent by the second network device, and acquires the first NCC in the RRC connection release message.
  • the terminal may determine the first key K eNB1 according to the first NCC, and derive the first user plane key K UPenc1 according to the first key K eNB1 .
  • the specific implementation process of the terminal determining the first base station key according to the first NCC may have the following implementation manner:
  • the terminal may be based on the second key K currently saved in the terminal.
  • the eNB2 , PCI, and downlink channel number horizontally derive the first key K eNB1 .
  • the terminal determines, according to the first NCC,
  • the first base station key K eNB1 is vertically derived according to the key K ASME , the NH, the PCI, and the downlink channel number.
  • the first network device After the terminal is replaced with the first network device, the first network device needs to acquire the first NCC from the second network device, and the context of the terminal and the like.
  • the following steps may also be included:
  • Step 402a The first network device sends a derivation user equipment context request message to the second network device.
  • Step 402b The second network device sends a derivation user equipment context response request message to the first network device.
  • the derivation user equipment context response request message includes a first NCC, a first key K eNB1, and security capability information of the terminal.
  • the first network device may determine the first key K eNB1 according to the first NCC, thereby pushing according to the first key K eNB1
  • the performance terminal encrypts the first user plane key K UPenc1 of the uplink data.
  • the first network device can also obtain the first key K eNB1 and the first user plane key K UPenc1 directly from the second network device.
  • the key update is performed again, that is, the first network device derives the third key K eNB3 according to the first key K eNB1 , PCI , and the downlink channel number level, and uses the first The triple key K eNB3 replaces the first key K eNB1 .
  • the first network device may further derive a third user plane key K Upenc3 of the terminal encrypted uplink data according to the third key K eNB3 .
  • the first network device acquires the third key K eNB3 and the third user plane key K Upenc3 , the third key K eNB3 and the third user plane key from the second network device.
  • K Upenc3 is the second network device based on the first NCC.
  • the terminal may send the uplink data to the first network device by using a random access procedure, and specifically refer to the following description:
  • Step 403 The terminal sends a Preamble to the first network device on the PRACH.
  • the Preamble indicates that the terminal needs to send uplink data to the first network device in message 3.
  • the second network device and the first network device may be the same network device, or may be different network devices.
  • Step 404 The first network device sends a RAR message to the terminal, where the RAR message carries a Timing Advance (TA) and a UL Grant.
  • TA Timing Advance
  • the number of uplink resources scheduled by the UL Grant for the terminal is greater than the number of uplink resources required for the RRC connection recovery request message in the message 3.
  • Step 405 After receiving the RAR message, the terminal restores the context information of the terminal.
  • this step may also be before step 404.
  • step 305 For the rest of the steps, refer to the description in step 305, and details are not described herein again.
  • Step 406 The terminal sends a message 3 to the first network device, where the message 3 includes uplink data.
  • the message 3 also includes an RRC connection recovery request message.
  • the uplink data is sent by the uplink resource scheduled by the UL Grant carried in the RAR, and the uplink data is encrypted by using the first user plane key K UPenc1 .
  • Step 407 The first network device receives the message 3 sent by the terminal, and sends an RRC connection recovery message to the terminal.
  • the third NCC is included in the RRC connection recovery message.
  • the third NCC is actually the same as the first NCC obtained by the first network device from the second network device.
  • the first NCC and the third NCC are used to distinguish the same. Does not mean anything else.
  • the RRC connection recovery message may be used to instruct the terminal to update the first key according to the third NCC.
  • the following describes how the RRC Connection Recovery message instructs the terminal to update the first key according to the third NCC.
  • the RRC connection recovery message may implicitly indicate that the terminal updates the first key according to the third NCC, that is, the first network device sends an RRC connection recovery message to the terminal, and may indicate that the terminal is in accordance with the third NCC pair.
  • a key is updated; when the terminal transmits the uplink data in Msg3 and then receives the RRC connection recovery message, the terminal updates the first key according to the third NCC.
  • the RRC connection recovery message may also be used to indicate that the terminal updates the first key according to the third NCC.
  • the RRC connection recovery message includes first indication information, where the first indication information is used to indicate The terminal updates the first key according to the third NCC.
  • the RRC connection recovery message may further include fourth indication information, where the fourth indication information is used to indicate whether the terminal resets one or more of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • the first network device may also implicitly determine whether at least the terminal resets the PDCP entity, the RLC entity, and the MAC entity.
  • the terminal may also implicitly determine whether at least the terminal resets the PDCP entity, the RLC entity, and the MAC entity.
  • the RRC connection recovery message may further include other indication information. For details, refer to the description in step 307, and details are not described herein.
  • Step 408 The terminal receives an RRC connection recovery message sent by the first network device.
  • the terminal determines that the third NCC in the RRC connection recovery message is the same as the first NCC in the RRC connection release message, and may perform the third secret according to the first key K eNB1 , PCI, and the downlink channel number level. Key K eNB3 .
  • the terminal may further derive a third user plane key K Upenc3 for encrypting the uplink data according to the third key K eNB3 .
  • the key stored in the terminal is the third key K eNB3 and the third user plane key K Upenc3
  • the key stored in the first network device is the third key K eNB3 and the third user plane key K.
  • the first network device can decrypt the uplink data encrypted by the terminal using the third user plane key K Upenc3 .
  • the terminal when the fourth indication information is included in the RRC connection recovery message, the terminal resets one or more of the following according to the fourth indication information: a PDCP entity, an RLC entity, and a MAC entity. At the same time, the terminal encrypts the PDCP SDU in the PDCP entity using the third user plane key.
  • Step 409 The terminal sends a message 5 (message 5, Msg5) to the first network device.
  • the message 5 includes an RRC Connection Resume Complete message.
  • the message 5 includes uplink data.
  • the first network device After receiving the message 5, the first network device sends the uplink data to the serving gateway.
  • the terminal sends the uplink data in the Msg3, and the first network device instructs the terminal to update the first key according to the third NCC in the RRC connection recovery message when the first network device decides to fall back to the RRC connection recovery process.
  • the user plane key determined by the terminal according to the first key is the same as the user plane key used by the first network device side, so that the user plane key of the terminal encrypting the uplink data matches the key of the first network device for decrypting the uplink data.
  • the data transmission between the first network device and the terminal can be successfully performed, thereby reducing data transmission failure caused by the key mismatch, thereby reducing the uplink data transmission delay of the terminal and reducing excessive resource consumption.
  • the terminal may also determine whether to update the key according to actual conditions, which is not required by the network device, and is described in detail below.
  • FIG. 5 it is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • the terminal supports sending uplink data to the base station through a random access procedure.
  • the terminal is connected to the second network device.
  • the second network device suspends the terminal by sending an RRC connection release message to the terminal.
  • the uplink data is sent to the first network device by using a random access procedure.
  • the terminal In order to avoid the user side key of the terminal encrypting the uplink data and the decryption key used by the network side, Matching, the terminal ignores the NCC in the RRC connection recovery message, and no longer updates the key according to the NCC in the RRC connection recovery message, so that the user plane key of the encrypted uplink data is no longer updated according to the NCC in the RRC connection recovery message. .
  • the first network device when the first network device is not the same device as the second network device, after receiving the NCC sent by the second device, the first network device does not update the key according to the NCC sent by the second device, thereby The number of times the terminal and the first network device update the key are the same, so that the user plane key of the terminal encrypting the uplink data matches the decryption key used by the network device.
  • the first network device and the second network device are the same device, after the first network device sends the RRC connection release message to the terminal, the first network device does not update the key according to the NCC, so that the terminal encrypts the user plane key of the uplink data. Matches the decryption key used by the network device.
  • the method includes:
  • Step 500 The second network device sends an RRC connection release message to the terminal.
  • the first NCC is included in the RRC Connection Release message.
  • the second network device is a network device that supports early data transmission or early data transmission (EDT).
  • EDT early data transmission
  • Step 501 The terminal determines the first key according to the first NCC in the RRC connection release message.
  • the terminal may determine the NH according to the first NCC, and perform the first step according to the NH, the PCI, and the downlink channel number.
  • a key K eNB1 A key K eNB1 .
  • the terminal after obtaining the first key K eNB1 , the terminal still retains the previously saved second key K eNB2 and the security context of the terminal.
  • the terminal After receiving the RRC connection release message, the terminal changes from the second network device to the first network device, and needs to send uplink data in the random access process by using the first network device.
  • the first network device is a network device that does not support EDT.
  • the terminal may determine, according to a system information (SI) broadcast by the first network device, whether the first network device supports EDT.
  • SI system information
  • the SI broadcasted by the first network device includes EDT indication information, where the EDT indication information indicates that the first network device does not support the EDT, and the terminal may determine, according to the EDT indication information, that the first network device does not support the EDT.
  • the first network device may further indicate to the terminal whether the first network device supports the EDT by using other methods, and details are not described herein again.
  • the first network device After the terminal switches to the first network device, the first network device needs to acquire information about the first NCC, and the context information of the terminal from the second network device.
  • the following steps may also be included:
  • Step 502a The first network device sends a derivation user equipment context request message to the second network device.
  • Step 502b The second network device sends a derivation user equipment context response request message to the first network device.
  • the derivation user equipment context response request message includes a first NCC, a first key K eNB1, and security capability information of the terminal, context information of the terminal, and the like.
  • the first network device may determine the first key K eNB1 according to the first NCC, thereby pushing according to the first key K eNB1
  • the performance terminal encrypts the first user plane key K UPenc1 of the uplink data.
  • the first network device can also obtain the first key K eNB1 and the first user plane key K UPenc1 directly from the second network device.
  • Step 503 The terminal sends a preamble to the first network device on the PRACH.
  • the preamble does not indicate that the terminal needs to send uplink data to the first network device in message 3.
  • Step 504 The first network device sends a RAR message to the terminal, where the RAR message carries a UL Grant.
  • the number of uplink resources scheduled by the UL Grant for the terminal is equal to the number of uplink resources required for the RRC connection recovery request message in the message 3.
  • Step 505 The terminal sends a message 3 to the first network device, where the uplink data is not included in the message 3.
  • the message 3 includes an RRC connection recovery request message.
  • Step 506 The first network device receives the message 3 sent by the terminal, and sends an RRC connection recovery message to the terminal.
  • the third NCC is included in the RRC connection recovery message.
  • the third NCC is actually the same as the first NCC obtained by the first network device from the second network device. To distinguish the NCC carried in different messages, the first NCC and the third NCC are used to distinguish the first NCC. Does not mean anything else.
  • Step 507 The terminal receives an RRC connection recovery message sent by the first network device.
  • step 507 is not limited in this embodiment of the present application, and details are not described herein again.
  • the first network device after receiving the first NCC, the first network device does not update the first key K eNB1 according to the first NCC, so that the first user plane key K UPenc1 is no longer updated.
  • the terminal when receiving the third NCC, the terminal does not update the key according to the third NCC, thereby implementing the first user plane key K saved in the first network device and the terminal.
  • the UPenc1 is consistent, thereby ensuring that the first network device and thus the uplink data sent by the terminal can be successfully decrypted, so that the data transmission can be successfully performed between the first network device and the terminal, thereby reducing data transmission failure caused by the key mismatch, and further Reduce the uplink data transmission delay of the terminal and reduce excessive resource consumption.
  • the terminal may further update the key according to the third NCC in the RRC connection recovery message sent by the first network device, which is described in detail below.
  • the terminal may perform key update according to the first NCC in the RRC connection release message, or may not perform the first NCC according to the RRC connection release message.
  • the key update is performed, and only the first NCC is saved, but the terminal retains the previously saved second key K eNB2 and the second user plane key K Upenc2 regardless of whether the key update is performed.
  • step 505 the terminal determines that the first network device does not support the EDT, and after receiving the RRC connection recovery message, the terminal saves the second user plane saved in the terminal according to the NCC in the RRC connection recovery message.
  • the key K Upenc2 is updated.
  • the updated key is ignored; when the terminal does not perform key update according to the first NCC, the first NCC is ignored.
  • step 505 the terminal determines that the first network device supports the EDT. After receiving the RAR message, if the uplink resource scheduled by the UL Grant in the RAR message is 56 bits or 88 bits, the terminal only needs to send the uplink resource. If the RRC connection recovery request message is sent, the terminal does not send uplink data to Msg3.
  • the updated key is ignored; when the terminal does not perform key update according to the first NCC, the first NCC is ignored.
  • step 507 after receiving the RRC connection recovery message sent by the first network device, the terminal determines that the third NCC is the same as the second NCC, so as to perform according to the second key K eNB2 , PCI , and the downlink channel number saved in the terminal.
  • the first key K eNB1 thereby inferring the first user plane key K UPenc1 according to the first key K eNB1 .
  • the key stored in the first network device is the same as the key updated by the terminal, so that the user plane key of the terminal encrypting the uplink data matches the key of the first network device for decrypting the uplink data, so that the first network device and the first network device Data transmission can be successfully performed between terminals, thereby reducing data transmission failure caused by key mismatch, thereby reducing terminal uplink data transmission delay and reducing excessive resource consumption.
  • the corresponding terminal changes from the second network device to the scenario of the first network device.
  • the first network device does not obtain the context of the terminal from the second network device, the first network device sends an RRC connection setup message to the terminal.
  • the RRC connection setup message includes data retention indication information indicating that the terminal reserves the PDCP SDU or instructs the terminal to reset a portion of the PDCP layer other than the PDCP SDU.
  • the PDCP SDU includes uplink data.
  • the first network device can reserve the PDCP SDU by instructing the terminal, so that the terminal can retain the uplink data that is not successfully sent or not sent after the RRC connection is established, thereby avoiding data loss.
  • the terminal After receiving the RRC connection setup message sent by the first network device, the terminal reserves the PDCP SDU according to the data retention indication information in the RRC connection setup message, or does not reset the PDCP SDU when the PDCP layer is reset, thereby implementing the RRC. After the connection is established, it can retain the uplink data that has not been sent successfully or not, so as to avoid data loss.
  • FIG. 6 it is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • the method includes:
  • Step 601 The second network device sends an RRC connection release message to the terminal.
  • Step 602 The terminal receives the RRC connection release message sent by the second network device, and acquires the first NCC in the RRC connection release message.
  • the terminal may determine the first key K eNB1 according to the first NCC, and derive the first user plane key K UPenc1 according to the first key K eNB1 .
  • the first network device After the terminal switches to the first network device, the first network device needs to acquire the first NCC from the second network device, and the context of the terminal and the like.
  • the first network device may determine the first key K eNB1 according to the first NCC, thereby deriving the first user plane key K UPenc1 of the terminal encrypted uplink data according to the first key K eNB1 .
  • the first network device can also obtain the first key K eNB1 and the first user plane key K UPenc1 directly from the second network device.
  • the third key K eNB3 may be derived according to the first key K eNB1 , PCI, the downlink channel number level, and the first key is replaced by the third key K eNB3 K eNB1 .
  • the first network device may further derive a third user plane key K Upenc3 of the terminal encrypted uplink data according to the third key K eNB3 .
  • the terminal may send the uplink data to the first network device by using a random access procedure, and specifically refer to the following description:
  • Step 603 The terminal sends a preamble to the first network device on the PRACH.
  • the preamble indicates that the terminal needs to send uplink data to the first network device in message 3.
  • Step 604 The first network device sends a RAR message to the terminal.
  • the RAR message carries a UL Grant.
  • the number of uplink resources scheduled by the UL Grant for the terminal is greater than the uplink resource required for the RRC connection recovery request message in the message 3. quantity.
  • Step 605 After receiving the RAR message, the terminal restores the context of the terminal.
  • this step may also be before step 603.
  • step 305 For the rest of the steps, refer to the description in step 305, and details are not described herein again.
  • Step 606 The terminal sends a message 3 to the first network device, where the message 3 includes uplink data.
  • the uplink data is sent by using the uplink resource scheduled for the terminal indicated by the RAR, and the uplink data is encrypted by using the first user plane key K UPenc1 .
  • Step 607 The first network device receives the message 3 sent by the terminal, and sends an RRC connection setup message to the terminal.
  • the RRC connection setup message is sent after the first network device determines that the context of the terminal is not acquired from the second network device.
  • the RRC connection setup message includes data retention indication information indicating that the terminal reserves the PDCP SDU or instructs the terminal to reset a portion of the PDCP layer other than the PDCP SDU.
  • Step 608 After receiving the RRC connection setup message sent by the first network device, the terminal reserves the PDCP SDU according to the data retention indication information in the RRC connection setup message.
  • the terminal does not reset the PDCP SDU when the PDCP layer is reset according to the data retention indication information in the RRC connection setup message.
  • Step 609 The terminal sends a message 5 to the first network device.
  • the message 5 includes an RRC Connection Setup Complete message.
  • the message 5 includes uplink data.
  • the first network device After receiving the message 5, the first network device sends the uplink data to the serving gateway.
  • the NCC may not be sent to the terminal.
  • the terminal may update the key according to the NCC sent by the first network device, which is described in detail below.
  • FIG. 7 is a schematic flowchart diagram of a data transmission method according to an embodiment of the present application.
  • the method includes:
  • Step 701 The second network device sends an RRC connection release message to the terminal.
  • the first NCC is not included in the RRC Connection Release message.
  • the terminal After receiving the RRC connection release message, the terminal changes from the second network device to the first network device, and needs to send uplink data in the random access process by using the first network device.
  • the first network device is a network device that supports EDT.
  • Step 702 The terminal sends a preamble to the first network device on the PRACH.
  • the preamble indicates that the terminal needs to send uplink data to the first network device in message 3.
  • Step 703 The first network device sends a RAR message to the terminal.
  • the RAR message carries a fixed UL Grant.
  • the number of uplink resources scheduled by the UL Grant for the terminal is greater than the number of uplink resources required for the RRC connection recovery request message in the message 3.
  • Step 704 The terminal sends a message 3 to the first network device, where the message 3 includes uplink data.
  • the uplink data in the message 3 is encrypted using the second user plane key K Upenc2 held in the terminal.
  • Step 705 The first network device receives the message 3 sent by the terminal, and sends the terminal context to the second network device. Request message.
  • the first network device may indicate, by the terminal context request message, that the first network device supports EDT.
  • Step 706 The second network device sends a terminal context response message to the first network device.
  • the terminal context response message includes a second key K eNB2 and a security context used by the terminal in the last connected state saved by the second network device, and further includes a first NCC and a first key K eNB1 derived from the first NCC.
  • Step 707 The first network device sends an RRC connection recovery message including the third NCC to the terminal.
  • the first network device uses the second key K eNB2 used before the terminal to solve the uplink data of the message 3, and sends the third NCC to the terminal, and then uses the first key K derived from the first NCC sent by the second network device. eNB1 .
  • Step 708 The terminal derives the first key K eNB1 according to the third NCC.
  • the data in the message 3 uses the second key K eNB2 saved before the terminal, and the first key K eNB1 used after the terminal sends the message 3 is the same as the current technology.
  • the second network device sends a second message to the terminal, where the second message is used to release the air interface connection of the terminal, the second message includes a first key and a first derivation parameter, and the second key is based on Obtained by the second key and the first derivation parameter, the second key is a key used by the terminal and the second network device;
  • the second network device sends a third key and the first derivation parameter to the target network device, where the third key is obtained according to the first key and the first derivation parameter.
  • the embodiment of the present application further provides a communication device, including: a processor 801, a transceiver 802, and a memory 803.
  • the processor 801, the transceiver 802, and the memory 803 are connected to each other through a bus 804.
  • the processor 801 can be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 801 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 803 may include a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory.
  • RAM random-access memory
  • the memory may also include a non-volatile memory such as a flash memory.
  • HDD hard disk drive
  • SSD solid-state drive
  • the bus 804 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the memory 803 can be used to store program instructions, and the processor 801 calls the program instructions stored in the memory 803 to perform one or more of the steps shown in the above scheme.
  • the transceiver 802 is configured to receive a first message from the second network device, where the first message is used to release the terminal air interface connection, and the first message includes a first derivation parameter;
  • the transceiver is configured to initiate a random access procedure to the first network device
  • the processor 801 is configured to acquire a first key, where the first key is based on the second key and the first derivation parameter Obtained; wherein the second key is a key used by the terminal and the second network device;
  • the transceiver is configured to send, in the random access procedure, first data encrypted by using a first user plane key derived by using the first key, and receive a second message from the first network device, where The second message is used to restore the air interface connection of the terminal, the second message includes a second derivation parameter; and the first network device is used to transmit the first key deduction by using the restored air interface connection.
  • a second data encrypted by a user plane key is used to send, in the random access procedure, first data encrypted by using a first user plane key derived by using the first key, and receive a second message from the first network device, where The second message is used to restore the air interface connection of the terminal, the second message includes a second derivation parameter; and the first network device is used to transmit the first key deduction by using the restored air interface connection.
  • a second data encrypted by a user plane key is used to send, in the random access procedure, first data encrypted by using a first user plane key derived by using the first key, and receive a second message from the first network device, where
  • the second message further includes a first indication, where the first indication is used to indicate that the second derivation parameter is ignored.
  • the processor is specifically configured to:
  • the threshold is 56 bits, or 88 bits.
  • the second message further includes a second indication, where the second indication is used to indicate:
  • the part of the current PDCP entity is reset, so that the first data is not lost.
  • the various modules of the foregoing apparatus may also be implemented by a logic unit, for example, including a processing unit corresponding to the processor in FIG. 8, a transceiver unit corresponding to the transceiver in FIG. 8, and the like, respectively, for implementing the steps in the above method.
  • a logic unit for example, including a processing unit corresponding to the processor in FIG. 8, a transceiver unit corresponding to the transceiver in FIG. 8, and the like, respectively, for implementing the steps in the above method.
  • the embodiment of the present application further provides a communication device, including a processing unit 901 and a transceiver unit 902.
  • the embodiment of the present application further provides a communication device, including: a processor 1001, a transceiver 1002, and a memory 1003.
  • the processor 1001, the transceiver 1002, and the memory 1003 are connected to each other through a bus 1004.
  • a transceiver configured to receive a first message from the second network device, where the terminal stores a second key, the first message is used to release the terminal air interface connection, and the first message includes a first derivation a parameter; initiating a random access procedure to the first network device; receiving a second message from the first network device, the second message is used to restore an air interface connection of the terminal, and the second message includes a second derivation parameter ;
  • a processor configured to acquire a first key, where the first key is obtained according to the second key and the second derivation parameter;
  • the transceiver is configured to send, by the restored air interface connection, first data encrypted by using the first user plane key derived by the first key to the first network device.
  • the processor is specifically configured to:
  • the first data is not sent in the random access procedure, or the first data is not obtained according to the first derivation parameter. Key.
  • the threshold is 56 bits, or 88 bits, or the size of the message 3, wherein the message 3 includes an RRC message and the first data.
  • the various modules of the foregoing apparatus may also be implemented by a logic unit, for example, including a processing unit corresponding to the processor in FIG. 10, a transceiver unit corresponding to the transceiver in FIG. 10, and the like, respectively, for implementing the steps in the above method.
  • a logic unit for example, including a processing unit corresponding to the processor in FIG. 10, a transceiver unit corresponding to the transceiver in FIG. 10, and the like, respectively, for implementing the steps in the above method.
  • the embodiment of the present application further provides a communication device, including a processing unit 1101 and a transceiver unit 1102.
  • the embodiment of the present application further provides a communication device, including: a processor 1201, a communication interface 1202, and a memory 1203.
  • the processor 1201, the communication interface 1202, and the memory 1203 are connected to each other through a bus 1204.
  • a communication interface 1202 configured to receive, by the second network device, a first key, a first derivation parameter, and a first indication, where The first key is obtained according to the second key and the first derivation parameter, where the second key is a key used by the terminal and the second network device, and the first indication is used to indicate that the Key update
  • the communication interface 1202 is configured to send a second message to the terminal in a random access process, where the second message is used to restore an air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the processor 1201 is configured to acquire a third key, where the third key is obtained according to the first key and the second derivation parameter.
  • the second message further includes a second indication, where the second indication is used to indicate:
  • the part of the current PDCP entity is reset, so that the first data is not lost.
  • the various modules of the foregoing apparatus may also be implemented by a logic unit, for example, including a processing unit corresponding to the processor in FIG. 12, a transceiver unit corresponding to the communication interface in FIG. 12, and the like, respectively, for implementing the steps in the above method.
  • a logic unit for example, including a processing unit corresponding to the processor in FIG. 12, a transceiver unit corresponding to the communication interface in FIG. 12, and the like, respectively, for implementing the steps in the above method.
  • the embodiment of the present application further provides a communication device, including a processing unit 1301 and a transceiver unit 1302.
  • the embodiment of the present application further provides a communication device, including: a processor 1401, a communication interface 1402, and a memory 1403.
  • the processor 1401, the communication interface 1402, and the memory 1403 are connected to each other through a bus 1404.
  • the communication interface 1402 is configured to receive, by the second network device, a first key, a first derivation parameter, where the first key is obtained according to the second key and the first derivation parameter, the second key Is a key used by the terminal and the second network device; receiving first data from the terminal in the random access procedure; sending a second message to the terminal in a random access procedure, the second The message is used to restore the air interface connection of the terminal, and the second message includes a second derivation parameter;
  • the processor 1401 is configured to acquire a third key, where the third key is obtained according to the first key and the second derivation parameter.
  • the communication interface 1402 is specifically configured to:
  • the first message further includes a first indication, where the first indication is used to indicate:
  • the part of the current PDCP entity is reset, so that the first data is not lost.
  • the various modules of the foregoing apparatus may also be implemented by a logic unit, for example, including a processing unit corresponding to the processor in FIG. 14, a transceiver unit corresponding to the communication interface in FIG. 14, and the like, respectively for implementing the steps in the above method.
  • a logic unit for example, including a processing unit corresponding to the processor in FIG. 14, a transceiver unit corresponding to the communication interface in FIG. 14, and the like, respectively for implementing the steps in the above method.
  • the embodiment of the present application further provides a communication device, including a processing unit 1501 and a transceiver unit 1502.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer usable memory channels (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • the computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine instruction for generating instructions executed by a processor of a computer or other programmable data processing device Means for implementing the functions specified in one or more flows of the flowchart or in a block or blocks of the flowchart.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de transmission de données. Le procédé comporte les étapes suivantes: un terminal reçoit un premier message provenant d'un second dispositif de réseau, le premier message étant utilisé pour libérer un connexion d'interface radio du terminal, et le premier message comportant un premier paramètre d'élaboration; le terminal amorce un premier processus d'accès aléatoire à un premier dispositif de réseau; le terminal obtient une première clé, la première clé étant obtenue d'après une deuxième clé et le premier paramètre d'élaboration, et la deuxième clé étant une clé utilisée par le terminal et le second dispositif de réseau; dans le processus d'accès aléatoire, le terminal envoie des premières données chiffrées par une première clé de plan d'utilisateur élaborée en utilisant la première clé; le terminal reçoit un second message provenant du premier dispositif de réseau, le second message étant utilisé pour rétablir la connexion d'interface radio du terminal, et le second message comportant un second paramètre d'élaboration; et en utilisant la connexion d'interface radio rétablie, le terminal envoie au premier dispositif de réseau des secondes données chiffrées par la première clé de plan d'utilisateur élaborée en utilisant la première clé.
PCT/CN2017/111469 2017-11-16 2017-11-16 Procédé et appareil de transmission de données WO2019095240A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/111469 WO2019095240A1 (fr) 2017-11-16 2017-11-16 Procédé et appareil de transmission de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/111469 WO2019095240A1 (fr) 2017-11-16 2017-11-16 Procédé et appareil de transmission de données

Publications (1)

Publication Number Publication Date
WO2019095240A1 true WO2019095240A1 (fr) 2019-05-23

Family

ID=66538405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/111469 WO2019095240A1 (fr) 2017-11-16 2017-11-16 Procédé et appareil de transmission de données

Country Status (1)

Country Link
WO (1) WO2019095240A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015013964A1 (fr) * 2013-08-01 2015-02-05 Nokia Corporation Procédés, appareils et produits-programmes informatiques de transfert rapide
CN105557006A (zh) * 2013-08-09 2016-05-04 三星电子株式会社 用于支持双连接的pdcp分布式结构的安全密钥生成和管理方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015013964A1 (fr) * 2013-08-01 2015-02-05 Nokia Corporation Procédés, appareils et produits-programmes informatiques de transfert rapide
CN105557006A (zh) * 2013-08-09 2016-05-04 三星电子株式会社 用于支持双连接的pdcp分布式结构的安全密钥生成和管理方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "NR SECURITY FRAMEWORK", 3GPP TSG RAN WG2 MEETING #99BIS R2-1710599, 13 October 2017 (2017-10-13), XP051342635 *
INTEL CORPORATION: "Security Optimizations When Resuming or Re-establishing", 3GPP TSG RAN WG2 ADHOC MEETING R2-1707040, 29 June 2017 (2017-06-29), XP051301536 *
SAMSUN G: "Security Procedure From RRC-INACTIVE State in NR", 3GPP TSG RAN WG2 ADHOC MEETING R2-1706806, 29 June 2017 (2017-06-29), XP051301302 *

Similar Documents

Publication Publication Date Title
CN111034265B (zh) Ran inactive模式下的位置和上下文管理
CN109802809B (zh) 网络接入的方法、终端设备和网络设备
CN107113895B (zh) 通信方法、网络侧设备和用户设备
CN110312296B (zh) 用户设备执行的方法、基站执行的方法、用户设备和基站
CN108617031B (zh) 处理用户端接入层文本的装置及方法
CN108924829B (zh) 一种发送、处理上行数据和认证的方法及装置
CN109788544B (zh) 一种层2处理方法、cu及du
TW201507525A (zh) 資料傳輸方法和設備
ES2963419T3 (es) Verificación de la seguridad cuando se reanuda una conexión de RRC
CN112492584B (zh) 终端设备和用户面网元之间的安全通信方法、装置及系统
CN110831258A (zh) 一种数据传输的方法及装置
WO2018083320A1 (fr) Transfert intercellulaire d'un dispositif qui utilise un autre dispositif en tant que relais
AU2024200711A1 (en) Managing security keys in a communication system
US20220345883A1 (en) Security key updates in dual connectivity
US20240172176A1 (en) Managing downlink early data transmission
WO2019095240A1 (fr) Procédé et appareil de transmission de données
WO2022133682A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
WO2020191782A1 (fr) Procédé et dispositif de transmission de données
WO2019091424A1 (fr) Procédé de transmission de données, dispositif et support de stockage
TW202046813A (zh) 在通信網路中恢復無線電連接
WO2020042040A1 (fr) Procédé et dispositif de transmission précoce de données de liaison descendante
WO2021026875A1 (fr) Procédé et appareil de transmission de données
WO2022135517A1 (fr) Procédé exécuté par un équipement utilisateur et équipement utilisateur
CN109756891B (zh) 数据传输方法、设备和存储介质
CN116458184A (zh) 一种用于密钥传递的方法

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: 17932292

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: 17932292

Country of ref document: EP

Kind code of ref document: A1