WO2019024837A1 - 一种计数方法及通信装置 - Google Patents

一种计数方法及通信装置 Download PDF

Info

Publication number
WO2019024837A1
WO2019024837A1 PCT/CN2018/097740 CN2018097740W WO2019024837A1 WO 2019024837 A1 WO2019024837 A1 WO 2019024837A1 CN 2018097740 W CN2018097740 W CN 2018097740W WO 2019024837 A1 WO2019024837 A1 WO 2019024837A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol layer
data packet
retransmission
layer data
retransmitted
Prior art date
Application number
PCT/CN2018/097740
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 AU2018312020A priority Critical patent/AU2018312020C1/en
Priority to JP2020505461A priority patent/JP7065943B2/ja
Priority to RU2020108768A priority patent/RU2770619C2/ru
Priority to KR1020207004999A priority patent/KR102303573B1/ko
Priority to EP18841834.7A priority patent/EP3657716B1/en
Publication of WO2019024837A1 publication Critical patent/WO2019024837A1/zh
Priority to US16/779,190 priority patent/US11258545B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1816Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of the same, encoded, message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1874Buffer management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/188Time-out mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02Data link layer protocols

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a counting method and a communication device.
  • the radio link control (RLC) layer is responsible for automatic repeat request (ARQ), for each RLC protocol that needs to be retransmitted.
  • the RLC layer maintains a retransmission counter for recording the RLC PDU and the RLC corresponding to the PDU. The total number of times the segment of the PDU and the part of the RLC PDU have been retransmitted, and when the retransmission counter reaches a preset threshold, the radio link reestablishment is triggered.
  • the RLC layer of the transmitting end delivers the RLC PDU, the segment of the RLC PDU, or the part of the RLC PDU that needs to be retransmitted to the MAC layer of the transmitting end according to the request of the media access control (MAC) layer, and then The MAC layer immediately transmits to the receiving end, and the RLC layer locally deletes the RLC PDU, the segment of the RLC PDU, or the part of the RLC PDU that needs to be retransmitted.
  • MAC media access control
  • the RLC layer of the transmitting end does not wait for the request of the MAC layer of the transmitting end, but directly the RLC PDU and RLC that need to be retransmitted.
  • the segment of the PDU or the part of the RLC PDU is delivered to the MAC layer in advance, and the MAC layer performs the pre-processing operation including adding the MAC header to cache the MAC layer.
  • the MAC layer does not necessarily send immediately, but only when it is determined that it needs to be sent. send.
  • the radio link re-establishment may be erroneously triggered.
  • the present application provides a counting method and a communication device for improving the situation in which an error triggers wireless link reconstruction.
  • the application provides a counting method, including: determining to retransmit a first protocol layer data packet; if the retransmission is a first retransmission, setting the first protocol layer data packet to a positive weight Transmitting, re-initiating the retransmission counter associated with the first protocol layer data packet; if the retransmission is not the first retransmission and the first protocol layer data packet is not pending retransmission, the first protocol layer is The data packet is set to be retransmitted, the retransmission counter is updated or the value of the retransmission counter is kept unchanged; if the first protocol layer data packet is pending retransmission and the second protocol layer indicates the A protocol layer data packet has been sent, and the first protocol layer data packet is set to be not to be retransmitted.
  • the second protocol layer immediately sends the first protocol layer data packet, so the first protocol layer will send after the data packet is sent.
  • the second protocol layer may not immediately send the first protocol layer data packet, so if the first protocol layer sets the first protocol layer data packet to the second protocol layer, the status of the first protocol layer data packet is set to not wait. The retransmission may result in an error setting the state of the first protocol layer data packet.
  • the second protocol layer receives the first protocol.
  • the first protocol layer data packet is set to be not to be retransmitted, which avoids setting the state of the first protocol layer data packet erroneously, and ensures the correctness of the retransmission processing.
  • the method may be performed by a notification device, where the communication device may be a terminal, a chip of the terminal, a base station, a chip in the base station, a central unit (CU), a chip in the CU, and a distributed unit (DU). ) or chips in the DU, etc.
  • the communication device may be a terminal, a chip of the terminal, a base station, a chip in the base station, a central unit (CU), a chip in the CU, and a distributed unit (DU). ) or chips in the DU, etc.
  • CU and DU refer to the CU-DU architecture introduced in the distributed radio access network to reduce the deployment cost of the access network equipment, and divide the radio access network side of the distributed radio access network into CU and DU.
  • Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) protocol stacks are distributed in CU, Radio Link Control (RLC) and Medium Access Control (Medium Access Control).
  • the MAC protocol stack is distributed in the DU.
  • the CU and the DU also have other protocol stacks.
  • the RRC may be divided into the CU, the PDCP, the RLC, and the RRC.
  • the MAC protocol stack is divided into DUs.
  • the specific protocol stack division between other CUs and DUs refer to TR 38.801v14.0.0.
  • one CU can be connected to multiple DUs.
  • the first protocol layer data packet is set to be retransmitted to: save the first protocol layer data packet in a first protocol layer retransmission buffer; A protocol layer data packet is not to be retransmitted as: the first protocol layer retransmission buffer does not have the first protocol layer data packet; and the first protocol layer data packet is not set to be awaiting Retransmitting: deleting the first protocol layer data packet from the first protocol layer retransmission buffer; the first protocol layer data packet is pending retransmission to: the first protocol layer retransmission buffer The first protocol layer data packet is stored therein.
  • the method uses a first protocol layer retransmission buffer to record the state of the first protocol layer data packet, that is, when the first protocol layer retransmission buffer includes the first protocol layer data packet, the state of the first protocol layer data packet If the first protocol layer retransmission buffer does not include the first protocol layer data packet, the state of the first protocol layer data packet is not to be retransmitted, and the method is simple and easy to implement.
  • the second protocol layer indicates that the first protocol layer data packet has been sent: when the first protocol layer data packet is sent in an air interface, the second protocol layer indicates the The first protocol layer data packet has been sent; or, after the second protocol layer passes the first protocol layer data packet to the physical layer, the second protocol layer indicates that the first protocol layer data packet has been sent Or after the hybrid automatic repeat request HARQ retransmission, the second protocol layer indicates that the first protocol layer data packet has been transmitted.
  • the method provides several implementation manners indicating that the first protocol layer data packet has been sent. In actual use, it can be flexibly selected according to actual needs.
  • the determining to retransmit the first protocol layer data packet is: receiving information indicating that the first protocol layer data packet transmission fails.
  • the first protocol layer data packet is delivered to the second protocol layer.
  • the application provides a counting method, including: determining to retransmit a first protocol layer data packet; and if the retransmission is a first retransmission, transmitting the first protocol layer data packet to a second protocol a layer, and initializing a retransmission counter associated with the first protocol layer data packet; if the retransmission is not a first retransmission and the second protocol layer indicates that the first protocol layer data packet is not to be transmitted or Transmitting, transmitting the first protocol layer data packet to the second protocol layer, and updating the retransmission counter or keeping the value of the retransmission counter unchanged.
  • the method when the second protocol layer indicates that the first protocol layer data packet is not being transmitted or is being transmitted, indicating that the second protocol layer does not have the first protocol layer data packet, so the first protocol layer may use the first protocol layer data
  • the packet is delivered to the second protocol layer, and the retransmission is counted.
  • the first protocol layer can count the retransmission according to the indication of the second protocol layer, and the method is simple and easy to implement.
  • the updating the retransmission counter is to increment the retransmission counter by one.
  • the updating the retransmission counter includes: adding 1 to the retransmission counter; And if the second protocol layer indicates segmentation of the first protocol layer data packet, adding the retransmission counter to N-1, where N is the number of segments of the first protocol layer data packet.
  • the first protocol layer data packet is a radio link control RLC protocol data unit PDU.
  • updating the retransmission counter or keeping the value of the retransmission counter unchanged including: if the first protocol layer data packet is the first data packet that occurs in one retransmission of the PDU, Adding the retransmission counter to 1; or, if the first protocol layer data packet is the Mth data packet that occurs in one retransmission of the PDU, keeping the value of the retransmission counter unchanged, M is An integer greater than one.
  • the first protocol layer data packet is a segment of an RLC PDU; Retransmitting the counter or keeping the value of the retransmission counter unchanged, including: if the first protocol layer data packet is the first data packet in the status report, the retransmission counter is incremented by one; Alternatively, if the first protocol layer data packet is the Lth data packet that appears in the PDU in the status report, the value of the retransmission counter is kept unchanged, and L is an integer greater than 1.
  • the first protocol layer data packet is a segment of the RLC PDU
  • the updating the retransmission counter or maintaining the value of the retransmission counter does not include: if the first protocol layer data packet is the first data packet that appears in the PDU in a transport block, The retransmission counter is incremented by one; or, if the first protocol layer data packet is the Kth data packet that appears in the PDU in a transport block, the value of the retransmission counter is kept unchanged, and K is an integer greater than 1. .
  • receiving indication information updating the retransmission counter or maintaining the retransmission counter The value is unchanged, including: updating the retransmission counter or keeping the value of the retransmission counter unchanged according to the indication information.
  • the retransmission counter is reset.
  • the retransmission counter is reset, which can reduce the number of times the wireless link fails to be triggered, which is beneficial to improving system performance.
  • the first protocol layer data packet is retransmitted in the primary cell. In this way, only the retransmission data packets on the more important primary cell are counted, and the retransmission data packets of the relatively less important secondary cells are not counted, which can save system overhead.
  • the present application provides a communication device having a function of implementing a communication device in the above method embodiment.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a processor, a memory, a bus, and a communication interface; the memory stores computer execution instructions, and the processor is connected to the memory through the bus, when the communication device is running, The processor executes the computer-executable instructions stored by the memory to cause the communication device to perform the counting method of any of the above aspects.
  • the communication device can be a terminal, a base station, a CU, a DU, or the like.
  • the communication device may also be a chip, such as a chip of a terminal, a chip within a base station, a chip within a CU, or a chip within a DU, the chip including a processing unit, optionally including storage Unit, the chip can be used to perform the counting method of any of the above first aspects.
  • a chip such as a chip of a terminal, a chip within a base station, a chip within a CU, or a chip within a DU, the chip including a processing unit, optionally including storage Unit, the chip can be used to perform the counting method of any of the above first aspects.
  • the present application provides a communication device having a function of implementing a communication device in the above method embodiment.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a processor, a memory, a bus, and a communication interface; the memory stores computer execution instructions, and the processor is connected to the memory through the bus, when the communication device is running, The processor executes the computer-executable instructions stored by the memory to cause the communication device to perform the counting method of any of the above second aspects.
  • the communication device can be a terminal, a base station, a CU, a DU, or the like.
  • the communication device may also be a chip, such as a chip of a terminal, a chip within a base station, a chip within a CU, or a chip within a DU, the chip including a processing unit, optionally including storage Unit, the chip can be used to perform the counting method of any of the above second aspects.
  • a chip such as a chip of a terminal, a chip within a base station, a chip within a CU, or a chip within a DU, the chip including a processing unit, optionally including storage Unit, the chip can be used to perform the counting method of any of the above second aspects.
  • the present application provides a computer storage medium storing computer software instructions for a terminal of the above third aspect, comprising a program designed to execute the terminal of the third aspect.
  • the present application provides a computer storage medium storing computer software instructions for a terminal of the above fourth aspect, comprising a program designed to execute the terminal of the fourth aspect.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions that are loadable by a processor to implement the flow in the counting method of any of the above first aspects.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions that are loadable by a processor to implement the flow in the counting method of any of the above second aspects.
  • FIG. 1 is a schematic diagram of a system architecture to which the present application applies;
  • 1A is a flow chart of a counting method provided by the present application.
  • FIG. 1B is a flowchart of another counting method provided by the present application.
  • FIG. 5 is a diagram showing an example of resetting a retransmission counter provided by the present application.
  • FIG. 6 is a diagram showing an example of retransmission counter update provided by the present application.
  • Figure 7 is a schematic diagram of a communication device provided by the present application.
  • FIG. 8 is a schematic diagram of another communication device provided by the present application.
  • FIG. 9 is a schematic diagram of another communication device provided by the present application.
  • a possible network architecture diagram applicable to the present application includes at least one terminal 10, which communicates with the base station 20 through a wireless interface.
  • the base station 20 communicates with the base station 20 through a wireless interface.
  • only one base station and one terminal device are shown in the figure.
  • a terminal is a device with wireless transceiver capability that can be deployed on land, indoors or outdoors, handheld or on-board; it can also be deployed on the water (such as ships); it can also be deployed in the air (such as airplanes, balloons, and Satellite, etc.).
  • the terminal may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transport safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • a base station is a device that accesses a terminal to a wireless network, including but not limited to: an evolved Node B (eNB), a radio network controller (RNC), and a Node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (BBU) a base station (g nodeB, gNB), a transmission point (tRP), a transmitting point (TP), a mobile switching center, etc., and may also include a wifi access point (AP), etc. .
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved node B, or home node B, HNB
  • BBU baseband unit
  • g nodeB, gNB gNodeB
  • tRP transmission point
  • the first protocol layer may be, for example, an RLC layer; and the second protocol layer may be, for example, a MAC layer.
  • the first protocol layer data packet for example, may be an RLC PDU, may be a fragment of an RLC PDU (RLC PDU segment), or may also be a part of a RLC PDU (portion of RLC PDU).
  • the first protocol layer retransmission buffer may also be referred to as an RLC retransmission buffer.
  • the RLC layer is responsible for ARQ retransmission. For each RLC PDU that needs to be retransmitted, the RLC layer maintains a retransmission counter for recording how many times the RLC PDU has been retransmitted.
  • the specific application is as follows: After the RLC layer of the transmitting end receives an RLC status report from the corresponding RLC layer of the receiving end, the RLC layer of the sending end finds that some RLC PDUs, segments of the RLC PDUs, or parts of the RLC PDUs are reported in the status report, and the transmitting end The RLC layer determines that the RLC PDU, the segment of the RLC PDU, or the portion of the RLC PDU needs to be retransmitted.
  • the RLC layer determines that an RLC PDU, a fragment of the RLC PDU, or a part of the RLC PDU needs to be retransmitted, the RLC layer puts the RLC PDU and the fragment of the RLC PDU that need to be retransmitted into the RLC retransmission buffer (retransmission buffer).
  • the RLC retransmission buffer is dedicated to temporarily storing RLC PDUs, segments of RLC PDUs, or portions of RLC PDUs that need to be retransmitted.
  • the RLC layer needs to initialize or update the RLC PDU, the segment of the RLC PDU or the retransmission counter corresponding to the part of the RLC PDU.
  • the initialization retransmission counter is 0, otherwise, the retransmission counter is incremented by one.
  • the RLC layer puts the RLC PDU, the segment of the RLC PDU, or the part of the RLC PDU that needs to be retransmitted into the RLC retransmission buffer, it is determined whether there is a segment of the same RLC PDU, RLC PDU, or The part of the RLC PDU is waiting for retransmission. In other words, whether the same RLC PDU, the fragment of the RLC PDU or the part of the RLC PDU exists in the RLC retransmission buffer, if any, the RLC layer will not need to be heavy.
  • the transmitted RLC PDU, the segment of the RLC PDU, or the portion of the RLC PDU is placed in the RLC retransmission buffer, and therefore, the RLC PDU, the segment of the RLC PDU, or the retransmission counter corresponding to the portion of the RLC PDU is not updated.
  • the RLC reports that the radio resource control (RRC) reaches the maximum number of retransmissions and is used to determine the radio link failure (RLF).
  • RRC radio resource control
  • the MAC layer of the terminal When the base station performs uplink scheduling on the terminal, the MAC layer of the terminal requests data from the RLC layer of the base station for uplink transmission according to the size of the uplink scheduling.
  • the priority of the retransmission PDU is higher than the priority of the initial transmission PDU, and the RLC layer of the terminal.
  • the RLC PDU, the fragment of the RLC PDU, or the part of the RLC PDU that needs to be retransmitted is first handed to the MAC layer of the terminal for uplink transmission, and the corresponding cached RLC PDU and RLC PDU of the RLC retransmission buffer are deleted.
  • the segment or part of the RLC PDU is the priority of the initial transmission PDU.
  • the RLC layer of the transmitting end does not wait for the request of the transmitting MAC layer, but directly the RLC PDU, the fragment of the RLC PDU or the RLC PDU that needs to be retransmitted.
  • the MAC layer Partially delivered to the MAC layer in advance, the MAC layer performs a pre-processing operation including adding a MAC header and buffers it in the MAC layer.
  • the MAC layer does not necessarily transmit immediately, but is sent only when it is determined that it needs to be sent.
  • the retransmission processing method in LTE and the counting method for retransmission are directly used, it will cause erroneous counting of retransmissions, thereby erroneously triggering RLC.
  • the second protocol layer immediately sends the first protocol layer data packet, and therefore, the first protocol layer is in the data packet.
  • the status of the first protocol layer data packet can be set to be not to be retransmitted immediately after transmission, for example, from local deletion, but in future communication, the first protocol layer sends the first protocol layer data packet to the second protocol layer.
  • the second protocol layer may not immediately send the first protocol layer data packet, so if the first protocol layer sends the first protocol layer data packet to the second protocol layer, the state of the first protocol layer data packet is set immediately. If it is not waiting for retransmission, it will cause the status of the first protocol layer packet to be incorrectly set.
  • the present application provides a counting method, where the first protocol layer data packet is set when the first protocol layer data packet is to be retransmitted and the second protocol layer indicates that the first protocol layer data packet has been sent. It is not waiting for retransmission, avoiding the error setting of the state of the first protocol layer data packet, and ensuring the correctness of the retransmission processing.
  • the present application further provides another counting method, when the retransmission is not the first retransmission and the second protocol layer indicates that the first protocol layer data packet is not being transmitted or is being transmitted, the retransmission counter is updated. Or keep the value of the retransmission counter unchanged.
  • the method when the second protocol layer indicates that the first protocol layer data packet is not being transmitted or is being transmitted, indicating that the second protocol layer does not have the first protocol layer data packet, so the first protocol layer may use the first protocol layer data
  • the packet is delivered to the second protocol layer, and the retransmission is counted.
  • the first protocol layer can count the retransmission according to the indication of the second protocol layer, thereby avoiding erroneously setting the state of the first protocol layer data packet. The correctness of the retransmission process is guaranteed. .
  • a counting method provided by the present application is applicable to the system architecture shown in FIG. 1, and includes the following steps:
  • Step 1 Determine to retransmit the first protocol layer data packet.
  • the first protocol layer data packet when receiving information indicating that the first protocol layer data packet transmission fails, it is determined that the first protocol layer data packet is retransmitted, for example, receiving an indication of an RLC PDU or an RLC PDU segment or an RLC PDU.
  • a partial transmission failure status report determines the retransmission of the RLC PDU, the segment of the RLC PDU, or the portion of the RLC PDU.
  • Step 2 Determine whether the first protocol layer data packet is the first retransmission. If yes, go to step 3. If not, go to step 4.
  • Step 3 Set the first protocol layer data packet to be retransmitted, initialize the retransmission counter associated with the first protocol layer data packet, and go to step 6.
  • the retransmission counter associated with the first protocol layer data packet is not set, so the retransmission counter needs to be initialized.
  • the retransmission counter is not set to mean that the retransmission counter does not exist, or the retransmission counter exists and the initial value is not set.
  • the first protocol layer data packet needs to be set to be retransmitted.
  • the first protocol layer retransmission buffer is set in the first protocol layer, and the data packets in the retransmission buffer are all data packets to be retransmitted, and therefore, the first protocol layer data packet is used.
  • Set to be re-transmitted that is, to save the first protocol layer data packet in the first protocol layer retransmission buffer, or to understand that the first protocol layer data packet is buffered to the first protocol layer retransmission buffer;
  • another implementation manner is: establishing a state table in the first protocol layer, and recording a retransmission status of each protocol layer packet that needs to be retransmitted, such as the status record is pending retransmission, not positive. Waiting for retransmission.
  • the retransmission buffer is set in the first protocol layer as an example, and other implementation manners also belong to the protection scope of the present application.
  • Step 4 Determine whether the data packet of the first protocol layer is to be retransmitted. If not, go to step 5. If yes, go to step 6.
  • the first protocol layer data packet When the first protocol layer data packet is stored in the first protocol layer retransmission buffer, the first protocol layer data packet is to be retransmitted; when the first protocol layer retransmission buffer is not stored in the first protocol When the layer packet is used, the first protocol layer packet is not waiting to be retransmitted.
  • Step 5 Set the first protocol layer data packet to be retransmitted, update the retransmission counter or keep the value of the retransmission counter unchanged, and go to step 6.
  • the retransmission is not the first retransmission
  • the first protocol layer data packet is not to be retransmitted, that is, the first protocol layer retransmission buffer does not have the first protocol layer data packet
  • the first protocol is The layer data packet is set to be retransmitted, that is, the first protocol layer data packet is saved in the first protocol layer retransmission buffer. Further, it is also necessary to update the retransmission counter or keep the value of the retransmission counter unchanged.
  • Step 6 Whether the second protocol layer indicates that the first protocol layer data packet has been sent. If yes, go to step 7. If no, go to step 6.
  • the second protocol layer indicates that the first protocol layer data packet has been sent; or, when the second protocol layer transmits the first protocol layer data packet to the physical layer, The second protocol layer indicates that the first protocol layer data packet has been sent; or after the hybrid automatic repeat-request (HARQ) retransmission, the second protocol layer indicates the first protocol layer, whether the result is a failure or a success.
  • the packet has been sent.
  • the second protocol layer indicates that the first protocol layer data packet has been sent.
  • Step 7 Set the first protocol layer data packet to not be retransmitted.
  • the first protocol layer data packet is set to be not to be retransmitted, that is, retransmitted from the first protocol layer.
  • the buffer deletes the first protocol layer packet.
  • the method further includes: transmitting the first protocol layer data packet to the second protocol layer.
  • the first protocol layer data packet is set only when the second protocol layer is received to indicate that the first protocol layer data packet has been sent.
  • the state of the first protocol layer data packet is incorrectly set, the correct retransmission and the retransmission counter are correctly counted, and the RLC is correctly triggered, thereby reducing the number of times the RLC is unnecessarily triggered. Can save costs.
  • FIG. 1B another counting method provided by the present application is applicable to the system architecture shown in FIG. 1, and includes the following steps:
  • Step 1 Determine to retransmit the first protocol layer data packet.
  • the first protocol layer data packet when receiving information indicating that the first protocol layer data packet transmission fails, it is determined that the first protocol layer data packet is retransmitted, for example, receiving an indication of an RLC PDU or an RLC PDU segment or an RLC PDU.
  • a partial transmission failure status report determines the retransmission of the RLC PDU, the segment of the RLC PDU, or the portion of the RLC PDU.
  • Step 2 Determine whether the first protocol layer data packet is the first retransmission, if yes, go to step 3; if no, go to step 4.
  • Step 3 Pass the first protocol layer data packet to the second protocol layer, and initialize a retransmission counter associated with the first protocol layer data packet.
  • the retransmission counter associated with the first protocol layer data packet is not set, so the retransmission counter needs to be initialized.
  • the retransmission counter is not set to mean that the retransmission counter does not exist, or the retransmission counter exists and the initial value is not set.
  • the second protocol layer has no first protocol layer data packet to be transmitted or being transmitted, and therefore the first protocol layer data packet is delivered to the second protocol layer.
  • Step 4 Whether the second protocol layer indicates that the first protocol layer data packet is being transmitted or being transmitted, if not, executing step 5, and if yes, ending the process.
  • Step 5 Pass the first protocol layer data packet to the second protocol layer, and update the retransmission counter or keep the value of the retransmission counter unchanged.
  • the second protocol layer When the second protocol layer indicates that the first protocol layer data packet is not being transmitted or is being transmitted, it indicates that there is no first protocol layer data packet being transmitted or being to be transmitted in the second protocol layer, therefore, the first protocol layer will The first protocol layer data packet is sent to the second protocol layer for retransmission, and then the retransmission counter needs to be updated or the value of the retransmission counter is kept unchanged.
  • the first protocol layer When the second protocol layer indicates that the first protocol layer data packet is to be transmitted or is transmitting, indicating that the second protocol layer is ready to start retransmission, or the first protocol layer data packet is already being retransmitted, the first protocol layer does not need to be
  • the first protocol layer data packet is repeatedly sent to the second protocol layer, and only the second protocol layer needs to continue to retransmit the first protocol layer data packet. At this time, it is not necessary to update the retransmission counter.
  • the first protocol layer can determine whether it is needed. Transmitting the first protocol layer data packet and updating the retransmission counter to the second protocol layer.
  • the first protocol layer data packet need not be recorded in the first protocol layer. The status (for example, whether it is waiting to be retransmitted, or not waiting to be retransmitted), so in the specific implementation, there is no need to maintain a retransmission buffer in the first protocol layer, or maintain a state table, thus saving more Resources.
  • the first protocol layer is the RLC layer
  • the second protocol layer is the MAC layer
  • the first protocol layer data packet is the RLC data packet to be retransmitted
  • the first protocol layer retransmission buffer is the RLC retransmission buffer. Description.
  • Solution 1 When the RLC layer counts the retransmission counter, each of the RLC retransmission buffers and/or the RLC PDUs, the segments of the RLC PDUs, or the RLC PDUs that are submitted to the MAC layer are counted a number of times.
  • the RLC layer when the initial transmission, the RLC layer sends an RLC PDU to the MAC layer, and the RLC status report received by the RLC layer indicates that the entire RLC PDU is lost, then the RLC layer is heavy. Pass the RLC PDU.
  • the RLC layer puts the entire RLC PDU into the RLC retransmission buffer and/or submits it to the MAC layer.
  • the retransmission counter is initialized, for example, initialized to 0, followed by Retransmit once, then add 1 until the preset threshold is reached, trigger the radio link failure RLC; or, initialize to a certain value, such as 10, then repeat each time after retransmission, until the retransmission counter is 0. , triggers RLC.
  • the RLC layer may be required to re-segment the RLC PDU according to the scheduling and the packet size, but the RLC layer does not update the retransmission counter.
  • segment 1 The third retransmission, since it is a PDU segment that needs to be retransmitted: segment 1, then a segment is placed in the RLC retransmission buffer and/or submitted to the MAC, so the retransmission counter is incremented by one.
  • Solution 2 When the RLC layer counts the retransmission counter, each time it is placed in the RLC retransmission buffer or the segment submitted to the MAC layer is counted, and after the MAC layer requests segmentation, the segment also needs to be counted.
  • the RLC layer when the initial transmission, the RLC layer sends an RLC PDU to the MAC layer, and the RLC status report received by the RLC layer indicates that the entire RLC PDU is lost, then the RLC layer Retransmit the RLC PDU.
  • the RLC layer puts the entire RLC PDU into the RLC retransmission buffer and/or delivers to the MAC layer, at which time the retransmission counter is initialized to zero. Then, when the actual transmission occurs, the MAC layer requests the RLC layer to segment the RLC PDU, for example, the segmentation is: segment 1, segment 2, segment 3, and then the RLC layer segments the segmented RLC PDU. Re-input into the RLC retransmission buffer and/or submit to the MAC layer. At this time, since there is one RLC PDU before the segmentation, there are 3 RLC PDU segments after segmentation. Therefore, the added value is 2, so the first After a retransmission, after re-segmentation, the retransmission counter is initialized to 0 plus 2.
  • the second retransmission because the MAC layer does not require re-segmentation of Segment 1 and Segment 3, so the retransmission counter no longer continues to update.
  • segment 1 The third retransmission, since it is a PDU segment that needs to be retransmitted: segment 1, then a segment is placed in the RLC retransmission buffer and/or submitted to the MAC, so the retransmission counter is incremented by one.
  • the third retransmission because the MAC layer does not require re-segmentation of segment 1, so the retransmission counter will not continue to update.
  • the above method for each PDU or PDU segment that needs to be retransmitted, first increments the retransmission counter by 1, and then if the MAC layer indicates to the RLC data packet (ie, the RLC PDU, the segment of the RLC PDU, or the part of the RLC PDU) For the segment, the retransmission counter is incremented by N-1, where N is the number of RLC packet segments.
  • Solution 3 When the RLC layer counts the retransmission counter, no matter how many segments are present, as long as they belong to the same PDU, after the first segment is counted, the subsequent segments are not counted.
  • the retransmission counter is incremented by one; if the RLC data packet to be retransmitted is the PDU once Retransmitting the Mth data packet that appears, keeps the value of the retransmission counter unchanged, and M is an integer greater than 1.
  • the one-time retransmission of the PDU means that the retransmission of the segments of all the PDUs that need to be retransmitted in one PDU constitutes one retransmission.
  • the status report 1 reports that the PDU segment to be retransmitted is: the PDU of the PDU1.
  • Status Report 2 reports that the PDU segment to be retransmitted is: Segment 2 of PDU1, Segment 3 of PDU2, and PDU of PDU1 in Status Report 1.
  • Segment 1, PDU1 segment 3 and PDU1 PDU segment 2 in status report 2 the retransmission of these three segments constitutes a retransmission, when retransmitting the three segments, only the first The retransmitted segment count, the subsequent retransmitted segments are not counted; likewise, segment 1 of PDU2 in status report 1 and segment 3 of PDU2 in status report 2, these two segments also constitute one Retransmission, when retransmitting these two segments, only the first retransmitted segment is counted, and the retransmission of the second segment is not counted.
  • the retransmission counter is one for each PDU. Therefore, in this example, each of PDU1 and PDU2 corresponds to one retransmission counter, and each retransmission counter is updated or maintained.
  • determining whether it is a retransmission of the PDU may also be determined according to whether a repeated segment occurs. For example, suppose the status report 1 reports that the PDU segment that needs to be retransmitted is: PDU segment of the PDU1. 1. Segment 3 of PDU1, Segment 1 of PDU2; Status Report 2 reports that the PDU segment to be retransmitted is: Segment 1 of PDU1, Segment 3 of PDU2, and PDU Segment 1 of PDU1 in Status Report 1. Segment 3 of PDU1 constitutes a retransmission of PDU1 once.
  • PDU segment 1 of PDU1 in status report 2 and PDU segment 1 of PDU1 in status report 1 are duplicated, PDU of PDU1 in status report 2
  • the PDU segment 1 of PDU1 and the segment 3 of PDU1 in segment 1 and status report 1 do not belong to one retransmission, so PDU segment 1 of PDU1 in status report 2 needs to be counted.
  • determining whether it is a retransmission of the PDU may also be determined according to whether a partially repeated segment occurs. For example, if the status report 1 reports that the PDU segment to be retransmitted is: PDU of the PDU1 Segment 1, segment 3 of PDU1, segment 1 of PDU2; status report 2 reports that the PDU segment that needs to be retransmitted is: segment 1-1 of segment 1 of PDU1, segment 3 of PDU2, where PDU1 is divided Segment 1-1 of segment 1 refers to the first segment after segment 1 of PDU1 is re-segmented, that is, part of segment 1 of PDU1, and PDU segment 1 of PDU1 in status report 1 Segment 3 of PDU1 constitutes a retransmission of PDU1 once, due to the partial repetition of PDU segment 1 of PDU segment 1 of PDU1 in Status Report 2 and PDU segment 1 of PDU1 in Status Report 1, status report 2 Segment 1-1 of PDU Segment 1 of PDU1 and Segment 3 of PDU
  • the RLC layer when the initial transmission, the RLC layer sends an RLC PDU to the MAC layer, and the RLC status report received by the RLC layer indicates that the entire RLC PDU is lost, then the RLC layer Retransmit the RLC PDU.
  • the RLC layer puts the entire RLC PDU into the RLC retransmission buffer and/or delivers to the MAC layer, at which time the retransmission counter is initialized to zero.
  • segment 1 and segment 3 since there are two discrete PDU segments that need to be retransmitted: segment 1 and segment 3, then two segments are placed in the RLC retransmission buffer and/or submitted to the MAC.
  • the retransmission counter only increments 1 for the first PDU segment (ie, PDU segment 1), and maintains the count for the second PDU segment (ie, PDU segment 3).
  • segment 1 The third retransmission, since it is a PDU segment that needs to be retransmitted: segment 1, then a segment is placed in the RLC retransmission buffer and/or submitted to the MAC, and the retransmission counter is incremented by one.
  • Solution 4 When the RLC counts the retransmission counter, no matter how many segments, as long as they belong to the same PDU and are in the same status report, they are counted only once until the next status report.
  • the retransmission counter is incremented by one; if the RLC data packet to be retransmitted is in a status report
  • the L data packet that appears in the same PDU keeps the value of the retransmission counter unchanged, and L is an integer greater than 1.
  • the PDU segments that need to be retransmitted are: PDU segment 1 of PDU1, segment 3 of PDU1, segment 5 of PDU1, segment 1 of PDU2, segment 3 of PDU2; status report 2 Report the PDU segments that need to be retransmitted as: segment 6 of PDU1, segment 8 of PDU1, segment 4 of PDU2, segment 6 of PDU2, then for status report 1, PDUs belonging to PDU1 with PDU1 Segment 1, segment 3 of PDU1, segment 5 of PDU1, wherein PDU segment 1 of PDU1 triggers a retransmission counter plus 1, segment 3 of PDU1, segment 5 of PDU1, so that the retransmission counter maintains a count;
  • the segment belonging to PDU2 has segment 1 of PDU2, segment 3 of PDU2, where PDU segment 1 of PDU2 triggers a retransmission counter plus 1, segment 3 of PDU2, so that the retransmission counter maintains a count.
  • the segment belonging to PDU1 has PDU segment 6 of PDU1, segment 8 of PDU1, wherein PDU segment 6 of PDU1 triggers a retransmission counter plus 1, segment 8 of PDU1, such that The retransmission counter maintains the count;
  • the segment belonging to PDU2 has segment 4 of PDU2 and segment 6 of PDU2, wherein PDU segment 4 of PDU2 triggers a retransmission counter plus 1, segment 6 of PDU2, so that the retransmission counter Maintain the count.
  • the foregoing description of the solution is only an example, and it is not necessarily determined whether the first packet in the same status report determines whether to update the retransmission counter, or whether there is at least one data of a PDU according to the status report.
  • the packet determines whether the retransmission counter is incremented by one. For example, when it is judged that there is at least one data packet of one PDU in a status report, the retransmission counter is incremented by 1, otherwise, the value of the retransmission counter is kept unchanged.
  • Solution 5 The RLC layer does not count when retransmitting the retransmitted PDU or PDU segment to the MAC layer, but notifies the MAC layer that the PDU or PDU segment is a retransmitted PDU or PDU segment, and the MAC layer is When the PDU or PDU segment is delivered to the physical layer transmission, the RLC layer is notified, which PDU or PDU segments are put into the same transport block or MAC PDU, the PDU or PDU segment belonging to the same PDU is put into the same transmission data. For a block or MAC PDU, the corresponding retransmission counter is incremented by one.
  • the above method can also be understood as: if the RLC data packet to be retransmitted is the first data packet of the PDU in the transport block, the retransmission counter is incremented by one; if the RLC data packet to be retransmitted is a transmission
  • the Kth packet appearing in the PDU in the block keeps the value of the retransmission counter unchanged, and K is an integer greater than 1.
  • Solution 6 receiving the indication information; updating the retransmission counter or keeping the value of the retransmission counter unchanged according to the indication information.
  • the specific manner of updating the retransmission counter or keeping the value of the retransmission counter unchanged may be one of the foregoing schemes 1 to 5, that is, in the scheme 6, according to the indication information, selecting a retransmission counter update manner .
  • the terminal may receive the indication information of the base station, and select a counting manner to update the retransmission counter according to the indication information of the base station.
  • the above describes several update or maintenance modes of the retransmission counter. In actual use, one or several of them can be selected according to requirements. For example, different PDUs can select different counting modes and different logical channels. Different counting methods may be selected, and the specific counting manner may be preset, or may be sent by the base station to notify the terminal.
  • the retransmission counter After retransmission by the RLC, if some PDU segment retransmission is successful and some PDU segments still fail, in the LTE counting method, the retransmission counter will continue to accumulate, that is, as long as there are retransmitted PDUs. If the segment retransmission fails, the retransmission counter will accumulate until the maximum number of retransmissions is exceeded, triggering radio link failure (RLF), but the counting method has a big problem, for example, when the channel quality temporarily deteriorates, resulting in When there are many PDU segments, the number of PDU segment retransmission failures will increase, which will cause the retransmission counter to easily reach the maximum number of retransmissions and trigger the RLF.
  • RLF radio link failure
  • the present application provides a retransmission counter reset method.
  • the retransmission counter is reset, that is, as long as there is one RLC data packet (RLC PDU, RLC PDU) If the retransmission is successful, the segment or the RLC PDU is successfully triggered, and the retransmission counter is triggered to reset, which will greatly reduce the retransmission counter to reach the maximum number of retransmissions, thereby optimizing system performance.
  • FIG. 5 an example of resetting a retransmission counter provided by the present application is shown.
  • the third retransmission it is found that the retransmitted PDU segment retransmission succeeds, and thus the retransmission counter is reset.
  • a retransmission counter when a retransmission counter is used, it does not consider whether a retransmission occurs in a primary cell (PCell) or a primary secondary cell (PSCell), that is, whether a primary cell has a PDU or a PDU segment needs to be retransmitted, Whether the secondary cell has PDU or PDU segment needs to be retransmitted, it will trigger the operation of updating, maintaining or resetting the retransmission counter.
  • the RLF is only for the primary cell, and the primary and secondary cells are damaged even if they are damaged. Therefore, the present application further provides a processing method for the retransmission counter, and the processing method can be applied to the foregoing counting method.
  • the MAC layer notifies the RLC layer whether the transport block is transmitted in the PCell or in the PSCell.
  • the RCL layer retransmits the counter for counting only when the transport block is transmitted on the PCell.
  • FIG. 6 an example of a retransmission counter update provided by the present application is provided, wherein the retransmission counter is updated only when there is a PDU segment retransmission on the PCell.
  • FIG. 7 is a schematic diagram of a communication device provided by the present application.
  • the communication device 700 may be the terminal or the base station shown in FIG. 1, or may be a chip in the terminal, a chip in the base station, or may be a CU, a chip in the CU, a chip in the DU or the DU, or the like.
  • the communication device can be used to perform the method illustrated in FIG. 1A or FIG. 1B, and to perform any of the counting methods of the above embodiments.
  • the communication device 700 includes at least one processor 71, at least one communication interface 74, and optionally a memory 73.
  • the processor 71 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of the present invention. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • the memory 73 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 73 is used to store application code for executing the solution of the present invention, and is controlled by the processor 71 for execution.
  • the processor 71 is configured to execute application code stored in the memory 73.
  • processor 71 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 700 can include multiple processors, such as processor 71 and processor 78 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the terminal in FIG. 1 may be the communication device shown in FIG. 7, and one or more software modules are stored in the memory of the communication device.
  • the communication device can implement the software module through the processor and the program code in the memory to implement the functions of the communication device in any of the embodiments of the present application.
  • the retransmission buffer used in the counting method of the present application may be implemented by the memory 73 in FIG. 7, or may be implemented by the memory in the processor 71 (and/or the processor 78), which is not limited herein.
  • the present application may divide a functional module into a communication device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 8 is a schematic structural diagram of a communication device for implementing counting involved in the above embodiment, and the device 800 includes a determining unit 801, an initializing unit 802.
  • a determining unit 801 configured to determine to retransmit the first protocol layer data packet
  • the initializing unit 802 is configured to: if the retransmission is the first retransmission, set the first protocol layer data packet to be retransmitted, and initialize a retransmission counter associated with the first protocol layer data packet;
  • the updating unit 803 is configured to: if the retransmission is not the first retransmission and the first protocol layer data packet is not to be retransmitted, set the first protocol layer data packet to be retransmitted, and update the Retransmitting the counter or keeping the value of the retransmission counter unchanged;
  • the updating unit 803 is further configured to: when the first protocol layer data packet is to be retransmitted and the second protocol layer indicates that the first protocol layer data packet has been sent, set the first protocol layer data packet It is not waiting for retransmission.
  • the updating unit 803 is specifically configured to: save the first protocol layer data packet in a first protocol layer retransmission buffer;
  • the first protocol layer data packet is not to be retransmitted as: the first protocol layer retransmission buffer does not have the first protocol layer data packet;
  • the updating unit 803 is specifically configured to: delete the first protocol layer data packet from the first protocol layer retransmission buffer;
  • the first protocol layer data packet is to be retransmitted as: the first protocol layer retransmission buffer stores the first protocol layer data packet.
  • the second protocol layer indicates that the first protocol layer data packet has been sent as:
  • the second protocol layer After the first protocol layer data packet is sent in an air interface, the second protocol layer indicates that the first protocol layer data packet has been sent.
  • the second protocol layer After the second protocol layer passes the first protocol layer data packet to the physical layer, the second protocol layer indicates that the first protocol layer data packet has been sent; or
  • the second protocol layer After the hybrid automatic repeat request HARQ retransmission, the second protocol layer indicates that the first protocol layer data packet has been sent.
  • the receiving unit 805 is configured to: receive information indicating that the first protocol layer data packet transmission fails.
  • the sending unit 804 is configured to: deliver the first protocol layer data packet to the second protocol layer.
  • the updating unit 803 is specifically configured to: add the retransmission counter to 1.
  • the updating unit 803 is specifically configured to: add the retransmission counter by one; if the second protocol layer indicates that the first protocol layer data packet is re-segmented, the retransmission is performed.
  • the counter adds N-1, N is the number of segments in which the first protocol layer data packet is re-segmented.
  • the first protocol layer data packet is a segment of a radio link control RLC protocol data unit PDU;
  • the updating unit 803 is specifically configured to: if the first protocol layer data packet is the first data packet that occurs in one retransmission of the PDU, add the retransmission counter to 1; or
  • the first protocol layer data packet is the Mth data packet that occurs in one retransmission of the PDU, the value of the retransmission counter is kept unchanged, and M is an integer greater than 1.
  • the first protocol layer data packet is a segment of an RLC PDU
  • the updating unit 803 is specifically configured to:
  • the retransmission counter is incremented by one; or,
  • the first protocol layer data packet is the Lth data packet of the PDU in the status report, the value of the retransmission counter is kept unchanged, and L is an integer greater than 1.
  • the updating unit 803 is specifically configured to:
  • the retransmission counter is incremented by one; or,
  • the value of the retransmission counter is kept unchanged, and K is an integer greater than 1.
  • the receiving unit 805 is configured to receive indication information.
  • the updating unit 803 is specifically configured to update the retransmission counter or keep the value of the retransmission counter unchanged according to the indication information.
  • the updating unit 803 is further configured to: if the first protocol layer data packet is successfully retransmitted, reset the retransmission counter.
  • the first protocol layer data packet is retransmitted in the primary cell.
  • the communications apparatus 800 includes a first protocol layer processing unit and a second protocol layer processing unit, where the first protocol layer processing unit is configured to implement the determining unit 801, the initializing unit 802, and the update.
  • the function of the unit 803, the sending unit 804, and the receiving unit 805, the second protocol layer processing unit is configured to indicate to the first protocol layer processing unit that the first protocol layer data packet has been transmitted. The specific way to achieve it can be determined according to actual needs.
  • the communication device may be the communication device in any of the foregoing method embodiments. All the related content of the steps in the foregoing method embodiments may be referred to the function description of the corresponding function module, and details are not described herein.
  • FIG. 9 shows a possible schematic diagram of a possible communication device for implementing counting in the above embodiment.
  • the device 900 includes a determining unit 901, and an initializing unit 902.
  • a determining unit 901 configured to determine to retransmit the first protocol layer data packet
  • the initializing unit 902 is configured to initialize a retransmission counter associated with the first protocol layer data packet if the retransmission is a first retransmission;
  • the updating unit 903 is configured to: if the retransmission is not the first retransmission and the second protocol layer indicates that the first protocol layer data packet is not being transmitted or being transmitted, updating the retransmission counter or the maintenance station The value of the retransmission counter is unchanged.
  • the updating unit 903 is specifically configured to:
  • the retransmission counter is incremented by one.
  • the updating unit 903 is specifically configured to:
  • the retransmission counter is added with N-1, where N is the number of segments re-segmented by the first protocol layer data packet.
  • the first protocol layer data packet is a segment of a radio link control RLC protocol data unit PDU;
  • the updating unit 903 is specifically configured to:
  • the retransmission counter is incremented by one; or,
  • the first protocol layer data packet is the Mth data packet that occurs in one retransmission of the PDU, the value of the retransmission counter is kept unchanged, and M is an integer greater than 1.
  • the first protocol layer data packet is a segment of an RLC PDU
  • the updating unit 903 is specifically configured to:
  • the retransmission counter is incremented by one; or,
  • the first protocol layer data packet is the Lth data packet of the PDU in the status report, the value of the retransmission counter is kept unchanged, and L is an integer greater than 1.
  • the updating unit 903 is specifically configured to:
  • the retransmission counter is incremented by one; or,
  • the value of the retransmission counter is kept unchanged, and K is an integer greater than 1.
  • the receiving unit 904 is configured to receive indication information.
  • the updating unit is specifically configured to update the retransmission counter or keep the value of the retransmission counter unchanged according to the indication information.
  • the updating unit 903 is further configured to:
  • the retransmission counter is reset.
  • the first protocol layer data packet is retransmitted in the primary cell.
  • the communications apparatus 900 includes a first protocol layer processing unit and a second protocol layer processing unit, where the first protocol layer processing unit is configured to implement the determining unit 901, the initializing unit 902, and the update.
  • the unit 903, and the function of the receiving unit 904, is configured to indicate to the first protocol layer processing unit that the first protocol layer data packet is not being transmitted or being transmitted. The specific way to achieve it can be determined according to actual needs.
  • the communication device may be the communication device in any of the foregoing method embodiments. All the related content of the steps in the foregoing method embodiments may be referred to the function description of the corresponding function module, and details are not described herein.
  • the communication device is presented in the form of dividing each functional module corresponding to each function, or the communication device is presented in a form that divides each functional module in an integrated manner.
  • a "module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above.
  • ASIC application-specific integrated circuit
  • the communication device 800 can take the form shown in FIG.
  • the determining unit 801, the initializing unit 802, the updating unit 803, the sending unit 804, and the receiving unit 805 in FIG. 8 may be implemented by the processor 71 (and/or the processor 78) and the memory 73 of FIG.
  • the determining unit 801, the initializing unit 802, the updating unit 803, the transmitting unit 804, and the receiving unit 805 may be executed by calling the application code stored in the memory 73 by the processor 71 (and/or the processor 78).
  • the determining unit 901, the initializing unit 902, the updating unit 903, and the receiving unit 904 in FIG. 9 may be implemented by the processor 71 (and/or the processor 78) and the memory 73 of FIG. 7, specifically,
  • the determining unit 901, the initializing unit 902, the updating unit 903, and the receiving unit 904 may be executed by calling the application code stored in the memory 73 by the processor 71 (and/or the processor 78), which is not limited in this application.
  • the present application also provides a computer storage medium for storing computer software instructions for use in the communication device illustrated in Figures 7-9 above, including program code for performing the above-described method embodiments.
  • the application also provides a computer program product.
  • the computer program product includes computer software instructions that are loadable by a processor to implement the methods of the above method embodiments.
  • embodiments of the present application can be provided as a method, apparatus (device), or computer program product.
  • the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects, which are collectively referred to herein as "module” or “system.”
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

