WO2018165995A9 - 一种数据处理方法及终端设备、基站 - Google Patents

一种数据处理方法及终端设备、基站 Download PDF

Info

Publication number
WO2018165995A9
WO2018165995A9 PCT/CN2017/078199 CN2017078199W WO2018165995A9 WO 2018165995 A9 WO2018165995 A9 WO 2018165995A9 CN 2017078199 W CN2017078199 W CN 2017078199W WO 2018165995 A9 WO2018165995 A9 WO 2018165995A9
Authority
WO
WIPO (PCT)
Prior art keywords
radio bearer
type
rlc
layer entity
terminal device
Prior art date
Application number
PCT/CN2017/078199
Other languages
English (en)
French (fr)
Other versions
WO2018165995A1 (zh
Inventor
徐海博
坦尼纳坦•爱德华
邝奕如
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17900535.0A priority Critical patent/EP3585087B1/en
Priority to US16/492,969 priority patent/US11096184B2/en
Priority to CN201780032825.3A priority patent/CN109196902B/zh
Publication of WO2018165995A1 publication Critical patent/WO2018165995A1/zh
Publication of WO2018165995A9 publication Critical patent/WO2018165995A9/zh
Priority to US17/375,290 priority patent/US11924870B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H04L1/1841—Resequencing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors
    • H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to a data processing method, a terminal device, and a base station.
  • a user equipment can be directly connected to the base station, and communicates with the base station in a direct connection manner, or can be connected to the base station through a relay UE (also referred to as a UE-to-Network Relay), and performs data communication through the relay.
  • the user equipment that performs data communication between the UE and the base station is called a remote user equipment (Remote UE).
  • the Remote UE may be referred to as an eRemote UE, which may also be referred to as an Evolved Remote UE.
  • the Relay UE may be referred to as an eRelay UE, also referred to as an Evolved Relay UE or an Evolved UE-to-NW Relay.
  • the eRelay UE forwards data of the eRemote UE through a Data Radio Bearer (DRB) and a Signaling Radio Bearer (SRB).
  • DRB Data Radio Bearer
  • SRB Signaling Radio Bearer
  • Manner 1 Multiplexing a radio bearer of the eRelay UE to transmit a radio bearer of the eRemote UE, the radio bearer of the eRelay UE for simultaneously transmitting its own data/signaling and data/signaling of at least one eRemote UE, For type I radio bearers.
  • the eRelay UE specifically establishes a radio bearer to transmit a radio bearer of the eRemote UE, and the radio bearer of the eRelay UE that is only used to transmit data/signaling of at least one eRemote UE is called a Type II radio bearer.
  • the eRelay UE also has another type of radio bearer, that is, a radio bearer that only transmits the data/signaling of the eRelay UE itself, and the radio bearer becomes a type III radio bearer.
  • a radio bearer of the eRelay UE may perform the conversion of the Type I radio bearer and the Type III radio bearer described above in some cases.
  • the base station may configure the eRemote UE to multiplex a data radio bearer currently existing by the eRelay UE.
  • the type of the data radio bearer can be converted from the type III to the type I.
  • the first type I data radio bearer multiplexed by the eRemote UE and the eRelay UE no longer needs to transmit the data of the eRemote UE, and the type of the data radio bearer can be converted from the type I.
  • type III For type III.
  • the RLC layer corresponding to the radio bearer and the radio bearer may buffer the data packet generated by the radio bearer according to the protocol stack corresponding to the original type.
  • the format of the data packet generated by the protocol stack of the new type of radio bearer is different from the format of the data packet generated by the protocol stack of the original type radio bearer. Therefore, when the receiving end receives the data packet corresponding to the cached original radio bearer type, if the data packet is parsed according to the new radio bearer type corresponding packet format, the error parsed data packet is delivered to the upper protocol stack. For example, the IP layer eventually leads to packet loss.
  • the embodiment of the present application provides a data processing method, a terminal device, and a base station, which are used to solve the problem of how to avoid packet loss when a type between a type I and a type III of a radio bearer is converted in the prior art. problem.
  • the application provides a data processing method, including:
  • the terminal device determines that the type of the at least one radio bearer of the terminal device is converted from the first type to the second type;
  • the terminal device discards the RLC protocol data unit and/or the RLC service data unit buffered by the transmitting side of the radio link control protocol RLC layer entity of the at least one radio bearer;
  • the terminal device assembles the RLC protocol data unit that has been received by the RLC layer entity receiving side of the at least one radio bearer into an RLC service data unit, and delivers the RLC service data unit to the RLC layer entity in order.
  • An upper layer entity wherein the upper layer entity is an upper layer entity of the RLC layer entity before the at least one radio bearer type is converted.
  • the RLC layer entity for the transmitting side of the RLC layer entity of the at least one radio bearer of the terminal device, when the type of the at least one radio bearer of the terminal device is changed, the RLC layer entity sends the uplink data buffered by the transmitting side. Including the data packets that have not been sent to the MAC layer entity, and the data packets are sent to the base station after the type conversion, which causes the base station side to unpack the packet to generate the packet loss, and discards the data cached by the transmitting side of the RLC layer entity of the radio bearer.
  • the base station does not receive the data packets, the PDCP status report of the at least one radio bearer is sent to the terminal device, and the terminal device is instructed to resend the data packets to avoid packet discarding caused by the unpacking failure. Discarding these packets that may cause unpacking failures, avoiding wasted resources caused by invalid packets, and saving valuable air interface resources.
  • the downlink data received by the receiving side of the RLC layer entity includes Packets received before type conversion but not yet delivered to the upper layer entity (upper layer entity before type conversion), these packets have been sent successfully, in order to avoid wasting air interface resource retransmission, when the type conversion occurs, the data is Submitted to the upper entity before the type conversion, to ensure that the data packet can be properly unpacked, avoiding the unpacking failure caused by the upper entity submitted after the type conversion.
  • the method further includes:
  • the terminal device stops and resets all timers of the RLC layer entity of the at least one radio bearer
  • the terminal device resets all state variables of the RLC layer entity of the at least one radio bearer to an initial value.
  • the upper layer entity of the RLC layer entity is a packet data convergence protocol PDCP layer entity; when the type of the at least one radio bearer is the second type, the RLC The upper layer entity of the layer entity is an adaptation protocol layer entity; or
  • the upper layer entity of the RLC layer entity is an adaptation protocol layer entity; when the type of the at least one radio bearer is the second type, the upper layer of the RLC layer entity The entity is the PDCP layer entity.
  • the method further includes:
  • the PDCP protocol data unit is delivered to the underlying entity before the at least one radio bearer type is converted, but the underlying entity has not fed back the PDCP protocol data unit that is successfully received; wherein the underlying entity is the An underlying entity of the PDCP layer entity before the at least one radio bearer type is converted;
  • the terminal device generates and sends a PDCP status report, where the PDCP status report is used to notify the base station of the sequence number of the PDCP service data unit that is not successfully received.
  • the RLC acknowledge mode is adopted to adapt to the at least one radio bearer.
  • An application scenario for transmitting downlink data for an uplink PDCP PDU that is sent before the type conversion but has not received a successful reception acknowledgement, the PDCP entity needs to retransmit the data packet. Thereby it can be guaranteed that the data packet will not be lost.
  • the method further includes:
  • the terminal device resets the value of the variable of the sequence number of the next transmitted PDCP service data unit and the value of the superframe number to 0 by the PDCP entity of the at least one radio bearer;
  • the terminal device resets the value of the variable of the sequence number of the next received PDCP service data unit and the value of the superframe number to 0 by the PDCP entity of the at least one radio bearer.
  • the method further includes:
  • the terminal device resets the medium access control MAC layer entity.
  • the terminal device clears a buffer of all uplink HARQ processes of the media access control MAC layer entity
  • the terminal device sets the new data indication information of all uplink HARQ processes to 0.
  • the terminal device clears a buffer of all downlink HARQ processes of the media access control MAC layer entity
  • the terminal device For each downlink HARQ process, the terminal device considers its subsequently received transport block as the first transmission of the transport block.
  • the method further includes:
  • the media access control MAC layer entity of the terminal device receives the type-converted MAC protocol data unit of the at least one radio bearer
  • the MAC protocol data unit includes the MAC service data unit of the at least one radio bearer, the at least one wireless The MAC service data unit carried is discarded.
  • the uplink HARQ process on the transmitting side of the MAC layer entity includes at least one terminal device.
  • the MAC SDU corresponding to the logical channel of the radio bearer is a packet that has not been successfully transmitted
  • the packets are sent to the base station after the type conversion, which causes the base station side to unpack the packet to generate a packet loss.
  • the layer entity is reset, or the buffer of the MAC layer entity sending side uplink HARQ process is cleared.
  • the base station does not receive the data packet, the PDCP status report of at least one radio bearer is sent to the terminal device, indicating that the terminal device is heavy. Send these data packets to avoid packet discarding caused by unpacking failure. On the other hand, discard these packets that may cause unpacking failure, avoiding waste of resources caused by transmitting invalid data packets, and saving valuable air interface resources.
  • the terminal device for the receiving side of the MAC layer entity of the terminal device, at the terminal device When the type of the at least one radio bearer is changed, if the buffer of the downlink HARQ process on the receiving side of the MAC layer entity includes the MAC PDU of the terminal device waiting for HARQ retransmission, and the MAC PDU includes the MAC of the at least one radio bearer In the SDU, after the type conversion occurs, the MAC SDUs are delivered to the upper MAC entity, which causes the upper layer entity to unpack the packet to be lost. The MAC layer entity is reset, or the downlink HARQ process on the receiving side of the MAC layer entity is received.
  • the cache is emptied, or the MAC SDU corresponding to the logical channel of the at least one radio bearer is discarded before the type conversion of the buffer of the downlink HARQ process on the receiving side of the MAC layer entity.
  • the terminal device if the terminal device does not receive the data packet, the terminal device further Sending a PDCP status report of the at least one radio bearer of the terminal device to the base station, instructing the base station to resend the data packets, and avoiding packet discarding caused by the unpacking failure of the terminal device, and on the other hand, discarding the data packets that may cause unpacking failure To avoid wasting resources caused by transmitting invalid data packets, and save valuable air interface resources.
  • the second aspect of the present application provides a data processing method, including:
  • the first device receives the first indication information that is sent by the second device, where the first indication information is used to indicate that the radio bearer type of the data of the at least one radio bearer received by the first device is a first type of radio Bearer or second type radio bearer;
  • the first device is a terminal device, and the second device is a base station; or the first device is a base station, and the second device is a terminal device.
  • the first indication information may be used to notify the receiving end device which data packets need to be delivered to the PDCP layer of the receiving end device after the RLC layer of the receiving end device is processed, and which data packets are processed in the RLC layer of the receiving end device. Afterwards, it needs to be submitted to the protocol adaptation layer of the receiving device, so as to ensure that the data packet can be correctly unpacked, and the unpacking failure caused by the type conversion is avoided.
  • the first indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, and the RLC protocol data unit is included according to the The last RLC protocol data unit of the RLC service data unit encapsulated by the format of the first type of radio bearer, or the RLC protocol data unit refers to an RLC service data unit that is encapsulated according to the format of the second type radio bearer The first RLC protocol data unit.
  • the radio bearer type of the received RLC protocol data unit of the at least one radio bearer according to the first indication information and the received sequence number of the RLC protocol data unit of the at least one radio bearer a first type of radio bearer or a second type of radio bearer;
  • the first device acquiring the first indication information includes:
  • the first device receives an RRC connection reconfiguration message of the at least one radio bearer sent by the second device, where the RRC connection reconfiguration message includes the first indication information or
  • the RLC control protocol data unit includes the first indication information.
  • the acquiring, by the first device, the first indication information includes:
  • MAC protocol data unit that is sent by the second device, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, where the MAC service data unit corresponds to a MAC subheader.
  • the method further includes:
  • the first device sends the second indication information to the second device, where the second indication information is used to notify the second device that the radio bearer type of the data of the at least one radio bearer is the first type. Radio bearer or second type radio bearer.
  • the second indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included
  • the sending, by the first device, the second indication information to the second device includes:
  • the first device sends an RRC connection reconfiguration complete message of the at least one radio bearer to the second device, where the RRC connection reconfiguration complete message includes the second indication information;
  • the first device sends the RLC control protocol data unit of the at least one radio bearer to the second device, where the second indication information is included in the RLC control protocol data unit.
  • the sending, by the first device, the second indication information to the second device includes:
  • the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, where the MAC sub-header corresponding to the MAC service data unit carries
  • the second indication information is described.
  • the application provides a data processing method, including:
  • the terminal device receives the first configuration information that is sent by the base station, where the first configuration information is used to configure the at least one radio bearer of the terminal device to be converted into the second type radio bearer by the first type of radio bearer;
  • the terminal device determines, according to the first configuration information, that the type of the at least one radio bearer is converted by the first type of radio bearer to the second type of radio bearer, including:
  • the terminal device Determining, by the terminal device, that the at least one radio bearer is a currently configured radio bearer according to the identifier of the at least one radio bearer carried in the first configuration information, and determining that the type of the at least one radio bearer is first Type radio bearer,
  • the first configuration information includes the third indication information, determining that the type of the at least one radio bearer is converted by the first type of radio bearer to the second type of radio bearer;
  • the first type of radio bearer includes: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity, and a logical channel;
  • the second type radio bearer includes: a PDCP layer entity, the adaptation protocol layer The entity, the RLC layer entity and the logical channel;
  • the third indication information is used to indicate that the type of the radio bearer configured by the terminal device is the second type of radio bearer.
  • the terminal device may determine, according to the first configuration information, that at least one radio bearer of the terminal device is converted into a Type I radio bearer by the Type III radio bearer.
  • the terminal device determines, according to the first configuration information, that the type of the at least one radio bearer is converted by the first type of radio bearer to the second type of radio bearer, including:
  • the terminal device Determining, by the terminal device, that the at least one radio bearer is a currently configured radio bearer according to the identifier of the at least one radio bearer carried in the first configuration information, and determining that the type of the at least one radio bearer is first Type radio bearer,
  • the first configuration information does not include the fifth indication information, determining that the type of the at least one radio bearer is converted by the first type of radio bearer to the second type of radio bearer;
  • the first type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel;
  • the second type of radio bearer includes: a packet data convergence protocol PDCP layer entity, and a radio link
  • the control protocol RLC layer entity and the logical channel, the fifth indication information is used to indicate that the type of the radio bearer configured by the terminal device is the first type of radio bearer.
  • the terminal device may determine, according to the first configuration information, that at least one radio bearer of the terminal device is converted into a Type III radio bearer by the Type I radio bearer.
  • the application provides a data processing method, including:
  • the base station sends the first configuration information to the terminal device, where the first configuration information is used to configure the at least one radio bearer of the terminal device to be converted into the second type radio bearer by the first type of radio bearer.
  • the first type of radio bearer includes: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity, and a logical channel
  • the second type radio bearer includes: a PDCP layer entity , the adaptation protocol layer entity, the RLC layer entity and the logical channel
  • the first configuration information includes an identifier of the at least one radio bearer, and further includes third indication information, where the third indication information is used to indicate that the type of the radio bearer configured by the terminal device is the second type radio bearer.
  • the base station can configure at least one radio bearer of the terminal device to be converted into a Type I radio bearer by the Type III radio bearer.
  • the first type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel
  • the second type of radio bearer includes: a packet data convergence protocol PDCP layer entity, radio link control protocol RLC layer entity and logical channel
  • the first configuration information includes an identifier of the at least one radio bearer, but does not include the fifth indication information, where the fifth indication information is used to indicate that the type of the radio bearer configured by the terminal device is the first type.
  • Wireless bearer the base station can configure that at least one radio bearer of the terminal device is converted into a Type III radio bearer by the Type I radio bearer.
  • the application provides a terminal device, where the terminal device includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction; the processor is configured to execute an instruction stored in the memory, and Controlling the transceiver to perform signal reception and signal transmission, and when the processor executes the instruction stored in the memory, the terminal device is configured to perform the foregoing first aspect or any possible implementation manner of the first aspect The method described.
  • the present application provides a terminal device, where the terminal device includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction, and the processor is configured to execute an instruction stored in the memory according to an instruction Controlling, by the transceiver, signal reception and signal transmission, when the processor executes the instruction stored by the memory, the terminal device is configured to perform any of the foregoing second aspect or the second aspect Terminal related steps.
  • the application provides a base station, where the base station includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction;
  • the processor is configured to control the transceiver to perform signal reception and signal transmission according to an instruction to execute the memory, and when the processor executes the instruction stored in the memory, the base station is configured to execute the second Aspects or steps related to the base station in any of the possible implementations of the second aspect.
  • the present application provides a terminal device, where the terminal device includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction; the processor is configured to execute an instruction stored in the memory, and Controlling the transceiver to perform signal reception and signal transmission, and when the processor executes the instruction stored by the memory, the terminal device is configured to perform any of the foregoing third aspect or the third aspect method.
  • the application provides a base station, where the base station includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction;
  • the processor is configured to control the transceiver to perform signal reception and signal transmission according to an instruction to execute the memory, and the base station is used in the fourth aspect when the processor executes the instruction stored in the memory Or a method in any of the possible implementations of the fourth aspect.
  • the present application provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform any of the first aspect or the first aspect described above The method described in the implementation.
  • the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method described in the first aspect or any of the possible implementations of the first aspect.
  • the present application provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform any of the second aspect or the second aspect described above The method described in the possible implementation.
  • the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method described in any of the second or second aspects of the above.
  • the present application provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform any of the third aspect or the third aspect described above The method described in the possible implementation.
  • the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method described in any of the third or third aspects above.
  • the present application provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform any of the fourth aspect or the fourth aspect described above The method described in the possible implementation.
  • the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method described in any of the above-described fourth or fourth aspects.
  • FIG. 1 is a schematic structural diagram of a system according to an embodiment of the present disclosure
  • 2(a) to 2(d) are schematic diagrams showing a protocol stack of a user plane and a control plane in a system architecture according to an embodiment of the present application;
  • 3(a) to 3(c) are schematic diagrams showing a communication protocol stack of an access network according to an embodiment of the present application.
  • FIG. 3(d) is a schematic diagram of a packet format of a data packet of a type III radio bearer according to an embodiment of the present application
  • FIG. 3(e) is a schematic diagram of a packet format of a data packet of a Type I radio bearer according to an embodiment of the present application
  • FIG. 4 is a flowchart of a method for processing a data according to an embodiment of the present application.
  • FIG. 5 is a flowchart of an uplink data transmission process of converting a Type III radio bearer into a Type I radio bearer according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a downlink data transmission process of converting a Type III radio bearer into a Type I radio bearer according to an embodiment of the present disclosure
  • FIG. 7 is a flowchart of an uplink data transmission process of converting a Type I radio bearer into a Type III radio bearer according to an embodiment of the present disclosure
  • FIG. 8 is a flowchart of a downlink data transmission process of converting a Type I radio bearer into a Type III radio bearer according to an embodiment of the present disclosure
  • FIG. 9 is a flowchart of a method for data processing according to an embodiment of the present application.
  • FIG. 10 is a flowchart of a method for sending an RLC control PDU according to an embodiment of the present disclosure
  • FIG. 11(a) to 11(c) are schematic diagrams showing the structure of an RLC control PDU according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a MAC PDU according to an embodiment of the present disclosure.
  • FIG. 13 and FIG. 14 are schematic structural diagrams of a terminal device according to an embodiment of the present application.
  • FIG. 15 and FIG. 16 are schematic structural diagrams of a base station according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of a format of a status report of an SRB according to an embodiment of the present disclosure.
  • LTE systems such as LTE/LTE-A/eLTE systems
  • LTE/LTE-A/eLTE systems or other wireless communication systems using various wireless access technologies, for example, using multiple code divisions.
  • SC-FDMA single carrier-frequency division multiple access
  • 5G also known as new radio
  • NR new radio
  • an infrastructure of the communication system of the present application includes a relay terminal 20, a remote terminal 30, and a base station 10, and the base station 10 and the relay terminal 20 can perform data or signaling transmission through a wireless interface, including For uplink transmission and downlink transmission, the connection between the relay terminal 20 and the base station 10 includes an uplink and a downlink.
  • the remote terminal 30 is connected to the base station 10 through the relay terminal 20 and performs data or signaling transmission, and the connection between the relay terminal 20 and the remote terminal 30 is a side link.
  • the relay terminal 20 passes the RLC layer entity of the relay terminal 20, and the PDCP layer entity performs data forwarding.
  • the data forwarding mode may be called Layer 2 UE-to-NW Relay.
  • the remote terminal 30 may be referred to as an eRemote UE, which may also be referred to as an Evolved Remote UE, and the relay terminal 20 may be referred to as an eRelay UE, also referred to as an Evolved Relay UE or an Evolved UE-to-NW Relay.
  • the remote terminal 30 when the remote terminal 30 connects to the network side through the relay terminal 20 and transmits data, the remote terminal 30 and the relay terminal 20 are connected through a Sidelink technology/PC5 interface, and the remote terminal 30 and the relay terminal are connected.
  • the base station (eNB) 10 and the core network (CN) user plane protocol stack see FIG. 2 (a)
  • the remote terminal 30, the relay terminal 20 the base station (eNB) 10
  • the control plane of the core network (CN) See Figure 2(b) for the protocol stack.
  • the relay terminal 20 and the remote terminal 30 may also be connected by using a non-3GPP access technology.
  • a non-3GPP access technology For example, Bluetooth access technology, WLAN access technology, and the like.
  • the remote terminal 30 is connected to the network side through the relay terminal 20, and the remote terminal 30 and the relay terminal 20 are connected by a non-3GPP access technology, the remote terminal 30, the relay terminal 20, and the base station.
  • the radio bearer is a type I radio bearer, and the communication protocol stack architecture between the relay terminal 20 and the base station (eNB) 10 is shown in FIG. 3(a). As can be seen from FIG.
  • one of the relay terminals 20 or multiple radio bearers include a PDCP layer, a protocol adaptation layer RLC layer, and a logical channel, and a protocol adaptation layer is added between the PDCP layer and the RLC layer of the relay terminal 20; one or more of the base station 10 and the relay terminal 20
  • the protocol layer entities corresponding to the radio bearers include a PDCP layer, a protocol adaptation layer, an RLC layer, and a logical channel, and a protocol adaptation layer is added between the PDCP layer and the RLC layer.
  • the communication protocol stack architecture between the relay terminal 20 and the base station (eNB) 10 is shown in FIG. 3(b), which can be seen from FIG. 3(b). It can be seen that one or more radio bearers of the relay terminal 20 include a protocol adaptation layer, an RLC layer, and a logical channel; a protocol layer in the base station 10 corresponding to one or more radio bearers of the relay terminal 20
  • the entity includes a protocol adaptation layer and an RLC layer.
  • the communication protocol stack architecture between the relay terminal 20 and the base station (eNB) 10 is shown in FIG. 3(c), which can be seen from FIG. 3(c). It can be seen that one or more radio bearers of the relay terminal 20 include a PDCP layer, an RLC layer, and a logical channel; a protocol layer entity corresponding to one or more radio bearers of the relay terminal 20 in the base station 10 includes a PDCP layer, and an RLC Layer, and logical channel.
  • the remote terminal 30 accesses the network side through the relay terminal 20
  • the upper layer entity of the RLC layer entity of one or more radio bearers of the relay terminal 20 is converted by the PDCP layer entity into an adaptation protocol layer entity
  • the PDCP layer entity of one or more radio bearers of the relay terminal 20 The lower layer entity is converted by the RLC layer entity into an adaptation protocol layer entity.
  • the RLC SDU packet format of the RLC layer of one or more radio bearers of the relay terminal 20 is converted by the packet format of the RLC SDU of the Type III radio bearer into the packet format of the RLC SDU of the Type I radio bearer, III.
  • the packet format of the RLC SDU of the type radio bearer see FIG. 3(d)
  • the packet format of the RLC SDU of the Type I radio bearer is shown in FIG. 3(e).
  • the remote terminal 30 when the remote terminal 30 does not access the network side through the relay terminal 20, if one or more radio bearers of the relay terminal 20 are converted from the Type I radio bearer to the first type The type III radio bearer, the upper layer entity of the RLC layer entity of one or more radio bearers of the relay terminal 20 is converted into a PDCP layer entity by the adaptation protocol layer entity, and the PDCP layer entity of one or more radio bearers of the relay terminal 20 The lower layer entity is converted by the adaptation protocol layer entity into an RLC layer entity.
  • the packet format of the data and signaling is converted into the type III radio bearer by the encapsulation format of the type I radio bearer.
  • the package format is converted into the type III radio bearer by the encapsulation format of the type I radio bearer.
  • Relay terminal based on the examples illustrated in Fig. 1, Fig. 2(a), Fig. 2(b), Fig. 2(c), Fig. 2(d), Fig. 3(a), Fig. 3(b), Fig. 3(c)
  • the embodiment of the present application provides a data processing method, a terminal device, and a base station, to solve one or more wireless of the relay terminal 20 existing in the system architecture. How to avoid the technical problem of packet loss when the type of bearer occurs between the Type I and Type III transitions.
  • terminal device in this application refers to the relay terminal 20 in the basic system architecture.
  • the relationship between the user and the terminal (or UE) in the present application may be that the user accesses the network by using the terminal (or UE) to implement communication with the base station.
  • the terminal involved in the present application may be a device that provides voice and/or data connectivity to a user, including a wired terminal and a wireless terminal.
  • the wireless terminal can be a handheld device with wireless connectivity, or other processing device connected to a wireless modem, and a mobile terminal that communicates with one or more core networks via a wireless access network.
  • the wireless terminal can be a mobile phone, a computer, a tablet, a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, and an e-book reader. Wait.
  • the wireless terminal can also be a portable, pocket, handheld, computer built-in or in-vehicle mobile device.
  • the wireless terminal can be a mobile station or an access point.
  • the aforementioned UE is a type of terminal and is a title in the LTE system.
  • the above-mentioned devices are collectively referred to as terminals.
  • the base station involved in the present application is a device deployed in a radio access network (RAN) to provide a wireless communication function for a terminal.
  • the base station may include various forms of macro base stations, micro base stations, relay stations, access point base station controllers, transmission and reception nodes (TRPs), and the like.
  • TRPs transmission and reception nodes
  • the specific name of the base station may be different.
  • an evolved NodeB (eNB) may be used in a subsequent evolved system. It is called new radio node B (gNB).
  • the plurality of articles referred to in the present application mean two or more.
  • the present application provides two types of data processing methods to solve the technical problem of how to avoid packet loss.
  • each protocol layer corresponding to the radio bearer in the terminal device is mainly provided.
  • An implementation manner of processing, by the sending end and the receiving end of the entity, the data packet before the type conversion of the stored radio bearer mainly includes a MAC layer corresponding to the radio bearer, an RLC layer, and a pair of the transmitting end and the receiving end of the PDCP layer. The processing method of the data packet.
  • the radio bearer data radio bearer of a terminal device when the radio bearer data radio bearer of a terminal device needs to perform type conversion, the data packet stored before the type conversion of the radio bearer stored by the transmitting device continues to be transmitted after the type conversion.
  • the receiving device receives data packets of two different encapsulation formats for a period of time.
  • the transmitting end device needs to notify the receiving end device which data packets need to be delivered to the PDCP layer of the receiving end device after the RLC layer of the receiving end device is processed, and which data packets are in the After the RLC layer of the receiving device is processed, it needs to be submitted to the protocol adaptation layer of the receiving device.
  • the second type of data processing method mainly provides several notification methods for the sender device to notify the receiver device that the data packet is of the type of radio bearer.
  • the transmitting end device is a terminal device, and the receiving end device is a base station.
  • the transmitting end device is a base station, and the receiving end device is a terminal.
  • Both of the data processing methods can avoid the loss of the data packet of the relay UE during the transmission process of the access layer caused by the transition of the radio bearer type of the terminal device when the terminal device is used as the relay UE, and can also reduce the wireless of the relay UE. After the bearer is converted, the resource caused by transmitting invalid data packets is wasted.
  • a data processing method as shown in FIG. 4 provided by the present application includes:
  • Step 401 The terminal device determines that the type of the at least one radio bearer of the terminal device is converted from the first type to the second type.
  • Step 402 The terminal device discards the RLC protocol data unit and/or the RLC service data unit buffered by the radio link control protocol RLC layer entity sending side (or the RLC layer sending side entity) of the at least one radio bearer; the terminal The device assembles the RLC protocol data unit received by the RLC layer entity receiving side (or the RLC layer receiving entity) of the at least one radio bearer into an RLC service data unit, and delivers the RLC service data unit to the An upper layer entity of the RLC layer entity; wherein the upper layer entity is an upper layer entity of the RLC layer entity before the at least one radio bearer type is converted.
  • the type of the at least one radio bearer of the terminal device is converted from the first type to the second type, and at least one radio bearer including the terminal device may be converted from the type III radio bearer to the first type.
  • the radio bearer can also be converted from the Type I radio bearer to the Type III radio bearer.
  • the entity corresponding to the radio bearer includes: a PDCP layer entity, an adaptation protocol layer entity, an RLC layer entity, and a logical channel; and at least one radio bearer in the terminal device
  • the entity corresponding to the radio bearer includes: a PDCP layer entity, an RLC layer entity, and a logical channel.
  • the upper layer entity of the RLC layer entity is converted into the PDCP layer entity by the adaptation protocol layer entity, and the lower layer entity of the PDCP layer entity is configured by The adaptation protocol layer entity is converted to an RLC layer entity.
  • the upper layer entity of the RLC layer entity is converted into the adaptation protocol layer entity by the PDCP layer entity, and the lower layer entity of the PDCP layer entity is configured by the RLC layer
  • the entity is converted to an adaptation protocol layer entity.
  • the data radio bearer of the terminal device can transmit data in the RLC Unacknowledged Mode (UM) mode
  • the data can be transmitted in the Rack Acknowledged Mode (AM) mode
  • the signaling radio bearer of the terminal device is adopted.
  • the data is transmitted in the RLC AM mode. Therefore, in order to adapt the at least one radio bearer to the signaling radio bearer or the data radio bearer in the RLC AM mode, in step 402, the RLC protocol of the RLC layer entity of the at least one radio bearer of the terminal device is discarded.
  • Packet Data Unit PDU
  • SDU RLC Service Data Unit
  • the RLC layer entity for the transmitting side of the RLC layer entity of the at least one radio bearer of the terminal device, when the type of the at least one radio bearer of the terminal device is changed, the RLC layer entity sends the uplink data buffered by the transmitting side. Including the data packets that have not been sent to the MAC layer entity, and the data packets are sent to the base station after the type conversion, which causes the base station side to unpack the packet to generate the packet loss, and discards the data cached by the transmitting side of the RLC layer entity of the radio bearer.
  • the base station does not receive the data packets, the PDCP status report of the at least one radio bearer is sent to the terminal device, and the terminal device is instructed to resend the data packets to avoid packet discarding caused by the unpacking failure. Discarding these packets that may cause unpacking failures, avoiding wasted resources caused by invalid packets, and saving valuable air interface resources.
  • the downlink data received by the receiving side of the RLC layer entity includes Packets received before type conversion but not yet delivered to the upper layer entity (upper layer entity before type conversion), these packets have been sent successfully, in order to avoid wasting air interface resource retransmission, when the type conversion occurs, the data is Submitted to the upper entity before the type conversion, to ensure that the data packet can be properly unpacked, avoiding the unpacking failure caused by the upper entity submitted after the type conversion.
  • the method further includes:
  • the terminal device stops and resets all timers of the RLC layer entity of the at least one radio bearer
  • the terminal device resets all state variables of the RLC layer entity of the at least one radio bearer to an initial value.
  • the method further includes:
  • the PDCP layer entity of the at least one radio bearer does not send a successful PDCP protocol data unit, where the PDCP protocol data unit is submitted to the underlying entity before the at least one radio bearer type is converted, but the bottom layer The entity has not yet fed back the PDCP protocol data unit that has been successfully received; wherein the underlying entity is an underlying entity of the PDCP layer entity before the at least one radio bearer type is converted;
  • the method may further include: sending, by the terminal device, the PDCP status report of the at least one radio bearer to the base station, where the PDCP status report is used to notify the base station of the at least one radio bearer The serial number of the successfully received PDCP service data unit.
  • the terminal may determine, according to the indication of the base station, whether the PDCP status report needs to be sent for the at least one radio bearer. When the terminal receives the PDCP status report that the base station indicates that the at least one radio bearer needs to be sent, the terminal sends the PDCP status report.
  • the layer entity can process and send the uplink data that needs to be sent according to the type-converted encapsulation format.
  • the receiving side of the PDCP layer entity of the at least one radio bearer of the terminal device when the type of the at least one radio bearer of the terminal device is changed, the receiving side of the PDCP layer entity receives the type before the conversion.
  • the downstream packets submitted by the underlying entity, these packets have been sent successfully.
  • the data is delivered to the upper layer entity before the type conversion to ensure that the data packet can be correctly unpacked. , to avoid the unpacking failure caused by the upper entity submitted to the type conversion after the type conversion occurs.
  • the RLC acknowledge mode is adopted to adapt to the at least one radio bearer.
  • An application scenario for transmitting downlink data for an uplink PDCP PDU that is sent before the type conversion but has not received a successful reception acknowledgement, the PDCP entity needs to retransmit the data packet. Thereby it can be guaranteed that the data packet will not be lost.
  • At least one radio bearer is a format and content of a PDCP status report when a signaling radio bearer in an RLC AM mode is used, and when at least one radio bearer is a data radio bearer in an RLC AM mode.
  • the PDCP status report is different.
  • the PDCP status report in this application is the status report of the PDCP layer defined in the standard TS 36.323.
  • the format and content setting of the PDCP status report refer to TS 36.323.
  • SRB using the RLC AM mode See Figure 17 for the format of the PDCP status report.
  • the method further includes:
  • the terminal device resets the value of the variable of the sequence number of the next transmitted PDCP service data unit and the value of the superframe number to 0 by the PDCP entity of the at least one radio bearer;
  • the terminal device resets the value of the variable of the sequence number of the next received PDCP service data unit and the value of the superframe number to 0 by the PDCP entity of the at least one radio bearer.
  • the method further includes:
  • the PDCP entity that discards the at least one radio bearer receives all the PDCP PDUs that are received by the RLC layer entity due to the type conversion of the radio bearer, and discards all the stored PDCP SDUs and PDCP PDUs.
  • the method further includes:
  • the PDCP SDU and the PDCP PDU stored by the transmitting side of the PDCP layer entity of the at least one radio bearer are sent to the underlying entity according to the normal uplink data transmission process, that is, the radio bearer type.
  • the PDCP PDU refers to a PDCP PDU that is submitted by the underlying entity before the PDCP layer entity type conversion of the at least one radio bearer due to type conversion of the radio bearer.
  • the method further includes: for the MAC layer entity of the terminal device, the following data processing modes are:
  • the terminal device resets the medium access control MAC layer entity.
  • the processing of the MAC layer entity includes at least one of the following features: the terminal device clears a buffer of all uplink HARQ processes of the media access control MAC layer entity, and the terminal device adds all uplink HARQ processes.
  • the data indication information is set to 0, and the terminal device clears the buffer of all downlink HARQ processes of the media access control MAC layer entity, and the terminal device considers the subsequent received transport block as the transmission for each downlink HARQ process. The first transmission of the block.
  • the media access control MAC layer entity of the terminal device receives the MAC protocol data unit after the at least one radio bearer type is converted; if the initial reception of the MAC protocol data unit is in the at least one wireless Before the bearer type conversion, and the MAC protocol data unit includes the MAC service data unit of the at least one radio bearer, the MAC service data unit of the at least one radio bearer is discarded.
  • the uplink HARQ process on the transmitting side of the MAC layer entity includes at least one terminal device.
  • the MAC SDU corresponding to the logical channel of the radio bearer is a packet that has not been successfully transmitted, the data packet is sent to the base station after the type conversion, and the packet loss of the base station side is lost.
  • the base station By resetting the MAC layer entity, or clearing the buffer of the MAC layer entity sending side uplink HARQ process, on the one hand, if the base station does not receive the data packet, it also sends a PDCP status report of the at least one radio bearer to the terminal device, indicating The terminal device resends these data packets to avoid packet discarding caused by unpacking failure. On the other hand, discarding these data packets that may cause unpacking failure, avoiding waste of resources caused by transmitting invalid data packets, and saving valuable air interface resources. .
  • the MAC SDUs are delivered to the upper MAC entity, which causes the upper layer entity solution.
  • the packet fails to generate a packet loss, by resetting the MAC layer entity, or clearing the buffer of the downlink HARQ process on the receiving side of the MAC layer entity, or converting the type of the buffer of the downlink HARQ process on the receiving side of the MAC layer entity with at least one wireless
  • the MAC SDU corresponding to the logical channel of the bearer is discarded.
  • the terminal device if the terminal device does not receive the data packet, the terminal device sends a PDCP status report of the at least one radio bearer of the terminal device to the base station, instructing the base station to resend the data packet to avoid the terminal. Packet discarding caused by device unpacking failure. On the other hand, these may cause unpacking failure. Packets discarded, to avoid waste of resources invalid packet transmission caused, saves valuable air interface resources.
  • the type of the at least one radio bearer of the terminal device is converted from the first type to the second type, including being convertible from the type III radio bearer to the type I radio bearer, or from the first type
  • the type radio bearer is converted to a type III radio bearer.
  • the data radio bearer DRB of the terminal device can transmit data in the RLCUM mode, or can transmit data in the RLC AM mode, and the signaling radio bearer of the terminal device uses the RLC AM mode to transmit data. Therefore, in the foregoing first type of data processing method, the data processing methods in the following six application scenarios are mainly included, and the six application scenarios are:
  • Application Scenario 1 The data radio bearer transmitting data in the RLC UM mode is converted from the Type III radio bearer to the Type I radio bearer.
  • Application scenario 2 The data radio bearer transmitting data in the RLC AM mode is converted from the Type III radio bearer to the Type I radio bearer.
  • Application scenario 3 The signaling radio bearer transmitting data in the RLC AM mode is converted from the Type III radio bearer to the Type I radio bearer.
  • Application Scenario 4 The data radio bearer transmitting data in the RLC UM mode is converted from the Type I radio bearer to the Type III radio bearer.
  • Application Scenario 5 The data radio bearer transmitting data in the RLC AM mode is converted from the Type I radio bearer to the Type III radio bearer.
  • Application scenario 6 The signaling radio bearer transmitting data in the RLC AM mode is converted from the Type I radio bearer to the Type III radio bearer.
  • the terminal device receives the RRC connection reconfiguration message sent by the base station, and the indication information included in the RRC connection reconfiguration message indicates that the terminal device converts the type of the DRBi from the type III radio bearer to the type I radio bearer.
  • DRBi is a DRB that is converted from a Type III radio bearer to a Type I radio bearer by any one of the terminal devices.
  • the data processing method on the transmitting side includes:
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the DRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RLC layer entity of the DRBi to the initial value.
  • all uplink HARQ buffers are cleared, and all new data indicators (NDI) of the uplink HARQ process are set to zero.
  • NDI new data indicators
  • the second method is to reset the MAC, including all the operations that need to be performed when the MAC is reset. This operation is prior art and will not be repeated here.
  • the data processing method of the receiving side of the terminal device includes:
  • all the downlink HARQ buffers are cleared, and all the new data indicators (NDI) of the downlink HARQ process are set to 0, and the next received transport block is received for each downlink HARQ process.
  • the transmission of (TB, Transport Block) is considered as the first transmission of the transport block.
  • the second method is to reset the MAC, including all the operations that need to be performed when the MAC is reset. This operation is prior art and will not be repeated here.
  • the initial reception of the MAC PDU occurs before the DRBi type conversion, and the MAC SDU included in the MAC PDU includes the MAC SDU corresponding to the DRBi. Then, the MAC SDU of the DRBi in the MAC PDU is discarded, and the unpacking failure caused by the different packet formats of the MAC SDU of the DRBi before and after the type conversion is avoided.
  • the RLC PDUs of the DRBi received before the DRBi type conversion but not yet delivered to the PDCP layer entity included in the buffer of the receiving side are recomposed into the RLC SDU according to the packet format before the type conversion, and the data included in the RLC SDU is ordered. Submitted to the PDCP layer entity of DRBi.
  • the method may further include: stopping and resetting all timers of the RLC layer entity of the DRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RLC layer entity of the DRBi to an initial value.
  • the PDCP PDU that is received by the RLC layer entity of the DRBi due to the type conversion is processed and processed according to the processing after receiving the PDCP PDU from the RLC layer entity of the DRBi.
  • the terminal device receives the RRC connection reconfiguration message sent by the base station, and the indication information included in the RRC connection reconfiguration message indicates that the terminal device converts the type of the DRBi from the type III radio bearer to the type I radio bearer.
  • DRBi is a DRB that is converted from a Type III radio bearer to a Type I radio bearer by any one of the terminal devices.
  • the data processing method of the transmitting side of the terminal device includes:
  • the DRBi type is forwarded to the RLC layer entity of the DRBi, but the RLC layer entity of the DRBi has not confirmed that the PDCP PDU has been successfully transmitted for retransmission. According to the normal process after the type conversion, the DRBi needs to be retransmitted.
  • the PDCP PDU is sent to the protocol adaptation layer entity.
  • the PDCP PDU that needs to be retransmitted and submitted by the PDCP layer entity of the DRBi after the type conversion is sent to the RLC layer entity of the DRBi.
  • the data that needs to be retransmitted by the protocol adaptation layer entity is processed and sent to the MAC layer entity.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the DRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RLC layer entity of the DRBi to the initial value.
  • the data processing method of the receiving side of the terminal device includes:
  • the receiving side of the MAC layer entity corresponding to the logical channel of the DRBi is the same as the scenario 1, and is not described here.
  • the base station For the receiving side of the PDCP layer entity of the DRBi: optionally, determining the sequence number of the received downlink data (PDCP PDU), sending a PDCP status report to the base station through the PDCP layer entity, for notifying the downlink data packet that is not correctly received The serial number, so that the base station retransmits the unsuccessfully transmitted downlink data packets to the terminal device according to the PDCP status report.
  • the base station can configure whether the PDCP layer entity needs to send a PDCP status report.
  • the terminal device receives the RRC connection reconfiguration message sent by the base station, and the indication information included in the RRC connection reconfiguration message indicates that the terminal device converts the type of the SRBi from the type III radio bearer to the type I radio bearer.
  • the SRBi is an SRB that is converted from a Type III radio bearer to a Type I radio bearer by any one of the terminal devices.
  • the data processing method of the transmitting side of the terminal device includes:
  • the SRBi is forwarded to the RLC layer entity of the SRBi before the type conversion, but the RLC layer entity of the SRBi has not confirmed that the PDCP PDU has been successfully transmitted for retransmission. According to the normal flow after the type conversion, the SRBi needs to retransmit the PDCP PDU and send it to the protocol. Adaptation layer entity.
  • the method further includes: for the uplink data transmission, discarding all stored PDCP SDUs and PDCP PDUs on the transmitting side; and using the PDCP layer entity of the SRBi to record the value of the variable of the serial number of the next transmitted PDCP SDU and used for recording The value of the superframe number on the transmitting side that generated the COUNT value is reset to zero.
  • the method further includes: sending, to the uplink data transmission, the PDCP SDU and the PDCP PDU of the SRBi that have not been sent before the type conversion stored by the sending side, according to the normal uplink data sending process.
  • the protocol adapts the layer entity and resets the value of the variable of the PDCP layer entity of SRBi for recording the sequence number of the next transmitted PDCP SDU and the value of the superframe number used to record the COUNT value to 0.
  • the PDCP PDU that needs to be retransmitted by the PDCP layer entity of the SRBi after the type conversion is sent to the RLC layer entity of the SRBi.
  • the method further includes: transmitting, by the PDC layer entity, the PDCP SDU and the buffered PDCP PDU of the SRBi that have not been sent before the type conversion submitted by the PDCP layer entity to the RLC layer entity.
  • the data that needs to be retransmitted by the protocol adaptation layer entity is processed and sent to the MAC layer entity through the logical channel of the SRBi.
  • the method further includes: sending, according to the type conversion, the unsent data buffered before the type conversion submitted by the protocol adaptation layer to the MAC layer entity by using the logical channel of the SRBi.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the SRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RRC layer entity of the SRBi to initial value.
  • all uplink HARQ buffers are cleared, and all new data indicators (NDI) of the uplink HARQ process are set to zero.
  • NDI new data indicators
  • the second method is to reset the MAC, including all the operations that need to be performed when the MAC is reset. This operation is prior art and will not be repeated here.
  • the MAC SDU that needs to be retransmitted which is submitted by the RLC layer entity of the SRBi, is multiplexed into one transport block and then sent to the MAC layer entity of the base station.
  • the method further includes: sending, by the RLC layer entity of the SRBi, the data cached before the type conversion but not yet sent, to the MAC layer entity of the base station by using an air interface.
  • the data processing method of the receiving side of the terminal device includes:
  • all the downlink HARQ buffers are cleared, and all the new data indicators (NDI) of the downlink HARQ process are set to 0, and the next received transport block is received for each downlink HARQ process.
  • the transmission of (TB, Transport Block) is considered as the first transmission of the transport block.
  • the second method is to reset the MAC, including all the operations that need to be performed when the MAC is reset. This operation is prior art and will not be repeated here.
  • the initial reception of the MAC PDU occurs before the SRBi type conversion, and the MAC SDU included in the MAC PDU includes the MAC SDU corresponding to the SRBi. Then, the MAC SDU of the SRBi in the MAC PDU is discarded, and the unpacking failure caused by the different packet formats of the MAC SDU of the SRBi before and after the type conversion is avoided.
  • the RLC PDUs of the SRBi received before the SRBi type conversion but not yet delivered to the PDCP layer entity included in the buffer of the receiving side are recombined into the RLC SDU according to the packet format before the type conversion, and the data contained in the RLC SDU is ordered. Submitted to the PDCP layer entity of SRBi.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the SRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RRC layer entity of the SRBi to initial value.
  • the PDCP PDU that is received by the RLC layer entity of the SRBi due to the type conversion is processed and processed according to the processing after receiving the PDCP PDU from the RLC layer entity of the SRBi.
  • determining a sequence number of the received downlink data packet (PDCP PDU), and sending, by the PDCP layer entity, a PDCP status report to the base station, to notify the sequence number of the downlink data packet that is not correctly received, so that the base station according to the PDCP status
  • the report retransmits these unsuccessful downlink packets to the terminal device.
  • the base station can configure whether the PDCP layer entity needs to send a PDCP status report.
  • the method further includes: for downlink data transmission, discarding all downlink PDCP SDUs and PDCP PDUs buffered by the receiving side.
  • the value of the variable of the PDCP layer entity of SRBi for recording the sequence number of the next received PDCP SDU and the value of the superframe number for the receiving side for recording the COUNT value are reset to 0.
  • the method further includes: for downlink data transmission, submitting, by the received RLC layer entity, the PDCP PDU delivered by the SRBi type conversion to the RRC layer, and using the PDCP layer entity of the SRBi to record the next transmitted PDCP SDU.
  • the value of the variable of the serial number and the value of the superframe number used to record the receiving side generating the COUNT value are reset to zero.
  • the terminal device receives the RRC connection reconfiguration message, and the indication information included in the RRC connection reconfiguration message indicates that the terminal device converts the type of the DRBi from the Type I radio bearer to the Type III radio bearer.
  • the data processing method of the transmitting side of the terminal device includes:
  • the data processing method on the receiving side of the terminal device includes:
  • the RLC PDUs of the DRBi received before the DRBi type conversion but not yet delivered to the protocol adaptation layer entity included in the buffer of the receiving side are recombined into the RLC SDU according to the packet format before the type conversion, and the data included in the RLC SDU is used. Submitted to the protocol adaptation layer entity of DRBi in order.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the DRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RLC layer entity of the DRBi to the initial value.
  • the data part (ie, PDCP PDU) in the protocol adaptation layer PDU submitted by the RLC layer entity of the DRBi is sent to the terminal device, it is processed and delivered to the PDCP layer entity; if it is sent to the terminal device, For the remote terminal, the data part of the protocol adaptation layer PDU is discarded.
  • the PDCP PDU that is received by the protocol adaptation layer entity of the receiving DRBi is processed according to the processing process after receiving the PDCP PDU from the protocol adaptation layer entity.
  • the terminal device receives the RRC connection reconfiguration message, and the indication information included in the RRC connection reconfiguration message indicates that the terminal device converts the type of the DRBi from the Type I radio bearer to the Type III radio bearer.
  • the data processing method of the transmitting side of the terminal device includes:
  • the DRBi is forwarded to the protocol adaptation layer entity of the DRBi before the type conversion, but the protocol adaptation layer entity of the DRBi has not confirmed the PDCP PDU that has been successfully transmitted for retransmission, and the SRBi needs to retransmit the PDCP.
  • the PDU is sent to the RLC layer entity.
  • the RLC SDU and the RLC PDU that are currently buffered by the transmitting side are discarded.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the DRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RLC layer entity of the DRBi to the initial value.
  • the data to be retransmitted including DRBi after type conversion is multiplexed into one transport block and then sent to the MAC layer entity of the base station.
  • the other steps are the same as those in scenario 1, and are not described here.
  • the data processing method on the receiving side of the terminal device includes:
  • the specific content is the same as that of the scenario 4, and is not described here.
  • the specific content is the same as that of the scenario 4, and is not described here.
  • determining a sequence number of the received downlink data packet (PDCP PDU), and sending, by the PDCP layer entity, a PDCP status report to the base station, to notify the sequence number of the downlink data packet that is not correctly received, so that the base station according to the PDCP status
  • the report retransmits these unsuccessful downlink packets to the terminal device.
  • the base station can configure whether the PDCP layer entity needs to send a PDCP status report. The other steps are the same as those in scenario 4, and are not described here.
  • the data processing method for the application scenario 6 specifically includes the following steps:
  • the terminal device receives the RRC connection reconfiguration message, and the indication information included in the RRC connection reconfiguration message indicates that the terminal device converts the type of the DRBi from the Type I radio bearer to the Type III radio bearer.
  • the data processing method of the transmitting side of the terminal device includes:
  • the SRBi is forwarded to the protocol adaptation layer entity of SRBi before the type conversion, but the protocol adaptation layer entity of SRBi has not confirmed the PDCP PDU that has been successfully transmitted for retransmission, and SRBi needs to retransmit PDCP.
  • the PDU is sent to the RLC layer entity.
  • the method further includes: for uplink data transmission, discarding all stored PDCP SDUs and PDCP PDUs on the transmitting side;
  • the value of the variable of the PDCP layer entity of SRBi for recording the sequence number of the next transmitted PDCP SDU and the value of the superframe number for recording the COUNT value are reset to zero.
  • the method further includes: sending, after the type conversion, the PDCP SDU and the PDCP PDU of the pre-type SRBi stored on the transmitting side to the RLC layer entity according to the normal uplink data sending process, and The value of the variable of the PDCP layer entity of SRBi for recording the sequence number of the next transmitted PDCP SDU and the value of the superframe number for recording the COUNT value are reset to zero.
  • the RLC SDU and the RLC PDU that are currently buffered by the transmitting side are discarded.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the SRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RRC layer entity of the SRBi to initial value.
  • the method further includes: sending, according to the type conversion, the normal uplink sending process, the RLC SDU and the buffer RLC PDU of the SRBi that have not been sent in the pre-conversion buffer delivered by the PDCP layer entity are sent to the MAC layer entity through the logical channel of the SRBi .
  • the MAC PDU of the MAC SDU that needs to be retransmitted after the type conversion is multiplexed into one transport block and then sent to the MAC layer entity of the base station.
  • the method further includes: sending, according to the type-converted uplink data, the MAC SDU and the MAC PDU that have not been sent in the pre-conversion buffer of the SRBi logical channel are sent to the MAC layer entity of the base station through the air interface.
  • the other steps are the same as those in scenario 1, and are not described here.
  • the data processing method of the receiving side of the terminal device includes:
  • the RLC PDU of the SRBi received before the SRBi type conversion but not yet delivered to the protocol adaptation layer entity included in the buffer of the receiving side is recombined into the RLC SDU according to the packet format before the type conversion, and the data included in the RLC SDU is used.
  • the protocol adaptation layer entity is delivered to SRBi in order.
  • the method further includes: stopping and resetting all timers of the RLC layer entity of the SRBi, including a reordering timer for detecting the lost RLC PDU; and resetting all state variables of the RRC layer entity of the SRBi to initial value.
  • the RLC layer entity receiving the SRBi is processed as a PDCP PDU by the protocol adaptation layer PDU submitted by the type conversion, and is delivered to the PDCP layer entity of the SRBi.
  • the PDCP PDU that the protocol adaptation layer entity of the SRBi receives due to the type conversion is received, and is processed according to the processing after receiving the PDCP PDU from the protocol adaptation layer entity of the SRBi.
  • Other alternative embodiments are the same as scenario 3, this It is no longer exhaustive.
  • the uplink data transmission process of the at least one data radio bearer of the terminal device is as shown in FIG. 5, the transmitting side and the protocol adaptation layer of the PDCP layer entity of the DRBi.
  • the transmitting side of the entity, the transmitting side of the RLC layer entity, and the transmitting side of the MAC layer entity sequentially send uplink data according to the process of transmitting the uplink data after the type conversion.
  • the MAC layer entity, the RLC layer entity, the protocol adaptation layer entity, and the PDCP layer entity of the base station side corresponding to the DRBi receive the uplink data according to the process of receiving the uplink data after the type conversion.
  • the downlink data transmission process of the at least one data radio bearer of the terminal device is as shown in FIG. 6.
  • the receiving side and the protocol adaptation layer of the PDCP layer entity of the DRBi The receiving side of the entity, the receiving side of the RLC layer entity, and the receiving side of the MAC layer entity sequentially receive the downlink data according to the process of receiving the downlink data after the type conversion.
  • the MAC layer entity, the RLC layer entity, the protocol adaptation layer entity, and the PDCP layer entity on the base station side corresponding to the DRBi sequentially transmit the downlink data according to the process of transmitting the downlink data after the type conversion.
  • the uplink data transmission process of at least one data radio bearer of the terminal device is as shown in FIG. 7, the transmitting side of the PDCP layer entity of the DRBi, and the transmitting side of the RLC layer entity.
  • the sending side of the MAC layer entity sends the uplink data in sequence according to the process of transmitting the uplink data after the type conversion.
  • the MAC layer entity, the RLC layer entity, and the PDCP layer entity on the base station side corresponding to the DRBi receive the uplink data in sequence according to the process of receiving the uplink data after the type conversion.
  • the downlink data transmission process of the at least one data radio bearer of the terminal device is as shown in FIG. 8, and the receiving side of the PDCP layer entity of the DRBi receives the RLC layer entity.
  • the receiving side of the side and the MAC layer entity sequentially receives the downlink data according to the process of receiving the downlink data after the type conversion.
  • the MAC layer entity, the RLC layer entity, and the PDCP layer entity on the base station side corresponding to the DRBi sequentially transmit the downlink data according to the process of transmitting the downlink data after the type conversion.
  • the method further includes: determining, by the base station, the sequence number of the received uplink data packet, and sending, by the PDCP layer entity, the PDCP status report to the terminal device, to notify the uplink data packet of the DRBi that is not correctly received.
  • the serial number the terminal device resends the data packets to the base station according to the PDCP status report.
  • the base station can configure whether the PDCP layer entity needs to send a PDCP status report.
  • the method further includes: determining, by the base station, the sequence number of the uplink data packet of the SRBi that is not received, and sending, by the PDCP layer entity, the PDCP status report to the terminal device, to notify the uplink data of the SRBi that is not correctly received.
  • the sequence number of the packet, and the terminal device resends the data packets of the SRBi to the base station according to the PDCP status report.
  • the format and content of the PDCP status report of SRBi are different from the PDCP status report of DRBi.
  • the present invention provides a data processing method as shown in FIG. 9 to solve the technical problem of how to avoid packet loss when a type of radio bearer of a terminal device undergoes a transition between Type I and Type III.
  • Step S1 The first device determines that the type of the at least one radio bearer of the first device is converted from the first type to the second type.
  • Step S2 The first device receives the first indication information that is sent by the second device, where the first indication information is used to indicate that the radio bearer type of the data of the at least one radio bearer received by the first device is a type of radio bearer or a second type of radio bearer;
  • the first device is a terminal device, and the second device is a base station; or the first device is a base station.
  • the second device is a terminal device.
  • the first indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • step S2 the method further includes:
  • the radio bearer type of the received RLC protocol data unit of the at least one radio bearer according to the first indication information and the received sequence number of the RLC protocol data unit of the at least one radio bearer a first type of radio bearer or a second type of radio bearer;
  • the acquiring, by the first device, the first indication information includes:
  • the first device receives an RRC connection reconfiguration message of the at least one radio bearer sent by the second device, where the RRC connection reconfiguration message includes the first indication information or
  • the RLC control protocol data unit includes the first indication information.
  • the acquiring, by the first device, the first indication information includes:
  • MAC protocol data unit that is sent by the second device, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, where the MAC service data unit corresponds to a MAC subheader.
  • it also includes:
  • the first device sends the second indication information to the second device, where the second indication information is used to notify the second device that the radio bearer type of the data of the at least one radio bearer is the first type. Radio bearer or second type radio bearer.
  • the second indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the first device sends the second indication information to the second device, including:
  • the first device sends an RRC connection reconfiguration complete message of the at least one radio bearer to the second device, where the RRC connection reconfiguration complete message includes the second indication information;
  • the second indication information is included in the RLC control protocol data unit.
  • the first device sends the second indication information to the second device, where the first device sends a MAC protocol to the second device.
  • the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, and the second sub-header corresponding to the MAC service data unit carries the second indication information.
  • the present application provides a data processing method on a terminal device side, including:
  • the terminal device determines that the type of the at least one radio bearer of the terminal device is converted from the first type to the second type;
  • the terminal device acquires first indication information, where the first indication information is used to indicate that after the at least one radio bearer type is switched, the radio bearer type of the data of the at least one radio bearer received by the terminal device is a first type of radio bearer or a second type of radio bearer;
  • the method further includes:
  • the terminal device Receiving, by the terminal device, the RLC protocol data unit of the at least one radio bearer; the terminal device determining, according to the first indication information and a sequence number of an RLC protocol data unit of the at least one radio bearer, the at least one radio The upper entity of the RLC protocol data unit that is carried.
  • the type of the at least one radio bearer of the terminal device is changed from the first type to the second type, and may be converted from the type III radio bearer to the type I radio bearer, or may be converted from the type I radio bearer to the third type. Wireless bearer.
  • the first indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the terminal device determines the RLC protocol data of the at least one radio bearer according to the first indication information and the sequence number of the RLC protocol data unit of the at least one radio bearer.
  • the upper entity of the unit including:
  • the radio bearer type of the received RLC protocol data unit of the at least one radio bearer according to the first indication information and the received sequence number of the RLC protocol data unit of the at least one radio bearer Type radio bearer or second type radio bearer;
  • the terminal device acquires the first indication information, including:
  • the terminal device receives an RRC connection reconfiguration message of the at least one radio bearer sent by the base station, where the RRC connection reconfiguration message includes the first indication information.
  • the received data packet from the radio bearer needs to be submitted to the PDCP after being processed by the RLC layer.
  • the layer is still submitted to the Adaptation layer layer, and the base station notifies the eRelay UE of the sequence number of one RLC PDU of the type-transformed radio bearer in the RRC Connection Reconfiguration message, and the RLC PDU is included in the content according to the type conversion.
  • Package format encapsulation of RLC SDU The serial number corresponding to an RLC PDU.
  • the RLC PDU is a sequence number corresponding to the last RLC PDU of the RLC SDU encapsulated according to the corresponding packet format before the type conversion.
  • the format of the RLC SDU of the Type III radio bearer is as shown in FIG. 3(d), and the format of the RLC SDU of the Type I radio bearer is as shown in FIG. 3(e) is shown.
  • the following takes an example of the transmission of downlink data from a Type III radio bearer to a Type I radio bearer as a radio bearer, and specifically describes how the above method is implemented:
  • the base station notifies the eRelay UE to transmit the RLC sequence number of the RLC PDU on the radio bearer in which the type conversion occurs, and the RLC sequence number refers to the first one including the RLC SDU as shown in FIG. 3(e).
  • the sequence number corresponding to the RLC PDUs; or the RLC sequence number refers to the sequence number corresponding to the last RLC PDU including the RLC SDU as shown in FIG. 3(d).
  • the eRelay UE After the eRelay UE receives the RLC PDU from the radio bearer, the eRelay UE determines, according to the sequence number included in the RLC PDU, that the received RLC PDU needs to be submitted to the radio bearer after the type conversion is performed.
  • the PDCP layer entity is also submitted to the protocol adaptation layer entity.
  • the RLC sequence number in the first indication information is a sequence number corresponding to the first RLC PDU of the RLC SDU of the DRB as shown in FIG. 3(e), for example, the RLC sequence number is 99. If the sequence number of the RLC PDU received from the DRB is 100, the eRelay UE determines that the received RLC PDU needs to be submitted to the protocol adaptation layer entity, PDCP, after being processed by the RLC layer entity. Layer entity. If the sequence number of the RLC PDU received from the DRB is 98, the eRelay UE determines that the received RLC PDU needs to be delivered to the PDCP layer entity after being processed by the RLC layer entity.
  • the operation for downlink data transmission is the same as above.
  • the eRelay UE needs to continue to use the upper layer entity of the RLC layer entity after the type conversion of the radio bearer. time. After determining that the base station side buffers all data packets before the type conversion, the eRelay UE may choose to release the Adaptation layer.
  • the base station and the eRelay UE side can no longer receive the RLC received before the type conversion of the current RLC layer cache.
  • SDU performs cascading and split operations.
  • the terminal device acquires the first indication information, including:
  • the RLC control protocol data unit includes the first indication information.
  • a new RLC Control PDU is newly defined.
  • the RLC control PDU is used to notify the foregoing RLC sequence number included in the first indication information, where the RLC sequence number is a sequence number of an RLC PDU of at least one radio bearer of the terminal device, and the RLC PDU is included according to a type conversion.
  • the RLC PDU is a sequence number corresponding to the last RLC PDU of the RLC SDU encapsulated according to the corresponding packet format before the type conversion.
  • the base station sends the corresponding RLC control PDU of the radio bearer on the radio bearer of the type-converted type. Therefore, after the terminal device receives the RLC control PDU on the radio bearer, it can learn which part of the data included in the RLC PDU transmitted on the radio bearer, which needs to be submitted to the PDCP layer, and which need to be submitted to the Adaptation layer. Floor.
  • the base station side sends, by using an RLC layer entity of the radio bearer, first indication information that includes the foregoing RLC control PDU, where the terminal device side receives, by the RLC layer entity of the radio bearer, the base station sends the foregoing The RLC controls the first indication information of the PDU.
  • three formats of the RLC control PDU are respectively corresponding to the length of the RLC SN of 5 bits, 10 bits, and 16 bits.
  • the meanings of the fields included in the format of the RLC Control PDU are as follows:
  • the D/C field occupies 1 bit and is used to indicate whether the RLC PDU including the RLC sequence number is an RLC data PDU or an RLC control PDU.
  • the CPT field occupies 3 bits and is used to indicate the type of the control PDU (control PDU type). If it is an RLC control PDU, it is used to indicate the type of the control PDU.
  • the values of this field are currently defined as shown in Table 1. For the newly defined control PDU, it is necessary to use the current reserved value to indicate only its type. For example, the newly defined control PDU can be represented by 001.
  • R is a reserved bit.
  • SN is the sequence number of the RLC PDU, and may be a sequence number corresponding to the first RLC PDU of the RLC SDU encapsulated by the corresponding packet format corresponding to the type conversion, or may include the RLC encapsulated according to the corresponding packet format before the type conversion.
  • a timing of generating the control PDU is: when the RLC layer entity of the base station transmits the RLC PDU of the RLC SDU received from the upper layer entity before the last type conversion; or the base station The RLC layer entity generates the RLC control PDU after determining the sequence number of the RLC PDU of the RLC SDU received from the upper layer entity before the last type conversion.
  • the RLC layer entity of the base station transmits the RLC PDU of the RLC SDU received from the upper layer entity after the first type conversion, or the RLC layer entity of the base station determines to receive the first type conversion and receives the content from the upper layer entity
  • the RLC Control PDU is generated after the sequence number of the RLC PDU of the RLC SDU.
  • the RLC layer entity of the terminal device delivers the RLC SDUs that are assembled by one RLC PDU in order, after receiving the RLC control PDU sent by the base station.
  • the corresponding upper entity that is, the PDCP layer entity or the Adaptation layer entity.
  • the terminal device receives a MAC protocol data unit sent by the base station, where the MAC protocol data unit includes MAC service data of the at least one radio bearer. And the unit, the MAC sub-head corresponding to the MAC service data unit carries the first indication information.
  • the terminal device determines, according to the indication information in the MAC sub-head corresponding to the MAC service data unit, the RLC protocol data unit of the at least one radio bearer.
  • the upper entity when the first indication information does not include the RLC sequence number, the terminal device determines, according to the indication information in the MAC sub-head corresponding to the MAC service data unit, the RLC protocol data unit of the at least one radio bearer. The upper entity.
  • the indication information in the MAC sub-header includes: when the indication value is 0, it indicates that the data included in the MAC SDU should be sent to the PDCP layer entity after being processed by the RLC layer entity. When the indication value is 1, it indicates that the data contained in the MAC SDU should be sent to the protocol adaptation layer entity after being processed by the RLC layer entity. Or vice versa.
  • the above notification is implemented through the MAC layer.
  • a MAC PDU may contain multiple MAC SDUs, each of which is from a logical channel of a radio bearer. Each MAC SDU has a corresponding MAC header (Subheader).
  • the MAC subheader of a MAC SDU includes a Logical Channel ID (LCID) and a Reserved Bit (R bit) field, and includes other fields.
  • LCID Logical Channel ID
  • R bit Reserved Bit
  • the LCID field of the MAC subheader of one MAC SDU is used to indicate which radio bearer logical channel the MAC SDU is from. In this way, according to the LCID, the receiving device can know which RLC entity the MAC SDU corresponding to the logical channel should be delivered to.
  • bit value of the R field in the MAC subheader of a MAC SDU when the bit value of the R field in the MAC subheader of a MAC SDU is 0, it indicates that the data included in the MAC SDU should be sent to the PDCP layer entity after being processed by the RLC layer entity, and the bit value of the R field is At 1 o'clock, it indicates that the data contained in the MAC SDU should be sent to the protocol adaptation layer entity after being processed by the RLC layer entity. Or vice versa.
  • the uplink data transmission or the downlink data transmission is performed, for the transmitting end device, when a radio bearer is converted, when the RLC layer entity corresponding to the radio bearer starts to transmit the RLC SDU including the packet format encapsulation according to the type conversion
  • the RLC entity simultaneously notifies the MAC layer by an indication that the RLC PDU contains the RLC SDU encapsulated according to the type-converted packet format.
  • the RLC entity simultaneously passes the RLC PDU to the MAC layer entity.
  • the indication informs the MAC layer that the RLC PDU contains the RLC SDU encapsulated according to the packet format before the type conversion. Whether the uplink data transmission or the downlink data transmission is performed, for the receiving end device, after the MAC layer entity receives a MAC PDU, it is determined whether the each MAC SDU is from the LCID in the subheader corresponding to each MAC SDU. A radio bearer that undergoes type conversion. If yes, the packet format of the RLC packet included in the MAC SDU is determined according to the value of the Rbit in the subheader. And when the MAC SDU is submitted to the RLC layer, the packet format of the RLC data packet of the RLC layer entity is simultaneously notified. Based on the result of the MAC layer entity notification, the RLC layer entity knows whether to submit the data part contained in the RLC data packet to the PDCP layer entity or to the protocol adaptation layer entity.
  • the method of the foregoing method is that the base station sends the first indication information to the terminal device, to indicate that after the at least one radio bearer type is switched, the radio bearer type of the data of the at least one radio bearer received by the terminal device is the first type. Radio bearer or second type radio bearer.
  • the received data packet from the radio bearer needs to be submitted to the PDCP layer after being processed by the RLC layer or submitted to the Adaptation layer layer, eRelay UE.
  • a notification needs to be sent to the base station.
  • the data processing method on the terminal device side further includes:
  • the terminal device Transmitting, by the terminal device, second indication information to the base station, where the second indication information is used to notify, after the at least one radio bearer type is switched, the wireless data of the at least one radio bearer received by the base station Host class
  • the type is a first type of radio bearer or a second type of radio bearer.
  • the second indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the terminal device sends an RRC connection reconfiguration complete message of the at least one radio bearer to the base station, where the RRC connection reconfiguration complete message includes the Two instructions.
  • the terminal notifies the base station of the RLC sequence number corresponding to one RLC PDU transmitted on the radio bearer that generates the type conversion by using an RRC Connection Reconfiguration Complete message, where the RLC PDU includes a packet corresponding to the type conversion.
  • the sequence number corresponding to the first RLC PDU of the format encapsulated RLC SDU; or the RLC PDU includes the sequence number corresponding to the last RLC PDU of the RLC SDU encapsulated according to the corresponding packet format before the type conversion.
  • the eRelay UE notifies the base station of the corresponding RLC sequence number by using the RRC connection reconfiguration complete message, and the base station uses the RRC connection reconfiguration message to notify the eRelay UE of the corresponding RLC sequence number in a similar manner. Repeatedly.
  • the base station and the eRelay UE side can no longer receive the current RLC layer buffer before the type conversion.
  • the RLC SDU performs cascading and split operations.
  • the terminal device sends the RLC control protocol data unit of the at least one radio bearer to the base station, where the RLC control protocol data unit includes the second indication information.
  • the RLC control protocol data unit is generated after the RLC layer entity of the at least one radio bearer of the first user equipment determines the sequence number of the last RLC PDU processed before the type conversion.
  • the terminal device sends the first indication information that includes the foregoing RLC control PDU to the base station by using the RLC layer entity of the radio bearer, and the base station receives, by using the RLC layer entity of the radio bearer, the RLC that is sent by the terminal device and includes the foregoing RLC. Control first indication information of the PDU.
  • the terminal device For the uplink data transmission, the terminal device notifies the RLC sequence number in the first indication information by using the RLC control PDU, which is similar to the manner in which the base station notifies the terminal of the RLC serial number in the first indication information in the foregoing embodiment, and is no longer Repeated.
  • the base station can learn the packet format of the RLC data packet according to the RLC sequence number indicated by the RLC control PDU, and deliver the RLC SDU obtained by assembling one RLC PDU to the PDCP layer entity in order, or submit the protocol to the protocol. Layer entity.
  • a timing of generating the control PDU is: when the RLC layer entity of the terminal device transmits the RLC PDU of the RLC SDU received from the upper layer entity before the last type conversion; or the terminal The RLC control PDU is generated after the RLC layer entity of the device determines the sequence number of the RLC PDU of the RLC SDU received from the upper layer entity before the last type conversion. Or, when the RLC layer entity of the terminal device transmits the RLC PDU of the RLC SDU received from the upper layer entity after the first type conversion, or the RLC layer entity of the terminal device determines to include the first type conversion from the upper layer entity After receiving the sequence number of the RLC PDU of the RLC SDU, the RLC control PDU is generated.
  • the RLC layer of the base station is directly After receiving the RLC control PDU sent by the terminal device, the RLC SDUs that are assembled by one RLC PDU are delivered to the corresponding upper layer entity, that is, the PDCP layer entity or the Adaptation layer entity.
  • the terminal device sends a MAC protocol data unit to the base station, where the MAC protocol data unit includes the at least a radio bearer MAC service data unit, where the MAC sub-head corresponding to the MAC service data unit carries the second indication information.
  • the MAC protocol data unit includes the at least a radio bearer MAC service data unit, where the MAC sub-head corresponding to the MAC service data unit carries the second indication information.
  • the present application further provides a data processing method on the base station side to solve the technical problem of how to avoid packet loss when a type of radio bearer of a terminal device undergoes a transition between Type I and Type III. .
  • the data processing method on the base station side provided by the application includes:
  • the type of the at least one radio bearer of the base station configuring the terminal device is converted from the first type to the second type;
  • the base station When performing the downlink data transmission, the base station sends the first indication information to the terminal device, where the first indication information is used to indicate that the terminal device receives the at least one radio bearer type after the terminal device is converted.
  • the radio bearer type of the data of the at least one radio bearer is a first type radio bearer or a second type radio bearer.
  • the first indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the base station sends an RRC connection reconfiguration message of the at least one radio bearer to the terminal device, where the RRC connection reconfiguration message includes the first indication information;
  • the base station sends the RLC control protocol data unit of the at least one radio bearer to the terminal device, where the RLC control protocol data unit includes the first indication information.
  • the base station sends a MAC protocol data unit to the terminal device, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, where the MAC service data unit corresponds to a MAC subheader.
  • the first indication information is not limited to whether the MAC protocol data unit is included in the terminal device.
  • it also includes:
  • the radio bearer type is a first type radio bearer or a second type radio bearer.
  • the method further includes:
  • an RLC protocol data unit of the at least one radio bearer Receiving, by the base station, an RLC protocol data unit of the at least one radio bearer; the base station determining, according to the first indication information and a sequence number of an RLC protocol data unit of the at least one radio bearer, the at least one radio bearer The upper entity of the RLC protocol data unit.
  • the second indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the base station is configured according to the first indication information and the at least a sequence number of a radio bearer RLC protocol data unit, determining an upper layer entity of the RLC protocol data unit of the at least one radio bearer, specifically:
  • the base station Determining, by the base station, the radio bearer type of the received RLC protocol data unit of the at least one radio bearer according to the first indication information and the received sequence number of the RLC protocol data unit of the at least one radio bearer a radio bearer or a second type of radio bearer;
  • the base station determining, by the base station, whether the upper layer entity of the received RLC protocol data unit of the at least one radio bearer is a PDCP layer entity or a protocol adaptation layer entity, according to the received radio bearer type of the RLC protocol data unit of the at least one radio bearer.
  • the eNB receives the RRC connection reconfiguration complete message of the at least one radio bearer sent by the terminal device, where the RRC connection reconfiguration complete message includes the second indication information;
  • the base station receives an RLC control protocol data unit of the at least one radio bearer sent by the terminal device, where the RLC control protocol data unit includes the second indication information.
  • the base station receives an RRC connection reconfiguration complete message of the at least one radio bearer sent by the terminal device, where the second indication information is included in the RRC connection reconfiguration complete message.
  • the base station receives the sent MAC protocol data unit sent by the terminal device, where the MAC protocol data unit includes the MAC service data unit of the at least one radio bearer.
  • the second sub-header corresponding to the MAC service data unit includes the second indication information.
  • the base station determines an upper layer entity of the RLC protocol data unit of the at least one radio bearer according to the indication information in the MAC sub-head corresponding to the MAC service data unit.
  • the indication information in the MAC sub-header includes: when the indication value is 0, indicating that the data included in the MAC SDU should be sent to the PDCP layer entity after the RLC layer entity processing, and the indication value is 1, indicating that the MAC SDU is in the MAC SDU.
  • the included data should be sent to the protocol adaptation layer entity after processing by the RLC layer entity. Or vice versa.
  • the data processing method on the base station side is the same as the data processing method on the terminal side, and will not be described in detail herein.
  • the present application further provides a third data processing method for implementing how to notify the terminal device that the type of at least one radio bearer is converted from the first type radio bearer to the second type radio bearer.
  • the third data processing method on the terminal side provided by the application mainly includes:
  • the terminal device receives the first configuration information that is sent by the base station, where the first configuration information is used to configure the at least one radio bearer of the terminal device to be converted into the second type radio bearer by the first type of radio bearer;
  • the terminal device determines, according to the first configuration information, that the type of the at least one radio bearer is converted from the first type of radio bearer to the second type of radio bearer, including:
  • the terminal device Determining, by the terminal device, that the at least one radio bearer is a currently configured radio bearer according to the identifier of the at least one radio bearer carried in the first configuration information, and determining that the type of the at least one radio bearer is first Type radio bearer,
  • the first configuration information includes the third indication information, determining that the type of the at least one radio bearer is converted by the first type of radio bearer to the second type of radio bearer;
  • the first type of radio bearer includes: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity, and a logical channel;
  • the second type radio bearer includes: a PDCP layer entity, the adaptation protocol a layer entity, an RLC layer entity and a logical channel;
  • the third indication information is used to indicate that the type of the radio bearer configured by the terminal device is the second type of radio bearer.
  • the terminal device may determine, according to the first configuration information, that at least one radio bearer of the terminal device is converted into a Type I radio bearer by the Type III radio bearer.
  • the terminal device determines, according to the first configuration information, that the type of the at least one radio bearer is converted from the first type of radio bearer to the second type of radio bearer, including:
  • the terminal device Determining, by the terminal device, that the at least one radio bearer is a currently configured radio bearer according to the identifier of the at least one radio bearer carried in the first configuration information, and determining that the type of the at least one radio bearer is first Type radio bearer,
  • the fourth configuration information is not included in the first configuration information, determining that the type of the at least one radio bearer is converted by the first type radio bearer to the second type radio bearer;
  • the first type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel;
  • the second type of radio bearer includes: a packet data convergence protocol PDCP layer entity, and a radio link
  • the control protocol RLC layer entity and the logical channel, the fourth indication information is used to indicate that the type of the radio bearer configured by the terminal device is the first type of radio bearer.
  • the terminal device may determine, according to the first configuration information, that at least one radio bearer of the terminal device is converted into a Type III radio bearer by the Type I radio bearer.
  • the first configuration information is included in an RRC connection reconfiguration message.
  • the third data processing method on the base station side provided by the application mainly includes:
  • the base station sends the first configuration information to the terminal device, where the first configuration information is used to configure to convert the type of the at least one radio bearer of the terminal device from the first type of radio bearer to the second type of radio bearer, where
  • the first configuration information includes at least the identifier of the at least one radio bearer.
  • the at least one radio bearer of the terminal device is configured to be converted into a Type I radio bearer by the Type III radio bearer, that is, if the first type of radio bearer comprises: a packet data convergence protocol PDCP layer. Entity, a radio link control protocol, an RLC layer entity, and a logical channel; the second type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel; and the first configuration information includes The identifier of the at least one radio bearer further includes third indication information, where the third indication information is used to indicate that the type of the radio bearer configured by the terminal device is the second type radio bearer.
  • the first type of radio bearer comprises: a packet data convergence protocol PDCP layer. Entity, a radio link control protocol, an RLC layer entity, and a logical channel
  • the second type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel
  • the first configuration information is included in an RRC connection reconfiguration message.
  • the at least one radio bearer of the terminal device in order to configure the at least one radio bearer of the terminal device to be converted into a type III radio bearer by the type I radio bearer, that is, if the first type radio bearer comprises: a PDCP layer entity, Adapting a protocol layer entity, an RLC layer entity and a logical channel; the second type of radio bearer comprises: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity and a logical channel;
  • the first configuration information includes an identifier of the at least one radio bearer, but does not include fourth indication information, where the fourth indication information is used to indicate that the type of the radio bearer configured by the terminal device is the first type. Wireless bearer.
  • the first configuration information is included in an RRC connection reconfiguration message.
  • the eRelay UE When the base station newly configures a radio bearer for the eRelay UE, the eRelay UE needs to know the type of the radio bearer. When the base station reconfigures a radio bearer for the eRelay UE, the eRelay UE needs to know that the radio bearer is maintained. The type is unchanged, reconfiguring its related parameters or changing the type of radio bearer by reconfiguration. Currently, the data radio bearer and the signaling radio bearer are added and modified, which are respectively implemented by including the SRB-To AddMod information and the DRB-To Add Mod information in the RRC connection reconfiguration message.
  • the indication information may be configured based on the SRB-To AddMod information and the DRB-To Add Mod information to indicate that the currently configured SRB or SRB is converted from the Type III radio bearer to the Type I radio bearer, and indicates the currently configured SRB. Or SRB is converted from a Type I radio bearer to a Type III radio bearer.
  • the indication information A is added to the information included in the SRB-ToAddMod and the DRB-ToAddMod, indicating that the configured radio bearer is a Type I radio bearer other than the Type III radio bearer.
  • an indication information B is added to the indication information A to indicate the conversion of the radio bearer type.
  • the radio bearer indicated by the DRB-ToAddMod to indicate that the increase should be the EPS Bearer ID is not a Type II radio bearer.
  • the addition, reconfiguration, and type conversion indications for one radio bearer of the eRelay UE are as follows:
  • Step 1 When the eRelay UE receives the RRC connection reconfiguration message including the DRB-ToAddMod sent by the base station, for a DRB ID included in the DRB-ToAddMod:
  • the DRB is not the DRB currently configured by the eRelay UE, then the situation corresponds to the case where a new DRB is newly added, and the process proceeds to step 2;
  • step 3 If the DRB is the DRB currently configured by the eRelay UE, go to step 3:
  • Step 2 In the case that it is determined that a new DRB is added, if the EPS bearer ID is included in the DRB-ToAddMod, but the indication information A is not included, the situation corresponds to newly adding a DRB of the third type;
  • the situation corresponds to newly adding a DRB of the first type
  • Step 3 In the case that it is determined that the DRB is a DRB currently configured by the eRelay UE, either reconfigure the DRB or perform type conversion on the DRB;
  • the situation corresponds to reconfiguring the DRB;
  • the DRB is a Type III DRB
  • the DRB-ToAddMod includes the indication information A
  • the case corresponds to converting the DRB from the Type III DR to the Type I DRB
  • the DRB is a Type II DRB
  • the indication information A is included in the DRB-ToAddMod, but the indication information A is not included in the indication information A, the situation corresponds to a reconfiguration Said DRB;
  • the DRB is a Type II DRB
  • the indication information A is included in the DRB-ToAddMod
  • the indication information A includes the indication information B
  • the situation corresponds to the DRB. Convert from Type II DRB to Type I DRB;
  • the DRB is a Type 1 DRB
  • the indication information A is included in the DRB-ToAddMod, but the indication information A is not included in the indication information A, the situation corresponds to a reconfiguration Said DRB;
  • the DRB-ToAddMod includes the finger
  • the information A is displayed, and the indication information A includes the indication information B, and the situation corresponds to converting the DRB from the type I DRB to the second type DRB;
  • the DRB is a Type 1 DRB
  • the indication information A is not included in the DRB-ToAddMod
  • the case corresponds to converting the DRB from the Type I DRB to the Type III DRB.
  • the SRB has only Type I and Type III. Therefore, the configuration of SRB addition, reconfiguration, and type conversion is the same as above, except that all configurations related to Type II radio bearers are not involved.
  • the embodiment of the present application further provides a base station and a terminal device, which are used to solve the problem in the prior art when a type of a radio bearer is converted between a type I and a type III.
  • the problem of technical problems with packet loss may be referred to each other, and the repeated description is not repeated.
  • the terminal device 1000 includes a processor 1001 and a transceiver 1004, where:
  • the transceiver 1004 is configured to support communication between the terminal and the base station, and send information or instructions involved in the method for resource allocation in the communication system to the base station.
  • the processor 1001 is configured to support the terminal to perform a corresponding function in the above data processing method.
  • a memory 1002 and a communication interface 1003 are further included; wherein the processor 1001, the memory 1002, the communication interface 1003, and the transceiver 1004 are connected to each other through a bus 1005.
  • the memory is for coupling with a processor that stores program instructions and data necessary for the terminal.
  • the processor 1001 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 1002 includes a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory.
  • RAM random-access memory
  • the memory may also include a non-volatile memory such as a flash memory.
  • a hard disk drive (HDD) or a solid-state drive (SSD); the memory may also include a combination of the above types of memories.
  • the communication interface 1003 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a WLAN interface.
  • the transceiver 1004 can be a wired transceiver, a wireless transceiver, or a combination thereof.
  • the wired transceiver can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless transceiver can be, for example, a wireless local area network communication interface, a cellular network communication interface, or a combination thereof.
  • the bus 1005 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
  • Bus 1005 can include any number of interconnected buses and bridges, specifically linked by various circuits of one or more processors 1001 represented by the processor and memory represented by memory 1002.
  • the bus can also link various other circuits such as peripherals, voltage regulators, and power management circuits. Together, this application will not further describe it.
  • Transceiver 1004 provides means for communicating with various other devices on a transmission medium.
  • the processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1002 can store data used by the processor 1001 in performing operations.
  • the processor 1001 and the transceiver 1004 of the present application can perform the steps related to the terminal device in the first data processing method of the present application, and can also perform the steps related to the terminal device in the second data processing method of the present application.
  • the method specifically includes:
  • the processor 1001 is configured to determine that the type of the at least one radio bearer of the terminal device is converted from the first type to the second type, and the RLC protocol of the radio link control protocol RLC layer entity that sends the at least one radio bearer a data unit and/or an RLC service data unit; assembling the RLC protocol data unit received by the RLC layer entity receiving side of the at least one radio bearer into an RLC service data unit, and delivering the RLC service data unit in order to An upper layer entity of the RLC layer entity; wherein the upper layer entity is an upper layer entity of the RLC layer entity before the at least one radio bearer type is converted.
  • the processor 1001 is further configured to: stop and reset all timers of the RLC layer entity of the at least one radio bearer; and reset all state variables of the RLC layer entity of the at least one radio bearer to Initial value.
  • the upper layer entity of the RLC layer entity is a packet data convergence protocol PDCP layer entity; when the type of the at least one radio bearer is a second type, The upper layer entity of the RLC layer entity is an adaptation protocol layer entity;
  • the upper layer entity of the RLC layer entity is an adaptation protocol layer entity
  • the RLC layer entity is the PDCP layer entity
  • the processor 1001 is further configured to: retransmit the PDCP layer of the at least one radio bearer
  • the entity does not send a successful PDCP protocol data unit, the PDCP protocol data unit is delivered to the underlying entity before the at least one radio bearer type is converted, but the underlying entity has not yet fed back the PDCP protocol data unit that is successfully received.
  • the underlying entity is an underlying entity of the PDCP layer entity before the at least one radio bearer type is converted;
  • the terminal device generates and sends a PDCP status report, where the PDCP status report is used to notify the base station of the sequence number of the PDCP service data unit that is not successfully received.
  • the processor 1001 is further configured to: use the PDCP entity of the at least one radio bearer to record the next sent PDCP service data.
  • the value of the variable of the sequence number of the unit and the value of the superframe number are reset to 0; the PDCP entity of the at least one radio bearer is used to record the value of the variable of the sequence number of the next received PDCP service data unit and the superframe The value of the number is reset to 0.
  • the processor 1001 is further configured to reset the medium access control MAC layer entity.
  • processor 1001 is further configured to perform at least one of the following features:
  • the subsequently received transport block is considered to be the first transmission of the transport block.
  • the processor 1001 is further configured to receive the MAC protocol of the at least one radio bearer after the type conversion.
  • the MAC protocol data unit includes the MAC service data unit of the at least one radio bearer, the at least one wireless The MAC service data unit carried is discarded.
  • the method specifically includes:
  • the processor 1001 and the transceiver 1004 of the terminal 1000 perform the following functions:
  • the processor 1001 is configured to: determine that the type of the at least one radio bearer of the terminal device is converted from the first type to the second type; acquire first indication information, where the first indication information is used to indicate that the at least one radio bearer is After the type conversion, the radio bearer type of the data of the at least one radio bearer received by the terminal device is a first type radio bearer or a second type radio bearer.
  • the first indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the transceiver 1004 is configured to: receive, by the base station, the RLC protocol data unit of the at least one radio bearer;
  • the processor 1001 is further configured to: determine, according to the first indication information and the received sequence number of the RLC protocol data unit of the at least one radio bearer, the wireless of the received RLC protocol data unit of the at least one radio bearer
  • the bearer type is a first type radio bearer or a second type radio bearer; and the received RLC protocol data unit of the at least one radio bearer is determined according to the radio bearer type of the received RLC protocol data unit of the at least one radio bearer.
  • the upper layer entity is an upper layer entity of the RLC protocol layer of the at least one radio bearer before the at least one radio bearer type is converted, or the at least one radio bearer type is converted.
  • the transceiver 1004 is configured to: receive an RRC connection reconfiguration message of the at least one radio bearer sent by the base station, where the RRC connection reconfiguration message includes the first indication information; or The at least one radio bearer RLC control protocol data unit; the RLC control protocol data unit includes the first indication information.
  • the transceiver 1004 is configured to: receive a MAC protocol data unit sent by the base station, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, and a MAC sub-portion corresponding to the MAC service data unit.
  • the first indication information is carried in the header.
  • the transceiver 1004 is further configured to: send, to the base station, second indication information, where the second indication information is used to notify the at least one received by the base station after the at least one radio bearer type is converted.
  • the radio bearer type of one radio bearer data is a first type radio bearer or a second type radio bearer.
  • the second indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the transceiver 1004 is configured to: send, to the base station, an RRC connection reconfiguration of the at least one radio bearer. Completing the message, the RRC connection reconfiguration complete message includes the second indication information; or sending the RLC control protocol data unit of the at least one radio bearer to the base station, where the RLC control protocol data unit includes The second indication information is described.
  • the transceiver 1004 is configured to: send, to the base station, a MAC protocol data unit, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, and a MAC subheader corresponding to the MAC service data unit. Carrying the second indication information.
  • the processor 1001 and the transceiver 1004 of the present application may further perform the steps related to the terminal device in the third data processing method of the present application, including:
  • the transceiver 1004 is configured to: receive the first configuration information that is sent by the base station, where the first configuration information is used to configure the at least one radio bearer of the terminal device to be converted by the first type of radio bearer to the second type of radio bearer;
  • the processor 1001 is configured to: according to the first configuration information, determine that the type of the at least one radio bearer is converted by the first type radio bearer to the second type radio bearer.
  • the processor 1001 is configured to: determine, according to the identifier of the at least one radio bearer carried in the first configuration information, that the at least one radio bearer is a currently configured radio bearer, and determine the at least one radio When the type of the bearer is the first type of radio bearer, if the first configuration information includes the third indication information, determining that the type of the at least one radio bearer is converted by the first type of radio bearer to the second type of radio bearer Carry
  • the first type of radio bearer includes: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity, and a logical channel;
  • the second type radio bearer includes: a PDCP layer entity, the adaptation protocol layer The entity, the RLC layer entity and the logical channel;
  • the third indication information is used to indicate that the type of the radio bearer configured by the terminal device is the second type of radio bearer.
  • the processor 1001 is configured to: determine, according to the identifier of the at least one radio bearer carried in the first configuration information, that the at least one radio bearer is a currently configured radio bearer, and determine When the type of the at least one radio bearer is the first type of radio bearer, if the first configuration information does not include the fifth indication information, determining that the type of the at least one radio bearer is converted into the Said second type of radio bearer;
  • the first type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel;
  • the second type of radio bearer includes: a packet data convergence protocol PDCP layer entity, and a radio link
  • the control protocol RLC layer entity and the logical channel, the fifth indication information is used to indicate that the type of the radio bearer configured by the terminal device is the first type of radio bearer.
  • the terminal includes a plurality of functional modules for performing the method steps related to the terminal in the foregoing embodiments related to the present application, and solving the technical problem of how to avoid packet loss.
  • the terminal 2000 includes a processing unit 2001 and a transceiver unit 2002. It should be noted that the operations performed by the processing unit 2001 or the transceiver unit 2002 can be regarded as the operation of the terminal 2000.
  • the processing unit 2001 in the terminal 2000 can be implemented by a processor in the terminal 2000, and the transceiver unit 2002 can be implemented by a transceiver in the terminal 2000.
  • the present application provides a base station 3000.
  • the base station 3000 includes a processor 3001 and a transceiver 3004, where:
  • the transceiver 3004 is configured to support communication between the terminal and the base station, and send the foregoing data processing method to the terminal device. Information or instructions involved.
  • the processor 3001 is configured to support the base station to perform corresponding functions in the above data processing methods.
  • a memory 3002 and a communication interface 3003 are further included; wherein the processor 3001, the memory 3002, the communication interface 3003, and the transceiver 3004 are connected to each other through a bus 3005.
  • the memory is for coupling with a processor that stores program instructions and data necessary for the base station.
  • the processor 3001 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 3002 includes a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory.
  • RAM random-access memory
  • the memory may also include a non-volatile memory such as a flash memory.
  • a hard disk drive (HDD) or a solid-state drive (SSD); the memory may also include a combination of the above types of memories.
  • the communication interface 3003 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a WLAN interface.
  • the transceiver 3004 can be a wired transceiver, a wireless transceiver, or a combination thereof.
  • the wired transceiver can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless transceiver can be, for example, a wireless local area network communication interface, a cellular network communication interface, or a combination thereof.
  • the bus 3005 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
  • Bus 3005 can include any number of interconnected buses and bridges, specifically linked by various circuits of memory represented by one or more processors 3001 and memory 3002 represented by the processor.
  • the bus can also link various other circuits such as peripherals, voltage regulators, and power management circuits, and will not be further described in this application.
  • Transceiver 3004 provides means for communicating with various other devices on a transmission medium.
  • the processor 3001 is responsible for managing the bus architecture and general processing, and the memory 3002 can store data used by the processor 3001 in performing operations.
  • the processor 3001 and the transceiver 3004 of the present application may be used to perform the steps related to the base station in the first data processing method of the present application, and may also perform the steps related to the base station in the second data processing method of the present application, and may also be performed. The steps related to the base station in the third data processing method of the present application.
  • the method specifically includes:
  • the transceiver 3004 is configured to receive a PDCP status report sent by the terminal device, where the status report is used to notify the base station of the sequence number of the PDCP service data unit that is not successfully received.
  • the processor 3001 and the transceiver 3004 of the present application are used to perform the steps related to the base station in the second data processing method of the present application.
  • the transceiver 3004 is configured to: send the first indication information to the terminal device, where The first indication information is used to indicate that after the at least one radio bearer type of the terminal device is converted, the terminal is configured.
  • the radio bearer type of the received data of the at least one radio bearer is a first type radio bearer or a second type radio bearer.
  • the first indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the transceiver 3004 is configured to: send, to the terminal device, an RRC connection reconfiguration message of the at least one radio bearer, where the RRC connection reconfiguration message includes the first indication information; or, The terminal device sends the RLC control protocol data unit of the at least one radio bearer, where the RLC control protocol data unit includes the first indication information.
  • the transceiver 3004 is configured to: send, to the terminal device, a MAC protocol data unit, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, and a MAC sub-portion corresponding to the MAC service data unit.
  • the first indication information is carried in the header.
  • the transceiver 3004 is configured to: receive second indication information that is sent by the terminal device, where the second indication information is used to indicate, after the at least one radio bearer type is switched, the base station receives the The radio bearer type of the at least one radio bearer data is a first type radio bearer or a second type radio bearer.
  • the second indication information includes an RLC sequence number, where the RLC sequence number is a sequence number of the RLC protocol data unit of the at least one radio bearer, where the RLC protocol data unit is included according to the first The last RLC protocol data unit of the RLC service data unit of the format encapsulated by the type of radio bearer, or the RLC protocol data unit refers to the first one of the RLC service data units encapsulated in the format of the second type of radio bearer RLC protocol data unit.
  • the processor 3001 is configured to: when the second indication information includes an RLC sequence number, determine, according to the first indication information and the received sequence number of the RLC protocol data unit of the at least one radio bearer, the received The radio bearer type of the at least one radio bearer RLC protocol data unit is a first type radio bearer or a second type radio bearer; and determining the radio bearer type according to the received radio bearer type of the RLC protocol data unit of the at least one radio bearer
  • the upper layer entity of the received RLC protocol data unit of the at least one radio bearer is a PDCP layer entity or a protocol adaptation layer entity.
  • the transceiver 3004 is configured to: receive an RRC connection reconfiguration complete message of the at least one radio bearer sent by the terminal device, where the RRC connection reconfiguration complete message includes the second indication information; or
  • the base station receives an RLC control protocol data unit of the at least one radio bearer sent by the terminal device, where the RLC control protocol data unit includes the second indication information.
  • the transceiver 3004 is configured to: receive an RRC connection reconfiguration complete message of the at least one radio bearer sent by the terminal device, where the RRC connection reconfiguration complete message of the at least one radio bearer includes the second Instructions.
  • the transceiver 3004 is configured to: receive, by the terminal device, a MAC protocol data unit of the at least one radio bearer, where the MAC protocol data unit includes a MAC service data unit of the at least one radio bearer, The second indication information is included in a MAC sub-head corresponding to the MAC service data unit.
  • the method specifically includes:
  • the transceiver 3004 is configured to: send the first configuration information to the terminal device, where the first configuration information is used to configure the at least one radio bearer of the terminal device to be converted by the first type of radio bearer to the second type of radio bearer.
  • the first type of radio bearer includes: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity, and a logical channel
  • the second type radio bearer includes: a PDCP layer entity, where a protocol layer entity, an RLC layer entity, and a logical channel
  • the first configuration information includes an identifier of the at least one radio bearer, and further includes third indication information, where the third indication information is used to indicate the terminal device configuration
  • the type of radio bearer is the second type of radio bearer.
  • the first type of radio bearer includes: a PDCP layer entity, the adaptation protocol layer entity, an RLC layer entity, and a logical channel
  • the second type radio bearer includes: a packet data convergence protocol PDCP layer entity, a radio link control protocol RLC layer entity and a logical channel
  • the first configuration information includes an identifier of the at least one radio bearer, but does not include fifth indication information, where the fifth indication information is used to indicate the terminal
  • the type of radio bearer configured by the device is the first type of radio bearer.
  • the base station includes multiple functional modules for performing the method steps related to the base station in various embodiments involved in the present application.
  • the base station 4000 shown in FIG. 16 includes a processing unit 4001 and a transceiver unit 4002.
  • the operations performed by the processing unit 4001 or the transceiver unit 4002 can be considered as operations of the base station 4000.
  • the processing unit 4001 in the base station 4000 can be implemented by a processor of the base station 4000, and the transceiver unit 4002 can be implemented by a transceiver in the base station 4000.
  • the present application provides a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to execute the various embodiments and terminals involved in the present application Related method steps.
  • the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform various embodiments in accordance with the present application with a base station Related method steps.
  • the present application provides a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the method steps associated with the terminal in various embodiments of the present application.
  • the present application provides a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the method steps associated with the base station in various embodiments of the present application.
  • the various illustrative logical blocks, modules and circuits described in the embodiments of the present application may be implemented by a general purpose processing unit.
  • Digital signal processing unit application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the above designed to implement or operate the described Features.
  • the general purpose processing unit may be a micro processing unit.
  • the general purpose processing unit may be any conventional processing unit, controller, microcontroller or state machine.
  • the processing unit may also be implemented by a combination of computing devices, such as a digital signal processing unit and a microprocessing unit, a plurality of microprocessing units, one or more microprocessing units in conjunction with a digital signal processing unit core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software module executed by a processing unit, or a combination of the two.
  • the software modules can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art.
  • the storage medium can be coupled to the processing unit such that the processing unit can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processing unit.
  • the processing unit and the storage medium may be configured in an ASIC, and the ASIC may be configured in the user terminal. Alternatively, the processing unit and the storage medium may also be configured in different components in the user terminal.
  • the above-described functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions may be stored on a computer readable medium or transmitted as one or more instructions or code to a computer readable medium.
  • Computer readable media includes computer storage media and communication media that facilitates the transfer of computer programs from one place to another.
  • the storage medium can be any available media that any general purpose or special computer can access.
  • Such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other device or data structure that can be used for carrying or storing Other media that can be read by a general purpose or special computer, or a general or special processing unit.
  • any connection can be appropriately defined as a computer readable medium, for example, if the software is from a website site, server or other remote source through a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or wirelessly transmitted in, for example, infrared, wireless, and microwave, is also included in the defined computer readable medium.
  • DSL digital subscriber line
  • the disks and discs include compact disks, laser disks, optical disks, DVDs, floppy disks, and Blu-ray disks. Disks typically replicate data magnetically, while disks typically optically replicate data with a laser. Combinations of the above may also be included in a computer readable medium.

Landscapes

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

Abstract

一种数据处理方法及终端设备、基站，该方法包括：终端设备确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；所述终端设备丢弃所述至少一个无线承载的无线链路控制协议RLC层实体发送侧缓存的RLC协议数据单元和/或RLC业务数据单元；所述终端设备将所述至少一个无线承载的RLC层实体接收侧已接收到的RLC协议数据单元组装成RLC业务数据单元，并将所述RLC业务数据单元按序递交给所述RLC层实体的上层实体；其中，所述上层实体为所述至少一个无线承载类型转换前所述RLC层实体的上层实体。当一个无线承载的类型发生第I类型和第III类型间的转换时，能够防止解包失败导致的丢包问题，还能并节约空口资源。

Description

一种数据处理方法及终端设备、基站
本申请要求在2017年3月13日提交中国专利局、申请号为201710147480.8、发明名称为“一种无线承载配置和数据处理方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种数据处理方法及终端设备、基站。
背景技术
一个用户设备可以直接与基站连接，采用直连方式与基站通信，也可以通过中继UE(Relay UE，也可以称为UE-to-Network Relay)与基站连接，并进行数据通信，通过中继UE与基站进行数据通信的用户设备称为远端用户设备(Remote UE)。
在LTE的Rel-15中，正在研究通过在Relay UE的RLC层以上，PDCP层以下进行数据转发，这种数据转发方式可以称为Layer 2UE-to-NW Relay。这种情况下，Remote UE可以称为eRemote UE，也可称作Evolved Remote UE，Relay UE可以称为eRelay UE，也称作Evolved Relay UE或者Evolved UE-to-NW Relay。
eRelay UE通过数据无线承载(Data Radio Bearer，DRB)和信令无线承载(Signaling radio bearer，SRB)来转发eRemoteUE的数据。具体有以下几种可能：
方式一：复用eRelay UE的一个无线承载来传输eRemote UE的一个无线承载，eRelay UE的这种用来同时传输自己的数据/信令和至少一个eRemote UE的数据/信令的无线承载，称为第I类型无线承载。
方式二：eRelay UE专门建立一个无线承载来传输eRemote UE的一个无线承载，eRelay UE的这种只用来传输至少一个eRemote UE的数据/信令的无线承载，称为第II类型无线承载。
除了上述两种类型的无线承载，eRelay UE还存在另外一种无线承载，即只用来传输eRelay UE自己的数据/信令的无线承载，这种无线承载成为第III类型无线承载。
eRelay UE的一个无线承载在某些情况下会发生上述第I类型无线承载与第III类型无线承载的转换。
例如，当一个eRemote UE通过eRelay UE与基站建立连接后，基站可能会配置eRemote UE去复用eRelay UE当前已经的一个数据无线承载。这种情况下，该数据无线承载的类型可以从第III类型转换为第I类型。当一个eRemote UE由于移动离开eRelay UE后，之前eRemote UE与eRelay UE复用的一个第I类型数据无线承载不再需要传输eRemote UE的数据，此时该数据无线承载的类型可以从第I类型转换为第III类型。
当一个无线承载的类型发生第I类型和第III类型间的转换时，在MAC层和该无线承载对应的RLC层可能会缓存有该无线承载按原类型对应的协议栈产生的数据包。而类型转换后，新类型无线承载的协议栈产生的数据包的格式和原类型无线承载的协议栈产生的数据包的格式是不同的。因此，当接收端接收到上述缓存的原无线承载类型对应的数据包时，如果按照新无线承载类型对应数据包格式来解析该数据包，会导致将错误解析的数据包递交给上层协议栈，例如IP层，最终导致丢包。
因此，当一个无线承载的类型发生第I类型和第III类型间的转换时，如何避免产生丢包的技术问题需要得以解决。
发明内容
本申请实施例提供了一种数据处理方法及终端设备、基站，用以解决现有技术中当一个无线承载的类型发生第I类型和第III类型间的转换时，如何避免产生丢包的技术问题。
第一方面，本申请提供一种数据处理方法，包括：
终端设备确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；
所述终端设备丢弃所述至少一个无线承载的无线链路控制协议RLC层实体发送侧缓存的RLC协议数据单元和/或RLC业务数据单元；
所述终端设备将所述至少一个无线承载的RLC层实体接收侧已接收到的RLC协议数据单元组装成RLC业务数据单元，并将所述RLC业务数据单元按序递交给所述RLC层实体的上层实体；其中，所述上层实体为所述至少一个无线承载类型转换前所述RLC层实体的上层实体。
本申请的上述实施例中，对于终端设备的至少一个无线承载的RLC层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，RLC层实体发送侧缓存的上行数据中包括还未发送给MAC层实体的数据包，这些数据包在类型转换后发送给基站，会导致基站侧解包失败产生丢包，通过将无线承载的RLC层实体发送侧缓存的数据丢弃，一方面如果基站没有接收到这些数据包，还会向终端设备发送所述至少一个无线承载的PDCP状态报告，指示终端设备重发这些数据包，避免解包失败造成的数据包丢弃，另一方面，将这些可能造成解包失败的数据包丢弃，避免传输无效数据包导致的资源浪费，可以节省宝贵的空口资源。
本申请的上述实施例中，对于终端设备的至少一个无线承载的RLC层实体的接收侧来说，在终端设备的至少一个无线承载的类型发生转换时，RLC层实体接收侧接收的下行数据包括在类型转换前接收但此时还未递交给上层实体(类型转换前的上层实体)的数据包，这些数据包已经发送成功，为了避免浪费空口资源重新传输，在发生类型转换时，将这些数据递交给类型转换前的上层实体，确保数据包能够被正确解包，避免了在发生类型转换后递交给类型转换后的上层实体导致的解包失败。
一种可能的实现方式中，还包括：
所述终端设备停止并重置所述至少一个无线承载的RLC层实体的所有计时器；以及
所述终端设备将所述至少一个无线承载的RLC层实体的所有状态变量重置为初始值。
其中，所述至少一个无线承载的类型为第一类型时，所述RLC层实体的上层实体为分组数据汇聚协议PDCP层实体；所述至少一个无线承载的类型为第二类型时，所述RLC层实体的上层实体为适配协议层实体；或者，
所述至少一个无线承载的类型为第一类型时，所述RLC层实体的上层实体为适配协议层实体；所述至少一个无线承载的类型为第二类型时，所述RLC层实体的上层实体为所述PDCP层实体。
一种可能的实现方式中，若所述至少一个无线承载为使用RLC确认模式的数据无线承载或使用RLC确认模式的信令无线承载，还包括：
所述终端设备重传所述至少一个无线承载的PDCP层实体未发送成功的PDCP协议数 据单元，所述PDCP协议数据单元为所述至少一个无线承载类型转换前递交给底层实体，但所述底层实体还未反馈确认成功接收的PDCP协议数据单元；其中，所述底层实体为所述至少一个无线承载类型转换前所述PDCP层实体的底层实体；
所述终端设备生成并发送PDCP状态报告，所述PDCP状态报告用于通知基站未成功接收的PDCP业务数据单元的序列号。
本申请的上述实施例中，对于终端设备的至少一个无线承载的PDCP层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，为适应至少一个无线承载采用RLC确认模式传输下行数据的应用场景，对于在类型转换前发送但是还未接收到成功接收确认的上行PDCP PDU，PDCP实体需要重传所述数据包。从而可以保证所述数据包不会丢失。
一种可能的实现方式中，若所述至少一个无线承载为使用RLC确认模式的信令无线承载，还包括：
所述终端设备将所述至少一个无线承载的PDCP实体用于记录下一个发送的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0；
所述终端设备将所述至少一个无线承载的PDCP实体用于记录下一个接收的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0。
一种可能的实现方式中，还包括：
所述终端设备重置媒体接入控制MAC层实体。
一种可能的实现方式中，还包括以下特征中的至少一个：
所述终端设备清空媒体接入控制MAC层实体的全部上行HARQ进程的缓存，
所述终端设备将所有上行HARQ进程的新数据指示信息置为0，
所述终端设备清空媒体接入控制MAC层实体的全部下行HARQ进程的缓存，
所述终端设备针对每一下行HARQ进程，将其后续接收到的传输块视为该传输块的第一次传输。
一种可能的实现方式中，还包括：
所述终端设备的媒体接入控制MAC层实体接收所述至少一个无线承载在类型转换后的MAC协议数据单元；
若所述MAC协议数据单元的初次接收是在所述至少一个无线承载类型转换前，且所述MAC协议数据单元中包含所述至少一个无线承载的MAC业务数据单元，则将所述至少一个无线承载的所述MAC业务数据单元丢弃。
本申请的上述实施例中，对于终端设备的MAC层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，MAC层实体发送侧的上行HARQ进程中包含终端设备至少一个无线承载的逻辑信道所对应的MAC SDU时，如果这些MAC SDU是还未发送成功的数据包，这些数据包在类型转换后发送给基站，会导致基站侧解包失败产生丢包，通过将MAC层实体重置，或者将MAC层实体发送侧上行HARQ进程的缓存清空，，一方面如果基站没有接收到这些数据包，还会向终端设备发送至少一个无线承载的PDCP状态报告，指示终端设备重发这些数据包，避免解包失败造成的数据包丢弃，另一方面，将这些可能造成解包失败的数据包丢弃，避免传输无效数据包导致的资源浪费，可以节省宝贵的空口资源。
本申请的上述实施例中，对于终端设备的MAC层实体的接收侧来说，在终端设备的 至少一个无线承载的类型发生转换时，如果MAC层实体接收侧的下行HARQ进程的缓存中包含终端设备的等待HARQ重传的MAC PDU，并且所述MAC PDU中包含所述至少一个无线承载的MAC SDU时，在发生类型转换后，，将这些MAC SDU递交给MAC上层实体，会导致上层实体解包失败产生丢包，通过将MAC层实体重置，或者将MAC层实体接收侧的下行HARQ进程的缓存清空，或者将MAC层实体接收侧的下行HARQ进程的缓存的类型转换前与至少一个无线承载的逻辑信道对应的MAC SDU丢弃，一方面如果终端设备没有接收到这些数据包，终端设备还会向基站发送终端设备至少一个无线承载的PDCP状态报告，指示基站重发这些数据包，避免终端设备解包失败造成的数据包丢弃，另一方面，将这些可能造成解包失败的数据包丢弃，避免传输无效数据包导致的资源浪费，可以节省宝贵的空口资源。
第二方面本申请提供一种数据处理方法，包括：
第一设备确定所述第一设备的至少一个无线承载的类型由第一类型转换为第二类型；
所述第一设备接收第二设备发送的第一指示信息，所述第一指示信息用于指示所述第一设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载；
其中，所述第一设备为终端设备，所述第二设备为基站；或者，所述第一设备为基站，所述第二设备为终端设备。
本申请中，通过第一指示信息，可以通知接收端设备哪些数据包在接收端设备的RLC层处理完后需要递交给接收端设备的PDCP层，哪些数据包在接收端设备的RLC层处理完后需要递交给接收端设备的协议适配层，从而确保数据包能够被正确解包，避免了在发生类型转换后导致的解包失败。
一种可能的实现方式中，所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
进一步的，还包括：
所述第一设备接收所述至少一个无线承载的RLC协议数据单元；
所述第一设备根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；
所述第一设备根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体，所述上层实体为所述至少一个无线承载类型转换前，或者所述至少一个无线承载类型转换后所述至少一个无线承载的RLC协议层的上层实体。
进一步的，所述第一设备获取第一指示信息，包括：
所述第一设备接收第二设备发送的所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息或者，
所述第一设备接收所述第二设备发送的所述至少一个无线承载的RLC控制协议数据单元；所述RLC控制协议数据单元中包含所述第一指示信息。
一种可能的实现方式中，所述第一设备获取第一指示信息，包括：
所述第一设备接收所述第二设备发送的MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。
一种可能的实现方式中，还包括：
所述第一设备向所述第二设备发送第二指示信息；所述第二指示信息用于通知所述第二设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
一种可能的实现方式中，所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
进一步的，所述第一设备向所述第二设备发送第二指示信息，包括：
所述第一设备向所述第二设备发送所述至少一个无线承载的RRC连接重配完成消息，所述RRC连接重配完成消息中包括所述第二指示信息；或者，
所述第一设备向所述第二设备发送所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包括所述第二指示信息。
一种可能的实现方式中，所述第一设备向所述第二设备发送第二指示信息，包括：
所述第一设备向所述第二设备发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第二指示信息。
第三方面，本申请提供一种数据处理方法，包括：
终端设备接收基站发送的第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载；
根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载。
一种可能的实现方式中，所述终端设备根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载，包括：
所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，
若所述第一配置信息中包括第三指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
其中，所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
在此实施例中，终端设备根据第一配置信息，可以确定出所述终端设备的至少一个无线承载由第III类型无线承载转换为第I类型无线承载。
一种可能的实现方式中，所述终端设备根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载，包括：
所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，
若所述第一配置信息中不包括第五指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
其中，所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道，所述第五指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。在此实施例中，终端设备根据第一配置信息，可以确定出所述终端设备的至少一个无线承载由第I类型无线承载转换为第III类型无线承载。
第四方面，本申请提供一种数据处理方法，包括：
基站向终端设备发送第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载。
一种可能的实现方式中，若所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；则
所述第一配置信息包括所述至少一个无线承载的标识，还包括第三指示信息，所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。通过此实施例基站可以配置所述终端设备的至少一个无线承载由第III类型无线承载转换为第I类型无线承载。
一种可能的实现方式中，若所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；则
所述第一配置信息中包括所述至少一个无线承载的标识，但不包括第五指示信息，所述第五指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。通过此实施例基站可以配置所述终端设备的至少一个无线承载由第I类型无线承载转换为第III类型无线承载。
第五方面，本申请提供一种终端设备，所述终端设备包括存储器、收发器和处理器，其中：所述存储器用于存储指令；所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述终端设备用于执行上述第一方面或第一方面中的任意可能的实现方式中所述的方法。
第六方面，本申请提供一种终端设备，所述终端设备包括存储器、收发器和处理器，其中：所述存储器用于存储指令；所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述终端设备用于执行上述第二方面或第二方面中的任意可能的实现方式中与终端有关的步骤。
第七方面，本申请提供一种基站，所述基站包括存储器、收发器和处理器，其中：所述存储器用于存储指令；
所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述基站用于执行上述第二方面或第二方面中的任意可能的实现方式中与基站有关的步骤。
第八方面，本申请提供一种终端设备，所述终端设备包括存储器、收发器和处理器，其中：所述存储器用于存储指令；所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述终端设备用于执行上述第三方面或第三方面中的任意可能的实现方式中的方法。
第九方面，本申请提供一种基站，所述基站包括存储器、收发器和处理器，其中：所述存储器用于存储指令；
所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述基站用于上述第四方面或第四方面中的任意可能的实现方式中的方法。
第十方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面中的任意可能的实现方式中所述的方法。
第十一方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面中的任意可能的实现方式中所述的方法。
第十二方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面中的任意可能的实现方式中所述的方法。
第十三方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面中的任意可能的实现方式中所述的方法。
第十四方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第三方面或第三方面中的任意可能的实现方式中所述的方法。
第十五方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第三方面或第三方面中的任意可能的实现方式中所述的方法。
第十六方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第四方面或第四方面中的任意可能的实现方式中所述的方法。
第十七方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第四方面或第四方面中的任意可能的实现方式中所述的方法。
附图说明
图1为本申请实施例提供的一种系统架构示意图；
图2(a)～图2(d)为本申请实施例提供的一种系统架构下的用户面、控制面的协议栈的示意图；
图3(a)～图3(c)为本申请实施例提供的一种接入网的通信协议栈的示意图；
图3(d)为本申请实施例提供的一种第III类型无线承载的数据包的包格式的示意图；
图3(e)为本申请实施例提供的一种第I类型无线承载的数据包的包格式的示意图；
图4为本申请实施例提供的一种数据处理方法的方法流程图；
图5为本申请实施例提供的一种第III类型无线承载转换为第I类型无线承载的上行数据传输过程的流程图；
图6为本申请实施例提供的一种第III类型无线承载转换为第I类型无线承载的下行数据传输过程的流程图；
图7为本申请实施例提供的一种第I类型无线承载转换为第III类型无线承载的上行数据传输过程的流程图；
图8为本申请实施例提供的一种第I类型无线承载转换为第III类型无线承载的下行数据传输过程的流程图；
图9为本申请实施例提供的一种数据处理方法的方法流程图；
图10为本申请实施例提供的一种发送RLC控制PDU的方法流程图；
图11(a)～图11(c)为本申请实施例提供的一种RLC控制PDU的结构示意图；
图12为本申请实施例提供的一种MAC PDU的结构示意图；
图13和图14为本申请实施例提供的一种终端设备的结构示意图；
图15和图16为本申请实施例提供的一种基站的结构示意图；
图17为本申请实施例提供的一种SRB的状态报告的格式示意图。
具体实施方式
下面将结合附图对本申请实施例作进一步地详细描述。
下面介绍一下本申请的系统运行环境，本申请描述的技术可以适用于LTE系统，如LTE/LTE-A/eLTE系统,或其他采用各种无线接入技术的无线通信系统，例如采用码分多址(code division multiple access,CDMA)，频分多址(frequency division multiple access,FDMA)，时分多址(time division multiple access,TDMA)，正交频分多址(orthogonal frequency division multiple access,OFDMA)，单载波频分多址(single carrier-frequency division multiple access,SC-FDMA)等接入技术的系统，还适用于后续的演进系统，如第五代5G(还可以称为新无线电(new radio,NR))系统等，也可以扩展到类似的无线通信系统中，如wifi、wimax、以及3gpp相关的蜂窝系统。
如图1所示，为本申请通信系统的一种基础架构，包括中继终端20、远程终端30和基站10，基站10和中继终端20通过无线接口可以进行数据或者信令的传输，包括上行传输和下行传输，中继终端20与基站10之间的连接包括上行链路和下行链路。其中，远程终端30通过中继终端20与基站10连接并进行数据或者信令的传输，中继终端20和远程终端30之间的连接为侧行链路。
在LTE的Rel-15中，中继终端20通过中继终端20的RLC层实体以上，PDCP层实体以下进行数据转发，这种数据转发方式可以称为Layer 2UE-to-NW Relay。这种情况下，远程终端30可以称为eRemote UE，也可称作Evolved Remote UE，中继终端20可以称为eRelay UE，也称作Evolved Relay UE或者Evolved UE-to-NW Relay。
在这种系统架构下，远程终端30通过中继终端20与网络侧进行连接和数据传输时，远程终端30和中继终端20间通过Sidelink技术/PC5接口进行连接，远程终端30、中继终端20、基站(eNB)10以及核心网(CN)的用户面的协议栈参见图2(a)，远程终端30、中继终端20、基站(eNB)10以及核心网(CN)的控制面的协议栈参见图2(b)。
可选的，中继终端20和远程终端30之间还可以采用non-3GPP接入技术进行连接。例如，蓝牙接入技术，WLAN接入技术等。
在这种情况下，远程终端30通过中继终端20与网络侧进行连接，并且远程终端30和中继终端20间通过non-3GPP接入技术进行连接，远程终端30、中继终端20、基站(eNB)10以及核心网(CN)的用户面的协议栈参见图2(c)，远程终端30、中继终端20、基站(eNB)10以及核心网(CN)的控制面的协议栈参见图2(d)。
基于图2a、图2b、图2(c)和图2(d)的协议栈，在远程终端30通过中继终端20与网络侧进行连接和数据传输时，若中继终端20的一个或多个无线承载为第I类型无线承载，中继终端20、基站(eNB)10之间的通信协议栈架构参见图3(a)，从图3(a)可以看出，中继终端20的一个或多个无线承载包括PDCP层、协议适配层RLC层，和逻辑信道，中继终端20的PDCP层和RLC层之间增加了协议适配层；基站10与中继终端20的一个或多个无线承载对应的协议层实体包括PDCP层、协议适配层，RLC层，和逻辑信道，在PDCP层和RLC层之间增加了协议适配层。
若中继终端20的一个或多个无线承载为第II类型无线承载，中继终端20、基站(eNB)10之间的通信协议栈架构参见图3(b)，从图3(b)可以看出，中继终端20的一个或多个无线承载包括协议适配层(Adaptation layer)，RLC层，和逻辑信道；基站10中与中继终端20的一个或多个无线承载对应的协议层实体包括协议适配层和RLC层。
若中继终端20的一个或多个无线承载为第III类型无线承载，中继终端20、基站(eNB)10之间的通信协议栈架构参见图3(c)，从图3(c)可以看出，中继终端20的一个或多个无线承载包括PDCP层，RLC层，和逻辑信道；基站10中与中继终端20的一个或多个无线承载对应的协议层实体包括PDCP层，RLC层，和逻辑信道。
基于图3(a)和图3(c)，当远程终端30通过中继终端20接入网络侧时，若中继终端20的一个或多个无线承载从第III类型无线承载转换为第I类型无线承载，中继终端20的一个或多个无线承载的RLC层实体的上层实体由PDCP层实体转换为适配协议层实体，中继终端20的一个或多个无线承载的PDCP层实体的下层实体由RLC层实体转换为适配协议层实体。此时，中继终端20的一个或多个无线承载的RLC层的RLC SDU包格式由第III类型无线承载的RLC SDU的包格式转换为第I类型无线承载的RLC SDU的包格式，第III类型无线承载的RLC SDU的包格式，参见图3(d)，第I类型无线承载的RLC SDU的包格式参见图3(e)。
基于图3(a)和图3(c)，当远程终端30不通过中继终端20接入网络侧时，若中继终端20的一个或多个无线承载从第I类型无线承载转换为第III类型无线承载，中继终端20的一个或多个无线承载的RLC层实体的上层实体由适配协议层实体转换为PDCP层实体，中继终端20的一个或多个无线承载的PDCP层实体的下层实体由适配协议层实体转换为RLC层实体。此时，中继终端20的一个或多个无线承载的RLC层实体进行数据和信令的传输时，数据和信令的包格式由第I类型无线承载的封装格式转换为第III类型无线承载的封装格式。
基于图1、图2(a)、图2(b)、图2(c)、图2(d)、图3(a)、图3(b)、图3(c)示例的中继终端20、远程终端30和基站10之间的基础系统架构，本申请实施例提供了一种数据处理方法及终端设备和基站，来解决该系统架构下存在的中继终端20的一个或多个无线承载的类型发生第I类型和第III类型间的转换时如何避免产生丢包的技术问题。
需要说明的是，本申请中的终端设备是指该基础系统架构中的中继终端20。
本申请中图1、图2(a)、图2(b)、图2(c)、图2(d)、图3(a)、图3(b)、图3(c)仅仅为示例性内容，并不对本申请应用场景进行限定。
以下，对本申请中的部分用语进行解释说明，以便与本领域技术人员理解。
本申请中所说的用户和终端(或者UE)，它们之间的关系可以是：用户使用终端(或者UE)接入网络，与基站实现通信。
本申请所涉及到的终端可以为向用户提供语音和/或数据连通性的设备(device)，包括有线终端和无线终端。无线终端可以是具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备，经无线接入网与一个或多个核心网进行通信的移动终端。例如，无线终端可以为移动电话、计算机、平板电脑、个人数码助理(personal digital assistant，PDA)、移动互联网设备(mobile Internet device，MID)、可穿戴设备和电子书阅读器(e-book reader)等。又如，无线终端也可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动设备。再如，无线终端可以为移动站(mobile station)、接入点(access point)。前述提及的UE即为终端的一种，是在LTE系统中的称谓。为方便描述，本申请后续的描述中，上面提到的设备统称为终端。
本申请所涉及到的基站是一种部署在无线接入网(radio access network,RAN)中用以为终端提供无线通信功能的装置。所述基站可以包括各种形式的宏基站，微基站，中继站，接入点基站控制器，收发节点(transmission reception point,TRP)等等。在采用不同的无线接入技术的系统中，基站的具体名称可能会有所不同，例如在LTE网络中，称为演进的节点B(evolved NodeB,eNB),在后续的演进系统中，还可以称为新无线节点B(new radio nodeB,gNB)。
本申请涉及的多个，是指两个或两个以上。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
当一个终端设备的无线承载的类型发生第I类型和第III类型间的转换时，本申请提供了两类数据处理方法来解决如何避免产生丢包的技术问题。
在第一类数据处理方法中，当一个终端设备的无线承载(包括数据无线承载DRB和信令无线承载SRB)需要进行类型转换时，主要提供了终端设备中与该无线承载对应的各个协议层实体的发送端和接收端对存储的所述无线承载发生类型转换前的数据包进行处理的实施方式，主要包括与该无线承载对应的MAC层，RLC层，PDCP层的发送端和接收端的对数据包的处理方法。
在第二类数据处理方法中，当一个终端设备的无线承载数据无线承载信令无线承载需要进行类型转换时，发送端设备存贮的无线承载发生类型转换前的数据包在类型转换后继续传输给接收端设备，接收端设备在一段时间内会收到两种不同封装格式的数据包。为了帮助接收端设备按照正确的封装格式来解码数据包，发送端设备需要通知接收端设备哪些数据包在接收端设备的RLC层处理完后需要递交给接收端设备的PDCP层，哪些数据包在接收端设备的RLC层处理完后需要递交给接收端设备的协议适配层。第二类数据处理方法主要提供了几种发送端设备通知接收端设备所接收的数据包是那种无线承载类型的通知方法。其中，对于上行数据传输，发送端设备是终端设备，接收端设备是基站，对于下行数据传输，发送端设备是基站，接收端设备是终端。
这两类数据处理方法都可以避免终端设备作为中继UE时其无线承载类型发生转换时导致的中继UE的数据包在接入层的传输过程中发生丢失，还可以减少中继UE的无线承载发生转换后，传输无效数据包导致的资源浪费。
下面结合附图对第一类数据处理方法进行详细描述。
本申请提供的如图4所示的一种数据处理方法，包括：
步骤401，终端设备确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；
步骤402，所述终端设备丢弃所述至少一个无线承载的无线链路控制协议RLC层实体发送侧(或者RLC层发送侧实体)缓存的RLC协议数据单元和/或RLC业务数据单元；所述终端设备将所述至少一个无线承载的RLC层实体接收侧(或者RLC层接收实体)已接收到的RLC协议数据单元组装成RLC业务数据单元，并将所述RLC业务数据单元按序递交给所述RLC层实体的上层实体；其中，所述上层实体为所述至少一个无线承载类型转换前所述RLC层实体的上层实体。
值得说明的是，步骤401中，所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型，包括终端设备的至少一个无线承载可以从第III类型无线承载转换为第I类型无线承载，也可以从第I类型无线承载转换为第III类型无线承载。
其中，在终端设备的至少一个无线承载为第I类型无线承载时，无线承载对应的实体包括：PDCP层实体，适配协议层实体，RLC层实体和逻辑信道；在终端设备的至少一个无线承载为第III类型无线承载时，无线承载对应的实体包括：PDCP层实体，RLC层实体和逻辑信道。
因此，当终端设备的至少一个无线承载从第I类型无线承载转换为第III类型无线承载时，RLC层实体的上层实体由适配协议层实体转换为PDCP层实体，PDCP层实体的下层实体由适配协议层实体转换为RLC层实体。
当终端设备的至少一个无线承载从第III类型无线承载转换为第I类型无线承载时，RLC层实体的上层实体由PDCP层实体转换为适配协议层实体，PDCP层实体的下层实体由RLC层实体转换为适配协议层实体。
值得说明的是，由于终端设备的数据无线承载可以采用RLC非确认(Unacknowleged Mode，UM)模式传输数据，也可以采用RLC确认(Aacknowleged Mode，AM)模式传输数据，终端设备的信令无线承载采用RLC AM模式传输数据，因此，为适应至少一个无线承载为采用RLC AM模式的信令无线承载或数据无线承载，步骤402中，丢弃终端设备至少一个无线承载的RLC层实体发送侧缓存的RLC协议数据单元(Packet Data Unit，PDU)和RLC业务数据单元(Service Data Unit，SDU)；为适应至少一个无线承载为采用RLC UM模式的数据无线承载，步骤402中，丢弃终端设备至少一个无线承载的RLC层实体发送侧缓存的RLC SDU。
本申请的上述实施例中，对于终端设备的至少一个无线承载的RLC层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，RLC层实体发送侧缓存的上行数据中包括还未发送给MAC层实体的数据包，这些数据包在类型转换后发送给基站，会导致基站侧解包失败产生丢包，通过将无线承载的RLC层实体发送侧缓存的数据丢弃，一方面如果基站没有接收到这些数据包，还会向终端设备发送所述至少一个无线承载的PDCP状态报告，指示终端设备重发这些数据包，避免解包失败造成的数据包丢弃，另一方面， 将这些可能造成解包失败的数据包丢弃，避免传输无效数据包导致的资源浪费，可以节省宝贵的空口资源。
本申请的上述实施例中，对于终端设备的至少一个无线承载的RLC层实体的接收侧来说，在终端设备的至少一个无线承载的类型发生转换时，RLC层实体接收侧接收的下行数据包括在类型转换前接收但此时还未递交给上层实体(类型转换前的上层实体)的数据包，这些数据包已经发送成功，为了避免浪费空口资源重新传输，在发生类型转换时，将这些数据递交给类型转换前的上层实体，确保数据包能够被正确解包，避免了在发生类型转换后递交给类型转换后的上层实体导致的解包失败。
可选的，步骤401之后，还包括：
所述终端设备停止并重置所述至少一个无线承载的RLC层实体的所有计时器；以及
所述终端设备将所述至少一个无线承载的RLC层实体的所有状态变量重置为初始值。
可选的，若所述至少一个无线承载为使用RLC确认模式的数据无线承载或使用RLC确认模式的信令无线承载，进一步还包括：
所述终端设备重传所述至少一个无线承载的PDCP层实体未发送成功的PDCP协议数据单元，所述PDCP协议数据单元为所述至少一个无线承载类型转换前递交给底层实体，但所述底层实体还未反馈确认成功接收的PDCP协议数据单元；其中，所述底层实体为所述至少一个无线承载类型转换前所述PDCP层实体的底层实体；
所述终端设备接收所述底层实体递交的PDCP协议数据单元，；
进一步的，还可包括：所述终端设备针对下行数据的传输，生成并向基站发送所述至少一个无线承载的PDCP状态报告，所述PDCP状态报告用于通知基站所述至少一个无线承载的未成功接收的PDCP业务数据单元的序列号。可选的，所述终端可以根据所述基站的指示来判断针对所述至少一个无线承载是否需要发送所述PDCP状态报告。当所述终端收到所述基站的指示需要发送所述至少一个无线承载的所述PDCP状态报告时，所述终端发送所述PDCP状态报告。
本申请的上述实施例中，对于终端设备的至少一个无线承载的PDCP层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，类型转换对PDCP层实体没有影响，PDCP层实体可以按照类型转换后的封装格式对需要发送的上行数据进行处理和发送。
本申请的上述实施例中，对于终端设备的至少一个无线承载的PDCP层实体的接收侧来说，在终端设备的至少一个无线承载的类型发生转换时，PDCP层实体的接收侧接收类型转换前的底层实体递交的下行数据包，这些数据包已经发送成功，为了避免浪费空口资源重新传输，在发生类型转换时，将这些数据递交给类型转换前的上层实体，确保数据包能够被正确解包，避免了在发生类型转换后递交给类型转换后的上层实体导致的解包失败。
本申请的上述实施例中，对于终端设备的至少一个无线承载的PDCP层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，为适应至少一个无线承载采用RLC确认模式传输下行数据的应用场景，对于在类型转换前发送但是还未接收到成功接收确认的上行PDCP PDU，PDCP实体需要重传所述数据包。从而可以保证所述数据包不会丢失。值得说明的是，至少一个无线承载为采用RLC AM模式的信令无线承载时的PDCP状态报告的格式和内容，与至少一个无线承载为采用RLC AM模式的数据无线承载时的 PDCP状态报告不同。对于采用RLC AM模式的DRB，本申请中PDCP状态报告是标准TS 36.323中定义的PDCP层的状态报告，PDCP状态报告的格式和内容设置参见TS 36.323，对于采用RLC AM模式的SRB，本申请中的PDCP的状态报告的格式参见图17。
可选的，若所述至少一个无线承载为使用RLC确认模式的信令无线承载，进一步还包括：
所述终端设备将所述至少一个无线承载的PDCP实体用于记录下一个发送的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0；
所述终端设备将所述至少一个无线承载的PDCP实体用于记录下一个接收的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0。
可选的，若所述至少一个无线承载为使用RLC确认模式的信令无线承载，进一步还包括：
对于上行数据传输，丢弃所述至少一个无线承载的PDCP实体发送侧所有存储的PDCP SDU和PDCP PDU；
对于下行数据传输，丢弃所述至少一个无线承载的PDCP实体接收侧所有接收到的RLC层实体由于所述无线承载发生类型转换而递交上来的PDCP PDU，丢弃所有存储的PDCP SDU和PDCP PDU。
可选的，若所述至少一个无线承载为使用RLC确认模式的信令无线承载，进一步还包括：
对于上行数据传输，在完成类型转换后，按照正常的上行数据的发送过程来发送所述至少一个无线承载的PDCP层实体发送侧所存储的PDCP SDU和PDCP PDU给底层实体，即该无线承载类型转换后的PDCP层实体的底层实体；
对于下行数据传输，在完成类型转换后，按照正常的下行数据的处理过程来接收PDCP PDU。其中，所述PDCP PDU是指所述至少一个无线承载的PDCP层实体类型转换前的底层实体由于所述无线承载发生类型转换而递交上来的PDCP PDU。
进一步的，步骤401之后，还包括，对于终端设备的MAC层实体，有以下几种可选的数据处理方式：
可选的，所述终端设备重置媒体接入控制MAC层实体。
可选的，对于MAC层实体的处理，包括以下特征中的至少一个：所述终端设备清空媒体接入控制MAC层实体的全部上行HARQ进程的缓存，所述终端设备将所有上行HARQ进程的新数据指示信息置为0，所述终端设备清空媒体接入控制MAC层实体的全部下行HARQ进程的缓存，所述终端设备针对每一下行HARQ进程，将其后续接收到的传输块视为该传输块的第一次传输。
可选的，所述终端设备的媒体接入控制MAC层实体在所述至少一个无线承载类型转换后接收到MAC协议数据单元；若所述MAC协议数据单元的初次接收是在所述至少一个无线承载类型转换前，且所述MAC协议数据单元中包含所述至少一个无线承载的MAC业务数据单元，则将所述至少一个无线承载的所述MAC业务数据单元丢弃。
本申请的上述实施例中，对于终端设备的MAC层实体的发送侧来说，在终端设备的至少一个无线承载的类型发生转换时，MAC层实体发送侧的上行HARQ进程中包含终端设备至少一个无线承载的逻辑信道所对应的MAC SDU时，如果这些MAC SDU是还未发送成功的数据包，这些数据包在类型转换后发送给基站，会导致基站侧解包失败产生丢包， 通过将MAC层实体重置，或者将MAC层实体发送侧上行HARQ进程的缓存清空，，一方面如果基站没有接收到这些数据包，还会向终端设备发送至少一个无线承载的PDCP状态报告，指示终端设备重发这些数据包，避免解包失败造成的数据包丢弃，另一方面，将这些可能造成解包失败的数据包丢弃，避免传输无效数据包导致的资源浪费，可以节省宝贵的空口资源。
本申请的上述实施例中，对于终端设备的MAC层实体的接收侧来说，在终端设备的至少一个无线承载的类型发生转换时，如果MAC层实体接收侧的下行HARQ进程的缓存中包含终端设备的等待HARQ重传的MAC PDU，并且所述MAC PDU中包含所述至少一个无线承载的MAC SDU时，在发生类型转换后，，将这些MAC SDU递交给MAC上层实体，会导致上层实体解包失败产生丢包，通过将MAC层实体重置，或者将MAC层实体接收侧的下行HARQ进程的缓存清空，或者将MAC层实体接收侧的下行HARQ进程的缓存的类型转换前与至少一个无线承载的逻辑信道对应的MAC SDU丢弃，一方面如果终端设备没有接收到这些数据包，终端设备还会向基站发送终端设备至少一个无线承载的PDCP状态报告，指示基站重发这些数据包，避免终端设备解包失败造成的数据包丢弃，另一方面，将这些可能造成解包失败的数据包丢弃，避免传输无效数据包导致的资源浪费，可以节省宝贵的空口资源。
由于上述第一类数据处理方法中，终端设备的至少一个无线承载的类型由第一类型转换为第二类型，包括可以从第III类型无线承载转换为第I类型无线承载，也可以从第I类型无线承载转换为第III类型无线承载。而且终端设备的数据无线承载DRB可以采用RLCUM模式传输数据，也可以采用RLC AM模式传输数据，终端设备的信令无线承载采用RLC AM模式传输数据。因此，在上述第一类数据处理方法中，主要包括以下六种应用场景下的数据处理方法，这六种应用场景分别是：
应用场景1：采用RLC UM模式传输数据的数据无线承载从第III类型无线承载转换为第I类型无线承载。
应用场景2：采用RLC AM模式传输数据的数据无线承载从第III类型无线承载转换为第I类型无线承载。
应用场景3：采用RLC AM模式传输数据的信令无线承载从第III类型无线承载转换为第I类型无线承载。
应用场景4：采用RLC UM模式传输数据的数据无线承载从第I类型无线承载转换为第III类型无线承载。
应用场景5：采用RLC AM模式传输数据的数据无线承载从第I类型无线承载转换为第III类型无线承载。
应用场景6：采用RLC AM模式传输数据的信令无线承载从第I类型无线承载转换为第III类型无线承载。
下面结合具体应用场景对上述第一类数据处理方法的方法流程进行说明。
第一种可能的实现方式中，针对应用场景1，具体包括以下步骤：
终端设备接收基站发送的RRC连接重配消息，RRC连接重配消息中包含的指示信息指示终端设备将DRBi的类型从第III类型无线承载转换为第I类型无线承载。其中，DRBi为终端设备中的任一个从第III类型无线承载转换为第I类型无线承载的DRB。
在确定DRBi的类型从第III类型无线承载转换为第I类型无线承载之后，终端设备的 发送侧的数据处理方法包括：
对于DRBi的RLC层实体的发送侧：将发送侧目前缓存的所有RLC SDU丢弃。
可选的，进一步还可包括：停止并重置DRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置DRBi的RLC层实体的所有状态变量为初始值。
对于MAC层实体的发送侧：
可选的方式一，清空所有的上行HARQ缓存，并将所有的上行HARQ进程的新数据指示(New Data Indicator，NDI)设为0。
可选的方式二，重置MAC，包括目前所有重置MAC时需要进行的操作，此操作为现有技术，此处不再累述。
在确定DRBi的类型从第III类型无线承载转换为第I类型无线承载之后，终端设备的接收侧的数据处理方法包括：
对于MAC层实体的接收侧：
可选的方式一，清空所有的下行HARQ缓存，并将所有的下行HARQ进程的新数据指示(New Data Indicator，NDI)设为0，针对每一下行HARQ进程，将接下来接收到的传输块(TB，Transport Block)的传输视为该传输块的第一次传输。
可选的方式二，重置MAC，包括目前所有重置MAC时需要进行的操作，此操作为现有技术，此处不再累述。
可选的方式三，在类型转换后，如果接收到DRBi的一个MAC PDU，该MAC PDU的初次接收发生在DRBi类型转换前，且该MAC PDU中包含的MAC SDU中包括DRBi对应的MAC SDU，则将该MAC PDU中DRBi的MAC SDU丢弃，避免DRBi的MAC SDU在类型转换前后的包格式不同导致的解包失败。
对于DRBi的RLC层实体的接收侧：
将接收侧的缓存中包括的在DRBi类型转换前接收到，但还未递交到PDCP层实体的DRBi的RLC PDU按照类型转换前的包格式重组成RLC SDU，将RLC SDU中包含的数据按序递交给DRBi的PDCP层实体。
进一步还可包括：停止并重置DRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置DRBi的RLC层实体的所有状态变量为初始值。
对于DRBi的PDCP层实体的接收侧：
接收DRBi的RLC层实体因类型转换而递交的PDCP PDU，并按照正常从DRBi的RLC层实体接收到PDCP PDU后的处理过程来处理。
第二种可能的设计中，针对应用场景2，具体包括以下步骤：
终端设备接收基站发送的RRC连接重配消息，RRC连接重配消息中包含的指示信息指示终端设备将DRBi的类型从第III类型无线承载转换为第I类型无线承载。其中，DRBi为终端设备中的任一个从第III类型无线承载转换为第I类型无线承载的DRB。
在确定DRBi的类型从第III类型无线承载转换为第I类型无线承载之后，终端设备的发送侧的数据处理方法包括：
对于DRBi的PDCP层实体的发送侧：
将DRBi类型转换前递交给DRBi的RLC层实体但是DRBi的RLC层实体还没有确认已经成功传输的PDCP PDU进行重传，按照类型转换后的正常流程，将DRBi需要重传 PDCP PDU发送给协议适配层实体。
对于DRBi的协议适配层实体的发送侧：
按照类型转换后的正常流程，将类型转换后DRBi的PDCP层实体递交的需要重传的PDCP PDU发送给DRBi的RLC层实体。
对于DRBi的RLC层实体的发送侧：将发送侧目前缓存的所有RLC SDU和RLC PDU丢弃。
按照类型转换后的正常流程，将协议适配层实体递交的需要重传的数据处理后发送给MAC层实体。
可选的，进一步还可包括：停止并重置DRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置DRBi的RLC层实体的所有状态变量为初始值。
对于MAC层实体的发送侧：同场景1，此处不再累述。
在确定DRBi的类型从第III类型无线承载转换为第I类型无线承载之后，终端设备的接收侧的数据处理方法包括：
对于DRBi的逻辑信道对应的MAC层实体的接收侧：同场景1，此处不再累述。
对于DRBi的RLC层实体的接收侧：同场景1，此处不再累述。
对于DRBi的PDCP层实体的接收侧：可选的，确定没有接收到的下行数据(PDCPPDU)的序列号，通过PDCP层实体向基站发送PDCP状态报告，用来通知没有正确接收的下行数据包的序列号，以便基站根据PDCP状态报告向终端设备重发这些未发送成功的下行数据包。可选的，基站可以配置PDCP层实体是否需要发送PDCP状态报告。
第三种可能的设计中，针对应用场景3，具体包括以下步骤：
终端设备接收基站发送的RRC连接重配消息，RRC连接重配消息中包含的指示信息指示终端设备将SRBi的类型从第III类型无线承载转换为第I类型无线承载。其中，SRBi为终端设备中的任一个从第III类型无线承载转换为第I类型无线承载的SRB。
在确定SRBi的类型从第III类型无线承载转换为第I类型无线承载之后，终端设备的发送侧的数据处理方法包括：
对于SRBi的PDCP层实体的发送侧：
将SRBi发生类型转换前递交给SRBi的RLC层实体但是SRBi的RLC层实体还没有确认已经成功传输的PDCP PDU进行重传，按照类型转换后的正常流程，将SRBi需要重传PDCP PDU发送给协议适配层实体。
可选的，还包括：对于上行数据传输，丢弃发送侧所有存储的PDCP SDU和PDCP PDU；将SRBi的PDCP层实体用于记录下一个发送的PDCP SDU的序列号的变量的值以及用于记录产生COUNT值的发送侧的超帧号的值重置为0。
可选的，还包括：对于上行数据传输，在完成类型转换后，按照正常的上行数据的发送过程将发送侧所存储的类型转换前缓存的还未发送的SRBi的PDCP SDU和PDCP PDU发送给协议适配层实体，并将SRBi的PDCP层实体用于记录下一个发送的PDCP SDU的序列号的变量的值以及用于记录产生COUNT值的超帧号的值重置为0。
对于SRBi的协议适配层实体的发送侧：
按照类型转换后的正常流程，将类型转换后SRBi的PDCP层实体递交的需要重传的PDCP PDU发送给SRBi的RLC层实体。
可选的，还包括：按照类型转换后上行数据正常的发送过程将PDCP层实体递交的类型转换前缓存的还未发送的SRBi的PDCP SDU和缓存PDCP PDU发送给RLC层实体。
对于SRBi的RLC层实体的发送侧：
将发送侧目前缓存的所有RLC SDU和RLC PDU丢弃。
按照类型转换后的正常流程，将协议适配层实体递交的需要重传的数据处理后通过SRBi的逻辑信道发送给MAC层实体。
可选的，还包括：按照类型转换后将协议适配层递交的类型转换前缓存的还未发送的数据发送给通过SRBi的逻辑信道发送给MAC层实体。
可选的，进一步还可包括：停止并重置SRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置SRBi的RLC层实体的所有状态变量为初始值。
对于MAC层实体的发送侧：
可选的方式一，清空所有的上行HARQ缓存，并将所有的上行HARQ进程的新数据指示(New Data Indicator，NDI)设为0。
可选的方式二，重置MAC，包括目前所有重置MAC时需要进行的操作，此操作为现有技术，此处不再累述。
将SRBi的RLC层实体递交的需要重传的MAC SDU复用到一个传输块后发送到基站的MAC层实体。
可选的，还包括：将SRBi的RLC层实体递交的类型转换前缓存但还未发送的数据通过空口发送到基站的MAC层实体。
在确定SRBi的类型从第III类型无线承载转换为第I类型无线承载之后，终端设备的接收侧的数据处理方法包括：
对于MAC层实体的接收侧：
可选的方式一，清空所有的下行HARQ缓存，并将所有的下行HARQ进程的新数据指示(New Data Indicator，NDI)设为0，针对每一下行HARQ进程，将接下来接收到的传输块(TB，Transport Block)的传输视为该传输块的第一次传输。
可选的方式二，重置MAC，包括目前所有重置MAC时需要进行的操作，此操作为现有技术，此处不再累述。
可选的方式三，在类型转换后，如果接收到SRBi的一个MAC PDU，该MAC PDU的初次接收发生在SRBi类型转换前，且该MAC PDU中包含的MAC SDU中包括SRBi对应的MAC SDU，则将该MAC PDU中SRBi的MAC SDU丢弃，避免SRBi的MAC SDU在类型转换前后的包格式不同导致的解包失败。
对于SRBi的RLC层实体的接收侧：
将接收侧的缓存中包括的在SRBi类型转换前接收到，但还未递交到PDCP层实体的SRBi的RLC PDU按照类型转换前的包格式重组成RLC SDU，将RLC SDU中包含的数据按序递交给SRBi的PDCP层实体。
可选的，进一步还可包括：停止并重置SRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置SRBi的RLC层实体的所有状态变量为初始值。
对于SRBi的PDCP层实体的接收侧：
接收SRBi的RLC层实体因类型转换而递交的PDCP PDU，并按照正常从SRBi的RLC层实体接收到PDCP PDU后的处理过程来处理。
可选的，确定没有接收到的下行数据包(PDCP PDU)的序列号，通过PDCP层实体向基站发送PDCP状态报告，用来通知没有正确接收的下行数据包的序列号，以便基站根据PDCP状态报告向终端设备重发这些未发送成功的下行数据包。可选的，基站可以配置PDCP层实体是否需要发送PDCP状态报告。
可选的，还包括：对于下行数据传输，丢弃接收侧缓存的所有下行PDCP SDU和PDCP PDU。将SRBi的PDCP层实体用于记录下一个接收的PDCP SDU的序列号的变量的值以及用于记录产生COUNT值的接收侧的超帧号的值重置为0
可选的，还包括：对于下行数据传输，将接收到的RLC层实体因SRBi类型转换递交上来的PDCP PDU递交给RRC层，并将SRBi的PDCP层实体用于记录下一个发送的PDCP SDU的序列号的变量的值以及用于记录产生COUNT值的接收侧的超帧号的值重置为0。
第四种可能的设计中，针对应用场景4，具体包括以下步骤：
终端设备接收RRC连接重配消息，RRC连接重配消息中包含的指示信息指示终端设备将DRBi的类型从第I类型无线承载转换为第III类型无线承载。
在确定DRBi的类型从第I类型无线承载转换为第III类型无线承载之后，终端设备的发送侧的数据处理方法包括：
对于DRBi的协议适配层实体的发送侧：清除目前缓存的所有上行数据。
对于DRBi的RLC层实体的发送侧：同场景1，此处不再累述。
对于MAC层实体的发送侧：同场景1，此处不再累述。
在确定DRBi的类型从第I类型无线承载转换为第III类型无线承载之后，终端设备的接收侧的数据处理方法包括：
对于MAC层实体的接收侧：同场景1，此处不再累述。
对于DRBi的RLC层实体的接收侧：
将接收侧的缓存中包括的在DRBi类型转换前接收到，但还未递交到协议适配层实体的DRBi的RLC PDU按照类型转换前的包格式重组成RLC SDU，将RLC SDU中包含的数据按序递交给DRBi的协议适配层实体。
可选的，进一步还可包括：停止并重置DRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置DRBi的RLC层实体的所有状态变量为初始值。
对于DRBi的协议适配层实体的接收侧：
接收DRBi的RLC层实体因类型转换而递交的协议适配层PDU，并将协议适配层PDU中包含的PDCP PDU处理后递交给PDCP层实体。
可选的，如果DRBi的RLC层实体递交的协议适配层PDU中的数据部分(即PDCP PDU)是发送给终端设备的，将其处理后递交给PDCP层实体；如果是发送给终端设备的远程终端的，将协议适配层PDU中的数据部分丢弃。
对于DRBi的PDCP层实体的接收侧：
接收DRBi的协议适配层实体递交的PDCP PDU，按照正常从协议适配层实体接收到PDCP PDU后的处理过程来处理。
第五种可能的设计中，针对应用场景5，具体包括以下步骤：
终端设备接收RRC连接重配消息，RRC连接重配消息中包含的指示信息指示终端设备将DRBi的类型从第I类型无线承载转换为第III类型无线承载。
在确定DRBi的类型从第I类型无线承载转换为第III类型无线承载之后，终端设备的发送侧的数据处理方法包括：
对于DRBi的PDCP层实体的发送侧：
按照类型转换后的正常流程，将DRBi发生类型转换前递交给DRBi的协议适配层实体但是DRBi的协议适配层实体还没有确认已经成功传输的PDCP PDU进行重传，将SRBi需要重传PDCP PDU发送给RLC层实体。
对于DRBi的协议适配层实体的发送侧：清除目前缓存的所有上行数据。
对于DRBi的RLC层实体的发送侧：将发送侧目前缓存的RLC SDU和RLC PDU丢弃。
将类型转换后PDCP层实体递交的需要重传的RLC SDU按照RLC SDU类型转换前的包格式处理成需要重传的RLC PDU，将需要重传的RLC PDU通过DRBi的逻辑信道发送给MAC层实体。
可选的，进一步还可包括：停止并重置DRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置DRBi的RLC层实体的所有状态变量为初始值。
对于MAC层实体的发送侧：
将类型转换后包含DRBi的需要重传的数据复用到一个传输块后发送到基站的MAC层实体。其它步骤同场景1，此处不再累述。
在确定DRBi的类型从第I类型无线承载转换为第III类型无线承载之后，终端设备的接收侧的数据处理方法包括：
对于MAC层实体的接收侧：同场景1，此处不再累述。
对于DRBi的RLC层实体的接收侧：具体内容与场景4相同，此处不再累述。
对于DRBi的协议适配层实体的接收侧：具体内容与场景4相同，此处不再累述。
对于DRBi的PDCP层实体的接收侧：
可选的，确定没有接收到的下行数据包(PDCP PDU)的序列号，通过PDCP层实体向基站发送PDCP状态报告，用来通知没有正确接收的下行数据包的序列号，以便基站根据PDCP状态报告向终端设备重发这些未发送成功的下行数据包。可选的，基站可以配置PDCP层实体是否需要发送PDCP状态报告。其其他步骤同场景4，此处不再累述。
第六种可能的设计中，针对应用场景6的数据处理方法，具体包括以下步骤：
终端设备接收RRC连接重配消息，RRC连接重配消息中包含的指示信息指示终端设备将DRBi的类型从第I类型无线承载转换为第III类型无线承载。
在确定DRBi的类型从第I类型无线承载转换为第III类型无线承载之后，终端设备的发送侧的数据处理方法包括：
对于SRBi的PDCP层实体的发送侧：
按照类型转换后的正常流程，将SRBi发生类型转换前递交给SRBi的协议适配层实体但是SRBi的协议适配层实体还没有确认已经成功传输的PDCP PDU进行重传，将SRBi需要重传PDCP PDU发送给RLC层实体。
可选的，还包括：对于上行数据传输，丢弃发送侧所有存储的PDCP SDU和PDCP PDU； 将SRBi的PDCP层实体用于记录下一个发送的PDCP SDU的序列号的变量的值以及用于记录产生COUNT值的超帧号的值重置为0。
可选的，还包括：对于上行数据传输，在完成类型转换后，按照正常的上行数据的发送过程将发送侧所存储的类型转换前SRBi的PDCP SDU和PDCP PDU发送给RLC层实体，并将SRBi的PDCP层实体用于记录下一个发送的PDCP SDU的序列号的变量的值以及用于记录产生COUNT值的超帧号的值重置为0。
对于SRBi的协议适配层实体的发送侧：清除目前缓存的上行数据。
对于SRBi的RLC层实体的发送侧：将发送侧目前缓存的RLC SDU和RLC PDU丢弃。
可选的，进一步还可包括：停止并重置SRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置SRBi的RLC层实体的所有状态变量为初始值。
将类型转换后PDCP层实体递交的需要重传的RLC SDU按照RLC SDU类型转换前的包格式处理成需要重传的RLC PDU，将需要重传的RLC PDU通过SRBi的逻辑信道发送给MAC层实体。
可选的，还包括：按照类型转换后上行数据正常的发送过程将PDCP层实体递交的类型转换前缓存中还未发送的SRBi的RLC SDU和缓存RLC PDU通过SRBi的逻辑信道发送给MAC层实体。
对于MAC层实体的发送侧：
按照类型转换后的正常流程，将类型转换后包含SRBi的需要重传的MAC SDU的MAC PDU复用到一个传输块后发送到基站的MAC层实体。
可选的，还包括：按照类型转换后上行数据正常的发送过程将SRBi的逻辑信道递交的类型转换前缓存中还未发送的MAC SDU和MAC PDU通过空口发送到基站的MAC层实体。其他步骤同场景1，此处不再累述。
在确定SRBi的类型从第I类型无线承载转换为第III类型无线承载之后，终端设备的接收侧的数据处理方法包括：
对于MAC层实体的接收侧：同场景3，此处不再累述。
对于SRBi的RLC层实体的接收侧：
将接收侧的缓存中包括的在SRBi类型转换前接收到，但还未递交到协议适配层实体的SRBi的RLC PDU按照类型转换前的包格式重组成RLC SDU，将RLC SDU中包含的数据按序递交给SRBi的协议适配层实体。
可选的，进一步还可包括：停止并重置SRBi的RLC层实体的所有计时器，包括用于检测丢失的RLC PDU的重排序计时器；重置SRBi的RLC层实体的所有状态变量为初始值。
对于SRBi的协议适配层实体的接收侧：
接收SRBi的RLC层实体因类型转换递交的协议适配层PDU，将其处理为PDCP PDU，递交给SRBi的PDCP层实体。
对于SRBi的PDCP层实体的接收侧：
接收SRBi的协议适配层实体因类型转换而递交的PDCP PDU，并按照正常从SRBi的协议适配层实体接收到PDCP PDU后的处理过程来处理。其他可选实施例同场景3，此 处不再累述。
对于场景1、场景2和场景3，在终端设备进行上述数据处理之后，终端设备的至少一个数据无线承载的上行数据传输过程参见附图5，DRBi的PDCP层实体的发送侧、协议适配层实体的发送侧、RLC层实体的发送侧以及MAC层实体的发送侧依次按照类型转换后的发送上行数据的过程发送上行数据。与DRBi对应的基站侧的MAC层实体、RLC层实体、协议适配层实体以及PDCP层实体依次按照类型转换后的接收上行数据的过程接收上行数据。
对于场景1、场景2和场景3，在终端设备进行上述数据处理之后，终端设备的至少一个数据无线承载的下行数据传输过程参见附图6，DRBi的PDCP层实体的接收侧、协议适配层实体的接收侧、RLC层实体的接收侧以及MAC层实体的接收侧依次按照类型转换后的接收下行数据的过程接收下行数据。与DRBi对应的基站侧的MAC层实体、RLC层实体、协议适配层实体以及PDCP层实体依次按照类型转换后的发送下行数据的过程发送下行数据。
对于场景4、场景5和场景6，在进行上述数据处理之后，终端设备的至少一个数据无线承载的上行数据传输过程参见附图7，DRBi的PDCP层实体的发送侧、RLC层实体的发送侧以及MAC层实体的发送侧依次按照类型转换后的发送上行数据的过程发送上行数据。与DRBi对应的基站侧的MAC层实体、RLC层实体以及PDCP层实体依次按照类型转换后的接收上行数据的过程接收上行数据。
对于场景4、场景5和场景6，在终端进行上述数据处理之后，终端设备的至少一个数据无线承载的下行数据传输过程参见附图8，DRBi的PDCP层实体的接收侧、RLC层实体的接收侧以及MAC层实体的接收侧依次按照类型转换后的接收下行数据的过程接收下行数据。与DRBi对应的基站侧的MAC层实体、RLC层实体以及PDCP层实体依次按照类型转换后的发送下行数据的过程发送下行数据。
可选的，对于上行数据传输，还包括：基站确定没有接收到的上行数据包的序列号，通过PDCP层实体向终端设备发送PDCP状态报告，用来通知没有正确接收的DRBi的上行数据包的序列号，终端设备根据PDCP状态报告向基站重发这些数据包。可选的，基站可以配置PDCP层实体是否需要发送PDCP状态报告。
可选的，对于上行数据传输，还包括：基站确定没有接收到的SRBi的上行数据包的序列号，通过PDCP层实体向终端设备发送PDCP状态报告，用来通知没有正确接收的SRBi的上行数据包的序列号，终端设备根据PDCP状态报告向基站重发SRBi的这些数据包。其中，SRBi的PDCP状态报告的格式和内容，与DRBi的PDCP状态报告不同。
下面结合附图对第二类数据处理方法进行详细描述。
本申请提供的如图9所示的一种数据处理方法，来解决当一个终端设备的无线承载的类型发生第I类型和第III类型间的转换时，如何避免产生丢包的技术问题，主要包括：
步骤S1：第一设备确定所述第一设备的至少一个无线承载的类型由第一类型转换为第二类型；
步骤S2：所述第一设备接收第二设备发送的第一指示信息，所述第一指示信息用于指示所述第一设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载；
其中，所述第一设备为终端设备，所述第二设备为基站；或者，所述第一设备为基站， 所述第二设备为终端设备。
可选的，所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
可选的，步骤S2之后还包括：
所述第一设备接收所述至少一个无线承载的RLC协议数据单元；
所述第一设备根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；
所述第一设备根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体，所述上层实体为所述至少一个无线承载类型转换前，或者所述至少一个无线承载类型转换后所述至少一个无线承载的RLC协议层的上层实体。
可选的，所述第一指示信息包含RLC序列号时，所述第一设备获取第一指示信息，包括：
所述第一设备接收第二设备发送的所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息或者，
所述第一设备接收所述第二设备发送的所述至少一个无线承载的RLC控制协议数据单元；所述RLC控制协议数据单元中包含所述第一指示信息。
可选的，所述第一指示信息不包含RLC序列号时，所述第一设备获取第一指示信息，包括：
所述第一设备接收所述第二设备发送的MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。
可选的，还包括：
所述第一设备向所述第二设备发送第二指示信息；所述第二指示信息用于通知所述第二设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
可选的，所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
可选的，所述第二指示信息包含RLC序列号时，所述第一设备向所述第二设备发送第二指示信息，包括：
所述第一设备向所述第二设备发送所述至少一个无线承载的RRC连接重配完成消息，所述RRC连接重配完成消息中包括所述第二指示信息；或者，
所述第一设备向所述第二设备发送所述至少一个无线承载的RLC控制协议数据单元， 所述RLC控制协议数据单元中包括所述第二指示信息。
可选的，所述第二指示信息不包含RLC序列号时，所述第一设备向所述第二设备发送第二指示信息，包括：所述第一设备向所述第二设备发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第二指示信息。下面结合具体的实施例进行说明。
本申请提供一种终端设备侧的数据处理方法，包括：
终端设备确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；
所述终端设备获取第一指示信息，所述第一指示信息用于指示在所述至少一个无线承载类型转换后，所述终端设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载；
在所述终端设备获取第一指示信息之后还包括：
所述终端设备接收所述至少一个无线承载的RLC协议数据单元；所述终端设备根据所述第一指示信息和所述至少一个无线承载的RLC协议数据单元的序列号，确定所述至少一个无线承载的RLC协议数据单元的上层实体。
其中，终端设备的至少一个无线承载的类型由第一类型转换为第二类型，包括可以从第III类型无线承载转换为第I类型无线承载，也可以从第I类型无线承载转换为第III类型无线承载。
可选的，所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
所述第一指示信息包含RLC序列号时，所述终端设备根据所述第一指示信息和所述至少一个无线承载的RLC协议数据单元的序列号，确定所述至少一个无线承载的RLC协议数据单元的上层实体，具体包括：
终端设备根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；
终端设备根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体为PDCP层实体还是协议适配层实体。
在此基础上，第一种可能的实现方式中，所述终端设备获取第一指示信息，包括：
所述终端设备接收基站发送的所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息。
例如，对于下行数据的传输，为了让作为中继终端的终端设备eRelay UE知道在一个无线承载发生类型转换后，接收到的来自该无线承载上的数据包在RLC层处理完后需要递交给PDCP层还是递交给Adaptation layer层，基站在RRC连接重配消息(RRC Connection Reconfiguration)中通知eRelay UE所述发生类型转换的无线承载的一个RLC PDU的序列号，该RLC PDU为包含按照类型转换后对应的包格式封装的RLC SDU的第 一个RLC PDU所对应的序列号。或者，该RLC PDU为包含按照类型转换前对应的包格式封装的RLC SDU的最后一个RLC PDU所对应的序列号。
当一个无线承载从第III类型无线承载转换为第I类型无线承载时，第III类型无线承载的RLC SDU的格式如下图3(d)所示，第I类型无线承载的RLC SDU的格式如图3(e)所示。下面以一个无线承载从第III类型无线承载转换为第I类型无线承载后的下行数据的传输情况为例，具体说明上述方法如何实施：
首先，在RRC连接重配消息中，基站通知eRelay UE在发生类型转换的无线承载上传输RLC PDU的RLC序列号，RLC序列号是指包含如图3(e)所示的RLC SDU的第一个RLC PDU所对应的序列号；或者RLC序列号是指包含如图3(d)所示的RLC SDU的最后一个RLC PDU所对应的序列号。
其次，在所述无线承载发生类型转换后，当eRelay UE接收到来自所述无线承载的RLC PDU时，eRelay UE根据该RLC PDU中包含的序列号，判断接收的该RLC PDU处理后需要递交给PDCP层实体，还是递交给协议适配层实体。
例如，对于一个DRB，第一指示信息中的RLC序列号是包含如图3(e)所示的该DRB的RLC SDU的第一个RLC PDU所对应的序列号，如RLC序列号为99。如果该DRB发生类型转换后，eRelay UE接收到来自该DRB的RLC PDU包含的序列号为100，则eRelay UE判断接收的该RLC PDU在RLC层实体处理后需要递交给协议适配层实体，PDCP层实体。如果该DRB发生类型转换后，eRelay UE接收到来自该DRB的RLC PDU包含的序列号为98，则eRelay UE判断接收的该RLC PDU在RLC层实体处理后需要递交给PDCP层实体。
当一个无线承载从第I类型转换为第III类型后，针对下行数据传输的操作同上述情况。当所述无线承载转换为第III类型之后，为了能处理基站侧缓存的类型转换前的数据包，eRelay UE在所述无线承载发生类型转换后，需要继续使用RLC层实体的上层实体Adaptation layer一段时间。在确定已经处理完基站侧缓存在所有类型转换前的数据包后，eRelay UE可以选择释放所述Adaptation layer。
值得说明的是，在此实施例中，当基站通过RRC连接重配消息通知eRelay UE相应的RLC序列号后，基站和eRelay UE侧不能再对当前RLC层缓存的在类型转换前收到的RLC SDU进行级联和分割的操作。
在此基础上，第二种可能的设计中，所述终端设备获取第一指示信息，包括：
所述终端设备接收所述基站发送的所述至少一个无线承载的RLC控制协议数据单元；所述RLC控制协议数据单元中包含所述第一指示信息。
例如，首先，新定义一种RLC控制PDU。所述RLC控制PDU用来通知第一指示信息中包含的上述RLC序列号，所述RLC序列号为所述终端设备的至少一个无线承载的RLC PDU的序列号，该RLC PDU为包含按照类型转换后对应的包格式封装的RLC SDU的第一个RLC PDU所对应的序列号。或者，该RLC PDU为包含按照类型转换前对应的包格式封装的RLC SDU的最后一个RLC PDU所对应的序列号。
其次，基站在发生类型的转换的无线承载上发送该无线承载相应的上述RLC控制PDU。因此，当终端设备在该无线承载上收到所述RLC控制PDU后，便可以获知针对该无线承载上传输的RLC PDU中包含的数据部分，哪些需要递交给PDCP层，哪些需要递交给Adaptation layer层。
可选的，如图10所示，基站侧通过该无线承载的RLC层实体下发包含上述RLC控制PDU的第一指示信息，终端设备侧通过该无线承载的RLC层实体接收基站发送的包含上述RLC控制PDU的第一指示信息。
可选的，如图11(a)、如图11(b)和如图11(c)所示，RLC控制PDU的3种格式示例，分别对应RLC SN的长度为5bit，10bit和16bit。其中，RLC控制PDU的格式中包含的各个字段的含义如下：
D/C字段占用1bit，用于指示包含RLC序列号的RLC PDU为RLC数据PDU还是RLC控制PDU。
CPT字段占用3bit，用于指示该控制PDU的类型(control PDU type)，如果是RLC控制PDU，用于指示该控制PDU的类型。目前该域的取值的定义如下表1所示。针对所述新定义的控制PDU，需要用目前的一个预留值来只指示其类型。例如，可以用001来表示所述新定义的control PDU。
R为预留比特。
SN：为该RLC PDU的序列号，可以为包含按照类型转换后对应的包格式封装的RLC SDU的第一个RLC PDU所对应的序列号，或者包含按照类型转换前对应的包格式封装的RLC SDU的最后一个RLC PDU所对应的序列号。其长度可以为5bit，10bit和16bit。实际使用长度由基站配置。
可选的，对于下行数据传输，该控制PDU的一种产生时机为：当基站的RLC层实体在传输完包含最后一个类型转换前从上层实体接收到的RLC SDU的RLC PDU后；或者基站的RLC层实体确定包含最后一个类型转换前从上层实体接收到的RLC SDU的RLC PDU的序列号后，产生所述RLC控制PDU。或者，当基站的RLC层实体在传输完包含第一个类型转换后从上层实体接收到的RLC SDU的RLC PDU后；或者基站的RLC层实体确定包含第一个类型转换后从上层实体接收到的RLC SDU的RLC PDU的序列号后，产生所述RLC控制PDU。
可选的，对于下行数据传输，当一个无线承载发生类型转换后，终端设备的RLC层实体直到接收到基站发送的所述RLC控制PDU后，才将一个RLC PDU组装得到的RLC SDU按序递交给相应的上层实体，即PDCP l层实体或者Adaptation layer实体。
表1
Figure PCTCN2017078199-appb-000001
可选的，在第一指示信息中并不包括RLC序列号时，所述终端设备接收所述基站发送的MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。
基于此，在所述第一指示信息不包含RLC序列号时，所述终端设备根据所述MAC业务数据单元对应的MAC子头中的指示信息，确定所述至少一个无线承载的RLC协议数据单元的上层实体。
可选的，MAC子头中的指示信息包括：指示值为0时，表示该MAC SDU中包含的数据应该在RLC层实体处理后发送给PDCP层实体。指示值为1时，表示该MAC SDU中包含的数据应该在RLC层实体处理后发送给协议适配层实体。或者反过来。
例如：通过MAC层来实现上述通知。
MAC PDU的格式如图12所示，一个MAC PDU中可能包含多个MAC SDU，每个MAC SDU来自一个无线承载的逻辑信道。每个MAC SDU中都有一个与之对应的MAC子头(Subheader)。一个MAC SDU的MAC subheader中包含逻辑信道标识字段(Logical channel ID，LCID)和预留比特(R bit)字段，还包括其它字段。
其中，一个MAC SDU的MAC subheader的LCID字段用于指示该MAC SDU来自于哪个无线承载的逻辑信道。这样，根据LCID，接收端设备便可以知道该逻辑信道对应的MAC SDU应该递交给哪个RLC实体。
其中，一个MAC SDU的MAC subheader中的R字段，现有技术中该R字段的比特的值目前只会设置为0。
本申请中，可以配置一个MAC SDU的MAC subheader中的R字段的比特值为0时，表示该MAC SDU中包含的数据应该在RLC层实体处理后发送给PDCP层实体，R字段的比特值为1时，表示该MAC SDU中包含的数据应该在RLC层实体处理后发送给协议适配层实体。或者反过来也可以。
无论是上行数据传输，还是下行数据传输，对于发送端设备来说，当一个无线承载发生转换后，当该无线承载对应的RLC层实体开始传输包含按照类型转换后的包格式封装的RLC SDU的RLC PDU时，RLC实体在将所述RLC PDU递交给MAC层时，同时通过一个指示通知MAC层，该RLC PDU中包含的是按照类型转换后的包格式封装的RLC SDU。当该无线承载对应的RLC层实体在一段时间内仍然传输包含按照类型转换前的包格式封装的RLC SDU的RLC PDU时，RLC实体在将所述RLC PDU递交给MAC层实体时，同时通过一个指示通知MAC层，该RLC PDU中包含的是按照类型转换前的包格式封装的RLC SDU。无论是上行数据传输，还是下行数据传输，对于接收端设备来说，在MAC层实体收到一个MAC PDU后，根据每个MAC SDU对应的subheader中的LCID，判断所述每个MAC SDU是否来自一个发生类型转换的无线承载。如果是，那么根据其subheader中的Rbit的值，判断该MAC SDU中包含的RLC的数据包的包格式。并在递交MAC SDU给RLC层时，同时通知RLC层实体RLC数据包的包格式。RLC层实体根据MAC层实体通知的结果，便知道将RLC数据包中包含的数据部分递交给PDCP层实体，还是递交给协议适配层实体。
上述方法流程是基站向终端设备发送第一指示信息，来指示在所述至少一个无线承载类型转换后，所述终端设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
对于上行数据的传输，为了让基站知道在一个无线承载发生类型转换后，接收到的来自该无线承载上的数据包在RLC层处理完后需要递交给PDCP层还是递交给Adaptation layer层，eRelay UE需要向基站发送通知。
基于此发明构思，终端设备侧的数据处理方法，还包括：
所述终端设备向所述基站发送第二指示信息；所述第二指示信息用于通知在所述至少一个无线承载类型转换后，所述基站接收到的所述至少一个无线承载的数据的无线承载类 型为第一类型无线承载或第二类型无线承载。
可选的，所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
在此基础上，第一种可能的实现方式中，所述终端设备向所述基站发送所述至少一个无线承载的RRC连接重配完成消息，所述RRC连接重配完成消息中包括所述第二指示信息。
例如，终端通过RRC连接重配完成消息(RRC Connection Reconfiguration Complete)通知基站所述发生类型转换的无线承载上传输的一个RLC PDU所对应的RLC序列号，该RLC PDU包含按照类型转换后对应的包格式封装的RLC SDU的第一个RLC PDU所对应的序列号；或者该RLC PDU包含按照类型转换前对应的包格式封装的RLC SDU的最后一个RLC PDU所对应的序列号。
其中，eRelay UE通过RRC连接重配完成消息通知基站相应的RLC序列号的实现方式，与上述方法流程中基站通过RRC连接重配消息通知eRelay UE相应的RLC序列号的实现方式类似，此处不再累述。
值得说明的是，在此实施例中，当eRelay UE通过RRC连接重配完成消息通知基站相应的RLC序列号后，基站和eRelay UE侧不能再对当前RLC层缓存的在类型转换前收到的RLC SDU进行级联和分割的操作。
在此基础上，第二种可能的设计中，所述终端设备向所述基站发送所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包括所述第二指示信息。其中，所述RLC控制协议数据单元是所述第一用户设备的所述至少一个无线承载的RLC层实体确定类型转换前处理的最后一个RLC PDU的序列号之后生成的。
可选的，对于上行数据传输，终端设备通过该无线承载的RLC层实体向基站发送包含上述RLC控制PDU的第一指示信息，基站通过该无线承载的RLC层实体接收终端设备发送的包含上述RLC控制PDU的第一指示信息。
对于上行数据传输，终端设备通过RLC控制PDU通知基站第一指示信息中的RLC序列号方式，与上述实施例中基站向终端通知第一指示信息中的RLC序列号的方式相似，此处不再累述。
对于上行数据传输，基站根据RLC控制PDU指示的RLC序列号，可以获知RLC数据包的包格式的方式，以及将一个RLC PDU组装得到的RLC SDU按序递交给PDCP层实体，还是递交给协议适配层实体。
可选的，对于上行数据传输，该控制PDU的一种产生时机为：当终端设备的RLC层实体在传输完包含最后一个类型转换前从上层实体接收到的RLC SDU的RLC PDU后；或者终端设备的RLC层实体确定包含最后一个类型转换前从上层实体接收到的RLC SDU的RLC PDU的序列号后，产生所述RLC控制PDU。或者，当终端设备的RLC层实体在传输完包含第一个类型转换后从上层实体接收到的RLC SDU的RLC PDU后；或者终端设备的RLC层实体确定包含第一个类型转换后从上层实体接收到的RLC SDU的RLC PDU的序列号后，产生所述RLC控制PDU。
可选的，对于上行数据传输，当一个无线承载发生类型转换后，基站的RLC层实体直 到接收到终端设备发送的所述RLC控制PDU后，才将一个RLC PDU组装得到的RLC SDU按序递交给相应的上层实体，即PDCP l层实体或者Adaptation layer实体。
可选的，当所述第二指示信息不包含RLC序列号时，一种可能的实现方式中，所述终端设备向所述基站发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第二指示信息。具体实现方式参见上述实施例中的相关内容，此处不再累述。
基于相同的发明构思，本申请还提供了基站侧的数据处理方法，来解决当一个终端设备的无线承载的类型发生第I类型和第III类型间的转换时，如何避免产生丢包的技术问题。
本申请提供的基站侧的数据处理方法，包括：
基站配置终端设备的至少一个无线承载的类型由第一类型转换为第二类型；
在进行下行数据传输时，基站向终端设备发送第一指示信息，其中，所述第一指示信息用于指示在所述终端设备的至少一个无线承载类型转换后，所述终端设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
可选的，所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
进一步的，所述基站向所述终端设备发送所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息；或者，
所述基站向所述终端设备发送所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包含所述第一指示信息。
可选的，所述基站向所述终端设备发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。
可选的，还包括：
所述基站接收所述终端设备发送的第二指示信息，所述第二指示信息用于指示在所述至少一个无线承载类型转换后，所述基站接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
在所述基站获取第一指示信息之后还包括：
所述基站接收所述至少一个无线承载的RLC协议数据单元；所述基站根据所述第一指示信息和所述至少一个无线承载的RLC协议数据单元的序列号，确定所述至少一个无线承载的RLC协议数据单元的上层实体。
可选的，所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
在所述第二指示信息包含RLC序列号时，所述基站根据所述第一指示信息和所述至少 一个无线承载的RLC协议数据单元的序列号，确定所述至少一个无线承载的RLC协议数据单元的上层实体，具体包括：
基站根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；
基站根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体为PDCP层实体还是协议适配层实体。
进一步的，所述基站接收所述终端设备发送的所述至少一个无线承载的RRC连接重配完成消息，所述RRC连接重配完成消息中包含所述第二指示信息；或者，
所述基站接收所述终端设备发送的所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包含所述第二指示信息。
进一步的，所述基站接收所述终端设备发送的所述至少一个无线承载的RRC连接重配完成消息，所述第二指示信息包含在所述RRC连接重配完成消息中。
在所述第一指示信息不包含RLC序列号时，所述基站接收所述终端设备发送的发送的MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中包括所述第二指示信息。
在所述第一指示信息不包含RLC序列号时，所述基站根据所述MAC业务数据单元对应的MAC子头中的指示信息，确定所述至少一个无线承载的RLC协议数据单元的上层实体。
可选的，MAC子头中的指示信息包括：指示值为0时，表示该MAC SDU中包含的数据应该在RLC层实体处理后发送给PDCP层实体指示值为1时，表示该MAC SDU中包含的数据应该在RLC层实体处理后发送给协议适配层实体。或者反过来。
基站侧的数据处理方法与前述终端侧的数据处理方法相同，此处不再详述。
除了上述两种数据处理方法，本申请还提供第三种数据处理方法，用以实现如何通知终端设备的至少一个无线承载的类型由第一类型无线承载转换为第二类型无线承载。
本申请提供的终端侧的第三种数据处理方法，主要包括：
终端设备接收基站发送的第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载；
根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载。
一种可能的实施例中，所述终端设备根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载，包括：
所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，
若所述第一配置信息中包括第三指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
其中，所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议 层实体，RLC层实体和逻辑信道；所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
在此实施例中，终端设备根据第一配置信息，可以确定出所述终端设备的至少一个无线承载由第III类型无线承载转换为第I类型无线承载。
一种可能的实施例中，所述终端设备根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载，包括：
所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，
若所述第一配置信息中不包括第四指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
其中，所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道，所述第四指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。
在此实施例中，终端设备根据第一配置信息，可以确定出所述终端设备的至少一个无线承载由第I类型无线承载转换为第III类型无线承载。
可选的，所述第一配置信息包含于RRC连接重配置消息中。
本申请提供的基站侧的第三种数据处理方法，主要包括：
基站向所述终端设备发送第一配置信息，所述第一配置信息用于配置将所述终端设备的至少一个无线承载的类型由第一类型无线承载转换为第二类型无线承载，其中，所述第一配置信息中至少包括所述至少一个无线承载的标识。
一种可能的实施例中，为了配置所述终端设备的至少一个无线承载由第III类型无线承载转换为第I类型无线承载，即若所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；则所述第一配置信息包括所述至少一个无线承载的标识，还包括第三指示信息，所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
可选的，所述第一配置信息包含于RRC连接重配置消息中。
一种可能的实施例中，为了配置所述终端设备的至少一个无线承载由第I类型无线承载转换为第III类型无线承载，即若所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；则
所述第一配置信息中包括所述至少一个无线承载的标识，但不包括第四指示信息，所述第四指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。
可选的，所述第一配置信息包含于RRC连接重配置消息中。
下面结合具体的实施例进行说明。
当基站为eRelay UE新配置一个无线承载时，需要让eRelay UE知道该无线承载的类型。当基站为eRelay UE重配置一个无线承载时，需要让eRelay UE知道是保持无线承载 的类型不变，重新配置其相关参数还是通过重配来改变无线承载的类型。目前增加和修改数据无线承载和信令无线承载，分别是通过在RRC连接重配消息中包含SRB-To AddMod信息和DRB-To Add Mod信息来实现的。
基于此，可以基于SRB-To AddMod信息和DRB-To Add Mod信息来配置指示信息，以便指示当前配置的SRB或SRB从第III类型无线承载转换为第I类型无线承载，以及指示当前配置的SRB或SRB从第I类型无线承载转换为第III类型无线承载。
一种可能的实现方式中，对于SRB和DRB，在SRB-ToAddMod和DRB-ToAddMod包含的信息中增加指示信息A，指示所述配置的无线承载为第I类型无线承载不是第III类型无线承载。对于SRB和DRB，在所述指示信息A中增加一个指示信息B，用来指示无线承载类型的转换。对于DRB，通过DRB-ToAddMod中包含对应当EPS bearer ID来指示所述增加的无线承载不是第II类型无线承载。
基于上述配置方法，对于eRelay UE的一个无线承载的增加，重配以及类型转换指示如下：
步骤1：当eRelay UE接收到基站发送的包含DRB-ToAddMod的RRC连接重配消息时，对于一个包含在DRB-ToAddMod中的DRB ID：
如果该DRB不是eRelay UE当前配置的DRB，那么该情况对应于新增加一个DRB的情况，进入步骤2；
如果该DRB是eRelay UE当前配置的DRB，进入步骤3:；
步骤2：在确定是新增加一个DRB的情况下，如果在DRB-ToAddMod中包含EPS bearer ID，但是不包含上述指示信息A，那么该情况对应为新增加一个第III类型的DRB；
在确定是新增加一个DRB的情况下，如果在DRB-ToAddMod中不包含EPS bearer ID，但是包含上述指示信息A，那么该情况对应为新增加一个第II类型的DRB；
在确定是新增加一个DRB的情况下，如果在DRB-ToAddMod中包含EPS bearer ID，同时包含上述指示信息A，那么该情况对应为新增加一个第I类型的DRB；
步骤3：在确定该DRB是eRelay UE当前配置的一个DRB的情况下，要么重配置所述DRB的情况，要么是对所述DRB进行类型转换的情况；
进一步的，如果所述DRB为一个第III类型的DRB，且DRB-ToAddMod中不包含所述指示信息A，那么该情况对应为重配置所述DRB；
进一步的，如果所述DRB为一个第III类型的DRB，且DRB-ToAddMod中包含所述指示信息A，那么该情况对应为将所述DRB从第III类型DR转换为第I类型DRB；
进一步的，如果所述DRB为一个第II类型的DRB，且DRB-ToAddMod中包含所述指示信息A，但是所述指示信息A中不包含所述指示信息B，那么该情况对应为重配置所述DRB；
进一步的，如果所述DRB为一个第II类型的DRB，且DRB-ToAddMod中包含所述指示信息A，同时所述指示信息A中包含所述指示信息B，那么该情况对应为将所述DRB从第II类型DRB转换为第I类型DRB；
进一步的，如果所述DRB为一个第I类型的DRB，且DRB-ToAddMod中包含所述指示信息A，但是所述指示信息A中不包含所述指示信息B，那么该情况对应为重配置所述DRB；
进一步的，如果所述DRB为一个第I类型的DRB，且DRB-ToAddMod中包含所述指 示信息A，同时所述指示信息A中包含所述指示信息B，那么该情况对应为将所述DRB从第I类型DRB转换为第二类型DRB；
进一步的，如果所述DRB为一个第I类型的DRB，且DRB-ToAddMod中不包含所述指示信息A，那么该情况对应为将所述DRB从第I类型DRB转换为第III类型DRB。
SRB只有第I类型和第III类型，因此，SRB的增加，重配和类型转换的配置方法同上，除了不涉及所有与第II类型无线承载相关的配置。
基于上述方法实施例，本申请实施例还提供一种基站和终端设备，用以解决现有技术中存在的当一个无线承载的类型发生第I类型和第III类型间的转换时，如何避免产生丢包的技术问题的问题。基站和终端设备执行的相关方法步骤与上述方法实施例中的实施可以相互参见，重复之处不再赘述。
基于相同构思，本申请实施例提供的一种用于执行数据处理方法的终端设备，如图13所示，该终端设备1000包括处理器1001和收发器1004，其中：
收发器1004，用于支持终端与基站之间的通信，向基站发送上述通信系统中资源分配的方法中所涉及的信息或者指令。
处理器1001被配置为支持终端执行上述数据处理方法中相应的功能。
可选地，还包括存储器1002和通信接口1003；其中，处理器1001、存储器1002、通信接口1003和收发器1004通过总线1005相互连接。
可选地，所述存储器用于与处理器耦合，其保存终端必要的程序指令和数据。
处理器1001可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
存储器1002以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。
通信接口1003可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为WLAN接口。
收发器1004可以是有线收发机，无线收发机或其组合。有线收发机例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线收发机例如可以为无线局域网通信接口，蜂窝网络通信接口或其组合。
总线1005可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。总线1005可以包括任意数量的互联的总线和桥，具体由处理器代表的一个或多个处理器1001和存储器1002代表的存储器的各种电路链接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在 一起，本申请不再对其进行进一步描述。收发器1004提供用于在传输介质上与各种其他设备通信的单元。处理器1001负责管理总线架构和通常的处理，存储器1002可以存储处理器1001在执行操作时所使用的数据。
本申请的处理器1001、收发器1004既可以执行本申请第一种数据处理方法中与终端设备有关的步骤，又可以执行本申请第二种数据处理方法中与终端设备有关的步骤。
本申请的处理器1001、收发器1004既执行本申请第一种数据处理方法中与终端设备有关的步骤时具体包括：
处理器1001，用于确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；丢弃所述至少一个无线承载的无线链路控制协议RLC层实体发送侧缓存的RLC协议数据单元和/或RLC业务数据单元；将所述至少一个无线承载的RLC层实体接收侧已接收到的RLC协议数据单元组装成RLC业务数据单元，并将所述RLC业务数据单元按序递交给所述RLC层实体的上层实体；其中，所述上层实体为所述至少一个无线承载类型转换前所述RLC层实体的上层实体。
可选的，处理器1001，还用于：停止并重置所述至少一个无线承载的RLC层实体的所有计时器；以及将所述至少一个无线承载的RLC层实体的所有状态变量重置为初始值。
可选的，所述至少一个无线承载的类型为第一类型时，所述RLC层实体的上层实体为分组数据汇聚协议PDCP层实体；所述至少一个无线承载的类型为第二类型时，所述RLC层实体的上层实体为适配协议层实体；
或者，所述至少一个无线承载的类型为第一类型时，所述RLC层实体的上层实体为适配协议层实体；所述至少一个无线承载的类型为第二类型时，所述RLC层实体的上层实体为所述PDCP层实体。
可选的，若所述至少一个无线承载为使用RLC确认模式的数据无线承载或使用RLC确认模式的信令无线承载，处理器1001，还用于：重传所述至少一个无线承载的PDCP层实体未发送成功的PDCP协议数据单元，所述PDCP协议数据单元为所述至少一个无线承载类型转换前递交给底层实体，但所述底层实体还未反馈确认成功接收的PDCP协议数据单元；其中，所述底层实体为所述至少一个无线承载类型转换前所述PDCP层实体的底层实体；
所述终端设备生成并发送PDCP状态报告，所述PDCP状态报告用于通知基站未成功接收的PDCP业务数据单元的序列号。
可选的，若所述至少一个无线承载为使用RLC确认模式的信令无线承载，处理器1001，还用于：将所述至少一个无线承载的PDCP实体用于记录下一个发送的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0；将所述至少一个无线承载的PDCP实体用于记录下一个接收的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0。
可选的，处理器1001，还用于重置媒体接入控制MAC层实体。
可选的，处理器1001，还用于执行以下特征中的至少一个：
清空媒体接入控制MAC层实体的全部上行HARQ进程的缓存，
将所有上行HARQ进程的新数据指示信息置为0，
清空媒体接入控制MAC层实体的全部下行HARQ进程的缓存，
针对每一下行HARQ进程，将其后续接收到的传输块视为该传输块的第一次传输。
可选的，处理器1001，还用于接收所述至少一个无线承载在类型转换后的MAC协议 数据单元；
若所述MAC协议数据单元的初次接收是在所述至少一个无线承载类型转换前，且所述MAC协议数据单元中包含所述至少一个无线承载的MAC业务数据单元，则将所述至少一个无线承载的所述MAC业务数据单元丢弃。
本申请的处理器1001、收发器1004执行本申请第二种数据处理方法中与终端设备有关的步骤时具体包括：
终端1000的处理器1001和收发器1004执行以下功能：
处理器1001用于：确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；获取第一指示信息，所述第一指示信息用于指示在所述至少一个无线承载类型转换后，所述终端设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
可选的，所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
可选的，收发器1004用于：接收基站发送的所述至少一个无线承载的RLC协议数据单元；
处理器1001还用于：根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体，所述上层实体为所述至少一个无线承载类型转换前，或者所述至少一个无线承载类型转换后所述至少一个无线承载的RLC协议层的上层实体。
可选的，收发器1004用于：接收基站发送的所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息；或者，接收所述基站发送的所述至少一个无线承载的RLC控制协议数据单元；所述RLC控制协议数据单元中包含所述第一指示信息。
可选的，收发器1004用于：接收所述基站发送的MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。
可选的，收发器1004还用于：向所述基站发送第二指示信息；所述第二指示信息用于通知在所述至少一个无线承载类型转换后，所述基站接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
可选的，所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
可选的，收发器1004用于：向所述基站发送所述至少一个无线承载的RRC连接重配 完成消息，所述RRC连接重配完成消息中包括所述第二指示信息；或者，向所述基站发送所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包括所述第二指示信息。
可选的，收发器1004用于：向所述基站发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第二指示信息。
本申请的处理器1001、收发器1004还可执行本申请第三种数据处理方法中与终端设备有关的步骤时具体包括：
收发器1004用于：接收基站发送的第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载；
处理器1001用于：根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载。
可选的，处理器1001用于：根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，若所述第一配置信息中包括第三指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
其中，所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
可选的，处理器1001用于：所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，若所述第一配置信息中不包括第五指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
其中，所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道，所述第五指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。
在一种可能的实现方式中，该终端包括多个功能模块，用于执行本申请所涉及的前述实施例中与终端相关的方法步骤，解决如何避免产生丢包的技术问题。
如图14所示，终端2000包括处理单元2001和收发单元2002。需要说明的是，处理单元2001或者收发单元2002所执行的操作都可以视为是终端2000的操作。所述终端2000中的处理单元2001可以由终端2000中的处理器实现，所述收发单元2002可以由终端2000中的收发器实现。
关于该终端内装置或器件的功能的详细描述可以参照本申请前述实施例的相关内容，在此不做赘述。
基于相同构思，本申请提供一种基站3000，如图15所示，该基站3000包括处理器3001和收发器3004，其中：
收发器3004，用于支持终端与基站之间的通信，向终端设备发送上述数据处理方法中 所涉及的信息或者指令。
处理器3001被配置为支持基站执行上述数据处理方法中相应的功能。
可选地，还包括存储器3002和通信接口3003；其中，处理器3001、存储器3002、通信接口3003和收发器3004通过总线3005相互连接。
可选地，所述存储器用于与处理器耦合，其保存基站必要的程序指令和数据。
处理器3001可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
存储器3002以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。
通信接口3003可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为WLAN接口。
收发器3004可以是有线收发机，无线收发机或其组合。有线收发机例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线收发机例如可以为无线局域网通信接口，蜂窝网络通信接口或其组合。
总线3005可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。总线3005可以包括任意数量的互联的总线和桥，具体由处理器代表的一个或多个处理器3001和存储器3002代表的存储器的各种电路链接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，本申请不再对其进行进一步描述。收发器3004提供用于在传输介质上与各种其他设备通信的单元。处理器3001负责管理总线架构和通常的处理，存储器3002可以存储处理器3001在执行操作时所使用的数据。
本申请的处理器3001、收发器3004即可用于执行本申请第一种数据处理方法中与基站有关的步骤，又可以执行本申请第二种数据处理方法中与基站有关的步骤，还可以执行本申请第三种数据处理方法中与基站有关的步骤。
本申请的处理器3001、收发器3004用于执行本申请第一种数据处理方法中与基站有关的步骤时具体包括：
收发器3004用于接收终端设备发送的PDCP状态报告，所述状态报告用于通知基站未成功接收的PDCP业务数据单元的序列号。
本申请的处理器3001、收发器3004用于执行本申请第二种数据处理方法中与基站有关的步骤时具体包括：具体的，收发器3004用于：向终端设备发送第一指示信息，其中，所述第一指示信息用于指示在所述终端设备的至少一个无线承载类型转换后，所述终端设 备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
可选的，所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
可选的，收发器3004用于：向所述终端设备发送所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息；或者，向所述终端设备发送所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包含所述第一指示信息。
可选的，收发器3004用于：向所述终端设备发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。可选的，收发器3004用于：接收所述终端设备发送的第二指示信息，所述第二指示信息用于指示在所述至少一个无线承载类型转换后，所述基站接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
可选的，所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
处理器3001用于：在所述第二指示信息包含RLC序列号时，根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体为PDCP层实体还是协议适配层实体。
可选的，收发器3004用于：接收所述终端设备发送的所述至少一个无线承载的RRC连接重配完成消息，所述RRC连接重配完成消息中包含所述第二指示信息；或者，
所述基站接收所述终端设备发送的所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包含所述第二指示信息。
可选的，收发器3004用于：接收所述终端设备发送的所述至少一个无线承载的RRC连接重配完成消息，所述至少一个无线承载的RRC连接重配完成消息中包括所述第二指示信息。
可选的，收发器3004用于：接收所述终端设备发送的所述至少一个无线承载的MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中包括所述第二指示信息。
本申请的处理器3001、收发器3004用于执行本申请第三种数据处理方法中与基站有关的步骤时具体包括：
收发器3004用于：向终端设备发送第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载。
可选的，若所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；则所述第一配置信息包括所述至少一个无线承载的标识，还包括第三指示信息，所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
可选的，若所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；则所述第一配置信息中包括所述至少一个无线承载的标识，但不包括第五指示信息，所述第五指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。在一种可能的实现方式中，该基站包括多个功能模块，用于执行本申请所涉及的各种实施例中与基站相关的方法步骤，使得。
如图16所示的基站4000包括处理单元4001和收发单元4002。所述处理单元4001或者所述收发单元4002所执行的操作都可以视为是基站4000的操作。所述基站4000中的处理单元4001可以由基站4000的处理器实现，所述收发单元4002可以由基站4000中的收发器实现。
关于该基站内装置或器件的功能的详细描述可以参照本申请其他实施例的相关内容，在此不做赘述。
基于相同构思，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行本申请所涉及的各种实施例中与终端相关的方法步骤。
基于相同构思，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行本申请所涉及的各种实施例中与基站相关的方法步骤。
基于相同构思，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行本申请所涉及的各种实施例中与终端相关的方法步骤。
基于相同构思，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行本申请所涉及的各种实施例中与基站相关的方法步骤。
本所属领域的技术人员可以清楚地了解到，本发明提供的各实施例的描述可以相互参照，为描述的方便和简洁，关于本发明实施例提供的各装置、设备的功能以及执行的步骤可以参照本发明方法实施例的相关描述，在此不做赘述。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。为清楚展示硬件和软件的可替换性(interchangeability)，上述的各种说明性部件(illustrative components)和步骤已经通用地描述了它们的功能。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本发明实施例保护的范围。
本申请实施例中所描述的各种说明性的逻辑块，模块和电路可以通过通用处理单元， 数字信号处理单元，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理单元可以为微处理单元，可选地，该通用处理单元也可以为任何传统的处理单元、控制器、微控制器或状态机。处理单元也可以通过计算装置的组合来实现，例如数字信号处理单元和微处理单元，多个微处理单元，一个或多个微处理单元联合一个数字信号处理单元核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理单元执行的软件模块、或者这两者的结合。软件模块可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理单元连接，以使得处理单元可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理单元中。处理单元和存储媒介可以配置于ASIC中，ASIC可以配置于用户终端中。可选地，处理单元和存储媒介也可以配置于用户终端中的不同的部件中。
在一个或多个示例性的设计中，本发明实施例所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理单元读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、DVD、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本申请的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。

Claims (28)

  1. 一种数据处理方法，其特征在于，包括：
    终端设备确定所述终端设备的至少一个无线承载的类型由第一类型转换为第二类型；
    所述终端设备丢弃所述至少一个无线承载的无线链路控制协议RLC层实体发送侧缓存的RLC协议数据单元和/或RLC业务数据单元；
    所述终端设备将所述至少一个无线承载的RLC层实体接收侧已接收到的RLC协议数据单元组装成RLC业务数据单元，并将所述RLC业务数据单元按序递交给所述RLC层实体的上层实体；其中，所述上层实体为所述至少一个无线承载类型转换前所述RLC层实体的上层实体。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    所述终端设备停止并重置所述至少一个无线承载的RLC层实体的所有计时器；以及
    所述终端设备将所述至少一个无线承载的RLC层实体的所有状态变量重置为初始值。
  3. 根据权利要求2所述的方法，其特征在于，
    所述至少一个无线承载的类型为第一类型时，所述RLC层实体的上层实体为分组数据汇聚协议PDCP层实体；所述至少一个无线承载的类型为第二类型时，所述RLC层实体的上层实体为适配协议层实体；或者，
    所述至少一个无线承载的类型为第一类型时，所述RLC层实体的上层实体为适配协议层实体；所述至少一个无线承载的类型为第二类型时，所述RLC层实体的上层实体为所述PDCP层实体。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，若所述至少一个无线承载为使用RLC确认模式的数据无线承载或使用RLC确认模式的信令无线承载，还包括：
    所述终端设备重传所述至少一个无线承载的PDCP层实体未发送成功的PDCP协议数据单元，所述PDCP协议数据单元为所述至少一个无线承载类型转换前递交给底层实体，但所述底层实体还未反馈确认成功接收的PDCP协议数据单元；其中，所述底层实体为所述至少一个无线承载类型转换前所述PDCP层实体的底层实体；
    所述终端设备生成并发送PDCP状态报告，所述PDCP状态报告用于通知基站未成功接收的PDCP业务数据单元的序列号。
  5. 根据权利要求1至3中任一项所述的方法，其特征在于，若所述至少一个无线承载为使用RLC确认模式的信令无线承载，还包括：
    所述终端设备将所述至少一个无线承载的PDCP实体用于记录下一个发送的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0；
    所述终端设备将所述至少一个无线承载的PDCP实体用于记录下一个接收的PDCP业务数据单元的序列号的变量的值以及超帧号的值重置为0。
  6. 根据权利要求1至3中任一项所述的方法，其特征在于，还包括：
    所述终端设备重置媒体接入控制MAC层实体。
  7. 根据权利要求1至3中任一项所述的方法，其特征在于，还包括以下特征中的至少一个：
    所述终端设备清空媒体接入控制MAC层实体的全部上行HARQ进程的缓存，
    所述终端设备将所有上行HARQ进程的新数据指示信息置为0，
    所述终端设备清空媒体接入控制MAC层实体的全部下行HARQ进程的缓存，
    所述终端设备针对每一下行HARQ进程，将其后续接收到的传输块视为该传输块的第一次传输。
  8. 根据权利要求1至3中任一项所述的方法，其特征在于，还包括：
    所述终端设备的媒体接入控制MAC层实体接收所述至少一个无线承载在类型转换后的MAC协议数据单元；
    若所述MAC协议数据单元的初次接收是在所述至少一个无线承载类型转换前，且所述MAC协议数据单元中包含所述至少一个无线承载的MAC业务数据单元，则将所述至少一个无线承载的所述MAC业务数据单元丢弃。
  9. 一种数据处理方法，其特征在于，包括：
    第一设备确定所述第一设备的至少一个无线承载的类型由第一类型转换为第二类型；
    所述第一设备接收第二设备发送的第一指示信息，所述第一指示信息用于指示所述第一设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载；
    其中，所述第一设备为终端设备，所述第二设备为基站；或者，所述第一设备为基站，所述第二设备为终端设备。
  10. 根据权利要求9所述的方法，其特征在于，
    所述第一指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    所述第一设备接收所述至少一个无线承载的RLC协议数据单元；
    所述第一设备根据所述第一指示信息和所述接收到的至少一个无线承载的RLC协议数据单元的序列号，确定所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型为第一类型无线承载或第二类型无线承载；
    所述第一设备根据所述接收到的至少一个无线承载的RLC协议数据单元的无线承载类型，确定所述接收到的至少一个无线承载的RLC协议数据单元的上层实体，所述上层实体为所述至少一个无线承载类型转换前，或者所述至少一个无线承载类型转换后所述至少一个无线承载的RLC协议层的上层实体。
  12. 根据权利要求10所述的方法，其特征在于，所述第一设备获取第一指示信息，包括：
    所述第一设备接收第二设备发送的所述至少一个无线承载的RRC连接重配消息，所述RRC连接重配消息中包含所述第一指示信息或者，
    所述第一设备接收所述第二设备发送的所述至少一个无线承载的RLC控制协议数据单元；所述RLC控制协议数据单元中包含所述第一指示信息。
  13. 根据权利要求9所述的方法，其特征在于，所述第一设备获取第一指示信息，包括：
    所述第一设备接收所述第二设备发送的MAC协议数据单元，所述MAC协议数据单 元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第一指示信息。
  14. 根据权利要求9所述的方法，其特征在于，还包括：
    所述第一设备向所述第二设备发送第二指示信息；所述第二指示信息用于通知所述第二设备接收到的所述至少一个无线承载的数据的无线承载类型为第一类型无线承载或第二类型无线承载。
  15. 根据权利要求14所述的方法，其特征在于，
    所述第二指示信息包含RLC序列号，所述RLC序列号为所述至少一个无线承载的RLC协议数据单元的序列号，所述RLC协议数据单元是指包含按照所述第一类型无线承载的格式封装的RLC业务数据单元的最后一个RLC协议数据单元，或者，所述RLC协议数据单元是指包含按照所述第二类型无线承载的格式封装的RLC业务数据单元的第一个RLC协议数据单元。
  16. 根据权利要求15所述的方法，其特征在于，所述第一设备向所述第二设备发送第二指示信息，包括：
    所述第一设备向所述第二设备发送所述至少一个无线承载的RRC连接重配完成消息，所述RRC连接重配完成消息中包括所述第二指示信息；或者，
    所述第一设备向所述第二设备发送所述至少一个无线承载的RLC控制协议数据单元，所述RLC控制协议数据单元中包括所述第二指示信息。
  17. 根据权利要求14所述的方法，其特征在于，所述第一设备向所述第二设备发送第二指示信息，包括：
    所述第一设备向所述第二设备发送MAC协议数据单元，所述MAC协议数据单元包括所述至少一个无线承载的MAC业务数据单元，所述MAC业务数据单元对应的MAC子头中携带所述第二指示信息。
  18. 一种数据处理方法，其特征在于，包括：
    终端设备接收基站发送的第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载；
    根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载。
  19. 根据权利要求18所述的方法，其特征在于，所述终端设备根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载，包括：
    所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，
    若所述第一配置信息中包括第三指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
    其中，所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
  20. 根据权利要求18所述的方法，其特征在于，所述终端设备根据所述第一配置信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载，包括：
    所述终端设备根据所述第一配置信息中携带的所述至少一个无线承载的标识，确定所述至少一个无线承载为当前配置的无线承载，且确定所述至少一个无线承载的类型为第一类型无线承载时，
    若所述第一配置信息中不包括第五指示信息，确定所述至少一个无线承载的类型由所述第一类型无线承载转换为所述第二类型无线承载；
    其中，所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道，所述第五指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。
  21. 一种数据处理方法，其特征在于，包括：
    基站向终端设备发送第一配置信息，所述第一配置信息，用于配置所述终端设备的至少一个无线承载由第一类型无线承载转换为第二类型无线承载。
  22. 根据权利要求21所述的方法，其特征在于，若所述第一类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；所述第二类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；则
    所述第一配置信息包括所述至少一个无线承载的标识，还包括第三指示信息，所述第三指示信息用于指示所述终端设备配置的无线承载的类型为所述第二类型无线承载。
  23. 根据权利要求21所述的方法，其特征在于，若所述第一类型无线承载包括：PDCP层实体，所述适配协议层实体，RLC层实体和逻辑信道；所述第二类型无线承载包括：分组数据汇聚协议PDCP层实体，无线链路控制协议RLC层实体和逻辑信道；则
    所述第一配置信息中包括所述至少一个无线承载的标识，但不包括第五指示信息，所述第五指示信息用于指示所述终端设备配置的无线承载的类型为所述第一类型无线承载。
  24. 一种终端设备，其特征在于，所述终端设备包括存储器、收发器和处理器，其中：
    所述存储器用于存储指令；
    所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述终端设备用于执行权利要求1-8中任一权利要求所述的方法。
  25. 一种终端设备，其特征在于，所述终端设备包括存储器、收发器和处理器，其中：
    所述存储器用于存储指令；
    所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述终端设备用于执行权利要求9-17中任一权利要求所述的方法。
  26. 一种基站，其特征在于，所述基站包括存储器、收发器和处理器，其中：所述存储器用于存储指令；
    所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述基站用于执行权利要求9-17中任一权利要求所述的方法。
  27. 一种终端设备，其特征在于，所述终端设备包括存储器、收发器和处理器，其中：
    所述存储器用于存储指令；
    所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述终端设备用于执行权利要求18-20中任一权利要求所述的方法。
  28. 一种基站，其特征在于，所述基站包括存储器、收发器和处理器，其中：所述存储器用于存储指令；
    所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述基站用于执行权利要求21-23中任一权利要求所述的方法。
PCT/CN2017/078199 2017-03-13 2017-03-24 一种数据处理方法及终端设备、基站 WO2018165995A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17900535.0A EP3585087B1 (en) 2017-03-13 2017-03-24 Data processing method and base station for handling change of radio bearer type
US16/492,969 US11096184B2 (en) 2017-03-13 2017-03-24 Data processing method, terminal device, and base station
CN201780032825.3A CN109196902B (zh) 2017-03-13 2017-03-24 一种数据处理方法及终端设备、基站
US17/375,290 US11924870B2 (en) 2017-03-13 2021-07-14 Data processing method, terminal device, and base station using RLC sequence numbers

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710147480.8 2017-03-13
CN201710147480 2017-03-13

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/492,969 A-371-Of-International US11096184B2 (en) 2017-03-13 2017-03-24 Data processing method, terminal device, and base station
US17/375,290 Continuation US11924870B2 (en) 2017-03-13 2021-07-14 Data processing method, terminal device, and base station using RLC sequence numbers

Publications (2)

Publication Number Publication Date
WO2018165995A1 WO2018165995A1 (zh) 2018-09-20
WO2018165995A9 true WO2018165995A9 (zh) 2019-02-21

Family

ID=63522600

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078199 WO2018165995A1 (zh) 2017-03-13 2017-03-24 一种数据处理方法及终端设备、基站

Country Status (4)

Country Link
US (2) US11096184B2 (zh)
EP (1) EP3585087B1 (zh)
CN (1) CN109196902B (zh)
WO (1) WO2018165995A1 (zh)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11147122B2 (en) * 2017-03-22 2021-10-12 Nokia Technologies Oy Data forwarding support
US11082889B2 (en) * 2017-04-25 2021-08-03 Lg Electronics Inc. Method and device for receiving data unit
WO2018232602A1 (zh) * 2017-06-20 2018-12-27 北京小米移动软件有限公司 功能配置方法及装置、消息发送方法及装置和用户设备
WO2019066558A1 (en) 2017-09-29 2019-04-04 Lg Electronics Inc. METHOD AND APPARATUS FOR EMPTYING HARQ BUFFER MEMORY IN WIRELESS COMMUNICATION SYSTEM
US11533136B2 (en) * 2018-01-11 2022-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Discard of PDCP PDU submitted for transmission
CN116017785A (zh) * 2018-02-09 2023-04-25 中兴通讯股份有限公司 Rrc状态转换方法、终端、cu、du和计算机可读存储介质
US10939357B2 (en) * 2018-07-03 2021-03-02 Nokia Solutions And Networks Oy Integrated access and backhaul adaptation layer status report
US12010548B2 (en) * 2018-09-07 2024-06-11 Apple Inc. Apparatus and method for congestion handling in radio access network
WO2020155124A1 (zh) * 2019-02-01 2020-08-06 Oppo广东移动通信有限公司 复制数据的传输方法、终端设备及接入网设备
KR20200099394A (ko) * 2019-02-14 2020-08-24 주식회사 아이티엘 무선통신 시스템에서 harq 재전송을 지원하는 방법 및 장치
US20220272598A1 (en) * 2019-08-07 2022-08-25 Nec Corporation Simultaneous connectivity based handover
CN110572850B (zh) * 2019-09-05 2023-07-25 京信网络系统股份有限公司 5g基站缓存处理业务数据方法、装置、设备和存储介质
WO2021062809A1 (zh) * 2019-09-30 2021-04-08 华为技术有限公司 一种时刻信息的通知方法和装置
WO2021097808A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Methods and apparatus of adaptation handling for sidelink relay
CN114071803A (zh) * 2020-07-31 2022-02-18 中国移动通信有限公司研究院 数据传输方法、终端及网络侧设备
KR20230069197A (ko) * 2020-10-15 2023-05-18 애플 인크. 스플릿 베어러 통신
WO2022133918A1 (zh) * 2020-12-24 2022-06-30 华为技术有限公司 解码失败的处理方法、装置和系统
CN115835238A (zh) * 2021-09-17 2023-03-21 上海华为技术有限公司 一种信息传输方法以及相关设备
CN115996108A (zh) * 2021-10-20 2023-04-21 华为技术有限公司 一种数据传输方法及相关装置
CN114979312B (zh) * 2022-05-27 2024-05-28 山东闻远通信技术有限公司 一种高层业务类型检测方法及装置
WO2024117952A1 (en) * 2022-12-02 2024-06-06 Telefonaktiebolaget Lm Ericsson (Publ) Method performed by a communication device comprising a protocol stack, receiving an indication from an upper layer to clear data in a buffer which data have not been yet submitted to one or more layers below the layer
WO2024164179A1 (en) * 2023-02-08 2024-08-15 Mediatek Inc. Linked pdcp entities for ue assistance with data transmissions

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030206534A1 (en) * 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
US20070110101A1 (en) * 2005-11-16 2007-05-17 Chih-Hsiang Wu Method of Handling RLC SDUs During RLC Reset and RLC Re-establishment in a UMTS System
US8295265B2 (en) * 2005-11-16 2012-10-23 Htc Corporation Method for handling radio bearer messages during reset and reestablishment in a wireless system
KR20080073438A (ko) * 2007-02-06 2008-08-11 엘지전자 주식회사 차별적인 폐기 기준에 따른 데이터 블록 전송 방법
RU2492593C2 (ru) * 2007-06-25 2013-09-10 Нокиа Сименс Нетворкс Ой Перенос сообщений для сообщений внутриполосной сигнализации в сетях радиодоступа
WO2009018318A2 (en) * 2007-08-02 2009-02-05 Interdigital Patent Holdings, Inc. Packet data convergence protocol procedures
CN101374331B (zh) 2007-08-20 2011-06-01 华为技术有限公司 配置无线链路控制层序列号的方法、系统和设备
US20090168723A1 (en) * 2007-11-27 2009-07-02 Qualcomm Incorporated Method and apparatus for handling out-of-order packets during handover in a wireless communication system
EP2136501B1 (en) * 2008-06-20 2019-12-04 LG Electronics Inc. Method of delivering a PDCP data unit to an upper layer
US8396037B2 (en) * 2008-06-23 2013-03-12 Htc Corporation Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof
US8724548B2 (en) * 2010-04-22 2014-05-13 Qualcomm Incorporated Counter check procedure for packet data transmission
US8379855B2 (en) * 2010-06-03 2013-02-19 Nokia Corporation Ciphering in a packet-switched telecommunications system
US9432847B2 (en) * 2010-11-04 2016-08-30 Lg Electronics Inc. Method and apparatus for reconfiguring connection to base station at relay node in a wireless communication system
EP2761922B1 (en) * 2011-09-27 2018-07-25 LG Electronics Inc. Method and apparatus for reporting location information
US9497169B2 (en) * 2012-06-08 2016-11-15 Samsung Electronics Co., Ltd. Method and system for selective protection of data exchanged between user equipment and network
US9210619B2 (en) * 2012-06-20 2015-12-08 Ofinno Technologies, Llc Signalling mechanisms for wireless device handover
US9113387B2 (en) * 2012-06-20 2015-08-18 Ofinno Technologies, Llc Handover signalling in wireless networks
CN103517356B (zh) * 2012-06-28 2017-04-05 电信科学技术研究院 一种进行切换的方法、系统和设备
US9119190B2 (en) * 2012-08-06 2015-08-25 Qualcomm Incorporated Method and apparatus for enhancing data retransmission to improve call performance
US10034196B2 (en) * 2013-09-30 2018-07-24 Alcatel Lucent Methods, systems and devices for improving discontinuous reception in wideband wireless networks
US9560656B2 (en) * 2013-10-17 2017-01-31 Qualcomm Incorporated Joint support for UEs capable of communicating data of a same bearer on first and second RATs simultaneously and UEs not capable of communicating data of a same bearer on the first and second RATs simutaneously
KR20190107170A (ko) * 2014-03-28 2019-09-18 후지쯔 가부시끼가이샤 베어러 관리 장치, 방법 및 통신 시스템
CN104955064B (zh) 2014-03-28 2019-01-11 上海诺基亚贝尔股份有限公司 一种在双连接系统中处理用户设备端rlc/pdcp实体的方法与设备
US9544812B2 (en) * 2015-01-30 2017-01-10 Alcatel Lucent System and method for mitigating network congestion using fast congestion detection in a wireless radio access network (RAN)
US10869344B2 (en) * 2015-03-19 2020-12-15 Acer Incorporated Method of radio bearer transmission in dual connectivity
CN107211475B (zh) * 2015-04-02 2020-10-30 株式会社Kt 用于重新配置无线承载的方法及其装置
WO2016159634A1 (ko) * 2015-04-02 2016-10-06 주식회사 케이티 무선 베어러 재구성 방법 및 그 장치
US10397754B2 (en) * 2015-08-06 2019-08-27 Qualcomm Incorporation Packet data convergence protocol reordering with enhanced component carriers
US10320693B2 (en) * 2016-07-06 2019-06-11 Qualcomm Incorporated Method for packet data convergence protocol count synchronization
US10701583B2 (en) * 2016-07-07 2020-06-30 Industrial Technology Research Institute Method of service level traffic differentiation at radio access network, wireless network system and radio access network access node
CN114885375B (zh) * 2016-08-09 2024-08-09 三星电子株式会社 无线通信系统中管理用户平面操作的方法和装置
CN109417695B (zh) * 2017-01-10 2020-10-23 华为技术有限公司 一种通信路径转换方法及设备
CN109429568B (zh) * 2017-06-19 2022-07-29 北京小米移动软件有限公司 一种上报缓存状态报告的方法及装置
CN113784457B (zh) * 2018-08-10 2022-08-19 华为技术有限公司 一种通知方法、装置及基站
CN111757341A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 一种无线承载的配置方法、装置及系统

Also Published As

Publication number Publication date
WO2018165995A1 (zh) 2018-09-20
US20200068581A1 (en) 2020-02-27
EP3585087B1 (en) 2021-05-05
CN109196902A (zh) 2019-01-11
EP3585087A1 (en) 2019-12-25
US11924870B2 (en) 2024-03-05
CN109196902B (zh) 2021-02-09
EP3585087A4 (en) 2020-04-15
US20220007376A1 (en) 2022-01-06
US11096184B2 (en) 2021-08-17

Similar Documents

Publication Publication Date Title
WO2018165995A1 (zh) 一种数据处理方法及终端设备、基站
US9844070B2 (en) System and method for decoupling long term evolution media access control scheduling from subframe rate procedures
JP4806030B2 (ja) 移動通信システムで信号を転送する方法
WO2018028391A1 (zh) 进行重传处理的方法和装置
JP7177259B2 (ja) データ伝送方法及び装置
WO2019192516A1 (zh) 一种传输数据的方法、装置和系统
WO2018059438A1 (zh) 消息传输方法、设备和系统
WO2016029737A1 (zh) 一种数据传输方法及基站
WO2017016351A1 (zh) 一种上行数据的传输方法及装置
WO2021000783A1 (zh) 指示数据传输情况的方法和装置
WO2016127666A1 (zh) 一种rlc数据包分流方法及基站
WO2018202133A1 (zh) 数据处理方法及设备
WO2018058380A1 (zh) 一种数据传输方法、网络设备及终端设备
WO2014166053A1 (zh) 一种通讯方法和终端
CN114342287A (zh) 一种数据传输方法及装置
WO2014026386A1 (zh) 数据包传输方法和装置
RU2744946C2 (ru) Способ и устройство для асимметричных стека протоколов восходящей/нисходящей линии связи и структуры кадра в системе связи 5g nr
WO2024199047A1 (zh) 一种通信方法及装置
US20200187235A1 (en) Method, apparatus, computer program product and computer program
WO2015113296A1 (zh) 双连接模式下的状态反馈方法及设备
WO2020164441A1 (zh) 无线通信系统中的切换方法、装置及系统
WO2019061856A1 (en) PRETREATMENT IN WIRELESS UPLINK TRANSMISSIONS
JP6389126B2 (ja) 無線通信装置及び送信フレーム制御方法
WO2012155419A1 (zh) 一种处理重传数据的方法及基站
WO2018202204A1 (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: 17900535

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017900535

Country of ref document: EP

Effective date: 20190919