WO2022036611A1 - 一种数据传输方法及通信装置 - Google Patents

一种数据传输方法及通信装置 Download PDF

Info

Publication number
WO2022036611A1
WO2022036611A1 PCT/CN2020/110110 CN2020110110W WO2022036611A1 WO 2022036611 A1 WO2022036611 A1 WO 2022036611A1 CN 2020110110 W CN2020110110 W CN 2020110110W WO 2022036611 A1 WO2022036611 A1 WO 2022036611A1
Authority
WO
WIPO (PCT)
Prior art keywords
drb
data
pdcp
uplink data
terminal device
Prior art date
Application number
PCT/CN2020/110110
Other languages
English (en)
French (fr)
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/CN2020/110110 priority Critical patent/WO2022036611A1/zh
Publication of WO2022036611A1 publication Critical patent/WO2022036611A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a data transmission method and a communication device.
  • a terminal device When a terminal device has an uplink data transmission requirement, it can transmit uplink data based on a dynamic grant (grant based, GB) or dynamic scheduling manner, and the specific process may include the following steps.
  • the terminal device reports a non-empty buffer state report (BSR) to the network device, and the network device sends downlink control information (DCI) to the terminal device, and the DCI carries an uplink grant (UL grant).
  • BSR non-empty buffer state report
  • DCI downlink control information
  • UL grant uplink grant
  • MTC machine type communication
  • mMTC massive machine type communication
  • NB-IoT narrow band internet of things
  • the data volume of the data to be transmitted by the terminal device is small (may be referred to as small packet data), and the terminal device has the requirement of low power consumption. If the terminal device transmits uplink data based on GB or dynamic scheduling, the system overhead is too large, the resource utilization efficiency is low, the power consumption of the terminal is too large, and the data transmission
  • a terminal device in a radio resource control (RRC) inactive (INACTIVE) state can transmit small packets of data in a random access (RA) process, or based on a grant-free (grant- free, GF) resource configuration to transmit small packet data, without the need to perform state transition to enter the RRC connection state and transmit small packet data based on GB or dynamic scheduling. This can save signaling overhead and reduce terminal power consumption.
  • RRC radio resource control
  • GF grant-free resource configuration
  • the data transmission process performed by the terminal equipment in the RRC inactive state without performing state transition needs to be further optimized.
  • the present application provides a data transmission method and a communication device, so as to improve the reliability of data transmission.
  • a data transmission method is provided, and the method can be executed by a terminal device or by a component of the terminal device (eg, a processor, a chip, or a chip system, etc.).
  • the method can be implemented by the following steps: when in the RRC idle (IDLE) state or the RRC INACTIVE state, sending uplink data to the network device through the first data radio bearer DRB, or sending the uplink data of the first data radio bearer DRB to the network device, Receive a first message from the network device, where the first message is used to instruct the terminal device to enter the RRC connected state, and send the uplink data of the first DRB to the network device through the second DRB.
  • the second DRB After the terminal device enters the connected state, the second DRB transmits the uplink data of the first DRB sent in the process of early data transmission, which can avoid the loss of uplink data caused by the early transmission of data due to state transition, and improve the reliability of uplink data transmission. .
  • the uplink data of the first DRB before sending the uplink data of the first DRB to the network device through the second DRB, the uplink data of the first DRB is reserved. Retaining can also be called not releasing.
  • the uplink data of the first DRB can be sent in time after the state transitions into the connected state, which not only shortens the transmission delay of the uplink small packet data, but also ensures that the uplink small packet data is not in the state transition process. will be lost.
  • retaining the uplink data of the first DRB may refer to retaining the packet data convergence protocol PDCP service data unit SDU corresponding to the first DRB, or may refer to retaining the PDCP protocol data unit PDU corresponding to the first DRB.
  • the discard timer corresponding to the PDCP SDU can also be stopped, and the discard timer corresponding to the PDCP PDU can also be stopped. It is avoided that the PDCP SDU and/or the PDCP PDU cause packet loss at the PDCP layer due to the expiration of the discard timer.
  • the terminal device retains the PDCP data corresponding to the first DRB
  • the PDCP SDU or PDCP PDU corresponding to the first DRB is processed by the SDAP layer corresponding to the first DRB to generate SDAP SDU, that is, application layer data.
  • SDAP SDU that is, application layer data.
  • the uplink data of the first DRB is reserved, and the SDAP layer data corresponding to the first DRB may also be reserved.
  • the service data adaptation protocol SDAP SDU corresponding to the first DRB is reserved, and for example, the SDAP PDU corresponding to the first DRB is reserved.
  • the SDAP data is the application layer data. According to the mapping relationship between the QoS flow associated with the second DRB and the DRB, it is determined that the application layer data is mapped to the second DRB.
  • the PDCP process generates a PDCP PDU of the second DRB.
  • a second message from the network device may also be received, where the second message is used to indicate the second DRB.
  • the second message is used to indicate the second DRB.
  • a DRB used for transmitting uplink data of the first DRB in the one or more DRBs may be determined according to the second message.
  • a DRB for transmitting uplink data of the first DRB in one or more DRBs may also be determined according to a rule.
  • the rule can be any one of the following: the second DRB is the DRB with the smallest identification among the one or more DRBs established by the terminal device; or, the second DRB is the DRB with the largest identification among the one or more DRBs established by the terminal device; or , the second DRB is a DRB with the same identifier as the first DRB among one or more DRBs established by the terminal device; or, the second DRB is a DRB determined according to a mapping rule of QoS flows to DRBs.
  • a data transmission method is provided, and the method can be executed by a terminal device or by a component of the terminal device (for example, a processor, a chip, or a chip system, etc.).
  • the method can be implemented by the following steps: when in the RRC inactive INACTIVE state, sending the uplink data of the first data radio bearer DRB to the first cell, performing cell reselection, and sending the uplink data of the first DRB to the second cell through the first DRB data, wherein the second cell is the target cell for cell reselection.
  • the uplink data of the first DRB sent in the early data transmission process is retransmitted through the first DRB, which can avoid the loss of uplink data due to the early data transmission caused by the cell reselection, and improve the transmission efficiency of uplink data. reliability.
  • the terminal device after performing cell reselection, the terminal device remains in the RRC_INACTIVE state, or the terminal device is still in the RRC_INACTIVE state, or the terminal device does not perform state transition, which means that the terminal device enters the idle state from the RRC_INACTIVE state.
  • the loss of uplink data on the previously transmitted first DRB due to entering the idle state is avoided.
  • the first DRB is suspended; and/or, after the cell reselection is performed, the PDCP entity corresponding to the first DRB is suspended. In this way, the UE context can be preserved.
  • the uplink data of the first DRB is reserved.
  • the PDCP SDU corresponding to the first DRB may be reserved, and the PDCP protocol data unit PDU corresponding to the first DRB may also be reserved.
  • the discard timer corresponding to the PDCP SDU may also be stopped, and the discard timer corresponding to the PDCP PDU may also be stopped. It is avoided that the PDCP SDU and/or the PDCP PDU cause packet loss at the PDCP layer due to the expiration of the discard timer.
  • the terminal device retains the PDCP data corresponding to the first DRB
  • the PDCP SDU or PDCP PDU corresponding to the first DRB is processed by the SDAP layer corresponding to the first DRB to generate SDAP SDU, that is, application layer data.
  • SDAP SDU that is, application layer data.
  • the uplink data of the first DRB is reserved, and the SDAP layer data corresponding to the first DRB may also be reserved.
  • the service data adaptation protocol SDAP SDU corresponding to the first DRB is reserved, and for example, the SDAP PDU corresponding to the first DRB is reserved.
  • the SDAP data is the application layer data. According to the mapping relationship between the QoS flow associated with the second DRB and the DRB, it is determined that the application layer data is mapped to the second DRB.
  • the PDCP process generates a PDCP PDU of the second DRB.
  • sending the uplink data of the first DRB may be considered as retransmitting the PDCP data of the first DRB, wherein the retransmission of the PDCP data of the first DRB may be implemented by performing the PDCP retransmission of the first DRB.
  • the establishment process; or, the RRC layer notifies the PDCP layer to retransmit the PDCP data corresponding to the first DRB.
  • PDCP re-establishment or retransmission of PDCP data may include the following process: the PDCP SDU corresponding to the first DRB may be retransmitted, and the PDCP PDU corresponding to the first DRB may also be retransmitted.
  • one or more of the following operations are performed: retaining the data of the first DRB, suspending the first DRB, or Suspend the PDCP entity corresponding to the first DRB.
  • a data transmission method is provided, and the method can be executed by a terminal device or by a component of the terminal device (for example, a processor, a chip, or a chip system, etc.).
  • the method can be implemented by the following steps: when in the RRC idle state or the RRC inactive INACTIVE state, based on the first data transmission mode, send the uplink data of the first data radio bearer DRB to the network device, from the first data transmission mode Fall back to the second data transmission mode, and send the uplink data of the first DRB to the network device through the second data transmission mode.
  • the terminal device can retransmit the uplink data of the first DRB in time to ensure that the uplink data transmitted early will not be lost and improve the early transmission of data. Performance in fallback scenarios.
  • the first data transmission method is based on random access RA to perform early data transmission, and the second data transmission method is based on configuration-based authorized CG to perform data early transmission; or, the first data transmission method is based on The CG performs early data transmission, and the second data transmission method is to perform data early transmission based on RA; or, the first data transmission method includes RA-based or CG-based data early transmission, and the second data transmission method is to enter the RRC connection state for data transmission. transmission.
  • sending the uplink data of the first DRB to the network device may be implemented in the following manner: retransmitting the RLC layer data on the uplink data of the first DRB; or, retransmitting the uplink data of the first DRB PDCP layer data retransmission; MAC layer data retransmission is performed for the uplink data of the first DRB.
  • a communication device may be a terminal device, a device in a terminal device (eg, a chip, or a chip system, or a circuit), or a device that can be used in conjunction with the terminal device.
  • the communication device may include modules corresponding to one-to-one execution of the methods/operations/steps/actions described in the first aspect, and the modules may be hardware circuits, software, or hardware circuits combined with software.
  • the communication device may include a processing module and a communication module. The processing module is used to call the communication module to perform the function of receiving and/or sending. Further, the communication module may also include a receiving module and a sending module.
  • the sending module is configured to: when in the RRC idle (IDLE) state or the RRC INACTIVE state, send the uplink data to the network device through the first data radio bearer DRB, or send the uplink data of the first data radio bearer DRB to the network device
  • the receiving module is used for: receiving the first message from the network device, the first message is used to instruct the terminal device to enter the RRC connection state, and the sending module is further used for: sending the uplink data of the first DRB to the network device through the second DRB.
  • the second DRB After the terminal device enters the connected state, the second DRB transmits the uplink data of the first DRB sent in the process of early data transmission, which can avoid the loss of uplink data caused by the early transmission of data due to state transition, and improve the reliability of uplink data transmission. .
  • the processing module is configured to: retain the uplink data of the first DRB before sending the uplink data of the first DRB to the network device through the second DRB. Retaining can also be called not releasing.
  • the uplink data of the first DRB can be sent in time after the state transitions into the connected state, which not only shortens the transmission delay of the uplink small packet data, but also ensures that the uplink small packet data is not in the state transition process. will be lost.
  • the processing module is used to: reserve the uplink data of the first DRB, which may refer to retaining the packet data convergence protocol PDCP service data unit SDU corresponding to the first DRB, or may refer to retaining the PDCP corresponding to the first DRB Protocol Data Unit PDU.
  • the processing module is further configured to: after receiving the first message from the network device, stop the discard timer corresponding to the PDCP SDU, and also stop the discard timer corresponding to the PDCP PDU. It is avoided that the PDCP SDU and/or the PDCP PDU cause packet loss at the PDCP layer due to the expiration of the discard timer.
  • the processing module is further configured to: if the PDCP data corresponding to the first DRB is reserved, the PDCP SDU or PDCP PDU corresponding to the first DRB is processed by the SDAP layer corresponding to the first DRB to generate the SDAP SDU, that is, Application layer data. According to the mapping relationship between the QoS flow associated with the second DRB and the DRB, it is determined that the application layer data is mapped to the second DRB, and the PDCP PDU of the second DRB is generated through the PDCP processing corresponding to the second DRB.
  • the processing module is further configured to: reserve the uplink data of the first DRB, and may also reserve SDAP layer data corresponding to the first DRB.
  • the service data adaptation protocol SDAP SDU corresponding to the first DRB is reserved, and for example, the SDAP PDU corresponding to the first DRB is reserved.
  • the processing module is further configured to: if the SDAP data corresponding to the first DRB is reserved, the SDAP data is the application layer data, and determine the application layer data mapping through the mapping relationship between the QoS flow associated with the second DRB and the DRB. To the second DRB, the PDCP PDU of the second DRB is generated after the PDCP processing corresponding to the second DRB.
  • the receiving module is further configured to: further receive a second message from the network device, where the second message is used to indicate the second DRB.
  • the second message is used to indicate the second DRB.
  • the processing module is further configured to: also determine a DRB used for transmitting uplink data of the first DRB in one or more DRBs according to a rule.
  • the rule can be any one of the following: the second DRB is the DRB with the smallest identification among the one or more DRBs established by the terminal device; or, the second DRB is the DRB with the largest identification among the one or more DRBs established by the terminal device; or , the second DRB is a DRB with the same identifier as the first DRB among one or more DRBs established by the terminal device; or, the second DRB is a DRB determined according to a mapping rule of QoS flows to DRBs.
  • a communication device in a fifth aspect, can be a terminal device, a device in a terminal device (eg, a chip, or a chip system, or a circuit), or a device that can be used in conjunction with the terminal device.
  • the communication device may include modules corresponding to one-to-one execution of the methods/operations/steps/actions described in the first aspect, and the modules may be hardware circuits, software, or hardware circuits combined with software.
  • the communication device may include a processing module and a communication module. The processing module is used to call the communication module to perform the function of receiving and/or sending. Further, the communication module may also include a receiving module and a sending module. Exemplarily:
  • the communication module is used for: sending the uplink data of the first data radio bearer DRB to the first cell when the RRC is in the inactive INACTIVE state; the processing module is used for: performing cell reselection; the communication module is further used for: sending to the first cell through the first DRB
  • the second cell sends the uplink data of the first DRB, wherein the second cell is the target cell for cell reselection.
  • the uplink data of the first DRB sent in the early data transmission process is retransmitted through the first DRB, which can avoid the loss of uplink data due to the early data transmission caused by the cell reselection, and improve the transmission efficiency of uplink data. reliability.
  • the processing module is further configured to: after the cell reselection is performed, retain the RRC_INACTIVE state, or remain in the RRC_INACTIVE state, or do not perform state transition, which means that the terminal device enters the idle state from the RRC_INACTIVE state. The loss of uplink data on the previously transmitted first DRB due to entering the idle state is avoided.
  • the processing module is further configured to: suspend the first DRB after performing the cell reselection; and/or suspend the PDCP entity corresponding to the first DRB after performing the cell reselection. In this way, the UE context can be preserved.
  • the processing module is further configured to: after the cell reselection is performed, retain the uplink data of the first DRB.
  • the PDCP SDU corresponding to the first DRB may be reserved, and the PDCP protocol data unit PDU corresponding to the first DRB may also be reserved.
  • the processing module is further configured to stop the discard timer corresponding to the PDCP SDU and also stop the discard timer corresponding to the PDCP PDU after the cell reselection is performed. It is avoided that the PDCP SDU and/or the PDCP PDU cause packet loss at the PDCP layer due to the expiration of the discard timer.
  • the processing module is further configured to: if the PDCP data corresponding to the first DRB is reserved, the PDCP SDU or PDCP PDU corresponding to the first DRB is processed by the SDAP layer corresponding to the first DRB to generate the SDAP SDU, that is, Application layer data. According to the mapping relationship between the QoS flow associated with the second DRB and the DRB, it is determined that the application layer data is mapped to the second DRB, and the PDCP PDU of the second DRB is generated through the PDCP processing corresponding to the second DRB.
  • the processing module is further configured to: reserve the uplink data of the first DRB, and may also reserve SDAP layer data corresponding to the first DRB.
  • the service data adaptation protocol SDAP SDU corresponding to the first DRB is reserved, and for example, the SDAP PDU corresponding to the first DRB is reserved.
  • the processing module is further configured to: if the SDAP data corresponding to the first DRB is reserved, the SDAP data is the application layer data, and determine the application layer data mapping through the mapping relationship between the QoS flow associated with the second DRB and the DRB. To the second DRB, the PDCP PDU of the second DRB is generated after the PDCP processing corresponding to the second DRB.
  • sending the uplink data of the first DRB may be considered as retransmitting the PDCP data of the first DRB, wherein the retransmission of the PDCP data of the first DRB may be implemented by performing the PDCP retransmission of the first DRB.
  • the establishment process; or, the RRC layer notifies the PDCP layer to retransmit the PDCP data corresponding to the first DRB.
  • the communication module is used for: retransmitting the PDCP SDU corresponding to the first DRB, and also retransmitting the PDCP PDU corresponding to the first DRB.
  • the processing module is further configured to perform one or more of the following operations after determining that the response message for the uplink data of the first DRB is not received from the network device: retain the data of the first DRB, hang up the Activate the first DRB, or suspend the PDCP entity corresponding to the first DRB.
  • a communication apparatus may be a terminal device, or a device in the terminal device (eg, a chip, or a chip system, or a circuit), or a device that can be matched with the terminal device.
  • the communication device may include modules corresponding to one-to-one execution of the methods/operations/steps/actions described in the first aspect, and the modules may be hardware circuits, software, or hardware circuits combined with software.
  • the communication device may include a processing module and a communication module. The processing module is used to call the communication module to perform the function of receiving and/or sending. Further, the communication module may also include a receiving module and a sending module.
  • the communication module is configured to: when in the RRC idle state or the RRC inactive INACTIVE state, send the uplink data of the first data radio bearer DRB to the network device based on the first data transmission mode; the processing module is configured to: Falling back from the first data transmission mode to the second data transmission mode; the communication module is further configured to: send the uplink data of the first DRB to the network device through the second data transmission mode.
  • the terminal device can retransmit the uplink data of the first DRB in time to ensure that the uplink data transmitted early will not be lost and improve the early transmission of data. Performance in fallback scenarios.
  • the first data transmission method is based on random access RA to perform early data transmission, and the second data transmission method is based on configuration-based authorized CG to perform data early transmission; or, the first data transmission method is based on The CG performs early data transmission, and the second data transmission method is to perform data early transmission based on RA; or, the first data transmission method includes RA-based or CG-based data early transmission, and the second data transmission method is to enter the RRC connection state for data transmission. transmission.
  • the communication module when sending the uplink data of the first DRB to the network device, is specifically configured to: retransmit the RLC layer data on the uplink data of the first DRB; or, retransmit the uplink data of the first DRB , perform PDCP layer data retransmission; perform MAC layer data retransmission for the uplink data of the first DRB.
  • a communication device in a seventh aspect, includes a communication interface and a processor, and the communication interface is used for the communication device to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in any one of the first aspect to the third aspect.
  • the communication apparatus may also include a memory for storing programs, instructions or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, the method described in any one of the first to third aspects above can be implemented.
  • the embodiments of the present application further provide a computer-readable storage medium, where computer-readable instructions are stored in the computer-readable storage medium, and when the computer-readable instructions are executed on a computer, the computer-readable instructions can The method described in any one of the one to third aspects is performed.
  • an embodiment of the present application provides a chip system, where the chip system includes a processor, and may further include a memory, for implementing the method described in any one of the first to third aspects.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • an embodiment of the present application provides a communication system, where the communication system includes a terminal device and a network device, where the terminal device is configured to execute the method described in any one of the first to third aspects.
  • a twelfth aspect provides a computer program product comprising instructions which, when run on a computer, cause the method as described in any of the first to third aspects to be performed.
  • FIG. 1 is a schematic diagram of a communication system architecture in an embodiment of the application
  • 2a is a schematic diagram of a user plane protocol stack in an embodiment of the application
  • FIG. 2b is a schematic diagram of a control plane protocol stack in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of state transition in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a process of early data transmission in four-step RA in an embodiment of the present application
  • FIG. 5 is a schematic diagram of a process of early data transmission in two-step RA in an embodiment of the present application
  • FIG. 6 is a schematic diagram of a process of CG-based early data transmission in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a data transmission method in an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another data transmission method in an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another data transmission method in an embodiment of the present application.
  • FIG. 10 is one of the schematic structural diagrams of the communication device in the embodiment of the application.
  • FIG. 11 is the second schematic diagram of the structure of the communication device according to the embodiment of the present application.
  • Embodiments of the present application provide a data transmission method and apparatus. Among them, the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • "and/or" describes the association relationship of the associated objects, indicating that there may be three kinds of relationships, for example, A and/or B may indicate that A exists alone, A and B exist simultaneously, and a single relationship exists. There are three cases of B.
  • the character "/" generally indicates that the associated objects are an "or” relationship. In this application, at least one refers to one or more; multiple refers to two or more.
  • the data transmission method provided by the embodiments of the present application may be applied to a fourth generation (4th generation, 4G) communication system, such as a long term evolution (long term evolution, LTE) communication system, and may also be applied to a fifth generation (5th generation, 5G) communication system A communication system, such as a 5G new radio (NR) communication system, or applied to various communication systems in the future, such as a 6th generation (6G) communication system.
  • the methods provided in the embodiments of the present application may also be applied to a Bluetooth system, a WiFi system, a LoRa system, or a car networking system.
  • the methods provided in the embodiments of the present application may also be applied to a satellite communication system, where the satellite communication system may be integrated with the above-mentioned communication system.
  • eMBB enhanced mobile broadband
  • ultra-reliable and low-latency communication ultra-reliable and low-latency communication
  • URLLC ultra-reliable low-latency communication
  • MTC machine type communication
  • mMTC massive machine type communication
  • D2D device-to-device
  • V2X vehicle to vehicle
  • IoT Internet of things
  • the communication system 100 includes a network device 101 and a terminal device 102 .
  • the apparatuses provided in the embodiments of the present application may be applied to the network device 101 or applied to the terminal device 102 .
  • FIG. 1 only shows a possible communication system architecture to which the embodiments of the present application can be applied, and in other possible scenarios, the communication system architecture may also include other devices.
  • the network device 110 is a node in a radio access network (radio access network, RAN), which may also be referred to as a base station, and may also be referred to as a RAN node (or device).
  • access network devices 101 are: gNB/NR-NB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (for example, home evolved NodeB, or home Node B, HNB) , base band unit (BBU), or wireless fidelity (wireless fidelity, Wifi) access point (access point, AP), satellite equipment, or network equipment in 5G communication systems, or possible future communication systems network equipment.
  • RNC transmission reception point
  • RNC radio network controller
  • Node B Node B
  • BSC Base Station Controller
  • BTS Base Transceiver Station
  • BBU base band
  • the network device 110 may also be other devices with network device functions.
  • the network device 110 may also be a device that functions as a network device in device to device (device to device, D2D) communication, vehicle networking communication, and machine communication.
  • the network device 110 may also be a network device in a possible future communication system.
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include a radio unit (RU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB, for example, CU implements radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP) layer functions
  • DU implements wireless chain
  • the functions of the road control radio link control, RLC
  • media access control media access control, MAC
  • physical (physical, PHY) layers The functions of the road control (radio link control, RLC), media access control (media access control, MAC) and physical (physical, PHY) layers.
  • the network device may be a CU node, a DU node, or a device including a CU node and a DU node.
  • the CU may be divided into network equipment in the access network RAN, and the CU may also be divided into network equipment in the core network CN, which is not limited herein.
  • the terminal device 102 also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice or data connectivity to users , or IoT devices.
  • the terminal device includes a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • terminal devices can be: mobile phones, tablet computers, notebook computers, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), in-vehicle devices ( For example, automobiles, bicycles, electric vehicles, airplanes, ships, trains, high-speed rails, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices ( For example, refrigerators, TVs, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in unmanned driving, wireless terminals in remote surgery, wireless terminals in smart grid, wireless terminals in transportation safety , wireless terminals in smart cities, or wireless terminals in smart homes, flying equipment (eg, smart robots, hot air balloons, drones, airplanes), etc.
  • MIDs mobile internet devices
  • wearable devices such as smart watches, smart bracelets, pedometers, etc.
  • in-vehicle devices For example, automobiles, bicycles, electric vehicles, airplanes
  • the terminal device may also be other devices with a terminal function, for example, the terminal device may also be a device serving as a terminal function in D2D communication.
  • the terminal device may also be a device serving as a terminal function in D2D communication.
  • a terminal device with a wireless transceiver function and a chip that can be installed in the aforementioned terminal device are collectively referred to as a terminal device.
  • the user plane protocol stack for communication between the terminal device and the network device includes a service data adaptation (SDAP) layer, a packet data convergence protocol (PDCP) layer, radio link control (radio link control, RLC) layer, medium access control (medium access control, MAC) layer and physical (physical, PHY) layer.
  • SDAP service data adaptation
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical
  • the control plane protocol stack for communication between terminal equipment and network equipment includes a non-access stratum (NAS) layer, a radio resource control (RRC) layer, and an SDAP layer.
  • NAS non-access stratum
  • RRC radio resource control
  • SDAP Secure Sockets Layer
  • RRC For the RRC layer, there are several RRC states of the terminal equipment, which are RRC idle (RRC_IDLE) state, RRC inactive (RRC_INACTIVE) state (also called the third state) and RRC connected (RRC_CONNECTED) state.
  • RRC idle RRC_IDLE
  • RRC_INACTIVE RRC inactive
  • RRC_CONNECTED RRC connected
  • the RRC_INACTIVE state is a state introduced for the terminal equipment in the 5G NR communication system, and the RRC_INACTIVE state is mainly aimed at the situation that "terminal equipment with infrequent data transmission is usually kept in the RRC_INACTIVE state by the network".
  • the terminal device starts to be in the RRC_IDLE state.
  • the terminal device will perform a random access procedure to establish an RRC connection with the network device and enter the RRC_CONNECTED state.
  • the terminal device starts data transmission after entering the RRC_CONNECTED state, where the RRC connection is established by sending a connection establishment request message, such as RRCSetupRequest, to the network device during the process of initiating random access by the terminal device, and receiving the connection establishment message sent by the network device, For example RRCSetup.
  • the network device may release the terminal device to make it transfer to the RRC_IDLE state or the RRC_INACTIVE state. For example, the network device sends a release message with a suspend indication, such as RRCRelease with suspend indication, so that the terminal device enters the RRC_INACTIVE state. Or the network device sends a release message, such as RRCRelease, to make the terminal device enter the RRC_IDLE state.
  • a suspend indication such as RRCRelease with suspend indication
  • the terminal device in the RRC_INACTIVE state can also return to the RRC_CONNECTED state through a resume (resume) message, for example, the terminal device sends an RRC resume request (RRCResumeRequest) and receives an RRC resume (RRCResume), returning to the RRC_CONNECTED state.
  • the network device can also release the terminal device to transfer it to the RRC_IDLE state.
  • the PDCP suspension operation may mean that the terminal device does not discard or save the PDCP service data unit (service data unit, SDU).
  • SDU service data unit
  • PDCP SDUs that are not discarded or saved may also be referred to as pending PDCP SDUs.
  • the suspended PDCP SDU can continue to be transmitted, thereby avoiding the loss of data packets during the state transition process.
  • the RRC_IDLE state can also be briefly described as the idle state or the IDLE state; the RRC_INACTIVE state can also be briefly described as the inactive state or the INACTIVE state; the RRC_CONNECTED state can also be briefly described as the connected state or the active state or the CONNECTED state.
  • the RRC_IDLE state or the RRC_INACTIVE state may also be referred to as the RRC disconnected state, and the RRC disconnected state may also be briefly described as the disconnected state.
  • RRC states which may also be simply referred to as states
  • a terminal device in an RRC idle state or an RRC inactive state may perform data transmission when no state transition is performed, which may be called early data transmission (EDT) or small data transmission (small data transmission, SDT) or inactive data transmission (IDT).
  • EDT early data transmission
  • SDT small data transmission
  • IDT inactive data transmission
  • the concepts of early data transmission EDT, small data transmission SDT and inactive data transmission can be replaced with each other.
  • the following uses early data transmission as an example for description.
  • Early data transmission can be considered that a terminal device in an RRC idle state or an RRC inactive state can transmit data without changing the state to enter the RRC connected state.
  • the data transmitted in the early data transmission may include user plane data, and the user plane data in this embodiment of the present application is simply referred to as data.
  • Early data transmission may include early transmission of uplink data and early transmission of downlink data.
  • the user plane data transmitted during the early transmission of uplink data may be referred to as uplink data.
  • the user plane data transmitted during the early transmission of downlink data may be called downlink data.
  • the data transmitted in the process of early data transmission can be called small data or small data, and the process of early data transmission can also be called small packet transmission.
  • Mode 1 Implement early data transmission in the random access (RA) process.
  • the RA-based small packet transmission means that the terminal device sends uplink data to the network device or receives downlink data during the RA process.
  • RA can include two-step RA and four-step RA.
  • the terminal device sends a message 1 (Msg1) to the network device, and the network device receives a message 1 (Msg1) from the terminal device, where the message 1 is a random access preamble (random access preamble).
  • Msg1 message 1
  • Msg1 random access preamble
  • the network device sends a message 2 (Msg2) to the terminal device, and the terminal device receives the message 2 from the network device.
  • Msg2 message 2
  • the message 2 is a random access response (random access response).
  • the terminal device sends a message 3 (Msg3) to the network device, and the network device receives the message 3 (Msg3) from the terminal device.
  • Msg3 message 3
  • Uplink data can be carried in Msg3.
  • the network device sends a message 4 (Msg4) to the terminal device, and the terminal device receives the message 4 from the network device.
  • Msg4 message 4
  • downlink data is carried in Msg4.
  • the terminal device sends a message A (MsgA) to the network device, and the network device receives the message A from the terminal device.
  • MsgA message A
  • Uplink data can be carried in MsgA.
  • the transmission channel of MsgA may include a physical random access channel (PRACH) and a physical uplink shared channel (PUSCH).
  • PRACH is used to send the random access preamble Preamble
  • PUSCH physical uplink shared channel
  • PRACH is used to send the random access preamble Preamble
  • Preamble is used by the network device to estimate the timing advance (Timing Advance) of the terminal device, so that the terminal device can achieve uplink synchronization with the network device.
  • the early transmitted uplink data can be sent through the PUSCH of the MsgA.
  • the network device returns a message B (MsgB) to the terminal, and the terminal device receives the message B from the network device.
  • MsgB message B
  • Downlink data can be carried in MsgB.
  • the early transmitted downlink data can be transmitted on the physical downlink shared channel PDSCH of the MsgB.
  • Method 2 Early data transmission based on grant-free (GF).
  • the network device pre-configures PUSCH resources and transmission parameters for the terminal device for uplink data transmission in a semi-static manner.
  • the terminal device When the terminal device has uplink data to send, it directly uses the pre-configured PUSCH resources and parameters to send data to the network device. It is not necessary to receive a dynamic UL grant from the network device, nor to send a Preamble for random access.
  • Pre-configured uplink resource (PUR) transmission in LTE and configured grant (CG) transmission in NR belong to the category of uplink grant-free transmission.
  • CG includes the first type (Type 1) CG and the second type (Type 2) CG.
  • the PUR-based transmission is similar to the Type 1 CG-based transmission.
  • the network device configures resources and transmission parameters for the terminal device through RRC signaling, for example, configure one or more of the following parameters: time domain resource period, open-loop power control related parameters , waveform, redundancy version sequence, repetition times, frequency hopping mode, resource allocation type, hybrid automatic retransmission request (HARQ) process number, demodulation reference signal (demodulation reference Signal, DMRS) related parameters, modulation Coding scheme (modulation and coding scheme, MCS) table, resource block (resource block group, RBG) group size, and time domain resources, frequency domain resources, MCS, etc.
  • HARQ hybrid automatic retransmission request
  • the network device adopts a two-step resource configuration method.
  • the network device sends the configured authorization configuration information through RRC signaling, and the configuration information is used to configure one or more of the following transmission resources and transmission parameters: period of time domain resources, open-loop power control related parameters, waveform, redundancy Remainder version sequence, repetition times, frequency hopping mode, resource allocation type, HARQ process number, demodulation reference signal related parameters, MCS table, RBG group size.
  • the PUSCH transmission of Type 2CG is activated by the downlink control information (DCI) scrambled with the configured scheduling radio network temporary identifier (CS-RNTI), and the PUSCH transmission including the time domain resources is configured at the same time , frequency domain resources, DMRS, MCS and other transmission resources and transmission parameters.
  • DCI downlink control information
  • CS-RNTI scheduling radio network temporary identifier
  • the terminal device sends an RRC resume request (RRCResumeResuest) message to the network device on the CG resource, and the network device receives the RRC resume request message from the terminal device.
  • RRC resume request RRCResumeResuest
  • the RRC recovery request message may carry uplink data.
  • the terminal device directly sends the uplink data on the CG resource without carrying the RRC recovery request message, and the network device receives the uplink data from the terminal device.
  • the network device returns an RRC release (Release) message to the terminal device, and the terminal device receives the RRC release (Release) message from the network device.
  • the RRC release (Release) message is used to instruct the terminal device to continue to stay in the RRC_INACTIVE state.
  • the network device may also send downlink data, and the downlink data may be multiplexed with the RRC release message, or may be separately sent to the terminal before the RRC release message.
  • the network device does not send the RRC release message to the terminal, which may correspond to the situation in S601 when the terminal device directly sends the uplink data on the CG resource.
  • the terminal device Based on the license-free small packet transmission, the terminal device does not need to send the preamble, so it is more suitable for the scenario where the terminal device and the network device are in a synchronized state. Compared with the RA-based solution, signaling overhead and terminal device power consumption can be further saved.
  • the terminal device When the terminal device is in the disconnected state, it sends the uplink small packet data to the network device.
  • the network device may not be able to correctly parse the early transmitted uplink small packet data, and the network device may instruct the terminal device to enter the connected state. For example, after receiving the uplink small packet data from the terminal device, the network device needs to obtain the UE context to be able to correctly parse the uplink small packet data. If the network device cannot obtain the UE context, the network device cannot correctly parse the early transmitted uplink small packet data. In this way, the network device may send an RRC connection establishment message to the terminal device, so that the terminal device enters the RRC connection state.
  • the RB can be a data radio bearer (DRB) or a signaling radio bearer (signaling radio bearer).
  • bearer, SRB bearer
  • the terminal device when the data is transmitted early, the RB may be restored, and the suspended PDCP entity corresponding to the RB may also be restored.
  • the terminal device After the terminal device sends small packets of data to the network device, if the network device instructs the terminal device to enter the connected state, the terminal device will release all established RBs, release the PDCP entity corresponding to the RB, and discard the saved PDCP corresponding to the RB.
  • SDU and/or PDCP protocol data unit (protocol data unit, PDU), thereby causing the loss of uplink small packet data that has already initiated transmission.
  • the embodiments of the present application provide a data transmission method, so as to improve the reliability of uplink data transmission.
  • the flow of a data transmission method provided by an embodiment of the present application is as follows.
  • the terminal device When in the RRC idle state or the RRC inactive state, the terminal device sends the uplink data of the first DRB to the network device.
  • the network device receives the uplink data of the first DRB from the terminal device.
  • the first DRB may be one or more DRBs, and when the first DRB is multiple DRBs, the data of the multiple DRBs may be multiplexed into one MAC PDU.
  • the network device sends a first message to the terminal device, where the first message is used to instruct the terminal device to enter the RRC connection state.
  • the terminal device receives the first message from the network device.
  • the terminal device sends the uplink data of the first DRB to the network device through the second DRB.
  • the second DRB transmits the uplink data of the first DRB sent in the process of early data transmission, which can avoid the loss of uplink data caused by the early transmission of data due to state transition, and improve the reliability of uplink data transmission. , which optimizes the early data transmission process.
  • the terminal device may establish a first DRB with the network device, and transmit the uplink data through the first DRB, and the uplink data may be referred to as the uplink data of the first DRB.
  • the process of establishing the first DRB can also be considered as restoring the first DRB, that is, restoring the relevant configuration of the first DRB, the PDCP entity. Therefore, the uplink data to be transmitted can be processed by entities such as SDAP, PDCP, and RLC associated with the first DRB to generate a MAC SDU.
  • the uplink data of the first DRB may be transmitted through message 3, message A or CG resources.
  • the uplink data of the first DRB may be carried in message 3 or message A.
  • the uplink data of the first DRB may be sent through the CG resource.
  • a possible method is that the uplink data of the first DRB can be carried in an RRC message, and the RRC message can be an RRC resume request (RRC resume request) message or an RRC resume request 1 (RRC resume request) message. request 1) message.
  • the RRC recovery request message and the RRC recovery request 1 are used to carry RRC messages of different sizes.
  • the RRC message may also carry the identifier of the terminal device, for example, the identifier of the terminal device in the RRC inactive state (inactive radio network temporary identifier, I-RNTI).
  • the identity of the terminal device is used by the network device to obtain the UE context.
  • the RRC message may also carry integrity protection check information, which is used by the network device to check whether the content of the RRC message is complete.
  • the RRC message may also carry a cause value, which is used to indicate the purpose of the current RRC connection recovery of the network device, for example, the purpose of the RRC connection recovery is uplink small packet transmission.
  • the RRC message and the uplink data can be multiplexed in the same MAC PDU, and the RRC message and the uplink data can be transmitted through one data packet, which is similar when the uplink data is transmitted through the message 3 or the message A.
  • Another possible way is to not carry the RRC message, and the terminal device sends the uplink data of the first DRB through the CG resource.
  • the identifier of the terminal device can also carry the identifier of the terminal device, for example, the cell-radio network temporary identifier Identifier, C-RNTI), or all or part of the bits of I-RNTI, the identifier of the terminal device can be used as a MAC control element (control element, CE) multiplexed with uplink data in the same MAC PDU, through a data packet The identification of the terminal equipment and the uplink data are transmitted.
  • C-RNTI cell-radio network temporary identifier Identifier
  • CE control element
  • a possible way is: for example, if the CG resource is a shared resource, that is, more than one terminal device can use the CG resource for early data transmission, in this case, the terminal device sends the first data in the CG resource.
  • the uplink data of a DRB can carry the identifier of the terminal equipment, so that the base station equipment can identify which terminal equipment the uplink data transmitted through early data transmission belongs to; on the contrary, if the CG resource is an exclusive resource, that is, the CG resource It is not shared with other terminal devices. In this case, the terminal device may not carry the identifier of the terminal device when the CG resource sends the uplink data of the first DRB.
  • whether the terminal device needs to carry the identifier of the terminal device when the CG resource sends the uplink data of the first DRB can be indicated by the network device, for example, through an RRC message to inform the terminal device whether it needs to carry the identifier of the terminal device or whether the CG resource needs to carry the identifier of the terminal device or not. It is a shared or exclusive resource, so that when the terminal device performs early data transmission, it can be judged according to the indication whether it is necessary to carry the identifier of the terminal device on the CG resource.
  • the network device will return the message B or the message 4 to the terminal device.
  • Message B or message 4 may carry contention resolution (contention resolution) information, and the contention resolution information may be all or part of bits of message 3.
  • the conflict resolution information is used to indicate that the uplink data transmission is successful.
  • message B can also carry uplink timing advance command (timing advance command, TAC) information, and after receiving the TAC, the terminal device can use the TA value corresponding to the TAC to synchronize the uplink timing.
  • TAC timing advance command
  • the terminal device can use the TA value corresponding to the TAC to synchronize the uplink timing.
  • the synchronization of uplink timing can further be used for subsequent early transmission of data based on the CG method.
  • message B or message 4 can also carry uplink authorized resources. Further, the terminal device can use the uplink authorized resources for subsequent transmission. Transmission of upstream data.
  • the network device may return message B or message 4 or a new MAC layer response message to the terminal device.
  • the message B or message 4 or the new MAC layer message may carry conflict resolution information, and the conflict resolution information may be all or part of the bits of the terminal equipment identifier transmitted by the CG resource.
  • the conflict resolution information is used to indicate that the uplink data transmission is successful; another possible way is: the network device returns an RRC release message to the terminal device, and the terminal device considers that the uplink data transmission is successful after receiving the RRC release message.
  • the network device may also send a response message of physical downlink control channel (physical downlink control channel, PDCCH) transmission to the terminal device.
  • PDCCH physical downlink control channel
  • the network device successfully receives the uplink data, it can send a successful acknowledgement (acknowledgement, ACK) to the terminal device, and the terminal device can determine that the uplink data is successfully sent after receiving the ACK.
  • ACK acknowledgement
  • NACK error response
  • the terminal device After the terminal device receives the NACK, it can determine that the uplink data transmission failed, and further , the terminal device can initiate retransmission when the uplink data transmission fails.
  • the terminal may start a timer after sending the uplink data of the first DRB, and monitor the transmission of the PDCCH during the running of the timer.
  • the uplink data response message of the first DRB transmitted by the PDCCH is not monitored, and the response message can be the above-mentioned message B or message 4 or a new MAC layer response message or RRC release message or PDCCH transmission response message
  • the terminal device can determine that the uplink data is sent successfully, so that the response message is not required; or the terminal device considers that the uplink data transmission failed, and thus retransmits the uplink data in the message A or the CG resource.
  • S702 After S701, if the network device cannot correctly receive the uplink data of the first DRB, S702 will be executed.
  • the failure of the network device to correctly receive the uplink data of the first DRB may be based on the following possible scenarios.
  • the network device is a serving network device of the terminal device, and the serving network device may not save the UE context. This is when the serving network device needs to initiate a UE context acquisition process after receiving the uplink data.
  • the serving network device sends a UE context acquisition request to the anchor network device, where the UE context acquisition request is used to request the UE context.
  • the anchor network device is a network device that saves the UE context. Before the serving network device sends the UE context acquisition request to the anchor network device, the serving network device may receive the identity of the terminal device, the identity of the anchor network device and/or the identity of the UE context from the terminal device.
  • the UE context acquisition request sent by the serving network device may carry the identity of the terminal device and/or the identity of the UE context.
  • the anchor network device After receiving the UE context acquisition request from the serving network device, the anchor network device acquires the UE context according to the identity of the terminal device and/or the identity of the UE context. If the anchor network device cannot obtain the UE context, or the anchor network device cannot successfully verify the identity of the terminal device, or the anchor network device decides not to provide the UE context to the serving network device, the anchor network device returns the UE to the serving network device Context get failure message.
  • the network device determines that the terminal device needs to enter the RRC connection state, and executes S702.
  • the first message sent by the network device to the terminal device is used to instruct the terminal device to enter the RRC connection state, and the first message may be an RRC connection establishment message or an RRC release (RRC release) message.
  • the first message is used to instruct the terminal device to establish a new RRC connection.
  • S704 may also be included.
  • the terminal device retains the uplink data of the first DRB. Retaining can also be called not releasing. The following takes reservation as an example.
  • Reserving the uplink data of the first DRB may be implemented in the following manner A or manner B.
  • Manner A The PDCP layer data corresponding to the first DRB is reserved.
  • the PDCP SDU corresponding to the first DRB may be reserved.
  • the PDCP PDU corresponding to the first DRB may be reserved, and for another example, the PDCP SDU corresponding to the first DRB and the corresponding PDCP PDU may be reserved.
  • the PDCP entity may be responsible for compressing and decompressing Internet Protocol (IP) and/or Ethernet Protocol (ethernet) headers, transmitting user plane data, and maintaining sequence numbers (SNs) for radio bearers.
  • IP Internet Protocol
  • ethernet Ethernet Protocol
  • the PDCP entity can process RRC messages on the control plane and IP packets on the user plane.
  • the PDCP layer can perform header compression and encryption on the IP data packet, and then deliver it to the RLC sublayer.
  • the PDCP layer can also provide sequential submission and duplicate packet detection functions to the upper layer according to the SN of the PDCP data packet.
  • the PDCP layer processing procedure may include the following steps. After the PDCP layer receives the PDCP SDU, it sets a discard timer (discardTimer) corresponding to the PDCP SDU; and sets the PDCP SN corresponding to the SDU, so as to assign the PDCP header (Header) corresponding to the SDU; compresses the upstream data. ;;Add the PDCP header (Header) to the PDCP SDU to generate the PDCP PDU, and can set the discard timer corresponding to the PDCP PDU; send the PDCP PDU to the RLC layer.
  • discardTimer a discard timer corresponding to the PDCP SDU
  • PDCP SN corresponding to the SDU
  • the terminal device When the terminal device sends the uplink data of the first DRB to the network device in S701, the PDCP layer corresponding to the first DRB starts a discard timer. After receiving the first message from the network device in S702, the terminal device can also stop the discard timer corresponding to the PDCP SDU, and can also stop the discard timer corresponding to the PDCP PDU. It is avoided that the PDCP SDU and/or the PDCP PDU cause packet loss at the PDCP layer due to the expiration of the discard timer.
  • Retaining the PDCP layer data corresponding to the first DRB may be an operation determined by the PDCP layer, or may be notified by the RRC layer to the PDCP layer. For example, after receiving the first message from the network device, the terminal device notifies the PDCP layer through the RRC layer to reserve the PDCP layer data corresponding to the first DRB.
  • Manner B Retain SDAP layer data corresponding to the first DRB.
  • the SDAP SDU corresponding to the first DRB may be reserved.
  • the SDAP PDU corresponding to the first DRB may be reserved, and for another example, the PDCP SDU corresponding to the first DRB and the corresponding PDCP PDU may be reserved.
  • the SDAP layer data corresponding to the first DRB may be processed. For example, assuming that the SDAP SDU corresponding to the first DRB is reserved, the SDAP SDU can be processed to generate an SDAP PDU, and the SDAP PDU is sent to the PDCP layer to continue processing. Assuming that the SDAP PDU corresponding to the first DRB is reserved, the reserved SDAP PDU can be sent to the PDCP layer to continue processing.
  • Retaining SDAP layer data corresponding to the first DRB may be an operation determined by the SDAP layer, or may be notified by the RRC layer to the SDAP layer, or may be notified by the RRC layer to the PDCP layer, and then the PDCP layer notifies the SDAP layer. For example, after receiving the first message from the network device, the terminal device notifies the SDAP layer through the RRC layer to reserve the PDCP layer data corresponding to the first DRB.
  • the network device may return a response message to the terminal device to indicate whether the uplink data of the first DRB is successfully received, and the response message also It can be used to respond to other information sent together with the uplink data of the first DRB in S701.
  • the terminal device executes S704 to retain the uplink data of the first DRB.
  • the terminal device after the terminal device sends the uplink data of the first DRB to the network device in S701, the terminal device maintains a timer for judging whether the uplink data of the first DRB is successfully received.
  • the terminal device executes S704 and retains the uplink data of the first DRB.
  • the terminal device sends the uplink data of the first DRB to the network device through the second DRB, and the uplink data of the first DRB is referred to as uplink data for short.
  • the terminal device can process the PDCP SDU of the uplink data through the PDCP entity corresponding to the second DRB to generate the PDCP PDU.
  • the process of processing by the PDCP entity corresponding to the second DRB may include one or more of assigning a sequence number, encryption or integrity protection.
  • the terminal device retains the PDCP data corresponding to the first DRB
  • the PDCP SDU or PDCP PDU corresponding to the first DRB is processed by the SDAP layer corresponding to the first DRB to generate SDAP SDU, that is, application layer data.
  • SDAP SDU that is, application layer data.
  • the SDAP data is the application layer data. According to the mapping relationship between the QoS flow associated with the second DRB and the DRB, it is determined that the application layer data is mapped to the second DRB.
  • the PDCP process generates a PDCP PDU of the second DRB.
  • the terminal device After the terminal device receives the first message from the network device, the terminal device enters the RRC connection state. After the terminal device enters the RRC connected state or during the process of the terminal device entering the RRC connected state, the terminal device may establish a second DRB with the network device. Optionally, after S702 and before S703, S705 may also be included. The order of S705 and S704 is not limited.
  • the network device sends the second message to the terminal device, and the terminal device receives the second message from the network device.
  • the second message is used to establish the second DRB.
  • the second message may be an RRC message, for example, the RRC message may be an RRC reconfiguration (RRC reconfiguration) message.
  • RRC message may be an RRC reconfiguration (RRC reconfiguration) message.
  • the second message may also carry any one or more of the following information: the identifier of the second DRB; the PDCP configuration, which is used to configure the parameters of the PDCP entity associated with the second DRB, including parameters such as the length of the sequence number of the PDCP; SDAP configuration, For configuring the parameters of the SDAP entity associated with the second DRB, including the mapping relationship between the quality of service (quality of service, QoS) flow to the second DRB, for indicating the QoS flow identity (QoS flow identity, QFI) mapped to the second DRB ).
  • the quality of service quality of service
  • QoS quality of service
  • QFI QoS flow identity
  • the network device may establish one or more DRBs with the terminal device. Then how the terminal device determines the second DRB used to send the uplink data of the first DRB in one or more DRBs, some optional implementations may be provided in the embodiments of the present application.
  • the terminal device determines the second DRB according to the rules.
  • the rule may be, for example: the DRB with the smallest identification among the one or more DRBs; the DRB with the largest identification among the one or more DRBs; the DRB with the same identification as the first DRB among the one or more DRBs; or a randomly selected DRB.
  • DRB, or the DRB to be mapped is determined according to the mapping relationship between the QoS flow and the DRB.
  • the rule may be predefined by a protocol, or may be notified by the network device to the terminal device, for example, the rule may be notified by a second message. This rule can also be implemented by the terminal device.
  • the second DRB used to send the uplink data of the first DRB can also be indicated by the second message.
  • the second message includes the identifier of the second DRB, and the terminal device can Identify, determine the second DRB used for sending the uplink data of the first DRB.
  • the configurations of the first DRB and the second DRB may be different, for example, the PDCP configurations of the first DRB and the second DRB are different, and the PDCP configurations include keys and/or encryption algorithms.
  • FIG. 7 the embodiment of FIG. 7 and some possible implementation manners can improve the reliability of uplink data transmission.
  • a terminal device in an RRC inactive state may camp in a cell. Due to the mobility of the terminal equipment, cell reselection may occur to the terminal equipment. For example, after the terminal equipment moves, it may be necessary to change to another cell with a higher priority or better signal to camp on, so that cell reselection occurs. If the terminal device in the RRC inactive state sends the uplink small packet data to the source cell during the early data transmission process, the cell reselection occurs and enters the target cell, then the terminal device will not receive the source cell's response to the uplink data. And the terminal device will enter the RRC idle state.
  • the terminal equipment in the RRC inactive state Since the terminal equipment in the RRC inactive state has already resumed the RB during the early data transmission process, it is also possible to resume the PDCP entity whose corresponding RB has been suspended.
  • the terminal equipment When the terminal equipment enters the target cell and switches to the RRC idle state, the terminal equipment will release the established RB, release the PDCP entity corresponding to the RB, and discard the saved PDCP SDU and/or PDCP PDU of the corresponding RB, thus causing the The upstream packet data that initiated the transmission is lost.
  • the embodiments of the present application provide another data transmission method, so as to improve the reliability of uplink data transmission.
  • the flow of another data transmission method provided by an embodiment of the present application is as follows.
  • the terminal device When the terminal device is in the RRC inactive state, it sends the uplink data of the first DRB to the first cell, and the first cell receives the uplink data of the first DRB from the terminal device.
  • the process of cell reselection may be that the terminal equipment switches from camping on the first cell to camping on the second cell.
  • the first cell may be considered as the source cell, and the second cell may be considered as the target cell.
  • the first cell and the second cell may be located in the same network device or different network devices, and the first cell and the second cell may be different cells, or may be the same cell.
  • the second cell is the target cell of the cell reselection in S802, or the second cell is the cell where the terminal device resides after the cell reselection in S802.
  • the uplink data of the first DRB sent in the data early transmission process is retransmitted through the first DRB, so that the uplink data loss due to the early data transmission caused by the cell reselection can be avoided.
  • the reliability of uplink data transmission is improved, and the data early transmission process is optimized.
  • the terminal device may perform the following optional operation 1.
  • the terminal device retains the RRC_INACTIVE state, or the terminal device is still in the RRC_INACTIVE state, or the terminal device does not perform state transition, which means that the terminal device enters the idle state from the RRC_INACTIVE state.
  • the terminal device may also perform one or more of the following optional operations 2: suspend the first DRB; suspend the PDCP corresponding to the first DRB entity.
  • the terminal device in the RRC_INACTIVE state sends the uplink data of the first DRB to the first cell.
  • the terminal device has recovered the first DRB, and may also have recovered the PDCP entity corresponding to the first DRB.
  • the terminal device After sending the uplink data of the first DRB, the terminal device performs cell reselection. In this case, the terminal device will not enter the RRC idle state, but will suspend the first DRB again and/or suspend the corresponding cell of the first DRB.
  • the UE context can be preserved.
  • the first DRB may be restored again, and the PDCP entity corresponding to the first DRB may be restored again, so as to send the uplink data of the first DRB to the second cell through the first DRB. In this way, it can be ensured that the uplink data of the first DRB will not be lost in the process of early data transmission.
  • the terminal device may also perform the following optional operation 3: Retain the uplink data of the first DRB.
  • optional operation 3 reference may be made to the specific descriptions of the optional implementation manners of S704 and S704 above, which will not be repeated here.
  • the terminal device performs optional operation 1, optional operation 2 or optional operation 3, which can be performed based on the following conditions.
  • the terminal device does not receive a response message from the network device, where the response message is a response message for the uplink data of the first DRB transmitted in S801. It can be an ACK message or a NACK message, or a response message from other protocol layers.
  • the terminal device can send uplink data to the first cell through the first DRB, and in S803, send the uplink data of the first DRB to the second cell through the first DRB.
  • S803 may be considered as retransmitting the PDCP data of the first DRB.
  • the retransmission of the PDCP data of the first DRB may be implemented in the following manner: performing the PDCP re-establishment process of the first DRB; or, the RRC layer notifies the PDCP layer to retransmit the PDCP data corresponding to the first DRB.
  • the PDCP re-establishment or retransmission of PDCP data may include the following process: the PDCP SDU corresponding to the first DRB may be retransmitted, and the PDCP PDU corresponding to the first DRB may also be retransmitted.
  • the terminal device may perform retransmission of the PDCP SDU starting from the first SDU corresponding to the PDCP PDU that has not received a successful RLC response. That is, the PDCP SDU corresponding to the uplink data of the first DRB is processed and retransmitted, and the processing may include operations such as reassigning the sequence number of the PDCP, encryption, and the like.
  • FIG. 8 the embodiment of FIG. 8 and some possible implementation manners can improve the reliability of uplink data transmission.
  • the fallback operation can also be called a data transmission mode switch (switch). For example, switching from a CG-based mode to an RA-based mode, switching from early data transmission to data transmission in the connected state, and switching back and data transmission modes can be replaced with each other. , the following is an example of rollback.
  • the fallback may mean that the terminal device is converted from one data transmission mode to another data transmission mode to perform data early transmission, or it may refer to the terminal device performing state transition to enter the connection state for data early transmission. For example, a terminal device in a disconnected state performs early data transmission based on RA, and falls back to early data transmission based on CG.
  • a terminal device in a disconnected state performs early data transmission in a CG-based manner, and falls back to an RA-based manner for early data transmission.
  • a terminal device in a disconnected state performs data transmission after being converted from a disconnected state to a connected state. Fallback generally occurs after multiple data transfer failures based on one data transfer method.
  • the terminal device may clear the cached uplink data. For example, the previously transmitted uplink data exists in the HARQ cache. If the terminal device performs HARQ cache clearing, or the terminal device has new data arriving, the existing HARQ buffer is overwritten. The data in the cache will cause the loss of uplink data.
  • the embodiments of the present application provide another data transmission method, so as to improve the reliability of uplink data transmission.
  • the flow of another data transmission method provided by an embodiment of the present application is as follows.
  • the terminal device When the terminal device is in the RRC idle state or the RRC inactive state, the terminal device sends the uplink data of the first DRB to the network device, and the network device receives the uplink data of the first DRB from the terminal device.
  • the terminal device may use the first data transmission mode to transmit uplink data.
  • the first data transmission mode may be early data transmission based on RA, or early data transmission based on CG, or early data transmission in a disconnected state.
  • the terminal device falls back from the first data transmission mode to the second data transmission mode.
  • the second data transmission mode may be based on the CG method for early data transmission or data transmission after entering the connected state.
  • the first data transmission method is based on the CG method for early data transmission
  • the second data transmission method may be based on the RA method for early data transmission or data transmission after entering the connected state.
  • the terminal device may perform rollback when any one or more of the following conditions are met.
  • Condition 1 The transmission of the uplink data of the first DRB fails at least once.
  • the network device may further configure a threshold, and rollback is performed when the number of failures to transmit the uplink data of the first DRB equals or exceeds the threshold.
  • Condition 2 The uplink data of the first DRB is sent based on the first data transmission mode, and the condition of the first data transmission mode is no longer satisfied.
  • the data volume of the uplink data of the first DRB is greater than the threshold required by the first data transmission mode.
  • the first data transmission mode is the CG-based mode
  • the uplink TA of the terminal device loses synchronization, the condition for early data transmission based on the CG-based mode is no longer satisfied.
  • Condition 3 The network device instructs the terminal device to roll back, for example, the network device delivers an RRC connection recovery message to the terminal device, so that the terminal device transitions from a disconnected state to a connected state.
  • the terminal device sends the uplink data of the first DRB to the network device through the second data transmission mode, and the network device receives the uplink data of the first DRB from the terminal device.
  • the terminal device When the second data transmission mode is RA-based or CG-based early data transmission, the terminal device keeps the state unchanged, or the terminal device does not switch to the connected state, and sends the first DRB to the network device through the second data transmission mode upstream data.
  • the terminal device When the second data transmission mode is to enter the connected state for data transmission, after the terminal device enters the connected state, it sends the uplink data of the first DRB to the network device in the connected state. For example, with reference to the manner of the embodiment in FIG. 7 , a second DRB may be established, and uplink data of the first DRB may be sent on the second DRB.
  • the terminal device After the terminal device falls back from the first data transmission mode to the second data transmission mode in S902, the terminal device sends the uplink data of the first DRB to the network device through the second data transmission mode, that is, the terminal device triggers the uplink data of the first DRB Retransmission.
  • the retransmission of the uplink data of the first DRB may be triggered from different protocol layers.
  • RLC layer data retransmission is performed on the uplink data of the first DRB.
  • the RLC entity is triggered to retransmit the RLC SDU or RLC PDU corresponding to the RLC sequence number of the uplink data, and further, the RLC SDU can perform RLC repacketization, thereby sending in S903 Repackaged RLC packets.
  • the terminal device can indicate to the RLC entity through the RRC layer or the MAC layer that it is a negative response to the RLC SDU or RLC PDU corresponding to the uplink data, thereby triggering the RLC entity to retransmit the RLC SDU or RLC PDU.
  • PDCP layer data retransmission is performed on the uplink data of the first DRB.
  • the PDCP entity is triggered to retransmit the PDCP SDU or PDCP PDU corresponding to the PDCP sequence number of the uplink data. Packed PDCP packets.
  • MAC layer data retransmission is performed on the uplink data of the first DRB.
  • the MAC layer buffer For the MAC layer buffer corresponding to the uplink data of the first DRB, for example, the MAC layer buffer corresponding to message A or message 3 or the CG resource, the MAC layer buffer stores the MAC sub-PDU or complete MAC sub-PDU corresponding to the uplink data of the first DRB.
  • the terminal device can retransmit the uplink data of the first DRB in time to ensure that the uplink data transmitted early will not be lost and improve the early transmission of data. Performance in fallback scenarios.
  • the terminal device may include hardware structures and/or software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • an embodiment of the present application also provides a communication apparatus 1000 .
  • the communication apparatus 1000 may be a terminal device, a device in a terminal device, or a device that can be used in combination with a terminal device. installation.
  • the communication apparatus 1000 may include modules that perform one-to-one correspondence with the methods/operations/steps/actions performed by the terminal device in the above method embodiments.
  • the modules may be hardware circuits, software, or hardware.
  • the circuit is implemented in combination with software.
  • the communication device 1000 may include a communication module 1001 and a processing module 1002 .
  • the communication module 1001 may further include a receiving module 1001-1 and a sending module 1001-2.
  • the processing module 1002 is configured to call the communication module 1001 to receive and/or send signals.
  • the sending module 1001-2 is configured to: when in the RRC idle (IDLE) state or the RRC INACTIVE state, send uplink data to the network device through the first data radio bearer DRB, or send the uplink data of the first data radio bearer DRB to the network device.
  • the receiving module 1001-1 is configured to: receive a first message from the network device, where the first message is used to instruct the terminal device to enter the RRC connection state.
  • the sending module 1001-2 is further configured to: send the uplink data of the first DRB to the network device through the second DRB.
  • the receiving module 1001-1, the sending module 1001-2, and the processing module 1002 are further configured to perform other operations performed by the terminal device in the foregoing method embodiment of FIG. 7, which will not be repeated here.
  • the communication module 1001 is configured to: when in the RRC inactive INACTIVE state, send uplink data of the first data radio bearer DRB to the first cell.
  • the processing module 1002 is used for: performing cell reselection.
  • the communication module 1001 is further configured to: send the uplink data of the first DRB to the second cell through the first DRB, where the second cell is a target cell for cell reselection.
  • the communication module 1001 and the processing module 1002 are further configured to perform other operations performed by the terminal device in the foregoing method embodiment of FIG. 8 , which will not be repeated here.
  • the communication module 1001 is configured to: send uplink data of the first data radio bearer DRB to the network device based on the first data transmission mode when in the RRC idle state or the RRC inactive INACTIVE state.
  • the processing module 1002 is configured to: fall back from the first data transmission mode to the second data transmission mode.
  • the communication module 1001 is further configured to: send the uplink data of the first DRB to the network device through the second data transmission mode.
  • the communication module 1001 and the processing module 1002 are further configured to perform other operations performed by the terminal device in the foregoing method embodiment of FIG. 9 , which will not be repeated here.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of the present application may be integrated into one processing unit. In the device, it can also exist physically alone, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.
  • a communication apparatus 1100 provided by an embodiment of the present application is used to implement the function of the terminal device in the above method.
  • the device may be a terminal device, or a device in the terminal device, or a device that can be used in combination with the terminal device.
  • the device may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication apparatus 1100 includes at least one processor 1120, configured to implement the function of the terminal device in the method provided in the embodiment of the present application.
  • the communication device 1100 may also include a communication interface 1110 .
  • the communication interface may be a transceiver, a circuit, a bus, a module or other types of communication interfaces, which are used to communicate with other devices through a transmission medium.
  • the communication interface 1110 is used for the apparatus in the communication apparatus 1100 to communicate with other devices.
  • the processor 1120 uses the communication interface 1110 to send and receive data, and is used to implement the methods described in the above method embodiments.
  • the processor 1120 uses the communication interface 1110 to: when in the RRC idle (IDLE) state or the RRC INACTIVE state, send the uplink data to the network device through the first data radio bearer DRB, or send the uplink data to the network device.
  • the device sends the uplink data of the first data radio bearer DRB.
  • the processor 1120 is further configured to receive a first message from the network device using the communication interface 1110, where the first message is used to instruct the terminal device to enter the RRC connection state.
  • the processor 1120 is further configured to: send the uplink data of the first DRB to the network device through the second DRB.
  • the processor 1120 uses the communication interface 1110 to: when in the RRC inactive INACTIVE state, send the uplink data of the first data radio bearer DRB to the first cell.
  • the processor 1120 is configured to: perform cell reselection.
  • the processor 1120 is further configured to use the communication interface 1110 to send the uplink data of the first DRB to the second cell through the first DRB, where the second cell is a target cell for cell reselection.
  • the processor 1120 uses the communication interface 1110 to: when in the RRC idle state or the RRC inactive INACTIVE state, send the first data radio bearer DRB to the network device based on the first data transmission mode upstream data.
  • the processor 1120 is configured to: fall back from the first data transmission mode to the second data transmission mode.
  • the processor 1120 is further configured to: send the uplink data of the first DRB to the network device through the second data transmission manner.
  • the processor 1120 and the communication interface 1110 may also be used to perform other corresponding steps or operations performed by the terminal device in the foregoing method embodiments, which will not be repeated here.
  • Communication apparatus 1100 may also include at least one memory 1130 for storing program instructions and/or data.
  • Memory 1130 and processor 1120 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1120 may cooperate with the memory 1130.
  • the processor 1120 may execute program instructions stored in the memory 1130 . At least one of the at least one memory may be integrated with the processor.
  • the specific connection medium between the communication interface 1110 , the processor 1120 , and the memory 1130 is not limited in this embodiment of the present application.
  • the memory 1130, the processor 1120, and the communication interface 1110 are connected through a bus 1140 in FIG. 11.
  • the bus is represented by a thick line in FIG. 11, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • the communication module 1001 and the communication interface 1110 may output or receive baseband signals.
  • the output or reception of the communication module 1001 and the communication interface 1110 may be radio frequency signals.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can implement or The methods, steps and logic block diagrams disclosed in the embodiments of this application are executed.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory 1130 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory (volatile memory), Such as random-access memory (random-access memory, RAM).
  • Memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.
  • an embodiment of the present application further provides a chip, including a processor, for supporting the communication apparatus to implement the functions involved in the terminal device or the network device in the foregoing method embodiment. Function.
  • the chip is connected to a memory or the chip includes a memory for storing necessary program instructions and data of the communication device.
  • An embodiment of the present application provides a computer-readable storage medium storing a computer program, where the computer program includes instructions for executing the foregoing method embodiments.
  • the embodiments of the present application provide a computer program product containing instructions, which, when executed on a computer, cause the above method embodiments to be executed.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Landscapes

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