本申请提供一种计数方法及通信装置。该方法包括:确定重传第一协议层数据包;若重传是第一次重传,将第一协议层数据包设为正待重传,初始化第一协议层数据包关联的重传计数器;若重传不是第一次重传且第一协议层数据包不是正待重传,将第一协议层数据包设为正待重传,更新重传计数器或保持重传计数器的值不变;若第一协议层数据包为正待重传且第二协议层指示第一协议层数据包已发送,将第一协议层数据包设为不是正待重传。由于只有在接收到第二协议层指示第一协议层数据包已发送时,才将第一协议层数据包设为不是正待重传,避免了错误地设置第一协议层数据包的状态,保证了重传计数的正确性,进而保证可正确触发无线链路重建。

Description

一种计数方法及通信装置
本申请要求在2017年8月2日提交中华人民共和国知识产权局、申请号为201710652768.0、发明名称为“一种计数方法及通信装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域,尤其涉及一种计数方法及通信装置。
背景技术
长期演进(long term evolution,LTE)中,根据协议36.322记载,无线链路控制(radio link control,RLC)层负责自动重传请求(automatic repeat request,ARQ),对于每一个需要重传的RLC协议数据单元(protocol data unit,PDU)、RLC PDU的分段(segment)、RLC PDU的部分(portion),RLC层针对一个PDU,维护一个重传计数器,用于记录该PDU对应的RLC PDU、RLC PDU的分段、RLC PDU的部分已经被重传的总次数,当重传计数器达到预设阈值时,触发无线链路重建。
在LTE中,发送端的RLC层根据媒体接入控制(media access control,MAC)层的请求,将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分递交给发送端的MAC层,然后MAC层立即发送至接收端,以及,RLC层将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分从本地删除。
在第五代(5th Generation,5G)通信中,为了加快处理速度,引入预处理的概念,发送端的RLC层并不等待发送端MAC层的请求,而是直接将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分提前递交到MAC层,由MAC层进行包括添加MAC包头的预处理操作后缓存在MAC层,MAC层并不一定会立即发送,而是在确定需要发送时才发送。
在引入预处理的情形下,若仍使用LTE中的重传计数方法,可能会错误的触发无线链路重建。
发明内容
本申请提供一种计数方法及通信装置,用以改善错误触发无线链路重建的情况。
第一方面,本申请提供一种计数方法,包括:确定重传第一协议层数据包;若所述重传是第一次重传,将所述第一协议层数据包设为正待重传,初始化所述第一协议层数据包关联的重传计数器;若所述重传不是第一次重传且所述第一协议层数据包不是正待重传,将所述第一协议层数据包设为正待重传,更新所述重传计数器或保持所述重传计数器的值不变;若所述第一协议层数据包为正待重传且第二协议层指示所述第一协议层数据包已发送,将所述第一协议层数据包设为不是正待重传。LTE中,第一协议层将第一协议层数据包发送至第二协议层后,第二协议层会立即将第一协议层数据包发送出去,因此,第一协议层在数据包发送之后会立即将第一协议层数据包的状态设置为不是正待重传,例如从本地删除,在未来通信中,第一协议层将第一协议层数据包发送至第二协议层后,第二协议层可能不会立即发送该第一协议层数据包,因此若第一协议层在将第一协议层数据包发送至第二协议层后立即将第一协议层数据包的状态设置为不是正待重传,则会导致错误设置第一协议层数据包的状态,本申请, 第一协议层将第一协议层数据包发送至第二协议层后,在接收到第二协议层指示第一协议层数据包已发送时,将第一协议层数据包设为不是正待重传,避免了错误地设置第一协议层数据包的状态,保证了重传处理的正确性。
可选地,该方法可由通知装置执行,该通信装置可以是终端、终端的芯片、基站、基站内的芯片、集中单元(central Unit,CU)、CU内的芯片、分布单元(Distributed Unit,DU)或DU内的芯片等。
CU和DU指的是,在分布式无线接入网络中,为了降低接入网设备部署成本,引入了CU-DU架构,将分布式无线接入网络的无线接入网侧分为CU和DU。无线资源控制(Radio Resource Control,RRC)和分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)协议栈分布在CU,无线链路层控制协议(Radio Link Control,RLC)和媒体访问控制(Medium Access Control,MAC)协议栈分布在DU,本申请实施例中CU和DU也存在其它协议栈的划分方式,比如根据网络的配置,CU和DU部署时,也可以把RRC划分在CU,PDCP、RLC、MAC协议栈划分在DU。具体其它的CU和DU间的协议栈划分方式可以参考TR 38.801v14.0.0。一般地,一个CU可与多个DU连接。
在一种可能的设计中,所述将所述第一协议层数据包设为正待重传为:在第一协议层重传缓存器中保存所述第一协议层数据包;所述第一协议层数据包不是正待重传为:所述第一协议层重传缓存器未存有所述第一协议层数据包;所述将所述第一协议层数据包设为不是正待重传为:从所述第一协议层重传缓存器删除所述第一协议层数据包;所述第一协议层数据包为正待重传为:所述第一协议层重传缓存器中存有所述第一协议层数据包。该方法,使用第一协议层重传缓存器来记录第一协议层数据包的状态,即当第一协议层重传缓存器包括第一协议层数据包,则第一协议层数据包的状态为正待重传;当当第一协议层重传缓存器不包括第一协议层数据包,则第一协议层数据包的状态为不是正待重传,该方法简单易实施。
在一种可能的设计中,所述第二协议层指示所述第一协议层数据包已发送为:当所述第一协议层数据包在空口发送后,所述第二协议层指示所述第一协议层数据包已发送;或者,当所述第二协议层将所述第一协议层数据包传递至物理层后,所述第二协议层指示所述第一协议层数据包已发送;或者当混合自动重传请求HARQ重传后,所述第二协议层指示所述第一协议层数据包已发送。该方法,给出了几种指示第一协议层数据包已发送的实现方式,实际使用中,可根据实际需要灵活选择。
在一种可能的设计中,所述确定重传第一协议层数据包为:接收指示所述第一协议层数据包传输失败的信息。
在一种可能的设计中,将所述第一协议层数据包传递至所述第二协议层。
第二方面,本申请提供一种计数方法,包括:确定重传第一协议层数据包;若所述重传是第一次重传,将所述第一协议层数据包传递至第二协议层,以及初始化所述第一协议层数据包关联的重传计数器;若所述重传不是第一次重传且所述第二协议层指示所述第一协议层数据包不是正待传输或者正在传输,将所述第一协议层数据包传递至第二协议层,以及更新所述重传计数器或保持所述重传计数器的值不变。该方法,当第二协议层指示第一协议层数据包不是正待传输或者正在传输时,表明第二协议层没有该第一协议层数据包,因此第一协议层可以将第一协议层数据包递交到第二协议 层,并对重传进行计数,该方法第一协议层可根据第二协议层的指示,对重传进行计数,方法简单易实现。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,所述更新所述重传计数器为:将所述重传计数器加1。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,所述更新所述重传计数器,包括:将所述重传计数器加1;若所述第二协议层指示对所述第一协议层数据包分段,则将所述重传计数器加N-1,N为所述第一协议层数据包的分段数量。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,所述第一协议层数据包是无线链路控制RLC协议数据单元PDU的分段;所述更新所述重传计数器或保持所述重传计数器的值不变,包括:若所述第一协议层数据包是所述PDU的一次重传出现的第一个数据包,则将所述重传计数器加1;或者,若所述第一协议层数据包是所述PDU的一次重传出现的第M个数据包,则保持所述重传计数器的值不变,M为大于1的整数。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,所述第一协议层数据包是RLC PDU的分段;所述更新所述重传计数器或保持所述重传计数器的值不变,包括:若第一协议层数据包是一个状态报告中所述PDU出现的第一个数据包,则将所述重传计数器加1;或者,若第一协议层数据包是一个状态报告中所述PDU出现的第L个数据包,则保持所述重传计数器的值不变,L为大于1的整数。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,所述第一协议层数据包是RLC PDU的分段;
所述更新所述重传计数器或保持所述重传计数器的值不变,包括:若第一协议层数据包是一个传输块中的所述PDU出现的第一个数据包,则将所述重传计数器加1;或者,若第一协议层数据包是一个传输块中的所述PDU出现的第K个数据包,则保持所述重传计数器的值不变,K为大于1的整数。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,接收指示信息;所述更新所述重传计数器或保持所述重传计数器的值不变,包括:根据所述指示信息,更新所述重传计数器或保持所述重传计数器的值不变。
以上给出了几种更新或保持重传计数器的值不变方法,可根据实际使用选择相应的计数方式。
结合第一方面,或结合第一方面的可能的设计,或结合第二方面,在另一种可能的设计中,若第一协议层数据包重传成功,则重置所述重传计数器。当第一协议层数据包重传成功,则重置重传计数器,可以减少触发无线链路失败的次数,有利于提升系统性能。
在以上任一种可能的设计,第一协议层数据包在主小区重传。如此,只对比较重要的主小区上的重传数据包进行计数,不对相对没那么重要的辅小区的重传数据包计数,可节约系统开销。
第三方面,本申请提供一种通信装置,该通信装置具有实现上述方法实施例中通信装置的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该 硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中,该通信装置包括:处理器、存储器、总线和通信接口;该存储器存储有计算机执行指令,该处理器与该存储器通过该总线连接,当该通信装置运行时,该处理器执行该存储器存储的该计算机执行指令,以使该通信装置执行如上述第一方面任意一项的计数方法。例如,该通信装置可以是终端、基站、CU或DU等。
在另一种可能的设计中,该通信装置还可以是芯片,如终端的芯片、基站内的芯片、CU内的芯片或DU内的芯片,该芯片包括处理单元,可选地,还包括存储单元,该芯片可用于执行如上述第一方面任意一项的计数方法。
第四方面,本申请提供一种通信装置,该通信装置具有实现上述方法实施例中通信装置的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中,该通信装置包括:处理器、存储器、总线和通信接口;该存储器存储有计算机执行指令,该处理器与该存储器通过该总线连接,当该通信装置运行时,该处理器执行该存储器存储的该计算机执行指令,以使该通信装置执行如上述第二方面任意一项的计数方法。例如,该通信装置可以是终端、基站、CU或DU等。
在另一种可能的设计中,该通信装置还可以是芯片,如终端的芯片、基站内的芯片、CU内的芯片或DU内的芯片,该芯片包括处理单元,可选地,还包括存储单元,该芯片可用于执行如上述第二方面任意一项的计数方法。
第五方面,本申请提供了一种计算机存储介质,储存有为上述第三方面的终端所用的计算机软件指令,其包含用于执行上述方面为第三方面的终端所设计的程序。
第六方面,本申请提供了一种计算机存储介质,储存有为上述第四方面的终端所用的计算机软件指令,其包含用于执行上述方面为第四方面的终端所设计的程序。
第七方面,本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令,该计算机软件指令可通过处理器进行加载来实现上述第一方面中任意一项的计数方法中的流程。
第八方面,本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令,该计算机软件指令可通过处理器进行加载来实现上述第二方面中任意一项的计数方法中的流程。
另外,第三方面至第八方面中任一种设计方式所带来的技术效果可参见第一方面或第二方面中不同设计方式所带来的技术效果,此处不再赘述。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请所适用的系统架构示意图;
图1A为本申请提供的一种计数方法流程图;
图1B为本申请提供的另一种计数方法流程图;
图2为本申请提供的更新重传计数器的一种示例;
图3为本申请提供的更新重传计数器的另一种示例;
图4为本申请提供的更新重传计数器的另一种示例;
图5为本申请提供的重传计数器的重置示例图;
图6为本申请提供的重传计数器更新示例图;
图7为本申请提供的通信装置示意图;
图8为本申请提供的另一通信装置示意图;
图9为本申请提供的另一通信装置示意图。
具体实施方式
下面将结合本申请中的附图,对本申请中的技术方案进行描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中,在本申请的描述中,除非另有说明,“多个”的含义是两个或两个以上。
本申请描述的架构以及业务场景是为了更加清楚的说明本申请的技术方案,并不构成对于本申请提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请提供的技术方案对于类似的技术问题,同样适用。
如图1所示,为本申请所适用的一种可能的网络架构示意图,包括至少一个终端10,通过无线接口与基站20通信,为清楚起见,图中只示出一个基站和一个终端设备。
终端,是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality,VR)终端、增强现实(augmented reality,AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
基站,是一种将终端接入到无线网络的设备,包括但不限于:演进型节点B(evolved Node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved nodeB,或home node B,HNB)、基带单元(baseband unit,BBU)、基站(g nodeB,gNB)、传输点(transmitting and receiving point,TRP)、发射点(transmitting point,TP)、移动交换中心等,此外,还可以包括wifi接入点(access point,AP)等。
本申请,第一协议层,例如可以是RLC层;第二协议层,例如可以是MAC层。第一协议层数据包,例如可以是RLC PDU,可以是RLC PDU的分段(RLC PDUsegment,),或者还可以是RLC PDU的部分(portion of RLC PDU)。第一协议层重传缓存器,也可以称为RLC重传缓存器。
在LTE中,RLC层负责ARQ重传,对于每一个需要重传的RLC PDU,RLC层维护一个重传计数器,用于记录该RLC PDU已经被重传了多少次,具体的应用如下所示:当发送端的RLC层从接收端的对应的RLC层接收到一个RLC状态报告后,发送端的RLC层发现该状态报告中报告某些RLC PDU、RLC PDU的分段或RLC PDU的部分丢失,则发送端的RLC层判断该RLC PDU、RLC PDU的分段或RLC PDU的部分需要重传。
当RLC层判断一个RLC PDU、RLC PDU的分段或RLC PDU的部分需要重传时,该RLC层会将需要重传的RLC PDU、RLC PDU的分段放入RLC重传缓存器(retransmission buffer),RLC重传缓存器是专门用来暂存需要进行重传的RLC PDU、 RLC PDU的分段或RLC PDU的部分。同时,RLC层需要初始化或更新该RLC PDU、RLC PDU的分段或RLC PDU的部分对应的重传计数器。
如果该RLC PDU、RLC PDU的分段或RLC PDU的部分是第一重传,那么初始化重传计数器为0,否则,重传计数器加1。
需要说明的是,在RLC层将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分放入RLC重传缓存器之前,会判断是否有相同的RLC PDU、RLC PDU的分段或RLC PDU的部分正在等待重传,换句话说,RLC重传缓存器中是否已经有相同的RLC PDU、RLC PDU的分段或RLC PDU的部分存在,如果有,那么RLC层不会将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分放入RLC重传缓存器,因此,也不会更新该RLC PDU、RLC PDU的分段或RLC PDU的部分对应的重传计数器。
当重传计数器达到最大重传次数阈值(maxRetxThreshold),RLC会报告无线资源控制(radio resource control,RRC)达到最大重传次数,用于判断发生无线链路失败(radio link failure,RLF)。
当基站对终端进行上行调度时,终端的MAC层会根据上行调度的大小向基站的RLC层请求数据用于上行传输,由于重传PDU优先级高于初传PDU的优先级,终端的RLC层会先将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分递给终端的MAC层用于上行传输,同时删除RLC重传缓存器中对应的缓存的RLC PDU、RLC PDU的分段或RLC PDU的部分。
在5G通信中,为了加快处理速度,引入预处理的概念,发送端的RLC层并不等待发送端MAC层的请求,而是直接将需要重传的RLC PDU、RLC PDU的分段或RLC PDU的部分提前递交到MAC层,由MAC层进行包括添加MAC包头的预处理操作后缓存在MAC层,MAC层并不一定会立即发送,而是在确定需要发送时才发送。
因此,在引入预处理的情况下,若直接使用LTE中的重传处理方法和对重传的计数方法,将会导致错误地对重传进行计数,进而错误地触发RLC。因为,在LTE中,第一协议层将第一协议层数据包发送至第二协议层后,第二协议层会立即将第一协议层数据包发送出去,因此,第一协议层在数据包发送之后可以立即将第一协议层数据包的状态设置为不是正待重传,例如从本地删除,但在未来通信中,第一协议层将第一协议层数据包发送至第二协议层后,第二协议层可能不会立即发送该第一协议层数据包,因此若第一协议层在将第一协议层数据包发送至第二协议层后立即将第一协议层数据包的状态设置为不是正待重传,则会导致错误设置第一协议层数据包的状态。
针对上述问题,本申请提供一种计数方法,当第一协议层数据包为正待重传且第二协议层指示第一协议层数据包已发送时,才将第一协议层数据包设为不是正待重传,避免了错误地设置第一协议层数据包的状态,保证了重传处理的正确性。
针对上述问题,本申请还提供另一种计数方法,当重传不是第一次重传且第二协议层指示第一协议层数据包不是正待传输或者正在传输,则更新所述重传计数器或保持重传计数器的值不变。该方法,当第二协议层指示第一协议层数据包不是正待传输或者正在传输时,表明第二协议层没有该第一协议层数据包,因此第一协议层可以将第一协议层数据包递交到第二协议层,并对重传进行计数,该方法第一协议层可根据第二协议层的指示,对重传进行计数,避免了错误地设置第一协议层数据包的状态, 保证了重传处理的正确性。。
下面对本申请给出的计数方法做具体说明。
如图1A所示,为本申请提供的一种计数方法,该方法适用于图1所示的系统架构,包括以下步骤:
步骤1、确定重传第一协议层数据包。
例如,作为一种实现,可以是在接收指示第一协议层数据包传输失败的信息时,确定重传第一协议层数据包,如,收到指示RLC PDU或RLC PDU分段或RLC PDU的部分传输失败的状态报告,则确定重传RLC PDU、RLC PDU的分段或RLC PDU的部分。
步骤2、判断该第一协议层数据包是否为第一次重传,若是,执行步骤3,若不是,执行步骤4。
步骤3、将第一协议层数据包设为正待重传,初始化第一协议层数据包关联的重传计数器,转到步骤6。
当第一协议层数据包为第一次重传时,第一协议层数据包关联的重传计数器未设置,因此需要初始化重传计数器。重传计数器未设置指的是重传计数器不存在,或者重传计数器存在并未设置初始值。
进一步地,还需要将第一协议层数据包设为正待重传。例如,一种实现方式为,在第一协议层设置第一协议层重传缓存器,重传缓存器中的数据包均为正待重传的数据包,因此,将第一协议层数据包设为正待重传,即为在第一协议层重传缓存器中保存第一协议层数据包,或者可以理解为,将第一协议层数据包缓存至第一协议层重传缓存器;再比如,另一种实现方式为,在第一协议层建立一张状态表,记录每个需要重传的第一协议层数据包的重传状态,如状态记录为正待重传、不是正待重传等。
为方便说明,后续将以第一协议层中设置重传缓存器为例进行说明,其它实现方式也属于本申请的保护范围。
步骤4、判断第一协议层数据包是否为正待重传,若不是,执行步骤5,若是,则执行步骤6。
当第一协议层重传缓存器中存储有该第一协议层数据包时,则第一协议层数据包是正待重传;当第一协议层重传缓存器中未存储有该第一协议层数据包时,则第一协议层数据包不是正待重传。
步骤5、将第一协议层数据包设为正待重传,更新重传计数器或保持重传计数器的值不变,转到步骤6。
该情形下,重传不是第一次重传,且第一协议层数据包不是正待重传,即第一协议层重传缓存器未存有第一协议层数据包,则将第一协议层数据包设为正待重传,即在第一协议层重传缓存器中保存第一协议层数据包。进一步地,还需要更新重传计数器或保持重传计数器的值不变。
步骤6、第二协议层是否指示第一协议层数据包已发送,若是,执行步骤7,若否,转到步骤6。
可选地,当第一协议层数据包在空口发送后,第二协议层指示第一协议层数据包已发送;或者,当第二协议层将第一协议层数据包传递至物理层后,第二协议层指示第一协议层数据包已发送;或者当混合自动重传请求(hybrid automatic repeat-request, HARQ)重传后,无论结果是失败还是成功,第二协议层指示第一协议层数据包已发送。或者,还可以在其他情形,第二协议层指示第一协议层数据包已发送。
步骤7、将第一协议层数据包设为不是正待重传。
第一协议层数据包为正待重传且第二协议层指示第一协议层数据包已发送,则将第一协议层数据包设为不是正待重传,即从第一协议层重传缓存器删除第一协议层数据包。
可选地,在上述步骤1之后还包括:将第一协议层数据包传递至第二协议层。
本申请,第一协议层将第一协议层数据包发送至第二协议层后,只有在接收到第二协议层指示第一协议层数据包已发送时,才将第一协议层数据包设为不是正待重传,避免了错误地设置第一协议层数据包的状态,保证了正确处理重传及正确对重传计数器计数,进而可正确触发RLC,减少了不必要地触发RLC的次数,可节约开销。
如图1B所示,为本申请提供的另一种计数方法,该方法适用于图1所示的系统架构,包括以下步骤:
步骤1、确定重传第一协议层数据包。
例如,作为一种实现,可以是在接收指示第一协议层数据包传输失败的信息时,确定重传第一协议层数据包,如,收到指示RLC PDU或RLC PDU分段或RLC PDU的部分传输失败的状态报告,则确定重传RLC PDU、RLC PDU的分段或RLC PDU的部分。
步骤2、判断第一协议层数据包是否为第一次重传,若是,执行步骤3;若否,执行步骤4。
步骤3、将第一协议层数据包传递至第二协议层,并初始化第一协议层数据包关联的重传计数器。
当第一协议层数据包为第一次重传时,第一协议层数据包关联的重传计数器未设置,因此需要初始化重传计数器。重传计数器未设置指的是重传计数器不存在,或者重传计数器存在并未设置初始值。以及,第一协议层数据包为第一次重传时,第二协议层没有正待传输或正在传输的第一协议层数据包,因此将第一协议层数据包传递至第二协议层。
步骤4、第二协议层是否指示第一协议层数据包为正待传输或者正在传输,若否,执行步骤5,若是,结束流程。
步骤5、将第一协议层数据包传递至第二协议层,并更新重传计数器或保持所述重传计数器的值不变。
当第二协议层指示第一协议层数据包不是正待传输或者正在传输,则表明第二协议层中没有正在传输或正待传输的第一协议层数据包,因此,第一协议层将该第一协议层数据包发送给第二协议层进行重传,然后还需要更新所述重传计数器或保持所述重传计数器的值不变。
当第二协议层指示第一协议层数据包是正待传输或者正在传输,则表明第二协议层中已经准备开始重传,或已经正在重传第一协议层数据包,则第一协议层无需重复向第二协议层发送该第一协议层数据包,只需要第二协议层继续重传该第一协议层数据包即可,此时,也无需更新重传计数器。
本申请提供的上述计数方法,只要第二协议层指示第一协议层数据包(即待重传 的数据包)是否已经是待重传或正在重传,则第一协议层即可确定是否需要向第二协议层发送第一协议层数据包及更新重传计数器,相较于图1A所示的方法,图1B所示的方法中,无需在第一协议层中记录第一协议层数据包的状态(如,是正待重传,或不是正待重传),因而在具体实现时,无需再第一协议层中维护一个重传缓存器、或维护一张状态表,因此,更为节约资源。
下面结合附图,介绍几种重传计数器的更新方法,该几种方法可应用于图1A或图1B所示的流程,具体说明了如何更新重传计数器或保持重传计数器的值不变。
下面以第一协议层为RLC层,第二协议层为MAC层,第一协议层数据包为待重传的RLC数据包,第一协议层重传缓存器为RLC重传缓存器为例进行说明。
方案一:RLC层对重传计数器计数时,每一个放入RLC重传缓存器和/或递交到MAC层的RLC PDU、RLC PDU的分段或RLC PDU的部分记一次数。
如图2所示,为更新重传计数器的一种示例,初传时,RLC层向MAC层发送一个RLC PDU,并且RLC层接收到的RLC状态报告,指示整个RLC PDU丢失,则RLC层重传RLC PDU。
第一次重传,由于是整个RLC PDU丢失,因此RLC层将整个RLC PDU放入RLC重传缓存器和/或递交到MAC层,此时重传计数器进行初始化,例如初始化为0,后面每重传一次,则加1,直到达到预设的阈值,则触发无线链路失败RLC;或者,初始化为某个值,如10,后续每重传一次,则减1,直到重传计数器为0,则触发RLC。
在MAC层实际将这个RLC PDU进行重传的时候,可以根据调度和数据包大小等情况,要求RLC层对该RLC PDU进行重分段,但RLC层并不更新重传计数器。
第二次重传,由于是两个不连续的需要重传的PDU分段:分段1和分段3,那么会有两个分段放入RLC重传缓存器和/或递交到MAC,因此重传计数器加2。
即针对每个需要重传的PDU分段,均加1,也可以理解为,有几个需要重传的PDU分段,则重传计算器加几。
第三次重传,由于是一个需要重传的PDU分段:分段1,那么会有一个分段放入RLC重传缓存器和/或递交到MAC,因此重传计数器加1。
方案二:RLC层对重传计数器计数时,每一个放入RLC重传缓存器或者递交到MAC层的分段记一次数,且MAC层要求分段之后,分段也需要计数。
如图3所示,为更新重传计数器的另一种示例,初传时,RLC层向MAC层发送一个RLC PDU,并且RLC层接收到的RLC状态报告,指示整个RLC PDU丢失,则RLC层重传RLC PDU。
第一次重传,由于是整个RLC PDU丢失,因此RLC层将整个RLC PDU放入RLC重传缓存器和/或递交到MAC层,此时重传计数器初始化为0。然后,MAC层在实际传输发生时,要求RLC层对RLC PDU进行分段,例如分段为:分段1,分段2,分段3,然后RLC层将分段后的RLC PDU的分段重新放入RLC重传缓存器和/或递交到MAC层,此时由于分段前有一个RLC PDU,分段后有3个RLC PDU的分段,因此,增加的数量值为2,所以第一次重传,重新分段后,重传计数器初始化为0再加2。
第二次重传,由于是两个不连续的需要重传的PDU分段:分段1和分段3,那么会有两个分段放入RLC重传缓存器和/或递交到MAC,因此重传计数器加2。
第二次重传,因为MAC层并没有要求对分段1和分段3进行重分段,因此重传 计数器不再继续更新。
第三次重传,由于是一个需要重传的PDU分段:分段1,那么会有一个分段放入RLC重传缓存器和/或递交到MAC,因此重传计数器加1。
第三次重传,因为MAC层并没有要求对分段1进行重分段,因此重传计数器不再继续更新。
上述方法,针对每个需要重传的PDU或PDU分段,首先将重传计数器加1,然后若MAC层指示对RLC数据包(即RLC PDU、RLC PDU的分段或RLC PDU的部分)分段,则将重传计数器加N-1,N为RLC数据包分段的数量。
方案三:RLC层对重传计数器计数时,无论有多少个分段,只要属于同一个PDU,第一个分段计数后,后面的分段都不计数。
也可以理解为,若待重传的PDU的分段是所述PDU的一次重传出现的第一个数据包,则将重传计数器加1;若待重传的RLC数据包是PDU的一次重传出现的第M个数据包,则保持重传计数器的值不变,M为大于1的整数。
其中,PDU的一次重传指的是,一个PDU中需要重传的所有PDU的分段的重传构成一次重传,例如,假设状态报告1报告需要重传的PDU分段为:PDU1的PDU分段1、PDU1的分段3、PDU2的分段1;状态报告2报告需要重传的PDU分段为:PDU1的分段2、PDU2的分段3,则状态报告1中的PDU1的PDU分段1、PDU1的分段3和状态报告2中的PDU1的PDU分段2,这三个分段的重传构成一次重传,对这三个分段重传时,只对第一个重传的分段计数,后续重传的分段不计数;同样地,状态报告1中的PDU2的分段1和状态报告2中的PDU2的分段3,这两个分段的也构成一次重传,对这两个分段重传时,只对第一个重传的分段计数,第二个分段的重传不计数。需要说明的是,重传计数器是每个PDU对应一个,因此,这个例子中,PDU1和PDU2分别各自对应一个重传计数器,分别对各自的重传计数器进行更新或维持。
在另一种实现方式中,判断是否是PDU的一次重传,也可以根据是否出现重复的分段来判断,例如,假设状态报告1报告需要重传的PDU分段为:PDU1的PDU分段1、PDU1的分段3、PDU2的分段1;状态报告2报告需要重传的PDU分段为:PDU1的分段1、PDU2的分段3,则状态报告1中PDU1的PDU分段1、PDU1的分段3构成一次对PDU1的重传,由于状态报告2中的PDU1的PDU分段1和状态报告1中PDU1的PDU分段1发生重复,则状态报告2中的PDU1的PDU分段1和状态报告1中PDU1的PDU分段1、PDU1的分段3不属于一次重传,因此需要对状态报告2中的PDU1的PDU分段1进行计数。
在另一种实现方式中,判断是否是PDU的一次重传,也可以根据是否出现部分重复的分段来判断,例如,假设状态报告1报告需要重传的PDU分段为:PDU1的PDU分段1、PDU1的分段3、PDU2的分段1;状态报告2报告需要重传的PDU分段为:PDU1的分段1的分段1-1、PDU2的分段3,其中PDU1的分段1的分段1-1指的是PDU1的分段1被重分段后的第一个分段,也就是PDU1的分段1的一部分,则状态报告1中PDU1的PDU分段1、PDU1的分段3构成一次对PDU1的重传,由于状态报告2中的PDU1的PDU分段1的分段1-1和状态报告1中PDU1的PDU分段1发生部分重复,则状态报告2中的PDU1的PDU分段1的分段1-1和状态报告1中PDU1的PDU分段1、PDU1的分段3不属于一次重传,因此需要对状态报告2中的PDU1 的PDU分段1的分段1-1进行计数。
如图4所示,为更新重传计数器的另一种示例,初传时,RLC层向MAC层发送一个RLC PDU,并且RLC层接收到的RLC状态报告,指示整个RLC PDU丢失,则RLC层重传RLC PDU。
第一次重传,由于是整个RLC PDU丢失,因此RLC层将整个RLC PDU放入RLC重传缓存器和/或递交到MAC层,此时重传计数器初始化为0。第二次重传,由于是两个不连续的需要重传的PDU分段:分段1和分段3,那么会有两个分段放入RLC重传缓存器和/或递交到MAC,重传计数器只针对第一个PDU分段加1(即PDU分段1),针对第二个PDU分段(即PDU分段3),维持计数。
第三次重传,由于是一个需要重传的PDU分段:分段1,那么会有一个分段放入RLC重传缓存器和/或递交到MAC,且重传计数器加1。
方案四:RLC对重传计数器计数时,无论有多少个分段,只要属于同一个PDU,且位于同一个状态报告,则只计数一次,直到下一个状态报告。
也可以理解为,若待重传的RLC数据包是一个状态报告中同一个PDU出现的第一个数据包,则将重传计数器加1;若待重传的RLC数据包是一个状态报告中同一个PDU出现的第L个数据包,则保持重传计数器的值不变,L为大于1的整数。
例如,假设状态报告1报告需要重传的PDU分段为:PDU1的PDU分段1、PDU1的分段3、PDU1的分段5、PDU2的分段1、PDU2的分段3;状态报告2报告需要重传的PDU分段为:PDU1的分段6、PDU1的分段8、PDU2的分段4、PDU2的分段6,则针对状态报告1,属于PDU1的分段有PDU1的PDU分段1、PDU1的分段3、PDU1的分段5,其中,PDU1的PDU分段1会触发重传计数器加1,PDU1的分段3、PDU1的分段5,使得重传计数器维持计数;属于PDU2的分段有PDU2的分段1、PDU2的分段3,其中,PDU2的PDU分段1会触发重传计数器加1,PDU2的分段3,使得重传计数器维持计数。同样地,针对状态报告2,属于PDU1的分段有PDU1的PDU分段6、PDU1的分段8,其中,PDU1的PDU分段6会触发重传计数器加1,PDU1的分段8,使得重传计数器维持计数;属于PDU2的分段有PDU2的分段4、PDU2的分段6,其中,PDU2的PDU分段4会触发重传计数器加1,PDU2的分段6,使得重传计数器维持计数。
需要说明的是,上述方案描述只是一种实例,也不一定根据是否同一个状态报告中是否第一个数据包判断是否更新重传计数器,也可以根据状态报告中是否有一个PDU的至少一个数据包,判断是否将重传计数器加1,例如,当判断一个状态报告中有一个PDU的至少一个数据包时,将重传计数器加1,否则,保持重传计数器的值不变。
方案五:RLC层向MAC层递交重传的PDU或PDU分段时不进行计数,但通知MAC层,这几个PDU或PDU分段是重传的PDU或PDU分段,MAC层在将这些PDU或PDU分段递交到物理层传输时,通知RLC层,哪些PDU或PDU分段被放入同一个传输块或MAC PDU,属于同一PDU的PDU或PDU分段,且被放入同一传数据块或MAC PDU时,对应的重传计数器加1。
上述方法,也可以理解为,若待重传的RLC数据包是一个传输块中的PDU出现的第一个数据包,则将重传计数器加1;若待重传的RLC数据包是一个传输块中的PDU 出现的第K个数据包,则保持重传计数器的值不变,K为大于1的整数。
方案六:接收指示信息;根据指示信息,更新重传计数器或保持重传计数器的值不变。
其中,更新重传计数器或保持重传计数器的值不变的具体方式可以是上述方案一至方案五中的一种,即在该方案六中,根据指示信息,选择一种重传计数器的更新方式。
例如,当上述计数方法由终端执行时,则终端可以接收基站的指示信息,根据基站的指示信息,选择一个计数方式更新重传计数器。
以上给出了重传计数器的几种更新或维持方式,在实际使用中,可根据需要选择其中的一种或几种进行使用,例如,不同的PDU可以选择不同的计数方式,不同的逻辑信道可以选择不同的计数方式,具体的计数方式可以是预设的,也可以是由基站发送信息通知终端。
当经过RLC的重传后,如果部分PDU分段重传成功,部分PDU分段还是失败的情况下,在LTE的计数方法中,重传计数器会继续累加,即只要还有重传的PDU分段重传失败,重传计数器会一直累加,直到超过最大重传次数,触发无线链路失败(radio link failure,RLF),但该计数方式存在较大问题,例如当信道质量暂时变差,导致PDU分段很多时,PDU分段重传失败的次数将会增多,这将导致重传计数器很容易达到最大重传次数而触发RLF,为此,本申请提供一种重传计数器的重置方法,在上述计数方法一~方法六的任一计数方法中,若待重传的RLC数据包重传成功,则重置重传计数器,即只要有一个RLC数据包(RLC PDU、RLC PDU的分段或RLC PDU的部分)重传成功,则触发将重传计数器重置,这将大大减少重传计数器达到最大重传次数,因而可优化系统性能。
参考图5,为本申请提供的重传计数器的重置示例图,在第三次重传时,发现前面有重传的PDU分段重传成功,因此将重传计数器重置。
目前,在LTE中,使用重传计数器时,并不考虑重传是发生主小区(PCell)还是发生在主辅小区(PSCell),即,不管是主小区有PDU或PDU分段需要重传,还是辅小区有PDU或PDU分段需要重传,都会触发去对重传计数器的更新、维持或重置等操作。但在实际应用中,考虑到RLF仅仅是针对主小区的,主辅小区即使都损坏了也没关系,因此,本申请还提供一种重传计数器的处理方法,该处理方法可应用于上述计数方法一~方法六,MAC层通知RLC层,传输块是在PCell传输还是在PSCell传输,仅当该传输块在PCell上传输时,RCL层才会重传计数器进行计数。例如,参考图6,为本申请提供的重传计数器更新示例图,其中,仅当PCell上有PDU分段重传时,才更新重传计数器。
图7所示为本申请提供的通信装置示意图。通信装置700可以是图1所示的终端或基站,或者还可以是终端内的芯片、基站内的芯片,或者还可以是CU、CU内的芯片、DU或DU内的芯片等。该通信装置可用于执行图1A或图1B所示的方法,以及执行上述实施例中任一计数方法。该通信装置700包括至少一个处理器71,至少一个通信接口74,可选地,还包括存储器73。
处理器71可以是一个通用中央处理器(central processing unit,CPU),微处理器,特定应用集成电路(application-specific integrated circuit,ASIC),或一个或多个用于 控制本发明方案程序执行的集成电路。
存储器73可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其他类型的动态存储设备,也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory,EEPROM)、只读光盘(compact disc read-only memory,CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器可以是独立存在,通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中,所述存储器73用于存储执行本发明方案的应用程序代码,并由处理器71来控制执行。所述处理器71用于执行所述存储器73中存储的应用程序代码。
在具体实现中,作为一种实施例,处理器71可以包括一个或多个CPU,例如图7中的CPU0和CPU1。
在具体实现中,作为一种实施例,通信装置700可以包括多个处理器,例如图7中的处理器71和处理器78。这些处理器中的每一个可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
示例性的,图1中的终端可以为图7所示的通信装置,通信装置的存储器中存储了一个或多个软件模块。通信装置可以通过处理器以及存储器中的程序代码来实现软件模块,实现本申请任一实施例中通信装置的功能。
本申请的计数方法中使用到的重传缓存器可以是由图7中的存储器73实现,也可以是由处理器71(和/或处理器78)中的存储器实现,本申请不做限定。
本申请可以根据上述方法示例对通信装置进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
比如,在采用对应各个功能划分各个功能模块的情况下,图8示出了上述实施例中所涉及的一种实现计数的通信装置可能的结构示意图,该装置800包括确定单元801,初始化单元802,更新单元803,可选地,还包括发送单元804,接收单元805。
确定单元801,用于确定重传第一协议层数据包;
初始化单元802,用于若所述重传是第一次重传,将所述第一协议层数据包设为正待重传,初始化所述第一协议层数据包关联的重传计数器;
更新单元803,用于若所述重传不是第一次重传且所述第一协议层数据包不是正待重传,将所述第一协议层数据包设为正待重传,更新所述重传计数器或保持所述重传计数器的值不变;
所述更新单元803,还用于若所述第一协议层数据包为正待重传且第二协议层指示所述第一协议层数据包已发送,将所述第一协议层数据包设为不是正待重传。
可选地,所述更新单元803,具体用于:在第一协议层重传缓存器中保存所述第 一协议层数据包;
所述第一协议层数据包不是正待重传为:所述第一协议层重传缓存器未存有所述第一协议层数据包;
所述更新单元803,具体用于:从所述第一协议层重传缓存器删除所述第一协议层数据包;
所述第一协议层数据包为正待重传为:所述第一协议层重传缓存器中存有所述第一协议层数据包。
可选地,所述第二协议层指示所述第一协议层数据包已发送为:
当所述第一协议层数据包在空口发送后,所述第二协议层指示所述第一协议层数据包已发送;或者,
当所述第二协议层将所述第一协议层数据包传递至物理层后,所述第二协议层指示所述第一协议层数据包已发送;或者
当混合自动重传请求HARQ重传后,所述第二协议层指示所述第一协议层数据包已发送。
可选地,所述接收单元805,用于:接收指示所述第一协议层数据包传输失败的信息。
可选地,所述发送单元804,用于:将所述第一协议层数据包传递至所述第二协议层。
可选地,所述更新单元803,具体用于:将所述重传计数器加1。
可选地,所述更新单元803,具体用于:将所述重传计数器加1;若所述第二协议层指示对所述第一协议层数据包重新分段,则将所述重传计数器加N-1,N为所述第一协议层数据包重新分段的段数。
可选地,所述第一协议层数据包是无线链路控制RLC协议数据单元PDU的分段;
所述更新单元803,具体用于:若所述第一协议层数据包是所述PDU的一次重传出现的第一个数据包,则将所述重传计数器加1;或者,
若所述第一协议层数据包是所述PDU的一次重传出现的第M个数据包,则保持所述重传计数器的值不变,M为大于1的整数。
可选地,所述第一协议层数据包是RLC PDU的分段;
所述更新单元803,具体用于:
若第一协议层数据包是一个状态报告中所述PDU的第一个数据包,则将所述重传计数器加1;或者,
若第一协议层数据包是一个状态报告中所述PDU的第L个数据包,则保持所述重传计数器的值不变,L为大于1的整数。
可选地,所述更新单元803,具体用于:
若第一协议层数据包是一个传输块中的第一个数据包,则将所述重传计数器加1;或者,
若第一协议层数据包是一个传输块中的第K个数据包,则保持所述重传计数器的值不变,K为大于1的整数。
可选地,所述接收单元805,用于接收指示信息;
所述更新单元803,具体用于根据所述指示信息,更新所述重传计数器或保持所 述重传计数器的值不变。
可选地,所述更新单元803,还用于:若第一协议层数据包重传成功,则重置所述重传计数器。
可选地,所述第一协议层数据包在主小区重传。
可选地,在另一种实现方式中,通信装置800包括第一协议层处理单元和第二协议层处理单元,其中,第一协议层处理单元用于实现确定单元801,初始化单元802,更新单元803,发送单元804,以及接收单元805的功能,第二协议层处理单元用于向第一协议层处理单元指示第一协议层数据包已发送。具体采用何种方式实现,可根据实际需要而定。
其中,该通信装置可以是上述任一方法实施例中的通信装置,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
比如,在采用对应各个功能划分各个功能模块的情况下,图9示出了上述实施例中所涉及的一种实现计数的通信装置可能的结构示意图,该装置900包括确定单元901,初始化单元902,更新单元903,可选地,还包括接收单元904。
确定单元901,用于确定重传第一协议层数据包;
初始化单元902,用于若所述重传是第一次重传,初始化所述第一协议层数据包关联的重传计数器;
更新单元903,用于若所述重传不是第一次重传且所述第二协议层指示所述第一协议层数据包不是正待传输或者正在传输,更新所述重传计数器或保持所述重传计数器的值不变。
可选地,所述更新单元903,具体用于:
将所述重传计数器加1。
可选地,所述更新单元903,具体用于:
将所述重传计数器加1;
若所述第二协议层指示对所述第一协议层数据包重新分段,则将所述重传计数器加N-1,N为所述第一协议层数据包重新分段的段数。
可选地,所述第一协议层数据包是无线链路控制RLC协议数据单元PDU的分段;
所述更新单元903,具体用于:
若所述第一协议层数据包是所述PDU的一次重传出现的第一个数据包,则将所述重传计数器加1;或者,
若所述第一协议层数据包是所述PDU的一次重传出现的第M个数据包,则保持所述重传计数器的值不变,M为大于1的整数。
可选地,所述第一协议层数据包是RLC PDU的分段;
所述更新单元903,具体用于:
若第一协议层数据包是一个状态报告中所述PDU的第一个数据包,则将所述重传计数器加1;或者,
若第一协议层数据包是一个状态报告中所述PDU的第L个数据包,则保持所述重传计数器的值不变,L为大于1的整数。
可选地,所述更新单元903,具体用于:
若第一协议层数据包是一个传输块中的第一个数据包,则将所述重传计数器加1; 或者,
若第一协议层数据包是一个传输块中的第K个数据包,则保持所述重传计数器的值不变,K为大于1的整数。
可选地,接收单元904,用于接收指示信息;
所述更新单元,具体用于根据所述指示信息,更新所述重传计数器或保持所述重传计数器的值不变。
可选地,所述更新单元903,还用于:
若第一协议层数据包重传成功,则重置所述重传计数器。
可选地,所述第一协议层数据包在主小区重传。
可选地,在另一种实现方式中,通信装置900包括第一协议层处理单元和第二协议层处理单元,其中,第一协议层处理单元用于实现确定单元901,初始化单元902,更新单元903,以及接收单元904的功能,第二协议层处理单元用于向第一协议层处理单元指示第一协议层数据包不是正待传输或者正在传输。具体采用何种方式实现,可根据实际需要而定。
其中,该通信装置可以是上述任一方法实施例中的通信装置,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在本实施例中,该通信装置以对应各个功能划分各个功能模块的形式来呈现,或者,该通信装置以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit,ASIC),电路,执行一个或多个软件或固件程序的处理器和存储器,集成逻辑电路,和/或其他可以提供上述功能的器件。在一个简单的实施例中,本领域的技术人员可以想到通信装置800可以采用图7所示的形式。比如,图8中的确定单元801、初始化单元802、更新单元803、发送单元804、接收单元805可以通过图7的处理器71(和/或处理器78)和存储器73来实现,具体的,确定单元801、初始化单元802、更新单元803、发送单元804、接收单元805可以通过由处理器71(和/或处理器78)来调用存储器73中存储的应用程序代码来执行,本申请对此不作任何限制;比如,图9中的确定单元901、初始化单元902、更新单元903、接收单元904可以通过图7的处理器71(和/或处理器78)和存储器73来实现,具体的,确定单元901、初始化单元902、更新单元903、接收单元904可以通过由处理器71(和/或处理器78)来调用存储器73中存储的应用程序代码来执行,本申请对此不作任何限制。
本申请还提供了一种计算机存储介质,用于储存为上述图7~图9所示的通信装置所用的计算机软件指令,其包含用于执行上述方法实施例所设计的程序代码。
本申请还提供了计算机程序产品。该计算机程序产品包括计算机软件指令,该计算机软件指令可通过处理器进行加载来实现上述方法实施例中的方法。
尽管在此结合各实施例对本发明进行了描述,然而,在实施所要求保护的本发明过程中,本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书,可理解并实现所述公开实施例的其他变化。在权利要求中,“包括”(comprising)一词不排除其他组成部分或步骤,“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施,但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白,本申请的实施例可提供为方法、装置(设备)、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式,这里将它们都统称为“模块”或“系统”。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机程序存储/分布在合适的介质中,与其它硬件一起提供或作为硬件的一部分,也可以采用其他分布形式,如通过Internet或其它有线或无线电信系统。
本申请是参照本申请的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述,显而易见的,在不脱离本发明的精神和范围的情况下,可对其进行各种修改和组合。相应地,本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明,且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。

