WO2018202190A1 - 一种数据传输的处理方法和装置 - Google Patents

一种数据传输的处理方法和装置 Download PDF

Info

Publication number
WO2018202190A1
WO2018202190A1 PCT/CN2018/085746 CN2018085746W WO2018202190A1 WO 2018202190 A1 WO2018202190 A1 WO 2018202190A1 CN 2018085746 W CN2018085746 W CN 2018085746W WO 2018202190 A1 WO2018202190 A1 WO 2018202190A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
pdu
timer
sequence number
rlc pdu
Prior art date
Application number
PCT/CN2018/085746
Other languages
English (en)
French (fr)
Inventor
徐小英
黄曲芳
娄崇
曾清海
郭英昊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18794399.8A priority Critical patent/EP3609106A4/en
Publication of WO2018202190A1 publication Critical patent/WO2018202190A1/zh
Priority to US16/672,974 priority patent/US20200068652A1/en

Links

Images

Classifications

    • 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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • 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/1848—Time-out mechanisms
    • H04L1/1851—Time-out mechanisms using multiple timers
    • 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
    • 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/1607—Details of the supervisory signal
    • H04L1/1642—Formats specially adapted for sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a method and an apparatus for processing data transmission.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA single carrier FDMA
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • the new wireless access network can provide a higher transmission rate than the LTE network, and the new wireless access network is also called a 5G network, a next generation network, and the like.
  • UMTS is a third generation mobile communication system adopting WCDMA air interface technology, adopting a structure similar to that of the second generation mobile communication system, and generally also The UMTS system is called a WCDMA communication system.
  • the UMTS system includes a Radio Access Network (RAN) and a Core Network (CN).
  • RAN Radio Access Network
  • CN Core Network
  • the wireless access network is used to handle all wireless related functions, while the CN handles all voice calls and data connections in the UMTS system and implements switching and routing functions with the external network.
  • the CN is logically divided into a Circuit Switched Domain (CS) and a Packet Switched Domain (PS).
  • CS Circuit Switched Domain
  • PS Packet Switched Domain
  • the core network includes the Mobile Switching Center (MSC)/Visitor Location Register (VLR), and the Serving GPRS (General Packet Radio Service) Support Node, SGSN. ), Home Location Register (HLR), Gateway Mobile-services Switching Centre (Gateway Mobile-services Switching Centre) and Gateway GPRS Support Node Network (GGSN), and other network elements.
  • the external network can be connected to the external network through the GMSC or the GGSN, for example, through the GMSC and the Public Land Mobile Network (PLMN), the Public Switched Telephone Network (PSTN), the integrated service number.
  • a connection such as an Integrated Services Digital Network (ISDN) can be connected to the Internet (INTERNET) through the GGSN.
  • ISDN Integrated Services Digital Network
  • the interface between the user equipment (UE) and the universal terrestrial radio access network (UTRAN) is a Uu interface, and the interface between the Node B and the radio network controller (RNC) passes through the Iub interface. Connected. Within the UTRAN, Radio Network Controllers (RNCs) are interconnected by Iur, and Iur can be connected through a direct physical connection between RNCs or through a transport network.
  • RNCs Radio Network Controllers
  • the interface between UTRAN and CN is collectively referred to as an Iu interface, including an Iu-CS interface and an Iu-PS interface.
  • the NodeB is interconnected with the RNC through the Iub interface, and is used to complete the processing of the physical layer protocol of the Uu interface, allocate and control the radio resources of the NodeB connected or associated with the NodeB, and complete the conversion of the data stream between the Iub interface and the Uu interface.
  • the RNC is used to control the radio resources of the UTRAN, and mainly performs functions such as connection establishment and disconnection, handover, macro diversity, and radio resource management control.
  • 3GPP proposes a new evolution network architecture to meet the application requirements of mobile networks in the next ten years or even longer, including system architecture evolution (SAE) and access network.
  • SAE system architecture evolution
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the goal of network evolution is to provide a low latency, high data rate, high system capacity and coverage, low cost, fully IP based network.
  • the evolved packet core network may include a Mobility Management Entity (MME), a Serving SAE GW, and a data packet.
  • MME Mobility Management Entity
  • SAE GW Three logical functional entities (PDN (Packet Data Network) SAE GW).
  • PDN Packet Data Network
  • the MME is responsible for mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, etc., corresponding to the control plane portion of the current GPRS/UMTS system internal service GPRS support section SGSN.
  • the Serving SAE GW is responsible for initiating paging for downlink data in an idle state, managing and storing IP bearer parameters and intra-network routing information, etc., corresponding to the current GPRS/UMTS system internal SGSN and Gateway GPRS Support Node Network (GGSN, Gateway GPRS Support Node).
  • GGSN Gateway GPRS Support Node Network
  • the PDN SAE GW acts as a user plane anchor between different access systems.
  • PCRF Policy and Charging Rule Function
  • the Home Subscriber Server (HSS) is used to store user subscription information.
  • the Long Term Evolution (LTE) network has a faster transmission rate, and its highest theoretical transmission rate can reach tens of gigabytes per second (Gigabyte, Gb for short).
  • the new communication system is a 5G or a next-generation communication system, including a next-generation core network (NG Core) and a base station (gNB), where the gNB generally includes a Radio Resource Control (RRC) layer and packet data aggregation. Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY).
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY Physical Layer
  • the gNB may also adopt a Centralized Unit (CU) and a Distributed Unit (DU) architecture, and the CU and the DU communicate by wire or wirelessly, and the DU communicates with the receiving end through an air interface, and receives the same.
  • the terminals move in different cells under the same or different DUs.
  • FIG. 3 is a schematic structural diagram of the gNB adopting the CU-DU architecture in the prior art.
  • the CU includes an RRC layer and a PDCP layer
  • the DU includes an RLC layer, a MAC layer, and a PHY layer.
  • the CU device is generally responsible for centralized radio resources and connection management control.
  • the DU device generally includes a distributed user plane processing function, and mainly processes layer 2 (Layer 2) functions with high physical layer functions and real-time requirements.
  • Layer 2 Layer 2
  • the CU device handles the functions of the wireless high-layer protocol stack, such as the RRC layer, the PDCP layer, etc., and can even support partial core network functions to sink to the access network, which is called an edge computing network, and can satisfy future communication networks for emerging services such as video and online shopping. , virtual / augmented reality for higher requirements for network latency.
  • the wireless high-layer protocol stack such as the RRC layer, the PDCP layer, etc.
  • the CU covers the high-level protocol stack of the radio access network and some functions of the core network, while the DU covers the physical layer of the baseband processing and the functions of the layer 2, the CU can be deployed in a centralized manner, and the DU deployment depends on the actual network environment, the core urban area, Areas with high traffic density, small station spacing, and limited space in the computer room, such as colleges and universities, large-scale performance venues, etc., DU can also be distributed in a centralized manner, while the traffic is sparse, and the station spacing is relatively large, such as the suburbs. In areas such as mountains, DUs can be distributed in a distributed manner.
  • QoS Quality of Service
  • QoS Class Identifier 1 to 4, which indicates that the service needs to guarantee bandwidth.
  • This part of QCI is used to guarantee the bandwidth guarantee rate.
  • Guaranteed bit rate (GBR) service which is generally a service that requires continuous equal bandwidth transmission, such as video or audio services.
  • GRR Guaranteed bit rate
  • QCI is 5-9 for services that do not need bandwidth guarantee.
  • the delay requirement of this part of service may be very high, such as IMS signaling message with QCI of 5 and IMS signaling message for VoLTE. Control of voice calls (eg, setup, release, hold, etc.) is very sensitive to latency.
  • video transmission includes a group of pictures (GOP), and a GOP is a group of consecutive pictures, that is, a sequence.
  • a sequence is a stream of data encoded by an image.
  • Three frames are defined in the H264 protocol.
  • the fully encoded frame is called an I frame (intra-coded frame, indicating a key frame); the frame generated by the previous I-frame only containing the difference partial coding is called a P-frame, and the P-frame represents Is the difference between this frame and a previous key frame (or P frame).
  • I frame intra-coded frame, indicating a key frame
  • P-frame the frame generated by the previous I-frame only containing the difference partial coding
  • the P-frame represents Is the difference between this frame and a previous key frame (or P frame).
  • B frame is a bidirectional difference frame, that is, the B frame records the difference between the current frame and the previous and subsequent frames.
  • the reliably transmitted service is carried in an AM RLC entity in an RLC Acknowledged Mode (RLC AM), such as a cached video download.
  • RLC AM RLC Acknowledged Mode
  • UM RLC entity RLC Unacknowledged Mode (RLC UM) mode, such as real-time video or voice.
  • the real-time video adopts the RLC UM mode
  • the real-time streaming protocol (RSTP) layer if the real-time transport protocol (RTP) layer or the user datagram protocol (User) of the transport layer (User)
  • the data packet of the Datagram Protocol (UDP) layer fails to be sent on the air interface, and the application layer retransmission is too late, resulting in poor QoS experience.
  • the cached video adopts the RLC AM mode, when a P frame or a segment thereof retransmits the maximum number of times, the RLC is reconstructed. Even if an I frame is received, it is not used. When the I frame or the segment is retransmitted the maximum number of times, the wireless is caused. The link fails and can only be rebuilt, resulting in an extension of the interruption.
  • a method, an apparatus, and a terminal device for processing data transmission are provided, which improve reliability while ensuring service transmission quality.
  • a first aspect of the present invention provides a data transmission processing method, including: an access network device generates configuration information of a terminal device, where configuration information of the terminal device is mapped to at least two PDCP entities of the terminal device a different RLC entity; the access network device sends configuration information of the terminal device to the terminal device.
  • the at least two different RLC entities respectively adopt RLC AM and RLC UM.
  • the at least two different RLC entities adopt the RLC AM or the RLC UM, and the at least two different RLC entities respectively configure timers of different durations, and each timer is used for detecting the corresponding RLC entity. Whether the RLC PDU sent by the access network device is lost.
  • the at least two different RLC entities adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer, and each of the timers is used by a corresponding RLC entity thereof.
  • the RLC PDU sent by the access network device that is not received as indicated in the status report sent by it.
  • a second aspect of the present invention provides a data transmission processing apparatus, including: a processor, configured to generate configuration information of a terminal device, where configuration information of the terminal device is mapped to at least one PDCP entity of the terminal device Two different RLC entities; a transmitter, configured to send configuration information of the terminal device to the terminal device.
  • the at least two different RLC entities respectively adopt RLC AM and RLC UM.
  • the at least two different RLC entities adopt the RLC AM or the RLC UM, and the at least two different RLC entities respectively configure timers of different durations, and each timer is used for detecting the corresponding RLC entity. Whether the RLC PDU sent by the access network device is lost.
  • the at least two different RLC entities adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer, and each of the timers is used by a corresponding RLC entity thereof.
  • the RLC PDU sent by the access network device that is not received as indicated in the status report sent by it.
  • a third aspect of the present invention provides a data transmission processing method, including: receiving, by a terminal device, configuration information sent by an access network device, where the configuration information is that one PDCP entity of the terminal device is mapped to at least two different The RLC entity; the terminal device selects to use different RLC entities for data transmission according to the type of the data stream or the QoS requirement of the data stream.
  • the at least two different RLC entities respectively adopt RLC AM and RLC UM.
  • the at least two different RLC entities adopt the RLC AM or the RLC UM, and the at least two different RLC entities respectively configure timers of different durations, and each timer is used for detecting the corresponding RLC entity. Whether the RLC PDU sent by the access network device is lost.
  • the at least two different RLC entities adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer, and each of the timers is used by a corresponding RLC entity thereof.
  • the RLC PDU sent by the access network device that is not received as indicated in the status report sent by it.
  • a fourth aspect of the present invention provides a terminal device, including: a receiver, configured to receive configuration information sent by the access network device, where the configuration information is that at least two PDCP entities of the terminal device are mapped to at least two Different RLC entities; a transmitter for selecting data transmission using different RLC entities according to the type of the data stream or the QoS requirements of the data stream.
  • the at least two different RLC entities respectively adopt RLC AM and RLC UM.
  • the at least two different RLC entities adopt the RLC AM or the RLC UM, and the at least two different RLC entities respectively configure timers of different durations, and each timer is used for detecting the corresponding RLC entity. Whether the RLC PDU sent by the access network device is lost.
  • the at least two different RLC entities adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer, and each of the timers is used by a corresponding RLC entity thereof.
  • the RLC PDU sent by the access network device that is not received as indicated in the status report sent by it.
  • a fifth aspect of the present invention provides a data transmission processing method, including: a receiving end determines that a value of a highest receiving state variable VR(H) is greater than a value of a receiving state variable VR(R), starts a first timer, and sets a state variable.
  • a value of VR(X) wherein the value of the VR(H) indicates a sequence number of the RLC PDU and a sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by one
  • the VR (R) The value of the RLC PDU indicates the sequence number of the RLC PDU and is the sequence number corresponding to the RLC PDU that the receiving end expects to receive when the first timer is started.
  • the value of the VR(X) indicates the sequence number of the RLC PDU and is the first to start.
  • the sequence number corresponding to the highest RLC PDU received by the timer is incremented by one; the first timer expires, the status report is sent, and the second timer is started, where the status report indicates the sequence number of the at least one RLC PDU that is lost;
  • the second timer expires, and the value of the VR(R) is set to be the first one of all the RLC PDUs corresponding to the RLC PDU sequence number corresponding to the value of the VR (X).
  • To the serial number of the RLC PDU setting the value of the VR(X) to the second timer From time to time corresponding to the maximum RLC PDU has been received sequence number plus one.
  • the third timer is started, and the value of VR1(R) is set.
  • the RLC PDU sequence number is greater than or equal to the VR(X) set when the first timer is started.
  • the value of the VR1(X) is the highest RLC that has been received when the first timer expires.
  • the value of the VR1(X) is set to the highest RLC received by the first timer when the first timer expires.
  • the sequence number corresponding to the PDU is incremented by one; the third timer expires, and the value of the VR(R) is set.
  • the RLC PDU sequence number is greater than or equal to the value of the VR1(X) set when the third timer is started.
  • the first one of all the RLC PDUs corresponding to the corresponding RLC PDU sequence number does not receive the sequence number of the RLC PDU, and the value of the VR (X) is set to correspond to the highest RLC PDU that has been received when the third timer expires.
  • the serial number is incremented by 1.
  • the receiving end determines that the sequence number of the received RLC PDU exists between the value of the VR(X) at the start of the first timer and the value of the current VR(H).
  • the third timer is used to determine whether the RLC PDU corresponding to the missing sequence number is lost.
  • a sixth aspect of the present invention provides a data transmission processing apparatus, including: a processor, configured to determine that a value of a highest received state variable VR(H) is greater than a value of a received state variable VR(R), and starts a first timer, Setting a value of the state variable VR(X), where the value of the VR(H) indicates the sequence number of the RLC PDU and the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by one,
  • the value of VR(R) indicates the sequence number of the RLC PDU and is the sequence number corresponding to the RLC PDU that the receiving end expects to receive when the first timer is started, and the value of the VR(X) indicates the sequence number of the RLC PDU and is The sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by one;
  • the sender is configured to send a status report when the first timer expires, and the status report indicates that at least
  • the processor is further configured to start a second timer when the first timer expires; the processor is further configured to time out the second timer, and set the value of the VR(R)
  • the RLC PDU sequence number is greater than or equal to the RLC PDU sequence number corresponding to the value of the VR(X). Maximum RLC PDU corresponding to all the first RLC PDU not received the RLC PDU sequence number, provided the VR (X) value of the second timer has timed out when the received sequence number plus one.
  • the processor is further configured to: when the first timer expires, start a third timer, and set a value of VR1(R) to be set when the RLC PDU sequence number is greater than or equal to when the first timer is started.
  • the value of the VR(X) corresponding to the RLC PDU sequence number corresponding to the first one of the RLC PDUs that does not receive the sequence number of the RLC PDU, and the value of the VR1(X) is set to be the first timer super
  • the sequence number corresponding to the highest RLC PDU received at the time is incremented by one; the processor is further configured to time out the third timer, and set the value of the VR (R) to be greater than or equal to the start of the third RLC PDU sequence number.
  • the processor is further configured to determine, before the first timer expires, a value of the VR(X) of the sequence number of the received RLC PDU at the start of the first timer to the current VR(H).
  • the third timer is used to determine whether the RLC PDU corresponding to the missing sequence number is lost.
  • a seventh aspect of the present invention provides a data transmission processing method, including: when a receiving end determines that a value of a highest receiving state variable VR(H) is greater than a value of a receiving state variable VR(R), sending a status report to the transmitting end, and starting a first timer that sets a value of a state variable VR(X), wherein the status report includes status information that the receiving end receives all RLC PDUs when the first timer is started, and the value of the VR(H) Indicates the sequence number of the RLC PDU and adds 1 to the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started.
  • the value of the VR(R) indicates the sequence number of the RLC PDU and is the first timer.
  • the value of the VR(X) indicating the sequence number of the RLC PDU and the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by one;
  • the first timer expires, set the value of VR(R) to all received RLC PDUs whose RLC PDU sequence number is greater than or equal to the RLC PDU sequence number corresponding to the value of the VR(X) when the first timer is started.
  • the serial number of the first unsuccessfully received RLC PDU and set the said The value of VR(X) when a timer expires is the value of VR(H) when the first timer expires; or, before the first timer expires, the receiving end determines the received RLC PDU.
  • the sequence number is discontinuous between the value of the VR(X) at the start of the first timer and the value of the current VR(H), and the third timer is started, and the third timer is used by the receiving end to determine the missing serial number. Whether the corresponding RLC PDU is lost.
  • setting a value of VR(R) corresponds to a value of the VR(X) when the RLC PDU sequence number is greater than or equal to starting the third timer.
  • the sending end when the first or third timer expires, sending a status report to the sending end, where the status report includes the receiving end receiving all RLC PDUs when the first or third timer expires Status information.
  • An eighth aspect of the present invention provides a processing apparatus for data transmission, comprising: a processor, configured to start a first timing when determining that a value of a highest received state variable VR(H) is greater than a value of a received state variable VR(R) And setting a value of the state variable VR(X), wherein the value of the VR(H) indicates the sequence number of the RLC PDU and the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by one,
  • the value of the VR(R) indicates the sequence number of the RLC PDU and is the sequence number corresponding to the RLC PDU that the receiving end expects to receive when the first timer is started, and the value of the VR(X) indicates the sequence number of the RLC PDU.
  • the transmitter is configured to determine that the value of the highest receiving state variable VR(H) is greater than the value of the receiving state variable VR(R) Sending a status report to the sending end, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer is started;
  • the processor is further configured to be in the first timer At the same time, set the value of VR(R) to be the RLC PDU sequence number greater than or equal to the first start.
  • the value of VR(H) when the first timer expires; or the processor is further configured to determine the sequence number of the received RLC PDU before the first timer expires
  • a discontinuity exists between the value of VR(X) at the start of a timer and the value of the current VR(H), and a third timer is started, where the third timer is used by the receiving end to determine the RLC PDU corresponding to the missing sequence number. Is it lost?
  • the processor is further configured to set a value of VR(R), where the RLC PDU sequence number is greater than or equal to the third timer is started.
  • the sequence number of the first unsuccessfully received RLC PDU of all received RLC PDUs of the RLC PDU sequence number corresponding to the value of VR(X).
  • the sender is further configured to send a status report to the sending end when the first or third timer expires, where the status report includes when the first or third timer expires
  • the receiving end receives status information of all RLC PDUs.
  • a ninth aspect of the present invention provides a data transmission processing method, including: receiving, by an RLC layer of a transmitting end, a discarding indication of discarding a first PDCP PDU sent by a PDCP layer of the transmitting end; the RLC layer discarding the discarding according to the discarding indication The RLC PDU corresponding to the first PDCP PDU or the corresponding RLC SDU.
  • the RLC layer discarding the RLC SDU corresponding to the first PDCP PDU according to the discarding indication, if the RLC layer has not processed the first PDCP PDU, the RLC layer is configured according to the Discarding indicates that the RLC SDU corresponding to the first PDCP PDU is discarded.
  • the RLC layer discarding the RLC PDU corresponding to the first PDCP PDU according to the discarding indication includes: if the RLC layer has performed an RLC serial number number on the first PDCP PDU, or has generated the The RLC PDU corresponding to a PDCP PDU or the RLC layer that has sent the first PDCP PDU, the RLC PDU corresponding to the first PDCP PDU is discarded according to the discarding indication, and the receiving end is notified to discard the corresponding RLC PDU. serial number.
  • the discarding indication carries information that discards the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, where the RLC layer receives the first The PDCP PDU starts the drop timer and discards the first PDCP PDU when the drop timer expires.
  • a tenth aspect of the present invention provides a data transmission processing apparatus, including: a receiver, configured to receive a discard indication of discarding a first PDCP PDU sent by a PDCP layer of the transmitting end, and a processor, configured to discard according to the discarding indication The RLC PDU corresponding to the first PDCP PDU or the corresponding RLC SDU.
  • the processor is configured to: discard, according to the discarding indication, the RLC SDU corresponding to the first PDCP PDU, where the processor is configured to: if the first PDCP PDU has not been processed, according to the The discarding indicates discarding the RLC SDU corresponding to the first PDCP PDU.
  • the processor is configured to: discard the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, where the processor is configured to: if the first PDCP PDU has been RLC serial number or The RLC PDU corresponding to the first PDCP PDU has been generated or the first PDCP PDU has been sent, the RLC PDU corresponding to the first PDCP PDU is discarded according to the discarding indication, and the receiving end is notified to discard the RLC PDU.
  • the corresponding serial number is configured to: if the first PDCP PDU has been RLC serial number or The RLC PDU corresponding to the first PDCP PDU has been generated or the first PDCP PDU has been sent, the RLC PDU corresponding to the first PDCP PDU is discarded according to the discarding indication, and the receiving end is notified to discard the RLC PDU.
  • the corresponding serial number is configured to: if the first PDCP PDU has been RLC serial number or The RLC PDU corresponding to
  • the discarding indication carries information for discarding the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, and the processor is further configured to be at the receiver Upon receiving the first PDCP PDU, the discard timer is started and the first PDCP PDU is discarded when the discard timer expires.
  • An eleventh aspect of the present invention provides a data transmission processing method, where a base station includes a CU and a DU, including: a DU receiving a discarding timer sent by a CU for a first bearer or a first logical channel (group); When a PDCP PDU of the first logical channel (group) is carried, the discard timer is started, and the PDCP PDU is discarded when the discard timer expires.
  • the discarding the PDCP PDU when the discard timer expires includes: if the DU has not processed the PDCP PDU, the DU discards the PDCP when the discard timer expires The RLC SDU corresponding to the PDU.
  • the discarding the PDCP PDU when the discard timer expires includes: if the DU has performed an RLC sequence number number on the PDCP PDU or has generated an RLC PDU corresponding to the PDCP PDU or has sent The PDCP PDU, the DU discards the RLC PDU corresponding to the PDCP PDU when the discard timer expires, and notifies the terminal device to discard the sequence number corresponding to the RLC PDU.
  • a twelfth aspect of the present invention provides a processing device for data transmission, comprising: a receiver, configured to receive a discard timer sent by a CU for a first bearer or a first logical channel (group); a processor, configured to: When the receiver receives the PDCP PDU of the first bearer or the first logical channel (group), the discarding timer is started, and the PDCP PDU is discarded when the discarding timer expires.
  • the processor when the discarding timer expires, discarding the PDCP PDU, specifically: the processor is configured to discard the discarding timer when the discarding timer expires if the PDCP PDU has not been processed yet The RLC SDU corresponding to the PDCP PDU.
  • the processor is configured to: when the discarding timer expires, discarding the PDCP PDU, where the processor is configured to: if the PDCP PDU has been RLC serial number or has generated the PDCP PDU corresponding to the PDCP PDU The RLC PDU or the PDCP PDU has been sent, and the RLC PDU corresponding to the PDCP PDU is discarded when the discard timer expires;
  • the processing device for data transmission further includes: a transmitter,
  • a thirteenth aspect of the present invention provides a data transmission processing method, the base station includes a CU and a DU, and the method includes: the DU receives the QoS parameter information of the first PDCP PDU that is sent by the CU, and the DU discards the The RLC PDU corresponding to the first PDCP PDU or the corresponding RLC SDU.
  • the disc discarding the RLC SDU corresponding to the first PDCP PDU according to the discarding indication includes: if the DU has not processed the first PDCP PDU, the DU discards according to the discarding indication The RLC SDU corresponding to the first PDCP PDU.
  • the disc discarding the RLC PDU corresponding to the first PDCP PDU according to the discarding indication includes: if the DU has performed an RLC serial number number on the first PDCP PDU or has generated the first PDCP The RLC PDU corresponding to the PDU or the first PDCP PDU has been sent, the DU discards the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, and notifies the terminal device to discard the serial number corresponding to the RLC PDU. .
  • the discarding indication carries information for discarding the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, where the DU is receiving the first PDCP The PDU starts the drop timer and discards the first PDCP PDU when the drop timer expires.
  • a fourteenth aspect of the present invention provides a data transmission processing apparatus, including: a receiver, configured to receive a discard indication of discarding a first PDCP PDU sent by a distributed unit CU, and a processor, configured to discard according to the discarding indication The RLC PDU corresponding to the first PDCP PDU or the corresponding RLC SDU.
  • the processor is configured to discard the RLC SDU corresponding to the first PDCP PDU according to the discarding indication, where the processor is configured to: according to the discarding, the first PDCP PDU is not processed according to the discarding Instructing to discard the RLC SDU corresponding to the first PDCP PDU.
  • the processor is configured to discard the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, where the processor is configured to: if the first PDCP PDU has been RLC serial number numbered or has been generated The RLC PDU corresponding to the first PDCP PDU or the first PDCP PDU has been sent, and the RLC PDU corresponding to the first PDCP PDU is discarded according to the discarding indication; the processing device for data transmission further includes: sending And is configured to notify the terminal device to discard the sequence number corresponding to the RLC PDU.
  • the discarding indication carries information for discarding the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, where the processor is configured to receive at the receiver The first PDCP PDU is started when the first PDCP PDU is started, and the first PDCP PDU is discarded when the drop timer expires.
  • a fifteenth aspect of the present invention provides a data transmission processing method, where the base station includes a CU and a DU, and the method includes: the DU receives the first bearer or the first logical channel (group) of the Qos parameter information sent by the CU, where the QoS parameter parameter information At least one of the following: a guaranteed bit rate, a scheduling priority, a buffer allowed delay, a priority bit rate PBR (Prioritized Bit Rate), a Bulb Size Duration (BSD), the DU according to the Qos
  • the parameter information manages data transmission of the first bearer or the first logical channel (group).
  • the disc discarding the RLC SDU corresponding to the first PDCP PDU according to the allowed delay of the buffer includes: if the DU has not processed the first PDCP PDU, the DU is according to the Discarding indicates that the RLC SDU corresponding to the first PDCP PDU is discarded. For example, the maximum delay in the transmission of the PDCP or RLC layer.
  • the DU performs scheduling transmission of the uplink or downlink data packet of the bearer according to the guaranteed bit rate or scheduling priority.
  • the processing method, device and terminal device for data transmission described in the above various aspects improve reliability while ensuring service transmission quality.
  • FIG. 1 is a schematic structural diagram of a UMTS communication system in the prior art
  • FIG. 2 is a schematic diagram of a packet core network architecture evolved in the prior art
  • FIG. 3 is a schematic structural diagram of a gNB adopting a CU-DU architecture in the prior art
  • FIG. 4 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another communication system according to another embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of another communication system according to another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another communication system according to another embodiment of the present invention.
  • FIG. 9 is a schematic diagram of another video data transmission according to another embodiment of the present invention.
  • FIG. 10 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another communication system according to another embodiment of the present invention.
  • FIG. 12 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 13 is a schematic diagram of a data state of a data transmission process according to another embodiment of the present invention.
  • FIG. 14 is a schematic diagram of a data state of a data transmission process according to another embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • FIG. 16 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 17 is a schematic diagram of a data state of a data transmission process according to another embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • FIG. 19 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • FIG. 21 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 22 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • FIG. 23 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 24 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 25 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • FIG. 26 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • FIG. 27 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • a “module” as referred to herein generally refers to a program or instruction stored in a memory that is capable of performing certain functions;
  • "unit” as referred to herein generally refers to a functional structure that is logically divided, the "unit” It can be implemented by pure hardware or a combination of hardware and software.
  • Multiple as referred to herein means two or more. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • the techniques described herein can be used in various communication systems, such as current 2G, 3G, 4G communication systems and new radio access networks, such as GSM systems, CDMA systems, TDMA systems, WCDMA systems, FDMA systems, OFDMA systems, SC-FDMA Systems, GPRS systems, LTE systems, UMTS networks, new wireless access networks, and other such communication systems.
  • the new wireless access network can provide a higher transmission rate than the LTE network, and the new wireless access network is also called a 5G network, a next generation network, and the like.
  • the terminal device may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or data connectivity to the receiving end, a handheld device with wireless connection function, or a wireless modem connected to the wireless modem. Other processing equipment.
  • the wireless terminal can communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and with a mobile terminal
  • RAN Radio Access Network
  • the computers for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network.
  • a wireless terminal may also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, or an access point.
  • Remote Terminal Access Terminal, User Terminal, User Equipment, or User Agent.
  • a base station may refer to a device in an access network that communicates with a wireless terminal over one or more sectors over an air interface.
  • the base station can be used to convert the received air frame to the IP packet as a router between the wireless terminal and the rest of the access network, wherein the remainder of the access network can include an Internet Protocol (IP) network.
  • IP Internet Protocol
  • the base station can also coordinate attribute management of the air interface.
  • the base station may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or may be a base station (NodeB) in a WCDMA system, or may be an evolved base station (eNodeB or eNB or e- in an LTE system).
  • NodeB may also be an access network device of a new radio access network, which is not limited in this application.
  • the access network device of the new radio access network is also referred to as a base station (gNB), an NR Node (node), or an NR BS (Base Station), which is not limited herein, but is convenient for description, and is collectively referred to herein.
  • gNB base station
  • node NR Node
  • NR BS Base Station
  • the base station controller (ie, the control node) may be a base station controller (BSC) in the GSM system or the CDMA system, or may be a radio network controller (RNC) in the WCDMA. Not limited.
  • BSC base station controller
  • RNC radio network controller
  • FIG. 4 is a schematic diagram of a communication system including an access network device 41 and a terminal device 42 according to an embodiment of the present invention.
  • the communication system may be a 2G, 3G, 4G communication system or a new Radio access networks, such as GSM systems, CDMA systems, TDMA systems, WCDMA systems, FDMA systems, OFDMA systems, SC-FDMA systems, GPRS systems, LTE systems, UMTS networks, new radio access networks, and other such communication systems.
  • the new wireless access network can provide a higher transmission rate than the LTE network, and the new wireless access network is also called a 5G network, a next generation network, and the like. Therefore, the access network device 41 may be a base station of a 2G, 3G or 4G communication system, or may be a gNB of a 5G communication system.
  • the access network device 41 includes a three-layer structure: layer one is a physical layer (PHY layer), layer two is a medium access control layer (MAC layer), a radio link control layer (RLC layer), and a packet data convergence protocol layer. (PDCP layer), layer 3 is the radio resource control layer (RRC layer), where the PHY layer is the lowest layer of the radio access system, which uses the transport channel as an interface to provide services to the upper layer.
  • the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and the RRC layer of the access network device 41 are provided with a receiving entity and a sending entity for each bearer, respectively, for receiving and transmitting data, but for description Conveniently, the following descriptions are all described by sending or receiving at each layer.
  • the data received by the access network device 41 from the terminal device 42 is processed through the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and the RRC layer of the access network device 41 in sequence.
  • the PHY layer processes the received data into a PHY service data unit ( a Service Data Unit (SDU), the PHY layer transmitting the PHY SDU to the MAC layer; the MAC layer receiving the PYH SDU, and then processing the PYH SDU as a MAC SDU, the MAC layer Transmitting the MAC SDU to the RLC layer; the RLC layer receives the MAC SDU, and then processes the MAC SDU into an RLC SDU, where the RLC layer sends the RLC SDU to the PDCP layer; the PDCP Receiving, by the layer, the RLC SDU, and then processing the RLC SDU into a signaling PD
  • a PHY service data unit a Service Data Unit (SDU)
  • SDU Service Data Unit
  • the PHY layer transmit
  • the data sent by the access network device 41 sequentially passes through the PDCP layer, the RLC layer, the MAC layer, and the PHY layer, and is then sent to the terminal device 42.
  • the PDCP layer processes data into a PDCP Protocol Data Unit (PDU), and then sends the PDCP PDU to the RLC layer;
  • the RLC layer receives The PDCP PDU, which then processes the PDCP PDU as an RLC PDU, the RLC layer sends the RLC PDU to the MAC layer;
  • the MAC layer receives the RLC PDU, and then processes the RLC PDU as a MAC PDU, the MAC layer transmitting the MAC PDU to the PHY layer;
  • the PHY layer receiving the MAC PDU, and then processing the MAC PDU as a PHY PDU, the PHY layer sending the PHY PDU To the terminal device 42.
  • the terminal device 42 includes a PHY layer, a MAC layer, an RLC layer, and a PDCP layer, and each layer included in the terminal device 42 is provided with a receiving entity and a sending entity for receiving and transmitting data for each bearer. However, for convenience of description, the following description is described by transmitting or receiving at each layer. .
  • the data received by the terminal device 42 from the access network device 41 is processed through the PDCP layer, the RLC layer, the MAC layer, and the PHY layer of the terminal device 42 in sequence.
  • the PDCP layer processes the received PHY PDU into a PDCP PDU, and then Transmitting a PDCP PDU to the RLC layer;
  • the RLC layer receives the PDCP PDU, and then processes the PDCP PDU as an RLC PDU, and the RLC layer sends the RLC PDU to the MAC layer;
  • the MAC The layer receives the RLC PDU, and then processes the RLC PDU into a MAC PDU, the MAC layer sends the MAC PDU to the PHY layer;
  • the PHY layer receives the MAC PDU, and then the MAC PDU Processed as a PHY PDU, the PHY layer sends the PHY PDU to
  • the data is sequentially processed by the PHY layer, the MAC layer, the RLC layer, and the PDCP layer of the terminal device 42.
  • the PHY layer data is processed as a PHY SDU, and then the PHY SDU is transmitted to the MAC layer;
  • the MAC layer receives the PYH SDU, and then processes the PYH SDU into a MAC SDU, the MAC layer sends the MAC SDU to the RLC layer;
  • the RLC layer receives the MAC SDU, and then processes the MAC SDU into an RLC SDU, and the RLC layer sends the RLC SDU to
  • the PDCP layer receives the RLC SDU, and then processes the RLC SDU into a PDCP SDU, and the PDCP layer sends the PDCP SDU to the access network device 41.
  • FIG. 5 is a schematic structural diagram of a communication system according to another embodiment of the present invention.
  • the communication system is a 5G or next generation communication system, and includes an access network device 51, a terminal device 52, and a next generation core network (NG Core) 53.
  • the access network device 51 is a 5G gNB
  • the access network device 51 includes a centralized unit (CU) 511 and a distributed unit (DU) 512, and the CU 511 and the DU 512 communicate by wire or wirelessly.
  • the DU 512 communicates with the terminal device 52 through an air interface.
  • the RRC layer and the PDCP layer function are located on the CU 511, and the RLC layer, the MAC layer, and the PHY layer function are located on the DU 512.
  • FIG. 6 is a schematic structural diagram of a communication system according to another embodiment of the present invention.
  • the communication system is a 3G or 4G communication system, and includes an access network device 61, a terminal device 62, and a core network (CN) 53.
  • the access network device 61 is a distributed base station of a 3G or 4G communication system, and the access network device 61 may include: a Radio Remote Unit (RRU) 611 and a Baseband Processing Unit (Building Baseband Unit). , BBU) 612.
  • RRU 611 and the BBU 612 communicate by wire or wirelessly, and the RRU 611 communicates with the terminal device 62 through an air interface.
  • the RRC layer and the PDCP layer function are located on the BBU 611, and the RLC layer, the MAC layer, and the PHY layer function are located on the RRU 612.
  • the process of data transmission of each layer of the access network device and the terminal device may refer to the content described in the embodiment of FIG. 4 , and details are not described herein again.
  • FIG. 7 is a schematic flowchart of a data transmission processing method according to an embodiment of the present invention.
  • the data transmission processing method in this embodiment is performed by an access network device, and the access network device may be 2G.
  • the base station of a 3G, 4G or 5G communication system, the main process is as follows.
  • Step 71 The access network device generates configuration information of the terminal device, where the configuration information of the terminal device is that one PDCP entity of the terminal device is mapped to at least two different RLC entities.
  • Step 72 The access network device sends configuration information of the terminal device to the terminal device.
  • the access network device configures one PDCP entity of the terminal device to correspond to at least two different RLC entities, for example, one radio bearer (RB) or a logical channel (LCH) corresponds to one RLC entity.
  • the PDCP entity of the terminal device selects data transmission by using different RLC entities according to the type of the data stream or the quality of service (QoS) requirement of the data stream.
  • QoS quality of service
  • a PDCP entity uses at least two logical channels
  • different LCHs of the UM RLC or the AM RLC entity have different priorities
  • the terminal device uplink buffer status report (BSR) priority The amount of data to be sent reported by the AM RLC entity or the amount of data to be sent reported by the LCH from high to low according to the LCH priority.
  • the at least two different RLC entities each adopt an RLC AM or an RLC UM, and the at least two different RLC entities respectively configure timers of different durations (may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • timers of different durations may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • one of the RLC entities corresponding to the terminal device PDCP entity finds that the RLC PDU sent by the access network device is not successfully received, and the RLC entity starts its configured t-Reordering timer or reassembly segmentation timer.
  • the t-Reordering timer or the reassembly segmentation timer expires, triggering the terminal device to send a status report to the access network device, where the status report includes the t-Reordering timer or the reassembly segmentation timer expires
  • the serial number of the RLC PDU for example, including a sequence number (SN) of the RLC PDU sent by the access network device that is not received, and/or a packet that is sent by the access network device that is successfully received.
  • the serial number of the RLC PDU for example, including a sequence number (SN) of the RLC PDU sent by the access network device that is not received, and/or a packet that is sent by the access network device that is successfully received.
  • the RLC entity receiving end of the RLC AM determines whether the unreceived RLC PDU is received when the t-Reordering timer or the reassembly segmentation timer expires, at the t-Reordering timer or the reassembly segmentation timing. If the RLC entity does not receive the unsuccessfully received RLC PDU, the terminal device determines that the RLC PDU sent by the access network device is lost, and then sends a status report to the access network device.
  • the status report includes status information that the receiving end receives all RLC PDUs when the t-Reordering timer or the reassembly segmentation timer expires, for example, including the sequence number of the RLC PDU sent by the access network device that is not received. It should be understood that the timer used for the RLC entity employing RLC AM or RLC UM may also be a timer for waiting to assemble the segmented RLC PDU, and the PDU for UM RLC does not trigger a status report.
  • the at least two different RLC entities all adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer (may be referred to as continuing waiting timing) And each of the continuation wait timers for its corresponding RLC entity to continue to wait to receive the RLC PDUs sent by the access network device that are not received as indicated in the status report sent by it.
  • the RLC entity configured to continue to wait for the timer sends a request when the t-Reordering timer or the reassembly segmentation timer expires or according to the status report sent by the access network device, and the terminal device sends the request to the access network device.
  • Sending a status report starting its configured continuation wait timer, continuing to receive the unreceived RLC PDU within the duration of the continuation wait timer, determining whether the unreceived RLC PDU can be before the continuation wait timer expires Receiving, wherein the status report includes status information of receiving all data packets when the t-Reordering timer or the reassembly segmentation timer expires or receiving the status report transmission request, for example, including the unreceived Serial number of the RLC PDU sent by the network access device.
  • the configuration continues to wait for the RLC entity of the timer to still receive the unreceived RLC PDU, and the terminal device determines the RLC PDU sent by the access network device. Loss, sending the latest status report to the access network device, the latest status report including status information of the receiving end receiving all RLC PDUs when the continuation wait timer expires.
  • the terminal device performs a push window of the receiving window while waiting for the timer to expire, and no longer waits for the RLC PDU of the t-Reordering timer or the reassembly segmentation timer to be triggered last time.
  • One or more RLC PDUs that are not received and are not received in the continuation wait timer in order to receive the RLC PDU sent by the access network device next time, the terminal device notifying the access network device The terminal device has pushed the window.
  • the specific push window please refer to the description of the subsequent push window embodiment.
  • the access network device configures a first maximum number of retransmissions for the at least one AM RLC entity of the terminal device, and the AM RLC entity of the terminal device receives the RLC PDU and receives the Retransmitting the RLC PDU after the NACK sent by the access network device, if the RLC PDU is not successfully sent after retransmitting the first maximum number of retransmissions, discarding the retransmitted RLC PDU, the terminal device does not The access network device is notified to trigger RLC re-establishment, that is, not used as a basis for radio link failure (RLF) judgment.
  • RLF radio link failure
  • the access network device configures a second maximum number of retransmissions for the at least one AM RLC entity of the terminal device, and the AM RLC entity of the terminal device receives the RLC PDU and receives the Retransmitting the RLC PDU after the NACK sent by the access network device, if the RLC PDU is not successfully sent after retransmitting the second maximum number of retransmissions, discarding the retransmitted RLC PDU, the terminal device notifying The access network device triggers RLC reconstruction.
  • the second maximum number of retransmissions is greater than or equal to the first number of retransmissions.
  • the PDCP entity of the terminal device may be selected according to the type of the data stream or the quality of service (QoS) requirement, because one PDCP entity of the terminal device is mapped to at least two different RLC entities.
  • QoS quality of service
  • FIG. 8 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the communication system includes an access network device 81 and a terminal device 82, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system, the access network device including: a receiver 811, a processor 812, a transmitter 813, and a memory 814, wherein the receiving The 811, the processor 812, the transmitter 813, and the memory 814 communicate with each other via a bus.
  • the processor 812 may be an Erasable Programmable Logic Device (EPLD), a Field Programmable Gate Array (FPGA), or a Digital Signal Processor (Digital Signal). Processor, DSP) chip, Application Specific Integrated Circuit (ASIC), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like.
  • EPLD Erasable Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • the memory 814 is used to store code or instruction information, and may also store information of a device type.
  • the memory 814 can include a Read-Only Memory (ROM) and a Random Access Memory (RAM) for providing instructions and data to the processor 812.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a portion of the memory 814 may also include a non-volatile random access memory.
  • the receiver 811 is configured to receive data sent by a terminal device or a core network.
  • the processor 812 is configured to generate configuration information of the terminal device, where the configuration information of the terminal device is mapped to at least two different RLC entities by one PDCP entity of the terminal device.
  • the transmitter 813 is configured to send configuration information of the terminal device to the terminal device.
  • the processor 812 configures one PDCP entity of the terminal device to correspond to at least two different RLC entities, for example, one RB or LCH corresponds to one RLC entity.
  • the PDCP entity of the terminal device selects to use different RLC entities for data transmission according to the type of the data stream or the quality of service QoS requirement of the data stream.
  • the terminal device uplink BSR preferentially reports the AM RLC to the receiver 811.
  • the amount of data to be transmitted of the entity or the amount of data to be transmitted of the LCH reported to the receiver 811 from high to low according to the LCH priority.
  • the at least two different RLC entities each adopt an RLC AM or an RLC UM, and the at least two different RLC entities respectively configure timers of different durations (may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • timers of different durations may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • one of the RLC entities corresponding to the terminal device PDCP entity finds that the RLC PDU sent by the access network device is not successfully received, and the RLC entity starts its configured t-Reordering timer or reassembly segmentation timer.
  • the t-Reordering timer or the reassembly segmentation timer expires, triggering the terminal device to send a status report to the receiver 811 of the access network device, where the status report includes the t-Reordering timer or the reassembly segment Receiving, by the receiving end, the status information of all RLC PDUs when the timer expires, for example, including the sequence number of the RLC PDU sent by the transmitter 813 of the access network device that has been lost, and/or including the successfully received The serial number of the RLC PDU sent by the transmitter 813 of the network access device.
  • the RLC entity receiving end using RLC AM or RLC UM determines whether the unreceived RLC PDU is received when the t-Reordering timer or the reassembly segmentation timer expires, in the t-Reordering timer or reorganization
  • the terminal device determines that the RLC PDU sent by the sender 813 of the access network device is lost, and then goes to the The receiver 811 of the access network device sends a status report, where the status report includes status information that the receiving end receives all RLC PDUs when the t-Reordering timer or the reassembly segmentation timer expires, for example, including not receiving The serial number of the RLC PDU sent by the transmitter 813.
  • the at least two different RLC entities all adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer (may be referred to as continuing waiting timing) And each of the continuation wait timers is used by the RLC PDU sent by the transmitter 813 of the access network device that is not received by the corresponding RLC entity to continue waiting for the status report it is transmitting.
  • the RLC entity configured to continue to wait for the timer sends a request to the access network when the t-Reordering timer or the reassembly segmentation timer expires or according to the status report sent by the transmitter 813 of the access network device.
  • the receiver 811 of the device sends a status report, starts its configured continuation wait timer, continues to receive the unreceived RLC PDU within the duration of the continuation wait timer, and determines whether the unreceived RLC PDU can be
  • the continuation waits for the timer to be received before the timer expires, wherein the status report includes status information of all the data packets received when the t-Reordering timer or the reassembly segmentation timer expires or the reception status report is sent, for example, including the unreceived The sequence number of the RLC PDU sent by the sender 813.
  • the configuration continues to wait for the RLC entity of the timer or does not receive the unreceived RLC PDU, the terminal device determines that the RLC PDU sent by the sender 813 is lost, to the The receiver 811 sends a latest status report, and the latest status report includes status information that the receiving end receives all RLC PDUs when the continuation wait timer expires.
  • the terminal device when the terminal device continues to wait for the timer to time out, the terminal device performs a push window of the receiving window to receive the RLC PDU sent by the access network device next time, and the terminal device notifies the The terminal device of the access network device has been pushed to the window.
  • the terminal device performs a push window of the receiving window to receive the RLC PDU sent by the access network device next time, and the terminal device notifies the The terminal device of the access network device has been pushed to the window.
  • the processor 812 configures an AM RLC entity of the terminal device with a first maximum number of retransmissions, and the AM RLC entity of the terminal device receives the access after transmitting the RLC PDU. Retransmitting the RLC PDU after the NACK sent by the sender 813 of the network device, and if the RLC PDU is not successfully sent after retransmitting the first maximum number of retransmissions, discarding the retransmitted RLC PDU, The terminal device does not notify the access network device to trigger RLC re-establishment, that is, does not serve as a basis for RLF determination.
  • the processor 812 configures an AM RLC entity of the terminal device with a second maximum number of retransmissions, and the AM RLC entity of the terminal device receives the access after sending the RLC PDU. Retransmitting the RLC PDU after the NACK sent by the sender 813 of the network device, and if the RLC PDU is still not successfully sent after retransmitting the second maximum number of retransmissions, discarding the retransmitted RLC PDU, The terminal device notifies the processor 812 of the access network device to trigger RLC re-establishment.
  • the PDCP entity of the terminal device may select to use different RLC entities for data transmission according to the type of the data stream or the QoS requirement, because one PDCP entity of the terminal device is mapped to at least two different RLC entities. Ensure the normal transmission of different services and improve the reliability while ensuring the service experience.
  • FIG. 9 is a schematic diagram of transmission of video data according to another embodiment of the present invention.
  • the video data stream includes an I frame and a P frame, and the at least two different The RLC entity uses RLC AM and RLC UM respectively.
  • the terminal device includes a PHY layer, a MAC layer, an RLC layer, and a PDCP layer.
  • the access network device configures one PDCP entity of the terminal device, and one RB corresponds to at least one RLC entity or one LCH corresponds to at least one RLC entity.
  • the LCH1 of the first PDCP entity corresponds to the first AM RLC entity of the RLC AM
  • the LCH1 or LCH3 of the first PDCP entity corresponds to the first UM RLC entity of the RLC UM
  • the LCH2 of the second PDCP entity corresponds to the second of the RLC UM.
  • UM RLC entity UM RLC entity.
  • the first PDCP entity selects to use different RLC entities for data transmission according to the type of data stream or QoS requirement. For example, the first PDCP entity may obtain the information based on the manner in which the application layer indicates the access layer or the access layer parses the characteristics of the application layer data packet, for example, a control message such as an I frame, an important P frame, or an application layer RSTP.
  • the RLC entity is placed in the RLC AM, and the normal P frame is sent on the first UM RLC entity that uses the RLC UM, and the voice service is placed in the second UM RLC entity corresponding to the second PDCP entity. Send on.
  • the PDCP determines the correspondence between the IP flow and the RB according to the characteristics of the IP flow or the QoS parameter, and sends the IP data packet. Go to the corresponding RB.
  • the IP data packet is transmitted to the corresponding RB according to the characteristics of the IP flow or the QoS parameter by the SDAP responsible for the IP flow and the RB mapping.
  • LCH1, LCH2, and LCH3 have different priorities, for example, the priority of the LCH1 is greater than the priority of the LCH2, the priority of the LCH2 and the priority of the LCH3, and the uplink BSR of the terminal device is preferentially reported.
  • the amount of data to be sent of the first AM RLC entity or the amount of data to be transmitted of the LCH is reported from high to low according to the LCH priority.
  • the first AM RLC entity, the first UM RLC entity, and the second UM sub-RLC entity respectively configure t-Reordering timers or reassembly segmentation timers of different durations And each t-Reordering timer or the reassembly segmentation timer is used by the receiving end of the corresponding RLC entity to detect whether the RLC PDU sent by the access network device is lost.
  • the first AM RLC entity finds that the I frame RLC PDU sent by the access network device is not received, and the first AM RLC entity starts its configured t-Reordering timer or a reassembly segmentation timer, where The t-Reordering timer or the reassembly segmentation timer expires, triggering the terminal device to send a status report to the access network device, where the status report includes the t-Reordering timer or the reassembly segmentation timer expires
  • the receiving end receives status information of all RLC PDUs, for example, including the sequence number of the I frame RLC PDU that has been lost and/or the sequence number of the I frame RLC PDU that is successfully received.
  • the first AM RLC entity receiving end determines whether the unreceived I frame RLC PDU is received when the t-Reordering timer or the reassembly segmentation timer expires, if the first AM RLC The entity does not receive the I frame RLC PDU that is not received, the terminal device determines that the I frame RLC PDU sent by the access network device is lost, and then sends a status report to the access network device.
  • the status report includes status information that the receiving end receives all RLC PDUs when the t-Reordering timer or the reassembly segmentation timer expires, for example, including the I frame RLC PDU sent by the access network device that is not received. Serial number.
  • the PDCP entity corresponds to at least two AM RLC entities that all adopt RLC AM, for example, one AM RLC entity is used to transmit an I frame RLC PDU, and another AM RLC entity is used for transmission.
  • P frame RLC PDU, and at least one of the at least two AM RLC entities is configured to continue waiting for a timer, each of the continuation wait timers being used in a status report for which its corresponding AM RLC entity continues to wait for its transmission The indicated RLC PDU sent by the access network device that is not received.
  • the AM RLC entity configured to continue to wait for a timer sends a status report to the access network device when the t-Reordering timer or the reassembly segmentation timer expires or according to a status report transmission request sent by the access network device, Activating a continuation wait timer of its configuration, continuing to receive the unreceived RLC PDU within the duration of the continuation wait timer, and determining whether the unreceived RLC PDU can be received before the continuation wait timer expires, where
  • the status report includes status information that the receiving end receives all RLC PDUs when the t-Reordering timer or the reassembly segmentation timer expires, for example, includes a sequence of RLC PDUs sent by the access network device that is not received.
  • the terminal device determines that the RLC PDU sent by the access network device is lost, optionally, And transmitting, to the access network device, an latest status report or indication information of a mobile window, where the latest status report includes status information that the receiving end receives all RLC PDUs when the continuation wait timer expires.
  • the indication information of the moving window is used to indicate that the sequence number of the lost RLC PDU or the next desired RLC PDU packet is no longer received.
  • the terminal device when the terminal device continues to wait for the timer to time out, the terminal device performs a push window of the receiving window to receive the RLC PDU sent by the access network device next time, and the terminal device notifies the The terminal device of the access network device has been pushed to the window.
  • the terminal device performs a push window of the receiving window to receive the RLC PDU sent by the access network device next time, and the terminal device notifies the The terminal device of the access network device has been pushed to the window.
  • the access network device configures a first maximum retransmission number of the first AM RLC entity of the terminal device, and the first AM RLC entity receives the RLC PDU and receives the RLC PDU. Retransmitting the RLC PDU after the NACK sent by the access network device, and if the RLC PDU is not successfully sent after retransmitting the first maximum number of retransmissions, discarding the retransmitted RLC PDU, the terminal device The access network device is not notified to trigger the RLC re-establishment, that is, it is not used as the basis for the RLF judgment.
  • the terminal device sends the latest status report or the indication information of the mobile window to the access network device, where the indication information of the mobile window is used to indicate that a plurality of the lost RLC PDU packets are no longer received.
  • the serial number or the sequence number of the next expected RLC PDU packet is used to indicate that a plurality of the lost RLC PDU packets are no longer received.
  • the access network device configures the first AM RLC entity of the terminal device with a second maximum number of retransmissions, and the first AM RLC entity receives the RLC PDU and receives the RCM PDU. Retransmitting the RLC PDU after the NACK sent by the access network device, and if the RLC PDU is not successfully sent after retransmitting the second maximum number of retransmissions, discarding the retransmitted RLC PDU, the terminal device Notifying the access network device to trigger RLC reestablishment.
  • FIG. 10 is a schematic flowchart of a data transmission processing method according to an embodiment of the present invention.
  • the data transmission processing method in this embodiment is performed by a terminal device, and the access network device may be 2G, 3G, 4G or
  • the main process of the base station of the 5G communication system is as follows.
  • Step 101 The terminal device receives configuration information sent by the access network device, where the configuration information is that one PDCP entity of the terminal device is mapped to at least two different RLC entities.
  • Step 102 The terminal device selects data transmission by using different RLC entities according to the type of the data stream or the QoS requirement of the data stream.
  • the access network device configures one PDCP entity of the terminal device to correspond to at least two different RLC entities, for example, one RB or LCH corresponds to one RLC entity.
  • the PDCP entity of the terminal device selects to use different RLC entities for data transmission according to the type of the data stream or the QoS requirement of the data stream.
  • a PDCP entity adopts at least two logical channels
  • different LCHs of the UM RLC or the AM RLC entity have different priorities
  • the terminal device preferentially reports the AM RLC entity to be sent when transmitting the uplink BSR.
  • the amount of data or the amount of data to be transmitted of the LCH is reported from high to low according to the LCH priority.
  • the at least two different RLC entities each adopt an RLC AM or an RLC UM, and the at least two different RLC entities respectively configure timers of different durations (may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • timers of different durations may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • one of the RLC entities corresponding to the terminal device PDCP entity discovers that the RLC PDU sent by the access network device is not received, and the RLC entity starts its configured t-Reordering timer or reassembly segmentation timer, where t - the Reordering timer or the reassembly segmentation timer expires, triggering the terminal device to send a status report to the access network device, the status report including the t-Reordering timer or the reassembly segmentation timer when the timeout is
  • the terminal receives status information of all RLC PDUs, for example, including the sequence number of the RLC PDU sent by the access network device that has been lost, and/or the sequence number of the RLC PDU sent by the access network device that is successfully received.
  • the RLC entity receiving end using the RLC AM or the RLC UM determines whether the unreceived RLC PDU is received when the t-Reordering timer or the reassembly segmentation timer expires, if the RLC entity does not receive And to the unreceived RLC PDU, the terminal device determines that the RLC PDU sent by the access network device is lost, and then sends a status report to the access network device, where the status report includes the t-Reordering timer or When the reassembly segmentation timer expires, the receiving end receives status information of all RLC PDUs, for example, including the sequence number of the RLC PDU sent by the access network device that is not received.
  • the at least two different RLC entities all adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer (may be referred to as continuing waiting timing) And each of the continuation wait timers for its corresponding RLC entity to continue to wait to receive the RLC PDUs sent by the access network device that are not received as indicated in the status report sent by it.
  • the RLC entity configured to continue to wait for the timer sends a request when the t-Reordering timer or the reassembly segmentation timer expires or according to the status report sent by the access network device, and the terminal device sends the request to the access network device.
  • Sending a status report starting its configured continuation wait timer, continuing to receive the unreceived RLC PDU within the duration of the continuation wait timer, determining whether the unreceived RLC PDU can be before the continuation wait timer expires Receiving, wherein the status report includes status information of receiving all data packets when the t-Reordering timer or the reassembly segmentation timer expires or receiving a status report transmission request, for example, including the access network that is not received The serial number of the RLC PDU sent by the device.
  • the configuration continues to wait for the RLC entity of the timer or does not receive the unreceived RLC PDU, and the terminal device determines that the RLC PDU sent by the access network device is lost.
  • the access network device sends the latest status report.
  • the terminal device when the terminal device continues to wait for the timer to time out, the terminal device performs a push window of the receiving window to receive the RLC PDU sent by the access network device next time, and the terminal device notifies the The terminal device of the access network device has been pushed to the window.
  • the terminal device performs a push window of the receiving window to receive the RLC PDU sent by the access network device next time, and the terminal device notifies the The terminal device of the access network device has been pushed to the window.
  • the terminal device further receives a first maximum number of retransmissions configured by the access network device to the AM RLC entity of the terminal device, and the AM RLC entity of the terminal device sends the RLC.
  • the PDU After receiving the NACK sent by the access network device, the PDU retransmits the RLC PDU, and if the RLC PDU is not successfully sent after the first maximum retransmission number is retransmitted, the retransmitted RLC PDU is discarded.
  • the terminal device does not notify the access network device to trigger RLC re-establishment, that is, does not serve as a basis for RLF determination.
  • the terminal device further receives a second maximum number of retransmissions configured by the access network device to the AM RLC entity of the terminal device, and the AM RLC entity of the terminal device sends the RLC.
  • the PDU After receiving the NACK sent by the access network device, the PDU retransmits the RLC PDU, and if the RLC PDU is not successfully sent after the second maximum retransmission number is retransmitted, the retransmitted RLC PDU is discarded.
  • the terminal device notifies the access network device to trigger RLC reestablishment.
  • the PDCP entity of the terminal device may select to use different RLC entities for data transmission according to the type of the data stream or the QoS requirement, because one PDCP entity of the terminal device is mapped to at least two different RLC entities. Ensure the normal transmission of different services and improve the reliability while ensuring the service experience.
  • FIG. 11 is a schematic structural diagram of another communication system according to another embodiment of the present invention.
  • the communication system includes an access network device 111 and a terminal device 112, and the access network device communicates with the terminal device through air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system
  • the terminal device 112 includes: a receiver 1121, a processor 1122, a transmitter 1123, and a memory 1124, where The receiver 1121, the processor 1122, the transmitter 1123, and the memory 1124 communicate with each other via a bus.
  • the processor 1122 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 1124 is used to store code or instruction information, and may also store information of a device type.
  • the memory 1124 can include a ROM and a RAM for providing instructions and data to the processor 1122.
  • a portion of the memory 1124 can also include a non-volatile random access memory.
  • the receiver 1121 is configured to receive configuration information sent by the access network device 111, where the configuration information is that one PDCP entity of the terminal device is mapped to at least two different RLC entities.
  • the transmitter 1123 is configured to select data transmission by using different RLC entities according to the type of the data stream or the QoS requirement of the data stream.
  • the access network device configures one PDCP entity of the terminal device to correspond to at least two different RLC entities, for example, one RB or LCH corresponds to one RLC entity.
  • the PDCP entity of the terminal device selects to use different RLC entities for data transmission according to the type of the data stream or the QoS requirement of the data stream.
  • a PDCP entity uses at least two logical channels
  • different LCHs of the UM RLC or the AM RLC entity have different priorities
  • the transmitter 1123 is configured to preferentially report the AM when the uplink BSR is sent.
  • the amount of data to be sent of the RLC entity or the amount of data to be transmitted reported by the LCH from high to low according to the LCH priority.
  • the at least two different RLC entities each adopt an RLC AM or an RLC UM, and the at least two different RLC entities respectively configure timers of different durations (may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • timers of different durations may be called t- a reordering timer or a reassembly segmentation timer, where each t-Reordering timer or reassembly segmentation timer is used by the RLC entity receiving end of the RLC AM or RLC UM of the terminal device to detect the transmission by the access network device Whether the RLC PDU is lost.
  • one of the RLC entities corresponding to the terminal device PDCP entity discovers that the RLC PDU sent by the access network device is not received, and the RLC entity starts its configured t-Reordering timer or reassembly segmentation timer, where t - the Reordering timer or the reassembly segmentation timer expires, triggering the sender 1123 to send a status report to the access network device, where the status report includes the t-Reordering timer or the reassembly segmentation timer expires
  • the receiving end receives status information of all RLC PDUs, for example, including the sequence number of the RLC PDU sent by the access network device that has been lost, and/or the sequence number of the RLC PDU sent by the access network device that is successfully received.
  • the RLC entity receiving end using the RLC AM or the RLC UM determines whether the unreceived RLC PDU is received when the t-Reordering timer or the reassembly segmentation timer expires, if the RLC entity does not receive Up to the unreceived RLC PDU, the processor 1122 determines that the RLC PDU sent by the access network device is lost, and then the sender 1123 sends a status report to the access network device, where the status report includes the When the t-Reordering timer or the reassembly segmentation timer expires, the receiving end receives status information of all RLC PDUs, for example, including the sequence number of the RLC PDU sent by the access network device that is not received.
  • the at least two different RLC entities all adopt an RLC AM, and at least one of the at least two different RLC entities configures a timer (may be referred to as continuing waiting timing) And each of the continuation wait timers for its corresponding RLC entity to continue to wait to receive the RLC PDUs sent by the access network device that are not received as indicated in the status report sent by it.
  • the RLC entity configured to continue to wait for a timer sends a request when the t-Reordering timer or the reassembly segmentation timer expires or according to a status report sent by the access network device, and the transmitter 1123 sends the request to the access network.
  • the device sends a status report, and the configuration continues to wait for the RLC entity of the timer to start its configured continuation wait timer, continues to receive the unreceived RLC PDU within the duration of the continuation wait timer, and determines that the RLC is not received. Whether the PDU can be received before the continuation wait timer expires, wherein the status report includes status information of the RLC PDU received by the receiving end when the t-Reordering timer or the reassembly segmentation timer expires, for example, including The received serial number of the RLC PDU sent by the access network device.
  • the configuration continues to wait for the RLC entity of the timer to still receive the unreceived RLC PDU, and the processor 1122 determines that the RLC PDU sent by the access network device is lost.
  • the transmitter 1123 sends the latest status report to the access network device, where the latest status report includes status information of the receiving end receiving all RLC PDUs when the continuation wait timer expires.
  • the processor 1122 performs a push window of the receiving window when the waiting for the timer expires, so that the receiver 1121 receives the RLC PDU sent by the access network device next time.
  • the sender 1123 notifies the access network device that the terminal device has pushed the window.
  • the specific window please refer to the description of the subsequent push window embodiment.
  • the receiver 1121 is further configured to receive a first maximum number of retransmissions configured by the access network device to an AM RLC entity of the terminal device, and the terminal RTL of the terminal device After the entity sends the RLC PDU, if the receiver 1121 receives the NACK sent by the access network device, the sender 1123 retransmits the RLC PDU, and if it is retransmitted to the first maximum retransmission number, it still fails. The RLC PDU is sent, and the retransmitted RLC PDU is discarded. The sender 1123 does not notify the access network device to trigger RLC re-establishment, that is, does not serve as a basis for RLF determination.
  • the receiver 1121 is further configured to receive a second maximum number of retransmissions configured by the access network device to the AM RLC entity of the terminal device, and the AM RLC of the terminal device After the entity sends the RLC PDU, if the receiver 1121 receives the NACK sent by the access network device, the transmitter 1123 retransmits the RLC PDU, and if it is retransmitted to the second maximum retransmission number, it still fails. The RLC PDU is sent, the retransmitted RLC PDU is discarded, and the sender 1123 notifies the access network device to trigger RLC re-establishment.
  • the PDCP entity of the terminal device may select to use different RLC entities for data transmission according to the type of the data stream or the QoS requirement, because one PDCP entity of the terminal device is mapped to at least two different RLC entities. Ensure the normal transmission of different services and improve the reliability while ensuring the service experience.
  • FIG. 12 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system, where one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, when the connection When the network access device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • the RLC layer of the access network device and the RLC layer of the terminal device adopt an RLC AM mode.
  • Step 121 The receiving end determines that the value of the highest receiving state variable VR(H) is greater than the value of the receiving state variable VR(R), starts the first timer, and sets the value of the state variable VR(X).
  • the receiving end stores several variables, such as VR (R), VR (H), and VR (X). Each time the receiving end receives an RLC PDU sent by the sending end, it needs to determine VR (R). ), the variable values of VR(H) and VR(X) and the magnitude of the variable value between VR(H) and VR(R), for example, the receiving end receives an RLC sent by the transmitting end.
  • the VR The value of (H) indicates the sequence number of the RLC PDU and is incremented by 1 for the sequence number corresponding to the highest RLC PDU that was received when the first timer was started.
  • the value of the VR(R) indicates the sequence number of the RLC PDU and is started.
  • the receiving end sequentially receives the transmitting end to send a first RLC PDU, a second RLC PDU, and a third RLC PDU, where the sequence number of the first RLC PDU is 1, The sequence number of the second RLC PDU is 2, and the sequence number of the third RLC PDU is 3.
  • the lower boundary of the current receiving window is the receiving time point at which the first RLC PDU is expected to be received.
  • FIG. 13 is a schematic diagram of a data state of a data transmission process according to another embodiment of the present invention, that is, a process of changing a variable value of VR(R), VR(H), and VR(X) when a receiving end receives an RLC PDU. schematic diagram.
  • the receiving end Before receiving the RLC PDU of the sending end, the receiving end is expected to receive the first RLC PDU with the sequence number of 1, and does not currently receive any RLC PDU, that is, set VR (R), VR (H) and VR (
  • the receiving end determines that the VR (H) is equal to the VR (R); if the receiving end does not successfully receive the second RLC PDU, the highest RLC PDU that has been successfully received is the serial number 1
  • the receiving end determines that the VR (H) is greater than the VR (R); if the receiving end does not successfully receive the second RLC PDU, currently does not successfully receive any RLC PDU, and the RLC PDU that is expected to be received is
  • the receiving end determines that the VR (H) is greater than the VR (R), that is, the receiving end currently successfully receives the second RLC PDU but fails to receive the first RLC PDU, which may also be called a success.
  • the first timer (which may be called a t-Reordering timer or a reassembly segmentation timer) is started for the first RLC PDU that is not successfully received, and is started.
  • the first timer which may be called a t-Reordering timer or a reassembly segmentation timer
  • the first timer is used for the duration of the first timer of the receiving end.
  • the receiving end may further receive the RLC after the second RLC PDU, within a duration of the first timer, that is, before the first timer expires.
  • a PDU such as the third RLC PDU and an RLC PDU following the third RLC PDU.
  • Step 122 The first timer expires, the receiving end sends a status report, and starts a second timer, where the status report indicates a sequence number of the lost at least one RLC PDU.
  • the first timer expires. If the receiving end successfully receives the first RLC PDU, the highest RLC PDU that the receiving end has successfully received when the first timer expires is the serial number is 2.
  • the status information of all RLC PDUs includes, for example, a sequence number that has successfully received the first RLC PDU and a sequence number that successfully received the second RLC PDU.
  • the first timer expires. If the receiving end still fails to receive the first RLC PDU, the receiving end determines to lose the first RLC PDU, and the receiving end sends a status report to start the first timer.
  • a second timer (which may be referred to as a continuation wait timer) indicating the missing sequence number of the first RLC PDU.
  • the second timer is used by the receiving end to continue to receive the RLC PDU sent by the access network device that is not received in the status report that is sent by the receiving end, for example, the receiving end is in the second timer.
  • the first RLC PDU that is not received continues to be received within the duration to determine whether the unreceived first RLC PDU can be received before the second timer expires.
  • the receiving end may further receive an RLC PDU after the second RLC PDU, such as the third RLC PDU and an RLC PDU subsequent to the third RLC PDU, within a duration of the first timer. .
  • the receiving end When the first timer expires, if the receiving end receives the RLC PDU after the second RLC PDU as continuous reception, for example, the receiving end successfully receives the first timer when the first timer expires.
  • the RLC PDU with the highest sequence number is equal to N, and the N is a positive integer greater than or equal to 3.
  • the receiving end receives the RLC PDU after the second RLC PDU as discontinuous reception, for example, the receiving end receives the highest sequence number when the first timer expires.
  • An RLC PDU equal to N the N being a positive integer greater than or equal to 3, but before the sequence number is N, there is a first sequence number 2 that has not received at least one RLC PDU, assuming that the sequence number has been successfully received
  • the sequence number of the first unsuccessfully received RLC PDU after the second RLC PDU is M, the M is a positive integer greater than or equal to 3, and the M is less than or equal to N; when the first timer expires,
  • the RLC PDU that the receiving end expects to receive is also the first RLC PDU with sequence number 1.
  • the RLC PDU with the sequence number N/M is the first unsuccessfully received RLC PDU after the second RLC PDU, and the highest RLC PDU that the receiving end has successfully received when the first timer expires.
  • the receiving end sends a status report, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer expires.
  • the receiving end may further receive the RLC PDU after the second RLC PDU, in the duration of the second timer, that is, before the second timer expires.
  • the third RLC PDU and the RLC PDU after the third RLC PDU may be further receive the RLC PDU after the second RLC PDU, in the duration of the second timer, that is, before the second timer expires.
  • Step 123 The second timer expires, and the receiving end sets the value of the VR(R) to be all the RLC corresponding to the RLC PDU sequence number corresponding to the RLC PDU sequence number being greater than or equal to the value of the VR (X).
  • the first PDU does not receive the sequence number of the RLC PDU, and the value of the VR(X) is set to be 1 by the sequence number corresponding to the highest RLC PDU that has been received when the second timer expires.
  • the receiving end determines that the first RLC PDU sent by the sending end is lost, optionally, The access network device sends the latest status report or the mobile window indication information, and the receiving end moves the lower boundary of the receiving window when the second timer expires to or sets the next expected reception (ie, does not receive The receiving time point of the RLC PDU transmitted by the transmitting end, which is called the lower boundary movement of the receiving window.
  • the receiving end may further receive an RLC PDU after the second RLC PDU, after receiving the second RLC PDU, within a duration of the second timer, that is, before the second timer expires.
  • an RLC PDU after receiving the second RLC PDU, within a duration of the second timer, that is, before the second timer expires.
  • a lost RLC PDU occurs again, so when the second timer expires, the receiving end moves VR(R), VR(H) to the lower boundary of the receiving window.
  • the variable value of VR(X) is set to: the receiving end sets the value of the VR(R) corresponding to the value of the VR(X) when the RLC PDU sequence number is greater than or equal to the first timer startup.
  • the first one of all the RLC PDUs corresponding to the RLC PDU sequence number does not receive the sequence number of the RLC PDU, and the value of the VR (H) is set to the sequence corresponding to the highest RLC PDU that has been received when the second timer expires.
  • the number is incremented by 1, and the value of the VR(X) is set to be 1 plus the sequence number corresponding to the highest RLC PDU that has been received when the second timer expires.
  • the receiving end no longer waits to receive the first RLC PDU, but moves the lower boundary of the receiving window to the RLC PDU with the highest sequence number that has been successfully received when the first timer starts (ie, the second The received sequence number of the first unreceived RLC PDU after the RLC PDU).
  • the receiving end sends a status report or window movement indication information, where the status report includes status information of all RLC PDUs received by the receiving end when the second timer expires, and the window movement indication information includes the latest expected reception of the terminal.
  • the serial number of the RLC PDU which is the serial number of the current VR(R).
  • the receiving end receives the RLC PDU after the second RLC PDU is discontinuous reception, for example, the receiving end receives the highest when the second timer times out.
  • the RLC PDU whose sequence number is equal to K, the K is a positive integer greater than or equal to 3, but there is a non-receiving at least one RLC PDU before the sequence number is K, for example, when the first timer starts.
  • the successfully received RLC PDU with the highest sequence number is the second RLC PDU, and the sequence number of the first unsuccessfully received RLC PDU after the second RLC PDU is L, and the L is greater than or equal to 3.
  • the L is less than or equal to K; when the second timer expires, the receiving end performs a lower boundary movement of the receiving window, that is, after moving the lower boundary of the receiving window to the second RLC PDU The receiving time point of the first unsuccessfully received RLC PDU. For example, if the L is less than K, that is, the RLC PDU with the sequence number K is the RLC PDU of the highest sequence number successfully received when the second timer expires, and the RLC PDU with the sequence number L is the second RLC.
  • the receiving end no longer waits to receive the first RLC PDU, but moves the lower boundary of the receiving window from the receiving time point of the first RLC PDU that is expected to be received to when the first timer starts.
  • the receiving end sends a status report, where the status report includes status information that the receiving end receives all RLC PDUs when the second timer expires.
  • the receiving end determines that the sequence number of the received RLC PDU is the value of VR(X) when the first timer is started to the current VR (H). There is a discontinuity between the values, and a third timer is started, the third timer is used by the receiving end to determine that the value of VR(X) when the first timer is started is missing from the value of the current VR(H) Whether the RLC PDU corresponding to the serial number is lost.
  • the receiving end also starts a t-Reordering timer or a reassembly segmentation timer, that is, a third timer, for example, the receiving end is in the The three timer determines whether the RLC PDU with the sequence number M is lost.
  • the RLC PDU of M may be a fragmented or complete RLC PDU.
  • the duration of the first timer is equal to the duration of the third timer, or the duration of the first timer is not equal to the duration of the third timer.
  • the third timer is a first timer, and the terminal device has multiple first timers running at the same time, respectively managing or waiting for different ranges of RLC PDUs.
  • the receiving end starts the third timer, and the RLC PDU with the highest sequence number that has been successfully received when the first timer starts is started (for example, the second The first unreceived RLC PDU after the RLC PDU) (for example, the RLC PDU with the sequence number M), and the value of VR1(R) is set to be the RLC PDU sequence number greater than or equal to when the first timer is started.
  • the receiving end sends a status report, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer expires.
  • a status report is sent, where the status report indicates that the RLC PDU with the sequence number M is lost, and a continuation wait timer, that is, a fourth timer, is started.
  • the timer expires, and the value of the VR(R) is set to be equal to or equal to the RLC PDU sequence number corresponding to the RLC PDU sequence number corresponding to the value of the VR1 (X) set when the third timer is started.
  • the first sequence number of the RLC PDU is not received, and the value of the VR(X) is set to be 1 by the sequence number corresponding to the highest RLC PDU that has been received when the third timer expires.
  • the receiving end sends a status report, where the status report includes status information that the receiving end receives all RLC PDUs when the third timer expires.
  • the terminal device may not send the status report. .
  • the fourth timer is used by the receiving end to continue to wait for reception in the duration of the fourth timer for the RLC PDU that has lost the sequence number M, in the When the fourth timer expires, it is determined whether the RLC PDU with the sequence number M is received. If not, it is determined that the RLC PDU with the sequence number M is lost, and the lower boundary of the receiving window is moved, for example,
  • the VR1(R) is set to a sequence number of the first unreceived RLC PDU after the RLC PDU sequence number is greater than or equal to the RLC PDU with the highest sequence number that has been successfully received when the third timer is started, and the VR1 (X) is set.
  • the value of the highest RLC PDU that has been received when the fourth timer expires is incremented by one, and the value of VR1 (H) is set to correspond to the highest RLC PDU that has been received when the fourth timer expires.
  • the serial number is incremented by 1.
  • the receiving end sends a status report, where the status report includes status information that the receiving end receives all RLC PDUs when the fourth timer expires.
  • the receiving end successfully receives the t-Reordering timer or the reassembly segmentation timer before the timeout expires.
  • the RLC PDU that was not successfully received the receiving end stops the t-Reordering timer or the reassembly segmentation timer.
  • the receiver stops the continuation wait timing once the receiver successfully receives the unsuccessfully received RLC PDU before the continuation wait timer expires.
  • all the unsuccessfully received RLC PDUs detected by starting the t-Reordering timer or the reassembly segmentation timer are successfully received to stop the continuation wait timer.
  • the foregoing embodiment describes a scheme for how to receive the lower boundary movement of the window when the RLC entity of the receiving end and the RLC entity of the transmitting end transmit the RLC PDU data, and transmits the PDCD between the PDCP entity of the receiving end and the PDCD entity of the transmitting end.
  • the lower boundary mobility scheme of the receiving window of the PDU data may also be similar to the lower border mobility scheme of the receiving window for transmitting the RLC PDU data, and details are not described herein again.
  • the difference is that the PDCP layer triggers a status report of the PDCP or a mobile window indication information including the PDCP SN.
  • the PDCP layer may have at least one of a first timer, a second timer, a third timer, and a fourth timer similar to the RLC, and each timer duration may be different from a timer duration of the RLC layer.
  • each timer duration may be different from a timer duration of the RLC layer.
  • Another embodiment of the present invention for a UM RLC entity corresponding to a PDCP entity, also uses a VR (R) variable, a VR (H) variable and a VR (X), wherein the value of the VR (H) represents a PDCP PDU
  • the serial number and the sequence number corresponding to the highest PDCP PDU that has been received when the first timer is started is incremented by one, and the value of the VR(R) indicates the serial number of the PDCP PDU and is received when the first timer is started.
  • the serial number corresponding to the received PDCP PDU, the value of the VR(X) indicating the serial number of the PDCP PDU and the sequence number corresponding to the highest PDCP PDU that has been received when the first timer is started is incremented by one.
  • VR(H) is greater than VR(R)
  • the t-Reordering timer or the reassembly segmentation timer is started, and the duration of the t-Reordering timer or the reassembly segmentation timer is infinity.
  • the receiving end receives a data packet outside the window, for example, the receiving end receives the PDCP PDU whose serial number is greater than the value of VR (MR), the PDCP PDU is discarded.
  • VR(H) is greater than VR(R)
  • set VR(X) start t-Reordering timer or reassemble segmentation timer
  • t-Reordering timer or reassembly segmentation timer sorting the received PDCP PDUs according to the sequence number from small to large, the t-Reordering timer or the reassembly segmentation timer does not move the window after timeout, and the t-Reordering is performed after the timeout
  • the complete PDCP SDU in the timer or reassembly segmentation timer management window is submitted to the upper layer, and VR(X) is set to V(H). If the t-Reordering timer or the packet before the reassembly segmentation timer is received, Then discard.
  • This embodiment adapts to the push window of the PDCP corresponding to different RLC entities, and promptly pushes the PDCP window of the UM RLC to avoid data loss of the PDCP of the AM.
  • the lower boundary movement of the timely receiving window is performed for the data transmission of the RLC AM mode, thereby improving the reliability and fluency of data transmission.
  • FIG. 14 is a schematic diagram of a data state of a data transmission process according to another embodiment of the present invention.
  • the receiving end receives the RLC PDU data packet or the PDCP PDU data packet sent by the transmitting end, which is collectively referred to as a data packet in this embodiment.
  • the configuration or protocol stipulates a T1 (that is, a t-Reordering timer or a reassembly segmentation timer), and starts T1 after a non-contiguous packet occurs.
  • a T1 that is, a t-Reordering timer or a reassembly segmentation timer
  • the receiving end currently receives the data packet No. 3, and the receiving succeeds, but finds that 1
  • the configuration or protocol stipulates a timer T2 (that is, continues to wait for a timer). Before the first T1 times out, the receiving end determines whether the data packet with the sequence number 1 is lost.
  • the receiving end If the receiving end successfully receives the data packet of sequence number 1 that was not successfully received before the first T1 timeout, optionally send a status report, preferably, in this case, the status report is not sent. Stopping the first T1 initiated for the previously unreceived data packet, the receiving end continues to receive the subsequent data packet until another unsuccessfully received data packet occurs, that is, the receiving end determines VR(H)>VR (R), starting the timer second T1 again for the newly occurring unsuccessfully received packet.
  • the receiving end may further receive a data packet after the data packet No. 3, and if a non-contiguous packet occurs between the first T1 and the first T1 timeout, That is, the sequence number of the received data packet is greater than or equal to the unsuccessfully received data packet in all the data packets of the value of VR(X) or VR1(X) when the first T1 is started, that is, the serial number of the data packet. All received data packets greater than or equal to the value of VR(X) when the first T1 is started to the value of the current VR(X) are non-contiguous data packets, for starting the first T1 to the first The first unsuccessfully received packet between one T1 timeout initiates another second T1.
  • the received data packets are non-contiguous data packets.
  • the receiving end If the first T1 times out, the receiving end still does not successfully receive the data packet with the sequence number of 1, for example, the receiving end has successfully received the data packet No. 7, and the number 2, 3, and 5
  • the data packet has been successfully received, but the data packets No. 1, No. 4 and No. 6 are not successfully received, the receiving end sends a status report, and the first T2 is started, and the status report includes the receiving when the first T1 times out.
  • the terminal receives status reports of all data packets, for example, the status report indicates that the data packets No. 1, No. 4, and No. 6 are successfully received, and the data packets No. 2, No. 3, No. 5, and No. 7 are successfully received.
  • the receiving end determines that the data packet with the sequence number 1 has been lost when the first T1 times out, and the receiving end continues to wait for receiving the data packet with the sequence number 1 within the first T2 duration.
  • the data packet that the receiving end expects to receive is set to a data packet with sequence number 1.
  • the receiving end successfully receives all previously unsuccessfully received data packets before the first T2 timeout, optionally sending a status report, stopping the second T1 initiated for the unreceived data packet, and stopping the first a T2, that is, a packet whose sequence number is VR1(R) stops the second T1, and a packet whose sequence number is VR(R) stops the first T2, and the receiving end continues to receive subsequent The data packet, until another unsuccessfully received data packet occurs, that is, the receiving end judges VR(H)>VR(R), and starts the timer third T1 again for the newly occurring unsuccessfully received data packet.
  • the receiving end may also receive a data packet after the data packet No. 7, if a non-contiguous packet occurs between the start T2 and the T2 timeout, that is, the sequence of the received data packet.
  • the number is greater than or equal to the number of unsuccessfully received packets in all packets of VR(X) or VR1(X) when T2 is started, that is, the sequence number of the packet is greater than or equal to the value of VR(X) when starting T2 to the sequence. All received packets between the values of the current VR(X) are non-contiguous packets, and another third T1 is initiated for the first unsuccessfully received packet between the start of T2 and the T2 timeout.
  • the receiving end successfully receives the packet No. 9 before the T2 times out, and the packets 2, 3, 4, and 5 have been successfully received, but the packets 1 and 6 are not successfully received.
  • the receiving end stops the second T1 initiated for the data packet of sequence number 4, does not stop the first T2 initiated for the data packet with sequence number 1 and the second T1 initiated for the data packet with sequence number 6. It should be understood that if the serial number 4 and 6 data packets are found to be unsuccessfully received at the same time, the second T1 is started simultaneously for the serial number 4 and 6 data packets, and the data packet with the column number 4 is not necessarily stopped.
  • the second T1 also does not have to restart the second T1 for the number 6 packet.
  • the receiving end When the first T2 times out, the receiving end still does not successfully receive the data packet with sequence number 1 and the data packets of 2, 3, 4, and 5 have been successfully received, but the data packets of numbers 1 and 6 are successfully received. Unsuccessful reception, the receiving end moves the lower boundary of the receiving window to the first unsuccessfully received data packet in all the data packets after successfully receiving the data packet with the highest sequence number when starting T1, that is, the serial number of the data packet is greater than Or equal to the sequence number of the first unsuccessfully received data packet in all the data packets of the value packet of VR(X) when T1 is started, that is, the receiving end sets the data packet expected to be received as the serial number 6
  • the receiving end configures an uplink maximum number of retransmissions, and does not trigger an RLC reset after the maximum number of retransmissions.
  • FIG. 15 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system, and the RLC layer of the access network device and the RLC layer of the terminal device adopt an RLC AM mode, and the access network device and the terminal One of the devices is the transmitting end, and the other is the receiving end.
  • the receiving end is the receiving end.
  • the data transfer processing device includes a receiver 151, a processor 152, a transmitter 153, and a memory 154, wherein the receiver 151, the processor 152, the transmitter 153, and the memory 154 pass each other Bus communication.
  • the processor 152 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 154 is used to store code or instruction information, and may also store information of a device type.
  • the memory 154 can include ROM and RAM for providing instructions and data to the processor 152.
  • a portion of the memory 154 may also include a non-volatile random access memory.
  • the processor 152 is configured to determine that the value of the highest received state variable VR(H) is greater than the value of the received state variable VR(R), activate the first timer, and set the value of the state variable VR(X).
  • the memory 154 stores several variables, such as VR(R), VR(H), and VR(X).
  • the processor 152 receives the RLC PDU sent by the sending end each time the processor 152 receives the RLC PDU. It is necessary to determine the variable values of VR(R), VR(H) and VR(X) and to perform variable value judgment between VR(H) and VR(R), for example, the receiver 151 receives the When the RLC PDU is sent by the sending end, the processor 152 determines whether the value of the VR (H) is greater than the value of the VR (R) and starts the first timer (may be called t-Reordering timing) Or reassembly segmentation timer), the value of the VR(H) indicates the sequence number of the RLC PDU and the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by one, the VR (R) The value of the RLC PDU indicates the sequence number of the RLC PDU and is the sequence number corresponding to the R
  • the receiver 151 sequentially receives the sending end to send the first RLC PDU, the second RLC PDU, and the third RLC PDU, where the sequence number of the first RLC PDU is 1, The sequence number of the second RLC PDU is 2, and the sequence number of the third RLC PDU is 3.
  • the lower boundary of the current receiving window is the receiving time point at which the first RLC PDU is expected to be received.
  • the receiver 151 before receiving the RLC PDU of the transmitting end, the receiver 151 is expected to receive the first RLC PDU with the sequence number of 1, and does not currently receive any RLC PDU, that is, sets VR(R),
  • the receiver 151 continues to receive the second RLC PDU after successfully receiving the first RLC PDU, and if the receiver 151 successfully receives the second RLC PDU, the highest RLC currently successfully received
  • the PDU is the second RLC PDU with sequence number 2.
  • the processor 152 determines that the VR (H) is equal to the VR (R); if the receiver 151 does not successfully receive the second RLC PDU, the highest RLC PDU that has been successfully received is a sequence.
  • the processor 152 determines that the VR(H) is equal to the VR(R).
  • the receiver 151 continues to receive the second RLC PDU after successfully receiving the first RLC PDU, and if the receiver 151 successfully receives the second RLC PDU, the highest RLC that has been successfully received currently.
  • the PDU is the second RLC PDU with sequence number 2.
  • the processor 152 determines that the VR (H) is greater than the VR (R), that is, the receiver 151 successfully receives the second RLC PDU but fails to receive the first RLC PDU, the processor 152 may also be called The first timer (which may be referred to as a t-Reordering timer or a reassembly segmentation timer) is started for the first RLC PDU that is not successfully received, before the current RLC PDU is successfully received, and there is a hole for receiving the RLC PDU.
  • the first RLC PDU continues to be received within the duration of the first timer, and the processor 152 determines whether the first RLC PDU is successfully received when the first timer expires.
  • the receiver 151 may further receive an RLC PDU after the second RLC PDU, for example, the third RLC PDU, and the duration of the first timer.
  • the RLC PDU after the third RLC PDU may further receive an RLC PDU after the second RLC PDU, for example, the third RLC PDU, and the duration of the first timer.
  • the transmitter 153 is configured to send a status report to the sending end when the first timer expires, and the processor 152 is further configured to start a second timer, where the status report indicates a sequence of the lost at least one RLC PDU. number.
  • the processor 152 determines that the VR (H) is equal to the VR (R).
  • the transmitter 153 sends a status report to the sending end, where the status report includes when the first timer expires.
  • the receiver 151 receives status information of all RLC PDUs, including, for example, a sequence number that has successfully received the first RLC PDU and a sequence number that successfully received the second RLC PDU.
  • the first timer expires. If the receiver 151 still fails to receive the first RLC PDU, the processor 152 determines to lose the first RLC PDU, and the transmitter 153 sends a status report. The processor 152 initiates the second timer (which may be referred to as a continuation wait timer), the status report indicating a missing sequence number of the first RLC PDU. The second timer is used by the receiver 151 to continue to receive the RLC PDU sent by the access network device that is not received in the status report that it sends, for example, the processor 152 is at the second timing. The first RLC PDU that is not received continues to be received within the duration of the device, and it is determined whether the unreceived first RLC PDU can be received before the second timer expires.
  • the receiver 151 may also receive an RLC PDU after the second RLC PDU, such as the third RLC PDU and the RLC after the third RLC PDU, within the duration of the first timer. PDU.
  • the receiver 151 When the first timer expires, if the receiver 151 receives the RLC PDU after the second RLC PDU as continuous reception, for example, the receiver 151 has successfully succeeded when the first timer expires. Receiving an RLC PDU with a highest sequence number equal to N, the N being a positive integer greater than or equal to 3.
  • the receiver 151 When the first timer expires, if the receiver 151 receives the RLC PDU after the second RLC PDU as discontinuous reception, for example, the receiver 151 receives the highest when the first timer expires.
  • the RLC PDU whose sequence number is equal to N, the N is a positive integer greater than or equal to 3, but before the sequence number is N, there is a sequence number 2 that has not received at least one RLC PDU, assuming that the sequence number 2 has been successfully received.
  • the sequence number of the first unsuccessfully received RLC PDU after the second RLC PDU is M, the M is a positive integer greater than or equal to 3, and the M is less than or equal to N; At the same time, the receiver 151 expects the received RLC PDU to be the first RLC PDU with sequence number 1. If the M is less than N, that is, the RLC PDU with the sequence number N is successfully received, and the RLC with the sequence number M is successfully received.
  • the transmitter 153 sends a status report to the sending end, where the status report includes status information that the receiver 151 receives all RLC PDUs when the first timer expires.
  • the receiver 151 may further receive an RLC PDU after the second RLC PDU, such as the third RLC PDU, and the The RLC PDU after the third RLC PDU.
  • the processor 152 is further configured to: when the second timer expires, set the value of the VR (R) corresponding to the RLC PDU sequence number corresponding to the RLC PDU sequence number greater than or equal to the value of the VR (X) The first one of the RLC PDUs does not receive the sequence number of the RLC PDU, and the value of the VR(X) is set to be 1 plus the sequence number corresponding to the highest RLC PDU that has been received when the second timer expires.
  • the processor 152 determines that the first RLC PDU sent by the sending end is lost, optionally Sending the latest status report or moving window indication information to the access network device, the processor 152 moves the lower boundary of the receiving window when the second timer expires to or sets the next expected reception (also That is, the reception time point of the RLC PDU transmitted by the transmitting end that is not received, this process is called the lower boundary movement of the receiving window.
  • the receiver 151 may further receive the RLC PDU after the second RLC PDU, and when the RLC PDU after receiving the second RLC PDU is discontinuously received, A missing RLC PDU appears again, so when the second timer expires, the processor 152 sets the variable values of VR(R), VR(H), and VR(X) for the lower boundary of the receive window.
  • the value of the VR(R) is set to be the first of all RLC PDUs corresponding to the RLC PDU sequence number corresponding to the value of the VR (X) when the first timer is started.
  • the sequence number of the RLC PDU is not received, and the value of the VR (H) is set to be 1 by the sequence number corresponding to the highest RLC PDU that has been received when the second timer expires, and the value of the VR (X) is set.
  • the sequence number corresponding to the highest RLC PDU that has been received when the second timer expires is incremented by one. That is, the receiver 151 no longer waits to receive the first RLC PDU, but moves the lower boundary of the receiving window to the RLC PDU with the highest sequence number that has been successfully received when the first timer starts (ie, the first The received sequence number of the first unreceived RLC PDU after the second RLC PDU).
  • the transmitter 153 sends a status report or window movement indication information to the sending end, where the status report includes status information that the receiver 151 receives all RLC PDUs when the second timer expires, the window movement indication
  • the information includes the serial number of the RLC PDU that the terminal expects to receive recently, that is, the serial number of the current VR (R).
  • the receiver 151 when the second timer expires, if the receiver 151 receives the RLC PDU after the second RLC PDU as discontinuous reception, for example, the receiver 151 times when the second timer expires.
  • the transmitter 153 sends a status report to the sending end, where the status report includes status information that the receiver 151 receives all RLC PDUs when the second timer expires.
  • the processor 152 determines that the sequence number of the received RLC PDU is the value of VR(X) at the start of the first timer to the current There is a discontinuity between the values of VR(H), and a third timer is started, and the third timer is used by the processor 152 to determine whether the RLC PDU corresponding to the missing sequence number is lost.
  • the processor 152 also starts a t-Reordering timer or a reassembly segmentation timer, that is, a third timer, for example, the processor 152 is in the The third timer determines whether the RLC PDU with the sequence number M is lost. It should be understood that the RLC PDU of M may be a fragmented or complete RLC PDU.
  • the duration of the first timer is equal to the duration of the third timer, or the duration of the first timer is not equal to the duration of the third timer.
  • the third timer is a first timer, and the terminal device has multiple first timers running at the same time, respectively managing or waiting for different ranges of RLC PDUs.
  • the processor 152 starts the third timer, and the RLC PDU with the highest sequence number that has been successfully received when the first timer is started (for example, the first The first unreceived RLC PDU after the second RLC PDU) (for example, the RLC PDU with the sequence number M), setting the value of VR1(R) to be the RLC PDU sequence number greater than or equal to the first timer is started.
  • the transmitter 153 sends a status report to the sending end, where the status report includes status information that the receiver 151 receives all RLC PDUs when the first timer expires.
  • a status report is sent, where the status report indicates that the RLC PDU with the sequence number M is lost, and a continuation wait timer, that is, a fourth timer, is started.
  • the timer expires, and the value of the VR(R) is set to be equal to or equal to the RLC PDU sequence number corresponding to the RLC PDU sequence number corresponding to the value of the VR1 (X) set when the third timer is started.
  • the first sequence number of the RLC PDU is not received, and the value of the VR(X) is set to be 1 by the sequence number corresponding to the highest RLC PDU that has been received when the third timer expires.
  • the transmitter 153 sends a status report to the sending end, where the status report includes status information that the receiver 151 receives all RLC PDUs when the third timer expires.
  • the terminal device may not send the status report. .
  • the fourth timer is used by the receiver 151 to continue to wait for reception in the duration of the fourth timer for the RLC PDU that has lost the sequence number M.
  • the fourth timer expires, it is determined whether the RLC PDU with the sequence number M is received.
  • the lower boundary of the receiving window is moved, for example, Setting the VR1(R) to a sequence number of the first unreceived RLC PDU after the RLC PDU sequence number is greater than or equal to the RLC PDU with the highest sequence number that has been successfully received when the third timer is started, and setting VR1 ( The value of X) is incremented by 1 in the sequence number corresponding to the highest RLC PDU that has been received when the fourth timer expires, and the value of VR1(H) is set to be the highest RLC PDU that has been received when the fourth timer expires. The corresponding serial number is incremented by 1.
  • the transmitter 153 sends a status report to the sending end, where the status report includes status information that the receiver 151 receives all RLC PDUs when the fourth timer expires.
  • the receiver 151 is successfully received before the t-Reordering timer or the reassembly segmentation timer expires.
  • the processor 152 stops the t-Reordering timer or the reassembly segmentation timer.
  • the processor 152 stops the continuation once the receiver 151 successfully receives the unsuccessfully received RLC PDU before the continuation wait timer expires. Waiting for the timer. It should be understood that all the unsuccessfully received RLC PDUs detected by starting the t-Reordering timer or the reassembly segmentation timer are successfully received to stop the continuation wait timer.
  • the foregoing embodiment describes a scheme for how to receive the lower boundary movement of the window when the RLC entity of the receiving end and the RLC entity of the transmitting end transmit the RLC PDU data, and transmits the PDCD between the PDCP entity of the receiving end and the PDCD entity of the transmitting end.
  • the lower boundary mobility scheme of the receiving window of the PDU data may also be similar to the lower border mobility scheme of the receiving window for transmitting the RLC PDU data, and details are not described herein again.
  • the difference is that the PDCP layer triggers a status report of the PDCP or a mobile window indication information including the PDCP SN.
  • the PDCP layer may have at least one of a first timer, a second timer, a third timer, and a fourth timer similar to the RLC, and each timer duration may be different from a timer duration of the RLC layer.
  • each timer duration may be different from a timer duration of the RLC layer.
  • Another embodiment of the present invention for a UM RLC entity corresponding to a PDCP entity, also uses a VR (R) variable, a VR (H) variable and a VR (X), wherein the value of the VR (H) represents a PDCP PDU
  • the serial number and the sequence number corresponding to the highest PDCP PDU that has been received when the first timer is started is incremented by one, and the value of the VR(R) indicates the serial number of the PDCP PDU and is received when the first timer is started.
  • the serial number corresponding to the received PDCP PDU, the value of the VR(X) indicating the serial number of the PDCP PDU and the sequence number corresponding to the highest PDCP PDU that has been received when the first timer is started is incremented by one.
  • the receiving window length is 100.
  • the processor 152 determines that VR(H) is greater than VR(R), sets VR(X), starts a t-Reordering timer or reassembles the segmentation timer, and manages the weight based on the t-Reordering timer or the reassembly segmentation timer.
  • a sorting window for example, sorting received PDCP PDUs from small to large according to a sequence number
  • the processor 152 sets VR(X) to V(H), and VR(R) is set to be greater than or equal to VR (X)
  • the AM RLC entity corresponds to one PDCP entity
  • the receiver 151 receives the data packet of the lower boundary, that is, receives the data packet with the sequence number of VR(R)
  • the processor 152 determines that VR(H) is greater than VR(R)
  • the t-Reordering timer or the reassembly segmentation timer is started, and the duration of the t-Reordering timer or the reassembly segmentation timer is infinity.
  • the receiver 151 receives a data packet outside the window, for example, the receiver 151 to a PDCP PDU whose sequence number is a value greater than VR (MR), the PDCP PDU is discarded.
  • a sorting window for example, sorting received PDCP PDUs according to a sequence number from small to large, the t-Reordering timer or the reassembly segmentation timer does not move the window after timeout
  • the transmitter 153 delivers the complete PDCP SDU in the t-Reordering timer or the reassembly segmentation timer management window to the upper layer after the timeout
  • the processor 152 sets VR(X) to V(H).
  • the packet before the receiver 151 receives the t-Reordering timer or the reassembly segmentation timer sorting window is discarded.
  • This embodiment adapts to the push window of the PDCP corresponding to different RLC entities, and promptly pushes the PDCP window of the UM RLC to avoid data loss of the PDCP of the AM.
  • FIG. 16 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, where one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, When the access network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • Step 161 when the receiving end determines that the value of the highest receiving state variable VR(H) is greater than the value of the receiving state variable VR(R), sends a status report to the transmitting end, starts the first timer, and sets the value of the state variable VR(X). .
  • the first timer is used by the receiving end to detect whether the RLC PDU corresponding to the value of the sequence number VR(R) that is not successfully received is discarded, and the receiving end receives the sequence number within the duration of the first timer.
  • the status report includes status information that the receiving end receives all RLC PDUs when the first timer is started, for example, the status report includes a sequence number of at least one RLC PDU that is not successfully received.
  • the value of the VR (H) indicates the sequence number of the RLC PDU and the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by 1, and the value of the VR (R) indicates the sequence number of the RLC PDU. And the sequence number corresponding to the RLC PDU that the receiving end expects to receive when starting the first timer, where the value of the VR(X) indicates the sequence number of the RLC PDU and is the highest RLC that has been received when the first timer is started. The sequence number corresponding to the PDU is incremented by 1.
  • Step 162 Before the first timer expires, the receiving end determines that the sequence number of the received RLC PDU exists between the value of the VR(X) at the start of the first timer and the value of the current VR(H). When continuous, the third timer is started.
  • the third timer is used by the receiving end to determine whether the RLC PDU corresponding to the missing sequence number is lost.
  • Step 163 When the first timer expires, set the value of VR(R) to be the RLC PDU sequence number greater than or equal to the RLC PDU sequence number corresponding to the value of the VR(X) when the first timer is started. Receiving a sequence number of the first unsuccessfully received RLC PDU in the RLC PDU, and setting a value of VR(X) when the first timer expires as a value of VR(H) when the first timer expires .
  • the status report or the window movement indication information may be optionally sent to the sending end, where the status report includes the first timing.
  • the receiver receives status information of all RLC PDUs when the third timer expires, for example, the status report includes a sequence number of at least one RLC PDU that is not received.
  • the window movement indication information includes a sequence number of the latest RLC PDU that the terminal expects to receive, that is, a sequence number of the current VR (R).
  • FIG. 17 is a schematic diagram of a data state of a data transmission process according to another embodiment of the present invention.
  • the receiving end receives the RLC PDU data packet or the PDCP PDU data packet sent by the transmitting end, which is collectively referred to as a data packet in this embodiment.
  • the configuration or protocol stipulates a T1, and the receiving end determines that the non-contiguous packet is started, and then starts T1.
  • the receiving end starts T1, and sends a status report to the sending end, where the status report includes starting T1, and the receiving end receives all data packets.
  • the status information includes, for example, the sequence number of the unsuccessfully received and successfully received data packet, for example, the sequence number of the unsuccessfully received data packet is 1, and the serial number of the successfully received data packet is 2 and 3.
  • the receiving end continues to receive the data packet with sequence number 1 within the T1 duration.
  • the receiving end successfully receives the data packet with the serial number 1 that was not successfully received before the first T1 timeout, set VR(R) to be greater than or equal to the VR(X) serial number.
  • the first one does not receive the serial number of the large RLC PDU, and optionally sends a status report or window movement indication information, stops the T1 initiated for the data packet with the sequence number of 1, and the receiving end continues to receive subsequent data packets.
  • the receiving end judges VR(H)>VR(R)
  • starts another timer T1 for the newly occurring unsuccessfully received data packet starts another timer T1 for the newly occurring unsuccessfully received data packet, and sets VR ( X) Add 1 to the highest sequence number of the currently successfully received packet.
  • the window movement indication information indicates a sequence number VR(R) that the current receiving end expects to receive.
  • the receiving end may also receive a data packet after the data packet No. 3, if a non-contiguous packet occurs between the T1 and the T1 timeout, that is, the received data packet If the sequence number is greater than or equal to the value of VR(X) or VR1(X) when the T1 is started, the unsuccessfully received data packet appears in the data packet, that is, the sequence number of the data packet is greater than or equal to when the T1 is started.
  • the value of VR(X) to all received packets between the sequence number of the current VR(X) is a non-contiguous packet, and the first unsuccessful reception between the T1 and the T1 timeout is initiated. The packet starts another T1.
  • the receiving end When the T1 times out, the receiving end still fails to receive the data packet with the serial number of 1, and the data packets of 2, 3, 4, and 5 have been successfully received, but the data packets of the first and sixth packets are unsuccessful. Receiving, the receiving end moves the lower boundary of the receiving window to the first unsuccessfully received data packet in all the data packets after successfully receiving the data packet with the highest sequence number when starting T1, that is, the serial number of the data packet is greater than or equal to The serial number of the first unsuccessfully received data packet in all the data packets of the value packet of VR(X) when T1 is started, that is, the data packet that the receiving end expects to receive is set as the data packet with sequence number 6.
  • the receiving end sends a status report or the window movement indication information, where the status report includes a status report that the receiving end receives all data packets when the T1 times out.
  • the window movement indication information indicates that the sequence number that the receiving end expects to receive is 6.
  • the receiving end configures an uplink maximum number of retransmissions, and does not trigger an RLC reset after the maximum number of retransmissions.
  • FIG. 18 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system, where one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, when the access When the network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • the data transmission processing device is the receiving end, and the data transmission processing device includes a receiver 181, a processor 182, a transmitter 183, and a memory 184, wherein the receiver 181 and the processor 182 The transmitter 183 and the memory 184 communicate with each other via a bus.
  • the processor 182 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 184 is used to store code or instruction information, and may also store information of a device type.
  • the memory 184 can include ROM and RAM for providing instructions and data to the processor 182.
  • a portion of the memory 184 may also include a non-volatile random access memory.
  • the receiver 181 is configured to receive an RLC PDU sent by the sending end.
  • the processor 182 When the processor 182 is configured to determine that the value of the highest received state variable VR(H) is greater than the value of the received state variable VR(R), the first timer is started, and the value of the state variable VR(X) is set.
  • the transmitter 183 is configured to send a status report to the transmitting end when the processor 182 determines that the value of the highest received state variable VR(H) is greater than the value of the received state variable VR(R).
  • the first timer is used by the processor 182 to detect whether the RLC PDU corresponding to the value of the VR(R) that is not successfully received is discarded, and the receiver 181 receives the duration of the first timer.
  • the serial number is the RLC PDU corresponding to the value of VR(R).
  • the status report includes status information that the receiving end receives all RLC PDUs when the first timer is started, for example, the status report includes a sequence number of at least one RLC PDU that is not successfully received.
  • the value of the VR (H) indicates the sequence number of the RLC PDU and the sequence number corresponding to the highest RLC PDU that has been received when the first timer is started is incremented by 1, and the value of the VR (R) indicates the sequence number of the RLC PDU. And the sequence number corresponding to the RLC PDU that the receiving end expects to receive when starting the first timer, where the value of the VR(X) indicates the sequence number of the RLC PDU and is the highest RLC that has been received when the first timer is started. The sequence number corresponding to the PDU is incremented by 1.
  • the processor 182 is further configured to determine, before the first timer expires, a value of the VR(X) of the sequence number of the received RLC PDU at the start of the first timer to a value of the current VR(H).
  • a third timer is started, and the third timer is used by the receiving end to determine whether the RLC PDU corresponding to the missing sequence number is lost.
  • the processor 182 is further configured to: when the first timer expires, set a value of VR(R), the RLC PDU sequence number is greater than or equal to the RLC corresponding to the value of the VR(X) when the first timer is started.
  • the sequence number of the first unsuccessfully received RLC PDU in the RLC PDU of the PDU sequence number, and the value of the VR(X) when the first timer expires is set to the VR when the first timer expires.
  • the transmitter 183 is further configured to: when the first timer or the third timer expires, send a status report to the sending end, where the status report includes the The receiving end receives status information of all RLC PDUs when a timer or a third timer expires, for example, the status report includes a sequence number of at least one RLC PDU that is not received.
  • timers such as a t-Reordering timer, a reassembly segmentation timer, a continuation wait timer, a first timer, a second timer, a third timer, or a fourth timer. If a packet that starts a timer (such as an RLC PDU or a PDCP PDU) is successfully received before its corresponding timer expires, the timer is stopped. For example, when the receiving end finds that an RLC PDU or a PDCP PDU is not successfully received, the t-Reordering timer is started.
  • a timer such as an RLC PDU or a PDCP PDU
  • the t-Reordering timer is stopped. For example, the receiving end starts to detect a t-Reordering timer for an RLC PDU or a PDCP PDU. If the receiving end does not successfully receive the RLC PDU or the PDCP PDU when the t-Reordering timer expires, The receiving end starts a continuation wait timer for the RLC PDU or the PDCP PDU, and if the receiving end successfully receives the RLC PDU or the PDCP PDU, the continuation wait timer stops before the continuation wait timer expires .
  • the t-Reordering timer, the reassembly segmentation timer, the continuation wait timer, and the first timer, the second timer, the third timer, or the fourth timer are all stopped when timeout.
  • FIG. 19 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system, where one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, when the connection When the network access device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • Step 191 The RLC layer of the sending end receives the discarding indication of discarding the first PDCP PDU sent by the PDCP layer of the sending end.
  • Step 192 The RLC layer of the sending end discards the RLC PDU corresponding to the first PDCP PDU or the RLC SDU corresponding to the first PDCP PDU according to the discarding indication.
  • the RLC layer discards the RLC SDU corresponding to the first PDCP PDU according to the discarding indication.
  • the processing, by the RLC layer, that the first PDCP PDU has not been processed includes: the RLC layer has not performed the RLC serial number number on the first PDCP PDU or does not generate the The RLC PDU corresponding to the first PDCP PDU.
  • the RLC layer if the RLC layer has performed the RLC sequence number numbering on the first PDCP PDU or has generated the RLC PDU corresponding to the first PDCP PDU or has sent the first PDCP PDU, And the RLC layer discards the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, and notifies the receiving end to discard the sequence number corresponding to the RLC PDU.
  • the PDCP layer of the sending end determines to discard the first PDCP PDU, and notifies the PDCP of the PDCP discarded by the PDCP of the receiving end.
  • the discarding indication carries information for discarding the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, where the RLC layer is used by Receiving the first PDCP PDU starts the drop timer and discarding the first PDCP PDU when the drop timer expires.
  • the RLC layer discards the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, and notifies the receiving end to discard the sequence number corresponding to the RLC PDU.
  • FIG. 20 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a 2G/3G/4G base station or a gNB in a 5G communication system, where one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, when the access When the network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • the sending end is the data transmission processing device
  • the data transmission processing device includes the receiver 201 and the processor 202.
  • the transmitter 203 and the memory 204 wherein the receiver 201, the processor 202, the transmitter 203, and the memory 204 communicate with each other through a bus.
  • the processor 202 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 204 is used to store code or instruction information, and may also store information of a device type.
  • the memory 204 can include ROM and RAM for providing instructions and data to the processor 202.
  • a portion of the memory 204 may also include a non-volatile random access memory.
  • the receiver 201 is configured to receive a discard indication of discarding the first PDCP PDU sent by the PDCP layer of the sending end.
  • the processor 202 is configured to discard the RLC PDU corresponding to the first PDCP PDU or the RLC SDU corresponding to the first PDCP PDU according to the discarding indication.
  • the processor 202 if the processor 202 has not processed the first PDCP PDU, the processor 202 discards the RLC corresponding to the first PDCP PDU according to the discarding indication. SDU.
  • the processing, by the processor 202, that the first PDCP PDU has not been processed includes: the processor 202 has not performed an RLC serial number or not generated on the first PDCP PDU. The RLC PDU corresponding to the first PDCP PDU.
  • the processor 202 if the processor 202 has performed the RLC sequence number numbering on the first PDCP PDU or has generated the RLC PDU corresponding to the first PDCP PDU or has sent the first PDCP PDU The processor 202 discards the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, and notifies the receiving end to discard the sequence number corresponding to the RLC PDU.
  • the discarding indication carries information for discarding the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, and the receiver 201 is configured to: Upon receiving the first PDCP PDU, the processor 202 is configured to start the drop timer and discard the first PDCP PDU when the drop timer expires.
  • FIG. 21 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, the distributed base station includes an RRU and a BBU, and the gNB includes a CU and a DU, but for simplicity of description, the present
  • the embodiment is described by taking the gNB as an example.
  • One of the access network devices and the terminal device is a transmitting end, and the other party is a receiving end. For example, when the access network device is a transmitting end, the terminal device is receiving. And vice versa.
  • Step 211 The DU receives a drop timer sent by the CU for the first bearer or the first logical channel (group).
  • the discarding timer sent by the first bearer or the first logical channel (group) may be a discard timer shared by one or more bearers of the terminal device.
  • the drop timer includes a drop for managing RLC SDUs, RLC PDUs, or PDCP PDUs.
  • Step 212 When the DU receives the PDCP PDU of the first bearer or the first logical channel (group) sent by the CU, the discarding timer is started, and the PDCP PDU is discarded when the discarding timer expires. .
  • the DU discards the RLC SDU corresponding to the PDCP PDU when the discard timer expires.
  • the processing, by the DU, that the PDCP PDU is not processed includes: the DU does not perform an RLC sequence number numbering on the PDCP PDU or does not generate an RLC PDU corresponding to the PDCP PDU.
  • the DU if the DU has performed the RLC sequence number numbering on the PDCP PDU or has generated the RLC PDU corresponding to the PDCP PDU or has sent the PDCP PDU, the DU is in the discarding When the timer expires, the RLC PDU corresponding to the PDCP PDU is discarded and the terminal device is notified to discard the sequence number corresponding to the RLC PDU.
  • the PDCP layer of the sending end determines to discard the PDCP PDU, and notifies the PDCP of the PDCP discarded by the PDCP of the receiving end.
  • FIG. 22 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface, and the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system.
  • the distributed base station includes an RRU and a BBU, and the gNB includes a CU and a DU, and one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, when the access network device is a transmitting end.
  • the terminal device is the receiving end and vice versa.
  • the data transmission processing device is the DU, and the data transmission processing device includes a receiver 221, a processor 222, and a transmitter 223. And a memory 224, wherein the receiver 221, the processor 222, the transmitter 223, and the memory 224 are in communication with each other via a bus.
  • the processor 222 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 224 is used to store code or instruction information, and may also store information of a device type.
  • the memory 224 can include ROM and RAM for providing instructions and data to the processor 222.
  • a portion of the memory 224 may also include a non-volatile random access memory.
  • the receiver 221 is configured to receive a drop timer sent by the CU for the first bearer or the first logical channel (group).
  • the processor 222 is configured to start the discarding timer when the DU receives the first bearer or the PDCP PDU of the first logical channel (group) sent by the CU, when the discard timer expires Discard the PDCP PDU.
  • the processor 222 if the processor 222 has not processed the PDCP PDU, the processor 222 discards the RLC SDU corresponding to the PDCP PDU when the discard timer expires.
  • the processor 222 does not process the PDCP PDU, and the processor 222 does not perform an RLC sequence number numbering on the PDCP PDU or does not generate an RLC corresponding to the PDCP PDU. PDU.
  • the processor 222 has performed the RLC serial number number on the PDCP PDU or has generated the RLC PDU corresponding to the PDCP PDU or has sent the PDCP PDU,
  • the processor 222 is further configured to discard the RLC PDU corresponding to the PDCP PDU when the discarding timer expires, and the transmitter 223 is configured to notify the terminal device to discard the sequence number corresponding to the RLC PDU.
  • FIG. 23 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, where one of the access network device and the terminal device is a transmitting end, and the other is a receiving end, for example, When the access network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • Step 231 After receiving the upper layer packet, the PDCP layer or the SDAP layer of the transmitting end starts a discard timer.
  • the drop timer is pre-configured.
  • Step 232 The PDCP layer of the sending end sends a PDCP PDU to the RLC layer of the sending end.
  • the PDCP layer of the transmitting end processes the upper layer packet as the PDCP PDU and sends it to the RLC layer of the transmitting end.
  • Step 233 The RLC layer of the sending end sends an RLC PDU to the MAC layer of the sending end.
  • the RLC layer of the transmitting end processes the PDCP PDU received from the PDCP layer of the transmitting end as the RLC PDU and sends it to the MAC layer of the transmitting end.
  • Step 234 After the timer expires, the PDCP layer of the sending end instructs the RLC layer of the sending end to discard the RLC PDU for the PDCP PDU or the RLC SDU for the PDCP PDU.
  • the PDCP layer of the transmitting end if the PDCP layer of the transmitting end has sent the PDCP PDU to the RLC layer of the transmitting end, the PDCP layer of the transmitting end notifies the RLC layer of the sending end to discard the RLC SDU packet, regardless of whether the RLC layer of the transmitting end is The corresponding RLC PDU has been generated and the RLC PDU has been sent.
  • Step 235 The RLC layer of the sending end notifies the RLC SN corresponding to the discarded RLC PDU or the RLC SDU data packet to the RLC layer of the receiving end.
  • This step is optional and may not be performed.
  • the RLC layer of the transmitting end if the RLC layer of the transmitting end already has an RLC PDU SN number for the PDCP or has sent an RLC PDU corresponding to the PDCP, the RLC layer of the transmitting end notifies the RLC of the receiving end.
  • the discarding information of the RLC SN that is discarded by the layer, and the RLC layer of the receiving end performs the receiving window movement of the RLC layer of the transmitting end according to the discarding information. If the RLC layer of the receiving end finds that a packet corresponding to the RLC SN has received a part of the segment, the received segment is deleted. .
  • the PDCP layer of the transmitting end may also notify the PDCP layer of the receiving end of the PDCP SN corresponding to the discarded RLC PDU or the RLC SDU data packet.
  • the RLC layer of the transmitting end may also notify the RLC layer of the receiving end of the discarded RLC PDU SN.
  • the RLC layer of the receiving end updates the VR (R).
  • the RLC layer of the receiving end sends the updated VR (R) to the RLC layer of the sending end.
  • the sender moves the upper boundary of the transmission window to the value of the sequence number VR(R) in the window movement indication.
  • the RLC layer of the sending end notifies the RLC SN of the RLC layer of the receiving end that the RLC SN corresponding to the RLC layer of the receiving end is greater than the VR (R) saved by the RLC layer of the receiving end, and between the RLC SN and the VR (R) The packets have all been received, and the RLC layer of the receiving end updates VR(R) to the sequence number of the first unreceived packet after the RLC SN.
  • the RLC layer of the receiving end does not need to send an updated VR(R) to the RLC layer of the transmitting end.
  • the RLC layer of the receiving end determines that a data packet corresponding to the RLC SN that is not transmitted by the RLC layer of the transmitting end has been received, and optionally, the sending end indicates the The PDCP entity at the receiving end and the PDCP SN corresponding to the RLC SN have received the data packet.
  • Step 236 The RLC layer of the receiving end notifies the PDCP SN of the PDCP layer of the receiving end.
  • This step is optional and may not be performed.
  • Step 237 The RLC layer of the receiving end sends a discard determination indication to the RLC layer of the sending end.
  • This step is optional and may not be performed.
  • the PDCP layer of the CU sends a discard timer to the RLC layer of the DU when the PDCP layer is sent to the RLC layer of the DU.
  • the RLC layer of the DU or the CU, will configure a drop timer to the RLC layer of the DU before transmitting the PDCP PDU, for example, by signaling configuration or network management.
  • the RLC layer of the DU starts the discarding timer.
  • the discarding timer expires, the RLC PDU or the RLC SDU corresponding to the PDCP PDU is discarded, and the receiving end is notified to discard.
  • different discard timers are set for different PDCP PDU data packets, and the discard timer of the important packets (for example, important I frames of video data) is long, and non-critical packets (for example, non-critical P of video data) Frame) has a small discard timer.
  • the important packet is associated with the non-critical packet.
  • the discard timer corresponding to the important packet associated with the packet is considered to be timed out as long as the discard timer corresponding to the data of the last non-critical packet of the same association is found.
  • the PDCP/CU at the transmitting end instructs the RLC layer to discard the RLC PDUs/SDUs corresponding to the plurality of PDCP PDUs.
  • FIG. 24 is a schematic flowchart diagram of another method for processing data transmission according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, the distributed base station includes an RRU and a BBU, and the gNB includes a CU and a DU, but for simplicity of description, the present
  • the embodiment is described by taking the gNB as an example.
  • One of the access network devices and the terminal device is a transmitting end, and the other party is a receiving end. For example, when the access network device is a transmitting end, the terminal device is receiving. And vice versa.
  • Step 241 The DU receives the discarding indication of discarding the first PDCP PDU sent by the CU.
  • Step 242 The DU discards the RLC PDU or the corresponding RLC SDU corresponding to the first PDCP PDU according to the discarding indication.
  • the DU discards the RLC SDU corresponding to the first PDCP PDU according to the discarding indication.
  • the processing, by the DU, that the first PDCP PDU has not been processed includes: the DU does not perform an RLC serial number numbering on the first PDCP PDU or does not generate the first PDCP RLC PDU corresponding to the PDU.
  • the DU if the DU has performed the RLC sequence number numbering on the first PDCP PDU or has generated the RLC PDU corresponding to the first PDCP PDU or has sent the first PDCP PDU, And the DU discards the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, and notifies the terminal device to discard the sequence number corresponding to the RLC PDU.
  • the discarding indication carries information that discards the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, where the DU is in the collection And discarding the first PDCP PDU when the first PDCP PDU starts the discarding timer and the discarding timer expires.
  • FIG. 25 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, the distributed base station includes an RRU and a BBU, and the gNB includes a CU and a DU, and the access network device and the terminal One of the devices is a transmitting end, and the other is a receiving end. For example, when the access network device is a transmitting end, the terminal device is a receiving end, and vice versa.
  • the data transmission processing device is the DU, and the data transmission processing device includes a receiver 251, a processor 252, and a transmitter 253. And a memory 254, wherein the receiver 251, the processor 252, the transmitter 253, and the memory 254 are in communication with each other via a bus.
  • the processor 252 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 254 is used to store code or instruction information, and may also store information of a device type.
  • the memory 254 can include ROM and RAM for providing instructions and data to the processor 252.
  • a portion of the memory 254 may also include a non-volatile random access memory.
  • the receiver 251 is configured to receive a discard indication of discarding the first PDCP PDU sent by the CU.
  • the processor 252 is configured to discard the RLC PDU or the corresponding RLC SDU corresponding to the first PDCP PDU according to the discarding indication.
  • the processor 252 if the processor 252 has not processed the first PDCP PDU, the processor 252 is configured to discard the corresponding location of the first PDCP PDU according to the discarding indication. Said RLC SDU. In another embodiment of the present invention, the processor 252 has not processed the first PDCP PDU, and the processor 252 does not perform the RLC serial number or the ungenerated instance of the first PDCP PDU. The RLC PDU corresponding to the first PDCP PDU.
  • the processor 252 if the processor 252 has performed the RLC sequence number numbering on the first PDCP PDU or has generated the RLC PDU corresponding to the first PDCP PDU or has sent the first PDCP a PDU, the processor 252 is configured to discard the RLC PDU corresponding to the first PDCP PDU according to the discarding indication, and notify the terminal device to discard a sequence number corresponding to the RLC PDU.
  • the discarding indication carries information for discarding the first PDCP PDU; or the discarding indication is a discarding timer of the first PDCP PDU, and the receiver 251 further uses When the first PDCP PDU is received, the processor 252 is configured to start the drop timer and discard the first PDCP PDU when the discard timer expires.
  • FIG. 26 is a schematic flowchart diagram of another data transmission processing method according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, the distributed base station includes an RRU and a BBU, and the gNB includes a CU and a DU, and the access network device and the terminal One of the devices is a transmitting end, and the other is a receiving end. For example, when the access network device is a transmitting end, the terminal device is a receiving end, and vice versa.
  • Step 261 Before the first timer expires, the receiving end determines that the sequence number of the received RLC PDU exists between the value of the VR(X) at the start of the first timer and the value of the current VR(H). Continuously, a third timer is started, where the third timer is used by the receiving end to determine whether the RLC PDU corresponding to the missing serial number between the value of the VR (X) at the start of the first timer and the current VR (H) value is Lost.
  • the receiving end also starts a t-Reordering timer or a reassembly segmentation timer, that is, a third timer, for example, the receiving end is in the The three timer determines whether the RLC PDU with the sequence number M is lost.
  • the RLC PDU of M may be a fragmented or complete RLC PDU.
  • the duration of the first timer is equal to the duration of the third timer, or the duration of the first timer is not equal to the duration of the third timer.
  • the third timer is a first timer, and the terminal device has multiple first timers running at the same time, respectively managing or waiting for different ranges of RLC PDUs.
  • Step 262 when the first timer expires and the third timer is running, setting the value of VR1(R) to be the RLC PDU sequence number greater than or equal to the VR(X) set when the third timer is started.
  • the value of the VR1(X) is the highest RLC that has been received when the first timer expires.
  • the value of the VR1(X) is set to the highest RLC received by the first timer when the first timer expires.
  • the sequence number corresponding to the PDU is incremented by 1.
  • Step 2621 the receiving end sends a status report to the sending end, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer expires.
  • Step 263 when the first timer expires and the third timer is not running, setting the value of VR1(R) is the RLC PDU sequence number is greater than or equal to the VR(X) set when the first timer is started.
  • the value of the VR1(X) is the highest RLC that has been received when the first timer expires.
  • the value of the VR1(X) is set to the highest RLC received by the first timer when the first timer expires.
  • the sequence number corresponding to the PDU is incremented by 1.
  • Step 2631 the receiving end sends a status report to the sending end, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer expires.
  • step 262 and the step 263 are parallel steps.
  • the embodiment of the present invention can separately manage the waiting time for the packets lost at different times, and trigger the status report in time to obtain timely retransmission.
  • FIG. 27 is a schematic structural diagram of another data transmission processing apparatus according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a distributed base station of 2G/3G/4G or a gNB in a 5G communication system, the distributed base station includes an RRU and a BBU, and the gNB includes a CU and a DU, and the access network device and the terminal One of the devices is a transmitting end, and the other is a receiving end. For example, when the access network device is a transmitting end, the terminal device is a receiving end, and vice versa.
  • the data transmission processing device is the DU, and the data transmission processing device includes a receiver 271, a processor 272, and a transmitter 273. And a memory 274, wherein the receiver 271, the processor 272, the transmitter 273, and the memory 274 are in communication with each other via a bus.
  • the processor 272 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 274 is used to store code or instruction information, and may also store information of a device type.
  • the memory 274 can include ROM and RAM for providing instructions and data to the processor 272.
  • a portion of the memory 274 may also include a non-volatile random access memory.
  • the processor 272 is configured to determine, before the first timer expires, a value of the VR(X) of the sequence number of the RLC PDU received by the receiver 271 at the start of the first timer to the current VR ( There is a discontinuity between the values of H), and a third timer is started, and the third timer is used by the receiving end to determine that the value of VR(X) when the first timer is started is missing from the value of the current VR(H) Whether the RLC PDU corresponding to the serial number is lost.
  • the 272 determines, at the third timer, whether the RLC PDU of sequence number M is lost. It should be understood that the RLC PDU of M may be a fragmented or complete RLC PDU.
  • the duration of the first timer is equal to the duration of the third timer, or the duration of the first timer is not equal to the duration of the third timer. It should be understood that an embodiment,
  • the third timer is the first timer, and the terminal device has multiple first timers running at the same time, respectively managing or waiting for different ranges of RLC PDUs.
  • the processor 272 is further configured to: when the first timer expires and the third timer is running, set the value of VR1(R) to be set when the RLC PDU sequence number is greater than or equal to the third timer is started.
  • the first one of all the RLC PDUs corresponding to the RLC PDU sequence number corresponding to the value of the VR(X) does not receive the sequence number of the RLC PDU, and the value of the VR1(X) is set to be the time when the first timer expires.
  • the sequence number corresponding to the highest RLC PDU received is incremented by 1.
  • the sender 273 is configured to send a status report to the sending end, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer expires.
  • the processor 272 is further configured to: when the first timer expires and the third timer is not running, set the value of VR1(R) to be set when the RLC PDU sequence number is greater than or equal to the first timer is started.
  • the first one of all the RLC PDUs corresponding to the RLC PDU sequence number corresponding to the value of the VR(X) does not receive the sequence number of the RLC PDU, and the value of the VR1(X) is set to be the time when the first timer expires.
  • the sequence number corresponding to the highest RLC PDU received is incremented by 1.
  • the sender 273 is configured to send a status report to the sending end, where the status report includes status information that the receiving end receives all RLC PDUs when the first timer expires.
  • the embodiment of the present invention can separately manage the waiting time for the packets lost at different times, and trigger the status report in time to obtain timely retransmission.
  • protocol data units using the UM transport mode protocol layer may not have sub-headers of the protocol layer without fragmentation.
  • the header of the next protocol layer of the protocol layer needs to include an indication of whether the protocol data unit of the protocol layer includes a header.
  • the protocol layer is RLC
  • the next protocol layer is a MAC
  • the foregoing indication may indicate that the RLC is indicated by a reserved bit in the MAC sub-head corresponding to the RLC PDU. Whether the PDU contains an RLC header.
  • the indication that the header of the next protocol layer protocol data unit includes "whether the protocol data unit of the previous protocol layer has a subheader" is also applicable to whether the SDCP PDU header is indicated by the PDCP PDU header in the 3GPP NR radio access technology.
  • the method of the present invention saves the overhead and reduces the processing delay, and solves the problem that the RLC processing at the receiving end has no RLC header.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.
  • sequence numbers of the above processes do not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the embodiments of the present application.
  • the process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • This feature if implemented as a software functional unit and sold or used as a standalone product, can be stored on a computer readable storage medium.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method in accordance with various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Abstract

本发明的多个方面公开一种数据传输的处理方法、装置和终端设备，接入网设备生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；所述接入网设备将所述终端设备的配置信息发送给所述终端设备。通过本发明的数据传输的处理方法、装置和终端设备，可以在保障业务传输质量的同时提高可靠性。

Description

一种数据传输的处理方法和装置
本申请要求于2017年5月5日提交中国专利局、申请号为201710314177.2、发明名称为“一种数据传输的处理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术，尤其涉及一种数据传输的处理方法和装置。
背景技术
目前通信存在各种制式，例如第二代(2G)、第三代(3G)、第四代(4G)通信系统和新无线接入网络，例如全球移动通信(Global System of Mobile communication，GSM)系统，码分多址(Code Division Multiple Access，CDMA)系统，时分多址(Time Division Multiple Access，TDMA)系统，宽带码分多址(Wideband Code Division Multiple Access，WCDMA)，频分多址(Frequency Division Multiple Addressing，FDMA)系统，正交频分多址(Orthogonal Frequency-Division Multiple Access，OFDMA)系统，单载波FDMA(SC-FDMA)系统，通用分组无线业务(General Packet Radio Service，GPRS)系统，长期演进(Long Term Evolution，LTE)系统，通用移动通信系统(Universal Mobile Telecommunications System，UMTS)以及其他此类通信系统。其中，新无线接入网络能够提供比LTE网络更高的传输速率，新无线接入网络也称为5G网络、下一代网络等。
如图1所示，为现有技术中一种UMTS通信系统的结构示意图，UMTS是采用WCDMA空中接口技术的第三代移动通信系统，采用与第二代移动通信系统类似的结构，通常也把UMTS系统称为WCDMA通信系统。
UMTS系统包括无线接入网络(Radio Access Network，RAN)和核心网络(Core Network，CN)。其中，无线接入网络用于处理所有与无线有关的功能，而CN处理UMTS系统内所有的话音呼叫和数据连接，并实现与外部网络的交换和路由功能。CN从逻辑上分为电路交换域(Circuit Switched Domain，CS)和分组交换域(Packet Switched Domain，PS)。
核心网(CN)包括移动交换中心(Mobile Switching Center，MSC)/访问位置寄存器(Visitor Location Register，VLR)，服务GPRS支持节(Serving GPRS(通用分组无线业务，General Packet Radio Service)Support Node，SGSN)，归属位置寄存器(Home Location Register，HLR)，网关移动业务交换中心(Gateway Mobile-services Switching Centre)和网关GPRS支持节点网(GGSN，Gateway GPRS Support Node，GMSC)等各种网元。通过GMSC或GGSN可以和外部网络连接(External Network)，例如，通过GMSC可以和公共陆地移动通信网(Public Land Mobile Network，PLMN)， 公共开关电话网络(Public Switched Telephone Network，PSTN)，综合业务数字网(Integrated Services Digital Network，ISDN)等连接，通过GGSN可以和因特网(INTERNET)连接。
用户设备(User Equipment，UE)与通用陆地无线接入网(Universal Terrestrial Radio Access Network，UTRAN)之间接口为Uu接口，Node B与无线网络控制器(Radio Network Controller，RNC)之间通过Iub接口相连。在UTRAN内部，无线网络控制器(RNC)之间通过Iur互联，Iur可以通过RNC之间的直接物理连接或通过传输网连接。UTRAN和CN之间的接口统称为Iu接口，包括Iu-CS接口和Iu-PS接口。
NodeB通过Iub接口和RNC互连，用于完成Uu接口物理层协议的处理，分配和控制与NodeB相连或相关的NodeB的无线资源,完成Iub接口和Uu接口之间的数据流的转换。
RNC用于控制UTRAN的无线资源，主要完成连接建立和断开、切换、宏分集合并、无线资源管理控制等功能。
为保持未来网络的竞争能力，3GPP提出了一种全新的演进网络架构以满足未来十年甚至更长时间内移动网络的应用需求，包括系统架构演进(SAE，system architecture evolution)和接入网的长期演进(LTE，LongTermEvolution)，其中演进的接入网称为演进通用陆地无线接入网(E-UTRAN，Evolved Universal Terrestrial Radio Access Network)。网络演进的目标是希望提供一种低时延、高数据速率、高系统容量和覆盖、低成本、完全基于IP的网络。
如图2所示，为现有技术演进的分组核心网络架构示意图，所述演进的分组核心网络可以包括移动性管理实体(Mobility Management Entity，MME)、服务SAE网关(Serving SAE GW)以及数据封包网路闸道器(PDN(Packet Data Network)SAE GW)三个逻辑功能实体。
其中，MME负责控制面的移动性管理，包括用户上下文和移动状态管理，分配用户临时身份标识等，对应于当前GPRS/UMTS系统内部服务GPRS支持节SGSN的控制平面部分。
Serving SAE GW负责空闲状态下为下行数据发起寻呼，管理保存IP承载参数和网络内路由信息等，对应于当前GPRS/UMTS系统内部SGSN和网关GPRS支持节点网(GGSN，Gateway GPRS Support Node)的数据平面部分。
PDN SAE GW则充当不同接入系统间的用户面锚点。
策略和计费规则功能实体(Policy and Charging Rule Function，PCRF)用于策略控制决定和流计费控制功能。
归属网络服务器(Home Subscriber Server，HSS)用于存储用户签约信息。
随着接收端需求和技术的飞速发展，第五代移动通信(the 5th Generation mobile communication technology，5G)系统或者新无线接入技术(New radio，NR)即将到来，5G系统或NR系统能够提供比长期演进(Long Term Evolution，LTE)网络更快的传输 速率，其最高理论传输速率可达每秒数十吉字节(Gigabyte，简称Gb)。
所述新通信系统为5G或下一代通信系统，包括下一代核心网(NG Core)和基站(gNB)，其中，所述gNB一般包括无线资源控制(Radio Resource Control，RRC)层、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制(Radio Link Control，RLC)层、媒体介入控制(Media Access Control，MAC)层和物理层(Physical Layer，PHY)。
所述gNB也可以采用采用集中式单元(Centralized Unit，CU)和分布式单元(Distributed Unit，DU)架构，所述CU和DU通过有线或无线通信，所述DU与接收端通过空口通信，接收端在同一个或不同的DU下的不同小区进行移动。
如果所述gNB采用CU-DU架构，CU和DU功能的划分存在多种可能，其中一种功能划分方式可以如图3所示，为现有技术中采用CU-DU架构的gNB的结构示意图，CU包括RRC层和PDCP层，DU包括RLC层、MAC层和PHY层。
CU设备一般负责集中式无线资源和连接管理控制，DU设备一般包含实现分布式用户面处理功能，主要处理物理层功能和实时性需求较高的层2(Layer 2)功能。
CU设备处理无线高层协议栈功能，例如RRC层，PDCP层等，甚至也能够支持部分核心网功能下沉至接入网，称作边缘计算网络，能够满足未来通信网络对于新兴业务例如视频，网购，虚拟/增强现实对于网络时延的更高要求。
CU涵盖无线接入网高层协议栈以及核心网的一部分功能，而DU涵盖了基带处理的物理层以及层2部分功能，CU可以集中式的布放，DU布放取决实际网络环境，核心城区，话务密度较高，站间距较小，机房资源受限的区域，例如高校，大型演出场馆等，DU也可以集中式布放，而话务较稀疏，站间距较大等区域，例如郊县，山区等区域，DU可以采取分布式的布放方式。
不同业务对服务质量(Quality of Service，QoS)要求不同，例如QoS等级标识(QoS Class Identifier，QCI)为1～4表示用于需要保证带宽的业务，这部分QCI被用于保证带宽保证速率(Guaranteed bit rate，GBR)的业务，这种业务一般是需持续相等带宽传送的业务，如视频或者音频类业务。QCI为5～9用于不需要进行带宽保障的业务，虽然不需要保证带宽，但这部分业务对时延要求可能非常高，如QCI为5的IMS信令消息，IMS信令消息用于VoLTE语音通话的控制(例如，建立、释放、保持等)，对时延非常敏感。
以H.264视频编码为例，视频传输包括画面组(Group of Pictures，GOP)，一个GOP就是一组连续的画面，也就是一个序列。一个序列是一段图像编码后的数据流。在H264协议里定义了三种帧，完整编码的帧叫I帧(帧内编码帧，表示关键帧)；参考之前的I帧生成的只包含差异部分编码的帧叫P帧，P帧表示的是本帧跟之前的一个关键帧(或P帧)的差别，解码时需要用之前缓存的画面叠加上本帧定义的差别，生成最终画面；还有一种参考前后的帧编码的帧叫B帧，B帧是双向差别帧，也就是B帧记录的是本帧与前后帧的差别。
一般来说，可靠传输的业务承载在RLC确定模式(RLC Acknowledged Mode，RLC AM)的AM RLC实体中，比如缓存视频下载。对于实时性要求高的业务承载在RLC非确定模式(RLC Unacknowledged Mode，RLC UM)模式的UM RLC实体中，比如实时视频或语音。
但是，当实时视频采用RLC UM模式时，如果传输层的实时流媒体协议(Real-Time Stream Protocol，RSTP)层、实时传输协议(Real-time Transport Protocol。RTP)层或用户数据报协议(User Datagram Protocol，UDP)层的数据包在空口发送失败，应用层重传过晚会导致QoS体验差。当缓存视频采用RLC AM模式，当某P帧或其中的分段重传最大次数后导致RLC重建，即使收到I帧也无不能用，当I帧或其中分段重传最大次数后导致无线链路失败，只能进行重建，导致中断时延长。
因为，现有技术的数据传输不可靠或者时延太长影响用户的体验。
发明内容
本发明的多个方面，提供一种数据传输的处理方法、装置和终端设备，在保障业务传输质量的同时提高可靠性。
本发明的第一方面提供一种数据传输的处理方法，包括：接入网设备生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；所述接入网设备将所述终端设备的配置信息发送给所述终端设备。
可选的，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
可选的，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器，每个定时器用于其对应的RLC实体检测所述接入网设备发送的RLC PDU是否丢失。
可选的，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器，每个所述定时器用于其对应的RLC实体等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。
本发明的第二方面提供一种数据传输的处理装置，包括：处理器，用于生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；发送器，用于将所述终端设备的配置信息发送给所述终端设备。
可选的，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
可选的，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器，每个定时器用于其对应的RLC实体检测所述接入网设备发送的RLC PDU是否丢失。
可选的，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器，每个所述定时器用于其对应的RLC 实体等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。
本发明的第三方面提供一种数据传输的处理方法，包括：终端设备接收接入网设备发送的配置信息，其中，所述配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；所述终端设备根据数据流的类型或数据流的QoS需求选择用不同的RLC实体进行数据传输。
可选的，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
可选的，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器，每个定时器用于其对应的RLC实体检测所述接入网设备发送的RLC PDU是否丢失。
可选的，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器，每个所述定时器用于其对应的RLC实体等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。
本发明的第四方面提供一种终端设备，包括：接收器，用于接收所述接入网设备发送的配置信息，其中，所述配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；发送器，用于根据数据流的类型或数据流的QoS需求选择用不同的RLC实体进行数据传输。
可选的，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
可选的，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器，每个定时器用于其对应的RLC实体检测所述接入网设备发送的RLC PDU是否丢失。
可选的，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器，每个所述定时器用于其对应的RLC实体等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。
本发明的第五方面提供一种数据传输的处理方法，包括：接收端确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值，启动第一定时器，设置状态变量VR(X)的值，其中，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；所述第一定时器超时，发送状态报告，启动第二定时器，所述状态报告指示丢失的至少一个RLC PDU的序列号；所述第二定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。
可选的，在所述第一定时器超时时，启动第三定时器，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序 列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1；所述第三定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR1(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第三定时器超时时已收到的最高RLC PDU对应的序列号加1。
可选的，在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
本发明的第六方面提供一种数据传输的处理装置，包括：处理器，用于确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值，启动第一定时器，设置状态变量VR(X)的值，其中，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；发送器，用于在所述第一定时器超时，发送状态报告，所述状态报告指示丢失的至少一个RLC PDU的序列号；所述处理器还用于在所述第一定时器超时，启动第二定时器；所述处理器还用于所述第二定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。
可选的，所述处理器还用于在所述第一定时器超时时，启动第三定时器，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1；所述处理器还用于所述第三定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR1(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第三定时器超时时已收到的最高RLC PDU对应的序列号加1。
可选的，所述处理器还用于在所述第一定时器超时之前，确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
本发明的第七方面提供一种数据传输的处理方法，包括：接收端确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，向发送端发送状态报告，启动第一定时器，设置状态变量VR(X)的值，其中，所述状态报告包括启动所述第一定时器时所述接收端接收所有RLC PDU的状态信息，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表 示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；在所述第一定时器超时时，设置VR(R)的值为RLC PDU序列号大于或等于启动第一定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号，并设置所述第一定时器超时时的VR(X)的值为所述第一定时器超时时的VR(H)的值；或者，在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
可选的，在所述第一定时器超时且第三定时器在运行，设置VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号。
可选的，在所述第一或第三定时器超时时，向所述发送端发送状态报告，所述状态报告包括所述第一或第三定时器超时时所述接收端接收所有RLC PDU的状态信息。
本发明的第八方面提供一种数据传输的处理装置，包括：处理器，用于在确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，启动第一定时器，设置状态变量VR(X)的值，其中，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；发送器，用于在确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，向发送端发送状态报告，其中，所述状态报告包括启动所述第一定时器时所述接收端接收所有RLC PDU的状态信息；所述处理器还用于在所述第一定时器超时时，设置VR(R)的值为RLC PDU序列号大于或等于启动第一定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号，并设置所述第一定时器超时时的VR(X)的值为所述第一定时器超时时的VR(H)的值；或者，在所述第一定时器超时之前，所述处理器还用于确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
可选的，在所述第一定时器超时且第三定时器在运行，所述处理器还用于设置VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号。
可选的，所述发送器还用于在所述第一或第三定时器超时时，向所述发送端发送状态报告，所述状态报告包括所述第一或第三定时器超时时所述接收端接收所有RLC PDU的状态信息。
本发明的第九方面提供一种数据传输的处理方法，包括：发送端的RLC层接收 该发送端的PDCP层发送的丢弃第一PDCP PDU的丢弃指示；所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
可选的，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU包括：如果所述RLC层还未对所述第一PDCP PDU进行处理，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
可选的，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU包括：如果所述RLC层已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
可选的，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，用于所述RLC层在收到所述第一PDCP PDU启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
本发明的第十方面提供一种数据传输的处理装置，包括：接收器，用于接收该发送端的PDCP层发送的丢弃第一PDCP PDU的丢弃指示；处理器，用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
可选的，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU具体包括：所述处理器，用于如果还未对所述第一PDCP PDU进行处理，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
可选的，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU具体包括：所述处理器，用于如果已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
可选的，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，所述处理器，还用于在所述接收器收到所述第一PDCP PDU时，启动所述丢弃定时器并在所述丢弃定时器超时时丢弃所述第一PDCP PDU。
本发明的第十一方面提供一种数据传输的处理方法，基站包括CU和DU，包括：DU接收CU针对第一承载或第一逻辑信道(组)发送的丢弃定时器；DU接收所述第一承载或第一逻辑信道(组)的PDCP PDU时，启动所述丢弃定时器，在所述丢弃定时器超时时丢弃所述PDCP PDU。
可选的，所述在所述丢弃定时器超时时丢弃所述PDCP PDU包括：如果所述DU还未对所述PDCP PDU进行处理，所述DU在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC SDU。
可选的，所述在所述丢弃定时器超时时丢弃所述PDCP PDU包括：如果所述DU 已经对所述PDCP PDU进行RLC序列号编号或已经生成所述PDCP PDU对应的RLC PDU或已经发送所述PDCP PDU，所述DU在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
本发明的第十二方面提供一种数据传输的处理装置，包括：接收器，用于接收CU针对第一承载或第一逻辑信道(组)发送的丢弃定时器；处理器，用于所述接收器接收所述第一承载或第一逻辑信道(组)的PDCP PDU时，启动所述丢弃定时器，在所述丢弃定时器超时时丢弃所述PDCP PDU。
可选的，所述处理器用于在所述丢弃定时器超时时丢弃所述PDCP PDU具体包括：所述处理器用于如果还未对所述PDCP PDU进行处理，在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC SDU。
可选的，所述处理器用于在所述丢弃定时器超时时丢弃所述PDCP PDU具体包括：所述处理器用于如果已经对所述PDCP PDU进行RLC序列号编号或已经生成所述PDCP PDU对应的RLC PDU或已经发送所述PDCP PDU，在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC PDU；所述数据传输的处理装置还包括：发送器，
用于通知终端设备丢弃与所述RLC PDU对应的序列号。
本发明的第十三方面提供一种数据传输的处理方法，基站包括CU和DU，包括：DU接收CU发送的丢弃第一PDCP PDU的Qos参数信息；所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
可选的，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU包括：如果所述DU还未对所述第一PDCP PDU进行处理，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
可选的，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU包括：如果所述DU已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
可选的，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，用于所述DU在收到所述第一PDCP PDU启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
本发明的第十四方面提供一种数据传输的处理装置，包括：接收器，用于接收分布式单元CU发送的丢弃第一PDCP PDU的丢弃指示；处理器，用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
可选的，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU具体包括：所述处理器用于如果还未对所述第一PDCP PDU进行处理，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
可选的，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的 RLC PDU具体包括：所述处理器用于如果已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU；所述数据传输的处理装置还包括：发送器，用于通知终端设备丢弃与所述RLC PDU对应的序列号。
可选的，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，所述处理器用于在所述接收器收到所述第一PDCP PDU时启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
本发明的第十五方面提供一种数据传输的处理方法，基站包括CU和DU，包括：DU接收CU发送的第一承载或第一逻辑信道(组)的Qos参数信息，其中QoS参数参数信息至少包括以下之一：保证比特速率、调度优先级、缓存允许的时延、优先的比特速率PBR(Prioritized Bit Rate)；令牌桶的时长BSD(Bucket Size Duration)，所述DU根据所述Qos参数信息管理所述第一承载或第一逻辑信道(组)的数据传输。
可选的，所述DU根据所述缓存允许的时延丢弃所述第一PDCP PDU对应的RLC SDU包括：如果所述DU还未对所述第一PDCP PDU进行处理，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。比如，在PDCP或RLC层的发送最大时延。
可选的，所述DU根据所述保证比特速率或调度优先级进行所述承载的上行或下行数据包的调度发送。
上述各个方面描述的数据传输的处理方法、装置和终端设备，在保障业务传输质量的同时提高可靠性。
附图说明
图1为现有技术中一种UMTS通信系统的结构示意图；
图2为现有技术演进的分组核心网络架构示意图；
图3为现有技术中采用CU-DU架构的gNB的结构示意图；
图4为本发明一实施例的一种通信系统的示意图；
图5为本发明另一实施例的另一种通信系统的结构示意图；
图6为本发明另一实施例的另一种通信系统的结构示意图；
图7为本发明另一实施例的另一种数据传输的处理方法的流程示意图
图8为本发明另一实施例的另一种通信系统的结构示意图；
图9为本发明另一实施例的另一种视频数据的传输示意图；
图10为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图11为本发明另一实施例的另一种通信系统的结构示意图；
图12为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图13为本发明另一实施例的一种数据传输过程数据状态示意图；
图14为本发明另一实施例的一种数据传输过程数据状态示意图；
图15为本发明另一实施例的另一种数据传输处理装置的结构示意图；
图16为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图17为本发明另一实施例的一种数据传输过程数据状态示意图；
图18为本发明另一实施例的另一种数据传输处理装置的结构示意图；
图19为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图20为本发明另一实施例的另一种数据传输处理装置的结构示意图；
图21为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图22为本发明另一实施例的另一种数据传输处理装置的结构示意图；
图23为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图24为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图25为本发明另一实施例的另一种数据传输处理装置的结构示意图；
图26为本发明另一实施例的另一种数据传输的处理方法的流程示意图；
图27为本发明另一实施例的另一种数据传输处理装置的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本文所提及的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“一个”或者“一”等类似词语也不表示数量限制，而是表示存在至少一个。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。
在本文提及的“模块”通常是指存储在存储器中的能够实现某些功能的程序或指令；在本文中提及的“单元”通常是指按照逻辑划分的功能性结构，该“单元”可以由纯硬件实现，或者，软硬件的结合实现。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本文中描述的技术可用于各种通信系统，例如当前2G、3G、4G通信系统和新 无线接入网络，例如GSM系统、CDMA系统、TDMA系统、WCDMA系统、FDMA系统、OFDMA系统、SC-FDMA系统、GPRS系统、LTE系统、UMTS网络、新无线接入网络以及其他此类通信系统。其中，新无线接入网络能够提供比LTE网络更高的传输速率，新无线接入网络也称为5G网络、下一代网络等。
本文中结合接收端和/或基站和/或基站控制器来描述各种方面。
终端设备(Terminal Device)，可以是无线终端也可以是有线终端，无线终端可以是指向接收端提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(例如，RAN，Radio Access Network)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户设备(User Equipment)或用户代理(User Agent)。
基站(即，节点)可以是指接入网中在空中接口上通过一个或多个扇区与无线终端通信的设备。基站可用于将收到的空中帧与IP分组进行相互转换，作为无线终端与接入网的其余部分之间的路由器，其中接入网的其余部分可包括网际协议(IP)网络。基站还可协调对空中接口的属性管理。例如，基站可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB)，还可以是LTE系统中的演进型基站(eNodeB或eNB或e-NodeB)，也可以是新无线接入网络的接入网设备，本申请并不限定。所述新无线接入网络的接入网设备也称为基站(gNB)、NR Node(节点)或者NR BS(基站，Base Station)，在此不作限制，但为描述方便，本文中统一称为gNB。
基站控制器(即，控制节点)，可以是GSM系统或CDMA系统中的基站控制器(Base Station Controller，BSC)，也可以是WCDMA中的无线网络控制器(Radio Network Controller，RNC)，本申请并不限定。
如图4所示，为本发明一实施例的一种通信系统的示意图，所述通信系统包括接入网设备41和终端设备42，所述通信系统可以是2G、3G、4G通信系统或新无线接入网络，例如GSM系统、CDMA系统、TDMA系统、WCDMA系统、FDMA系统、OFDMA系统、SC-FDMA系统、GPRS系统、LTE系统、UMTS网络、新无线接入网络以及其他此类通信系统。其中，新无线接入网络能够提供比LTE网络更高的传输速率，新无线接入网络也称为5G网络、下一代网络等。因此，所述接入网设备41可以是2G、3G或4G通信系统的基站，也可以是5G通信系统的gNB。
所述接入网设备41包括三层结构：层一为物理层(PHY层)，层二为媒体接入控制层(MAC层)、无线链路控制层(RLC层)和分组数据会聚协议层(PDCP层)，层三为无线资源控制层(RRC层)，其中PHY层是无线接入系统最底层，它以传输信道为接口，向上层提供服务。所述接入网设备41的所述PHY层、MAC层、RLC层、PDCP层和RRC层针对每个承载均设置有接收实体和发送实体，分别用于数据的接收和发送，但为描述的方便，下述描述时，均以各层发送或接收进行描述。
所述接入网设备41从终端设备42接收的数据依次经过所述接入网设备41的PHY层、MAC层、RLC层、PDCP层和RRC层进行处理。例如，所述接入网设备41的PHY层接收终端设备42发送的数据(Data)后，在所述接入网设备41内，所述PHY层将所接收的数据处理为PHY服务数据单元(Service Data Unit，SDU)，所述PHY层将所述PHY SDU发送给所述MAC层；所述MAC层接收所述PYH SDU，然后将所述PYH SDU处理为MAC SDU，所述MAC层将所述MAC SDU发送给所述RLC层；所述RLC层接收所述MAC SDU，然后将所述MAC SDU处理为RLC SDU，所述RLC层将所述RLC SDU发送给所述PDCP层；所述PDCP层接收所述RLC SDU，然后将所述RLC SDU处理为信令PDCP SDU和数据PDCP SDU，所述PDCP层将所述信令PDCP SDU发送给所述RRC层进行控制层的处理，所述PDCP层将所述数据PDCP SDU发送给核心网。
所述接入网设备41发送的数据依次经过PDCP层、RLC层、MAC层和PHY层，然后发送给终端设备42。例如，在所述接入网设备41内，所述PDCP层将数据处理为PDCP协议数据单元(Protocol Data Unit，PDU)，然后将所述PDCP PDU发送给所述RLC层；所述RLC层接收所述PDCP PDU，然后将所述PDCP PDU处理为RLC PDU，所述RLC层将所述RLC PDU发送给所述MAC层；所述MAC层接收所述RLC PDU，然后将所述RLC PDU处理为MAC PDU，所述MAC层将所述MAC PDU发送给所述PHY层；所述PHY层接收所述MAC PDU，然后将所述MAC PDU处理为PHY PDU，所述PHY层将所述PHY PDU发送给终端设备42。
所述终端设备42包括PHY层、MAC层、RLC层和PDCP层，所述终端设备42包括的每个层针对每个承载均设置有接收实体和发送实体，分别用于数据的接收和发送，但为描述的方便，下述描述时，均以各层发送或接收进行描述。。
所述终端设备42从所述接入网设备41接收的数据依次经过所述终端设备42的PDCP层、RLC层、MAC层和PHY层进行处理。例如，所述终端设备42的PDCP层接收所述接入网设备41发送的PHY PDU后，在所述终端设备42内，所述PDCP层将所接收的PHY PDU处理为PDCP PDU，然后将所述PDCP PDU发送给所述RLC层；所述RLC层接收所述PDCP PDU，然后将所述PDCP PDU处理为RLC PDU，所述RLC层将所述RLC PDU发送给所述MAC层；所述MAC层接收所述RLC PDU，然后将所述RLC PDU处理为MAC PDU，所述MAC层将所述MAC PDU发送给所述PHY层；所述PHY层接收所述MAC PDU，然后将所述MAC PDU处理为PHY PDU，所述PHY层将所述PHY PDU发送给终端设备42内的处理器进行处理。
所述终端设备42向所述接入网设备41发送数据之前数据依次经过所述终端设 备42的PHY层、MAC层、RLC层和PDCP层进行处理。在所述终端设备42内，所述PHY层数据处理为PHY SDU，然后将所述PHY SDU发送给所述MAC层；所述MAC层接收所述PYH SDU，然后将所述PYH SDU处理为MAC SDU，所述MAC层将所述MAC SDU发送给所述RLC层；所述RLC层接收所述MAC SDU，然后将所述MAC SDU处理为RLC SDU，所述RLC层将所述RLC SDU发送给所述PDCP层；所述PDCP层接收所述RLC SDU，然后将所述RLC SDU处理为PDCP SDU，所述PDCP层将所述PDCP SDU发送给所述接入网设备41。
图5为本发明另一实施例的一种通信系统的结构示意图，所述通信系统为5G或下一代通信系统，包括接入网设备51、终端设备52和下一代核心网(NG Core)53。例如，所述接入网设备51为5G的gNB，所述接入网设备51包括集中式单元(CU)511和分布式单元(DU)512，所述CU511和DU512通过有线或无线通信，所述DU512与所述终端设备52通过空口通信。其中，RRC层和PDCP层功能位于所述CU511上，RLC层、MAC层和PHY层功能位于所述DU512上。
图6为本发明另一实施例的一种通信系统的结构示意图，所述通信系统为3G或4G通信系统，包括接入网设备61、终端设备62和核心网(Core Network，CN)53。例如，所述接入网设备61为3G或4G通信系统的分布式基站，所述接入网设备61可以包括：射频拉远单元(Radio Remote Unit，RRU)611和基带处理单元(Building Baseband Unit，BBU)612。所述RRU611和所述BBU612通过有线或无线通信，所述RRU611与所述终端设备62通过空口通信。其中，RRC层和PDCP层功能位于所述BBU611上，RLC层、MAC层和PHY层功能位于所述RRU612上。
图5和图6实施例中，接入网设备和终端设备的各层数据传输的过程，可以参考图4实施例描述的内容，在此不再赘述。
如图7所示，为本发明一实施例的一种数据传输的处理方法的流程示意图，本实施例的数据传输的处理方法由接入网设备执行，所述接入网设备可以为2G、3G、4G或5G通信系统的基站，主要过程如下所述。
步骤71，接入网设备生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体。
步骤72，所述接入网设备将所述终端设备的配置信息发送给所述终端设备。
例如，所述接入网设备配置所述终端设备的一个PDCP实体对应至少两种不同的RLC实体，例如，一个无线承载(Radio Bearer，RB)或逻辑信道(Logical Channel，LCH)对应一个RLC实体。所述终端设备的PDCP实体根据数据流的类型或数据流的服务质量(Quality of Service，QoS)需求选择用不同的RLC实体进行数据传输。
在本发明的另一实施例中，如果一个PDCP实体采用至少两个逻辑信道，UM RLC或AM RLC实体的不同LCH具有不同的优先级，终端设备上行缓存状态报告(Buffer Status Report，BSR)优先上报AM RLC实体的待发送数据量或根据LCH优先级由高向低上报LCH的待发送数据量。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器(可以称为t-Reordering定时器或重组分段定时器)，每个t-Reordering定时器或重组分段定时器用于所述终端设备的采用RLC AM或RLC UM的RLC实体接收端检测所述接入网设备发送的RLC PDU是否丢失。例如，所述终端设备PDCP实体对应的其中一个RLC实体发现未成功接收到所述接入网设备发送的RLC PDU，该RLC实体启动其配置的t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器超时，触发所述终端设备向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号(Sequence Number，SN)和/或包括成功接收的所述接入网设备发送的RLC PDU的序列号。例如，采用RLC AM的RLC实体接收端确定在该t-Reordering定时器或重组分段定时器超时时是否有收到该未接收到的RLC PDU，在该t-Reordering定时器或重组分段定时器超时，如果所述RLC实体没有收到该未成功接收到的RLC PDU，所述终端设备确定所述接入网设备发送的RLC PDU丢失，然后向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。应理解，对于采用RLC AM或RLC UM的RLC实体所使用的所述定时器还可以是用于等待组装分段RLC PDU的定时器，对于UM RLC的PDU不会触发状态报告。在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器(可以称为继续等待定时器)，每个所述继续等待定时器用于其对应的RLC实体继续等待接收其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。例如，配置继续等待定时器的RLC实体在t-Reordering定时器或重组分段定时器超时时或根据所述接入网设备发送的状态报告发送请求，所述终端设备向所述接入网设备发送状态报告，启动其配置的继续等待定时器，在该继续等待定时器的时长内继续接收所述未收到的RLC PDU，确定未收到的RLC PDU是否能在该继续等待定时器超时之前收到，其中，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时或接收所述状态报告发送请求时接收所有数据包的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。可选的，如果该继续等待定时器超时时，所述配置继续等待定时器的RLC实体还是没有收到该未收到的RLC PDU，所述终端设备确定所述接入网设备发送的RLC PDU丢失，向所述接入网设备发送最新的状态报告，所述最新的状态报告包括该继续等待定时器超时时所述接收端接收所有RLC PDU的状态信息。
在本发明的另一实施例中，所述终端设备在继续等待定时器超时时，进行接收窗口的推窗，不再等待上次触发t-Reordering定时器或重组分段定时器的RLC PDU的未收到且在续等待定时器内仍没有收到的一个或多个RLC PDU，以便接收所述接入网设备下次发送的RLC PDU，所述终端设备通知所述接入网设备所述终端设备已推窗，具体推窗的描述，请参靠后续推窗实施例的描述。
在本发明的另一实施例中，所述接入网设备给所述终端设备的至少一个AM  RLC实体配置第一最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后收到所述接入网设备发送的NACK后重传RLC PDU，如果重传达到所述第一最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备不通知所述接入网设备触发RLC重建，即不作为无线链路失败(Radio Link Failure，RLF)判断的依据。
在本发明的另一实施例中，所述接入网设备给所述终端设备的至少一个AM RLC实体配置第二最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后收到所述接入网设备发送的NACK后重传RLC PDU，如果重传达到所述第二最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备通知所述接入网设备触发RLC重建。可选的，第二最大重传次数大于或等于第一重传次数。
在本发明的另一实施例中，在本发明的另一实施例中，如果一个PDCP实体采用至少两个AM RLC实体，至少一个RLC实体支持重传达到所述第一最大重传次数不触发RLC重建。上述实施例中，由于所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体，所述终端设备的PDCP实体可以根据数据流的类型或服务质量(Quality of Service，QoS)需求选择用不同的RLC实体进行数据传输，保证不同业务的正常传输,在保障业务体验的同时提高可靠性。
如图8所示，为本发明一实施例的一种通信系统的结构示意图，所述通信系统包括接入网设备81与终端设备82，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述接入网设备包括：接收器811、处理器812、发送器813和存储器814，其中，所述接收器811、处理器812、发送器813和存储器814相互之间通过总线通信。
在本申请实施例中，该处理器812可以是可擦除可编辑逻辑器件(Erasable Programmable Logic Device，EPLD)、现场可编程门阵列(Field Programmable Gate Array，FPGA)、数字信号处理器(Digital Signal Processor，DSP)芯片、专用集成电路(Application Specific Integrated Circuit，ASIC)、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器814用于存储代码或指令信息，还可以存储设备类型的信息。该存储器814可以包括只读存储器(Read-Only Memory，ROM)和随机存取存储器(Random Access Memory，RAM)，用于向所述处理器812提供指令和数据。所述存储器814的一部分还可以包括非易失性随机存取存储器。
所述接收器811用于接收终端设备或核心网发送的数据。
所述处理器812用于生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体。
所述发送器813用于将所述终端设备的配置信息发送给所述终端设备。
例如，所述处理器812配置所述终端设备的一个PDCP实体对应至少两种不同的RLC实体，例如，一个RB或LCH对应一个RLC实体。所述终端设备的PDCP实体 根据数据流的类型或数据流的服务质量QoS需求选择用不同的RLC实体进行数据传输。
在本发明的另一实施例中，如果一个PDCP实体采用至少两个逻辑信道，UM RLC或AM RLC实体的不同LCH具有不同的优先级，终端设备上行BSR优先向所述接收器811上报AM RLC实体的待发送数据量或根据LCH优先级由高向低向所述接收器811上报LCH的待发送数据量。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器(可以称为t-Reordering定时器或重组分段定时器)，每个t-Reordering定时器或重组分段定时器用于所述终端设备的采用RLC AM或RLC UM的RLC实体接收端检测所述接入网设备发送的RLC PDU是否丢失。例如，所述终端设备PDCP实体对应的其中一个RLC实体发现未成功接收到所述接入网设备发送的RLC PDU，该RLC实体启动其配置的t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器超时，触发所述终端设备向所述接入网设备的所述接收器811发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括已经丢失的所述接入网设备的所述发送器813发送的RLC PDU的序列号和/或包括成功接收的所述接入网设备的所述发送器813发送的RLC PDU的序列号。例如，采用RLC AM或RLC UM的RLC实体接收端确定在该t-Reordering定时器或重组分段定时器超时时是否有收到该未接收到的RLC PDU，在该t-Reordering定时器或重组分段定时器超时时，如果所述RLC实体没有收到该未接收到的RLC PDU，所述终端设备确定所述接入网设备的所述发送器813发送的RLC PDU丢失，然后向所述接入网设备的所述接收器811发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述发送器813发送的RLC PDU的序列号。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器(可以称为继续等待定时器)，每个所述继续等待定时器用于其对应的RLC实体继续等待其发送的状态报告中指示的未收到的所述接入网设备的所述发送器813发送的RLC PDU。例如，配置继续等待定时器的RLC实体在t-Reordering定时器或重组分段定时器超时时或根据所述接入网设备的所述发送器813发送的状态报告发送请求向所述接入网设备的所述接收器811发送状态报告，启动其配置的继续等待定时器，在该继续等待定时器的时长内继续接收所述未收到的RLC PDU，确定未收到的RLC PDU是否能在该继续等待定时器超时之前收到，其中，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时或接收状态报告发送请求时接收所有数据包的状态信息，例如包括未收到的所述发送器813发送的RLC PDU的序列号。如果该继续等待定时器超时时，所述配置继续等待定时器的RLC实体还是没有收到该未收到的RLC PDU，所述终端设备确定所述发送器813发送的RLC PDU丢失，向所述接收器811发送最新的状态报告，所述最新的状态报告包括该继续等待定时器超时时所述接收端接收所有RLC PDU的状态信息。
在本发明的另一实施例中，所述终端设备在继续等待定时器超时时，进行接收 窗口的推窗，以便接收所述接入网设备下次发送的RLC PDU，所述终端设备通知所述接入网设备所述终端设备已推窗，具体推窗的描述，请参靠后续推窗实施例的描述。
在本发明的另一实施例中，所述处理器812给所述终端设备的AM RLC实体配置第一最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后收到所述接入网设备的所述发送器813发送的NACK后重传RLC PDU，如果重传达到所述第一最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备不通知所述接入网设备触发RLC重建，即不作为RLF判断的依据。
在本发明的另一实施例中，所述处理器812给所述终端设备的AM RLC实体配置第二最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后收到所述接入网设备的所述发送器813发送的NACK后重传RLC PDU，如果重传达到所述第二最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备通知所述接入网设备的所述处理器812触发RLC重建。
上述实施例中，由于所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体，所述终端设备的PDCP实体可以根据数据流的类型或QoS需求选择用不同的RLC实体进行数据传输，保证不同业务的正常传输,在保障业务体验的同时提高可靠性。
如图9所示，为本发明另一实施例的一种视频数据的传输示意图，本实施例中，所述视频数据流(Video packet)包括I帧和P帧，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
终端设备包括PHY层、MAC层、RLC层和PDCP层，例如，所述接入网设备配置所述终端设备的一个PDCP实体中，一个RB对应至少一个RLC实体或一个LCH对应至少一个RLC实体，例如第一PDCP实体的LCH1对应采用RLC AM的第一AM RLC实体，第一PDCP实体的LCH1或者LCH3对应采用RLC UM的第一UM RLC实体，第二PDCP实体的LCH2对应采用RLC UM的第二UM RLC实体。所述第一PDCP实体根据数据流的类型或QoS需求选择用不同的RLC实体进行数据传输。例如，所述第一PDCP实体可以基于应用层指示接入层的方式或接入层解析应用层数据包的特征获得该信息，例如，将I帧、重要的P帧或应用层RSTP等控制信令放在采用RLC AM的RLC实体发送，将普通的P帧放在采用RLC UM的第一UM RLC实体上发送，将语音业务(Voice service)放在第二PDCP实体对应的第二UM RLC实体上发送。
在本发明的另一实施例中，对于一个RB对应至少一个RLC实体的情况，在LTE系统，PDCP根据IP流的特征或QoS参数确定所述IP流和RB的对应关系，将IP数据包发送到对应的RB。在下一代系统中，由负责IP流和RB映射的SDAP根据IP流的特征或QoS参数将IP数据包发送到对应的RB。
在本发明的另一实施例中，LCH1、LCH2和LCH3具有不同的优先级，例如LCH1的优先级大于LCH2的优先级，所述LCH2的优先级和LCH3的优先级，终端设备上行BSR优先上报所述第一AM RLC实体的待发送数据量或根据LCH优先级由高向低上报LCH的待发送数据量。
在本发明的另一实施例中，所述第一AM RLC实体、所述第一UM RLC实体和所述第二UM分RLC实体分别配置不同时长的t-Reordering定时器或重组分段定时器，每个t-Reordering定时器或重组分段定时器用于对应的RLC实体接收端检测所述接入网设备发送的RLC PDU是否丢失。例如，所述第一AM RLC实体发现未接收到所述接入网设备发送的I帧RLC PDU，所述第一AM RLC实体启动其配置的t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器超时，触发所述终端设备向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括已经丢失的所述I帧RLC PDU的序列号和/或包括成功接收的所述I帧RLC PDU的序列号。例如，所述第一AM RLC实体接收端确定在该t-Reordering定时器或重组分段定时器超时时是否有收到该未接收到的所述I帧RLC PDU，如果所述第一AM RLC实体没有收到该未接收到的所述I帧RLC PDU，所述终端设备确定所述接入网设备发送的所述I帧RLC PDU丢失，然后向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的所述I帧RLC PDU的序列号。
在本发明的另一实施例中，所述PDCP实体对应至少两个均采用RLC AM的AM RLC实体，例如，其中一个AM RLC实体用于传输I帧RLC PDU，另一个AM RLC实体用于传输P帧RLC PDU，且所述至少两个AM RLC实体中的至少一个AM RLC实体配置继续等待定时器，每个所述继续等待定时器用于其对应的AM RLC实体继续等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。例如，配置继续等待定时器的AM RLC实体在t-Reordering定时器或重组分段定时器超时时或根据所述接入网设备发送的状态报告发送请求向所述接入网设备发送状态报告，启动其配置的继续等待定时器，在该继续等待定时器的时长内继续接收所述未收到的RLC PDU，确定未收到的RLC PDU是否能在该继续等待定时器超时之前收到，其中，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。如果该继续等待定时器超时时，所述终端设备的AM RLC实体还是没有收到该未收到的RLC PDU，所述终端设备确定所述接入网设备发送的RLC PDU丢失，可选的，向所述接入网设备发送最新的状态报告或移动窗口的指示信息，所述最新的状态报告包括该继续等待定时器超时时所述接收端接收所有RLC PDU的状态信息。移动窗口的指示信息用于指示不再接收所述丢失的RLC PDU或下个期望接收的RLC PDU包的序号。
在本发明的另一实施例中，所述终端设备在继续等待定时器超时时，进行接收窗口的推窗，以便接收所述接入网设备下次发送的RLC PDU，所述终端设备通知所述接入网设备所述终端设备已推窗，具体推窗的描述，请参靠后续推窗实施例的描述。
在本发明的另一实施例中，所述接入网设备给所述终端设备的所述第一AM RLC实体配置第一最大重传次数，所述第一AM RLC实体发送RLC PDU后收到所述接入网设备发送的NACK后重传RLC PDU，如果重传达到所述第一最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备不通知所述接 入网设备触发RLC重建，即不作为RLF判断的依据。可选的，所述终端设备向所述接入网设备发送最新的状态报告或移动窗口的指示信息，移动窗口的指示信息用于指示不再接收的一个活多个所述丢失的RLC PDU包的序号或下个期望接收的RLC PDU包的序号。
在本发明的另一实施例中，所述接入网设备给所述终端设备的所述第一AM RLC实体配置第二最大重传次数，所述第一AM RLC实体发送RLC PDU后收到所述接入网设备发送的NACK后重传RLC PDU，如果重传达到所述第二最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备通知所述接入网设备触发RLC重建。
如图10所示，为本发明一实施例的一种数据传输的处理方法的流程示意图，本实施例的数据传输的处理方法由终端设备执行，接入网设备可以为2G、3G、4G或5G通信系统的基站，主要过程如下所述。
步骤101，终端设备接收接入网设备发送的配置信息，其中，所述配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体。
步骤102，所述终端设备根据数据流的类型或数据流的QoS需求选择用不同的RLC实体进行数据传输。
例如，所述接入网设备配置所述终端设备的一个PDCP实体对应至少两种不同的RLC实体，例如，一个RB或LCH对应一个RLC实体。所述终端设备的PDCP实体根据数据流的类型或数据流的QoS需求选择用不同的RLC实体进行数据传输。
在本发明的另一实施例中，如果一个PDCP实体采用至少两个逻辑信道，UM RLC或AM RLC实体的不同LCH具有不同的优先级，终端设备发送上行BSR时优先上报AM RLC实体的待发送数据量或根据LCH优先级由高向低上报LCH的待发送数据量。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器(可以称为t-Reordering定时器或重组分段定时器)，每个t-Reordering定时器或重组分段定时器用于所述终端设备的采用RLC AM或RLC UM的RLC实体接收端检测所述接入网设备发送的RLC PDU是否丢失。例如，所述终端设备PDCP实体对应的其中一个RLC实体发现未接收到所述接入网设备发送的RLC PDU，该RLC实体启动其配置的t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器超时，触发所述终端设备向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括已经丢失的所述接入网设备发送的RLC PDU的序列号和/或包括成功接收的所述接入网设备发送的RLC PDU的序列号。例如，所述采用RLC AM或RLC UM的RLC实体接收端确定在该t-Reordering定时器或重组分段定时器超时时是否有收到该未接收到的RLC PDU，如果所述RLC实体没有收到该未接收到的RLC PDU，所述终端设备确定所述接入网设备发送的RLC PDU丢失，然后向所述接入网设备发送状态报告，所述状态报告包括该 t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器(可以称为继续等待定时器)，每个所述继续等待定时器用于其对应的RLC实体继续等待接收其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。例如，配置继续等待定时器的RLC实体在t-Reordering定时器或重组分段定时器超时时或根据所述接入网设备发送的状态报告发送请求，所述终端设备向所述接入网设备发送状态报告，启动其配置的继续等待定时器，在该继续等待定时器的时长内继续接收所述未收到的RLC PDU，确定未收到的RLC PDU是否能在该继续等待定时器超时之前收到，其中，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时或接收状态报告发送请求时接收所有数据包的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。如果该继续等待定时器超时时，所述配置继续等待定时器的RLC实体还是没有收到该未收到的RLC PDU，所述终端设备确定所述接入网设备发送的RLC PDU丢失，向所述接入网设备发送最新的状态报告。
在本发明的另一实施例中，所述终端设备在继续等待定时器超时时，进行接收窗口的推窗，以便接收所述接入网设备下次发送的RLC PDU，所述终端设备通知所述接入网设备所述终端设备已推窗，具体推窗的描述，请参靠后续推窗实施例的描述。
在本发明的另一实施例中，所述终端设备还接收所述接入网设备给所述终端设备的AM RLC实体配置的第一最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后收到所述接入网设备发送的NACK后重传RLC PDU，如果重传达到所述第一最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备不通知所述接入网设备触发RLC重建，即不作为RLF判断的依据。
在本发明的另一实施例中，所述终端设备还接收所述接入网设备给所述终端设备的AM RLC实体配置的第二最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后收到所述接入网设备发送的NACK后重传RLC PDU，如果重传达到所述第二最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述终端设备通知所述接入网设备触发RLC重建。
上述实施例中，由于所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体，所述终端设备的PDCP实体可以根据数据流的类型或QoS需求选择用不同的RLC实体进行数据传输，保证不同业务的正常传输,在保障业务体验的同时提高可靠性。
如图11所示，为本发明另一实施例的另一种通信系统的结构示意图，所述通信系统包括接入网设备111与终端设备112，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述终端设备112包括：接收器1121、处理器1122、发送器1123和存储器1124，其中，所述接收器1121、处理器1122、发送器1123和存储器1124相互之间通过总线通信。
在本申请实施例中，该处理器1122可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器1124用于存储代码或指令信息，还可以存储设备类型的信息。该存储器1124可以包括ROM和RAM，用于向所述处理器1122提供指令和数据。所述存储器1124的一部分还可以包括非易失性随机存取存储器。
所述接收器1121用于接收所述接入网设备111发送的配置信息，其中，所述配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体。
所述发送器1123用于根据数据流的类型或数据流的QoS需求选择用不同的RLC实体进行数据传输。
例如，所述接入网设备配置所述终端设备的一个PDCP实体对应至少两种不同的RLC实体，例如，一个RB或LCH对应一个RLC实体。所述终端设备的PDCP实体根据数据流的类型或数据流的QoS需求选择用不同的RLC实体进行数据传输。
在本发明的另一实施例中，如果一个PDCP实体采用至少两个逻辑信道，UM RLC或AM RLC实体的不同LCH具有不同的优先级，所述发送器1123用于发送上行BSR时优先上报AM RLC实体的待发送数据量或根据LCH优先级由高向低上报LCH的待发送数据量。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器(可以称为t-Reordering定时器或重组分段定时器)，每个t-Reordering定时器或重组分段定时器用于所述终端设备的采用RLC AM或RLC UM的RLC实体接收端检测所述接入网设备发送的RLC PDU是否丢失。例如，所述终端设备PDCP实体对应的其中一个RLC实体发现未接收到所述接入网设备发送的RLC PDU，该RLC实体启动其配置的t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器超时，触发所述发送器1123向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括已经丢失的所述接入网设备发送的RLC PDU的序列号和/或包括成功接收的所述接入网设备发送的RLC PDU的序列号。例如，所述采用RLC AM或RLC UM的RLC实体接收端确定在该t-Reordering定时器或重组分段定时器超时时是否有收到该未接收到的RLC PDU，如果所述RLC实体没有收到该未接收到的RLC PDU，所述处理器1122确定所述接入网设备发送的RLC PDU丢失，然后所述发送器1123向所述接入网设备发送状态报告，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。
在本发明的另一实施例中，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器(可以称为继续等待定时器)，每个所述继续等待定时器用于其对应的RLC实体继续等待接收其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。例如，配置继续等待定时器的RLC实体在t-Reordering定时器或重组分段定时器超时时或根据所述接入网设备发送 的状态报告发送请求，所述发送器1123向所述接入网设备发送状态报告，所述配置继续等待定时器的RLC实体启动其配置的继续等待定时器，在该继续等待定时器的时长内继续接收所述未收到的RLC PDU，确定未收到的RLC PDU是否能在该继续等待定时器超时之前收到，其中，所述状态报告包括该t-Reordering定时器或重组分段定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括未收到的所述接入网设备发送的RLC PDU的序列号。如果该继续等待定时器超时时，所述配置继续等待定时器的RLC实体还是没有收到该未收到的RLC PDU，所述处理器1122确定所述接入网设备发送的RLC PDU丢失，所述发送器1123向所述接入网设备发送最新的状态报告，所述最新的状态报告包括该继续等待定时器超时时所述接收端接收所有RLC PDU的状态信息。
在本发明的另一实施例中，所述处理器1122在继续等待定时器超时时，进行接收窗口的推窗，以便所述接收器1121接收所述接入网设备下次发送的RLC PDU，所述发送器1123通知所述接入网设备所述终端设备已推窗，具体推窗的描述，请参靠后续推窗实施例的描述。
在本发明的另一实施例中，所述接收器1121还用于接收所述接入网设备给所述终端设备的AM RLC实体配置的第一最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后，如果所述接收器1121收到所述接入网设备发送的NACK，所述发送器1123重传RLC PDU，如果重传达到所述第一最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述发送器1123不通知所述接入网设备触发RLC重建，即不作为RLF判断的依据。
在本发明的另一实施例中，所述接收器1121还用于接收所述接入网设备给所述终端设备的AM RLC实体配置的第二最大重传次数，所述终端设备的AM RLC实体发送RLC PDU后，如果所述接收器1121收到所述接入网设备发送的NACK，所述发送器1123重传RLC PDU，如果重传达到所述第二最大重传次数后依然没有成功发送所述RLC PDU，则丢弃所述重传RLC PDU，所述发送器1123通知所述接入网设备触发RLC重建。
上述实施例中，由于所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体，所述终端设备的PDCP实体可以根据数据流的类型或QoS需求选择用不同的RLC实体进行数据传输，保证不同业务的正常传输,在保障业务体验的同时提高可靠性。
如图12所示，为本发明另一实施例的另一种数据传输的处理方法的流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。所述接入网设备的RLC层与终端设备的RLC层采用RLC AM模式。
步骤121，接收端确定最高接收状态变量VR(H)的值大于接收状态变量VR(R) 的值，启动第一定时器，设置状态变量VR(X)的值。
所述接收端保存有几个变量，例如VR(R)，VR(H)和VR(X)，所述接收端每次接收所述发送端发送的一个RLC PDU时，都需要确定VR(R)，VR(H)和VR(X)的变量值和进行VR(H)和VR(R)相互之间的变量值大小判断，例如，所述接收端收到所述发送端发送的一个RLC PDU时，确定所述VR(H)的值是否大于所述VR(R)的值并启动所述第一定时器(可以称为t-Reordering定时器或重组分段定时器)，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1。
例如，在一个接收窗口内，所述接收端依次接收所述发送端发送第一RLC PDU、第二RLC PDU和第三RLC PDU，其中，所述第一RLC PDU的序列号为1，所述第二RLC PDU的序列号为2，所述第三RLC PDU的序列号为3，则当前接收窗口的下边界为期待接收所述第一RLC PDU的接收时间点。
如图13所示，为本发明另一实施例的一种数据传输过程数据状态示意图，即接收端接收RLC PDU时的VR(R)，VR(H)和VR(X)的变量值变化过程示意图。
所述接收端未接收所述发送端的RLC PDU之前，期望接收序列号为1的所述第一RLC PDU，当前没有接收到任何RLC PDU，即设置VR(R)，VR(H)和VR(X)的初始变量值为：初始VR(R)＝1，初始VR(H)＝1和初始VR(X)＝1。
所述接收端在接收所述第一RLC PDU时，需要确定VR(R)，VR(H)和VR(X)的变量值和进行VR(H)和VR(R)相互之间的变量值大小判断，如果所述接收端成功接收序列号为1所述第一RLC PDU，则所述接收端期望收到序列号为2的所述第二RLC PDU，即VR(R)＝2，VR(H)＝2，设置VR(X)＝2，所述接收端判断所述VR(H)等于所述VR(R)；如果所述接收端未成功接收所述第一RLC PDU，则所述接收端期望收到序列号为1的所述第一RLC PDU，即VR(R)＝1，VR(H)＝1，设置VR(X)＝1，所述接收端判断所述VR(H)等于所述VR(R)。
所述接收端在成功接收到所述第一RLC PDU之后，继续接收所述第二RLC PDU，如果所述接收端成功接收所述第二RLC PDU，则当前已成功接收到的最高RLC PDU为序列号为2的第二RLC PDU，期望收到的RLC PDU为序列号为3的第三RLC PDU，即VR(R)＝3，VR(H)＝3，设置VR(X)＝3，所述接收端判断所述VR(H)等于所述VR(R)；如果所述接收端未成功接收所述第二RLC PDU，则当前已成功接收到的最高RLC PDU为序列号为1的第一RLC PDU，期望收到的RLC PDU为序列号为2的第二RLC PDU，即VR(R)＝2，VR(H)＝2，设置VR(X)＝2，所述接收端判断所述VR(H)等于所述VR(R)。
所述接收端在未成功接收到所述第一RLC PDU之后，继续接收所述第二RLC PDU，如果所述接收端成功接收所述第二RLC PDU，当前已成功接收到的最高RLC PDU为序列号为2的第二RLC PDU，期望收到的RLC PDU为序列号为1的第一RLC PDU， 即VR(R)＝1，VR(H)＝3，设置VR(X)＝3，所述接收端判断所述VR(H)大于所述VR(R)；如果所述接收端未成功接收所述第二RLC PDU，当前未成功接收到任何RLC PDU，期望收到的RLC PDU为序列号为1的第一RLC PDU，即VR(R)＝1，VR(H)＝1，设置VR(X)＝1，所述接收端判断所述VR(H)等于所述VR(R)。
针对所述第三RLC PDU的接收后的VR(R)，VR(H)和VR(X)的变量值的确定和VR(H)和VR(R)相互之间的变量值大小的判断，类似于所述第二RLC PDU的接收后VR(R)，VR(H)和VR(X)的变量值的确定和VR(H)和VR(R)相互之间的变量值大小的判断，在此不再赘述。
所述接收端判断所述VR(H)大于所述VR(R)时，即所述接收端当前成功接收所述第二RLC PDU但没有成功接收所述第一RLC PDU，亦可以称为成功接收当前RLC PDU之前存在接收RLC PDU的空洞，针对所述没有成功接收的所述第一RLC PDU启动所述第一定时器(可以称为t-Reordering定时器或重组分段定时器)，启动所述第一定时器时，VR(R)＝1，VR(H)＝3，设置VR(X)＝3，所述第一定时器用于所述接收端在所述第一定时器的时长内继续接收所述第一RLC PDU，所述接收端在所述第一定时器超时时判断是否成功接收到所述第一RLC PDU。
在本发明的另一实施例中，在所述第一定时器的时长内，也即所述第一定时器超时之前，所述接收端还可以接收所述所述第二RLC PDU之后的RLC PDU，例如所述第三RLC PDU以及所述第三RLC PDU之后的RLC PDU。
步骤122，所述第一定时器超时，所述接收端发送状态报告，启动第二定时器，所述状态报告指示丢失的至少一个RLC PDU的序列号。
所述第一定时器超时，如果所述接收端成功接收到所述第一RLC PDU，则所述接收端在所述第一定时器超时时已成功接收到的最高RLC PDU为序列号为2的第二RLC PDU，期望收到的RLC PDU为序列号为3的第三RLC PDU，即VR(R)＝3，VR(H)＝3，设置VR(X)＝3，所述接收端判断所述VR(H)等于所述VR(R)，可选的，所述接收端向所述发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息，例如包括已经成功接收所述第一RLC PDU的序列号和成功接收所述第二RLC PDU的序列号。
所述第一定时器超时，如果所述接收端还是未成功接收到所述第一RLC PDU，所述接收端确定丢失所述第一RLC PDU，所述接收端发送状态报告，启动所述第二定时器(可以称为继续等待定时器)，所述状态报告指示丢失的所述第一RLC PDU的序列号。所述第二定时器用于所述接收端继续等待接收其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU，例如，所述接收端在该第二定时器的时长内继续接收所述未收到的第一RLC PDU，确定所述未收到的第一RLC PDU是否能在该第二定时器超时之前收到。
由于在所述第一定时器的时长内，所述接收端还可以接收所述所述第二RLC PDU之后的RLC PDU，例如所述第三RLC PDU以及所述第三RLC PDU之后的RLC PDU。
当所述第一定时器超时时，如果所述接收端接收所述第二RLC PDU之后的RLC PDU为连续接收，例如，所述接收端在所述第一定时器超时时已成功连续接收到最高序列号等于N的RLC PDU，所述N为大于或等于3的正整数，此时，所述接收端期待接收的RLC PDU还是序列号为1的所述第一RLC PDU，但所述接收端在所述第一定时器超时时已经成功接收的RLC PDU的最高序列号为N，则所述接收端设置VR(R)＝1，VR(H)＝N，VR(X)＝N，所述接收端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息。
当所述第一定时器超时时，如果所述接收端接收所述第二RLC PDU之后的RLC PDU为非连续接收，例如，所述接收端在所述第一定时器超时时接收最高序列号等于N的RLC PDU，所述N为大于或等于3的正整数，但在所述序列号为N之前存在有未接收到至少一个RLC PDU，假设已经成功接收的序列号为2的所述第二RLC PDU之后的第一个未成功接收的RLC PDU的序列号为M，所述M为大于或等于3的正整数，所述M小于或等于N；在所述第一定时器超时时，所述接收端期待接收的RLC PDU还是序列号为1的所述第一RLC PDU，如果所述M小于N，即序列号为N的RLC PDU成功接收，而序列号为M的RLC PDU所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述接收端在所述第一定时器超时时已经成功接收的RLC PDU的最高序列号为N，则所述接收端设置VR(R)＝1，VR(H)＝N+1，VR(X)＝N+1；如果所述M等于N，即序列号为N/M的RLC PDU为所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述接收端在所述第一定时器超时时已经成功接收的RLC PDU的最高序列号为N-1，则所述接收端设置VR(R)＝1，VR(H)＝(N-1)+1，VR(X)＝(N-1)+1。所述接收端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息
在本发明的另一实施例中，在所述第二定时器的时长内，也即所述第二定时器超时之前，所述接收端还可以接收所述第二RLC PDU之后的RLC PDU，例如所述第三RLC PDU以及所述第三RLC PDU之后的RLC PDU。
步骤123，所述第二定时器超时，所述接收端设置所述VR(R)的值为RLC PDU序列号大于或等于所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。
所述第二定时器超时时，如果所述接收端还是没有收到该未收到的第一RLC PDU，所述接收端确定所述发送端发送的第一RLC PDU丢失，可选的，向所述接入网设备发送最新的状态报告或移动窗口指示信息，则所述接收端将所述第二定时器超时时的接收窗口的下边界移到或设置下一个期待接收(也即未接收到)的发送端发送的RLC PDU的接收时间点，该过程称为接收窗口的下边界移动。
由于在所述第二定时器的时长内，也即所述第二定时器超时之前，所述接收端还可以接收所述第二RLC PDU之后的RLC PDU，当接收所述第二RLC PDU之后的RLC PDU存在不连续接收时，即又出现一个丢失的RLC PDU，所以当所述第二定时器超时时，所述接收端对接收窗口的下边界移动的VR(R)、VR(H)和VR(X)的变量值设置为：所 述接收端设置所述VR(R)的值为RLC PDU序列号大于或等于所述第一定时器启动时所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(H)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。也即所述接收端不再等待接收所述第一RLC PDU，而将接收窗口的下边界移到所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(即所述第二RLC PDU)之后的第一个未接收到的RLC PDU的接收序列号。所述接收端发送状态报告或窗口移动指示信息，所述状态报告包括所述第二定时器超时时所述接收端接收所有RLC PDU的状态信息，所述窗口移动指示信息包括终端最新期待接收的RLC PDU的序列号，即当前的VR(R)的序列号。
例如，当所述第二定时器超时时，如果所述接收端接收所述第二RLC PDU之后的RLC PDU为非连续接收，例如，所述接收端在所述第二定时器超时时接收最高序列号等于K的RLC PDU，所述K为大于或等于3的正整数，但在所述序列号为K之前存在有未接收到至少一个RLC PDU，例如，所述第一定时器启动时已经成功接收的具有最高序列号的RLC PDU为所述第二RLC PDU，假设所述第二RLC PDU之后的第一个未成功接收的RLC PDU的序列号为L，所述L为大于或等于3的正整数，所述L小于或等于K；在所述第二定时器超时时，所述接收端进行接收窗口的下边界移动，即将接收窗口的下边界移到所述第二RLC PDU之后的第一个未成功接收的RLC PDU的接收时间点。例如，如果所述L小于K，即序列号为K的RLC PDU为所述第二定时器超时时成功接收的最高序列号的RLC PDU，而序列号为L的RLC PDU为所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述接收端设置VR(R)＝L，VR(H)＝K+1，VR(X)＝K+1；如果所述L等于K，即序列号为L/K的RLC PDU为所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述接收端在所述第二定时器超时时已经成功接收的RLC PDU的最高序列号为L/K-1，则所述接收端设置VR(R)＝L/K，VR(H)＝(L/K-1)+1，VR(X)＝(L/K-1)+1。也即所述接收端不再等待接收所述第一RLC PDU，而将接收窗口的下边界从期待接收的所述第一RLC PDU的接收时间点移到到所述第一定时器启动时已经成功接收的序列号最高为2的第二RLC PDU之后的第一个未接收到的RLC PDU的接收时间点，即将VR(R)＝1修改为VR(R)＝L/K。所述接收端发送状态报告，所述状态报告包括所述第二定时器超时时所述接收端接收所有RLC PDU的状态信息
在本发明的另一实施例中，在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定第一定时器启动时的VR(X)的值到当前VR(H)的值之间缺失的序列号对应的RLC PDU是否丢失。
例如，针对所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(例如，所述第二RLC PDU)之后的第一个未接收到的RLC PDU(例如，所述序列号为M的RLC PDU，记为RLC PDU SN＝M)，所述接收端也同样启动一个t-Reordering定时器或重组分段定时器，即第三定时器，例如，所述接收端在所述第三定时器确定是否丢失 所述序列号为M的RLC PDU。应理解，M的RLC PDU可能为分段或完整的RLC PDU。在本发明的另一实施例中，所述第一定时器的时长等于所述第三定时器的时长，或者，所述第一定时器的时长不等于所述第三定时器的时长。应理解，一种实施方式，所述第三定时器就是第一定时器，终端设备同时存在多个第一定时器在运行，分别管理或等待不同的范围的RLC PDU。
例如，在所述第一定时器超时时，所述接收端启动所述第三定时器，针对所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(例如，所述第二RLC PDU)之后的第一个未接收到的RLC PDU(例如，所述序列号为M的RLC PDU)，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，例如VR1(R)＝M，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1，例如VR1(X)＝N+1。所述接收端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息。
在所述第三定时器超时时，可选的，发送状态报告，所述状态报告指示所述序列号为M的RLC PDU已丢失，启动一个继续等待定时器，即第四定时器，第四定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR1(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第三定时器超时时已收到的最高RLC PDU对应的序列号加1。所述接收端发送状态报告，所述状态报告包括所述第三定时器超时时所述接收端接收所有RLC PDU的状态信息。一种实施方式，当在所述第三定时器超时时，若接收窗口的接收的RLC PDU的状态没有更新或者已经收到状态报告中指示的未收到的RLC PDU，终端设备可不发送状态报告。
在本发明的另一实施例中，所述第四定时器用于所述接收端针对所述已经丢失序列号为M的RLC PDU继续在所述第四定时器的时长内等待接收，在所述第四定时器超时时确定是否有收到所述序列号为M的RLC PDU，如果没有收到，确定所述序列号为M的RLC PDU丢失，并进行接收窗口的下边界移动，例如，将所述VR1(R)设置为RLC PDU序列号大于或等于启动第三定时器时已经成功接收的序列号最高的RLC PDU之后的第一个未接收到的RLC PDU的序列号，设置VR1(X)的值为所述第四定时器超时时已收到的最高RLC PDU对应的序列号加1，设置VR1(H)的值为所述第四定时器超时时已收到的最高RLC PDU对应的序列号加1。所述接收端发送状态报告，所述状态报告包括所述第四定时器超时时所述接收端接收所有RLC PDU的状态信息。
上述实施例中，对于启动t-Reordering定时器或重组分段定时器的未成功接收的RLC PDU，在该t-Reordering定时器或重组分段定时器超时之前，一旦所述接收端成功接收该未成功接收的RLC PDU，所述接收端停止该t-Reordering定时器或重组分段定时器。类似的，对于启动继续等待定时器的未成功接收的RLC PDU，在该继续等待定时器超时之前，一旦所述接收端成功接收该未成功接收的RLC PDU，所述接收端停止该继续等待定时器。应理解，这里包括启动t-Reordering定时器或重组分段定时器所检测的所有未成功接收的RLC PDU都成功接收才停止该继续等待定时器。
上述实施例描述的是所述接收端的RLC实体和发送端的RLC实体之间传输RLC PDU数据时如何接收窗口的下边界移动的方案，对于所述接收端的PDCP实体和发送端的PDCD实体之间传输PDCD PDU数据的接收窗口的下边界移动方案，也可以与传输RLC PDU数据的接收窗口的下边界移动方案类似，在此不再赘述。不同的之处在于，所述PDCP层触发的是PDCP的状态报告或包含PDCP SN的移动窗口指示信息。应理解，所述PDCP层可以有类似RLC的第一定时器、第二定时器、第三定时器、第四定时器中的至少一个，各个定时器时长可不同于RLC层的定时器时长。当RLC层不做RLC PDU的重排序，只负责分段的RLC PDU的重组,PDCP负责重排序时，该实施例的PDCP层等待和移窗更优选。
本发明的另一种实施方式，对于UM RLC实体对应一个PDCP实体，也采用VR(R)变量，VR(H)变量和VR(X)，其中，所述VR(H)的值表示PDCP PDU的序列号且为启动第一定时器时已收到的最高PDCP PDU对应的序列号加1，所述VR(R)的值表示PDCP PDU的序列号且为启动第一定时器时所述接收端期望接收的PDCP PDU对应的序列号，所述VR(X)的值表示PDCP PDU的序列号且为启动第一定时器时已收到的最高PDCP PDU对应的序列号加1。
如果接收端收到接收窗口外的数据包，则修改VR(R)值等于VR(H)减去接收窗口长度，即：VR(R)＝VR(H)-接收窗口长度，所述接收窗口长度为固定的能接收的数据包的个数，例如所述接收窗口固定接收n个数据包，n为大于或等于1的正整数，例如n＝100，则所述接收窗口长度为100。确定VR(H)大于VR(R)时，设置VR(X)，启动t-Reordering定时器或重组分段定时器，基于t-Reordering定时器或重组分段定时器管理重排序窗口(VR(R)，VR(X))，例如按照序列号从小到大对接收到PDCP PDU进行排序，所述t-Reordering定时器或重组分段定时器超时后将t-Reordering定时器或重组分段定时器管理窗口内完整的PDCP SDU向上层递交，将VR(X)设置为V(H)，VR(R)设置为大于或等于VR(X)的第一个未收到的包。若收到的PDCP的序列号满足(VR(H)–接收窗口长度)<＝PDCP SN<VR(R)，则接收端将该PDCP PDU丢弃。
本发明的另一种实施方式，对于AM RLC实体对应一个PDCP实体，如果接收端收到下边界的数据包，即收到序列号为VR(R)值的数据包，则接收端进行接收窗口下边界移动，设置VR(R)＝VR(R)+1，设置最大的接收序列号VR(MR)＝VR(R)+接收窗口长度。当VR(H)大于VR(R)启动t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器时长为无穷大。如果接收端收到窗口外的数据包，例如接收端收到序列号为大于VR(MR)的值的PDCP PDU，则丢弃该PDCP PDU。
本发明的另一种实施方式，对于至少两个UM RLC对应一个PDCP，如果接收端收到接收窗口外的数据包，则修改VR(R)值等于VR(H)减去接收窗口长度，即：VR(R)＝VR(H)-接收窗口长度。如果VR(H)大于VR(R)，设置VR(X)，启动t-Reordering定时器或重组分段定时器，基于t-Reordering定时器或重组分段定时器管理重排序窗口(VR(R)，VR(X))，例如按照序列号从小到大对接收到PDCP PDU进行排序，所述t-Reordering定时器或重组分段定时器超时后不移动窗口，超时后将所述t-Reordering定时器或重组分段定时器管理窗口内完整的PDCP SDU向上层递交，将VR(X)设置为 V(H)，若收到t-Reordering定时器或重组分段定时器排序窗口之前的包则丢弃。
本实施例适应不同RLC实体对应的PDCP的推窗，及时推动UM RLC的PDCP窗口，避免AM的PDCP的数据丢失。
上述实施例，针对RLC AM模式的数据传输进行及时接收窗口的下边界移动，可以提高数据传输的可靠性和流畅性。
为了更清楚说明接收窗口的下边界移动，本发明的另一实施例如图14所示，为本发明另一实施例的一种数据传输过程数据状态示意图。
如图14所示，对于一个接收窗口内，接收端接收发送端发送的RLC PDU数据包或PDCP PDU数据包，为描述简化，本实施例中统称数据包。
配置或协议约定一个T1(即为t-Reordering定时器或重组分段定时器)，出现非连续包后启动T1，例如，所述接收端当前接收3号数据包，并接收成功，但发现1号数据包没有接收成功，也即所述接收端当前期望接收序列号为1的数据包，已成功接收最高序列号为3的数据包，因此，VR(R)＝1，VR(H)＝4，VR(X)＝4，所述接收端判断VR(H)>VR(R)，此时，所述接收端启动第一T1。
本发明的另一实施例中，对移动窗口管理的区间进行区分，例如，对于所述序列号为1的数据包初始设置VR1(R)＝VR(R)＝1，VR1(X)＝VR(X)＝4，VR1(H)＝VR(H)＝4。所述接收端在所述T1时长内继续接收所述序列号为1的数据包。
配置或协议约定一个定时器T2(即为继续等待定时器)，所述第一T1超时之前，所述接收端确定所述序列号为1的数据包是否丢失。
如果所述接收端在所述第一T1超时之前成功接收到之前未成功接收的所述序列号为1的数据包，可选发送状态报告，优选的，在这种情况下，不发送状态报告，停止为之前未接收的数据包启动的所述第一T1，所述接收端继续接收后续数据包，直到又出现一个未成功接收的数据包，即所述接收端判断VR(H)>VR(R)，再次针对该新出现的未成功接收数据包启动定时器第二T1。
例如，在所述第一T1超时之前，所述接收端还可以接收3号数据包之后的数据包，如果在启动所述第一T1到所述第一T1超时之间又出现非连续包，也即接收的数据包的序列号大于或等于启动所述第一T1时VR(X)或VR1(X)的值的所有数据包中出现未成功接收的数据包，也即数据包的序列号大于或等于启动所述第一T1时VR(X)的值到序列号为当前VR(X)的值之间的所有接收的数据包为非连续数据包，对于启动第一T1到所述第一T1超时之间第一个未成功接收的数据包启动另一个第二T1。
例如，所述接收端在所述第一T1超时之前已成功接收7号数据包，且2、3和5号数据包已成功接收，但1号、4号、6号数据包未成功接收，即所述接收端期望接收所述序列号为1的数据包，当前已成功接收最高序列号为7的数据包，因此，所述接收端设置VR(R)＝1，VR(H)＝8，VR(X)＝4，对于启动第二T1，针对所述第一T1到所述第一T1超时之间第一个未成功接收的4号数据包，所述接收端设置VR1(R)的值为数据包的序列号大于或等于启动所述第一T1时VR(X)或VR1(X)的所有数据包中第一个未成功 接收的数据包的序列号，也即VR1(R)＝4，VR1(X)＝VR(X)＝8，VR1(H)＝VR(H)＝8，所述接收端判断序列号为VR1(R)＝4至VR1(X)＝8之间的接收数据包为非连续数据包。
如果所述第一T1超时时，所述接收端还是没有成功接收所述序列号为1的数据包，例如，所述接收端已成功接收7号数据包，且2号、3号和5号数据包已成功接收，但1号、4号和6号数据包未成功接收，所述接收端发送状态报告，启动所述第一T2，该状态报告包含所述第一T1超时时所述接收端接收所有数据包的状态报告，例如所述状态报告指示所述1号、4号和6号数据包未成功接收，所述2号、3号、5号和7号数据包成功接收。所述接收端确定所述序列号为1的数据包在所述第一T1超时时已丢失，所述接收端在所述第一T2时长内继续等待接收所述序列号为1的数据包。所述接收端期望接收的数据包设置为序列号为1的数据包，所述第一T1超时成功接收的数据包的最高序列号为7，所述接收端设置VR(R)＝1，VR(H)＝8，VR(X)＝8，VR1(R)＝4，VR1(X)＝VR(X)＝8，VR1(H)＝VR(H)＝8。
如果所述接收端在所述第一T2超时之前成功接收到之前所有未成功接收的数据包，可选发送状态报告，停止为未接收的数据包启动的所述第二T1以及停止所述第一T2，即对于序列号为VR1(R)的值的数据包停止所述第二T1，序列号为VR(R)的值的数据包停止所述第一T2，所述接收端继续接收后续数据包，直到又出现一个未成功接收的数据包，即所述接收端判断VR(H)>VR(R)，再次针对该新出现的未成功接收数据包启动定时器第三T1。
例如，在所述T2超时之前，所述接收端还可以接收7号数据包之后的数据包，如果在启动T2到所述T2超时之间又出现非连续包，也即接收的数据包的序列号大于或等于启动T2时VR(X)或VR1(X)的所有数据包中出现未成功接收的数据包，也即数据包的序列号大于或等于启动T2时VR(X)的值到序列号为当前VR(X)的值之间的所有接收的数据包为非连续数据包，对于启动T2到所述T2超时之间第一个未成功接收的数据包启动另一个第三T1。
例如，所述接收端在所述T2超时之前已成功接收9号数据包，且2、3、4和5号数据包已成功接收，但1号和6号数据包未成功接收，此时，所述接收端停止为序列号为4的数据包启动的第二T1，不停止为序列号为1的数据包启动的第一T2以及为序列号为6的数据包启动的第二T1。应理解，若序列号为4和6号数据包同时发现未成功接收，则第二T1的启动同时针对序列号为4和6号数据包的等待，不必停止针对列号为4的数据包的第二T1，也不必为6号数据包重启动第二T1。
当所述第一T2超时时，所述接收端还是没有成功接收所述序列号为1的数据包，且2、3、4和5号数据包已成功接收，但1号和6号数据包未成功接收，所述接收端将接收窗口的下边界移到启动T1时成功接收序列号最高的数据包之后的所有数据包中第一个未成功接收的数据包，即数据包的序列号大于或等于启动T1时VR(X)的值数据包的所有数据包中第一个未成功接收的数据包的序列号，也即所述接收端将期望接收的数据包设置为序列号为6的数据包，所述第一T2超时成功接收的数据包的最高序列号为9，也即VR(R)＝6，VR(H)＝10，VR(X)＝10，VR1(R)＝6，VR1(X)＝VR(X)＝10，VR1(H)＝VR(H)＝10，所述接收端判断序列号为VR1(R)＝6至VR1(X)＝10之间的接收数据包为非 连续数据包。所述接收端发送状态报告，该状态报告包含所述第一T2超时时所述接收端接收所有数据包的状态报告。
若所述接收端收到上边界外的包，沿用AM模式，则丢弃；或者，若沿用UM模式，则更新上边界到窗口外的包，设置VR(R)＝VR(H)-AM_Window_Size，设置VR(X)＝VR(H)。
在本发明的另一实施例中，所述接收端配置上行最大重传次数，且最大重传次数后不触发RLC复位。
如图15所示，为本发明另一实施例的另一种数据传输处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述接入网设备的RLC层与终端设备的RLC层采用RLC AM模式，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然，本实施例中，所述接收端为所述数据传输处理装置，所述数据传输处理装置包括接收器151、处理器152、发送器153和存储器154，其中，所述接收器151、处理器152、发送器153和存储器154相互之间通过总线通信。
在本申请实施例中，该处理器152可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器154用于存储代码或指令信息，还可以存储设备类型的信息。该存储器154可以包括ROM和RAM，用于向所述处理器152提供指令和数据。所述存储器154的一部分还可以包括非易失性随机存取存储器。
所述处理器152用于确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值，启动第一定时器，设置状态变量VR(X)的值。
所述存储器154保存有几个变量，例如VR(R)，VR(H)和VR(X)，所述接收器151每次接收所述发送端发送的一个RLC PDU时，所述处理器152都需要确定VR(R)，VR(H)和VR(X)的变量值和进行VR(H)和VR(R)相互之间的变量值大小判断，例如，所述接收器151收到所述发送端发送的一个RLC PDU时，所述处理器152确定所述VR(H)的值是否大于所述VR(R)的值并启动所述第一定时器(可以称为t-Reordering定时器或重组分段定时器)，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收器151期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1。
例如，在一个接收窗口内，所述接收器151依次接收所述发送端发送第一RLC PDU、第二RLC PDU和第三RLC PDU，其中，所述第一RLC PDU的序列号为1，所述第二RLC PDU的序列号为2，所述第三RLC PDU的序列号为3，则当前接收窗口的下边界为期待接收所述第一RLC PDU的接收时间点。
如图13所示，所述接收器151未接收所述发送端的RLC PDU之前，期望接收序列号为1的所述第一RLC PDU，当前没有接收到任何RLC PDU，即设置VR(R)，VR(H)和VR(X)的初始变量值为：初始VR(R)＝1，初始VR(H)＝1和初始VR(X)＝1。
所述接收器151在接收所述第一RLC PDU时，所述处理器152需要确定VR(R)，VR(H)和VR(X)的变量值和进行VR(H)和VR(R)相互之间的变量值大小判断，如果所述接收器151成功接收序列号为1所述第一RLC PDU，则所述接收器151期望收到序列号为2的所述第二RLC PDU，即VR(R)＝2，VR(H)＝2，设置VR(X)＝2，所述处理器152判断所述VR(H)等于所述VR(R)；如果所述接收器151未成功接收所述第一RLC PDU，则所述接收器151期望收到序列号为1的所述第一RLC PDU，即VR(R)＝1，VR(H)＝1，设置VR(X)＝1，所述处理器152判断所述VR(H)等于所述VR(R)。
所述接收器151在成功接收到所述第一RLC PDU之后，继续接收所述第二RLC PDU，如果所述接收器151成功接收所述第二RLC PDU，则当前已成功接收到的最高RLC PDU为序列号为2的第二RLC PDU，期望收到的RLC PDU为序列号为3的第三RLC PDU，即VR(R)＝3，VR(H)＝3，设置VR(X)＝3，所述处理器152判断所述VR(H)等于所述VR(R)；如果所述接收器151未成功接收所述第二RLC PDU，则当前已成功接收到的最高RLC PDU为序列号为1的第一RLC PDU，期望收到的RLC PDU为序列号为2的第二RLC PDU，即VR(R)＝2，VR(H)＝2，设置VR(X)＝2，所述处理器152判断所述VR(H)等于所述VR(R)。
所述接收器151在未成功接收到所述第一RLC PDU之后，继续接收所述第二RLC PDU，如果所述接收器151成功接收所述第二RLC PDU，当前已成功接收到的最高RLC PDU为序列号为2的第二RLC PDU，期望收到的RLC PDU为序列号为1的第一RLC PDU，即VR(R)＝1，VR(H)＝3，设置VR(X)＝3，所述处理器152判断所述VR(H)大于所述VR(R)；如果所述接收器151未成功接收所述第二RLC PDU，当前未成功接收到任何RLC PDU，期望收到的RLC PDU为序列号为1的第一RLC PDU，即VR(R)＝1，VR(H)＝1，设置VR(X)＝1，所述处理器152判断所述VR(H)等于所述VR(R)。
针对所述第三RLC PDU的接收后的VR(R)，VR(H)和VR(X)的变量值的确定和VR(H)和VR(R)相互之间的变量值大小的判断，类似于所述第二RLC PDU的接收后VR(R)，VR(H)和VR(X)的变量值的确定和VR(H)和VR(R)相互之间的变量值大小的判断，在此不再赘述。
所述处理器152判断所述VR(H)大于所述VR(R)时，即所述接收器151当前成功接收所述第二RLC PDU但没有成功接收所述第一RLC PDU，亦可以称为成功接收当前RLC PDU之前存在接收RLC PDU的空洞，针对所述没有成功接收的所述第一RLC PDU启动所述第一定时器(可以称为t-Reordering定时器或重组分段定时器)，所述处理器152启动所述第一定时器时，VR(R)＝1，VR(H)＝3，设置VR(X)＝3，所述第一定时器用于所述接收器151在所述第一定时器的时长内继续接收所述第一RLC PDU，所述处理器152在所述第一定时器超时时判断是否成功接收到所述第一RLC PDU。
在本发明的另一实施例中，在所述第一定时器的时长内，所述接收器151还可 以接收所述所述第二RLC PDU之后的RLC PDU，例如所述第三RLC PDU以及所述第三RLC PDU之后的RLC PDU。
所述发送器153用于在所述第一定时器超时，向发送端发送状态报告，所述处理器152还用于启动第二定时器，所述状态报告指示丢失的至少一个RLC PDU的序列号。
所述第一定时器超时，如果所述接收器151成功接收到所述第一RLC PDU，则所述接收器151在所述第一定时器超时时已成功接收到的最高RLC PDU为序列号为2的第二RLC PDU，期望收到的RLC PDU为序列号为3的第三RLC PDU，即VR(R)＝3，VR(H)＝3，设置VR(X)＝3，所述处理器152判断所述VR(H)等于所述VR(R)，可选的，所述发送器153向所述发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收器151接收所有RLC PDU的状态信息，例如包括已经成功接收所述第一RLC PDU的序列号和成功接收所述第二RLC PDU的序列号。
所述第一定时器超时，如果所述接收器151还是未成功接收到所述第一RLC PDU，所述处理器152确定丢失所述第一RLC PDU，所述发送器153发送状态报告，所述处理器152启动所述第二定时器(可以称为继续等待定时器)，所述状态报告指示丢失的所述第一RLC PDU的序列号。所述第二定时器用于所述接收器151继续等待接收其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU，例如，所述处理器152在该第二定时器的时长内继续接收所述未收到的第一RLC PDU，确定所述未收到的第一RLC PDU是否能在该第二定时器超时之前收到。
由于在所述第一定时器的时长内，所述接收器151还可以接收所述所述第二RLC PDU之后的RLC PDU，例如所述第三RLC PDU以及所述第三RLC PDU之后的RLC PDU。
当所述第一定时器超时时，如果所述接收器151接收所述第二RLC PDU之后的RLC PDU为连续接收，例如，所述接收器151在所述第一定时器超时时已成功连续接收到最高序列号等于N的RLC PDU，所述N为大于或等于3的正整数，此时，所述接收器151期待接收的RLC PDU还是序列号为1的所述第一RLC PDU，但所述接收器151在所述第一定时器超时时已经成功接收的RLC PDU的最高序列号为N，则所述处理器152设置VR(R)＝1，VR(H)＝N，VR(X)＝N，所述发送器153发送状态报告，所述状态报告包括所述第一定时器超时时所述接收器151接收所有RLC PDU的状态信息。
当所述第一定时器超时时，如果所述接收器151接收所述第二RLC PDU之后的RLC PDU为非连续接收，例如，所述接收器151在所述第一定时器超时时接收最高序列号等于N的RLC PDU，所述N为大于或等于3的正整数，但在所述序列号为N之前存在有未接收到至少一个RLC PDU，假设已经成功接收的序列号为2的所述第二RLC PDU之后的第一个未成功接收的RLC PDU的序列号为M，所述M为大于或等于3的正整数，所述M小于或等于N；在所述第一定时器超时时，所述接收器151期待接收的RLC PDU还是序列号为1的所述第一RLC PDU，如果所述M小于N，即序列号为N的RLC PDU成功接收，而序列号为M的RLC PDU所述第二RLC PDU之后的第一 个未成功接收的RLC PDU，则所述接收器151在所述第一定时器超时时已经成功接收的RLC PDU的最高序列号为N，则所述处理器152设置VR(R)＝1，VR(H)＝N+1，VR(X)＝N+1；如果所述M等于N，即序列号为N/M的RLC PDU为所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述接收器151在所述第一定时器超时时已经成功接收的RLC PDU的最高序列号为N-1，则所述处理器152设置VR(R)＝1，VR(H)＝(N-1)+1，VR(X)＝(N-1)+1。所述发送器153向所述发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收器151接收所有RLC PDU的状态信息
在本发明的另一实施例中，在所述第二定时器的时长内，所述接收器151还可以接收所述第二RLC PDU之后的RLC PDU，例如所述第三RLC PDU以及所述第三RLC PDU之后的RLC PDU。
所述处理器152还用于在所述第二定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。
所述第二定时器超时时，如果所述接收器151还是没有收到该未收到的第一RLC PDU，所述处理器152确定所述发送端发送的第一RLC PDU丢失，可选的，向所述接入网设备发送最新的状态报告或移动窗口指示信息，则所述处理器152将所述第二定时器超时时的接收窗口的下边界移到或设置下一个期待接收(也即未接收到)的发送端发送的RLC PDU的接收时间点，该过程称为接收窗口的下边界移动。
由于在所述第二定时器的时长内，所述接收器151还可以接收所述第二RLC PDU之后的RLC PDU，当接收所述第二RLC PDU之后的RLC PDU存在不连续接收时，即又出现一个丢失的RLC PDU，所以当所述第二定时器超时时，所述处理器152对接收窗口的下边界移动的VR(R)、VR(H)和VR(X)的变量值设置为：设置所述VR(R)的值为RLC PDU序列号大于或等于所述第一定时器启动时所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(H)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。也即所述接收器151不再等待接收所述第一RLC PDU，而将接收窗口的下边界移到所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(即所述第二RLC PDU)之后的第一个未接收到的RLC PDU的接收序列号。所述发送器153向所述发送端发送状态报告或窗口移动指示信息，所述状态报告包括所述第二定时器超时时所述接收器151接收所有RLC PDU的状态信息，所述窗口移动指示信息包括终端最新期待接收的RLC PDU的序列号，即当前的VR(R)的序列号。
例如，当所述第二定时器超时时，如果所述接收器151接收所述第二RLC PDU之后的RLC PDU为非连续接收，例如，所述接收器151在所述第二定时器超时时接收最高序列号等于K的RLC PDU，所述K为大于或等于3的正整数，但在所述序列号为K之前存在有未接收到至少一个RLC PDU，例如，所述第一定时器启动时已经成功接收的具有最高序列号的RLC PDU为所述第二RLC PDU，假设所述第二RLC PDU之后 的第一个未成功接收的RLC PDU的序列号为L，所述L为大于或等于3的正整数，所述L小于或等于K；在所述第二定时器超时时，所述处理器152进行接收窗口的下边界移动，即将接收窗口的下边界移到所述第二RLC PDU之后的第一个未成功接收的RLC PDU的接收时间点。例如，如果所述L小于K，即序列号为K的RLC PDU为所述第二定时器超时时成功接收的最高序列号的RLC PDU，而序列号为L的RLC PDU为所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述处理器152设置VR(R)＝L，VR(H)＝K+1，VR(X)＝K+1；如果所述L等于K，即序列号为L/K的RLC PDU为所述第二RLC PDU之后的第一个未成功接收的RLC PDU，则所述接收器151在所述第二定时器超时时已经成功接收的RLC PDU的最高序列号为L/K-1，则所述处理器152设置VR(R)＝L/K，VR(H)＝(L/K-1)+1，VR(X)＝(L/K-1)+1。也即所述接收器151不再等待接收所述第一RLC PDU，而将接收窗口的下边界从期待接收的所述第一RLC PDU的接收时间点移到到所述第一定时器启动时已经成功接收的序列号最高为2的第二RLC PDU之后的第一个未接收到的RLC PDU的接收时间点，即将VR(R)＝1修改为VR(R)＝L/K。所述发送器153向所述发送端发送状态报告，所述状态报告包括所述第二定时器超时时所述接收器151接收所有RLC PDU的状态信息
在本发明的另一实施例中，在所述第一定时器超时之前，所述处理器152确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于所述处理器152确定缺失的序列号对应的RLC PDU是否丢失。
例如，针对所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(例如，所述第二RLC PDU)之后的第一个未接收到的RLC PDU(例如，所述序列号为M的RLC PDU，记为RLC PDU SN＝M)，所述处理器152也同样启动一个t-Reordering定时器或重组分段定时器，即第三定时器，例如，所述处理器152在所述第三定时器确定是否丢失所述序列号为M的RLC PDU。应理解，M的RLC PDU可能为分段或完整的RLC PDU。在本发明的另一实施例中，所述第一定时器的时长等于所述第三定时器的时长，或者，所述第一定时器的时长不等于所述第三定时器的时长。应理解，一种实施方式，所述第三定时器就是第一定时器，终端设备同时存在多个第一定时器在运行，分别管理或等待不同的范围的RLC PDU。
例如，在所述第一定时器超时时，所述处理器152启动所述第三定时器，针对所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(例如，所述第二RLC PDU)之后的第一个未接收到的RLC PDU(例如，所述序列号为M的RLC PDU)，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，例如VR1(R)＝M，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1，例如VR1(X)＝N+1。所述发送器153向所述发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收器151接收所有RLC PDU的状态信息。
在所述第三定时器超时时，可选的，发送状态报告，所述状态报告指示所述序 列号为M的RLC PDU已丢失，启动一个继续等待定时器，即第四定时器，第四定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR1(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第三定时器超时时已收到的最高RLC PDU对应的序列号加1。所述发送器153向所述发送端发送状态报告，所述状态报告包括所述第三定时器超时时所述接收器151接收所有RLC PDU的状态信息。一种实施方式，当在所述第三定时器超时时，若接收窗口的接收的RLC PDU的状态没有更新或者已经收到状态报告中指示的未收到的RLC PDU，终端设备可不发送状态报告。
在本发明的另一实施例中，所述第四定时器用于所述接收器151针对所述已经丢失序列号为M的RLC PDU继续在所述第四定时器的时长内等待接收，在所述第四定时器超时时确定是否有收到所述序列号为M的RLC PDU，如果没有收到，确定所述序列号为M的RLC PDU丢失，并进行接收窗口的下边界移动，例如，将所述VR1(R)设置为RLC PDU序列号大于或等于启动第三定时器时已经成功接收的序列号最高的RLC PDU之后的第一个未接收到的RLC PDU的序列号，设置VR1(X)的值为所述第四定时器超时时已收到的最高RLC PDU对应的序列号加1，设置VR1(H)的值为所述第四定时器超时时已收到的最高RLC PDU对应的序列号加1。所述发送器153向所述发送端发送状态报告，所述状态报告包括所述第四定时器超时时所述接收器151接收所有RLC PDU的状态信息。
上述实施例中，对于启动t-Reordering定时器或重组分段定时器的未成功接收的RLC PDU，在该t-Reordering定时器或重组分段定时器超时之前，一旦所述接收器151成功接收该未成功接收的RLC PDU，所述处理器152停止该t-Reordering定时器或重组分段定时器。类似的，对于启动继续等待定时器的未成功接收的RLC PDU，在该继续等待定时器超时之前，一旦所述接收器151成功接收该未成功接收的RLC PDU，所述处理器152停止该继续等待定时器。应理解，这里包括启动t-Reordering定时器或重组分段定时器所检测的所有未成功接收的RLC PDU都成功接收才停止该继续等待定时器。
上述实施例描述的是所述接收端的RLC实体和发送端的RLC实体之间传输RLC PDU数据时如何接收窗口的下边界移动的方案，对于所述接收端的PDCP实体和发送端的PDCD实体之间传输PDCD PDU数据的接收窗口的下边界移动方案，也可以与传输RLC PDU数据的接收窗口的下边界移动方案类似，在此不再赘述。不同的之处在于，所述PDCP层触发的是PDCP的状态报告或包含PDCP SN的移动窗口指示信息。应理解，所述PDCP层可以有类似RLC的第一定时器、第二定时器、第三定时器、第四定时器中的至少一个，各个定时器时长可不同于RLC层的定时器时长。当RLC层不做RLC PDU的重排序，只负责分段的RLC PDU的重组,PDCP负责重排序时，该实施例的PDCP层等待和移窗更优选。
本发明的另一种实施方式，对于UM RLC实体对应一个PDCP实体，也采用VR(R)变量，VR(H)变量和VR(X)，其中，所述VR(H)的值表示PDCP PDU的序列号且为启动第一定时器时已收到的最高PDCP PDU对应的序列号加1，所述VR(R)的值表 示PDCP PDU的序列号且为启动第一定时器时所述接收端期望接收的PDCP PDU对应的序列号，所述VR(X)的值表示PDCP PDU的序列号且为启动第一定时器时已收到的最高PDCP PDU对应的序列号加1。
如果所述接收器151收到接收窗口外的数据包，则所述处理器152修改VR(R)值等于VR(H)减去接收窗口长度，即：VR(R)＝VR(H)-接收窗口长度，所述接收窗口长度为固定的能接收的数据包的个数，例如所述接收窗口固定接收n个数据包，n为大于或等于1的正整数，例如n＝100，则所述接收窗口长度为100。所述处理器152确定VR(H)大于VR(R)时，设置VR(X)，启动t-Reordering定时器或重组分段定时器，基于t-Reordering定时器或重组分段定时器管理重排序窗口(VR(R)，VR(X))，例如按照序列号从小到大对接收到PDCP PDU进行排序，所述发送器153在所述t-Reordering定时器或重组分段定时器超时后将t-Reordering定时器或重组分段定时器管理窗口内完整的PDCP SDU向上层递交，所述处理器152将VR(X)设置为V(H)，VR(R)设置为大于或等于VR(X)的第一个未收到的包。若所述接收器151收到的PDCP的序列号满足(VR(H)–接收窗口长度)<＝PDCP SN<VR(R)，则所述接收器151将该PDCP PDU丢弃。
本发明的另一种实施方式，对于AM RLC实体对应一个PDCP实体，如果所述接收器151收到下边界的数据包，即收到序列号为VR(R)值的数据包，则所述处理器152进行接收窗口下边界移动，设置VR(R)＝VR(R)+1，设置最大的接收序列号VR(MR)＝VR(R)+接收窗口长度。当所述处理器152确定VR(H)大于VR(R)时，启动t-Reordering定时器或重组分段定时器，该t-Reordering定时器或重组分段定时器时长为无穷大。如果所述接收器151收到窗口外的数据包，例如所述接收器151到序列号为大于VR(MR)的值的PDCP PDU，则丢弃该PDCP PDU。
本发明的另一种实施方式，对于至少两个UM RLC对应一个PDCP，如果所述接收器151收到接收窗口外的数据包，则所述处理器152修改VR(R)值等于VR(H)减去接收窗口长度，即：VR(R)＝VR(H)-接收窗口长度。如果所述处理器152确定VR(H)大于VR(R)，设置VR(X)，启动t-Reordering定时器或重组分段定时器，基于t-Reordering定时器或重组分段定时器管理重排序窗口(VR(R)，VR(X))，例如按照序列号从小到大对接收到PDCP PDU进行排序，所述t-Reordering定时器或重组分段定时器超时后不移动窗口，所述发送器153在超时后将所述t-Reordering定时器或重组分段定时器管理窗口内完整的PDCP SDU向上层递交，所述处理器152将VR(X)设置为V(H)，若所述接收器151收到t-Reordering定时器或重组分段定时器排序窗口之前的包则丢弃。
本实施例适应不同RLC实体对应的PDCP的推窗，及时推动UM RLC的PDCP窗口，避免AM的PDCP的数据丢失。
如图16所示，为本发明另一实施例的另一种数据传输的处理方法的流程示意图， 通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤161，接收端确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，向发送端发送状态报告，启动第一定时器，设置状态变量VR(X)的值。
所述第一定时器用于接收端检测未成功接收的序列号为VR(R)的值对应的RLC PDU是否丢弃，所述接收端在所述第一定时器的时长内接收所述序列号为VR(R)的值对应的RLC PDU。
所述状态报告包括启动所述第一定时器时所述接收端接收所有RLC PDU的状态信息，例如所述状态报告包括未成功接收的至少一个RLC PDU的序列号。
所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1。
步骤162，在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续时，启动第三定时器。
所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
步骤163，在所述第一定时器超时时，设置VR(R)的值为RLC PDU序列号大于或等于启动第一定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号，并设置所述第一定时器超时时的VR(X)的值为所述第一定时器超时时的VR(H)的值。
在本发明的另一实施例中，所述第一定时器或第三定时器超时时，可选向所述发送端发送状态报告或窗口移动指示信息，所述状态报告包括所述第一定时器或第三定时器超时时所述接收端接收所有RLC PDU的状态信息，例如所述状态报告包括未收到的至少一个RLC PDU的序列号。所述窗口移动指示信息包括终端最新期待接收的RLC PDU的序列号，即当前的VR(R)的序列号。
为了更清楚说明接收窗口的下边界移动，本发明的另一实施例如图17所示，为本发明另一实施例的一种数据传输过程数据状态示意图。
如图17所示，对于一个接收窗口内，接收端接收发送端发送的RLC PDU数据包或PDCP PDU数据包，为描述简化，本实施例中统称数据包。
配置或协议约定一个T1，所述接收端确定出现非连续包后启动T1，例如，所述接收端当前接收3号数据包，并接收成功，但发现1号数据包没有接收成功，也即所述接收端当前期望接收序列号为1的数据包，已成功接收最高序列号为3的数据包，因此，VR(R)＝1，VR(H)＝4，VR(X)＝4，所述接收端判断VR(H)>VR(R)，此时，所述接收端启 动T1，并向所述发送端发送状态报告，所述状态报告包括启动T1是所述接收端接收所有数据包的状态信息，例如包括未成功接收和成功接收的数据包的序列号，例如未成功接收的数据包的序列号为1，成功接收的数据包的序列号为2和3。所述接收端对应所述序列号为1的数据包，设置VR1(R)＝VR(R)＝1，VR1(H)＝VR(H)＝4，VR1(X)＝VR(X)＝4，所述接收端在所述T1时长内继续接收所述序列号为1的数据包。
如果所述接收端在所述第一T1超时之前成功接收到之前未成功接收的所述序列号为1的数据包，设置VR(R)为大于或等于VR(X)序列号的所有中的第一个未收到大RLC PDU的序列号，可选发送状态报告或窗口移动指示信息，停止为所述序列号为1的数据包启动的所述T1，所述接收端继续接收后续数据包，直到又出现一个未成功接收的数据包，即所述接收端判断VR(H)>VR(R)，再次针对该新出现的未成功接收数据包启动定时器另一T1，并设置VR(X)为当前成功接收的数据包的最高序列号加1。所述所述窗口移动指示信息指示当前接收端期待接收的序列号VR(R)。
例如，在所述T1超时之前，所述接收端还可以接收3号数据包之后的数据包，如果在启动所述T1到所述T1超时之间又出现非连续包，也即接收的数据包的序列号大于或等于启动所述T1时VR(X)或VR1(X)的值的所有数据包中出现未成功接收的数据包，也即数据包的序列号大于或等于启动所述T1时VR(X)的值到序列号为当前VR(X)的值之间的所有接收的数据包为非连续数据包，对于启动所述T1到所述T1超时之间第一个未成功接收的数据包启动另一个T1。
例如，所述接收端在所述T1超时之前已成功接收7号数据包，且2、3和5号数据包已成功接收，但1号、4号、6号数据包未成功接收，即所述接收端期望接收所述序列号为1的数据包，当前已成功接收最高序列号为7的数据包，因此，所述接收端设置VR(R)＝1，VR(H)＝8，VR(X)＝8，对于启动所述T1到所述T1超时之间第一个未成功接收的4号数据包，所述接收端设置VR1(R)的值为数据包的序列号大于或等于启动所述T1时VR(X)或VR1(X)的所有数据包中第一个未成功接收的数据包的序列号，也即VR1(R)＝4，VR1(X)＝VR(X)＝8，VR1(H)＝VR(H)＝8，所述接收端判断序列号为VR1(R)＝4至VR1(X)＝8之间的接收数据包为非连续数据包。
当所述T1超时时，所述接收端还是没有成功接收所述序列号为1的数据包，且2、3、4和5号数据包已成功接收，但1号和6号数据包未成功接收，所述接收端将接收窗口的下边界移到启动T1时成功接收序列号最高的数据包之后的所有数据包中第一个未成功接收的数据包，即数据包的序列号大于或等于启动T1时VR(X)的值数据包的所有数据包中第一个未成功接收的数据包的序列号，也即所述接收端将期望接收的数据包设置为序列号为6的数据包，所述T1超时成功接收的数据包的最高序列号为9，也即VR(R)＝6，VR(H)＝10，VR(X)＝10，VR1(R)＝6，VR1(X)＝VR(X)＝10，VR1(H)＝VR(H)＝10，所述接收端判断序列号为VR1(R)＝6至VR1(X)＝10之间的接收数据包为非连续数据包。可选，所述接收端发送状态报告或所述窗口移动指示信息，该状态报告包含所述T1超时时所述接收端接收所有数据包的状态报告。所述窗口移动指示信息指示接收端期待接收的序列号为6。
若所述接收端收到上边界外的包，沿用AM模式，则丢弃；或者，若沿用UM 模式，则更新上边界到窗口外的包，设置VR(R)＝VR(H)-AM_Window_Size，设置VR(X)＝VR(H)。
在本发明的另一实施例中，所述接收端配置上行最大重传次数，且最大重传次数后不触发RLC复位。
如图18所示，为本发明另一实施例的另一种数据传输处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
本实施例中，所述数据传输处理装置为所述接收端，所述数据传输处理装置包括接收器181、处理器182、发送器183和存储器184，其中，所述接收器181、处理器182、发送器183和存储器184相互之间通过总线通信。
在本申请实施例中，该处理器182可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器184用于存储代码或指令信息，还可以存储设备类型的信息。该存储器184可以包括ROM和RAM，用于向所述处理器182提供指令和数据。所述存储器184的一部分还可以包括非易失性随机存取存储器。
所述接收器181用于接收所述发送端发送的RLC PDU。
所述处理器182用于确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，启动第一定时器，设置状态变量VR(X)的值。
所述发送器183用于在所述处理器182确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，向所述发送端发送状态报告。
所述第一定时器用于所述处理器182检测未成功接收的序列号为VR(R)的值对应的RLC PDU是否丢弃，所述接收器181在所述第一定时器的时长内接收所述序列号为VR(R)的值对应的RLC PDU。
所述状态报告包括启动所述第一定时器时所述接收端接收所有RLC PDU的状态信息，例如所述状态报告包括未成功接收的至少一个RLC PDU的序列号。
所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1。
所述处理器182还用于在所述第一定时器超时之前，确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续时，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
所述处理器182还用于在所述第一定时器超时时，设置VR(R)的值为RLC PDU 序列号大于或等于启动第一定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号，并设置所述第一定时器超时时的VR(X)的值为所述第一定时器超时时的VR(H)的值。
在本发明的另一实施例中，所述发送器183还用于在所述第一定时器或第三定时器超时时，向所述发送端发送状态报告，所述状态报告包括所述第一定时器或第三定时器超时时所述接收端接收所有RLC PDU的状态信息，例如所述状态报告包括未收到的至少一个RLC PDU的序列号。
上述所有实施例中，对于各种定时器，例如t-Reordering定时器、重组分段定时器、继续等待定时器，第一定时器、第二定时器、第三定时器或第四定时器，如果启动定时器的数据包(例如RLC PDU或PDCP PDU)在其对应的定时器超时之前被成功接收，则该定时器停止。例如接收端发现一个RLC PDU或PDCP PDU没有被成功接收时，启动t-Reordering定时器，在该t-Reordering定时器超时之前，如果所述接收端成功接收了所述RLC PDU或PDCP PDU，则该t-Reordering定时器停止；例如接收端发现为一个RLC PDU或PDCP PDU启动t-Reordering定时器，如果所述接收端在t-Reordering定时器超时时还没有成功接收该RLC PDU或PDCP PDU，所述接收端为所述RLC PDU或PDCP PDU启动继续等待定时器，在该继续等待定时器超时之前，如果所述接收端成功接收了所述RLC PDU或PDCP PDU，则该继续等待定时器停止。
应该理解的是，所述t-Reordering定时器、重组分段定时器、继续等待定时器，第一定时器、第二定时器、第三定时器或第四定时器在超时时，均停止。
如图19所示，为本发明另一实施例的另一种数据传输的处理方法的流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤191，发送端的RLC层接收该发送端的PDCP层发送的丢弃第一PDCP PDU的丢弃指示。
步骤192，所述发送端的所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者所述第一PDCP PDU对应的RLC SDU。
本发明的另一实施例的中，如果所述RLC层还未对所述第一PDCP PDU进行处理，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。本发明的另一实施例的中，所述RLC层还未对所述第一PDCP PDU进行处理包括：所述RLC层还未对所述第一PDCP PDU进行RLC序列号编号或未生成所述第一PDCP PDU对应的RLC PDU。
本发明的另一实施例中，如果所述RLC层已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
可选的，发送端的PDCP层确定丢弃第一PDCP PDU，通知接收端的PDCP丢弃的PDCP的SN。
本发明的另一实施例的中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，用于所述RLC层在收到所述第一PDCP PDU启动所述丢弃定时器并在所述丢弃定时器超时时丢弃所述第一PDCP PDU。
可选的，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
本实施例的数据传输的处理方法，对于PDCP PDU包在RLC分段传输后，当部分分段包丢弃后，不必重传其他其余的分段包，提高传输速率。
如图20所示，为本发明另一实施例的另一种数据传输处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的基站或5G通信系统中的gNB，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然，本实施例中，所述发送端为所述数据传输处理装置，所述数据传输处理装置包括接收器201、处理器202、发送器203和存储器204，其中，所述接收器201、处理器202、发送器203和存储器204相互之间通过总线通信。
在本申请实施例中，该处理器202可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器204用于存储代码或指令信息，还可以存储设备类型的信息。该存储器204可以包括ROM和RAM，用于向所述处理器202提供指令和数据。所述存储器204的一部分还可以包括非易失性随机存取存储器。
所述接收器201用于接收该发送端的PDCP层发送的丢弃第一PDCP PDU的丢弃指示。
所述处理器202用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者所述第一PDCP PDU对应的RLC SDU。
本发明的另一实施例的中，如果所述处理器202还未对所述第一PDCP PDU进行处理，所述处理器202根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。本发明的另一实施例的中，所述处理器202还未对所述第一PDCP PDU进行处理包括：所述处理器202还未对所述第一PDCP PDU进行RLC序列号编号或未生成所述第一PDCP PDU对应的RLC PDU。
本发明的另一实施例中，如果所述处理器202已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，所述处理器202根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
本发明的另一实施例的中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息； 或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，所述接收器201用于在收到所述第一PDCP PDU时，所述处理器202用于启动所述丢弃定时器并在所述丢弃定时器超时时丢弃所述第一PDCP PDU。
本实施例的数据传输的处理方法，对于PDCP PDU包在RLC分段传输后，当部分分段包丢弃后，不必重传其他其余的分段包，提高传输速率。
如图21所示，为本发明另一实施例的另一种数据传输的处理方法的流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述分布式基站包括RRU和BBU，所述gNB包括CU和DU，但为描述的简洁，本实施例以gNB为例进行说明，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤211，DU接收CU针对第一承载或第一逻辑信道(组)发送的丢弃定时器。
应理解，第一承载或第一逻辑信道(组)发送的丢弃定时器，可以是针对终端设备的一个或多个承载共用一个丢弃定时器。所述丢弃定时器包含用于管理RLC SDU、RLC PDU或PDCP PDU的丢弃。
步骤212，所述DU接收所述CU发送的所述第一承载或第一逻辑信道(组)的PDCP PDU时，启动所述丢弃定时器，在所述丢弃定时器超时时丢弃所述PDCP PDU。
本发明的另一实施例中，如果所述DU还未对所述PDCP PDU进行处理，所述DU在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC SDU。本发明的另一实施例中，所述DU未对所述PDCP PDU进行处理包括：所述DU未对所述PDCP PDU进行RLC序列号编号或未生成所述PDCP PDU对应的RLC PDU。
本发明的另一实施例中，如果所述DU已经对所述PDCP PDU进行RLC序列号编号或已经生成所述PDCP PDU对应的RLC PDU或已经发送所述PDCP PDU，所述DU在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
可选的，发送端的PDCP层确定丢弃所述PDCP PDU，通知接收端的PDCP丢弃的PDCP的SN。
如图22所示，为本发明另一实施例的另一种数据传输处理装置的结构示意图，
通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述分布式基站包括RRU和BBU，所述gNB包括CU和DU，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
本实施例中，但为描述的简洁，本实施例以gNB为例进行说明，所述数据传输处理装置为所述DU，所述数据传输处理装置包括接收器221、处理器222、发送器223和存储器224，其中，所述接收器221、处理器222、发送器223和存储器224相互之间 通过总线通信。
在本申请实施例中，该处理器222可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器224用于存储代码或指令信息，还可以存储设备类型的信息。该存储器224可以包括ROM和RAM，用于向所述处理器222提供指令和数据。所述存储器224的一部分还可以包括非易失性随机存取存储器。
所述接收器221用于接收CU针对第一承载或第一逻辑信道(组)发送的丢弃定时器。
所述处理器222用于在所述DU接收所述CU发送的所述第一承载或第一逻辑信道(组)的PDCP PDU时，启动所述丢弃定时器，在所述丢弃定时器超时时丢弃所述PDCP PDU。
本发明的另一实施例中，如果所述处理器222还未对所述PDCP PDU进行处理，所述处理器222在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC SDU。
本发明的另一实施例中，所述处理器222未对所述PDCP PDU进行处理包括：所述处理器222未对所述PDCP PDU进行RLC序列号编号或未生成所述PDCP PDU对应的RLC PDU。
本发明的另一实施例中，如果所述处理器222已经对所述PDCP PDU进行RLC序列号编号或已经生成所述PDCP PDU对应的RLC PDU或已经发送所述PDCP PDU，
所述处理器222还用于在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC PDU，所述发送器223用于通知终端设备丢弃与所述RLC PDU对应的序列号。
如图23所示，为本发明另一实施例的另一种数据传输的处理方法的流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤231，发送端的PDCP层或SDAP层收到上层包后，启动丢弃定时器(discard timer)。
例如，所述丢弃定时器是预先配置的。
步骤232，所述发送端的PDCP层向所述发送端的RLC层发送PDCP PDU。
例如，所述发送端的PDCP层将所述上层包处理为所述PDCP PDU并向所述发送端的RLC层发送。
步骤233，所述发送端的RLC层向所述发送端的MAC层发送RLC PDU。
例如，所述发送端的RLC层将从所述发送端的PDCP层接收的所述PDCP PDU处理为所述RLC PDU并向所述发送端的MAC层发送。
步骤234，当该定时器超时后，所述发送端的PDCP层指示所述发送端的RLC 层丢弃所述PDCP PDU对于的RLC PDU或所述PDCP PDU对于的RLC SDU。
例如，若所述发送端的PDCP层已经将该PDCP PDU发送给所述发送端的RLC层，所述发送端的PDCP层通知所述发送端的RLC层丢弃该RLC SDU包，不管所述发送端的RLC层是否已经生成对应的RLC PDU以及是否已经发送过的RLC PDU。
步骤235，所述发送端的RLC层将这个丢弃的RLC PDU或RLC SDU数据包对应的的RLC SN通知接收端的RLC层。
本步骤为可选步骤，可以不执行。
在本发明的另一实施例中，若所述发送端的RLC层对于所述PDCP已经有RLC PDU SN号或已经发送过该PDCP对应的RLC PDU，所述发送端的RLC层通知所述接收端的RLC层丢弃的RLC SN的丢弃信息，所述接收端的RLC层根据该丢弃信息进行所述发送端的RLC层的接收窗口移动。所述接收端的RLC层如果发现这个RLC SN所对应的包已经有一部分分段(segment)收到了，就删除已经收到的segment。.
在本发明的另一实施例中，所述发送端的PDCP层还可以将这个丢弃的RLC PDU或RLC SDU数据包对应的的PDCP SN通知接收端的PDCP层。
在本发明的另一实施例中，所述发送端的RLC层还可以将这个丢弃的RLC PDU SN通知接收端的RLC层。
可选的，所述接收端的RLC层进行接收窗口移动后，更新VR(R)，可选地，所述接收端的RLC层向所述发送端的RLC层发送更新的VR(R)。发送端将发送窗口的上边界移动到窗口移动指示中的序列号VR(R)的值。
可选的，如果所述发送端的RLC层通知所述接收端的RLC层的丢弃包所对应的RLC SN大于所述接收端的RLC层保存的VR(R)，且RLC SN与VR(R)之间的包已经全部都收到了，则所述接收端的RLC层更新VR(R)为RLC SN之后的第一个未收到的包的序号。
在本发明的另一实施例中，所述接收端的RLC层不需要向所述发送端的RLC层发送更新的VR(R)。
在本发明的另一实施例中，所述接收端的RLC层确定所述发送端的RLC层指示的不再传输的RLC SN对应的数据包已经收到，可选地，所述发送端指示所述接收端的PDCP实体与所述RLC SN对应的PDCP SN的数据包已经收到。
步骤236，所述接收端的所述RLC层将所述PDCP SN通知所述接收端的PDCP层。
本步骤为可选步骤，可以不执行。
步骤237，所述接收端的所述RLC层向所述发送端的RLC层发送丢弃确定指示。
本步骤为可选步骤，可以不执行。
在本发明的另一实施例中，若PDCP层和RLC层分别在CU和DU时，所述CU 的PDCP层在将PDCP PDU数据包发送到DU的RLC层时将丢弃定时器也发生给所述DU的RLC层，或者所述CU在发送所述PDCP PDU数据包前将将丢弃定时器配置给所述DU的RLC层，例如，通过信令配置或网管配置。所述DU的RLC层收到所述PDCP PDU数据包后启动该丢弃定时器，当所述丢弃定时器超时后丢弃所述PDCP PDU对应的RLC PDU或RLC SDU，通知所述接收端丢弃。
在本发明的另一实施例中，针对不同PDCP PDU数据包设置不同的discard timer，重要包(例如视频数据重要I帧)的discard timer时长大，非重要包(例如，视频数据的非重要P帧)的discard timer时长小。假设重要包和非重要包有关联关系，发送端只要发现同一个关联关系的最后一个非重要包的数据对应的discard timer超时，就认为和该包关联的重要包对应的discard timer超时。发送端的PDCP/CU指示RLC层丢弃多个PDCP PDU对应的RLC PDU/SDU。
如图24所示，为本发明另一实施例的另一种数据传输的处理方法的流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述分布式基站包括RRU和BBU，所述gNB包括CU和DU，但为描述的简洁，本实施例以gNB为例进行说明，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤241，DU接收CU发送的丢弃第一PDCP PDU的丢弃指示。
步骤242，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
在本发明的另一实施例中，如果所述DU还未对所述第一PDCP PDU进行处理，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。在本发明的另一实施例中，所述DU还未对所述第一PDCP PDU进行处理包括：所述DU未对所述第一PDCP PDU进行RLC序列号编号或未生成所述第一PDCP PDU对应的RLC PDU。
在本发明的另一实施例中，如果所述DU已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
在本发明的另一实施例中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，用于所述DU在收到所述第一PDCP PDU启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
如图25所示，为本发明另一实施例的另一种数据传输处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述分布式基站包括RRU和BBU，所述gNB包括CU和DU，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收 端，反之亦然。
本实施例中，但为描述的简洁，本实施例以gNB为例进行说明，所述数据传输处理装置为所述DU，所述数据传输处理装置包括接收器251、处理器252、发送器253和存储器254，其中，所述接收器251、处理器252、发送器253和存储器254相互之间通过总线通信。
在本申请实施例中，该处理器252可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器254用于存储代码或指令信息，还可以存储设备类型的信息。该存储器254可以包括ROM和RAM，用于向所述处理器252提供指令和数据。所述存储器254的一部分还可以包括非易失性随机存取存储器。
所述接收器251用于接收CU发送的丢弃第一PDCP PDU的丢弃指示。
所述处理器252用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
在本发明的另一实施例中，如果所述处理器252还未对所述第一PDCP PDU进行处理，所述处理器252用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。在本发明的另一实施例中，所述处理器252还未对所述第一PDCP PDU进行处理包括：所述处理器252未对所述第一PDCP PDU进行RLC序列号编号或未生成所述第一PDCP PDU对应的RLC PDU。
在本发明的另一实施例中，如果所述处理器252已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，所述处理器252用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
在本发明的另一实施例中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，所述丢弃指示为所述第一PDCP PDU的丢弃定时器，所述接收器251还用于在收到所述第一PDCP PDU时，所述处理器252用于启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
如图26所示，为本发明另一实施例的另一种数据传输处理方法的流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述分布式基站包括RRU和BBU，所述gNB包括CU和DU，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤261，在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定第一定时器启动时的VR(X)的值到当前VR(H)的值之间缺失的序列号对应的RLC PDU是否丢失。
例如，针对所述第一定时器启动时已经成功接收的序列号最高的RLC PDU(例如，所述第二RLC PDU)之后的第一个未接收到的RLC PDU(例如，所述序列号为M的RLC PDU，记为RLC PDU SN＝M)，所述接收端也同样启动一个t-Reordering定时器或重组分段定时器，即第三定时器，例如，所述接收端在所述第三定时器确定是否丢失所述序列号为M的RLC PDU。应理解，M的RLC PDU可能为分段或完整的RLC PDU。在本发明的另一实施例中，所述第一定时器的时长等于所述第三定时器的时长，或者，所述第一定时器的时长不等于所述第三定时器的时长。应理解，一种实施方式，所述第三定时器就是第一定时器，终端设备同时存在多个第一定时器在运行，分别管理或等待不同的范围的RLC PDU。
步骤262，在所述第一定时器超时时且第三定时器在运行，设置VR1(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1。
步骤2621，可选的，所述接收端向发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息。
步骤263，在所述第一定时器超时时且第三定时器不在运行，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1。
步骤2631，可选的，所述接收端向发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息。
其中，所述步骤262和步骤263是并列的步骤。
通过本发明实施例可为不同时刻丢失的包分别管理等待时间，及时触发状态报告，来获得及时的重传。
如图27所示，为本发明另一实施例的另一种数据传输处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是2G/3G/4G的分布式基站或5G通信系统中的gNB，所述分布式基站包括RRU和BBU，所述gNB包括CU和DU，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
本实施例中，但为描述的简洁，本实施例以gNB为例进行说明，所述数据传输处理装置为所述DU，所述数据传输处理装置包括接收器271、处理器272、发送器273和存储器274，其中，所述接收器271、处理器272、发送器273和存储器274相互之间通过总线通信。
在本申请实施例中，该处理器272可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器274用于存储代码或指令信息，还可以存储设备类型的信息。该存储器274可以包括ROM和RAM，用于向所述处理器272提供指令和数据。所述存储器274的一部分还可以包括非易失性随机存取存储器。
所述处理器272，用于在所述第一定时器超时之前，确定所述接收器271接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定第一定时器启动时的VR(X)的值到当前VR(H)的值之间缺失的序列号对应的RLC PDU是否丢失。
例如，针对所述第一定时器启动时所述接收器271已经成功接收的序列号最高的RLC PDU(例如，所述第二RLC PDU)之后的第一个未接收到的RLC PDU(例如，所述序列号为M的RLC PDU，记为RLC PDU SN＝M)，所述接收端也同样启动一个t-Reordering定时器或重组分段定时器，即第三定时器，例如，所述处理器272在所述第三定时器确定是否丢失所述序列号为M的RLC PDU。应理解，M的RLC PDU可能为分段或完整的RLC PDU。
在本发明的另一实施例中，所述第一定时器的时长等于所述第三定时器的时长，或者，所述第一定时器的时长不等于所述第三定时器的时长。应理解，一种实施方式，
所述第三定时器就是第一定时器，终端设备同时存在多个第一定时器在运行，分别管理或等待不同的范围的RLC PDU。
所述处理器272还用于在所述第一定时器超时时且第三定时器在运行，设置VR1(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1。可选的，所述发送器273用于向发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息。
所述处理器272还用于在所述第一定时器超时时且第三定时器不在运行，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1。可选的，所述发送器273用于向发送端发送状态报告，所述状态报告包括所述第一定时器超时时所述接收端接收所有RLC PDU的状态信息。
通过本发明实施例可为不同时刻丢失的包分别管理等待时间，及时触发状态报告，来获得及时的重传。
在本发明的另一实施例中，为了节省开销和降低处理时延，使用UM传输模式协议层的协议数据单元在不分段的情况下可以没有本协议层的子头。这种情况下，本协议层的下一协议层的报头中需要包含本协议层的协议数据单元是否包含报头的指示。针对3GPP LTE和NR两种无线接入技术，当本协议层为RLC时，下一协议层为MAC，前面所述的指示可以为RLC PDU对应的MAC子头中用一个reserved bit来指示该RLC PDU是否包含RLC报头。进一步地，下一协议层协议数据单元的报头包含“上一协议层 的协议数据单元是否有子头”的指示也适用于3GPP NR无线接入技术中用PDCP PDU报头指示SDAP PDU是否有报头的情况。通过本发明实施例节省开销和降低处理时延，解决接收端RLC处理有、无RLC头的问题。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
应理解，在本申请的各个实施例中，上述各过程的序号大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
该作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
该功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以 存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例该方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (42)

  1. 一种数据传输的处理方法，其特征在于，包括：
    接入网设备生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；
    所述接入网设备将所述终端设备的配置信息发送给所述终端设备。
  2. 如权利要求1所述的方法，其中，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
  3. 如权利要求1所述的方法，其中，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器，每个定时器由其对应的RLC实体用于检测所述接入网设备发送的RLC PDU是否丢失。
  4. 如权利要求1所述的方法，其中，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器，每个所述定时器用于其对应的RLC实体等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。
  5. 一种数据传输的处理装置，其特征在于，包括：
    处理器，用于生成终端设备的配置信息，其中，所述终端设备的配置信息为所述终端设备的一个PDCP实体映射到至少两个不同的RLC实体；
    发送器，用于将所述终端设备的配置信息发送给所述终端设备。
  6. 如权利要求5所述的装置，其中，所述至少两个不同的RLC实体分别采用RLC AM和RLC UM。
  7. 如权利要求5所述的装置，其中，所述至少两个不同的RLC实体均采用RLC AM或RLC UM，且所述至少两个不同的RLC实体分别配置不同时长的定时器，每个定时器用于其对应的RLC实体检测所述接入网设备发送的RLC PDU是否丢失。
  8. 如权利要求1所述的装置，其中，所述至少两个不同的RLC实体均采用RLC AM，且所述至少两个不同的RLC实体中的至少一个RLC实体配置定时器，每个所述定时器用于其对应的RLC实体等待其发送的状态报告中指示的未收到的所述接入网设备发送的RLC PDU。
  9. 一种数据传输的处理方法，其特征在于，包括：
    接收端确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值，启动第一定时器，设置状态变量VR(X)的值，其中，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；
    所述第一定时器超时，发送状态报告，启动第二定时器，所述状态报告指示丢失的至少一个RLC PDU的序列号；
    所述第二定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。
  10. 如权利要求9所述的方法，其中，所述方法还包括：
    在所述第一定时器超时时，启动第三定时器，设置VR1(R)的值为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1；
    所述第三定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR1(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第三定时器超时时已收到的最高RLC PDU对应的序列号加1。
  11. 如权利要求9所述的方法，其中，所述方法还包括：
    在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
  12. 一种数据传输的处理装置，其特征在于，包括：
    处理器，用于确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值，启动第一定时器，设置状态变量VR(X)的值，其中，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；
    发送器，用于在所述第一定时器超时，发送状态报告，所述状态报告指示丢失的至少一个RLC PDU的序列号；
    所述处理器还用于在所述第一定时器超时，启动第二定时器；
    所述处理器还用于所述第二定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第二定时器超时时已收到的最高RLC PDU对应的序列号加1。
  13. 如权利要求12所述的装置，其中，
    所述处理器还用于在所述第一定时器超时时，启动第三定时器，设置VR1(R)的值 为RLC PDU序列号大于或等于启动第一定时器时所设置的所述VR(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR1(X)的值为所述第一定时器超时时已收到的最高RLC PDU对应的序列号加1；
    所述处理器还用于所述第三定时器超时，设置所述VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所设置的所述VR1(X)的值对应的RLC PDU序列号对应的所有RLC PDU中第一个未接收到RLC PDU的序列号，设置所述VR(X)的值为所述第三定时器超时时已收到的最高RLC PDU对应的序列号加1。
  14. 如权利要求12所述的装置，其中，
    所述处理器还用于在所述第一定时器超时之前，确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
  15. 一种数据传输的处理方法，其特征在于，包括：
    接收端确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，向发送端发送状态报告，启动第一定时器，设置状态变量VR(X)的值，其中，所述状态报告包括启动所述第一定时器时所述接收端接收所有RLC PDU的状态信息，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；
    在所述第一定时器超时时，设置VR(R)的值为RLC PDU序列号大于或等于启动第一定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号，并设置所述第一定时器超时时的VR(X)的值为所述第一定时器超时时的VR(H)的值；或者，
    在所述第一定时器超时之前，接收端确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
  16. 如权利要求15所述的方法，其中，所述方法还包括：
    在所述第一定时器超时且第三定时器在运行，设置VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号。
  17. 如权利要求15所述的方法，其中，所述方法还包括：
    在所述第一或第三定时器超时时，向所述发送端发送状态报告，所述状态报告包括所述第一或第三定时器超时时所述接收端接收所有RLC PDU的状态信息。
  18. 一种数据传输的处理装置，其特征在于，包括：
    处理器，用于在确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时， 启动第一定时器，设置状态变量VR(X)的值，其中，所述VR(H)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1，所述VR(R)的值表示RLC PDU的序列号且为启动第一定时器时所述接收端期望接收的RLC PDU对应的序列号，所述VR(X)的值表示RLC PDU的序列号且为启动第一定时器时已收到的最高RLC PDU对应的序列号加1；
    发送器，用于在确定最高接收状态变量VR(H)的值大于接收状态变量VR(R)的值时，向发送端发送状态报告，其中，所述状态报告包括启动所述第一定时器时所述接收端接收所有RLC PDU的状态信息；
    所述处理器还用于在所述第一定时器超时时，设置VR(R)的值为RLC PDU序列号大于或等于启动第一定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号，并设置所述第一定时器超时时的VR(X)的值为所述第一定时器超时时的VR(H)的值；或者所述处理器还用于在所述第一定时器超时之前，确定接收到的RLC PDU的序列号在第一定时器启动时的VR(X)的值到当前VR(H)的值之间存在不连续，启动第三定时器，所述第三定时器用于接收端确定缺失的序列号对应的RLC PDU是否丢失。
  19. 如权利要求18所述的装置，其中，
    所述处理器还用于在所述第一定时器超时且第三定时器在运行，设置VR(R)的值为RLC PDU序列号大于或等于启动第三定时器时所述VR(X)的值对应的RLC PDU序列号的所有接收RLC PDU中第一个未成功接收的RLC PDU的序列号。
  20. 如权利要求18所述的装置，其中，
    所述发送器还用于在所述第一或第三定时器超时时，向所述发送端发送状态报告，所述状态报告包括所述第一或第三定时器超时时所述接收端接收所有RLC PDU的状态信息。
  21. 一种数据传输的处理方法，其特征在于，包括：
    发送端的RLC层接收该发送端的PDCP层发送的丢弃第一PDCP PDU的丢弃指示；
    所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
  22. 如权利要求21所述的方法，其中，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU包括：
    如果所述RLC层还未对所述第一PDCP PDU进行处理，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
  23. 如权利要求21所述的方法，其中，所述RLC层根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU包括：
    如果所述RLC层已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU所述RLC层根据所 述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
  24. 如权利要求21所述的方法，其中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，
    所述丢弃指示为所述第一PDCP PDU的丢弃定时器，用于所述RLC层在收到所述第一PDCP PDU启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
  25. 一种数据传输的处理装置，其特征在于，包括：
    接收器，用于接收该发送端的PDCP层发送的丢弃第一PDCP PDU的丢弃指示；
    处理器，用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
  26. 如权利要求25所述的装置，其中，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU具体包括：
    所述处理器，用于如果还未对所述第一PDCP PDU进行处理，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
  27. 如权利要求25所述的装置，其中，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU具体包括：
    所述处理器，用于如果已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知接收端丢弃与所述RLC PDU对应的序列号。
  28. 如权利要求25所述的装置，其中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，
    所述丢弃指示为所述第一PDCP PDU的丢弃定时器，所述处理器，还用于在所述接收器收到所述第一PDCP PDU时，启动所述丢弃定时器并在所述丢弃定时器超时时丢弃所述第一PDCP PDU。
  29. 一种数据传输的处理方法，基站包括CU和DU，其特征在于，包括：
    DU接收CU针对第一承载或第一逻辑信道(组)第一承载或第一逻辑信道(组)或第一逻辑信道(组)发送的丢弃定时器；
    DU接收所述第一承载或第一逻辑信道(组)的PDCP PDU时，启动所述丢弃定时器，在所述丢弃定时器超时时丢弃所述PDCP PDU。
  30. 如权利要求29所述的方法，其中，所述在所述丢弃定时器超时时丢弃所述PDCP PDU包括：
    如果所述DU还未对所述PDCP PDU进行处理，所述DU在所述丢弃定时器超时时 丢弃所述PDCP PDU对应的所述RLC SDU。
  31. 如权利要求29所述的方法，其中，所述在所述丢弃定时器超时时丢弃所述PDCP PDU包括：
    如果所述DU已经对所述PDCP PDU进行RLC序列号编号或已经生成所述PDCP PDU对应的RLC PDU或已经发送所述PDCP PDU，所述DU在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
  32. 一种数据传输的处理装置，其特征在于，包括：
    接收器，用于接收CU针对第一承载或第一逻辑信道(组)发送的丢弃定时器；
    处理器，用于所述接收器接收所述第一承载或第一逻辑信道(组)的PDCP PDU时，启动所述丢弃定时器，在所述丢弃定时器超时时丢弃所述PDCP PDU。
  33. 如权利要求32所述的装置，其中，所述处理器用于在所述丢弃定时器超时时丢弃所述PDCP PDU具体包括：
    所述处理器用于如果还未对所述PDCP PDU进行处理，在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC SDU。
  34. 如权利要求32所述的装置，其中，所述处理器用于在所述丢弃定时器超时时丢弃所述PDCP PDU具体包括：
    所述处理器用于如果已经对所述PDCP PDU进行RLC序列号编号或已经生成所述PDCP PDU对应的RLC PDU或已经发送所述PDCP PDU，在所述丢弃定时器超时时丢弃所述PDCP PDU对应的所述RLC PDU；
    所述数据传输的处理装置还包括：发送器，用于通知终端设备丢弃与所述RLC PDU对应的序列号。
  35. 一种数据传输的处理方法，基站包括CU和DU，其特征在于，包括：
    DU接收CU发送的丢弃第一PDCP PDU的丢弃指示；
    所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
  36. 如权利要求35所述的方法，其中，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU包括：
    如果所述DU还未对所述第一PDCP PDU进行处理，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
  37. 如权利要求35所述的方法，其中，所述DU根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU包括：
    如果所述DU已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，所述DU根据所述丢 弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU并通知终端设备丢弃与所述RLC PDU对应的序列号。
  38. 如权利要求35所述的方法，其中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，
    所述丢弃指示为所述第一PDCP PDU的丢弃定时器，用于所述DU在收到所述第一PDCP PDU启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
  39. 一种数据传输的处理装置，其特征在于，包括：
    接收器，用于接收分布式单元CU发送的丢弃第一PDCP PDU的丢弃指示；
    处理器，用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU或者对应的RLC SDU。
  40. 如权利要求39所述的装置，其中，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC SDU具体包括：
    所述处理器用于如果还未对所述第一PDCP PDU进行处理，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC SDU。
  41. 如权利要求39所述的装置，其中，所述处理器用于根据所述丢弃指示丢弃所述第一PDCP PDU对应的RLC PDU具体包括：
    所述处理器用于如果已经对所述第一PDCP PDU进行RLC序列号编号或已经生成所述第一PDCP PDU对应的RLC PDU或已经发送所述第一PDCP PDU，根据所述丢弃指示丢弃所述第一PDCP PDU对应的所述RLC PDU；
    所述数据传输的处理装置还包括：发送器，用于通知终端设备丢弃与所述RLC PDU对应的序列号。
  42. 如权利要求39所述的装置，其中，所述丢弃指示携带丢弃所述第一PDCP PDU的信息；或者，
    所述丢弃指示为所述第一PDCP PDU的丢弃定时器，所述处理器用于在所述接收器收到所述第一PDCP PDU时启动所述丢弃定时器并所述丢弃定时器超时时丢弃所述第一PDCP PDU。
PCT/CN2018/085746 2017-05-05 2018-05-05 一种数据传输的处理方法和装置 WO2018202190A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18794399.8A EP3609106A4 (en) 2017-05-05 2018-05-05 DATA TRANSFER PROCESSING METHOD AND DEVICE
US16/672,974 US20200068652A1 (en) 2017-05-05 2019-11-04 Data transmission processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710314177.2A CN108809542B (zh) 2017-05-05 2017-05-05 一种数据传输的处理方法和装置
CN201710314177.2 2017-05-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/672,974 Continuation US20200068652A1 (en) 2017-05-05 2019-11-04 Data transmission processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2018202190A1 true WO2018202190A1 (zh) 2018-11-08

Family

ID=64016344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085746 WO2018202190A1 (zh) 2017-05-05 2018-05-05 一种数据传输的处理方法和装置

Country Status (4)

Country Link
US (1) US20200068652A1 (zh)
EP (1) EP3609106A4 (zh)
CN (1) CN108809542B (zh)
WO (1) WO2018202190A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020236416A1 (en) * 2019-05-22 2020-11-26 Qualcomm Incorporated Methods to reduce radio link control retransmission
EP3944647A4 (en) * 2019-03-20 2022-05-18 Datang Mobile Communications Equipment Co., Ltd. INFORMATION PROCESSING METHOD, APPARATUS AND DEVICE, AND COMPUTER READABLE STORAGE MEDIA
TWI807527B (zh) * 2020-12-18 2023-07-01 聯發科技股份有限公司 降低多分支傳輸中封包延遲的方法和裝置

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3596999B1 (en) * 2017-03-17 2024-02-07 Apple Inc. Re-transmission of pdcp pdus by centralized nodes of a ran architecture
JP6935509B2 (ja) * 2017-04-28 2021-09-15 オッポ広東移動通信有限公司Ｇｕａｎｇｄｏｎｇ Ｏｐｐｏ Ｍｏｂｉｌｅ Ｔｅｌｅｃｏｍｍｕｎｉｃａｔｉｏｎｓ Ｃｏｒｐ．， Ｌｔｄ． 無線通信方法及び装置
KR102384282B1 (ko) * 2017-06-09 2022-04-07 삼성전자주식회사 무선 통신 시스템에서 혼잡을 제어하기 위한 장치 및 방법
CN112237026A (zh) * 2018-07-10 2021-01-15 三星电子株式会社 数据链路层中反馈机制的优化方法和系统
CN112399468B (zh) * 2019-08-14 2022-02-15 大唐移动通信设备有限公司 一种数据传输方法及接收设备
CN112752305B (zh) * 2019-10-29 2023-03-31 中国移动通信有限公司研究院 流量控制方法、装置、相关设备及存储介质
CN112996053B (zh) * 2019-12-16 2023-04-18 成都鼎桥通信技术有限公司 语音数据包的重排序方法、装置及设备
WO2021217602A1 (zh) * 2020-04-30 2021-11-04 华为技术有限公司 处理数据包的方法和通信装置
CN115516912A (zh) * 2020-07-08 2022-12-23 Oppo广东移动通信有限公司 重组定时器的启动方法、配置方法、装置、设备及介质
US11696360B2 (en) * 2020-07-16 2023-07-04 FG Innovation Company Limited Method and user equipment for controlling discontinuous reception behavior on multiple radio interfaces
CN115088383A (zh) * 2021-01-13 2022-09-20 北京小米移动软件有限公司 一种数据传输方法及装置
US11533267B2 (en) * 2021-01-21 2022-12-20 Mellanox Technologies, Ltd. Out-of-order packet processing
US11387945B1 (en) * 2021-03-30 2022-07-12 Qualcomm Incorporated Multiple timers for effective reordering
CN113315608A (zh) * 2021-04-30 2021-08-27 上海微波技术研究所（中国电子科技集团公司第五十研究所） 一种动态确定重传pdu的方法、系统、介质及其通信系统
CN113507725A (zh) * 2021-07-14 2021-10-15 Oppo广东移动通信有限公司 分离承载模式下的数据传输方法、装置以及终端设备
CN115842703A (zh) * 2021-08-06 2023-03-24 华为技术有限公司 一种数据传输的方法及通信装置
CN115996424A (zh) * 2021-10-19 2023-04-21 维沃移动通信有限公司 数据丢弃方法、装置、终端及网络侧设备
CN117412285A (zh) * 2022-07-06 2024-01-16 华为技术有限公司 数据量指示方法、数据递交方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105376801A (zh) * 2014-08-25 2016-03-02 中兴通讯股份有限公司 一种上行数据传输的方法及终端
CN105580422A (zh) * 2013-07-24 2016-05-11 松下电器（美国）知识产权公司 小小区部署中的高效抛弃机制
CN106027211A (zh) * 2007-09-18 2016-10-12 Lg电子株式会社 在多层结构中确保QoS的方法

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8855572B2 (en) * 2004-06-16 2014-10-07 Qualcomm Incorporated Method and apparatus for link control in wireless communications
WO2008126806A1 (ja) * 2007-04-06 2008-10-23 Ntt Docomo, Inc. 再送要求送信方法及び受信側装置
CN101965705B (zh) * 2007-10-01 2015-05-06 交互数字专利控股公司 用于pdcp丢弃的方法和装置
US9008004B2 (en) * 2008-02-01 2015-04-14 Lg Electronics Inc. Method for sending RLC PDU and allocating radio resource in mobile communications system and RLC entity of mobile communications
EP2582076A4 (en) * 2010-06-09 2015-10-28 Samsung Electronics Co Ltd MOBILE COMMUNICATION SYSTEM AND PACKAGE CONTROL METHOD IN THIS MOBILE COMMUNICATION SYSTEM
CN101883390A (zh) * 2010-06-25 2010-11-10 京信通信系统（中国）有限公司 一种无线链路控制层的sdu管理方法及其系统
US8576709B2 (en) * 2011-05-25 2013-11-05 Futurewei Technologies, Inc. System and method for monitoring dropped packets
PL2761802T3 (pl) * 2011-09-30 2020-09-07 Nokia Solutions And Networks Oy Przerwania w komunikacji bezprzewodowej
CN103179597B (zh) * 2011-12-21 2016-03-09 华为技术有限公司 一种无线保真技术的处理方法和用户设备
CN102790998B (zh) * 2012-06-19 2015-02-18 大唐移动通信设备有限公司 一种网络侧装置及其缓存am业务数据的方法
ES2769858T3 (es) * 2013-04-01 2020-06-29 Innovative Sonic Corp Método y aparato para añadir células de servicio en un sistema de comunicación inalámbrica
CN104812000A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 一种实现数据传输的方法及装置
US10028170B2 (en) * 2014-02-06 2018-07-17 Lg Electronics Inc. Method for processing a packet data convergence protocol service data unit at a user equipment in a dual connectivity system and device therefor
KR102190444B1 (ko) * 2014-02-21 2020-12-11 삼성전자주식회사 무선 통신 시스템에서 데이터 처리 시스템 및 방법
WO2015133767A1 (en) * 2014-03-02 2015-09-11 Lg Electronics Inc. Method for reordering a packet data convergence protocol packet data unit at a user equipment in a dual connectivity system and device therefor
EP3122146A1 (en) * 2014-03-20 2017-01-25 Kyocera Corporation Secondary base station, mobile station, communication control method, and master base station
WO2015163593A1 (en) * 2014-04-22 2015-10-29 Lg Electronics Inc. Method for processing received pdcp pdus for d2d communication system and device therefor
CN105007137B (zh) * 2014-04-23 2018-10-23 电信科学技术研究院 一种rlc层的数据包处理方法和rlc实体
US20170041818A1 (en) * 2014-04-25 2017-02-09 Lg Electronics Inc. Method for a configuration error management for a sidelink radio bearer and device therefor
WO2016072039A1 (ja) * 2014-11-07 2016-05-12 日本電気株式会社 無線通信システム、基地局、通信方法
US10341466B2 (en) * 2014-11-14 2019-07-02 Qualcomm Incorporated Evolved data compression scheme signaling
US10355828B2 (en) * 2015-03-02 2019-07-16 Qualcomm Incorporated Fast radio link control error recovery with low latency transmissions
CN106068018B (zh) * 2015-04-24 2021-07-13 三星电子株式会社 在从中断场景重新开始期间进行吞吐量恢复的方法和设备
KR102385719B1 (ko) * 2016-08-09 2022-04-12 삼성전자주식회사 무선통신 시스템에서 사용자 평면 동작을 관리하기 위한 방법 및 장치
CN110505656B (zh) * 2016-09-30 2020-07-24 华为技术有限公司 数据处理方法、装置及系统
CN108617029B (zh) * 2016-12-30 2023-05-12 夏普株式会社 无线承载配置方法、及相应的ue和基站
WO2018131956A1 (en) * 2017-01-16 2018-07-19 Samsung Electronics Co., Ltd. Method and apparatus for communication in wireless mobile communication system
MX2019009533A (es) * 2017-02-13 2019-09-16 Ericsson Telefon Ab L M Tecnica para monitorear una comunicacion por radio.
CN116527213A (zh) * 2017-03-31 2023-08-01 三星电子株式会社 无线通信系统中的装置及其缓冲器控制方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106027211A (zh) * 2007-09-18 2016-10-12 Lg电子株式会社 在多层结构中确保QoS的方法
CN105580422A (zh) * 2013-07-24 2016-05-11 松下电器（美国）知识产权公司 小小区部署中的高效抛弃机制
CN105376801A (zh) * 2014-08-25 2016-03-02 中兴通讯股份有限公司 一种上行数据传输的方法及终端

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification (Release 12)", 3GPP TS 36.322 V12.4.0, 1 June 2016 (2016-06-01), XP055545076 *
See also references of EP3609106A4

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3944647A4 (en) * 2019-03-20 2022-05-18 Datang Mobile Communications Equipment Co., Ltd. INFORMATION PROCESSING METHOD, APPARATUS AND DEVICE, AND COMPUTER READABLE STORAGE MEDIA
WO2020236416A1 (en) * 2019-05-22 2020-11-26 Qualcomm Incorporated Methods to reduce radio link control retransmission
US10938520B2 (en) 2019-05-22 2021-03-02 Qualcomm Incorporated Methods to reduce radio link control retransmission
TWI807527B (zh) * 2020-12-18 2023-07-01 聯發科技股份有限公司 降低多分支傳輸中封包延遲的方法和裝置

Also Published As

Publication number Publication date
CN108809542A (zh) 2018-11-13
CN108809542B (zh) 2021-04-20
EP3609106A1 (en) 2020-02-12
EP3609106A4 (en) 2020-07-29
US20200068652A1 (en) 2020-02-27

Similar Documents

Publication Publication Date Title
WO2018202190A1 (zh) 一种数据传输的处理方法和装置
RU2709480C1 (ru) Эффективный механизм отбрасывания при развертывании небольших сот
JP6286588B2 (ja) ビデオアウェアの（ｖｉｄｅｏ ａｗａｒｅ）ハイブリッド自動再送要求のための方法および装置
JP6907444B2 (ja) データ伝送方法、通信デバイス、端末、および基地局
JP5281700B2 (ja) 無線装置とネットワーク間のデータユニットのシーケンスの送信のための無線通信方法
US20090149189A1 (en) Method and apparatus for supporting configuration and control of the rlc and pdcp sub-layers
JP5351329B2 (ja) 無線通信システムにおいて１対多サービスを受信する方法及び端末
WO2017201677A1 (zh) 数据传输的方法及装置
WO2014127515A1 (zh) 业务提供系统、方法、移动边缘应用服务器及支持节点
WO2015117537A1 (zh) 由辅基站和主基站执行的通信方法以及相应的基站
WO2015058336A1 (zh) 数据传输装置和方法
WO2014110810A1 (zh) 传输数据的方法、基站和用户设备
CN103179618B (zh) 一种基于LTE Femto系统中提高回程网络的QoS的方法
WO2016068308A1 (ja) ゲートウェイ装置及びゲートウェイ装置の制御方法
US20140086045A1 (en) Traffic flow establishment method and device and traffic flow modification method and device
WO2016015244A1 (zh) 多通信制式传输方法及装置
WO2013029521A1 (zh) 用于数据传输的方法、分流点设备、用户终端和系统
WO2013155709A1 (zh) 数据分流配置方法、基站系统和用户终端
WO2014166053A1 (zh) 一种通讯方法和终端
WO2015192317A1 (zh) 网络通信方法和装置
US20230224253A1 (en) Communication method and apparatus
US20240080729A1 (en) Communication Method and Apparatus
JP2021509779A (ja) データを再送信する方法及び機器
US20240031861A1 (en) Communication method and device
WO2014000611A1 (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: 18794399

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

Country of ref document: EP

Effective date: 20191108