Abstract

本申请提供一种数据传输方法及通信装置，该方法包括以下步骤：当终端设备处于RRC空闲态或RRC非激活态时，通过第一数据无线承载DRB向网络设备发送上行数据，或者向网络设备发送第一数据无线承载DRB的上行数据，该终端设备接收来自网络设备的第一消息，第一消息用于指示终端设备进入RRC连接态，该终端设备通过第二DRB向网络设备发送第一DRB的上行数据。终端设备在进入连接态后，通过第二DRB传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于状态转换导致的数据早传的上行数据丢失，提高上行数据传输的可靠性。

Description

一种数据传输方法及通信装置 技术领域
本申请涉及通信技术领域，特别涉及一种数据传输方法及通信装置。
背景技术
终端设备有上行数据传输需求时，可以基于动态授权(grant based，GB)或动态调度的方式传输上行数据，具体过程可以包括以下步骤。终端设备向网络设备上报非空的缓存状态报告(buffer state report，BSR)，网络设备向终端设备发送下行控制信息(downlink control information，DCI)，DCI中携带上行授权(UL grant)。在一些场景中，例如类似于机器类型通信(machine type communication，MTC)、大量机器类型通信(massive Machine Type Communication，mMTC)或窄带物联网(narrow band internet of thing，NB-IoT)通信场景下，终端设备的待传输数据的数据量较小(可以称为小包数据)，且终端设备具有低功耗的需求。若终端设备基于GB或动态调度的方式传输上行数据，则系统开销过大，资源利用效率低下，终端的功耗过大，并且无法满足数据传输时延要求。
现有技术中，处于无线资源控制(radio resource control，RRC)非激活(INACTIVE)态的终端设备，可以在随机接入(random access，RA)过程中传输小包数据，或者基于免授权(grant-free，GF)的资源配置传输小包数据，而无须进行状态转换进入RRC连接态并基于GB或动态调度的方式传输小包数据。这样可以节省信令开销以及降低终端功耗。
处于RRC非激活态的终端设备不进行状态转换而进行的数据传输的过程还需要进一步优化。
发明内容
本申请提供一种数据传输方法及通信装置，以期提高数据传输的可靠性。
第一方面，提供一种数据传输方法，该方法可以由终端设备执行，也可以由终端设备的部件(例如处理器、芯片、或芯片系统等)执行。该方法可以通过以下步骤实现：处于RRC空闲(IDLE)态或RRC INACTIVE态时，通过第一数据无线承载DRB向网络设备发送上行数据，或者向网络设备发送第一数据无线承载DRB的上行数据，接收来自网络设备的第一消息，第一消息用于指示终端设备进入RRC连接态，通过第二DRB向网络设备发送第一DRB的上行数据。终端设备在进入连接态后，通过第二DRB传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于状态转换导致的数据早传的上行数据丢失，提高上行数据传输的可靠性。
在一个可能的设计中，在通过第二DRB向网络设备发送第一DRB的上行数据之前，保留第一DRB的上行数据。保留也可以称为不释放。通过保留第一DRB的上行数据，能够在状态转换进入连接态后，及时发送第一DRB的上行数据，既缩短了上行小包数据的传输时延，又保证了上行小包数据在状态转换过程中不会丢失。
在一个可能的设计中，保留第一DRB的上行数据，可以是指保留第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU，也可以是指保留第一DRB对应的PDCP协议数据单元PDU。
在一个可能的设计中，接收来自网络设备的第一消息后，还可以停止PDCP SDU对应的丢弃定时器，还可以停止PDCP PDU对应的丢弃定时器。避免所述PDCP SDU和/或PDCP PDU由于丢弃定时器超时，造成PDCP层的丢包。
若终端设备保留第一DRB对应的PDCP数据，则第一DRB对应的PDCP SDU或PDCP PDU，通过第一DRB对应的SDAP层处理，生成SDAP SDU，即应用层数据。通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，保留第一DRB的上行数据，还可以是保留第一DRB对应的SDAP层数据。例如，保留第一DRB对应的业务数据适配协议SDAP SDU，又例如保留第一DRB对应的SDAP PDU。
若终端设备保留第一DRB对应的SDAP数据，SDAP数据即应用层数据，通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，还可以接收来自网络设备的第二消息，第二消息用于指示第二DRB。当与网络设备建立一个或多个DRB时，可以根据第二消息确定一个或多个DRB中用于传输第一DRB的上行数据的DRB。
在一个可能的设计中，还可以根据规则来确定一个或多个DRB中用于传输第一DRB的上行数据的DRB。该规则可以是以下任意一种：第二DRB为终端设备建立的一个或多个DRB中标识最小的DRB；或者，第二DRB为终端设备建立的一个或多个DRB中标识最大的DRB；或者，第二DRB为终端设备建立的一个或多个DRB中与第一DRB的标识相同的DRB；或者，所述第二DRB为根据服务质量QoS流到DRB的映射规则确定的DRB。
第二方面，提供一种数据传输方法，该方法可以由终端设备执行，也可以由终端设备的部件(例如处理器、芯片、或芯片系统等)执行。该方法可以通过以下步骤实现：处于RRC非激活INACTIVE态时，向第一小区发送第一数据无线承载DRB的上行数据，执行小区重选，通过第一DRB向第二小区发送第一DRB的上行数据，其中，第二小区为小区重选的目标小区。通过终端设备小区重选后，通过第一DRB再次传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于小区重选导致的数据早传的上行数据丢失，提高上行数据传输的可靠性。
在一个可能的设计中，在执行小区重选之后，终端设备保留RRC_INACTIVE态，或者，终端设备仍处于RRC_INACTIVE态，或者终端设备不进行状态转换，状态转换是指终端设备从RRC_INACTIVE态进入空闲态。避免因进入空闲态造成之前传输的第一DRB上的上行数据的丢失。
在一个可能的设计中，在执行小区重选之后，挂起第一DRB；和/或，在执行小区重选之后，挂起第一DRB对应的PDCP实体。这样，可以保留UE上下文。
在一个可能的设计中，在执行小区重选之后，保留第一DRB的上行数据。可以保留第一DRB对应的PDCP SDU，也可以保留第一DRB对应的PDCP协议数据单元PDU。
在一个可能的设计中，在执行小区重选之后，还可以停止PDCP SDU对应的丢弃定时器，还可以停止PDCP PDU对应的丢弃定时器。避免所述PDCP SDU和/或PDCP PDU由于丢弃定时器超时，造成PDCP层的丢包。
若终端设备保留第一DRB对应的PDCP数据，则第一DRB对应的PDCP SDU或PDCP  PDU，通过第一DRB对应的SDAP层处理，生成SDAP SDU，即应用层数据。通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，保留第一DRB的上行数据，还可以是保留第一DRB对应的SDAP层数据。例如，保留第一DRB对应的业务数据适配协议SDAP SDU，又例如保留第一DRB对应的SDAP PDU。
若终端设备保留第一DRB对应的SDAP数据，SDAP数据即应用层数据，通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，发送第一DRB的上行数据，可以认为是重传第一DRB的PDCP数据，其中，重传第一DRB的PDCP数据可以通过以下方式实现：执行第一DRB的PDCP重建立过程；或者，由RRC层通知PDCP层重传第一DRB对应的PDCP数据。
PDCP重建立或者重传PDCP数据可以包括以下过程：可以重传第一DRB对应的PDCP SDU，也可以重传第一DRB对应的PDCP PDU。
在一个可能的设计中，确定未收到来自网络设备的针对第一DRB的上行数据的响应消息之后，执行以下一种或多种操作：保留第一DRB的数据、挂起第一DRB、或挂起第一DRB对应的PDCP实体。
第三方面，提供一种数据传输方法，该方法可以由终端设备执行，也可以由终端设备的部件(例如处理器、芯片、或芯片系统等)执行。该方法可以通过以下步骤实现：处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，向网络设备发送第一数据无线承载DRB的上行数据，从第一数据传输方式回退到第二数据传输方式，通过第二数据传输方式，向网络设备发送第一DRB的上行数据。通过第一DRB的上行数据的重传，当终端设备清空HARQ缓存时，终端设备能够及时进行第一DRB的上行数据的重传，以保证数据早传的上行数据不会丢失，提高数据早传在回退场景中的性能。
在一个可能的设计中，第一数据传输方式为基于随机接入RA方式进行数据早传，第二数据传输方式为基于基于配置的授权CG进行数据早传；或者，第一数据传输方式为基于CG进行数据早传，第二数据传输方式为基于RA进行数据早传；或者，第一数据传输方式包括基于RA方式或基于CG进行数据早传，第二数据传输方式为进入RRC连接态进行数据传输。
在一个可能的设计中，向网络设备发送第一DRB的上行数据，可以通过以下方式实现：对第一DRB的上行数据，进行RLC层数据重传；或者，对第一DRB的上行数据，进行PDCP层数据重传；对第一DRB的上行数据，进行MAC层数据重传。
第四方面，提供一种通信装置，该通信装置可以是终端设备，也可以是终端设备中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和终端设备匹配使用的装置。一种设计中，该通信装置可以包括执行第一方面中所描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该通信装置可以包括处理模块和通信模块。处理模块用于调用通信模块执行接收和/或发送的功能。进一步地，通信模块还可以包括接收模块和发送模块。示例性地：发送模块用于：处于RRC空闲(IDLE)态或RRC INACTIVE态时，通过第一数据无线承载DRB向 网络设备发送上行数据，或者向网络设备发送第一数据无线承载DRB的上行数据；接收模块用于：接收来自网络设备的第一消息，第一消息用于指示终端设备进入RRC连接态，发送模块还用于：通过第二DRB向网络设备发送第一DRB的上行数据。终端设备在进入连接态后，通过第二DRB传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于状态转换导致的数据早传的上行数据丢失，提高上行数据传输的可靠性。
在一个可能的设计中，处理模块用于：在通过第二DRB向网络设备发送第一DRB的上行数据之前，保留第一DRB的上行数据。保留也可以称为不释放。通过保留第一DRB的上行数据，能够在状态转换进入连接态后，及时发送第一DRB的上行数据，既缩短了上行小包数据的传输时延，又保证了上行小包数据在状态转换过程中不会丢失。
在一个可能的设计中，处理模块用于：保留第一DRB的上行数据，可以是指保留第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU，也可以是指保留第一DRB对应的PDCP协议数据单元PDU。
在一个可能的设计中，处理模块还用于：接收来自网络设备的第一消息后，还可以停止PDCP SDU对应的丢弃定时器，还可以停止PDCP PDU对应的丢弃定时器。避免所述PDCP SDU和/或PDCP PDU由于丢弃定时器超时，造成PDCP层的丢包。
在一个可能的设计中，处理模块还用于：若保留第一DRB对应的PDCP数据，则第一DRB对应的PDCP SDU或PDCP PDU，通过第一DRB对应的SDAP层处理，生成SDAP SDU，即应用层数据。通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，处理模块还用于：保留第一DRB的上行数据，还可以是保留第一DRB对应的SDAP层数据。例如，保留第一DRB对应的业务数据适配协议SDAP SDU，又例如保留第一DRB对应的SDAP PDU。
在一个可能的设计中，处理模块还用于：若保留第一DRB对应的SDAP数据，SDAP数据即应用层数据，通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，接收模块还用于：还可以接收来自网络设备的第二消息，第二消息用于指示第二DRB。当与网络设备建立一个或多个DRB时，可以根据第二消息确定一个或多个DRB中用于传输第一DRB的上行数据的DRB。
在一个可能的设计中，处理模块还用于：还可以根据规则来确定一个或多个DRB中用于传输第一DRB的上行数据的DRB。该规则可以是以下任意一种：第二DRB为终端设备建立的一个或多个DRB中标识最小的DRB；或者，第二DRB为终端设备建立的一个或多个DRB中标识最大的DRB；或者，第二DRB为终端设备建立的一个或多个DRB中与第一DRB的标识相同的DRB；或者，所述第二DRB为根据服务质量QoS流到DRB的映射规则确定的DRB。
第五方面，提供一种通信装置，该通信装置可以是终端设备，也可以是终端设备中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和终端设备匹配使用的装置。一种设计中，该通信装置可以包括执行第一方面中所描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该通信装置可以包括处理模块和通信模块。处理模块用于调用通信模块执行接收和/或发送的功能。进一步地，通信模块还可以包括接收模块和发送模块。示例性地：
通信模块用于：处于RRC非激活INACTIVE态时，向第一小区发送第一数据无线承载DRB的上行数据；处理模块用于：执行小区重选；通信模块还用于：通过第一DRB向第二小区发送第一DRB的上行数据，其中，第二小区为小区重选的目标小区。通过终端设备小区重选后，通过第一DRB再次传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于小区重选导致的数据早传的上行数据丢失，提高上行数据传输的可靠性。
在一个可能的设计中，处理模块还用于：在执行小区重选之后，保留RRC_INACTIVE态，或者，仍处于RRC_INACTIVE态，或者不进行状态转换，状态转换是指终端设备从RRC_INACTIVE态进入空闲态。避免因进入空闲态造成之前传输的第一DRB上的上行数据的丢失。
在一个可能的设计中，处理模块还用于：在执行小区重选之后，挂起第一DRB；和/或，在执行小区重选之后，挂起第一DRB对应的PDCP实体。这样，可以保留UE上下文。
在一个可能的设计中，处理模块还用于：在执行小区重选之后，保留第一DRB的上行数据。可以保留第一DRB对应的PDCP SDU，也可以保留第一DRB对应的PDCP协议数据单元PDU。
在一个可能的设计中，处理模块还用于：在执行小区重选之后，还可以停止PDCP SDU对应的丢弃定时器，还可以停止PDCP PDU对应的丢弃定时器。避免所述PDCP SDU和/或PDCP PDU由于丢弃定时器超时，造成PDCP层的丢包。
在一个可能的设计中，处理模块还用于：若保留第一DRB对应的PDCP数据，则第一DRB对应的PDCP SDU或PDCP PDU，通过第一DRB对应的SDAP层处理，生成SDAP SDU，即应用层数据。通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，处理模块还用于：保留第一DRB的上行数据，还可以是保留第一DRB对应的SDAP层数据。例如，保留第一DRB对应的业务数据适配协议SDAP SDU，又例如保留第一DRB对应的SDAP PDU。
在一个可能的设计中，处理模块还用于：若保留第一DRB对应的SDAP数据，SDAP数据即应用层数据，通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
在一个可能的设计中，发送第一DRB的上行数据，可以认为是重传第一DRB的PDCP数据，其中，重传第一DRB的PDCP数据可以通过以下方式实现：执行第一DRB的PDCP重建立过程；或者，由RRC层通知PDCP层重传第一DRB对应的PDCP数据。
在PDCP重建立或者重传PDCP数据时，通信模块用于：可以重传第一DRB对应的PDCP SDU，也可以重传第一DRB对应的PDCP PDU。
在一个可能的设计中，处理模块还用于：确定未收到来自网络设备的针对第一DRB的上行数据的响应消息之后，执行以下一种或多种操作：保留第一DRB的数据、挂起第一DRB、或挂起第一DRB对应的PDCP实体。
第六方面，提供一种通信装置，该通信装置可以是终端设备，也可以是终端设备中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和终端设备匹配使用的装置。一种设计中，该通信装置可以包括执行第一方面中所描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该通信装置可以包括处理模块和通信模块。处理模块用于调用通信模块执行接收 和/或发送的功能。进一步地，通信模块还可以包括接收模块和发送模块。示例性地：通信模块用于：处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，向网络设备发送第一数据无线承载DRB的上行数据；处理模块用于：从第一数据传输方式回退到第二数据传输方式；通信模块还用于：通过第二数据传输方式，向网络设备发送第一DRB的上行数据。通过第一DRB的上行数据的重传，当终端设备清空HARQ缓存时，终端设备能够及时进行第一DRB的上行数据的重传，以保证数据早传的上行数据不会丢失，提高数据早传在回退场景中的性能。
在一个可能的设计中，第一数据传输方式为基于随机接入RA方式进行数据早传，第二数据传输方式为基于基于配置的授权CG进行数据早传；或者，第一数据传输方式为基于CG进行数据早传，第二数据传输方式为基于RA进行数据早传；或者，第一数据传输方式包括基于RA方式或基于CG进行数据早传，第二数据传输方式为进入RRC连接态进行数据传输。
在一个可能的设计中，在向网络设备发送第一DRB的上行数据时，通信模块具体用于：对第一DRB的上行数据，进行RLC层数据重传；或者，对第一DRB的上行数据，进行PDCP层数据重传；对第一DRB的上行数据，进行MAC层数据重传。
第七方面，提供一种通信装置，所述通信装置包括通信接口和处理器，所述通信接口用于该通信装置与其它设备进行通信，例如数据或信号的收发。示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。处理器用于调用一组程序、指令或数据，执行上述第一方面至第三方面任一方面所描述的方法。所述通信装置还可以包括存储器，用于存储处理器调用的程序、指令或数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的、指令或数据时，可以实现上述第一方面至第三方面任一方面所描述的方法。
第八方面，本申请实施例中还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可读指令，当所述计算机可读指令在计算机上运行时，使得如第一方面至第三方面任一方面所描述的方法被执行。
第九方面，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述如第一方面至第三方面任一方面所描述的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十方面，本申请实施例提供了一种通信系统，所述通信系统包括终端设备和网络设备，终端设备用于执行如第一方面至第三方面任一方面所描述的方法。
第十二方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得如第一方面至第三方面任一方面所描述的方法被执行。
附图说明
图1为本申请实施例中通信系统架构示意图；
图2a为本申请实施例中用户面协议栈示意图；
图2b为本申请实施例中控制面协议栈示意图；
图3为本申请实施例中状态转换示意图；
图4为本申请实施例中四步RA中数据早传的过程示意图；
图5为本申请实施例中两步RA中数据早传的过程示意图；
图6为本申请实施例中基于CG的数据早传的过程示意图；
图7为本申请实施例中一种数据传输方法的流程示意图；
图8为本申请实施例中另一种数据传输方法的流程示意图；
图9为本申请实施例中另一种数据传输方法的流程示意图；
图10为本申请实施例中通信装置结构示意图之一；
图11为本申请实施例中通信装置结构示意图之二。
具体实施方式
本申请实施例提供一种数据传输方法及装置。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。本申请实施例的描述中，“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。本申请中所涉及的至少一个是指一个或多个；多个，是指两个或两个以上。另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
本申请实施例提供的数据传输方法可以应用于第四代(4th generation，4G)通信系统，例如长期演进(long term evolution，LTE)通信系统，也可以应用于第五代(5th generation，5G)通信系统，例如5G新空口(new radio，NR)通信系统，或应用于未来的各种通信系统，例如第六代(6th generation，6G)通信系统。本申请实施例提供的方法还可以应用于蓝牙系统、WiFi系统、LoRa系统或车联网系统中。本申请实施例提供的方法还可以应用于卫星通信系统其中，所述卫星通信系统可以与上述通信系统相融合。
本申请实施例提供的技术方案可以应用于各种通信场景，例如可以应用于以下通信场景中的一种或多种：增强移动宽带(enhanced mobile broadband，eMBB)、超可靠低时延通信(ultra-reliable low-latency communication，URLLC)、机器类型通信(machine type communication，MTC)、大规模机器类型通信(massive machine type communications，mMTC)、设备到设备(device-to-device，D2D)、车辆外联(vehicle to everything，V2X)、车辆到车辆(vehicle to vehicle，V2V)、和物联网(internet of things，IoT)等。
为了便于理解本申请实施例，以图1所示的通信系统架构为例对本申请使用的应用场景进行说明。参阅图1所示，通信系统100包括网络设备101和终端设备102。本申请实施例提供的装置可以应用到网络设备101，或者应用到终端设备102。可以理解的是，图1仅示出了本申请实施例可以应用的一种可能的通信系统架构，在其他可能的场景中，所述通信系统架构中也可以包括其他设备。
网络设备110为无线接入网(radio access network，RAN)中的节点，又可以称为基站，还可以称为RAN节点(或设备)。目前，一些接入网设备101的举例为：gNB/NR-NB、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)，卫星设备，或5G通信系统中的网 络设备，或者未来可能的通信系统中的网络设备。网络设备110还可以是其他具有网络设备功能的设备，例如，网络设备110还可以是设备到设备(device to device，D2D)通信、车联网通信、机器通信中担任网络设备功能的设备。网络设备110还可以是未来可能的通信系统中的网络设备。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括射频单元(radio unit，RU)。CU实现gNB的部分功能，DU实现gNB的部分功能，比如，CU实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能，DU实现无线链路控制(radio link control，RLC)、媒体接入控制(media access control，MAC)和物理(physical，PHY)层的功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令或PHCP层信令，也可以认为是由DU发送的，或者，由DU+RU发送的。可以理解的是，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的设备。此外，CU可以划分为接入网RAN中的网络设备，也可以将CU划分为核心网CN中的网络设备，在此不做限制。
终端设备102，又可以称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音或数据连通性的设备，也可以是物联网设备。例如，终端设备包括具有无线连接功能的手持式设备、车载设备等。目前，终端设备可以是：手机、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备(例如智能手表、智能手环、计步器等)，车载设备(例如，汽车、自行车、电动车、飞机、船舶、火车、高铁等)、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制中的无线终端、智能家居设备(例如，冰箱、电视、空调、电表等)、智能机器人、车间设备、无人驾驶中的无线终端、远程手术中的无线终端、智能电网(smart grid)中的无线终端、运输安全中的无线终端、智慧城市中的无线终端，或智慧家庭中的无线终端、飞行设备(例如，智能机器人、热气球、无人机、飞机)等。终端设备还可以是其他具有终端功能的设备，例如，终端设备还可以是D2D通信中担任终端功能的设备。本申请中将具有无线收发功能的终端设备及可设置于前述终端设备的芯片统称为终端设备。
下面结合图1所示的通信系统，对本申请实施例提供的数据传输方法做详细说明。
为了更好的理解本申请实施例提供的方案，以下先对本申请实施例涉及到的一些术语、概念或流程进行介绍。
首先介绍一下终端设备可能处于的状态。
如图2a所示，在终端设备与网络设备之间进行通信的用户面协议栈中，包括服务数据适配(service data adaptation protocol，SDAP)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(medium access control，MAC)层和物理(physical，PHY)层。
如图2b所示，在终端设备与网络设备之间进行通信的控制面协议栈中，包括非接入(non access stratum，NAS)层、无线资源控制(radio resource control，RRC)层、SDAP层、PDCP层、RLC层、MAC层和PHY层。
针对RRC层，存在几种终端设备的RRC状态，分别为RRC空闲(RRC_IDLE)态，RRC非激活(RRC_INACTIVE)态(又可称之为第三态)以及RRC连接(RRC_CONNECTED) 态。当终端设备已经建立了RRC连接，则终端设备处于RRC_CONNECTED态或RRC_INACTIVE态。如果终端设备未建立RRC连接，则终端设备处于RRC_IDLE态。其中，RRC_INACTIVE态是在5G NR通信系统中为终端设备引入的一种状态，该RRC_INACTIVE态主要针对的情况为“具有不频繁(infrequent)数据传输的终端设备通常由网络保持在RRC_INACTIVE状态”。
当终端设备处于不同的RRC状态时，均会执行不同的操作。这三种状态之间的转换的流程如图3所示。终端设备开始处于RRC_IDLE状态，当终端设备需要进行数据传输时，终端设备会执行随机接入过程与网络设备建立RRC连接，进入RRC_CONNECTED态。终端设备在进入RRC_CONNECTED态后开始进行数据传输，其中建立RRC连接是通过终端设备在发起随机接入的过程中向网络设备发送连接建立请求消息，例如RRCSetupRequest，并接收网络设备发送的连接建立消息，例如RRCSetup。
当终端设备后续无需进行数据传输时，网络设备可将终端设备释放使其转入RRC_IDLE态或RRC_INACTIVE态。例如，网络设备发送带有挂起(suspend)指示的释放(release)消息，例如RRCRelease with suspend indication，使终端设备进入RRC_INACTIVE态。或者网络设备发送释放消息，例如RRCRelease，使终端设备进入RRC_IDLE态。
另外，处于RRC_INACTIVE态的终端设备还可以通过恢复(resume)消息回到RRC_CONNECTED态，例如终端设备发送RRC恢复请求(RRCResumeRequest)并接收RRC恢复(RRCResume)，回到RRC_CONNECTED态。同样，网络设备还可将终端设备释放使其转入RRC_IDLE态。
当终端设备从RRC连接态进入RRC_INACTIVE态时，会执行PDCP挂起的操作。PDCP挂起的操作可以是指，终端设备不丢弃或保存PDCP服务数据单元(service data unit，SDU)。不丢弃或保存PDCP SDU也可以称为挂起的PDCP SDU。这样，一旦终端设备从RRC_INACTIVE态进入RRC连接态后，挂起的PDCP SDU可以继续传输，从而避免数据包在状态转换过程中的丢失。
为了简要说明，RRC_IDLE态也可以简述为空闲态或IDLE态；RRC_INACTIVE态也可以简述为非激活态或INACTIVE态；RRC_CONNECTED态也可以简述为连接态或激活态或CONNECTED态。RRC_IDLE态或RRC_INACTIVE态也可以称为RRC非连接态，RRC非连接态也可以简述为非连接态。
综上，对于终端设备的几种RRC状态(也可以简称为状态)已经介绍完毕。本申请实施例中，RRC空闲态或RRC非激活态的终端设备可以在不进行状态转换时进行数据传输，可以称为数据早传(early data transmission，EDT)或者小数据传输(small data transmission,SDT)或者非激活态数据传输(inactive data transmission，IDT)。这里数据早传EDT跟小数据传输SDT和非激活态数据传输的概念可以互相替换，以下以数据早传为例进行说明。
以下介绍一下数据早传的概念和流程。
数据早传可以认为是，处于RRC空闲态或RRC非激活态的终端设备，不需要进行状态转换进入RRC连接态，就可以传输数据。数据早传所传输的数据可以包括用户面数据，本申请实施例中用户面数据简称为数据。数据早传可以包括上行数据早传和下行数据早传。上行数据早传过程中传输的用户面数据可以称为上行数据。下行数据早传过程中传输的用户面数据可以称为下行数据。
数据早传过程中传输的数据可以称为小包数据(small data)或者小数据，数据早传的过程也可以称为小包传输。
数据早传可以通过以下方式1或方式2实现。
方式1：在随机接入(random access，RA)过程中实现数据早传。基于RA的小包传输是指终端设备在RA的过程中，向网络设备发送上行数据或接收下行数据。RA可以包括两步RA和四步RA。
如图4所示，示例了四步RA中数据早传的过程。
S401、终端设备向网络设备发送消息1(Msg1)，网络设备从终端设备接收消息1(Msg1)，该消息1为随机接入前导码(random access preamble)。
S402、网络设备向终端设备发送消息2(Msg2)，终端设备从网络设备接收消息2。
其中，该消息2为随机接入响应(random access response)。
S403、终端设备向网络设备发送消息3(Msg3)，网络设备从终端设备接收消息3(Msg3)。
可以在Msg3中携带上行数据。
S404、网络设备向终端设备发送消息4(Msg4)，终端设备从网络设备接收消息4。
可选的，在Msg4中携带下行数据。
如图5所示，示例了两步RA中数据早传的过程。
S501、终端设备向网络设备发送消息A(MsgA)，网络设备从终端设备接收消息A。
可以在MsgA中携带上行数据。
MsgA的传输信道可以包括物理随机接入信道(physical random access channel，PRACH)和物理上行共享信道(physical uplink shared channel，PUSCH)。PRACH用于发送随机接入前导Preamble，Preamble用于网络设备对终端设备的时间提前量(Timing Advance)进行估计，使终端设备实现与网络设备的上行同步。
可以通过MsgA的PUSCH发送早传的上行数据。
S502、网络设备向终端返回消息B(MsgB)，终端设备从网络设备接收消息B。
可以在MsgB中携带下行数据。可以在MsgB的物理下行共享信道PDSCH上传输早传的下行数据。
方式2：基于免授权(grant-free，GF)的数据早传。
网络设备通过半静态的方式为终端设备预配置用于上行数据传输的PUSCH资源以及传输参数，当终端设备有上行数据需要发送时，直接使用预配置的PUSCH资源和参数向网络设备发送数据，而不必接收网络设备的动态上行授权(dynamic UL grant)，也不必发送Preamble进行随机接入。
LTE中基于预配置上行资源(pre-configured uplink resource，PUR)传输和NR中基于配置的授权(configured grant，CG)传输都属于上行免授权传输范畴。其中，CG包括第一类(Type 1)CG和第二类(Type 2)CG。基于PUR的传输和基于Type 1 CG的传输类似，网络设备通过RRC信令为终端设备配置资源和传输参数，例如配置以下一种或多种参数：时域资源的周期、开环功控相关参数、波形、冗余版本序列、重复次数、跳频模式、资源分配类型、混合自动重传请求(hybrid automatic retransmission request，HARQ)进程数、解调参考信号(demodulation reference Signal，DMRS)相关参数、调制编码方式(modulation and coding scheme，MCS)表格、资源块(resource block group，RBG)组大小、以及时域资源、频域资源、MCS等。
基于Type 2 CG的传输中，网络设备采用两步的资源配置方式。首先，网络设备通过RRC信令下发配置的授权配置信息，该配置信息用于配置以下一种或多种传输资源和传输参数：时域资源的周期、开环功控相关参数、波形、冗余版本序列、重复次数、跳频模式、资源分配类型、HARQ进程数、解调用参考信号相关参数、MCS表格、RBG组大小。然后由使用配置的调度无线网络临时标识符(configured scheduling radio network temporary identifier，CS-RNTI)加扰的下行控制信息(downlink control information，DCI)激活Type 2CG的PUSCH传输，并同时配置包括时域资源、频域资源、DMRS、MCS等在内的其他传输资源和传输参数。
如图6所示，当终端设备处于RRC_INACTIVE时，基于CG的数据早传的过程如下所述。
S601、终端设备在CG资源上向网络设备发送RRC恢复请求(RRCResumeResuest)消息，网络设备从终端设备接收RRC恢复请求消息。
RRC恢复请求消息可以携带上行数据。
另一种可能的方式为终端设备在CG资源直接发送上行数据，不需要携带RRC恢复请求消息，网络设备从终端设备接收上行数据。
S602、网络设备向终端设备返回RRC释放(Release)消息，终端设备接收来自网络设备的RRC释放(Release)消息。
RRC释放(Release)消息用于指示终端设备继续停留在RRC_INACTIVE态。
可选地，网络设备还可以发送下行数据，所述下行数据可以与RRC释放消息复用在一起，也可以在RRC释放消息前单独发送给终端。
另一种可能的方式为网络设备不发送RRC释放消息给终端，这种方式可以对应于S601当终端设备在CG资源直接发送上行数据的情况。
基于免授权的小包传输，终端设备不需要发送Preamble，因此更适用于终端设备与网络设备处于同步状态的场景，要求上行定时保持不变，即终端设备与网络设备的上行同步。相比基于RA的方案，可以进一步节省信令开销和终端设备功耗。
以上介绍了数据早传的概念和流程。
终端设备在处于非连接态时，向网络设备发送上行小包数据，网络设备在一些情况下可能无法正确解析早传的上行小包数据，则网络设备可能会指示终端设备进入连接态。例如，网络设备在接收到来自终端设备的上行小包数据之后，需要获取UE上下文，才能够正确解析上行小包数据，若网络设备无法获得UE上下文，则网络设备无法正确解析早传的上行小包数据。这样，网络设备可能会向终端设备发送RRC连接建立消息，使的终端设备进入RRC连接态。
由于处于非连接态的终端设备在进行数据早传时，会建立无线承载(radio bearer，RB)，RB可以是数据无线承载(data radio bearer，DRB)，也可以是信令无线承载(signaling radio bearer，SRB)。其中，假设终端设备处于RRC_INACTIVE态，在数据早传时，可能会恢复RB，还可以恢复对应RB的已挂起的PDCP实体。当终端设备向网络设备发送小包数据之后，若网络设备指示终端设备进入连接态，那么终端设备将会释放所有已经建立的RB，并释放掉对应RB的PDCP实体，丢弃对应RB的已经保存的PDCP SDU和/或PDCP协议数据单元(protocol data unit，PDU)，从而导致已经发起传输的上行小包数据丢失。
基于此，本申请实施例提供一种数据传输方法，以期提高上行数据传输的可靠性。如 图7所示，本申请实施例提供的一种数据传输方法的流程如下所述。
S701、终端设备当处于RRC空闲态或RRC非激活态时，向网络设备发送第一DRB的上行数据。对应的，网络设备接收来自终端设备的第一DRB的上行数据。
需要说明的是，第一DRB可以是一个或多个DRB，当第一DRB为多个DRB时，可以是多个DRB的数据复用到一个MAC PDU中。
S702、网络设备向终端设备发送第一消息，第一消息用于指示终端设备进入RRC连接态。对应的，终端设备接收来自网络设备的第一消息。
S703、终端设备通过第二DRB向网络设备发送第一DRB的上行数据。
终端设备在进入连接态后，通过第二DRB传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于状态转换导致的数据早传的上行数据丢失，提高上行数据传输的可靠性，优化了数据早传过程。
以下基于图7实施例，提供一些可选的实现方式。
处于RRC空闲态或RRC非激活态的终端设备，当产生待传输的上行数据时，需要通过数据早传过程传输该上行数据。终端设备可以建立与网络设备之间的第一DRB，通过第一DRB传输该上行数据，该上行数据可以称为第一DRB的上行数据。对于RRC非激活态的终端设备来说，建立第一DRB的过程也可以认为是恢复第一DRB，即恢复第一DRB的相关配置，PDCP实体。从而待传输的上行数据可以通过第一DRB关联的SDAP、PDCP、RLC等实体进行处理，产生MAC SDU。
第一DRB的上行数据可以通过消息3、消息A或CG资源传输。例如，若终端设备基于RA方式进行数据早传，则可以在消息3或消息A中携带该第一DRB的上行数据。若终端设备基于CG方式进行数据早传，则可以通过CG资源发送该第一DRB的上行数据。在基于CG方式进行数据早传时，一种可能的方式为第一DRB的上行数据可以携带于RRC消息中，RRC消息可以是RRC恢复请求(RRC resume request)消息或者RRC恢复请求1(RRC resume request 1)消息。RRC恢复请求消息和RRC恢复请求1用于承载不同大小的RRC消息。RRC消息还可以携带终端设备的标识，例如终端设备RRC非激活态的标识(inactive radio network temporary identifier,I-RNTI)。终端设备的标识用于网络设备获取UE上下文。RRC消息还可以携带完整性保护校验的信息，用于网络设备校验RRC消息内容是否完整。RRC消息还可以携带原因值，用于指示网络设备本次RRC连接恢复的目的，例如RRC连接恢复的目的为上行小包传输。可选的，RRC消息可以与上行数据复用在同一个MAC PDU中，通过一个数据包传输RRC消息以及上行数据，当通过消息3或消息A传输上行数据时类似。另一种可能的方式为不携带RRC消息，终端设备通过CG资源发送该第一DRB的上行数据，可选的，还可以携带终端设备的标识，例如小区无线网络临时标识(Cell-Radio Network Temporary Identifier,C-RNTI)，或者I-RNTI的全部或者部分比特，所述终端设备的标识可以作为MAC控制元素(control element,CE)与上行数据复用在同一个MAC PDU中，通过一个数据包传输终端设备的标识以及上行数据。
一种可能的方式为：例如，若所述CG资源为共享资源，即多于一个终端设备均可以使用所述CG资源进行数据早传时，这种情况下，终端设备在CG资源发送该第一DRB的上行数据时可以携带终端设备的标识，从而便于基站设备识别出通过数据早传传输的上行数据归属于哪个终端设备；相反的，若所述CG资源为专属资源，即所述CG资源不与其他终端设备共享，这种情况下，终端设备在CG资源发送该第一DRB的上行数据时可以不 携带终端设备的标识。进一步地，终端设备在CG资源发送该第一DRB的上行数据时是否需要携带终端设备的标识可以由网络设备指示，比如通过RRC消息告知终端设备是否需要携带终端设备的标识或者所述CG资源是否为共享或者专属资源，从而当终端设备进行数据早传时可以根据所述指示判断是否需要在CG资源上携带终端设备的标识。
在S701之后，若网络设备能够正确接收该第一DRB的上行数据，则会执行以下操作。
一种情况下，若通过消息A或者消息3携带该第一DRB的上行数据，则网络设备会向终端设备返回消息B或者消息4。消息B或者消息4可以携带冲突解决(contention resolution)信息，冲突解决信息可以是消息3的全部或者部分比特。冲突解决信息用于指示上行数据传输成功。可选地，消息B还可以携带上行定时提前量(timing advance command,TAC)信息，终端设备收到TAC后，可以使用TAC对应的TA值进行上行定时的同步。上行定时的同步进一步地还可以用于后续基于CG方式的数据早传，可选地，消息B或者消息4还可以携带上行授权资源，进一步地，终端设备可以使用所述上行授权资源进行后续的上行数据的传输。
另一种情况下，若通过CG资源携带该第一DRB的上行数据，一种可能的方式为：网络设备可能会向终端设备返回消息B或者消息4或者新的MAC层响应消息。其中消息B或者消息4或者新的MAC层消息可以携带冲突解决信息，冲突解决信息可以是CG资源传输的终端设备标识的全部或者部分比特。冲突解决信息用于指示上行数据传输成功；另一种可能的方式为：网络设备会给终端设备返回RRC释放消息，终端设备收到RRC释放消息后，认为上行数据传输成功。
另一种情况下，若通过CG资源携带该第一DRB的上行数据，网络设备还可能向终端设备发送物理下行控制信道(physical downlink control channel，PDCCH)传输的响应消息。当网络设备成功收到上行数据时，可以向终端设备发送成功应答(acknowledgement,ACK)，终端设备收到ACK后可以确定上行数据发送成功。当然，这里存在一种可能，网络设备未成功收到上行数据，这是网络设备可以向终端设备发送错误应答(negative acknowledgement,NACK)，终端设备收到NACK后可以确定上行数据发送失败，进一步地，终端设备在上行数据发送失败时可以发起重传。
另一种情况下，若通过CG资源携带该第一DRB的上行数据，终端发送所述第一DRB的上行数据后还可以启动一个定时器，在定时器运行期间，监听PDCCH的传输，若在定时器运行期间未监听到PDCCH传输的所述第一DRB的上行数据响应消息，所述响应消息可以是上述的消息B或者消息4或者新的MAC层响应消息或者RRC释放消息或者PDCCH传输的响应消息，终端设备可以确定上行数据发送成功，从而无须所述响应消息；或者终端设备认为上行数据发送失败，从而在消息A或者CG资源进行所述上行数据的重传。
在S701之后，若网络设备不能正确接收该第一DRB的上行数据，则会执行S702。
网络设备不能正确接收该第一DRB的上行数据，可能基于以下可能的场景。该网络设备为终端设备的服务网络设备，服务网络设备可能没有保存UE上下文。这是当服务网络设备接收到上行数据后，需要发起UE上下文获取过程。具体地，服务网络设备向锚点网络设备发送UE上下文获取请求，UE上下文获取请求用于请求UE上下文。其中，锚点网络设备为保存UE上下文的网络设备。在服务网络设备向锚点网络设备发送UE上下文获取请求之前，服务网络设备可能从终端设备接收终端设备的标识、锚点网络设备的标识和/或UE上下文的标识。服务网络设备发送的UE上下文获取请求中可以携带终端设备的 标识和/或UE上下文的标识。锚点网络设备接收到来自服务网络设备的UE上下文获取请求后，会根据终端设备的标识和/或UE上下文的标识获取UE上下文。若锚点网络设备无法获取UE上下文，或者锚点网络设备无法成功校验终端设备的身份，或者锚点网络设备决定不向服务网络设备提供UE上下文，则锚点网络设备向服务网络设备返回UE上下文获取失败消息。
在网络设备不能正确接收该第一DRB的上行数据时，网络设备确定终端设备需要进入RRC连接态，则执行S702。S702中网络设备向终端设备发送的第一消息用于指示终端设备进入RRC连接态，第一消息可以是RRC连接建立消息，也可以是RRC释放(RRC release)消息。
第一消息用于指示终端设备建立新的RRC连接。
在S702之后，S703之前，还可以包括S704。
S704、终端设备保留第一DRB的上行数据。保留也可以称为不释放。以下以保留为例说明。
保留第一DRB的上行数据，可以通过以下方式A或方式B来实现。
方式A：保留第一DRB对应的PDCP层数据。
例如，可以保留第一DRB对应的PDCP SDU。又例如，可以保留第一DRB对应的PDCP PDU，又例如，可以保留第一DRB对应的PDCP SDU以及对应的PDCP PDU。
为了更好的理解方式A，以下对PDCP层以及PDCP层的操作进行说明。PDCP实体可以负责将因特网协议(internet protocol，IP)和/或以太协议(ethernet)头压缩和解压、传输用户面数据并维护为无线承载的序列号(sequence number,SN)。PDCP实体可以处理控制面的RRC消息以及用户面的IP包。在用户面上，PDCP层得到来自上层的IP数据分组后，可以对IP数据分组进行头压缩和加密，然后递交到RLC子层。PDCP层还可以根据PDCP数据包的SN，向上层提供按序提交和重复分组检测功能。终端设备在向网络设备发送第一DRB的上行数据时，PDCP层处理过程可以包括以下步骤。PDCP层接收到PDCP SDU之后，设置一个该PDCP SDU对应的丢弃定时器(discardTimer)；并且设置该SDU对应的PDCP SN，从而赋给该SDU对应的PDCP头(Header)；对上行数据进行头压缩；；将PDCP头(Header)添加到PDCP SDU生成PDCP PDU，并可以设置该PDCP PDU对应的丢弃定时器；发送PDCP PDU到RLC层。
当S701中终端设备向网络设备发送第一DRB的上行数据时，第一DRB对应的PDCP层启动丢弃定时器。当S702终端设备接收来自网络设备的第一消息后，还可以停止PDCP SDU对应的丢弃定时器，还可以停止PDCP PDU对应的丢弃定时器。避免所述PDCP SDU和/或PDCP PDU由于丢弃定时器超时，造成PDCP层的丢包。
保留第一DRB对应的PDCP层数据，可以是PDCP层决定的操作，也可以是由RRC层通知PDCP层的。例如，终端设备接收来自网络设备的第一消息后，通过RRC层通知PDCP层保留第一DRB对应的PDCP层数据。
方式B：保留第一DRB对应的SDAP层数据。
例如，可以保留第一DRB对应的SDAP SDU。又例如，可以保留第一DRB对应的SDAP PDU，又例如，可以保留第一DRB对应的PDCP SDU以及对应的PDCP PDU。
在保留第一DRB对应的SDAP层数据之后，在S703通过第二DRB发送第一DRB的上行数据时，可以将第一DRB对应的SDAP层数据进行处理。例如，假设保留第一DRB 对应的SDAP SDU，可以对SDAP SDU处理以生成SDAP PDU，发送SDAP PDU到PDCP层继续处理。假设保留第一DRB对应的SDAP PDU，可以发送保留的SDAP PDU到PDCP层继续处理。
保留第一DRB对应的SDAP层数据，可以是SDAP层决定的操作，也可以是由RRC层通知SDAP层的，还可以是由RRC通知PDCP层，进而PDCP层通知SDAP层。例如，终端设备接收来自网络设备的第一消息后，通过RRC层通知SDAP层保留第一DRB对应的PDCP层数据。
一种可能的方式为：在S701终端设备向网络设备发送第一DRB的上行数据之后，网络设备可以向终端设备返回响应消息，用于指示第一DRB的上行数据是否接收成功，该响应消息也可以用于响应S701中随同第一DRB的上行数据一起发送的其它信息。可选的，当终端设备接收来自网络设备的该响应消息之后，若响应消息指示第一DRB的上行数据没有接收成功，则终端设备执行S704，保留第一DRB的上行数据。
另一种可能的方式为：在S701终端设备向网络设备发送第一DRB的上行数据之后，终端设备维护一个定时器，用于判断第一DRB的上行数据是否接收成功。可选的，当定时器运行期间没有收到响应消息，则终端设备执行S704，保留第一DRB的上行数据。
S703中终端设备通过第二DRB向网络设备发送第一DRB的上行数据，第一DRB的上行数据简称为上行数据。终端设备可以将上行数据的PDCP SDU通过第二DRB对应的PDCP实体进行处理，生成PDCP PDU。其中，通过第二DRB对应的PDCP实体进行处理的过程可以包括分配序列号、加密或完整性保护中的一项或多项。
若终端设备保留第一DRB对应的PDCP数据，则第一DRB对应的PDCP SDU或PDCP PDU，通过第一DRB对应的SDAP层处理，生成SDAP SDU，即应用层数据。通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
若终端设备保留第一DRB对应的SDAP数据，SDAP数据即应用层数据，通过第二DRB关联的QoS流到DRB的映射关系，确定该应用层数据映射到第二DRB，经过第二DRB对应的PDCP处理，生成第二DRB的PDCP PDU。
S702终端设备接收来自网络设备的第一消息之后，终端设备进入RRC连接态。在终端设备进入RRC连接态之后或在终端设备进入RRC连接态的过程中，终端设备可以建立与网络设备之间的第二DRB。可选的，在S702之后，S703之前，还可以包括S705。S705和S704的顺序不作限定。
S705、网络设备向终端设备发送第二消息，终端设备接收来自网络设备的第二消息。第二消息用于建立第二DRB。
第二消息可以是RRC消息，例如RRC消息可以是RRC重配置(RRC reconfiguration)消息。
该第二消息还可以携带以下任意一种或多种信息：第二DRB的标识；PDCP配置，用于配置第二DRB关联的PDCP实体的参数，包括PDCP的序列号长度等参数；SDAP配置，用于配置第二DRB关联的SDAP实体的参数，包括服务质量(quality of service，QoS)流到第二DRB的映射关系，用于指示映射到第二DRB的QoS流标识(QoS flow identity,QFI)。
在实际应用中，网络设备可能与终端设备建立一个或多个DRB。那么终端设备如何在一个或多个DRB中确定用于发送第一DRB的上行数据的第二DRB，本申请实施例可以给 出一些可选的实现方式。终端设备按照规则确定第二DRB。其中，该规则例如可以是：一个或多个DRB中标识最小的DRB；一个或多个DRB中标识最大的DRB；一个或多个DRB中与第一DRB的标识相同的DRB；或随机选择的DRB，或者根据QoS流到DRB的映射关系确定需要映射的DRB。该规则可以是协议预定义的，也可以是网络设备通知给终端设备的，例如可以通过第二消息来通知该规则。该规则也可以由终端设备来实现。
可选的，也可以由第二消息来指示用于发送第一DRB的上行数据的第二DRB，例如第二消息包括第二DRB的标识，终端设备可以根据第二消息中的第二DRB的标识，确定用于发送第一DRB的上行数据的第二DRB。
可选的，第一DRB与第二DRB的配置可以不同，例如第一DRB与第二DRB的PDCP的配置不同，PDCP的配置包括秘钥和/或加密算法等。
综上所述，图7实施例和一些可能的实现方式能够提高上行数据传输的可靠性。
处于RRC非激活态的终端设备，可能驻留在一个小区中。由于终端设备具有移动性，可能终端设备会发生小区重选。例如，终端设备在发生移动后，可能需要更换到另一个更高优先级或更好信号的小区驻留，从而发生小区重选。假如处于RRC非激活态的终端设备在数据早传过程中向源小区发送上行小包数据后，发生小区重选，进入目标小区，那么该终端设备将不会收到源小区对上行数据的响应，且终端设备会进入RRC空闲态。由于处于RRC非激活态的终端设备在数据早传过程中已经恢复了RB，还可能恢复对应RB已挂起的PDCP实体。当终端设备进入目标小区转换为RRC空闲态，那么终端设备将会释放已经建立的RB，并释放掉对应RB的PDCP实体，丢弃对应RB的已经保存的PDCP SDU和/或PDCP PDU，从而导致已经发起传输的上行小包数据丢失。
基于此，本申请实施例提供另一种数据传输方法，以期提高上行数据传输的可靠性。如图8所示，本申请实施例提供的另一种数据传输方法的流程如下所述。
S801、终端设备当处于RRC非激活态时，向第一小区发送第一DRB的上行数据，第一小区接收来自终端设备的第一DRB的上行数据。
S802、执行小区重选。
小区重选的过程可以是终端设备从驻留的第一小区，转换成驻留在第二小区。第一小区可以认为是源小区，第二小区可以认为是目标小区。第一小区和第二小区可能位于同一个网络设备或不同的网络设备，第一小区和第二小区可以是不同的小区，还可能是同一个小区。
S803、通过第一DRB向第二小区发送第一DRB的上行数据。
其中，第二小区为S802小区重选的目标小区，或者第二小区为S802小区重选之后终端设备驻留的小区。
图8实施例，通过终端设备小区重选后，通过第一DRB再次传输在数据早传过程中发送的第一DRB的上行数据，可以避免由于小区重选导致的数据早传的上行数据丢失，提高上行数据传输的可靠性，优化了数据早传过程。
以下基于8实施例，提供一些可选的实现方式。
在S802执行小区重选之后，或者在S802执行小区重选的过程中，终端设备可以执行以下可选操作1。终端设备保留RRC_INACTIVE态，或者，终端设备仍处于RRC_INACTIVE态，或者终端设备不进行状态转换，状态转换是指终端设备从RRC_INACTIVE态进入空闲态。
在S802执行小区重选之后，或者在S802执行小区重选的过程中，终端设备也可以执行以下可选操作2的一种或多种：挂起第一DRB；挂起第一DRB对应的PDCP实体。在S801中处于RRC_INACTIVE态的终端设备向第一小区发送第一DRB的上行数据，终端设备已经恢复第一DRB，还可能已经恢复第一DRB对应的PDCP实体。当发送完第一DRB的上行数据之后，终端设备进行小区重选，这种情况下，终端设备不会进入RRC空闲态，而是再次挂起第一DRB和/或挂起第一DRB对应的PDCP实体，这样，可以保留UE上下文。在S803中可以再次恢复第一DRB，还可以再次恢复第一DRB对应的PDCP实体，从而通过第一DRB向第二小区发送第一DRB的上行数据。这样能够保证数据早传过程中第一DRB的上行数据不会丢失。
在S802执行小区重选之后，或者在S802执行小区重选的过程中，终端设备也可以执行以下可选操作3：保留第一DRB的上行数据。该可选操作3可以参考上文中S704和S704的可选实现方式的具体描述，在此不再赘述。
终端设备执行可选操作1、可选操作2或可选操作3，可以基于以下条件下执行。终端设备未接收到来自网络设备的响应消息，该响应消息是针对S801传输的第一DRB的上行数据的响应消息。可以是ACK消息或NACK消息，或者其他协议层的响应消息。
S801中终端设备可以通过第一DRB向第一小区发送上行数据，在S803中，通过第一DRB向第二小区发送第一DRB的上行数据，两次发送上行数据都是通过第一DRB，那么可选的，S803可以认为是重传第一DRB的PDCP数据。其中，重传第一DRB的PDCP数据可以通过以下方式实现：执行第一DRB的PDCP重建立过程；或者，由RRC层通知PDCP层重传第一DRB对应的PDCP数据。
具体地，PDCP重建立或者重传PDCP数据可以包括以下过程：可以重传第一DRB对应的PDCP SDU，也可以重传第一DRB对应的PDCP PDU。例如，终端设备可以从第一个未收到RLC成功应答的PDCP PDU对应的SDU开始，执行PDCP SDU的重传。即对第一DRB的上行数据对应的PDCP SDU，进行处理后重传，处理可以包括重新分配PDCP的序列号、加密等操作。
综上所述，图8实施例和一些可能的实现方式能够提高上行数据传输的可靠性。
终端设备在数据早传时，如果发送数据早传失败，可能会进行回退(fallback)。回退操作还可以称之为数据传输方式切换(switch)，例如从基于CG的方式切换到基于RA的方式，数据早传切换到连接态的数据传输，回退以及数据传输方式切换可以互相替换，以下以回退为例进行说明。回退可以是指终端设备从一种数据传输方式转换为另一种数据传输方式进行数据早传，也可以是指终端设备进行状态转换以进入连接态进行数据早传。例如，处于非连接态的终端设备，基于RA的方式进行数据早传，回退到基于CG方式进行数据早传。又例如，处于非连接态的终端设备，基于CG的方式进行数据早传，回退到基于RA方式进行数据早传。又例如，处于非连接态的终端设备，由非连接态转换为连接态后进行数据传输。回退一般发生在基于一种数据传输方式进行多次数据传输失败后。在回退的场景中，终端设备可能会清理缓存的上行数据，例如，之前传输的上行数据存在于HARQ缓存中，若终端设备执行HARQ缓存清空，或者终端设备有新数据达到，覆盖已有HARQ缓存中的数据，则会造成上行数据的丢失。
基于此，本申请实施例提供另一种数据传输方法，以期提高上行数据传输的可靠性。如图9所示，本申请实施例提供的另一种数据传输方法的流程如下所述。
S901、终端设备当处于RRC空闲态或RRC非激活态时，向网络设备发送第一DRB的上行数据，网络设备接收来自终端设备的第一DRB的上行数据。
本步骤中，终端设备可以采用第一数据传输方式进行上行数据的传输。第一数据传输方式可以是基于RA的方式进行数据早传，也可以是基于CG的方式进行数据早传，或者是在非连接态下进行数据早传。
S902、终端设备从第一数据传输方式回退到第二数据传输方式。
当第一数据传输方式是基于RA的方式进行数据早传时，第二数据传输方式可能是基于CG的方式进行数据早传或者进入连接态后进行数据传输。当第一数据传输方式是基于CG的方式进行数据早传时，第二数据传输方式可能是基于RA的方式进行数据早传或者进入连接态后进行数据传输。
可选的，终端设备可以在以下任一种或多种条件满足的情况下进行回退。
条件1：发送第一DRB的上行数据失败至少一次，可选地，网络设备还可以配置一个阈值，当发送第一DRB的上行数据失败次数等于或者超过阈值时，进行回退。
条件2：基于第一数据传输方式发送第一DRB的上行数据，第一数据传输方式的条件不再满足。例如，第一DRB的上行数据的数据量大于第一数据传输方式所要求的阈值。又例如，若第一数据传输方式为基于CG的方式，当终端设备上行TA失步时，那么基于CG的方式进行数据早传的条件就不再满足。
条件3：网络设备指示终端设备进行回退，例如网络设备向终端设备下发RRC连接恢复消息，使得终端设备从非连接态转换到连接态。
S903、终端设备通过第二数据传输方式，向网络设备发送第一DRB的上行数据，网络设备接收来自终端设备的第一DRB的上行数据。
当第二数据传输方式为基于RA方式或基于CG方式进行数据早传时，终端设备保持状态不变，或者终端设备不转换到连接态，通过第二数据传输方式，向网络设备发送第一DRB的上行数据。
当第二数据传输方式为进入连接态进行数据传输时，终端设备进入连接态后，在连接态向网络设备发送第一DRB的上行数据。例如，可以参考图7实施例的方式，建立第二DRB，在第二DRB上发送第一DRB的上行数据。
在S902终端设备从第一数据传输方式回退到第二数据传输方式之后，终端设备通过第二数据传输方式向网络设备发送第一DRB的上行数据，即终端设备触发第一DRB的上行数据的重传。
其中，第一DRB的上行数据的重传可以从不同协议层触发重传。
例如，对第一DRB的上行数据进行RLC层数据重传。针对第一DRB的上行数据对应的RLC实体，触发RLC实体对上行数据的对应RLC序列号的RLC SDU或者RLC PDU进行重传，进一步地，RLC SDU可以进行RLC重新组包，从而在S903中发送重新组包的RLC数据包。终端设备可以通过RRC层或者MAC层向RLC实体指示，对于上行数据对应的RLC SDU或者RLC PDU的否定应答，从而触发RLC实体对RLC SDU或者RLC PDU进行重传。
又例如，对第一DRB的上行数据进行PDCP层数据重传。针对第一DRB的上行数据对应的PDCP实体，触发PDCP实体对上行数据的对应PDCP序列号的PDCP SDU或者PDCP PDU进行重传，进一步地，PDCP SDU可以进行PDCP重新组包，从而在S903发 送重新组包的PDCP数据包。
又例如，对第一DRB的上行数据进行MAC层数据重传。针对第一DRB的上行数据对应的MAC层缓存，例如消息A或者消息3或者CG资源对应的MAC层缓存，所述MAC层缓存保存有所述第一DRB的上行数据对应的MAC子PDU或者完整的MAC PDU，通知组包以及复用实体，S903中第一DRB的上行数据对应的MAC PDU，包含MAC层缓存中的上行数据对应的MAC子PDU，或者包含MAC层缓存中的完整的MAC PDU。
通过第一DRB的上行数据的重传，当终端设备清空HARQ缓存时，终端设备能够及时进行第一DRB的上行数据的重传，以保证数据早传的上行数据不会丢失，提高数据早传在回退场景中的性能。
需要说明的是，本申请中的各个应用场景中的举例仅仅表现了一些可能的实现方式，是为了对本申请的方法更好的理解和说明。本领域技术人员可以根据申请提供的侧行链路通信方法，得到一些演变形式的举例。
为了实现上述本申请实施例提供的方法中的各功能，终端设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
如图10所示，基于同一技术构思，本申请实施例还提供了一种通信装置1000，该通信装置1000可以是终端设备，也可以是终端设备中的装置，或者是能够和终端设备匹配使用的装置。一种设计中，该通信装置1000可以包括执行上述方法实施例中终端设备执行的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该通信装置1000可以包括通信模块1001和处理模块1002。进一步地，通信模块1001又可以包括接收模块1001-1和发送模块1001-2。处理模块1002用于调用通信模块1001进行接收和/或发送信号。
在一个实施例中：
发送模块1001-2用于：处于RRC空闲(IDLE)态或RRC INACTIVE态时，通过第一数据无线承载DRB向网络设备发送上行数据，或者向网络设备发送第一数据无线承载DRB的上行数据。
接收模块1001-1用于：接收来自网络设备的第一消息，第一消息用于指示终端设备进入RRC连接态。
发送模块1001-2还用于：通过第二DRB向网络设备发送第一DRB的上行数据。
接收模块1001-1、发送模块1001-2以及处理模块1002还用于执行上述图7方法实施例中终端设备执行其它操作，在此不再一一赘述。
在另一个实施例中：
通信模块1001用于：处于RRC非激活INACTIVE态时，向第一小区发送第一数据无线承载DRB的上行数据。
处理模块1002用于：执行小区重选。
通信模块1001还用于：通过第一DRB向第二小区发送第一DRB的上行数据，其中，第二小区为小区重选的目标小区。
通信模块1001以及处理模块1002还用于执行上述图8方法实施例中终端设备执行其它操作，在此不再一一赘述。
在另一个实施例中：
通信模块1001用于：处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，向网络设备发送第一数据无线承载DRB的上行数据。
处理模块1002用于：从第一数据传输方式回退到第二数据传输方式。
通信模块1001还用于：通过第二数据传输方式，向网络设备发送第一DRB的上行数据。
通信模块1001以及处理模块1002还用于执行上述图9方法实施例中终端设备执行其它操作，在此不再一一赘述。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
如图11所示为本申请实施例提供的通信装置1100，用于实现上述方法中终端设备的功能。该装置可以是终端设备，也可以是终端设备中的装置，或者是能够和终端设备匹配使用的装置。其中，该装置可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。通信装置1100包括至少一个处理器1120，用于实现本申请实施例提供的方法中终端设备的功能。通信装置1100还可以包括通信接口1110。在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口，用于通过传输介质和其它设备进行通信。例如，通信接口1110用于通信装置1100中的装置可以和其它设备进行通信。处理器1120利用通信接口1110收发数据，并用于实现上述方法实施例所述的方法。
示例性地，在一个实施例中，处理器1120利用通信接口1110用于：处于RRC空闲(IDLE)态或RRC INACTIVE态时，通过第一数据无线承载DRB向网络设备发送上行数据，或者向网络设备发送第一数据无线承载DRB的上行数据。处理器1120利用通信接口1110还用于接收来自网络设备的第一消息，第一消息用于指示终端设备进入RRC连接态。处理器1120利用通信接口1110还用于：通过第二DRB向网络设备发送第一DRB的上行数据。
在另一个实施例中，处理器1120利用通信接口1110用于：处于RRC非激活INACTIVE态时，向第一小区发送第一数据无线承载DRB的上行数据。处理器1120用于：执行小区重选。处理器1120利用通信接口1110还用于：通过第一DRB向第二小区发送第一DRB的上行数据，其中，第二小区为小区重选的目标小区。
在另一个实施例中，处理器1120利用通信接口1110用于：处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，向网络设备发送第一数据无线承载DRB的上行数据。处理器1120用于：从第一数据传输方式回退到第二数据传输方式。处理器1120利用通信接口1110还用于：通过第二数据传输方式，向网络设备发送第一DRB的上行数据。
处理器1120和通信接口1110还可以用于执行上述方法实施例终端设备执行的其它对应的步骤或操作，在此不再一一赘述。
通信装置1100还可以包括至少一个存储器1130，用于存储程序指令和/或数据。存储器1130和处理器1120耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。 处理器1120可能和存储器1130协同操作。处理器1120可能执行存储器1130中存储的程序指令。所述至少一个存储器中的至少一个可以与处理器集成在一起。
本申请实施例中不限定上述通信接口1110、处理器1120以及存储器1130之间的具体连接介质。本申请实施例在图11中以存储器1130、处理器1120以及通信接口1110之间通过总线1140连接，总线在图11中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信装置1100和通信装置1100具体是芯片或者芯片系统时，通信模块1001和通信接口1110所输出或接收的可以是基带信号。通信装置1100和通信装置1100具体是设备时，通信模块1001和通信接口1110所输出或接收的可以是射频信号。在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器1130可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请上述方法实施例描述的终端设备或网络设备所执行的操作和功能中的部分或全部，或者终端设备或网络设备所执行的操作和功能中的部分或全部，可以用芯片或集成电路来完成。
为了实现上述图10或图11所述的通信装置的功能，本申请实施例还提供一种芯片，包括处理器，用于支持该通信装置实现上述方法实施例中终端设备或网络设备所涉及的功能。在一种可能的设计中，该芯片与存储器连接或者该芯片包括存储器，该存储器用于保存该通信装置必要的程序指令和数据。
本申请实施例提供了一种计算机可读存储介质，存储有计算机程序，该计算机程序包括用于执行上述方法实施例的指令。
本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述方法实施例被执行。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机 程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (59)

  1. 一种数据传输方法，其特征在于，所述方法应用于终端设备或终端设备中的芯片，所述方法包括：
    处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，向网络设备发送第一数据无线承载DRB的上行数据；
    接收来自所述网络设备的第一消息，所述第一消息用于指示所述终端设备进入RRC连接态；
    通过第二DRB向所述网络设备发送所述第一DRB的上行数据。
  2. 如权利要求1所述的方法，其特征在于，在所述通过第二DRB向所述网络设备发送所述第一DRB的上行数据之前，所述方法还包括：保留所述第一DRB的上行数据。
  3. 如权利要求2所述的方法，其特征在于，所述保留所述第一DRB的上行数据，包括：
    保留所述第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU和/或所述第一DRB对应的PDCP协议数据单元PDU。
  4. 如权利要求3所述的方法，其特征在于，所述方法还包括：停止所述PDCP SDU和/或PDCP PDU对应的丢弃定时器。
  5. 如权利要求2所述的方法，其特征在于，所述保留所述第一DRB的上行数据，包括：
    保留所述第一DRB对应的业务数据适配协议SDAP SDU和/或所述第一DRB对应的SDAP PDU。
  6. 如权利要求1～5任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述网络设备的第二消息，所述第二消息用于指示所述第二DRB。
  7. 如权利要求1～5任一项所述的方法，其特征在于，所述第二DRB为所述终端设备建立的一个或多个DRB中标识最小的DRB；或者，所述第二DRB为所述终端设备建立的一个或多个DRB中标识最大的DRB；或者，所述第二DRB为所述终端设备建立的一个或多个DRB中与所述第一DRB的标识相同的DRB；或者，所述第二DRB为根据服务质量QoS流到DRB的映射规则确定的DRB。
  8. 一种数据传输方法，其特征在于，所述方法应用于终端设备或终端设备中的芯片，所述方法包括：
    处于RRC非激活INACTIVE态时，向第一小区发送第一数据无线承载DRB的上行数据；
    执行小区重选；
    通过所述第一DRB向第二小区发送所述第一DRB的上行数据，所述第二小区为所述小区重选的目标小区。
  9. 如权利要求8所述的方法，其特征在于，在所述执行小区重选之后，所述终端设备处于所述RRC INACTIVE态。
  10. 如权利要求8或9所述的方法，其特征在于，在所述执行小区重选之后，挂起所述第一DRB；和/或，在所述执行小区重选之后，挂起所述第一DRB对应的PDCP实体。
  11. 如权利要求8～10任一项所述的方法，其特征在于，所述发送所述第一DRB的上 行数据，包括：
    重传所述第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU。
  12. 如权利要求11所述的方法，其特征在于，重传所述第一DRB对应的PDCP SDU，包括：执行所述第一DRB的PDCP重建立过程；或者，通过RRC层通知所述第一DRB的PDCP层重传所述PDCP SDU。
  13. 如权利要求8～12任一项所述的方法，其特征在于，在所述执行小区重选之后，
    保留所述第一DRB对应的PDCP SDU；和/或，在所述执行小区重选之后，保留所述第一DRB对应的PDCP协议数据单元PDU。
  14. 如权利要求13所述的方法，其特征在于，所述方法还包括：停止所述PDCP SDU和/或PDCP PDU对应的丢弃定时器。
  15. 如权利要求8～12任一项所述的方法，其特征在于，在所述执行小区重选之后，保留所述第一DRB对应的业务数据适配协议SDAP SDU；和/或，在所述执行小区重选之后，保留所述第一DRB对应的SDAP PDU。
  16. 如权利要求8～15任一项所述的方法，其特征在于，所述方法包括：
    确定未收到来自所述网络设备的针对所述第一DRB的上行数据的响应消息。
  17. 一种数据传输方法，其特征在于，所述方法应用于终端设备或终端设备中的芯片，所述方法包括：
    处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，向网络设备发送第一数据无线承载DRB的上行数据；
    从所述第一数据传输方式回退到第二数据传输方式；
    通过所述第二数据传输方式，向所述网络设备发送所述第一DRB的上行数据。
  18. 如权利要求17所述的方法，其特征在于，所述向所述网络设备发送所述第一DRB的上行数据，包括：
    对所述第一DRB的上行数据，进行RLC层数据重传；或者，对所述第一DRB的上行数据，进行PDCP层数据重传；对所述第一DRB的上行数据，进行MAC层数据重传。
  19. 如权利要求17或18所述的方法，其特征在于，所述第一数据传输方式为基于随机接入RA方式进行数据早传，所述第二数据传输方式为基于基于配置的授权CG进行数据早传；或者，所述第一数据传输方式为基于CG进行数据早传，所述第二数据传输方式为基于RA进行数据早传；或者，所述第一数据传输方式包括基于RA方式或基于CG进行数据早传，所述第二数据传输方式为进入RRC连接态进行数据传输。
  20. 一种通信装置，其特征在于，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器，或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器用于通过逻辑电路或执行代码指令，以执行以下操作：
    处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，通过所述通信接口向网络设备发送第一数据无线承载DRB的上行数据；
    以及通过所述通信接口接收来自所述网络设备的第一消息，所述第一消息用于指示所述终端设备进入RRC连接态；
    通过第二DRB向所述网络设备发送所述第一DRB的上行数据。
  21. 如权利要求20所述的装置，其特征在于，所述处理器还用于：在所述通过第二 DRB向所述网络设备发送所述第一DRB的上行数据之前，保留所述第一DRB的上行数据。
  22. 如权利要求21所述的装置，其特征在于，在保留所述第一DRB的上行数据时，所述处理器具体用于：
    保留所述第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU和/或所述第一DRB对应的PDCP协议数据单元PDU。
  23. 如权利要求22所述的装置，其特征在于，所述处理器还用于：停止所述PDCP SDU和/或PDCP PDU对应的丢弃定时器。
  24. 如权利要求21所述的装置，其特征在于，在保留所述第一DRB的上行数据时，所述处理器具体用于：
    保留所述第一DRB对应的业务数据适配协议SDAP SDU和/或所述第一DRB对应的SDAP PDU。
  25. 如权利要求20～24任一项所述的装置，其特征在于，所述处理器还用于：通过所述通信接口接收来自所述网络设备的第二消息，所述第二消息用于指示所述第二DRB。
  26. 如权利要求20～24任一项所述的装置，其特征在于，所述第二DRB为所述终端设备建立的一个或多个DRB中标识最小的DRB；或者，所述第二DRB为所述终端设备建立的一个或多个DRB中标识最大的DRB；或者，所述第二DRB为所述终端设备建立的一个或多个DRB中与所述第一DRB的标识相同的DRB；或者，所述第二DRB为根据服务质量QoS流到DRB的映射规则确定的DRB。
  27. 一种通信装置，其特征在于，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器，或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器用于通过逻辑电路或执行代码指令，以执行以下操作：处于RRC非激活INACTIVE态时，通过所述通信接口向第一小区发送第一数据无线承载DRB的上行数据；
    执行小区重选；
    通过所述第一DRB通过所述通信接口向第二小区发送所述第一DRB的上行数据，所述第二小区为所述小区重选的目标小区。
  28. 如权利要求27所述的装置，其特征在于，在所述执行小区重选之后，所述通信装置处于所述RRC INACTIVE态。
  29. 如权利要求27或28所述的装置，其特征在于，所述处理器还用于：
    在所述执行小区重选之后，挂起所述第一DRB；和/或，在所述执行小区重选之后，挂起所述第一DRB对应的PDCP实体。
  30. 如权利要求27～29任一项所述的装置，其特征在于，在发送所述第一DRB的上行数据时，所述处理器具体用于：
    重传所述第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU。
  31. 如权利要求30所述的装置，其特征在于，在重传所述第一DRB对应的PDCP SDU时，所述处理器具体用于：执行所述第一DRB的PDCP重建立过程；或者，通过RRC层通知所述第一DRB的PDCP层重传所述PDCP SDU。
  32. 如权利要求27～31任一项所述的装置，其特征在于，所述处理器还用于：
    在所述执行小区重选之后，保留所述第一DRB对应的PDCP SDU；和/或，在所述执行小区重选之后，保留所述第一DRB对应的PDCP协议数据单元PDU。
  33. 如权利要求32所述的装置，其特征在于，所述处理器还用于：停止所述PDCP SDU和/或PDCP PDU对应的丢弃定时器。
  34. 如权利要求27～31任一项所述的装置，其特征在于，所述处理器还用于：
    在所述执行小区重选之后，保留所述第一DRB对应的业务数据适配协议SDAP SDU；和/或，在所述执行小区重选之后，保留所述第一DRB对应的SDAP PDU。
  35. 如权利要求27～34任一项所述的装置，其特征在于，所述处理器还用于：
    确定未收到来自所述网络设备的针对所述第一DRB的上行数据的响应消息。
  36. 一种通信装置，其特征在于，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器，或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器用于通过逻辑电路或执行代码指令，以执行以下操作：
    处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，通过所述通信接口向网络设备发送第一数据无线承载DRB的上行数据；
    从所述第一数据传输方式回退到第二数据传输方式；
    通过所述第二数据传输方式，通过所述通信接口向所述网络设备发送所述第一DRB的上行数据。
  37. 如权利要求36所述的装置，其特征在于，在向所述网络设备发送所述第一DRB的上行数据时，所述处理器具体用于：
    对所述第一DRB的上行数据，进行RLC层数据重传；或者，对所述第一DRB的上行数据，进行PDCP层数据重传；对所述第一DRB的上行数据，进行MAC层数据重传。
  38. 如权利要求36或37所述的装置，其特征在于，所述第一数据传输方式为基于随机接入RA方式进行数据早传，所述第二数据传输方式为基于基于配置的授权CG进行数据早传；或者，所述第一数据传输方式为基于CG进行数据早传，所述第二数据传输方式为基于RA进行数据早传；或者，所述第一数据传输方式包括基于RA方式或基于CG进行数据早传，所述第二数据传输方式为进入RRC连接态进行数据传输。
  39. 一种通信装置，其特征在于，包括：
    发送模块，用于在所述通信装置处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，向网络设备发送第一数据无线承载DRB的上行数据；
    接收模块，用于接收来自所述网络设备的第一消息，所述第一消息用于指示所述终端设备进入RRC连接态；
    发送模块，还用于通过第二DRB向所述网络设备发送所述第一DRB的上行数据。
  40. 如权利要求39所述的装置，其特征在于，还包括：
    处理模块，用于在所述通过第二DRB向所述网络设备发送所述第一DRB的上行数据之前，保留所述第一DRB的上行数据。
  41. 如权利要求40所述的装置，其特征在于，在保留所述第一DRB的上行数据时，所述处理模块具体用于：
    保留所述第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU和/或所述第一DRB对应的PDCP协议数据单元PDU。
  42. 如权利要求41所述的装置，其特征在于，所述处理模块还用于：停止所述PDCP SDU和/或PDCP PDU对应的丢弃定时器。
  43. 如权利要求40所述的装置，其特征在于，在保留所述第一DRB的上行数据时，所述处理模块具体用于：
    保留所述第一DRB对应的业务数据适配协议SDAP SDU和/或所述第一DRB对应的SDAP PDU。
  44. 如权利要求39～43任一项所述的装置，其特征在于，所述接收模块还用于接收来自所述网络设备的第二消息，所述第二消息用于指示所述第二DRB。
  45. 如权利要求39～43任一项所述的装置，其特征在于，所述第二DRB为所述终端设备建立的一个或多个DRB中标识最小的DRB；或者，所述第二DRB为所述终端设备建立的一个或多个DRB中标识最大的DRB；或者，所述第二DRB为所述终端设备建立的一个或多个DRB中与所述第一DRB的标识相同的DRB；或者，所述第二DRB为根据服务质量QoS流到DRB的映射规则确定的DRB。
  46. 一种通信装置，其特征在于，包括：
    通信模块，用于当所述通信装置处于RRC非激活INACTIVE态时，向第一小区发送第一数据无线承载DRB的上行数据；
    处理模块，用于执行小区重选；
    所述通信模块，还用于通过所述第一DRB向第二小区发送所述第一DRB的上行数据，所述第二小区为所述小区重选的目标小区。
  47. 如权利要求46所述的装置，其特征在于，在所述执行小区重选之后，所述通信装置处于所述RRC INACTIVE态。
  48. 如权利要求46或47所述的装置，其特征在于，所述处理模块还用于：
    在所述执行小区重选之后，挂起所述第一DRB；和/或，在所述执行小区重选之后，挂起所述第一DRB对应的PDCP实体。
  49. 如权利要求46～48任一项所述的装置，其特征在于，在发送所述第一DRB的上行数据时，所述处理模块具体用于：
    通过所述通信模块重传所述第一DRB对应的分组数据汇聚协议PDCP服务数据单元SDU。
  50. 如权利要求49所述的装置，其特征在于，在重传所述第一DRB对应的PDCP SDU时，所述处理模块具体用于：执行所述第一DRB的PDCP重建立过程；或者，通过RRC层通知所述第一DRB的PDCP层重传所述PDCP SDU。
  51. 如权利要求46～50任一项所述的装置，其特征在于，所述处理模块还用于：
    在所述执行小区重选之后，保留所述第一DRB对应的PDCP SDU；和/或，在所述执行小区重选之后，保留所述第一DRB对应的PDCP协议数据单元PDU。
  52. 如权利要求51所述的装置，其特征在于，所述处理模块还用于：停止所述PDCP SDU和/或PDCP PDU对应的丢弃定时器。
  53. 如权利要求46～50任一项所述的装置，其特征在于，所述处理模块还用于：
    在所述执行小区重选之后，保留所述第一DRB对应的业务数据适配协议SDAP SDU；和/或，在所述执行小区重选之后，保留所述第一DRB对应的SDAP PDU。
  54. 如权利要求46～53任一项所述的装置，其特征在于，所述处理模块还用于：
    确定未收到来自所述网络设备的针对所述第一DRB的上行数据的响应消息。
  55. 一种通信装置，其特征在于，包括：
    通信模块，用于当所述通信装置处于无线资源控制RRC空闲态或RRC非激活INACTIVE态时，基于第一数据传输方式，向网络设备发送第一数据无线承载DRB的上行数据；
    处理模块，用于从所述第一数据传输方式回退到第二数据传输方式；
    所述通信模块，还用于通过所述第二数据传输方式，向所述网络设备发送所述第一DRB的上行数据。
  56. 如权利要求55所述的装置，其特征在于，在向所述网络设备发送所述第一DRB的上行数据时，所述处理模块具体用于：
    对所述第一DRB的上行数据，进行RLC层数据重传；或者，对所述第一DRB的上行数据，进行PDCP层数据重传；对所述第一DRB的上行数据，进行MAC层数据重传。
  57. 如权利要求55或56所述的装置，其特征在于，所述第一数据传输方式为基于随机接入RA方式进行数据早传，所述第二数据传输方式为基于基于配置的授权CG进行数据早传；或者，所述第一数据传输方式为基于CG进行数据早传，所述第二数据传输方式为基于RA进行数据早传；或者，所述第一数据传输方式包括基于RA方式或基于CG进行数据早传，所述第二数据传输方式为进入RRC连接态进行数据传输。
  58. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于控制所述装置实现如权利要求1～7任一项所述的方法，或所述处理器用于控制所述装置实现如权利要求8～16任一项所述的方法，或所述处理器用于控制所述装置实现如权利要求17～19任一项所述的方法。
  59. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1～7任一项所述的方法，或，实现如权利要求8～16任一项所述的方法，或，实现如权利要求17～19任一项所述的方法。