Claims (33)

  1. 一种计数方法,其特征在于,包括:
    确定重传第一协议层数据包;
    当所述第一协议层数据包的重传是第一次重传时,初始化所述第一协议层数据包关联的重传计数器;
    当所述第一协议层数据包的重传不是第一次重传且所述第一协议层数据包不是正待重传时,更新所述重传计数器或保持所述重传计数器的值不变。
  2. 根据权利要求1所述的方法,其特征在于,还包括:
    接收状态报告,所述状态报告指示所述第一协议层数据包传输失败;
    所述确定重传第一协议层数据包,包括:
    根据所述状态报告确定重传所述第一协议层数据包。
  3. 根据权利要求2所述的方法,其特征在于,当所述状态报告还指示其它关联于所述重传计数器的第一协议层数据包传输失败时,所述重传计数器只更新一次。
  4. 根据权利要求2或3所述的方法,其特征在于,所述更新所述重传计数器或保持所述重传计数器的值不变,包括:
    当所述重传计数器未因为所述状态报告中其它传输失败的第一协议层数据包更新时,更新所述重传计数器;或者,
    当所述重传计数器因为所述状态报告中其它传输失败的第一协议层数据包进行了更新时,保持所述重传计数器的值不变。
  5. 根据权利要求1至4任一项所述的方法,其特征在于,所述初始化所述第一协议层数据包关联的重传计数器,包括:
    初始化所述重传计数器为0。
  6. 根据权利要求1至5任一项所述的方法,其特征在于,所述更新所述重传计数器,包括:
    将所述重传计数器加1。
  7. 根据权利要求1至6任一项所述的方法,其特征在于,所述第一协议层为无线链路控制RLC层。
  8. 根据权利要求1至7任一项所述的方法,其特征在于,还包括:
    将所述第一协议层数据包设为正待重传。
  9. 根据权利要求8所述的方法,其特征在于,
    所述将所述第一协议层数据包设为正待重传包括:在第一协议层重传缓存器中保存所述第一协议层数据包;
    所述第一协议层数据包不是正待重传包括:所述第一协议层重传缓存器未存有所述第一协议层数据包。
  10. 根据权利要求1至9任一项所述的方法,其特征在于,还包括:
    当所述第一协议层数据包为正待重传且第二协议层指示所述第一协议层数据包已发送,将所述第一协议层数据包设为不是正待重传。
  11. 根据权利要求10所述的方法,其特征在于,
    所述将所述第一协议层数据包设为不是正待重传包括:从所述第一协议层重传缓 存器删除所述第一协议层数据包;
    所述第一协议层数据包为正待重传包括:所述第一协议层重传缓存器中存有所述第一协议层数据包。
  12. 根据权利要求11所述的方法,其特征在于,所述第二协议层指示所述第一协议层数据包已发送包括:
    当所述第一协议层数据包在空口发送后,所述第二协议层指示所述第一协议层数据包已发送;或者,
    当所述第二协议层将所述第一协议层数据包传递至物理层后,所述第二协议层指示所述第一协议层数据包已发送;或者
    当混合自动重传请求HARQ重传后,所述第二协议层指示所述第一协议层数据包已发送。
  13. 根据权利要求1至12任一所述的方法,其特征在于,还包括:
    将所述第一协议层数据包传递至所述第二协议层。
  14. 根据权利要求1至13任一所述的方法,其特征在于,还包括:
    当第一协议层数据包重传成功时,重置所述重传计数器。
  15. 一种通信装置,其特征在于,包括:
    确定单元,用于确定重传第一协议层数据包;
    初始化单元,用于当所述第一协议层数据包的重传是第一次重传时,初始化所述第一协议层数据包关联的重传计数器;
    更新单元,用于当所述第一协议层数据包的重传不是第一次重传且所述第一协议层数据包不是正待重传时,更新所述重传计数器或保持所述重传计数器的值不变。
  16. 根据权利要求15所述的装置,其特征在于,还包括:
    接收单元,用于接收状态报告,所述状态报告指示所述第一协议层数据包传输失败;
    所述确定单元用于根据所述状态报告确定重传所述第一协议层数据包。
  17. 根据权利要求16所述的装置,其特征在于,当所述状态报告还指示其它关联于所述重传计数器的第一协议层数据包传输失败时,所述重传计数器只更新一次。
  18. 根据权利要求16或17所述的装置,其特征在于,所述更新单元用于:
    当所述重传计数器未因为所述状态报告中其它传输失败的第一协议层数据包更新时,更新所述重传计数器;或者,
    当所述重传计数器因为所述状态报告中其它传输失败的第一协议层数据包进行了更新时,保持所述重传计数器的值不变。
  19. 根据权利要求15至18任一项所述的装置,其特征在于,所述初始化单元初始化所述重传计数器,包括:
    初始化所述重传计数器为0。
  20. 根据权利要求15至19任一项所述的装置,其特征在于,所述更新单元更新所述重传计数器,包括:
    将所述重传计数器加1。
  21. 根据权利要求15至20任一项所述的装置,其特征在于,所述第一协议层为无线链路控制RLC层。
  22. 根据权利要求15至21任一项所述的装置,其特征在于,所述初始化单元和更新单元还用于:
    将所述第一协议层数据包设为正待重传。
  23. 根据权利要求22所述的装置,其特征在于,
    所述将所述第一协议层数据包设为正待重传包括:在第一协议层重传缓存器中保存所述第一协议层数据包;
    所述第一协议层数据包不是正待重传包括:所述第一协议层重传缓存器未存有所述第一协议层数据包。
  24. 根据权利要求15至23任一项所述的装置,其特征在于,所述更新单元还用于:
    当所述第一协议层数据包为正待重传且第二协议层指示所述第一协议层数据包已发送,将所述第一协议层数据包设为不是正待重传。
  25. 根据权利要求24所述的装置,其特征在于,
    所述将所述第一协议层数据包设为不是正待重传包括:从所述第一协议层重传缓存器删除所述第一协议层数据包;
    所述第一协议层数据包为正待重传包括:所述第一协议层重传缓存器中存有所述第一协议层数据包。
  26. 根据权利要求25所述的装置,其特征在于,所述第二协议层指示所述第一协议层数据包已发送包括:
    当所述第一协议层数据包在空口发送后,所述第二协议层指示所述第一协议层数据包已发送;或者,
    当所述第二协议层将所述第一协议层数据包传递至物理层后,所述第二协议层指示所述第一协议层数据包已发送;或者
    当混合自动重传请求HARQ重传后,所述第二协议层指示所述第一协议层数据包已发送。
  27. 根据权利要求15至26任一所述的装置,其特征在于,还包括:
    发送单元,用于将所述第一协议层数据包传递至所述第二协议层。
  28. 根据权利要求15至27任一所述的装置,其特征在于,所述更新单元还用于:
    当第一协议层数据包重传成功时,重置所述重传计数器。
  29. 一种通信装置,其特征在于,包括:处理器和存储器,所述处理器用于执行所述存储器存储的程序代码,以使该通信装置执行如权利要求1至14任一项所述的方法。
  30. 一种通信装置,其特征在于,与存储器相连,用于读取并执行所述存储器中存储的程序代码,以使该通信装置执行如权利要求1至14任一项所述的方法。
  31. 一种终端,其特征在于,包括如权利要求15至30任一项所述的装置。
  32. 一种计算机存储介质,其特征在于,存储程序代码,所述程序代码被处理器调用,用于执行如权利要求1至14任一项所述的方法。
  33. 一种计算机程序,其特征在于,包括计算机软件指令,所述计算机软件指令被处理器调用,用于执行如权利要求1至14任一项所述的方法。
PCT/CN2018/097740 2017-08-02 2018-07-30 一种计数方法及通信装置 WO2019024837A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
AU2018312020A AU2018312020C1 (en) 2017-08-02 2018-07-30 Counting method and communications apparatus
JP2020505461A JP7065943B2 (ja) 2017-08-02 2018-07-30 カウント方法および通信装置
RU2020108768A RU2770619C2 (ru) 2017-08-02 2018-07-30 Способ счета и устройство связи
KR1020207004999A KR102303573B1 (ko) 2017-08-02 2018-07-30 카운팅 방법 및 통신 장치
EP18841834.7A EP3657716B1 (en) 2017-08-02 2018-07-30 Counting method and communication device
US16/779,190 US11258545B2 (en) 2017-08-02 2020-01-31 Counting method and communications apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710652768.0A CN109547167B (zh) 2017-08-02 2017-08-02 一种计数方法及通信装置
CN201710652768.0 2017-08-02

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/779,190 Continuation US11258545B2 (en) 2017-08-02 2020-01-31 Counting method and communications apparatus

Publications (1)

Publication Number Publication Date
WO2019024837A1 true WO2019024837A1 (zh) 2019-02-07

Family

ID=65232266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097740 WO2019024837A1 (zh) 2017-08-02 2018-07-30 一种计数方法及通信装置