PCT/CN2020/110110 2020-08-19 2020-08-19 一种数据传输方法及通信装置 WO2022036611A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/110110 WO2022036611A1 (zh) 2020-08-19 2020-08-19 一种数据传输方法及通信装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/110110 WO2022036611A1 (zh) 2020-08-19 2020-08-19 一种数据传输方法及通信装置

Publications (1)

Publication Number Publication Date
WO2022036611A1 true WO2022036611A1 (zh) 2022-02-24

Family

ID=80322412

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/110110 WO2022036611A1 (zh) 2020-08-19 2020-08-19 一种数据传输方法及通信装置

Country Status (1)

Country Link
WO (1) WO2022036611A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117202257A (zh) * 2022-05-31 2023-12-08 荣耀终端有限公司 一种用户数据处理方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307512A (zh) * 2016-09-06 2018-07-20 中兴通讯股份有限公司 一种连接态的恢复方法及装置
CN108616941A (zh) * 2017-01-04 2018-10-02 电信科学技术研究院 一种终端位置信息上报、下行传输方法及装置
CN108632815A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 通信方法与设备
CN110139365A (zh) * 2018-02-08 2019-08-16 展讯通信（上海）有限公司 在非激活状态下传输数据的方法、装置及用户设备
US20190313333A1 (en) * 2018-04-05 2019-10-10 Samsung Electronics Co., Ltd. Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307512A (zh) * 2016-09-06 2018-07-20 中兴通讯股份有限公司 一种连接态的恢复方法及装置
CN108616941A (zh) * 2017-01-04 2018-10-02 电信科学技术研究院 一种终端位置信息上报、下行传输方法及装置
CN108632815A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 通信方法与设备
CN110139365A (zh) * 2018-02-08 2019-08-16 展讯通信（上海）有限公司 在非激活状态下传输数据的方法、装置及用户设备
US20190313333A1 (en) * 2018-04-05 2019-10-10 Samsung Electronics Co., Ltd. Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI (SUMMARY RAPPORTEUR): "Summary of Connection to 5GC in AI 7.1.12", 3GPP DRAFT; R2-2002014, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200224 - 20200306, 20 February 2020 (2020-02-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051850005 *
HUAWEI, HISILICON: "SRBs and DRBs handling for NB-IoT and eMTC connected to 5GC", 3GPP DRAFT; R2-2000646, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20200224 - 20200306, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051849223 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117202257A (zh) * 2022-05-31 2023-12-08 荣耀终端有限公司 一种用户数据处理方法和装置

Similar Documents

Publication Publication Date Title
US11706814B2 (en) Communications device, infrastructure equipment and methods
CN108886748B (zh) 用于减少信令开销和减少终端电池的方法和设备
CN114071804B (zh) 非活跃状态下的无连接数据传输方法和用户设备
WO2013166670A1 (zh) 上行信道资源配置方法和设备
WO2017118012A1 (zh) 一种数据传输方法、装置及系统
WO2019153928A1 (zh) Rrc状态转换方法、终端、cu、du和计算机可读存储介质
US20220338298A1 (en) Context management method and apparatus
US20090190572A1 (en) Downlink data control system for radio access networks
WO2022206618A1 (zh) 一种通信方法及装置
TW201911824A (zh) 處理承載型態改變的裝置及方法
US20230199895A1 (en) Methods and apparatus for data transmission in new radio (nr) inactive state
CN115022865A (zh) 一种通信方法及设备
WO2022036611A1 (zh) 一种数据传输方法及通信装置
US20230199600A1 (en) Method and communications apparatus for configuring assistance information
US20230156847A1 (en) Methods and apparatus for data transmission in new radio (nr) inactive state
WO2023276985A1 (ja) マスタノード、通信制御方法、及び通信装置
KR20220097893A (ko) 정보 전송 방법 및 관련 제품
WO2022121922A1 (zh) 一种被用于无线通信的通信节点中的方法和装置
WO2022141332A1 (zh) 一种通信方法及装置
WO2022032681A1 (zh) 一种数据传输方法及通信装置
WO2021057902A1 (zh) 资源使用方法及通信设备
WO2023093868A1 (zh) 一种通信方法及设备
US20240214127A1 (en) Method for data transmission, terminal device, and computer storage medium
CN115211220B (zh) 一种无线链路的重建方法和装置
WO2023065316A1 (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: 20949822

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

Country of ref document: EP

Kind code of ref document: A1