Country Status (8)

Country Link
US (1) US11258545B2 (zh)
EP (1) EP3657716B1 (zh)
JP (1) JP7065943B2 (zh)
KR (1) KR102303573B1 (zh)
CN (2) CN110401514B (zh)
AU (1) AU2018312020C1 (zh)
RU (1) RU2770619C2 (zh)
WO (1) WO2019024837A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7353365B2 (ja) * 2018-10-31 2023-09-29 オッポ広東移動通信有限公司 カウント方法、端末デバイス及び装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1667993A (zh) * 2004-03-12 2005-09-14 华为技术有限公司 一种控制状态报告发送频率的方法
CN101132260A (zh) * 2006-08-22 2008-02-27 中兴通讯股份有限公司 增强上行链路异步混合自动重传请求的重传控制方法
CN101374038A (zh) * 2007-08-20 2009-02-25 中兴通讯股份有限公司 Ofdm系统中基于harq技术的信号重传方法
US20090092131A1 (en) * 2006-10-11 2009-04-09 International Business Machines Corporation Method and Device for Rejecting Redundantly Retransmitted SIP Messages
CN101594219A (zh) * 2008-05-27 2009-12-02 中兴通讯股份有限公司 用于多输入多输出系统的混合自动重传请求方法及系统
CN102315924A (zh) * 2011-09-15 2012-01-11 武汉邮电科学研究院 一种基于下发bo计数的避免arq重传时lte空口资源浪费的方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR0309999A (pt) 2002-05-10 2005-02-15 Interdigital Tech Corp Priorização de dados de protocolo para retransmissão
US7584397B2 (en) * 2004-06-10 2009-09-01 Interdigital Technology Corporation Method and apparatus for dynamically adjusting data transmission parameters and controlling H-ARQ processes
TW200713895A (en) 2005-09-21 2007-04-01 Asustek Comp Inc Method and apparatus for improving transmission delay of status report in a wireless communications system
CN1992717B (zh) * 2005-12-30 2010-09-29 华为技术有限公司 无线接入网络架构及其实时业务无损迁移的实现方法
KR101563392B1 (ko) * 2007-12-10 2015-10-26 인터디지탈 패튼 홀딩스, 인크 무선 링크 제어 패킷 폐기 및 무선 링크 제어 재확립을 트리거하는 방법 및 장치
JP2010278588A (ja) 2009-05-27 2010-12-09 Fujitsu Ltd 基地局、再送実施状況通知方法、無線ネットワーク制御装置、およびデータ待ち合わせ方法
BR112015024982A2 (pt) * 2013-04-12 2017-07-18 Ericsson Telefon Ab L M equipamento de usuário e método no equipamento de usuário para monitoramento de um canal de controle de downlink
US20150382395A1 (en) * 2014-06-30 2015-12-31 Alcatel-Lucent Usa Inc. Method For Recovering From PDCP HFN De-Synchronization For VoLTE Call And Data Failure In RLC Layer
EP3202213B1 (en) * 2014-10-01 2019-12-04 Telefonaktiebolaget LM Ericsson (PUBL) Rlc delivery failure resolution
CN104486051B (zh) * 2014-12-09 2018-09-25 京信通信系统(中国)有限公司 一种数据重传方法及装置
WO2016178331A1 (ja) * 2015-05-01 2016-11-10 株式会社Nttドコモ 基地局及びユーザ装置
US20190334663A1 (en) * 2015-06-26 2019-10-31 Intel IP Corporation Transmission toggle uplink compensation
CN106375069B (zh) * 2015-07-22 2019-07-23 普天信息技术有限公司 数据重传方法及装置
US10484129B2 (en) * 2016-01-21 2019-11-19 Qualcomm Incorporated Protocol layer packet coding for transmitter/receiver buffer optimization

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1667993A (zh) * 2004-03-12 2005-09-14 华为技术有限公司 一种控制状态报告发送频率的方法
CN101132260A (zh) * 2006-08-22 2008-02-27 中兴通讯股份有限公司 增强上行链路异步混合自动重传请求的重传控制方法
US20090092131A1 (en) * 2006-10-11 2009-04-09 International Business Machines Corporation Method and Device for Rejecting Redundantly Retransmitted SIP Messages
CN101374038A (zh) * 2007-08-20 2009-02-25 中兴通讯股份有限公司 Ofdm系统中基于harq技术的信号重传方法
CN101594219A (zh) * 2008-05-27 2009-12-02 中兴通讯股份有限公司 用于多输入多输出系统的混合自动重传请求方法及系统
CN102315924A (zh) * 2011-09-15 2012-01-11 武汉邮电科学研究院 一种基于下发bo计数的避免arq重传时lte空口资源浪费的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3657716A4

Also Published As

Publication number Publication date
EP3657716B1 (en) 2022-08-31
CN110401514A (zh) 2019-11-01
AU2018312020A1 (en) 2020-02-20
AU2018312020B2 (en) 2021-04-15
RU2020108768A3 (zh) 2021-10-28
RU2020108768A (ru) 2021-08-30
JP2020529170A (ja) 2020-10-01
CN109547167B (zh) 2022-03-29
KR102303573B1 (ko) 2021-09-16
US20200169359A1 (en) 2020-05-28
KR20200027024A (ko) 2020-03-11
EP3657716A1 (en) 2020-05-27
EP3657716A4 (en) 2020-08-05
AU2018312020C1 (en) 2021-09-09
US11258545B2 (en) 2022-02-22
JP7065943B2 (ja) 2022-05-12
CN110401514B (zh) 2020-10-27
CN109547167A (zh) 2019-03-29
RU2770619C2 (ru) 2022-04-19

Similar Documents

Publication Publication Date Title
US11930554B2 (en) Radio link failure handling method and related product
BR112020013612A2 (pt) equipamento de usuário e método relacionado
US20190327033A1 (en) Segment retransmission method and apparatus
WO2020244645A1 (zh) 一种通信方法及装置
WO2013044982A1 (en) Interruptions in wireless communications
US10932159B2 (en) Data transmission method, data receiving device, and data sending device
WO2019018987A1 (zh) 处理无线链路失败的方法、终端设备和网络设备
WO2019024837A1 (zh) 一种计数方法及通信装置
WO2019061856A1 (en) PRETREATMENT IN WIRELESS UPLINK TRANSMISSIONS
US11316620B2 (en) Enhanced HARQ algorithm for large round trip delay links
WO2019095971A1 (zh) 一种通信方法及设备
WO2022134960A1 (zh) 通信方法、装置及设备
WO2022120744A1 (zh) 数据传输处理方法及相关装置
WO2012155419A1 (zh) 一种处理重传数据的方法及基站
CN113038632A (zh) Pdcp实体的控制方法以及pdcp实体
WO2021098638A1 (zh) 无线通信方法以及无线通信设备
WO2012155441A1 (zh) 一种处理重传数据的方法及基站
WO2018201905A1 (zh) 一种数据传输方法、终端以及基站
WO2021134106A2 (en) Methods and apparatus for efficient packet transmission

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020505461

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018312020

Country of ref document: AU

Date of ref document: 20180730

Kind code of ref document: A

Ref document number: 20207004999

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018841834

Country of ref document: EP

Effective date: 20200218