WO2013139249A1 - 数据包发送方法、模式转换方法及装置 - Google Patents

数据包发送方法、模式转换方法及装置 Download PDF

Info

Publication number
WO2013139249A1
WO2013139249A1 PCT/CN2013/072836 CN2013072836W WO2013139249A1 WO 2013139249 A1 WO2013139249 A1 WO 2013139249A1 CN 2013072836 W CN2013072836 W CN 2013072836W WO 2013139249 A1 WO2013139249 A1 WO 2013139249A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
mode
transmission
entity
receiving
Prior art date
Application number
PCT/CN2013/072836
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 华为技术有限公司
Publication of WO2013139249A1 publication Critical patent/WO2013139249A1/zh

Links

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/1867Arrangements specially adapted for the transmitter end

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a data packet sending method, a mode switching method, and a device. Background of the invention
  • the bearer is used to transmit the service data of the user equipment (UE), and the bearer includes the core according to the network through which the service data in the bearer passes.
  • Core Core Network, CN
  • RAN radio access network
  • the RAN bearer can adopt two transmission modes in the Radio Link Control (RLC) layer: Acknowledged Mode (AM) and Unacknowledged Mode (Un -acknowledged mode, UM).
  • RLC Radio Link Control
  • AM Acknowledged Mode
  • UM Unacknowledged Mode
  • the RLC layer uses the Automatic Repeat-ReQuest (ARQ) mechanism to transmit service data, and the receiving end successfully receives each data packet sent by the sender to indicate that the data packet is received.
  • ARQ Automatic Repeat-ReQuest
  • the transmitting end resends the corresponding data packet, and the mode is applied to the service transmission with lower delay requirement and higher reliability requirement;
  • the RLC layer is only responsible for transmitting and receiving data packets, and does not retransmit the transmitted data packets, nor does it provide feedback confirmation for the received data packets.
  • the UM mode is mainly applied to services with high latency requirements and low reliability requirements. Different types of data packets in the same service in the existing network are transmitted in the same mode. Different transmission modes cannot be used for different data packets of the same service.
  • part of the data of the same service is transmitted in the acknowledge mode and other packets are used. Confirm mode transfer.
  • the reliability and delay required for different data packets belonging to the same service are not consistent.
  • the AM mode transmission is adopted, the transmission reliability of the service data with lower reliability requirements in the service may be excessively guaranteed, and the transmission delay of the service data with higher delay requirement may be increased.
  • the UM mode transmission is used, the transmission reliability of the service data with higher reliability requirements may be reduced, and the transmission delay of the service data packet with lower delay requirement may be excessively guaranteed.
  • the embodiment of the invention provides a data packet sending method, a mode switching method and a device, which are used to solve the defect that the existing transmission mode can only transmit all data packets in the same transmission mode in the same bearer layer.
  • an embodiment of the present invention provides a data packet sending method, including:
  • the transmitting end transmitting entity receives the data packet from the upper layer entity
  • the transmitting end transmitting entity determines the transmission mode of the data packet according to the transmission mode indication information of the upper layer entity or the transmission mode indication information in the data packet; and the transmission mode indication information is set according to the transmission requirement of the data packet;
  • the transmitting end transmitting entity sends the data packet to the receiving end by using an acknowledge mode
  • the transmitting end transmitting entity sends the data packet to the receiving end in a non-acknowledgment mode.
  • an embodiment of the present invention provides a data packet sending apparatus, including:
  • a receiving module configured to receive, from an upper entity, a data packet to be sent
  • a mode determining module configured to indicate information or a location according to a transmission mode delivered by the upper layer entity Transmitting mode indication information in the data packet, determining a transmission mode of the data packet; the transmission mode indication information is set according to a transmission requirement of the data packet;
  • a confirmation transmission module configured to send the data packet to the receiving end by using an acknowledge mode if the transmission mode of the data packet is an acknowledge mode
  • the non-acknowledgment transmission module is configured to send the data packet to the receiving end in an unacknowledged mode if the transmission mode of the data packet is a non-acknowledgment mode.
  • an embodiment of the present invention provides a parameter configuration method, including:
  • the base station sends the hybrid transmission mode configuration parameter to the terminal, including the hybrid transmission mode identifier and the transmission parameter, where the hybrid transmission mode configuration parameter is used to indicate that the RLC entity corresponding to the RLC entity identifier in the terminal is according to the data packet in the RLC bearer layer.
  • the transmission requires transmission of the data packet in an acknowledgement mode or an unacknowledged mode;
  • the terminal configures the RLC entity corresponding to the received RLC entity identifier according to the hybrid transmission mode configuration parameter.
  • the embodiment of the present invention provides a parameter configuration apparatus, configured to send, to a terminal, a hybrid transmission mode configuration parameter, including a hybrid transmission mode identifier and a transmission parameter, where the hybrid transmission mode configuration parameter is used to indicate the terminal
  • a hybrid transmission mode configuration parameter including a hybrid transmission mode identifier and a transmission parameter, where the hybrid transmission mode configuration parameter is used to indicate the terminal
  • the RLC entity corresponding to the RLC entity identifier transmits the data packet in an acknowledge mode or a non-acknowledge mode according to the transmission requirement of the data packet in the RLC bearer layer.
  • the transmission mode of the data packet is first determined according to the transmission mode indication information of the data packet, and the transmission mode indicated by the transmission mode indication information is used. Send a packet to the receiver.
  • the transmission mode indication information of the data packet is set according to the transmission requirement of the data packet. For example, setting a data packet with high transmission reliability requirement or low transmission delay requirement to the acknowledge mode transmission, the transmission reliability requirement is low. Packets with higher transmission delay requirements are set to transmit in unacknowledged mode.
  • a mode conversion method includes:
  • the transmitting end transmitting entity determines that multiple consecutive data packets starting from the specified data packet are transmitted in an acknowledge mode
  • the transmitting end transmitting entity Before transmitting the designated data packet to the receiving end, the transmitting end transmitting entity sends a first transmission mode indication to the receiving end, where the first transmission mode indication is used to instruct the receiving end to start using the acknowledge mode transmission from the specified data packet;
  • the first transmission mode indicates that the previously adopted transmission mode is a non-acknowledgement mode, and the first transmission mode indication is further used to indicate that the receiving end converts from the non-acknowledgment mode to the acknowledge mode transmission from the specified data packet.
  • a continuous data packet after receiving the first transmission mode response fed back by the receiving end, the transmitting end transmitting entity adopts the acknowledge mode transmission; if the non-acknowledge mode is adopted before receiving the transmission mode indication, the unconfirmed mode is converted to Confirm mode.
  • an embodiment of the present invention provides a mode conversion apparatus, including:
  • a determining module configured to determine, before sending the data packet to the receiving end, that the plurality of consecutive data packets starting from the specified data packet are transmitted in an acknowledge mode
  • the indication module is configured to send, to the receiving end, a first transmission mode indication, where the first transmission mode indication is used to instruct the receiving end to use the acknowledge mode transmission from the specified data packet, if the specified data packet is sent to the receiving end, if The first transmission mode indication is further used to indicate that the receiving end converts from the non-acknowledgment mode to the acknowledge mode transmission from the specified data packet, when the transmission mode used before the sending the first transmission mode indication is a non-acknowledgement mode. a plurality of consecutive data packets; a conversion module, configured to transmit in an acknowledge mode after receiving the first transmission mode response fed back by the receiving end; if the non-acknowledge mode is adopted before receiving the transmission mode indication, the unconfirmed mode is adopted Convert to confirmation mode.
  • an embodiment of the present invention provides a mode conversion method, including:
  • the receiving end Receiving, by the receiving end, a first transmission mode indication sent by the transmitting end transmitting entity, where the first transmission mode indication is used to instruct the receiving end to start using the acknowledge mode transmission from the designated data packet; if the first transmission mode indication is sent before If the transmission mode adopted is non-confirmed mode, then the The first transmission mode indication is further configured to instruct the receiving end to transfer the specified data packet and the subsequent data packet of the specified data packet from the non-acknowledgment mode to the acknowledge mode;
  • the receiving end feeds back the first transmission mode response to the transmitting end
  • the receiving end starts to transmit in the acknowledge mode from the specified data packet, and if the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledgment mode, the receiving end The non-acknowledgment mode transitions to an acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet;
  • the receiving end If the data packet before the specified data packet has not been received, the receiving end starts a reordering event, after the reordering event is triggered, or before the reordering event is triggered, it is confirmed that the data packet before the specified data packet has been received, The receiving end transmits in the acknowledgment mode from the specified data packet, and if the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledge mode, the receiving end converts from the non-acknowledgment mode to the acknowledgment mode transmission from the specified data. Multiple consecutive packets starting with the packet.
  • an embodiment of the present invention provides a mode conversion apparatus, including:
  • a receiving module configured to receive a first transmission mode indication sent by the transmitting end transmitting entity, where the first transmission mode indication is used to indicate that the receiving end starts to adopt the acknowledge mode transmission from the specified data packet; if the first transmission mode is sent Instructing that the previously adopted transmission mode is a non-acknowledgement mode, the first transmission mode indication is further used to instruct the receiving end to convert the specified data packet and the subsequent data packet of the specified data packet from the non-acknowledgment mode to the acknowledge mode. ;
  • a response module configured to feed back a first transmission mode response to the sending end
  • a conversion module configured to: if the data packet before the specified data packet is received, use an acknowledge mode transmission from the specified data packet, if the transmission mode adopted before receiving the first transmission mode indication is a non-acknowledgment mode, Converting from a non-confirmed mode to an acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet;
  • the conversion module is further configured to: if the data packet before the specified data packet has not been received, the receiving end starts a reordering event, after the reordering event is triggered, or the reordering event is triggered Before confirming that the data packet before the specified data packet has been received, the receiving end starts to transmit in the acknowledge mode from the specified data packet, if the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledgment mode, The non-acknowledgment mode transitions to an acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet.
  • the mode conversion method and device in the process of transmitting a data packet, the transmitting end sends a first transmission mode indication to the receiving end, and instructs the receiving end to start transmitting multiple times from the specified data packet in the acknowledge mode.
  • a continuous data packet if the transmission mode adopted before the first transmission mode indication is a non-acknowledgement mode, instructing the receiving end to switch from the non-acknowledgment mode to the acknowledge mode to transmit a plurality of consecutive data starting from the specified data packet package. Therefore, this embodiment can use different modes to transmit different data packets.
  • an embodiment of the present invention provides a mode conversion method, including:
  • the transmitting end transmitting entity determines that the plurality of consecutive data packets starting from the specified data packet are transmitted in the unacknowledged mode
  • the transmitting end transmitting entity Before transmitting the designated data packet to the receiving end, the transmitting end transmitting entity sends a second transmission mode indication to the receiving end, where the second transmission mode indication is used to indicate that the receiving end starts to use the unacknowledged mode transmission from the designated data packet; Sending the second transmission mode indication before the transmission mode is an acknowledgment mode, where the second transmission mode indication is further used to indicate that the receiving end converts from the acknowledgment mode to the non-acknowledge mode transmission from the specified data packet. a continuous data packet; after receiving the second transmission mode response fed back by the receiving end, the transmitting end transmitting entity adopts the unacknowledged mode transmission; if the acknowledge mode is adopted before receiving the transmission mode indication, the clear mode is converted to Non-confirmed mode.
  • an embodiment of the present invention provides a mode conversion apparatus, including:
  • a determining module configured to determine, before sending the data packet to the receiving end, that the plurality of consecutive data packets starting from the specified data packet are transmitted in a non-acknowledged mode
  • a sending module configured to send a second transmission mode indication to the receiving end, where the second transmission mode indication is used to instruct the receiving end to open the specified data packet, before sending the designated data packet to the receiving end
  • the non-acknowledgment mode transmission is started; if the transmission mode adopted before the transmitting the second transmission mode indication is the acknowledge mode, the second transmission mode indication is further used to indicate that the receiving end converts from the acknowledge mode to the non-acknowledge mode.
  • a conversion module configured to receive the second transmission mode response fed back by the receiving end, using a non-acknowledgment mode transmission; if the transmission mode indication is received, Is the confirmation mode, then the mode is changed from the confirmation mode to the non-acknowledge mode.
  • an embodiment of the present invention provides a mode conversion method, including:
  • a second transmission mode indication sent by the transmitting end transmitting entity, where the second transmission mode indication is used to indicate that the receiving end starts to adopt the unacknowledged mode transmission from the designated data packet; if before sending the second transmission mode indication
  • the transmission mode used is an acknowledgment mode, and the second transmission mode indication is further used to indicate that the receiving end converts the acknowledgment mode to the non-acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet;
  • the receiving end If the data packet before the specified data packet is received, the receiving end starts to transmit in the unacknowledged mode from the designated data packet, and if the transmission mode adopted before receiving the second transmission mode indication is the acknowledge mode, the receiving end Confirming that the mode transitions to a non-acknowledgment mode to transmit a plurality of consecutive data packets starting from the specified data packet;
  • the receiving end starts a reordering event, and before the reordering event is triggered, it is confirmed that the data packet before the specified data packet has been received, and the receiving end starts to use the specified data packet.
  • the receiving end converts from the acknowledgment mode to the non-acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet; After the reordering event is triggered, the data packet before the specified data packet has not been received, and the sending failure status report is sent back to the transmitting end to cause the transmitting end to retransmit the unreceived data packet, and restart the reordering event.
  • an embodiment of the present invention provides a mode conversion apparatus, including: a receiving module, configured to receive a second transmission mode indication sent by the transmitting end transmitting entity, where the second transmission mode indication is used to indicate that the receiving end starts to use the unacknowledged mode transmission from the designated data packet; if the second transmission is being sent The mode indicates that the previously adopted transmission mode is the acknowledgment mode, and the second transmission mode indication is further used to instruct the receiving end to transmit a plurality of consecutive data packets starting from the specified data packet from the acknowledgment mode to the non-acknowledgment mode;
  • a response module configured to feed back a second transmission mode response to the sending end
  • a conversion module configured to: when receiving the data packet before the specified data packet, the receiving end starts to transmit in the unacknowledged mode from the designated data packet, if the transmission mode adopted before receiving the second transmission mode indication is confirmation Mode, converting from the acknowledgment mode to the non-acknowledgment mode, transmitting a plurality of consecutive data packets starting from the specified data packet;
  • the conversion module is further configured to: if the data packet before the specified data packet is not received, the receiving end starts a reordering event, and the data packet before the specified data packet is confirmed before the reordering event is triggered, from the The designated data packet begins to transmit in a non-acknowledgment mode, and if the transmission mode adopted before receiving the second transmission mode indication is an acknowledge mode, the transition from the acknowledge mode to the non-acknowledge mode transmits a plurality of consecutive starts from the specified data packet.
  • the transmitting end in the process of transmitting a data packet, sends a second transmission mode indication to the receiving end, and instructs the receiving end to start transmitting in the non-acknowledgment mode from the specified data packet.
  • Continuous data packets if the transmission mode adopted before the second transmission mode indication is an acknowledgment mode, further indicating that the receiving end converts from the acknowledgment mode to the non-acknowledge mode to transmit a plurality of consecutive data starting from the specified data packet package. Therefore, this embodiment can use different modes to transmit different data packets.
  • an embodiment of the present invention provides a data retransmission method in an acknowledge mode, including: a transmitting end transmission entity receiving a transmission failure report from a feedback of a receiving entity; The transmitting end transmitting entity determines, according to the transmission failure report, a PDU that fails to be transmitted;
  • the transmitting end transmitting entity resends the PDU that failed to transmit or the PDU that corresponds to the PDU that failed to transmit to the sending MAC entity, so that the priority of the PDU that failed to transmit is higher than the PDU that failed to be generated after the transmission; or
  • the transmitting end transmitting entity identifies the SDU corresponding to the PDU that failed to be transmitted, and retransmits the new PDU assembled by the SDU corresponding to the PDU that failed to transmit to the transmitting MAC entity according to the receiving sequence of the SDU that failed the transmission.
  • the SDU that fails to receive the transmission from the upper entity first has a higher priority than the SDU that has received the transmission failure from the upper entity.
  • an embodiment of the present invention provides a packet retransmission apparatus in an acknowledge mode, including:
  • a report receiving module configured to receive a transmission failure report from the receiving entity, and an identification module, configured to determine, according to the transmission failure report, a PDU that fails to be transmitted;
  • the retransmission module is configured to resend the PDU that fails to transmit to the sending MAC entity or the segment PDU corresponding to the PDU that fails to transmit, so that the PDU with the failed transmission has a higher priority than the PDU that fails to be transmitted after the transmission.
  • the SDU corresponding to the PDU that failed to be transmitted is identified, and the new PDU assembled by the SDU corresponding to the PDU that failed to be transmitted is sent to the sender MAC entity in the order of receiving the SDU from the uplink entity.
  • the SDU with the transmission failure received by the upper entity has a higher priority than the SDU of the transmission failure received from the upper entity.
  • the embodiment of the invention provides a data packet retransmission method and device in an acknowledgement mode, which sorts the retransmitted PDUs according to the generation order, so that the PDUs that are made by the clergy can be retransmitted preferentially when the transmission fails, so as to arrive at the receiving end early.
  • the receiving end can submit the PDU that has been received after the PDU, thereby reducing the time for the receiving end to buffer the received PDU.
  • FIG. 1 is a flowchart of a method for sending a data packet according to an embodiment of the present invention
  • FIG. 2 is a flowchart of another method for sending a data packet according to an embodiment of the present invention
  • 3A is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • FIG. 3B is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • FIG. 3C is a schematic diagram of an SDU retransmission according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • 3E is a schematic diagram of PDU retransmission according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • FIG. 7A is a flowchart of a mode conversion method according to an embodiment of the present invention.
  • FIG. 7B is a flowchart of another mode switching method according to an embodiment of the present invention.
  • FIG. 8A is a flowchart of still another mode conversion method according to an embodiment of the present invention.
  • FIG. 8B is a schematic diagram of mode switching according to an embodiment of the present invention.
  • FIG. 9A is a flowchart of still another mode switching method according to an embodiment of the present invention.
  • FIG. 9B is a flowchart of still another mode switching method according to an embodiment of the present invention.
  • 9C is a flowchart of still another mode switching method according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of a data retransmission method in an acknowledgment mode according to an embodiment of the present invention
  • FIG. 11B is a schematic structural diagram of a data packet sending apparatus according to an embodiment of the present invention
  • FIG. 12A is a schematic structural diagram of a mode conversion device according to an embodiment of the present invention
  • FIG. 12B is a schematic structural diagram of another mode conversion device according to an embodiment of the present invention
  • FIG. 13B is a schematic structural diagram of still another mode switching device according to an embodiment of the present invention
  • FIG. 14 is a schematic diagram of data packet retransmission in an acknowledge mode according to an embodiment of the present invention
  • FIG. 1 is a flowchart of a method for sending a data packet according to an embodiment of the present invention.
  • the data packet sending method provided in this embodiment includes: Step 11: The transmitting end transmitting entity receives the data packet to be sent from the upper layer entity.
  • the transmitting end transmitting entity may be a transmitting end RLC entity, a Packet Data Convergence Protocol (PDCP) entity, or a Radio Resource Control (RRC) entity, or another transport protocol, for example, an Internet Protocol (Internet Protocol). , IP), etc.
  • the data packet received from the upper layer entity may be a Radio Link Control Service Data Unit (RLC SDU).
  • RLC SDU Radio Link Control Service Data Unit
  • Step 12 The transmitting end transmitting entity determines the transmission mode of the data packet according to the transmission mode indication information sent by the upper layer entity or the transmission mode indication information in the data packet.
  • the transmission mode indication information is set according to a transmission requirement of the data packet.
  • the transmission mode indication information of the data packet may be notified by the upper layer entity to the sender RLC entity through an inter-layer message, for example, an inter-layer message of the PDCP entity or an inter-layer message of the RRC.
  • the transmission mode indication information of the data packet may also be carried by the upper layer entity to the sender RLC entity by using the indication bit included in the data packet.
  • the transmission mode indicates information such as the transmission requirement setting of the data packet, such as the priority information such as the transmission reliability requirement and the delay requirement of the data packet. If the data packet requires high transmission reliability or the transmission delay requirement is low, the transmission mode indication information of the data packet may set the transmission mode of the data packet to the acknowledge mode.
  • the transmission mode indication information of the data packet may set the transmission mode of the data packet to a non-acknowledge mode. For example, if the important packet transmission failure that affects the service delay causes the service to be interrupted, for example, the initialization fragment in the video service is lost, and the terminal cannot play the video, the waiting time for the user to watch the video is prolonged. Therefore, in order to ensure the transmission reliability of important data packets affecting the service delay, an acknowledgement mode can be used to transmit important data packets affecting the service delay.
  • Step 13 If the transmission mode of the data packet is the acknowledgment mode, the transmitting end transmitting entity sends the data packet to the receiving end by using an acknowledgment mode; if the transmission mode of the data packet is a non-acknowledgment mode, the transmitting end transmitting entity adopts a non-acknowledgment mode.
  • the acknowledge mode sends the packet.
  • the transmitting end transmitting entity receives the feedback from the receiving end.
  • the transmission status report of the data packet If the data packet transmission failure is determined according to the transmission status report of the data packet, the transmitting end transmission entity resends the data packet to the sending MAC entity, so that the sending MAC entity resends the sending to the receiving MAC entity. data pack.
  • the transmitting end transmitting entity before transmitting the data packet to the receiving end, the transmitting end transmitting entity first determines the transmission mode of the data packet according to the transmission mode indication information of the data packet, and according to the transmission mode indicated by the transmission mode indication information Send a packet to the receiver.
  • the transmission mode indication information of the data packet is set according to the transmission requirement of the data packet. For example, setting a data packet with high transmission reliability requirement or low transmission delay requirement to the acknowledge mode transmission, the transmission reliability requirement is low. Packets with higher transmission delay requirements are set to transmit in unacknowledged mode. Therefore, in this embodiment, the same bearer layer can adopt different transmission modes for different data packets according to the transmission mode indication information of different data packets, thereby satisfying the transmission characteristics of different data packets in the same service.
  • Figure 2 Figure 3A to Figure 3D correspond to the embodiment in which the specified data packet is transmitted using the local acknowledgment mode.
  • the transmitting RLC entity determines whether the data packet fails to be transmitted according to the transmission status report fed back by the MAC entity of the transmitting end, thereby determining whether to retransmit the data packet.
  • FIG. 2 is a flowchart of another method for sending a data packet according to an embodiment of the present invention. As shown in FIG. 2, the method for sending a data packet in the local acknowledge mode provided by this embodiment includes:
  • Step 21 The sender RLC entity receives the data packet from the upper entity.
  • Step 22 The transmitting RLC entity determines a transmission mode of the data packet according to the transmission mode indication information of the data packet; and the transmission mode indication information is set according to a transmission requirement of the data packet.
  • Step 23 After the sending RLC entity sends the data packet to the sending MAC entity, if the transmission mode of the data packet is the local acknowledgment mode, the sending RLC entity receives the feedback from the sending MAC entity. A transmission status report of the data packet of the receiving MAC entity.
  • the transmitting end RLC entity After the transmitting end RLC entity sends the data packet to the sending MAC entity, if the transmission mode of the data packet is the local acknowledgment mode, the sending RLC entity or the RRC entity may send the data packet to the sending MAC entity. And sending a result feedback indication, so that the MAC entity receives the transmission status report of the data packet sent by the receiving MAC entity, and then feeds back to the sending end RLC entity.
  • the sending result information is the receiving success information or the receiving failure information of the data packet from the receiving MAC entity, for example, returning an ACK, indicating that the receiving end successfully receives the data packet. Returning NACK indicates that the receiving end failed to receive the data packet.
  • the transmitting MAC entity After receiving the transmission status report returned by the receiving MAC entity, the transmitting MAC entity feeds back the transmission status report to the corresponding sending RLC entity.
  • the transmitting end RLC transmission status reporting entity may determine that the corresponding data packet transmission fails or succeeds according to the transmission status report fed back by the sending MAC entity. Step 24: If it is determined that the data packet transmission fails according to the transmission status report of the data packet, the sending RLC entity resends the data packet to the sending MAC entity, so that the sending MAC entity re-transmits to the receiving MAC entity. Send the packet.
  • the RLC entity of the transmitting end may discard the data packet, and no longer send the data packet to the sending MAC entity.
  • the sending end RLC entity may receive the sending MAC entity feedback.
  • the transmission status report of the packet from the receiving MAC entity.
  • the transmitting RLC entity Upon determining that the data packet transmission fails according to the transmission status report, the transmitting RLC entity resends the data packet to the sending MAC entity, so that the sending MAC entity resends the data packet to the receiving MAC entity. Therefore, the high reliability requirement of the transmission of the data packet can be satisfied, thereby meeting the requirement of high reliability of data packet transmission.
  • FIG. 3A is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • This embodiment transmits a data packet in a local acknowledgment mode, mainly explaining the processing when the transmission fails.
  • the data packet sending method provided in this embodiment includes:
  • Step la The sender RLC entity receives the RLC SDU from the upper entity
  • Step 2a The transmitting end RLC entity determines that the RLC SDU performs the local acknowledgment mode transmission according to the transmission mode indication information of the upper layer entity or the transmission mode indication information in the RLC SDU.
  • the upper layer entity in step 2a may be a PDCP or an RRC entity.
  • Step 3a The sending MAC entity performs a scheduling function to acquire the resources required for transmitting data.
  • Step 4a The transmitting MAC entity allocates resources for the RLC SDU to be sent by the sending RLC entity, and acquires the RLC PDU according to the resource size to the RLC entity. Packet Data Unit, Protocol Data Unit).
  • Step 5a The RLC entity of the sending end encapsulates the RLC PDU according to the resource provided by the MAC;
  • Step 6a The RLC entity of the sending end delivers the encapsulated RLC PDU to the MAC entity;
  • Step 7a The RLC entity of the sending end sends the RLC to the sending MAC entity The sending result feedback indication of the PDU is sent to the RLC entity after receiving the transmission failure indication or the transmission success indication of the data packet sent by the receiving MAC entity.
  • the RRC entity may also send a sending result feedback indication of each RLC PDU to the sending MAC entity, so that the MAC entity receives the receiving MAC address. And transmitting, by the entity, the transmission failure indication or the transmission success indication, and feeding back to the RLC entity.
  • Step 8a The sending MAC entity multiplexes the RLC PDU of one or more logical channel groups into a MAC PDU;
  • Step 9a The transmitting MAC entity transmits the MAC PDU through the HARQ process/entity; Step 10a: The transmitting MAC entity receives the transmission status report of the MAC PDU from the receiving MAC entity.
  • the transmission status report sent by the receiving MAC entity indicates that the corresponding MAC PDU transmission fails, for example, may be NACK feedback.
  • Step 11a The sender MAC entity feeds back the transmission status report of the RLC PDU to the RLC entity corresponding to the RLC PDU included in the MAC PDU.
  • Step 12a The RLC entity identifies the RLC SDIL that failed the transmission according to the transmission status report fed back by the MAC entity.
  • Step 13a The transmitting end RLC entity updates the transmission order, so that the RLC SDU with the transmission failure has a transmission priority higher than the transmission priority of the first transmitted RLC SDU.
  • the RLC SDU of the transmitting end puts the RLC SDUs that have failed to be transmitted into the RLC SDU retransmission queue according to the receiving order from the upper layer entity.
  • the data transmission priority of the RLC SDU retransmission queue is higher than that of other cached SDUs.
  • the RLC may mark the RLC SDU to be sent as not sent or need to be resent, and send the RLC SDU that needs to be resent according to the label of the RLC SDU in the subsequent sending process.
  • FIG. 3B is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • the data packet sending method provided in this embodiment is applicable to a scenario in which a data packet is retransmitted in an SDU format.
  • the data packet sending method provided in this embodiment includes:
  • Step lb The sender RLC entity identifies the RLC SDIL that failed the transmission based on the feedback from the sender MAC entity.
  • Step 2b The transmitting end RLC entity updates the transmission order, so that the transmission priority of the RLC SDU with the transmission failure is higher than the transmission priority of the first transmitted RLC SDU.
  • Step 3b The sender performs the scheduling function on the MAC to obtain the resources required to send data.
  • Step 4b The sending MAC entity allocates resources for the RLC SDU to be sent, and obtains RLC PDIL from the RLC entity according to the resource size.
  • Step 5b The sender RLC entity is encapsulated according to the resources provided by the sender MAC entity.
  • the RLC SDU if there is an RLC SDU that needs to be retransmitted, the transmitting RLC entity preferentially encapsulates the retransmitted RLC SDU into an RLC PDU.
  • the RLC SDU of the transmitting end preferentially encapsulates the retransmitted RLC SDUs into RLC PDIL according to the receiving order from the upper layer entity.
  • RLC SDU1 is encapsulated into RLC PDU1 and RLC PDU2, and RLC SDU2 is encapsulated into RLC PDU2 and RLC PDU3.
  • the RLC PDU2 contains data of part of the RLC SDU1 and data of part of the RLC SDU2.
  • the previously transmitted RLC SDU1 and RLC SDU2 cannot be completely assembled at the receiving end and are discarded, and the receiving MAC entity is only in the RLC PDU1, the RLC PDU2 and After all the RLC PDU3s are successfully received, they are fully assembled and delivered to the receiving RLCP entity.
  • the RLC SDU1 is re-encapsulated into the RLC PDU4 and the RLC PDU5
  • the RLC SDU2 is re-encapsulated into the RLC PDU5 and the RLC PDU6.
  • Step 6b The transmitting end RLC entity submits the encapsulated RLC PDU to the sending MAC entity;
  • Step 7b The sending MAC entity multiplexes the RLC PDU of one or more logical channel groups into a MAC PDU;
  • Step 8b The transmitting MAC entity transmits the MAC PDU through the HARQ process/entity; Step 9b: The transmitting MAC entity receives the transmission status report of the MAC PDU from the receiving MAC entity.
  • the transmission status report sent by the receiving MAC entity indicates that the corresponding MAC PDU transmission is successful, for example, may be ACK feedback.
  • Step 10b The transmitting MAC entity feeds back the transmission status report of the RLC PDU to the RLC entity corresponding to the RLC PDU included in the MAC PDU.
  • Step lib After receiving the indication that the RLC PDU is successfully transmitted, the RLC entity discards the RLC PDU and releases the cache resource of the RLC PDU.
  • FIG. 3D is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • the data packet sending method provided in this embodiment is applicable to a scenario in which a PDU is retransmitted by using a PDU.
  • the data packet sending method provided in this embodiment includes:
  • Step lc The RLC entity on the transmitting end identifies the RLC PDIL that failed to be transmitted according to the feedback of the sender MAC entity.
  • Step 2c The transmitting end RLC entity updates the transmission order, so that the RLC PDU with the failed transmission has a transmission priority higher than the transmission priority of the first transmitted RLC PDU.
  • Step 3c The sender performs the scheduling function on the MAC to obtain the resources required to send data.
  • Step 4c The sending MAC entity acquires the resource for the RLC SDU to be sent, and obtains the RLC PDIL from the RLC entity according to the resource size.
  • Step 5c The sender RLC entity encapsulates the RLC SDU according to the resources provided by the sender MAC entity.
  • Step 6c The RLC entity of the sending end delivers the encapsulated RLC PDU to the sender MAC entity; if there is an RLC PDU that needs to be retransmitted, the retransmitted RLC PDU is preferentially delivered to the sending MAC entity.
  • the PDU that fails to transmit or the transmission fails is sent to the sender MAC entity.
  • the segmentation PDU corresponding to the PDU makes the priority of the PDU that failed to transmit is higher than the PDU that failed to be transmitted after the transmission.
  • RLC SDU1 is encapsulated into RLC PDU1 and RLC PDU2
  • RLC SDU2 is encapsulated into RLC PDU2 and RLC PDU3.
  • the RLC PDU2 contains data of part of the RLC SDU1 and data of part of the RLC SDU2.
  • the transmitting MAC entity After receiving the lost RACK indication of the RLC PDU2, when the retransmission of the RLC PDU is adopted, the transmitting MAC entity retransmits only the RLC PDU2, and does not need to retransmit the RLC PDU1 and the RLC SDU2 that have been successfully transmitted in the RLC SDU1 have successfully transmitted the RLC. PDU3. As shown in FIG.
  • the transmitting MAC entity needs to retransmit all the PDUs of the RLC PDU1 and the RLC PDU2 and all the PDUs.
  • the SDU that should be received first may arrive at the PDCP layer due to retransmission, and in order to ensure that PDCP can deliver the data packet to the upper layer in order, PDCP needs to follow the SN carried in the data packet.
  • the received data packets are sorted; therefore, the implementation complexity of using PDU retransmission is smaller than that of SDU retransmission.
  • Step 7c The sending MAC entity multiplexes the RLC PDU of one or more logical channel groups into a MAC PDU;
  • Step 8c The transmitting MAC entity transmits the MAC PDU through the HARQ process/entity; Step 9c: The transmitting MAC entity receives the transmission status report of the MAC PDU from the receiving MAC entity.
  • the transmission status report sent by the receiving MAC entity indicates the corresponding MAC PDU.
  • the transmission is successful, for example, it can be ACK feedback.
  • Step 10c The transmitting MAC entity feeds back the transmission status report of the RLC PDU to the RLC entity corresponding to the RLC PDU included in the MAC PDU.
  • Step 11c After receiving the indication that the RLC PDU is successfully transmitted, the RLC entity discards the RLC PDU and releases the cache resource of the RLC PDU.
  • the automatic packet retransmission request acknowledge mode is used to transmit the designated data packet.
  • the transmitting RLC entity determines whether the data packet needs to be retransmitted according to the feedback of the receiving RLC entity.
  • FIG. 4 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • the data packet sending method provided in this embodiment includes:
  • Step 41 The sender RLC entity receives the data packet from the upper entity.
  • the upper layer entity may be a PDCP entity or an RRC entity.
  • the data packet received from the upper entity can be an RLC SDU.
  • Step 42 The transmitting end RLC entity determines a transmission mode of the data packet according to the transmission mode indication information of the data packet; and the transmission mode indication information is set according to a transmission requirement of the data packet.
  • the transmission mode indication information of the data packet may be notified by the upper layer entity to the sender RLC entity through an inter-layer message, for example, an inter-layer message of the PDCP entity or an inter-layer message of the RRC.
  • the transmission mode indication information of the data packet may also be carried by the upper layer entity to the sender RLC entity by using the indication bit included in the data packet.
  • Step 43 When the transmission mode of the data packet is determined to be an automatic retransmission request acknowledgement mode, the indication information of the feedback transmission result is added to the data packet, and the RLC entity of the receiving end is sent to the RLC entity after receiving the data packet. The end RLC entity feeds back the transmission success indication of the data packet.
  • Step 44 After the sending RLC entity sends the data packet to the sending MAC entity, the active retransmission event is initiated. If the active retransmission event is triggered, the receiving of the data packet sent by the receiving RLC entity is not successfully received. It is confirmed that the sender RLC entity resends the data packet to the sender MAC entity.
  • the transmitting end RLC entity determines that the transmission mode of the data packet is an automatic repeat request (ARQ) mode
  • ARQ automatic repeat request
  • the data packet is sent to the sending MAC entity.
  • the active retransmission trigger event is started, for example, setting an active retransmission timer.
  • the receiving RLC entity transmits according to the feedback in the data packet.
  • the resulting indication information feeds back to the sender RLC entity a successful receipt confirmation of the data packet.
  • the receiving end RLC entity Before the active retransmission event is triggered, for example, before the active retransmission timer expires, the receiving end RLC entity does not receive the successful hacking of the data packet sent by the receiving end RLC entity, and the sending RLC entity determines the location. The data packet fails to be sent, and the data packet is delivered to the sender MAC entity. If the receiving end RLC entity receives the successful reception confirmation of the data packet sent by the receiving end RLC entity before the active retransmission timer expires, the data packet is not re-transmitted to the sending MAC entity, and the active stop is stopped. Retransmission timer.
  • the RLC entity of the sending end can also set the maximum number of active retransmissions. When a certain data packet is repeatedly retransmitted, it still receives the successful reception confirmation from the receiving RLC entity after the active retransmission event is triggered. Then, the sender RLC entity no longer sends the data packet to the sender MAC entity.
  • the RLC entity of the sending end when the transmission mode of the data packet is determined to be the automatic retransmission request acknowledgement mode, receives the indication information of adding the feedback transmission result to the data packet sent by the upper layer entity, and indicates the receiving end. After receiving the data packet, the RLC entity feeds back to the sending RLC entity the transmission success indication of the data packet. After the RLC entity sends the data packet to the sending MAC entity, the active retransmission event is started. After the active retransmission event is triggered, the receiving RLC entity does not receive the receiving success confirmation from the receiving end RLC, and the sending RLC entity resends the data packet to the sending MAC entity.
  • the receiving RLC entity Before the active retransmission event is triggered, the receiving RLC entity receives a successful acknowledgement of the receiving of the data packet, and the transmitting RLC entity does not retransmit the data packet.
  • the automatic retransmission request acknowledgement mode is used to send the data packet to the receiving end, which satisfies the requirement of high reliability of the data packet transmission.
  • FIG. 5 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • the ARQ transmission mode of the data packet is described by taking a packet transmission failure as an example.
  • the data packet sending method provided in this embodiment includes:
  • Step Id The sender RLC entity receives the RLC SDU from the upper entity
  • Step 2d The RLC entity determines, according to the transmission mode indication information of the upper layer entity or the transmission mode indication information included in the RLC SDU, that the RLC SDU performs an automatic retransmission request acknowledge mode transmission.
  • the upper layer entity in step 2d may be a PDCP or RRC entity.
  • Step 3d The sending MAC entity performs a scheduling function to acquire the resources required for sending data.
  • Step 5d The RLC entity of the sending end encapsulates the data packet according to the resource provided by the MAC entity, and adds indication information of the feedback transmission result to the data packet, and indicates that the RLC entity of the receiving end receives the data packet and sends the RLC entity to the sending end. Feedback is successfully received by the receipt of the data packet.
  • Step 6d The sender RLC entity delivers the encapsulated RLC PDU to the sender MAC entity.
  • Step 7d The RLC entity at the transmitting end initiates an active retransmission timer of the RLC PDU.
  • Step 8d The transmitting MAC entity multiplexes the RLC PDU of one or more logical channel groups into a MAC PDU;
  • Step 9d The transmitting MAC entity transmits the MAC PDU through the HARQ process/entity; Step 10d: The transmitting MAC entity receives the transmission status report from the receiving MAC entity indicating that the MAC PDU failed to be sent.
  • Step lid Before the active retransmission timer of the RLC PDU expires, the transmitting RLC entity does not receive the successful reception confirmation of the RLC PDU sent by the receiving RLC entity, and marks that the RLC PDU needs to be retransmitted.
  • Step 12d The transmitting end RLC entity updates the transmission order, so that the RLC PDU that fails to transmit has a sending priority higher than the sending priority of the first transmitted RLC SDU.
  • the PDU that fails to transmit or the transmission fails is sent to the sender MAC entity.
  • the segmentation PDU corresponding to the PDU makes the priority of the PDU that failed to transmit is higher than the PDU that failed to be transmitted after the transmission.
  • the maximum number of retransmissions of the SDU or PDU corresponding to the terminal may be configured in advance by the base station according to the reliability of the data packet, if the maximum number of retransmissions of the corresponding SDU or PDU is equal to or exceeds the pre-request If the maximum number of retransmissions is configured, the retransmission of the SDU or PDU is stopped, that is, the SDU or PDU is not retransmitted.
  • the transmitting end may wait for receiving the reception success feedback after receiving the feedback, and then stop retransmission; therefore, after the receiving end successfully receives the data packet, even if the received data packet is invalid. , also reply to receive successful confirmation.
  • FIG. 6 is a flowchart of still another method for sending a data packet according to an embodiment of the present invention.
  • the ARQ transmission mode of the data packet is described by taking the success of the data packet transmission as an example.
  • the data packet sending method provided in this embodiment includes: Step le: The sender RLC entity receives the RLC SDU from the upper entity.
  • Step 2e The RLC entity determines whether the RLC SDU performs an automatic retransmission request acknowledge mode transmission according to the transmission mode indication information of the upper layer entity or the transmission mode indication information included in the RLC SDU.
  • Step 3e The sending MAC entity performs a scheduling function to acquire the resources required to send data.
  • Step 4e The sending MAC entity allocates resources for the data packet to be sent by the RLC entity, and obtains the RLC PDIL from the RLC entity with reference to the resource size.
  • Step 5e The transmitting end RLC entity encapsulates the data packet according to the resource provided by the sending MAC entity, and adds indication information of the feedback transmission result to the data packet, and indicates that the receiving end RLC entity receives the data packet and sends the data packet to the sending end.
  • the RLC entity feeds back the successful receipt of the data packet.
  • Step 6e The transmitting RLC entity delivers the encapsulated RLC PDU to the sending MAC entity.
  • Step 7e The RLC entity of the sending end initiates an active retransmission timer of the RLC PDU to be sent.
  • Step 8e The sending MAC entity multiplexes the RLC PDU of one or more logical channel groups into a MAC PDU;
  • Step 9e The sending MAC entity transmits the MAC PDU through the HARQ process/entity; Step 10e: The sending MAC entity receives the receiving success confirmation sent by the receiving MAC entity.
  • Step 12e The receiving MAC entity sends the demultiplexed RLC PDU to the corresponding receiving RLC entity according to the RLC identifier included in the MAC PDU.
  • Step 13e The receiving end RLC entity identifies that the RLC PDU needs to be successfully received by the feedback according to the indication information of the feedback transmission result included in the RLC PDU.
  • Step 14e The receiving RLC entity feeds back the successful confirmation of the RLC PDU to the sending RLC entity.
  • Step 15e Before the active retransmission timer of the RLC PDU expires, the RLC entity of the sending end confirms that the RLC PDU is successfully received by the receiving RLC entity, and stops the active retransmission timer.
  • the base station needs to configure the terminal, so that the RLC entity at the transmitting end adopts the transmission request according to the data packet.
  • the packet is transmitted in either the acknowledge mode or the non-acknowledge mode.
  • the base station sends the hybrid transmission mode configuration parameter to the terminal, including the hybrid transmission mode identifier and the transmission parameter, where the hybrid transmission mode configuration parameter is used to indicate that the RLC entity corresponding to the RLC entity identifier in the terminal adopts the confirmation according to the transmission requirement of the data packet.
  • the mode or non-acknowledgment mode transmits the data packet; the terminal configures the RLC entity corresponding to the received RLC entity identifier according to the hybrid transmission mode configuration parameter.
  • the hybrid transmission mode is a transmission mode in which the terminal can transmit the data packet in an acknowledge mode or an unacknowledged mode according to the transmission requirement of the data packet.
  • FIG. 11 is a schematic structural diagram of a data packet sending apparatus according to an embodiment of the present invention. As shown in FIG. 11A, the embodiment includes: a receiving module 111, a mode determining module 112, an acknowledgement transmission module 113, and a non-confirmation transmission module 114.
  • the receiving module 111 is configured to receive, from the upper layer entity, a data packet to be sent;
  • the mode determining module 112 is configured to determine, according to the transmission mode indication information sent by the upper layer entity or the transmission mode indication information in the data packet, a transmission mode of the data packet, where the transmission mode indication information is according to the data The transmission requirements of the package are set.
  • the acknowledgment transmission module 113 is configured to send the data packet to the receiving end by using the acknowledgment mode if the transmission mode of the data packet is the acknowledgment mode.
  • the non-acknowledgment transmission module 114 is configured to send the data packet to the receiving end in a non-acknowledgment mode if the transmission mode of the data packet is a non-acknowledgement mode.
  • the acknowledgment transmission module 113 includes: a sending unit 1131, a feedback receiving unit 1132, and a resending unit 1133.
  • the sending unit 1131 is configured to send the data packet to the sending MAC entity, so that the sending MAC entity sends the data packet to the receiving MAC entity.
  • the feedback receiving unit 1132 is configured to: if the transmission mode of the data packet is an acknowledge mode, receive a transmission status report of the data packet fed back from the receiving end.
  • the retransmission unit 1133 is configured to: if the data packet transmission failure is determined according to the transmission status report of the data packet, resend the data packet to the sending MAC entity, so that the sending MAC entity re-transmits to the receiving MAC entity. Send the packet.
  • the retransmission unit is further configured to: before resending the data packet to the sender MAC entity, update the transmission sequence, so that the transmission priority of the data packet with the transmission failure is higher than that of the first transmission. The priority of the packet to be sent.
  • the retransmission unit is further configured to resend the PDU that fails to be transmitted in the data packet or the PDU that corresponds to the PDU that fails to be transmitted to the sender MAC entity according to the sequence of generating the PDU that fails to be transmitted.
  • the PDU of the failed transmission PDU has a higher priority than the PDU that failed to be transmitted; or the SDU corresponding to the PDU that failed to transmit is sent to the sender MAC entity in the order of receiving the SDU from the upper layer entity.
  • the assembled new PDU is such that the SDU that fails to receive the transmission from the upper entity first has a higher SDU than the transmission failure that is received from the upper entity.
  • the sending unit is specifically configured to send the data packet to the sending MAC entity, and if the transmission mode of the data packet is a local acknowledgment mode, send a sending result feedback indication of the data packet to the sending MAC entity. So that the MAC entity receives the transmission status report of the data packet sent by the receiving MAC entity, and then feeds back to the sending end RLC entity;
  • the feedback receiving unit is specifically configured to: if the transmission mode of the data packet is a local acknowledgment mode, after receiving the transmission status report of the data packet, the receiving MAC entity receives the data packet fed back by the sending MAC entity Transmission status report.
  • FIG. 2 For the functions of the above modules, refer to FIG. 2, and FIG. 3A to FIG. 3D are respectively described in the corresponding embodiments, and details are not described herein again.
  • the transmission mode of the data packet is an automatic retransmission request acknowledgement mode:
  • the sending unit is specifically configured to send the data packet to the sending MAC entity, and if the transmission mode of the data packet is an automatic retransmission request acknowledgement mode, add indication information of the feedback transmission result to the data packet. And after receiving the data packet, the receiving end RLC entity feeds back, to the RLC entity, a successful reception confirmation of the data packet; and is further configured to: after sending the data packet to the sending MAC entity, start the active weight Pass the event;
  • the retransmission unit is specifically configured to: if the receiving of the data packet is not received before the triggering of the active retransmission event of the data packet, the receiving of the data packet is successfully sent to the sending MAC entity.
  • the data packet is specifically configured to: if the receiving of the data packet is not received before the triggering of the active retransmission event of the data packet, the receiving of the data packet is successfully sent to the sending MAC entity. The data packet.
  • the second embodiment further provides a parameter configuration apparatus, configured to send a hybrid transmission mode configuration parameter to the terminal, including a hybrid transmission mode identifier and a transmission parameter, where the hybrid transmission mode configuration parameter And the RLC entity corresponding to the RLC entity identifier in the terminal is configured to transmit the data packet according to a transmission request of a data packet in the RLC bearer layer by using an acknowledge mode or a non-acknowledge mode.
  • a parameter configuration apparatus configured to send a hybrid transmission mode configuration parameter to the terminal, including a hybrid transmission mode identifier and a transmission parameter, where the hybrid transmission mode configuration parameter And the RLC entity corresponding to the RLC entity identifier in the terminal is configured to transmit the data packet according to a transmission request of a data packet in the RLC bearer layer by using an acknowledge mode or a non-acknowledge mode.
  • Embodiment 2 illustrates a method of how the transmitting end and the receiving end switch the transmission mode during data packet transmission.
  • the transmission mode switching includes switching from UM mode to AM mode, or switching from AM mode to UM mode, so that different transmission modes are adopted for different data packets according to different data packet transmission requirements.
  • FIG. 7A is a flowchart of a mode switching method according to an embodiment of the present invention. This embodiment mainly explains how the transmitting end converts from the UM mode to the acknowledgment mode. As shown in FIG. 7A, the mode conversion method provided in this embodiment includes:
  • Step 70A Before the transmitting end transmitting entity sends the data packet to the receiving end, it is determined that the plurality of consecutive data packets starting from the specified data packet are transmitted in the acknowledge mode.
  • the transmitting end entity determines the transmission mode of the data packet according to the transmission mode indication information of the data packet.
  • the transmission mode indication information of the data packet may be notified by the upper layer entity to the transmitting end through the inter-layer message, or may be carried by the upper layer entity to the transmitting end transmitting entity through the indication bit included in the data packet.
  • Step 71A Before transmitting the designated data packet to the receiving end, the transmitting end transmitting entity sends a first transmission mode indication to the receiving end, where the first transmission mode indication is used to indicate that the receiving end starts to use the acknowledge mode transmission from the specified data packet;
  • the first transmission mode indicates that the previously adopted transmission mode is the non-acknowledgement mode, and the first transmission mode indication is further used to instruct the receiving end to switch from the non-acknowledgment mode to the acknowledge mode to transmit a plurality of consecutive data packets starting from the designated data packet.
  • the transmitting end transmitting entity determines that a plurality of consecutive data packets subsequent to the designated data packet are transmitted in an acknowledgment mode, and sends a first transmission mode indication to the receiving end, instructing the receiving end to transmit in the acknowledgment mode from the specified data packet. If the unacknowledged mode transmission is used before transmitting the first transmission mode indication, the first transmission mode indication is further used to instruct the receiving end to switch from the non-acknowledgment mode to the acknowledgment mode to transmit the designated data packet and the subsequent data packet of the designated data packet.
  • the transmitting end transmitting entity determines that a plurality of consecutive data packets after the specified data packet are transmitted in the ARQ acknowledge mode, the receiving end is the receiving end RLC entity, and the transmitting end transmitting entity sends the designated RLC entity to the receiving end RLC entity to carry the specified data packet.
  • the first transmission mode indication is sent; if the local acknowledgment mode transmission is adopted, the transmitting end transmission entity sends a first transmission mode indication to the underlying transmission entity, for example, a MAC entity, where the first transmission mode indication does not need to carry data a packet identifier, where the first transmission mode indication is further used to instruct the sender bottom layer entity to feed back a layer (MAC) transmission result (HARQ) to the sender transmitting entity, where the first transmission mode indication can be sent by the sender control layer (RRC)
  • RRC sender control layer
  • Step 72A After receiving the first mode conversion response fed back by the receiving end, the transmitting end transmitting entity adopts an acknowledgment mode transmission; if the unacknowledged mode is adopted before receiving the transmission mode indication, the unconfirmed mode is switched to the acknowledgment mode. .
  • the transport mode indication may specify a data packet identifier for starting the acknowledge mode transmission, and after receiving the first mode conversion response fed back by the receiving end, the transmitting end adopts the data packet for the specified data packet and subsequent data packets.
  • Acknowledge mode transmission if the receiver transmits in the non-acknowledge mode before the transmission mode indication, the mode is switched from the non-acknowledge mode to the acknowledge mode.
  • the first transmission mode indication may not carry the specified data packet identifier, and after receiving the first transmission mode indication, the receiving end entity feeds back the data layer to the data packet and the data packet afterwards. Transfer results.
  • the transmitting end sends a first transmission mode indication to the receiving end in the process of transmitting the data packet, and instructs the receiving end to start transmitting, by using the acknowledge mode, multiple consecutive data packets starting from the specified data packet. And if the transmission mode adopted before the first transmission mode indication is the non-acknowledgement mode, the receiving end is further instructed to switch from the non-acknowledgment mode to the acknowledge mode to transmit a plurality of consecutive data packets starting from the designated data packet. Therefore, this embodiment can use different modes to transmit different data packets.
  • FIG. 7B is a flowchart of another mode switching method according to an embodiment of the present invention. This embodiment mainly explains how the receiving end converts from the UM mode to the AM mode. As shown in FIG. 7B, the mode conversion method provided in this embodiment includes:
  • Step 70B The receiving end receives a first transmission mode indication sent by the transmitting end transmitting entity, where the first transmission mode indication is used to indicate that the receiving end starts to adopt the acknowledgment mode transmission from the designated data packet; if the first transmission mode indication is used before being sent The transmission mode is a non-acknowledgement mode, and the first transmission mode indication is further used to instruct the receiving end to switch from the non-acknowledgment mode to the acknowledge mode to transmit the designated data packet and the subsequent data packet of the designated data packet.
  • the acknowledge mode is the local acknowledge mode
  • the receiver is the sender bottom layer entity
  • the sender bottom layer entity further transmits, to the sender, the transmission result of the multiple consecutive data packets starting from the specified data packet
  • the acknowledge mode is automatic retransmission
  • the acknowledgement mode is requested, and the receiving end is a receiving end RLC entity, and the first transmission mode indication further includes an identifier of the specified data packet.
  • Step 71B The receiving end feeds back the first transmission mode response to the transmitting end.
  • Step 721B If the data packet before the specified data packet is received, the receiving end starts to transmit in the acknowledge mode from the specified data packet, and if the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledgment mode, the receiving end is non-acknowledged.
  • the acknowledgment mode transitions to acknowledgment mode to transfer multiple consecutive packets starting from the specified packet.
  • Step 722B If the data packet before the specified data packet has not been received, the receiving end starts the reordering event, after the reordering event is triggered, or before the reordering event is triggered, it confirms that the data packet before the specified data packet is received, and receives The terminal transmits in the acknowledgment mode from the specified data packet. If the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledge mode, the receiving end converts from the non-acknowledgment mode to the acknowledgment mode to transmit multiple packets starting from the specified data packet. Continuous data packets.
  • FIG. 8 is a flowchart of still another mode conversion method according to an embodiment of the present invention. This embodiment mainly describes the interaction process between the transmitting end and the receiving end in the process of converting from the UM mode to the ARQ confirming mode. As shown in FIG. 8A, the mode conversion method provided in this embodiment includes:
  • Step 2f The transmitting end RLC entity sends a first transmission mode indication carrying the data packet C to the receiving end RLC entity, where the first transmission mode indication is used to indicate that the receiving end starts to use the ARQ acknowledge mode transmission from the data packet C;
  • the first transmission mode indication is further used to indicate that the receiving end converts from the UM mode to the ARQ acknowledge mode to transmit multiple consecutive packets starting from the data packet C, before the first transmission mode indication is sent to the UM mode. data pack.
  • the transmitting end Before the transmitting end prepares to send the data packet c to the receiving end, it sends a first transmission mode indication carrying the data packet C to the receiving end.
  • Step 3f After receiving the first transmission mode indication, the receiving RLC entity feeds back the first transmission mode response to the sending RLC entity.
  • Step 4f Determining that packet b has not been received before packet C, the receiving RLC entity starts, or restarts the reordering timer, has received the packet before the reordering timer expires, or the reordering timer expires.
  • the receiving end determines, according to the first transmission mode indication, that the transmission mode adopted before receiving the first transmission mode indication is the UM mode, and converts from the UM mode to the ARQ.
  • the acknowledgment mode transmits a plurality of consecutive packets starting from packet C.
  • VR (UH) is the receiving upper limit of the receiving window in the UM mode, indicating that the receiving end has received the maximum SN+1 of the data packet
  • VR (UR) is the receiving lower limit of the receiving window in the UM mode, indicating receiving The terminal can receive the minimum SN of the data packet.
  • VR ( UH ) moves down clockwise
  • VR ( UR ) also moves clockwise downwards following VR ( UH ) after VR ( UH ) moves down.
  • VR (UX) indicates from which packet the UM mode starts the re-ordering timer.
  • the receiving end After the reordering timer expires, if the receiving end receives the data packet b, the receiving end does not wait for the data packet b because it transmits the data packet in the UM, sorts the received data packet, and converts from the UM mode to ARQ acknowledgment mode; if packet b is received before the reordering timer expires, the receiving end immediately stops the reordering timer, sorts the received data packets, and converts from UM mode to ARQ acknowledgment mode.
  • Step 5f After receiving the feedback from the RLC entity of the receiving end, the RLC entity responds to the first transmission mode response, and determines that the transmission mode adopted before receiving the first transmission mode indication is UM mode, and converts from UM mode to ARQ confirmation mode.
  • VT (A) represents the SN of the next to-be-acknowledged data packet of the transmitting end in the AM mode
  • VT(S) represents the SN, VT (MS) of the next to-be-sent packet of the transmitting end in the AM mode.
  • the upper limit of the transmission end of the sender in the AM mode indicates the maximum SN at which the sender can transmit the data packet.
  • UT ( S ) C, indicating that the next packet to be acknowledged by the sender is c in AM mode.
  • the receiving RLC entity converts the UM mode to the ARQ acknowledgment mode, and then feeds back the first mode switching response to the sending RLC entity.
  • FIG. 9A is a flowchart of still another mode switching method according to an embodiment of the present invention. This embodiment mainly explains how the transmitting end converts from the AM mode to the UM mode. As shown in FIG. 9A, the mode conversion method provided in this embodiment includes:
  • Step 90A Before the transmitting end transmitting entity sends the data packet to the receiving end, it is determined that the plurality of consecutive data packets starting from the specified data packet are transmitted in the unacknowledged mode.
  • the sender transmitting entity may be a sender RLC entity.
  • Step 91A Before sending the designated data packet to the receiving end, the transmitting end transmitting entity sends a second transmission mode indication to the receiving end, where the second transmission mode indication is used to instruct the receiving end to start transmitting in the unacknowledged mode from the designated data packet;
  • the transmission mode adopted before the second transmission mode indication is sent is an acknowledgment mode, and the second transmission mode indication is further used to instruct the receiving end to transmit a plurality of consecutive data packets starting from the specified data packet from the acknowledgment mode to the non-acknowledge mode.
  • the receiver is the sender bottom entity, such as the sender MAC entity; if the acknowledge mode is the automatic repeat request acknowledge mode, the receiver is the receiver RLC entity, and the second transmission mode indication further includes the specified data.
  • the identity of the package is the sender bottom entity, such as the sender MAC entity; if the acknowledge mode is the automatic repeat request acknowledge mode, the receiver is the receiver RLC entity, and the second transmission mode indication further includes the specified data. The identity of the package.
  • Step 92A After receiving the second transmission mode response fed back by the receiving end, the transmitting end transmitting entity adopts the unacknowledged mode transmission; if the acknowledge mode is adopted before receiving the transmission mode indication, the mode is changed from the confirming mode to the non-acknowledgment mode. mode.
  • the sender when the sender has at least one data packet that has been sent and needs to be acknowledged without being acknowledged by the receiver, the sender sends a sequence number (SN).
  • SN sequence number
  • the sender cannot send a packet using the SN that exceeds the upper limit of the transmission window.
  • the transmitting end sends a second transmission mode indication to the receiving end in the process of transmitting the data packet, and instructs the receiving end to start transmitting the plurality of consecutive data starting from the specified data packet in the non-acknowledgment mode.
  • the packet if the transmission mode adopted before the second transmission mode indication is the acknowledgment mode, further instructs the receiving end to transmit a plurality of consecutive data packets starting from the specified data packet from the acknowledgment mode to the non-acknowledge mode. Therefore, this embodiment can use different modes to transmit different data packets.
  • FIG. 9B is a flowchart of still another mode switching method according to an embodiment of the present invention. This embodiment mainly explains how the receiving end converts from AM mode to UM mode. As shown in FIG. 9B, the mode conversion method provided in this embodiment includes:
  • Step 90B The receiving end receives a second transmission mode indication sent by the transmitting end transmitting entity, where the second transmission mode indication is used to instruct the receiving end to start transmitting in the unacknowledged mode from the designated data packet; if the second transmission mode indication is sent before The transmission mode adopted is the acknowledgment mode, and the second transmission mode indication is further used to indicate that the receiving end converts from the acknowledgment mode to the non-acknowledge mode transmission finger.
  • the receiver is the sender bottom entity; if the acknowledge mode is the automatic repeat request acknowledge mode, the receiver is the receiver RLC entity, and the second transport mode indication further includes the identifier of the specified packet.
  • Step 91B The receiving end feeds back the second transmission mode response to the transmitting end.
  • Step 921B If the data packet before the designated data packet is received, the receiving end starts to transmit in the unacknowledged mode from the designated data packet, and if the transmission mode adopted before receiving the second transmission mode indication is the acknowledge mode, the receiving end confirms The mode transitions to a non-acknowledge mode to transfer multiple consecutive packets starting from the specified packet.
  • Step 922B If the data packet before the specified data packet is not received, the receiving end starts the reordering event, and the data packet before the specified data packet is acknowledged before the reordering event is triggered, and the receiving end starts to use the non-acknowledgment from the specified data packet.
  • Mode transmission if the transmission mode adopted before receiving the second transmission mode indication is the acknowledgment mode, the receiving end converts from the acknowledgment mode to the non-acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet; if the reordering event is triggered , has not received the packet before the specified packet, and sends a failure status report to the sender to cause the sender to retransmit the unreceived packet and restart the reordering event.
  • the sending of the failure status report to the transmitting end causes the transmitting end to retransmit the unreceived data packet.
  • the receiving end further The reordering event can be restarted.
  • the start reordering event may be a retransmission sorting timer, and the reordering event may be a retransmission sorting timer. If the data packet before the specified data packet has not been received after the reordering timer expires, since the receiving end is still in the ARQ acknowledgment mode, it needs to receive the data packet b before it can be converted to the UM mode, so the receiving end transmits to the transmitting end.
  • the feedback transmission failure status report causes the transmitting end to retransmit the data packet that has not been received, and restarts the reordering timer until the data packet b is received.
  • FIG. 9C is a flowchart of still another mode switching method according to an embodiment of the present invention. This embodiment mainly describes the interaction process between the sender and the receiver in the process of converting the ARQ acknowledgment mode to the UM mode. As shown in FIG. 9C, the mode conversion method provided in this embodiment includes:
  • Step lg Before the RLC entity sends the data packet c, it is determined that multiple consecutive data packets are transmitted in the UM mode starting from the data packet C.
  • VT (A) is the SN of the data packet to be acknowledged in the ARQ acknowledgement mode
  • VT (S) is the SN of the data packet to be transmitted in the ARQ acknowledgement mode
  • VT (MS) Indicates the upper transmission limit in ARQ acknowledgment mode, from VT (MS) to VT (A) is half the size of the transmission window.
  • Step 2g The sending end RLC entity sends a second transmission mode indication carrying the data packet C to the receiving end RLC entity, where the second transmission mode indication is used to indicate that the receiving end RLC entity starts to use UM transmission from the data packet C;
  • the second transmission mode indicates that the previously adopted transmission mode is the AM mode, and the second transmission mode indication is further used to indicate that the receiving end RLC entity converts from the AM mode to the UM mode to transmit a plurality of consecutive data packets starting from the data packet C.
  • Step 3g When receiving the second transmission mode indication, the receiving end RLC entity determines that the data packet b before the data packet C has been received, and the receiving end RLC entity starts the reordering timer, and has received the reordering timer before the timeout expires.
  • the data packet b is converted from the ARQ acknowledgment mode to the UM mode according to the second transmission mode indication; after the reordering timer expires, the data packet b has not been received, and the receiving end RLC entity feeds back the transmission failure status report to the transmitting end to make the transmitting end heavy Pass packet b and restart the reordering timer.
  • the receiving end If the data packet b has not been received after the reordering timer expires, the receiving end is still in the ARQ acknowledgment mode, and needs to receive the data packet b before it can be converted to the UM mode. Therefore, the receiving end feeds back the transmission failure status report to the transmitting end. Causes the sender to retransmit packet b and restart the reordering timer until packet b is received.
  • VR (H) moves downward in a clockwise direction only after the packet b before the packet C is successfully received.
  • VR (R) also follows VR (H) to move down in a clockwise direction.
  • VR (H) is the receiving upper limit of the receiving window in the AM mode, indicating that the receiving end can receive the maximum SN+1 of the data packet;
  • VR (R) is the receiving lower limit of the receiving window in the AM mode, indicating receiving The terminal can receive the minimum SN of the data packet.
  • From VR (MS) to VR (R) is the window in which the receiver sends a failure status report to the sender in AM mode.
  • From VR (R) to VR (MR) is half of the receive window.
  • Step 4g The receiving end RLC entity feeds back the second transmission mode response to the transmitting RLC entity when receiving the second transmission mode indication.
  • step 4g may also be preceded by step 3g, or step 4g and step 3g may be simultaneously entered. Row.
  • Step 5g After receiving the feedback from the receiving end RLC entity, the RLC entity responds to the first transmission mode response, and then converts from the ARQ acknowledgment mode to the UM mode.
  • Step 6g The transmitting end RLC entity does not receive the receiving end.
  • the receiving RLC entity sends a packet with the SN less than VT (MS) to the receiving RLC entity before the receiving of the data packet B is successful.
  • MS VT
  • the sender sets a size equal to the SN transmission range.
  • the half-size transmission window, the lower limit of the transmission window is the first SN corresponding to the data packet that has been sent and needs to be acknowledged without being acknowledged by the receiving end.
  • the upper limit of the transmission window is VT (MS), and the transmitting end cannot be used.
  • the SN that transmits the upper limit of the transmission window transmits a packet.
  • FIG. 12 is a schematic structural diagram of a mode conversion apparatus according to an embodiment of the present invention.
  • the mode conversion device at the transmitting end provided by this embodiment includes: a determining module 121 and an indicating module 122 and a converting module 123.
  • a determining module 121 configured to determine, before sending the data packet to the receiving end, that multiple consecutive data packets starting from the specified data packet are transmitted in an acknowledge mode
  • the indication module 122 is configured to send, by the receiving end, the first transmission mode indication to the receiving end, where the first transmission mode indication is used to instruct the receiving end to use the acknowledge mode transmission from the specified data packet; And the transmission mode adopted before the sending the first transmission mode indication is a non-acknowledgement mode, where the first transmission mode indication is further used to indicate that the receiving end converts from the non-acknowledgment mode to the acknowledge mode transmission from the specified data packet. Multiple consecutive packets.
  • the acknowledgement mode is the local acknowledgement mode
  • the receiving end is a sender bottom layer entity
  • the first transmission mode indication is further used to instruct the sender bottom layer entity to transmit feedback from the sender to the specified The result of the transmission of the plurality of consecutive data packets starting from the data packet;
  • the acknowledgement mode is the automatic repeat request acknowledgement mode
  • the receiving end is the receiving end RLC entity, and the first transmission mode indication further includes the identifier of the specified data packet.
  • the conversion module 123 is configured to: after receiving the first transmission mode response fed back by the receiving end, adopting the acknowledge mode transmission; if the non-acknowledgement mode is adopted before receiving the transmission mode indication, the non-confirmed mode is switched to the acknowledge mode.
  • FIG. 12B is a schematic structural diagram of another mode switching device according to an embodiment of the present invention.
  • the mode switching device at the receiving end provided by this embodiment includes: a receiving module 124, a response module 125, and a converting module 126.
  • the receiving module 124 is configured to receive a first transmission mode indication sent by the transmitting end transmitting entity, where the first transmission mode indication is used to indicate that the receiving end starts to adopt the acknowledge mode transmission from the designated data packet; if the first transmission is sent The mode indicates that the previously adopted transmission mode is the non-acknowledgement mode, and the first transmission mode indication is further used to instruct the receiving end to convert the specified data packet and the subsequent data of the specified data packet from the non-acknowledgment mode to the acknowledge mode. package. Further, if the acknowledgement mode is an automatic repeat request acknowledgement mode, the first transport mode indication further includes an identifier of the designated data packet.
  • the response module 125 is configured to feed back a first transmission mode response to the sending end.
  • the conversion module 126 is configured to: if the data packet before the specified data packet is received, use the acknowledge mode transmission from the specified data packet, if the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledge mode Transmitting from a non-acknowledgment mode to an acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet;
  • the conversion module 126 is further configured to: if the data packet before the specified data packet has not been received, the receiving end starts a reordering event, after the reordering event is triggered, or before the reordering event is triggered, confirming that the designation has been received.
  • the data packet before the data packet the receiving end starts to transmit in the acknowledgment mode from the specified data packet, and if the transmission mode adopted before receiving the first transmission mode indication is the non-acknowledge mode, the non-acknowledge mode is switched to the acknowledgment mode transmission.
  • FIG. 13A is a schematic structural diagram of still another mode switching device according to an embodiment of the present invention. As shown
  • the mode switching device at the transmitting end includes: a determining module 131, a sending module 132, and a converting module 133.
  • the determining module 131 is configured to determine, before sending the data packet to the receiving end, that the plurality of consecutive data packets starting from the specified data packet are transmitted in the unacknowledged mode.
  • the sending module 132 is configured to send, by the receiving end, the second transmission mode indication to the receiving end, where the second transmission mode indication is used to indicate the receiving end from the designated data packet. Start adopting non-acknowledgment mode transmission; if the transmission mode adopted before transmitting the second transmission mode indication is an acknowledgment mode, the second transmission mode indication is further used to indicate that the receiving end converts from the acknowledgment mode to the non-acknowledge mode transmission. A plurality of consecutive data packets starting from the specified data packet.
  • the receiving end is a sender bottom layer entity; if the acknowledge mode is an automatic repeat request acknowledgement mode, the receiving end is a receiving end RLC entity, and the second transmission
  • the mode indication also includes an identification of the specified data packet.
  • the conversion module 133 is configured to: after receiving the second transmission mode response fed back by the receiving end, transmit in a non-acknowledge mode; if the acknowledge mode is adopted before receiving the transmission mode indication, the mode is changed from the confirm mode to the non-acknowledge mode. .
  • the embodiment further includes: a limiting module, configured to send the data packet whose serial number is within the specified range before the receiving of the data packet before receiving the specified data packet is received.
  • FIG. 13B is a schematic structural diagram of still another mode switching apparatus according to an embodiment of the present invention.
  • the mode switching device at the receiving end provided by this embodiment includes: a receiving module 134 and a response module 135, and a converting module 136.
  • the receiving module 134 is configured to receive a second transmission mode indication sent by the transmitting end transmitting entity, where the second transmission mode indication is used to indicate that the receiving end starts to use the unacknowledged mode transmission from the designated data packet;
  • the transmission mode indicates that the previously adopted transmission mode is the acknowledgment mode, and the second transmission mode indication is further used to indicate that the receiving end converts the acknowledgment mode to the non-acknowledge mode to transmit a plurality of consecutive data packets starting from the specified data packet;
  • the response module 135 is configured to feed back the first transmission mode response to the sending end.
  • the second transport mode indication further includes an identifier of the designated data packet.
  • the conversion module 136 is configured to: if receiving the data packet before the specified data packet, the receiving end starts to transmit in the unacknowledged mode from the specified data packet, if the transmission mode used before receiving the second transmission mode indication is Acknowledge mode, transferring from the acknowledgment mode to the non-acknowledgment mode, transmitting a plurality of consecutive data packets starting from the specified data packet;
  • the conversion module is further configured to: if the data packet before the specified data packet is not received, the receiving end starts a reordering event, and confirms that the specified data has been received before the reordering event is triggered a packet before the packet, using the unacknowledged mode transmission from the specified data packet, and if the transmission mode adopted before receiving the second transmission mode indication is an acknowledgment mode, the conversion from the acknowledgment mode to the non-acknowledgment mode is performed. Specifying a plurality of consecutive data packets starting from the data packet; if the data packet before the specified data packet has not been received after the reordering event is triggered, feeding back a transmission failure status report to the transmitting end, so that the transmitting end retransmission is not received. The packet, and restart the reordering event.
  • the third embodiment provides a data retransmission method in the acknowledge mode in the prior art in the process of using the acknowledge mode transmission, in which the PDUs that need to be retransmitted are not sorted.
  • the transmitting end transmitting entity has no limitation on the transmission order of the retransmitted PDUs, and the transmission order may be arbitrary.
  • the receiving end RLC entity can deliver the PDU that is larger than the RLC PDU only after receiving the first RLC PDU that is not received. Therefore, the implementation of the prior art may cause the receiving end to buffer the received data. Long, which in turn leads to longer data transmission delays in the air interface.
  • FIG. 10 is a flowchart of a data retransmission method in an acknowledge mode according to an embodiment of the present invention. As shown in FIG. 10, this embodiment includes:
  • Step 101 The transmitting end transmitting entity receives a transmission failure report from the receiving entity.
  • the RLC entity receives the RLC SDU from the upper layer, encapsulates the received RLC SDU into an RLC PDU, and delivers it to the MAC layer entity for transmission.
  • the transmitting end RLC entity reports the transmission failure reported by the receiving end entity, for example, in the ARQ acknowledgment mode, receiving the transmission failure report fed back by the receiving end RLC entity; in the local acknowledgment mode, receiving the feedback from the transmitting MAC entity Transmission failure report.
  • Step 102 The transmitting end transmitting entity determines, according to the transmission failure report, a PDU that fails to be transmitted.
  • Step 103 The transmitting end transmitting entity resends the PDU that failed to transmit or the PDU that corresponds to the PDU that failed to transmit to the sending MAC entity, so that the priority of the PDU that failed to transmit is higher than that of the PDU that failed to be transmitted later.
  • the transmitting end transmitting entity resends the PDU that failed to transmit or the PDU that corresponds to the PDU that failed to transmit to the sending MAC entity, so that the PDU with the failed transmission has a higher priority than the PDU that failed to be transmitted.
  • the RLC submits the retransmitted data packet to the MAC layer entity for data retransmission in the retransmission order.
  • the step 103 may be: the transmitting end transmitting entity identifies the SDU corresponding to the PDU that failed to be transmitted, and reassembles the SDU corresponding to the PDU that failed to transmit to the sending MAC entity according to the receiving sequence of the SDU that failed to be transmitted.
  • the new PDU is configured such that the SDU with the transmission failure first received from the upper entity has a higher SDU than the transmission failure received from the upper entity.
  • FIG. 14 is a schematic structural diagram of a data packet retransmission apparatus in an acknowledge mode according to an embodiment of the present invention. As shown in FIG. 14, the embodiment includes: a report receiving module 141, an identifying module 142, and a retransmission module 143.
  • the report receiving module 141 is configured to receive a transmission failure report from the receiving entity, and the identification module 142 is configured to determine, according to the transmission failure report, a PDU that fails to be transmitted; and the retransmission module 143 is configured to re-send to the sending MAC entity.
  • a PDU that fails to transmit a transmission or a PDU that corresponds to a PDU that fails to transmit transmits a PDU whose transmission fails to be higher than a PDU that fails to be transmitted after the transmission.
  • the SDU corresponding to the PDU that failed to be transmitted is identified, and the new PDU assembled by the SDU corresponding to the PDU that failed to be transmitted is sent to the sender MAC entity in the order of receiving the SDU from the uplink entity.
  • the SDU with the transmission failure received by the upper entity has a higher priority than the SDU of the transmission failure received from the upper entity.

Landscapes

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

Abstract

本发明实施例提供一种数据包发送方法、模式转换方法及装置。该数据包发送方法包括:发送端实体从上层实体接收数据包;根据上层实体的传输模式指示信息或所述数据包中的传输模式指示信息,发送端实体判断所述数据包的传输模式;所述传输模式指示信息根据所述数据包的传输要求设定;若所述数据包的传输模式为确认模式,发送端实体采用确认模式向接收端发送所述数据包;若所述数据包的传输模式为非确认模式,发送端实体采用非确认模式向接收端发送所述数据包。本发明实施例在同一承载层可采用不同的模式传输不同的数据包。

Description

数据包发送方法、 模式转换方法及装置 本申请要求于 2012 年 3 月 19 日提交中国专利局、 申请号为 201210072939.X, 发明名称为 "数据包发送方法、 模式转换方法及装置" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明实施例涉及通信技术, 尤其涉及一种数据包发送方法、 模式转 换方法及装置。 发明背景
现有 EPS(Evolved Packet System, 演进分组系统)中, 采用承载 ( Bearer )来传输用户设备 ( User Equipment, UE ) 的业务数据, 按照在承 载中的业务数据所经过的网络的不同,承载包含核心网(Core Network, CN) 承载部分和无线接入网 (Radio Access Network, RAN)承载部分。
对于某一个特定的业务, RAN承载 (Radio Bearer, RB)在无线链路控 制(Radio Link Control , RLC) 层可以采用两种传输模式: 确认模式 (Acknowledged Mode , AM,)和非确认模式 (Un-acknowledged mode, UM)。 在 AM模式下, RLC层采用自动重传请求 (Automatic Repeat-reQuest, ARQ) 机制传输业务数据, 接收端会对发送端所发送出的每一个数据包进行成功 接收确认, 以表示该数据包被正确接收, 如果某数据包没有被接收端成功 确认、 或确认丢失, 则发送端重新发送对应的数据包, 该模式应用于对时 延要求较低, 而对可靠性要求较高的业务传输; 在 UM模式下, RLC层 只负责发送和接收数据包, 并不对所发送的数据包进行重传, 也不对所接 收的数据包反馈确认。 相对于 AM模式, UM模式主要应用于对时延要求 较高, 对可靠性要求较低的业务。 现有网络中同一业务中不同类型的数据包均采用相同的模式进行传 输, 不能对同一业务的不同数据包采用不同的传输模式, 例如同一业务的 部分数据采用确认模式传输而其它数据包采用非确认模式传输。 然而现有 的业务中, 对属于同一个业务的不同数据包, 其所需要的可靠性和时延并 不一致。 对于该种类型的业务, 如果采用 AM模式传输, 则可能过度保障 了业务中对可靠性要求较低的业务数据的传输可靠性, 而增加了对时延要 求较高的业务数据的传输时延; 如果采用 UM模式传输则可能降低了对可 靠性要求较高的业务数据的传输可靠性, 而过度保障了对时延要求较低的 业务数据包的传输时延。 发明内容
本发明实施例提供一种数据包发送方法、 模式转换方法及装置, 用以 解决现有传输模式在同一承载层只能采用同一种传输模式传输所有数据包 的缺陷。
一方面, 本发明实施例提供一种数据包发送方法, 包括:
发送端传输实体从上层实体接收数据包;
根据上层实体的传输模式指示信息或所述数据包中的传输模式指示信 息, 发送端传输实体判断所述数据包的传输模式; 所述传输模式指示信息 根据所述数据包的传输要求设定;
若所述数据包的传输模式为确认模式, 发送端传输实体采用确认模式 向接收端发送所述数据包;
若所述数据包的传输模式为非确认模式, 发送端传输实体采用非确认 模式向接收端发送所述数据包。
一方面, 本发明实施例提供一种数据包发送装置, 包括:
接收模块, 用于从上层实体接收待发送的数据包;
模式确定模块, 用于根据所述上层实体下发的传输模式指示信息或所 述数据包中的传输模式指示信息, 判断所述数据包的传输模式; 所述传输 模式指示信息根据所述数据包的传输要求设定;
确认传输模块, 用于若所述数据包的传输模式为确认模式, 采用确认 模式向接收端发送所述数据包;
非确认传输模块, 用于若所述数据包的传输模式为非确认模式, 采用 非确认模式向接收端发送所述数据包。
一方面, 本发明实施例提供一种参数配置方法, 包括:
基站向终端发送混合传输模式配置参数, 包括混合传输模式标识和传 输参数, 所述混合传输模式配置参数用于指示所述终端中所述 RLC实体标 识对应的 RLC实体根据 RLC承载层中数据包的传输要求采用确认模式或非 确认模式传输所述数据包;
终端根据混合传输模式配置参数配置所述接收 RLC 实体标识对应的 RLC实体。
一方面, 本发明实施例提供一种参数配置装置, 用于向终端发送混合 传输模式配置参数, 包括混合传输模式标识和传输参数, 所述混合传输模 式配置参数用于指示所述终端中所述 RLC实体标识对应的 RLC实体根据 RLC承载层中数据包的传输要求采用确认模式或非确认模式传输所述数据 包。
本实施例提供的数据包发送方法,发送端 RLC实体向接收端发送数据 包之前, 先根据所述数据包的传输模式指示信息判断数据包的传输模式, 根据传输模式指示信息所指示的传输模式向接收端发送数据包。 数据包的 传输模式指示信息根据所述数据包的传输要求而设置, 例如将传输可靠性 要求较高或传输时延要求较低的数据包设置为确认模式传输, 将对传输可 靠性要求较低或传输时延要求较高的数据包设置为非确认模式传输。 因此, 本实施例在同一承载层可根据不同数据包的传输模式指示信息对不同数据 包采用不同的传输模式, 从而可满足同一业务中不同数据包的传输特性。 另一方面, 本发明实施例一种模式转换方法, 包括:
发送端传输实体向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用确认模式传输;
发送端传输实体向接收端发送该指定数据包之前, 向接收端发送第一 传输模式指示, 所述第一传输模式指示用于指示接收端从该指定数据包开 始采用确认模式传输; 如果在发送所述第一传输模式指示之前所采用的传 输方式为非确认模式, 则所述第一传输模式指示还用于指示接收端从非确 认模式转换为确认模式传输从所述指定数据包开始的多个连续数据包; 发送端传输实体接收到接收端反馈的第一传输模式响应之后, 采用确 认模式传输; 如果在接收到该传输模式指示之前, 采用的是非确认模式, 则从非确认模式转换为确认模式。
另一方面, 本发明实施例提供一种模式转换装置, 包括:
确定模块, 用于向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用确认模式传输;
指示模块, 用于向接收端发送该指定数据包之前, 向接收端发送第一 传输模式指示, 所述第一传输模式指示用于指示接收端从该指定数据包开 始采用确认模式传输; 如果在发送所述第一传输模式指示之前所采用的传 输方式为非确认模式, 则所述第一传输模式指示还用于指示接收端从非确 认模式转换为确认模式传输从所述指定数据包开始的多个连续数据包; 转换模块, 用于接收到接收端反馈的第一传输模式响应之后, 采用确 认模式传输; 如果在接收到该传输模式指示之前, 采用的是非确认模式, 则从非确认模式转换为确认模式。
另一方面, 本发明实施例提供一种模式转换方法, 包括:
接收端接收发送端传输实体发送的第一传输模式指示, 所述第一传输 模式指示用于指示接收端从该指定数据包开始采用确认模式传输; 如果在 发送所述第一传输模式指示之前所采用的传输方式为非确认模式, 则所述 第一传输模式指示还用于指示接收端从非确认模式转换为确认模式传输所 述指定数据包和所述指定数据包的后续数据包;
接收端向发送端反馈第一传输模式响应;
如果接收到所述指定数据包之前的数据包, 接收端从该指定数据包开 始采用确认模式传输, 如果在接收所述第一传输模式指示之前所采用的传 输方式为非确认模式, 接收端从非确认模式转换为确认模式传输从所述指 定数据包开始的多个连续数据包;
如果还没有接收到所述指定数据包之前的数据包, 接收端启动重排序 事件, 在重排序事件触发之后, 或, 重排序事件触发之前确认已接收到所 述指定数据包之前的数据包, 接收端从该指定数据包开始采用确认模式传 输, 如果在接收所述第一传输模式指示之前所采用的传输方式为非确认模 式, 接收端从非确认模式转换为确认模式传输从所述指定数据包开始的多 个连续数据包。
另一方面, 本发明实施例提供一种模式转换装置, 包括:
接收模块, 用于接收发送端传输实体发送的第一传输模式指示, 所述 第一传输模式指示用于指示接收端从该指定数据包开始采用确认模式传 输; 如果在发送所述第一传输模式指示之前所采用的传输方式为非确认模 式, 则所述第一传输模式指示还用于指示接收端从非确认模式转换为确认 模式传输所述指定数据包和所述指定数据包的后续数据包;
响应模块, 用于向发送端反馈第一传输模式响应;
转换模块, 用于如果接收到所述指定数据包之前的数据包, 从该指定 数据包开始采用确认模式传输, 如果在接收所述第一传输模式指示之前所 采用的传输方式为非确认模式, 从非确认模式转换为确认模式传输从所述 指定数据包开始的多个连续数据包;
转换模块, 还用于如果还没有接收到所述指定数据包之前的数据包, 接收端启动重排序事件, 在重排序事件触发之后, 或, 重排序事件触发之 前确认已接收到所述指定数据包之前的数据包, 接收端从该指定数据包开 始采用确认模式传输, 如果在接收所述第一传输模式指示之前所采用的传 输方式为非确认模式, 从非确认模式转换为确认模式传输从所述指定数据 包开始的多个连续数据包。
本发明实施例提供的模式转换方法和装置, 发送端在发送数据包的过 程中, 通过向接收端发送第一传输模式指示, 指示使接收端开始采用确认 模式传输从指定数据包开始的多个连续数据包, 如果在所述第一传输模式 指示之前所采用的传输方式为非确认模式, 则还指示接收端从非确认模式 转换为确认模式传输从所述指定数据包开始的多个连续数据包。 因此, 本 实施例可采用不同的模式传输不同的数据包,
另一方面, 本发明实施例提供一种模式转换方法, 包括:
发送端传输实体向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用非确认模式传输;
发送端传输实体向接收端发送该指定数据包之前, 向接收端发送第二 传输模式指示, 所述第二传输模式指示用于指示接收端从该指定数据包开 始采用非确认模式传输; 如果在发送所述第二传输模式指示之前所采用的 传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确认 模式转换为非确认模式传输从所述指定数据包开始的多个连续数据包; 发送端传输实体接收到接收端反馈的第二传输模式响应之后, 采用非 确认模式传输; 如果在接收到该传输模式指示之前, 采用的是确认模式, 则从确认模式转换为非确认模式。
另一方面, 本发明实施例提供一种模式转换装置, 包括:
确定模块, 用于向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用非确认模式传输;
发送模块, 用于向接收端发送该指定数据包之前, 向接收端发送第二 传输模式指示, 所述第二传输模式指示用于指示接收端从该指定数据包开 始采用非确认模式传输; 如果在发送所述第二传输模式指示之前所采用的 传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确认 模式转换为非确认模式传输从所述指定数据包开始的多个连续数据包; 转换模块, 用于接收到接收端反馈的第二传输模式响应之后, 采用非 确认模式传输; 如果在接收到该传输模式指示之前, 采用的是确认模式, 则从确认模式转换为非确认模式
另一方面, 本发明实施例提供一种模式转换方法, 包括:
接收端接收发送端传输实体发送的第二传输模式指示, 所述第二传输 模式指示用于指示接收端从该指定数据包开始采用非确认模式传输; 如果 在发送所述第二传输模式指示之前所采用的传输方式为确认模式, 则所述 第二传输模式指示还用于指示接收端从确认模式转换为非确认模式传输从 所述指定数据包开始的多个连续数据包;
向发送端反馈第二传输模式响应;
如果接收到所述指定数据包之前的数据包, 接收端从该指定数据包开 始采用非确认模式传输, 如果在接收所述第二传输模式指示之前所采用的 传输方式为确认模式, 接收端从确认模式转换为非确认模式传输从所述指 定数据包开始的多个连续数据包;
如果没有接收到所述指定数据包之前的数据包, 接收端启动重排序事 件, 重排序事件触发之前确认已接收到所述指定数据包之前的数据包, 接 收端从该指定数据包开始采用非确认模式传输, 如果在接收所述第二传输 模式指示之前所采用的传输方式为确认模式, 接收端从确认模式转换为非 确认模式传输从所述指定数据包开始的多个连续数据包; 如果重排序事件 触发之后, 还未接收到所述指定数据包之前的数据包, 向发送端反馈发送 失败状态报告使所述发送端重传未接收到的数据包, 并重新启动重排序事 件。
另一方面, 本发明实施例提供一种模式转换装置, 包括: 接收模块, 用于接收发送端传输实体发送的第二传输模式指示, 所述 第二传输模式指示用于指示接收端从该指定数据包开始采用非确认模式传 输; 如果在发送所述第二传输模式指示之前所采用的传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确认模式转换为非确认模式 传输从所述指定数据包开始的多个连续数据包;
响应模块, 用于向发送端反馈第二传输模式响应;
转换模块, 用于如果接收到所述指定数据包之前的数据包, 接收端从 该指定数据包开始采用非确认模式传输, 如果在接收所述第二传输模式指 示之前所采用的传输方式为确认模式, 从确认模式转换为非确认模式传输 从所述指定数据包开始的多个连续数据包;
所述转换模块,还用于如果没有接收到所述指定数据包之前的数据包, 接收端启动重排序事件, 重排序事件触发之前确认已接收到所述指定数据 包之前的数据包, 从该指定数据包开始采用非确认模式传输, 如果在接收 所述第二传输模式指示之前所采用的传输方式为确认模式, 从确认模式转 换为非确认模式传输从所述指定数据包开始的多个连续数据包; 如果重排 序事件触发之后, 还未接收到所述指定数据包之前的数据包, 向发送端反 馈发送失败状态报告使所述发送端重传未接收到的数据包, 并重新启动重 排序事件。
本发明实施例提供的模式转换方法和装置, 发送端在发送数据包的过 程中, 通过向接收端发送第二传输模式指示, 指示使接收端开始采用非确 认模式传输从指定数据包开始的多个连续数据包, 如果在所述第二传输模 式指示之前所采用的传输方式为确认模式, 则还指示接收端从确认模式转 换为非确认模式传输从所述指定数据包开始的多个连续数据包。 因此, 本 实施例可采用不同的模式传输不同的数据包。
又一方面, 本发明实施例提供一种确认模式下的数据重传方法, 包括: 发送端传输实体接收来自接收端实体反馈的传输失败报告; 发送端传输实体根据所述传输失败报告确定传输失败的 PDU;
发送端传输实体重新向发送端 MAC实体下发传输失败的 PDU或传输 失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高于后 生成的传输失败的 PDU; 或者,
发送端传输实体识别传输失败的 PDU对应的 SDU, 按照传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实体下发传输失败 的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实体接收到的传输 失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
又一方面, 本发明实施例提供一种确认模式下的数据包重传装置, 包 括:
报告接收模块, 用于接收来自接收端实体反馈的传输失败报告; 识别模块, 用于根据所述传输失败报告确定传输失败的 PDU;
重传模块, 用于重新向发送端 MAC实体下发传输失败的 PDU或传输 失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高于后 生成的传输失败的 PDU。 或者, 识别传输失败的 PDU对应的 SDU, 按照 传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实体下 发传输失败的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实体接 收到的传输失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
本发明实施例提供一种确认模式下的数据包重传方法和装置, 对重传 的 PDU按照生成顺序进行排序, 使得先生成的 PDU在传输失败时能优先 重传,从而早到达接收端,使接收端可以提交该 PDU之后已接收到的 PDU, 从而减少了接收端緩存已接收到的 PDU的时间。 附图简要说明
图 1为本发明实施例提供的一种数据包发送方法流程图; 图 2为本发明实施例提供的另一种数据包发送方法流程图;
图 3A为本发明实施例提供的又一种数据包发送方法流程图;
图 3B为本发明实施例提供的再一种数据包发送方法流程图;
图 3C为本发明实施例提供的一种 SDU重传示意图;
图 3D为本发明实施例提供的再一种数据包发送方法流程图;
图 3E为本发明实施例提供的一种 PDU重传示意图;
图 4为本发明实施例提供的再一种数据包发送方法流程图;
图 5为本发明实施例提供的再一种数据包发送方法流程图;
图 6为本发明实施例提供的再一种数据包发送方法流程图;
图 7A为本发明实施例提供的一种模式转换方法流程图;
图 7B为本发明实施例提供的另一种模式转换方法流程图
图 8A为本发明实施例提供的又一种模式转换方法流程图;
图 8B为本发明实施例提供的一种模式转换示意图;
图 9A为本发明实施例提供的再一种模式转换方法流程图;
图 9B为本发明实施例提供的再一种模式转换方法流程图;
图 9C为本发明实施例提供的再一种模式转换方法流程图;
图 10为本发明实施例提供的一种确认模式下的数据重传方法流程图; 图 11 A为本发明实施例提供的一种数据包发送装置结构示意图; 图 11B为本发明实施例提供的另一种数据包发送装置结构示意图; 图 12A为本发明实施例提供的一种模式转换装置结构示意图; 图 12B为本发明实施例提供的另一种模式转换装置结构示意图; 图 13A为本发明实施例提供的又一种模式转换装置结构示意图; 图 13B为本发明实施例提供的再一种模式转换装置结构示意图; 图 14为本发明实施例提供的一种确认模式下的数据包重传装置结构示 意图。 实施本发明的方式 实施例一
图 1为本发明实施例提供的一种数据包发送方法流程图。 如图 1所示, 本实施例提供的数据包发送方法包括: 步骤 11 : 发送端传输实体从上层实体接收待发送的数据包。
发送端传输实体可以是发送端 RLC 实体, 分组数据汇聚协议 (Packet Data Convergence Protocol, PDCP)实体, 或无线资源控制 ( Radio Resource Control, RRC )实体,或其他传输协议,例如,互联网协议 (Internet Protocol, IP)等。 从上层实体接收的数据包可以是无线链路控制业务数据单元 (Radio Link Control Service Data Unit, RLC SDU)。
步骤 12: 根据所述上层实体下发的传输模式指示信息或所述数据包中 的传输模式指示信息, 发送端传输实体判断所述数据包的传输模式。 其中, 所述传输模式指示信息根据所述数据包的传输要求设置。
所述数据包的传输模式指示信息可以由上层实体通过层间消息通知发 送端 RLC实体, 例如可以是 PDCP 实体的层间消息或 RRC 的层间消息。 另外, 所述数据包的传输模式指示信息也可以由上层实体通过所述数据包 所包括的指示位携带给发送端 RLC实体。 传输模式指示信息所述数据包的 传输要求设置, 例如所述数据包的传输可靠性要求和时延要求等优先级信 息。 如果所述数据包对传输可靠性要求较高或传输时延要求较低, 所述数 据包的传输模式指示信息可以设置所述数据包的传输模式为确认模式。 如 果所述数据包对传输可靠性要求较低或传输时延要求较高, 所述数据包的 传输模式指示信息可以设置所述数据包的传输模式为非确认模式。 举例来 说, 如果影响业务时延的重要数据包传输失败会使业务中断, 例如视频业 务中初始化分片 (Initialization Segment )丢失, 终端无法播放视频, 会导致 用户观看视频的等待时间延长。 因此, 为保证影响业务时延的重要数据包 的传输可靠性, 可采用确认模式传输影响业务时延的重要数据包。
步骤 13: 若所述数据包的传输模式为确认模式, 发送端传输实体采用 确认模式向接收端发送所述数据包; 若所述数据包的传输模式为非确认模 式, 发送端传输实体采用非确认模式发送所述数据包。
若所述数据包的传输模式为确认模式, 发送端传输实体向发送端媒体 访问控制 (Media Access Control, MAC ) 实体下发所述数据包后, 所述发 送端传输实体接收来自接收端反馈的所述数据包的传输状态报告。 若根据 所述数据包的传输状态报告确定所述数据包传输失败, 发送端传输实体重 新向发送端 MAC实体下发所述数据包, 以使发送端 MAC实体重新向接收 端 MAC实体发送所述数据包。 本实施例提供的数据包发送方法, 发送端传输实体向接收端发送数据 包之前, 先根据所述数据包的传输模式指示信息判断数据包的传输模式, 根据传输模式指示信息所指示的传输模式向接收端发送数据包。 数据包的 传输模式指示信息根据所述数据包的传输要求而设置, 例如将传输可靠性 要求较高或传输时延要求较低的数据包设置为确认模式传输, 将对传输可 靠性要求较低或传输时延要求较高的数据包设置为非确认模式传输。 因此, 本实施例在同一承载层可根据不同数据包的传输模式指示信息对不同数据 包采用不同的传输模式, 从而可满足同一业务中不同数据包的传输特性。
图 2、图 3A至图 3D对应实施例中采用本地确认模式传输指定数据包。 在本地确认模式中, 发送端 RLC实体根据发送端 MAC实体反馈的传输状 态报告判断数据包是否传输失败, 从而确定是否重传该数据包。
图 2为本发明实施例提供的另一种数据包发送方法流程图。 如图 2所 示, 本实施例提供的采用本地确认模式发送数据包的方法包括:
步骤 21: 发送端 RLC实体从上层实体接收数据包。
步骤 22: 根据所述数据包的传输模式指示信息, 发送端 RLC实体判断 所述数据包的传输模式; 所述传输模式指示信息根据所述数据包的传输要 求设置。
步骤 23: 发送端 RLC实体向发送端 MAC实体下发所述数据包后, 若 所述数据包的传输模式为本地确认模式, 所述发送端 RLC实体接收所述发 送端 MAC实体反馈的、 来自接收端 MAC实体的所述数据包的传输状态报 告。
发送端 RLC实体向发送端 MAC实体下发所述数据包后, 若所述数据 包的传输模式为本地确认模式, 所述发送端 RLC实体或 RRC实体可以向 发送端 MAC实体发送所述数据包的发送结果反馈指示, 以使所述 MAC实 体接收到所述接收端 MAC 实体发送的所述数据包的传输状态报告后向所 述发送端 RLC实体反馈。 发送结果信息为来自接收端 MAC实体的对所述 数据包的接收成功信息或接收失败信息、 例如返回 ACK, 表示接收端成功 接收数据包。 返回 NACK表示接收端接收数据包失败。 发送端 MAC实体 接收到接收端 MAC实体返回的传输状态报告后,将所述传输状态报告反馈 给对应的发送端 RLC实体。 发送端 RLC传输状态报告实体可根据发送端 MAC实体反馈的传输状态报告, 确定对应的数据包传输失败或成功。 步骤 24:若根据所述数据包的传输状态报告确定所述数据包传输失败, 发送端 RLC 实体重新向发送端 MAC 实体下发所述数据包, 以使发送端 MAC实体重新向接收端 MAC实体发送所述数据包。
若根据所述数据包的传输状态报告确定所述数据包传输成功, 发送端 RLC实体可以丢弃所述数据包, 而不再向发送端 MAC实体下发所述数据 包。
本实施例提供的数据包发送方法, 发送端 RLC实体向发送端 MAC实 体下发数据包后, 在该数据包的传输模式为本地确认模式时, 发送端 RLC 实体可接收到发送端 MAC实体反馈的、 来自接收端 MAC实体的该数据包 的传输状态报告。 在根据传输状态报告确定该数据包传输失败时, 发送端 RLC实体重新向发送端 MAC实体下发该数据包,以使发送端 MAC实体重 新向接收端 MAC实体发送该数据包。因此可满足该数据包的传输高可靠性 要求, 从而满足数据包传输可靠性高的要求。
图 3A为本发明实施例提供的又一种数据包发送方法流程图。本实施例 以本地确认模式传输数据包, 主要说明发送失败时的处理。 如图 3A所示, 本实施例提供的数据包发送方法包括:
步骤 la: 发送端 RLC 实体接收到来自上层实体的 RLC SDU;
步骤 2a: 发送端 RLC 实体依据上层实体的传输模式指示信息、 或该 RLC SDU中的传输模式指示信息,确定 RLC SDU执行本地确认模式传输; 步骤 2a中的上层实体可以是 PDCP或 RRC实体。
步骤 3a: 发送端 MAC实体执行调度功能, 获取发送数据所需资源; 步骤 4a: 发送端 MAC 实体为该发送端 RLC 实体所要发送的 RLC SDU分配资源, 并根据资源大小向 RLC实体获取 RLC PDU ( Packet Data Unit, 协议数据单元)。
步骤 5a: 发送端 RLC实体按照 MAC所提供的资源封装 RLC PDU; 步骤 6a: 发送端 RLC实体将封装的 RLC PDU递交给 MAC实体; 步骤 7a: 发送端 RLC实体向发送端 MAC实体发送所述 RLC PDU的 发送结果反馈指示, 使所述 MAC实体接收到所述接收端 MAC实体发送的 所述数据包的传输失败指示或传输成功指示后向所述 RLC实体反馈。
可选地, 在步骤 7a 中也可由 RRC 实体向发送端 MAC 实体发送各 RLC PDU的发送结果反馈指示,使所述 MAC实体接收到所述接收端 MAC 实体发送的所述数据包的传输失败指示或传输成功指示后向所述 RLC实体 反馈。
步骤 8a: 发送端 MAC 实体将一个或多个逻辑信道组的 RLC PDU 复 用成为 MAC PDU;
步骤 9a: 发送端 MAC 实体通过 HARQ进程 /实体传输 MAC PDU; 步骤 10a:发送端 MAC实体接收来自接收端 MAC实体的该 MAC PDU 的传输状态报告。
本实施例中接收端 MAC实体发送的传输状态报告表示对应 MAC PDU 传输失败, 例如可以是 NACK反馈。
步骤 11a:发送端 MAC 实体向该 MAC PDU 中所包含的 RLC PDU所 对应的 RLC实体反馈该 RLC PDU的传输状态报告。
步骤 12a: 发送端 RLC实体依据 MAC实体反馈的传输状态报告识别 出传输失败的 RLC SDIL
步骤 13a:发送端 RLC 实体更新传输顺序,使得传输失败的 RLC SDU 具有发送优先级高于首次发送的 RLC SDU的发送优先级。
例如,发送端 RLC实体将传输失败的 RLC SDU按照从上层实体的接 收顺序,放入 RLC SDU 重传队列, RLC SDU 重传队列中数据传输的优先 级高于其他緩存的 SDU 的传输优先级。 或者, RLC 可将待发送的 RLC SDU标记为没有发送过或需要重新发送,在后续发送过程中按照 RLC SDU 的标记优先发送需要重新发送的 RLC SDU。
图 3B为本发明实施例提供的再一种数据包发送方法流程图。本实施例 提供的数据包发送方法适用于采用 SDU形式重传数据包的场景。 如图 3B 所示, 本实施例提供的数据包发送方法包括:
步骤 lb: 发送端 RLC 实体依据发送端 MAC 实体的反馈, 识别出传 输失败的 RLC SDIL
步骤 2b: 发送端 RLC 实体更新传输顺序, 使传输失败的 RLC SDU的 发送优先级高于首次发送的 RLC SDU的发送优先级。
步骤 3b: 发送端 MAC执行调度功能, 获取发送数据所需资源。
步骤 4b: 发送端 MAC实体为所待发送的 RLC SDU分配资源, 并根据 资源大小向 RLC实体获取 RLC PDIL
步骤 5b: 发送端 RLC 实体按照发送端 MAC 实体所提供的资源封装 RLC SDU, 如果存在需要重传的 RLC SDU, 发送端 RLC实体优先将重传 的 RLC SDU封装成 RLC PDU。
进一步, 如果存在多个需要重传的 RLC SDU, 发送端 RLC实体优先 将重传的 RLC SDU, 按照从上层实体的接收顺序封装成 RLC PDIL
如图 3C所示, RLC SDU1被封装成 RLC PDU1和 RLC PDU2, RLC SDU2被封装成 RLC PDU2和 RLC PDU3。其中, RLC PDU2包含部分 RLC SDU1的数据, 又包含部分 RLC SDU2 的数据。 在接收 RLC PDU2丢失的 NACK指示后, 采用 RLC SDU的重传时, 则先前传输的 RLC SDU1 和 RLC SDU2在接收端不能被完整组装而被丢弃, 接收端 MAC实体只有在 RLC PDUl、 RLC PDU2和 RLC PDU3全部接收成功后, 才进行完整组装并 向接收端 RLCP实体递交。发送端 RLC 实体采用 RLC SDU的重传时, RLC SDU1被重新封装成 RLC PDU4和 RLC PDU5, RLC SDU2被重新封装成 RLC PDU5和 RLC PDU6。
步骤 6b: 发送端 RLC 实体将封装的 RLC PDU递交给发送端 MAC 实体;
步骤 7b: 发送端 MAC实体将一个或多个逻辑信道组的 RLC PDU 复 用成为 MAC PDU;
步骤 8b: 发送端 MAC实体通过 HARQ进程 /实体传输 MAC PDU; 步骤 9b:发送端 MAC实体接收来自接收端 MAC实体的该 MAC PDU 的传输状态报告。
本实施例中接收端 MAC实体发送的传输状态报告表示对应 MAC PDU 传输成功, 例如可以是 ACK反馈。
步骤 10b:发送端 MAC 实体向该 MAC PDU 中所包含的 RLC PDU所 对应的 RLC实体反馈该 RLC PDU的传输状态报告。
步骤 lib: 发送端 RLC实体接收到该 RLC PDU传输成功的指示后, 丢弃该 RLC PDU, 释放该 RLC PDU的緩存资源。
图 3D为本发明实施例提供的再一种数据包发送方法流程图。本实施例 提供的数据包发送方法适用于采用 PDU重传数据包的场景。如图 3D所示, 本实施例提供的数据包发送方法包括:
步骤 lc: 发送端 RLC 实体依据发送端 MAC 实体的反馈, 识别出传 输失败的 RLC PDIL 步骤 2c: 发送端 RLC实体更新传输顺序, 使得传输失败的 RLC PDU 具有发送优先级高于首次发送的 RLC PDU的发送优先级,
步骤 3c: 发送端 MAC执行调度功能, 获取发送数据所需资源。
步骤 4c: 发送端 MAC实体为待发送的 RLC SDU获取资源, 并根据资 源大小向 RLC实体获取 RLC PDIL
步骤 5c: 发送端 RLC 实体按照发送端 MAC 实体所提供的资源封装 RLC SDU。
步骤 6c: 发送端 RLC实体将封装的 RLC PDU递交给发送端 MAC实 体; 如果存在需要重传的 RLC PDU, 优先将重传的 RLC PDU递交给发送 端 MAC实体。
进一步, 如果存在多个需要重传的 RLC PDU, 按照传输失败的 PDU 的生成顺序, 例如 SN (序列号, Sequence Number)递增顺序, 重新向发送端 MAC实体下发传输失败的 PDU或传输失败的 PDU对应的分段 PDU,使先 生成的传输失败的 PDU优先级高于后生成的传输失败的 PDU。
如图 3E所示, RLC SDU1被封装成 RLC PDU1和 RLC PDU2, RLC SDU2被封装成 RLC PDU2和 RLC PDU3。其中, RLC PDU2包含部分 RLC SDU1的数据, 又包含部分 RLC SDU2 的数据。 在接收 RLC PDU2丢失的 NACK指示后, 采用 RLC PDU的重传时, 发送端 MAC实体只重传 RLC PDU2, 而不需要重传 RLC SDU1 中已经传输成功的 RLC PDU1和 RLC SDU2已经传输成功的 RLC PDU3。 而如图 3C所示, 采用 RLC SDU的重 传时,发送端 MAC实体需重传 RLC PDU1的全部 PDU和 RLC PDU2和全 部 PDU。 采用 RLC SDU的重传时, 应该先接收到的 SDU, 可能由于重传 而后到达 PDCP层, 而为了保证 PDCP可以将数据包按序递交给更上层, 因此 PDCP需要依数据包中所携带的 SN对接收到的数据包进行排序;因 此, 采用 PDU重传比 SDU重传的实现复杂度小。
步骤 7c: 发送端 MAC实体将一个或多个逻辑信道组的 RLC PDU 复 用成为 MAC PDU;
步骤 8c: 发送端 MAC实体通过 HARQ进程 /实体传输 MAC PDU; 步骤 9c:发送端 MAC实体接收来自接收端 MAC实体的该 MAC PDU 的传输状态报告。
本实施例中接收端 MAC实体发送的传输状态报告表示对应 MAC PDU 传输成功, 例如可以是 ACK反馈。
步骤 10c:发送端 MAC 实体向该 MAC PDU 中所包含的 RLC PDU所 对应的 RLC实体反馈该 RLC PDU的传输状态报告。
步骤 11c: 发送端 RLC实体接收到 该 RLC PDU传输成功的指示后, 丢弃该 RLC PDU, 释放该 RLC PDU的緩存资源。
图 4、图 5和图 6对应实施例中采用自动重传请求确认模式传输指定数 据包。在自动重传请求确认模式中,发送端 RLC实体根据接收端 RLC实体 的反馈判断数据包是否需要重传。
图 4为本发明实施例提供的再一种数据包发送方法流程图。 如图 4所 示, 本实施例提供的数据包发送方法包括:
步骤 41: 发送端 RLC实体从上层实体接收数据包。
上层实体可以是 PDCP实体或 RRC实体。 从上层实体接收的数据包可 以是 RLC SDU。
步骤 42: 根据所述数据包的传输模式指示信息, 发送端 RLC实体判断 所述数据包的传输模式; 所述传输模式指示信息根据所述数据包的传输要 求设置。
所述数据包的传输模式指示信息可以由上层实体通过层间消息通知发 送端 RLC实体, 例如可以是 PDCP 实体的层间消息或 RRC 的层间消息。 另外, 所述数据包的传输模式指示信息也可以由上层实体通过所述数据包 包括的指示位携带给发送端 RLC实体。
步骤 43: 确定所述数据包的传输模式为自动重传请求确认模式时, 在 所述数据包中添加反馈传输结果的指示信息, 指示接收端 RLC实体接收到 所述数据包后向所述发送端 RLC实体反馈所述数据包的传输成功指示。
步骤 44: 发送端 RLC实体向发送端 MAC实体下发数据包后, 启动主 动重传事件; 若在主动重传事件被触发前, 没有接收到接收端 RLC实体发 送的所述数据包的接收成功确认, 发送端 RLC实体重新向发送端 MAC实 体下发所述数据包。
发送端 RLC实体确定所述数据包的传输模式为自动重传请求( ARQ ) 模式时, 在所述数据包中添加反馈传输结果的指示信息后, 向发送端 MAC 实体下发所述数据包, 并同时启动主动重传触发事件, 例如设置主动重传 定时器。 接收端 RLC实体接收到所述数据包后, 根据数据包中的反馈传输 结果的指示信息向所述发送端 RLC实体反馈所述数据包的接收成功确认。 发送端 RLC实体在主动重传事件触发之前, 例如在主动重传定时器超 时之前, 还没有接收到所述接收端 RLC实体发送的所述数据包的接收成功 砍认, 发送端 RLC实体确定所述数据包发送失败, 重新向发送端 MAC实 体下发所述数据包。 如果发送端 RLC实体在主动重传定时器超时之前接收 到所述接收端 RLC实体发送的所述数据包的接收成功确认, 则不重新向发 送端 MAC实体下发所述数据包, 并停止主动重传定时器。
进一步, 发送端 RLC 实体还可以设置主动重传的最大次数, 当某一 个数据包在经过多次重传后, 仍然在主动重传事件触发之后没有接收到来 自接收端 RLC 实体的接收成功确认, 则发送端 RLC 实体不再向发送端 MAC实体发送该数据包。
本实施例提供的数据包发送方法, 在确定数据包的传输模式为自动重 传请求确认模式时, 发送端 RLC实体接收上层实体下发的数据包中添加反 馈传输结果的指示信息, 指示接收端 RLC实体接收到该数据包后向所述发 送端 RLC实体反馈该数据包的传输成功指示。 发送端 RLC实体向发送端 MAC实体下发该数据包后,启动主动重传事件。在主动重传事件被触发后, 没有接收到来自接收端 RLC 的接收成功确认, 发送端 RLC实体重新向发 送端 MAC实体下发该数据包。在主动重传事件被触发前,接收到来自接收 端 RLC实体对所述数据包的接收成功确认, 发送端 RLC实体不再重传该 数据包。 本发明实施例采用自动重传请求确认模式向接收端发送该数据包, 满足了该数据包传输可靠性高的要求。
图 5 为本发明实施例提供的再一种数据包发送方法流程图。 本实施例 以数据包发送失败为例说明数据包的 ARQ传输模式。 如图 5所示, 本实施 例提供的数据包发送方法包括:
步骤 Id: 发送端 RLC 实体接收到来自上层实体的 RLC SDU;
步骤 2d: 发送端 RLC 实体依据上层实体的传输模式指示信息、或检测 该 RLC SDU中包含的传输模式指示信息,确定该 RLC SDU执行自动重传 请求确认模式传输。
步骤 2d中的上层实体可以是 PDCP或 RRC实体。
步骤 3d: 发送端 MAC实体执行调度功能, 获取发送数据所需资源; 步骤 4d:发送端 MAC 实体为该发送端 RLC实体所要发送的 RLC SDU 分配资源, 并根据资源大小向 RLC实体获取 RLC PDU。
步骤 5d: 发送端 RLC 实体按照 MAC实体所提供的资源封装数据包, 并在数据包中添加反馈传输结果的指示信息, 指示接收端 RLC实体接收到 所述数据包后向所述发送端 RLC实体反馈所述数据包的接收成功确认。
步骤 6d:发送端 RLC 实体将封装的 RLC PDU递交给发送端 MAC实 体。
步骤 7d: 发送端 RLC 实体启动该 RLC PDU的主动重传定时器。
步骤 8d: 发送端 MAC实体将一个或多个逻辑信道组的 RLC PDU 复 用成为 MAC PDU;
步骤 9d: 发送端 MAC实体通过 HARQ进程 /实体传输 MAC PDU; 步骤 10d: 发送端 MAC 实体接收到来自接收端 MAC 实体的表示该 MACPDU发送失败的传输状态报告。
步骤 lid: 在 RLC PDU的主动重传定时器超时之前,发送端 RLC实体 没有接收到所述接收端 RLC实体发送的该 RLC PDU的接收成功确认, 标 记该 RLC PDU需要重传。
步骤 12d: 发送端 RLC 实体更新传输顺序, 使得传输失败的 RLC PDU具有发送优先级高于首次发送的 RLC SDU的发送优先级。
进一步, 如果存在多个需要重传的 RLC PDU, 按照传输失败的 PDU 的生成顺序, 例如 SN (序列号, Sequence Number)递增顺序, 重新向发送端 MAC实体下发传输失败的 PDU或传输失败的 PDU对应的分段 PDU,使先 生成的传输失败的 PDU优先级高于后生成的传输失败的 PDU。
对于上述重传的 SDU或 PDU, 可以依据数据包的可靠性, 预先由基 站配置给终端 对应的 SDU或 PDU 的最大重传次数, 如果对应的 SDU 或 PDU 的最大重传次数等于或超过该预配置的最大重传次数, 则停止对 该 SDU或 PDU 的重传, 即不再重传该 SDU或 PDU。 另外, 对于上述 重传的 SDU或 PDU, 发送端也可一直等待接收到接收端反馈的接收成功 确认后才停止重发;, 因此接收端在成功接收数据包之后, 即使接收的数据 包是无效的, 也要回复接收成功确认。
图 6为本发明实施例提供的再一种数据包发送方法流程图。 本实施例 以数据包传输成功为例说明数据包的 ARQ传输模式。 如图 6所示, 本实施 例提供的数据包发送方法包括: 步骤 le: 发送端 RLC 实体接收到来自上层实体的 RLC SDU。
步骤 2e:发送端 RLC 实体依据上层实体的传输模式指示信息、或检测 该 RLC SDU中包含的传输模式指示信息, 确定该 RLC SDU执行自动重传 请求确认模式传输。
步骤 3e: 发送端 MAC实体执行调度功能, 获取发送数据所需的资源。 步骤 4e: 发送端 MAC实体为该 RLC 实体待发送的数据包分配资源, 并参考资源大小向 RLC实体获取 RLC PDIL
步骤 5e:发送端 RLC 实体按照发送端 MAC实体所提供的资源封装数 据包, 并在数据包中添加反馈传输结果的指示信息, 指示接收端 RLC实体 接收到所述数据包后向所述发送端 RLC实体反馈所述数据包的接收成功确 认。
步骤 6e: 发送端 RLC 实体将封装的 RLC PDU递交给发送端 MAC实 体。
步骤 7e: 发送端 RLC 实体启动待发送 RLC PDU的主动重传定时器。 步骤 8e: 发送端 MAC实体将一个或多个逻辑信道组的 RLC PDU 复 用成为 MAC PDU;
步骤 9e: 发送端 MAC实体通过 HARQ进程 /实体传输 MAC PDU; 步骤 10e: 发送端 MAC实体接收到接收端 MAC实体发送的接收成功 确认。
步骤 lie: 接收端 MAC实体解复用 MAC PDIL
步骤 12e: 接收端 MAC实体依据 MAC PDU中所包含的 RLC 标识, 将解复用后的 RLC PDU发送给对应的接收端 RLC实体。
步骤 13e:接收端 RLC实体依据 RLC PDU中包含的反馈传输结果的指 示信息, 识别该 RLC PDU需要反馈接收成功确认。
步骤 14e:接收端 RLC实体向发送端 RLC 实体反馈该 RLC PDU的接 成功确认。
步骤 15e: 该 RLC PDU的主动重传定时器超时之前, 发送端 RLC 实 体确认该 RLC PDU被接收端 RLC实体成功接收, 使主动重传定时器停止 工作。
以上采用数据包的传输模式指示对数据包进行传输的方法中, 基站需 要对终端进行配置, 以使发送端的 RLC实体根据数据包的传输要求采用确 认模式或非确认模式传输所述数据包。 具体方法如下:
基站向终端发送混合传输模式配置参数, 包括混合传输模式标识和传 输参数, 所述混合传输模式配置参数用于指示所述终端中所述 RLC实体标 识对应的 RLC实体根据数据包的传输要求采用确认模式或非确认模式传输 所述数据包; 终端根据混合传输模式配置参数配置所述接收 RLC实体标识 对应的 RLC实体。 其中, 混合传输模式为终端可根据数据包的传输要求采 用确认模式或非确认模式传输所述数据包的一种传输模式。
以下为装置实施例
图 11A为本发明实施例提供的一种数据包发送装置结构示意图。 如图 11A所示, 本实施例包括: 接收模块 111、 模式确定模块 112、 确认传输模 块 113和非确认传输模块 114。
接收模块 111 , 用于从上层实体接收待发送的数据包;
模式确定模块 112,用于根据所述上层实体下发的传输模式指示信息或 所述数据包中的传输模式指示信息, 判断所述数据包的传输模式; 所述传 输模式指示信息根据所述数据包的传输要求设定。
确认传输模块 113, 用于若所述数据包的传输模式为确认模式, 采用确 认模式向接收端发送所述数据包。
非确认传输模块 114, 用于若所述数据包的传输模式为非确认模式, 采 用非确认模式向接收端发送所述数据包。
以上各模块的功能参见图 1对应实施例中描述, 在此不再赘述。
如图 11B所示, 所述确认传输模块 113包括: 下发单元 1131、 反馈接 收单元 1132和重发单元 1133。
下发单元 1131 , 用于向发送端 MAC实体下发所述数据包, 以使发送 端 MAC实体向接收端 MAC实体发送所述数据包。
反馈接收单元 1132, 用于若所述数据包的传输模式为确认模式, 接收 来自接收端反馈的所述数据包的传输状态报告。
重发单元 1133, 用于若根据所述数据包的传输状态报告确定所述数据 包传输失败, 重新向发送端 MAC实体下发所述数据包, 以使发送端 MAC 实体重新向接收端 MAC实体发送所述数据包。
进一步, 重发单元,还用于重新向发送端 MAC实体下发所述数据包之 前, 更新传输顺序, 使得传输失败的数据包的发送优先级高于首次发送的 数据包的发送优先级。
进一步, 所述重发单元, 还用于按照传输失败的 PDU的生成顺序, 重 新向发送端 MAC 实体下发所述数据包中传输失败的 PDU 或传输失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高于后生成的 传输失败的 PDU;或者,按照传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC 实体下发传输失败的 PDU对应的 SDU所组装成的 新 PDU,使先从上层实体接收到的传输失败的 SDU优先级高于后从上层实 体接收到的传输失败的 SDU。
若所述数据包的传输模式为本地确认模式:
所述下发单元具体用于向发送端 MAC实体下发所述数据包,若所述数 据包的传输模式为本地确认模式, 向所述发送端 MAC实体发送所述数据 包的发送结果反馈指示, 以使所述 MAC实体接收到所述接收端 MAC实 体发送的所述数据包的传输状态报告后向所述发送端 RLC实体反馈;
所述反馈接收单元具体用于若所述数据包的传输模式为本地确认模 式, 在接收端 MAC实体发送所述数据包的传输状态报告后,接收所述发送 端 MAC实体反馈的所述数据包的传输状态报告。
以上各模块的功能参见图 2、 图 3A至图 3D对应实施例中描述, 在此 不再赘述。
若所述数据包的传输模式为自动重传请求确认模式:
所述下发单元具体用于向发送端 MAC实体下发所述数据包,若所述数 据包的传输模式为自动重传请求确认模式时, 在所述数据包中添加反馈传 输结果的指示信息, 以使所述接收端 RLC实体接收到所述数据包后向所述 RLC实体反馈所述数据包的接收成功确认; 还用于向发送端 MAC实体下 发所述数据包后, 启动主动重传事件;
所述重发单元, 具体用于若在所述数据包的主动重传事件触发之前没 有接收到所述接收端 RLC实体发送的所述数据包的接收成功确认, 重新向 发送端 MAC实体下发所述数据包。
以上各模块的功能参见图 4、 图 5至图 6对应实施例中描述, 在此不再 赘述。
实施例二还提供一种参数配置装置, 用于向终端发送混合传输模式配 置参数, 包括混合传输模式标识和传输参数, 所述混合传输模式配置参数 用于指示所述终端中所述 RLC实体标识对应的 RLC实体根据 RLC承载层 中数据包的传输要求采用确认模式或非确认模式传输所述数据包。
实施例二
实施例二说明在数据包传输过程中发送端与接收端如何切换传输模式 的方法。 传输模式切换包括从 UM模式切换到 AM模式, 或从 AM模式切 换到 UM模式, 从而根据不同数据包的传输要求对不同数据包采用不同的 传输模式。
图 7A为本发明实施例提供的一种模式转换方法流程图。本实施例主要 说明发送端如何从 UM模式转换为确认模式。如图 7A所示,本实施例提供 的模式转换方法包括:
步骤 70A: 发送端传输实体向接收端发送数据包之前, 确定从指定数 据包开始的多个连续数据包采用确认模式传输。
发送端实体根据数据包的传输模式指示信息, 判断数据包的传输模式。 数据包的传输模式指示信息可以由上层实体通过层间消息通知发送端传输 实体, 也可以由上层实体通过该数据包所包括的指示位携带给发送端传输 实体。
步骤 71A: 发送端传输实体向接收端发送该指定数据包之前, 向接收 端发送第一传输模式指示, 第一传输模式指示用于指示接收端从该指定数 据包开始采用确认模式传输; 如果在第一传输模式指示之前所采用的传输 方式为非确认模式, 则第一传输模式指示还用于指示接收端从非确认模式 转换为确认模式传输从指定数据包开始的多个连续数据包。
发送端传输实体确定指定数据包之后的多个连续的数据包采用确认模 式传输, 向接收端发送第一传输模式指示, 指示接收端从该指定数据包开 始采用确认模式传输。 如果在发送第一传输模式指示之前采用非确认模式 传输, 则第一传输模式指示还用于指示接收端从非确认模式转换为确认模 式传输指定数据包和指定数据包的后续数据包。
进一步, 如果发送端传输实体确定指定数据包之后的多个连续的数据 包采用 ARQ确认模式传输, 接收端为接收端 RLC实体, 发送端传输实体 向接收端 RLC实体下发携带有指定数据包的标识的第一传输模式指示; 如 果采用本地确认模式传输, 发送端传输实体向底层传输实体, 例如: MAC 实体, 发送第一传输模式指示, 该第一传输模式指示中可以不用携带数据 包标识, 该第一传输模式指示还用于指示发送端底层实体向发送端传输实 体反馈本层 (MAC)的传输结果 (HARQ), 该第一传输模式指示可以由发送端 控制层( RRC ) 实体或发送端 RLC实体发送给底层实体。
步骤 72A: 发送端传输实体接收到接收端反馈的第一模式转换响应之 后, 采用确认模式传输; 如果在接收到该传输模式指示之前, 采用的是非 确认模式, 则从非确认模式转换为确认模式。
因此,对于 ARQ确认模式传输,传输模式指示中可以指定开始确认模 式传输的数据包标识, 并且发送端接收到接收端反馈的第一模式转换响应 之后, 对指定数据包及其之后的数据包采用确认模式传输, 如果在该传输 模式指示之前, 接收端采用非确认模式传输, 则从非确认模式转换为确认 模式。 对于本地确认模式, 第一传输模式指示中可以不携带指定的数据包 标识, 接收端实体在接收到第一传输模式指示之后, 对该数据包及其之后 的数据包, 向上层反馈本层的传输结果。
本实施例提供的模式转换方法, 发送端在发送数据包的过程中, 通过 向接收端发送第一传输模式指示, 指示使接收端开始采用确认模式传输从 指定数据包开始的多个连续数据包, 如果在所述第一传输模式指示之前所 采用的传输方式为非确认模式, 则还指示接收端从非确认模式转换为确认 模式传输从所述指定数据包开始的多个连续数据包。 因此, 本实施例可采 用不同的模式传输不同的数据包,
图 7B为本发明实施例提供的另一种模式转换方法流程图。本实施例主 要说明接收端如何从 UM模式转换为 AM模式。如图 7B所示,本实施例提 供的模式转换方法包括:
步骤 70B: 接收端接收发送端传输实体发送的第一传输模式指示, 第 一传输模式指示用于指示接收端从该指定数据包开始采用确认模式传输; 如果在发送第一传输模式指示之前所采用的传输方式为非确认模式, 则第 一传输模式指示还用于指示接收端从非确认模式转换为确认模式传输指定 数据包和指定数据包的后续数据包。
进一步, 若确认模式为本地确认模式, 接收端为发送端底层实体, 发 送端底层实体还向发送端传输反馈从指定数据包开始的多个连续数据包的 传输结果; 若确认模式为自动重传请求确认模式, 接收端为接收端 RLC实 体, 第一传输模式指示还包括指定数据包的标识。 步骤 71B: 接收端向发送端反馈第一传输模式响应。
步骤 721B: 如果接收到指定数据包之前的数据包, 接收端从该指定数 据包开始采用确认模式传输, 如果在接收第一传输模式指示之前所采用的 传输方式为非确认模式, 接收端从非确认模式转换为确认模式传输从指定 数据包开始的多个连续数据包。
步骤 722B: 如果还没有接收到指定数据包之前的数据包, 接收端启动 重排序事件, 在重排序事件触发之后, 或, 重排序事件触发之前确认已接 收到指定数据包之前的数据包, 接收端从该指定数据包开始采用确认模式 传输, 如果在接收第一传输模式指示之前所采用的传输方式为非确认模式, 接收端从非确认模式转换为确认模式传输从指定数据包开始的多个连续数 据包。
图 8A为本发明实施例提供的又一种模式转换方法流程图。本实施例主 要说明从 UM模式转换为 ARQ确认模式的过程中发送端和接收端的交互过 程。 如图 8A所示, 本实施例提供的模式转换方法包括:
步骤 If: 发送端 RLC实体准备向接收端发送数据包 c, 确定从数据包 C开始的多个连续数据包采用 ARQ确认模式传输。
步骤 2f: 发送端 RLC实体向接收端 RLC实体发送携带有数据包 C的 第一传输模式指示, 所述第一传输模式指示用于指示接收端从数据包 C开 始采用 ARQ确认模式传输;如果在发送所述第一传输模式指示之前所采用 的传输方式为 UM模式,则所述第一传输模式指示还用于指示接收端从 UM 模式转换为 ARQ确认模式传输从数据包 C开始的多个连续数据包。
如图 8B所示, VT ( US )表示在 UM模式下发送端下一个待发送数据 包的 SN, 此时 VT ( US ) =C, 表示在 UM模式下发送端下一个待发送的数 据包为 c。 发送端准备向接收端发送数据包 c之前, 向接收端发送携带有数 据包 C的第一传输模式指示。
步骤 3f: 接收端 RLC实体接收到第一传输模式指示后, 向发送端 RLC 实体反馈第一传输模式响应。
步骤 4f: 确定还未接收到数据包 C之前的数据包 b, 接收端 RLC实体 启动、 或重新启动重排序定时器, 在重排序定时器超时, 或重排序定时器 超时前已接收到数据包 b,接收端根据第一传输模式指示, 确定在接收第一 传输模式指示之前所采用的传输方式为 UM模式,从 UM模式转换为 ARQ 确认模式传输从数据包 C开始的多个连续数据包。
如图 8B所示, VR ( UH )为 UM模式下接收窗的接收上限, 表示接收 端已经接收到数据包的最大 SN+1; VR ( UR )为 UM模式下接收窗的接收 下限, 表示接收端可接收到数据包的最小 SN。 从 UM模式转换为 ARQ确 认模式的过程中, 接收端在成功接收到数据包 C之前的数据包 b时, 或者 接收端在重排序定时器超时的时候还没有数据包 C之前的数据包 b, VR ( UH )按照顺时针方向向下移动, 在 VR ( UH ) 向下移动之后 VR ( UR ) 也跟随 VR ( UH )按照顺时针方向向下移动。
如图 8B所示, VR ( UX )表示 UM模式下从哪个数据包开始启动重排 序定时器( re-ordering timer )。 接收端接收到携带数据包 c标识的第一传输 模式指示时,接收端确定此时还未接收到数据包 c之前的数据包 b, VR( UX ) =c, 启动重排序定时器。 在重排序定时器超时后, 接收端如果还朱接收到 数据包 b, 由于在 UM传输数据包, 接收端不再等待数据包 b, 对接收到的 数据包进行排序, 并从 UM模式转换为 ARQ确认模式; 如果在重排序定时 器超时之前就接收到数据包 b,接收端立即停止重排序定时器,对接收到的 数据包进行排序, 并从 UM模式转换为 ARQ确认模式。
步骤 5f: 发送端 RLC实体接收到接收端 RLC实体的反馈第一传输模 式响应后, 确定在接收第一传输模式指示之前所采用的传输方式为 UM模 式, 从 UM模式转换为 ARQ确认模式。
如图 8B所示, VT ( A )表示在 AM模式下发送端下一个待确认数据包 的 SN, VT ( S )表示在 AM模式下发送端下一个待发送数据包的 SN, VT ( MS )为在 AM模式下发送端的发送上限, 表示发送端可发送数据包的最 大 SN。 发送端从 UM模式转换为 ARQ确认模式时, UT ( S ) =C, 表示在 AM模式下发送端下一个待确认的数据包为 c。
可选地, 步骤 3f 也可在步骤 4f之后, 即接收端 RLC实体从 UM模式 转换为 ARQ确认模式后, 再向发送端 RLC实体反馈第一模式转换响应。
图 9A为本发明实施例提供的再一种模式转换方法流程图。本实施例主 要说明发送端如何从 AM模式转换为 UM模式。 如图 9A所示, 本实施例 提供的模式转换方法包括:
步骤 90A: 发送端传输实体向接收端发送数据包之前, 确定从指定数 据包开始的多个连续数据包采用非确认模式传输。 发送端传输实体可以是发送端 RLC实体。
步骤 91A: 发送端传输实体向接收端发送该指定数据包之前, 向接收 端发送第二传输模式指示, 第二传输模式指示用于指示接收端从该指定数 据包开始采用非确认模式传输; 如果在发送第二传输模式指示之前所采用 的传输方式为确认模式, 则第二传输模式指示还用于指示接收端从确认模 式转换为非确认模式传输从指定数据包开始的多个连续数据包。
若确认模式为本地确认模式, 接收端为发送端底层实体, 例如发送端 MAC 实体; 若确认模式为自动重传请求确认模式, 接收端为接收端 RLC 实体, 第二传输模式指示还包括指定数据包的标识。
步骤 92A: 发送端传输实体接收到接收端反馈的第二传输模式响应之 后, 采用非确认模式传输; 如果在接收到该传输模式指示之前, 采用的是 确认模式, 则从确认模式转换为非确认模式。
进一步, 为了避免在发送端进入 UM模式后发送过多的数据包, 当发 送端存在至少一个已发送并需要被确认、 而没有被接收端确认的数据包时, 发送端发送序列号 (SN )在指定范围内的数据包。 具体地, 在发送端设置 一个大小等于 SN (序列号) 发送范围一半大小的发送窗, 发送窗的下限 为第一个已发送并需要被确认、 而没有被接收端确认的数据包对应的 SN, 发送端不能使用超过该发送窗上限的 SN发送数据包。
本实施例提供的模式转换方法, 发送端在发送数据包的过程中, 通过 向接收端发送第二传输模式指示, 指示使接收端开始采用非确认模式传输 从指定数据包开始的多个连续数据包, 如果在所述第二传输模式指示之前 所采用的传输方式为确认模式, 则还指示接收端从确认模式转换为非确认 模式传输从所述指定数据包开始的多个连续数据包。 因此, 本实施例可采 用不同的模式传输不同的数据包。
图 9B为本发明实施例提供的再一种模式转换方法流程图。本实施例主 要说明接收端如何从 AM模式转换为 UM模式。如图 9B所示,本实施例提 供的模式转换方法包括:
步骤 90B: 接收端接收发送端传输实体发送的第二传输模式指示, 第 二传输模式指示用于指示接收端从该指定数据包开始采用非确认模式传 输; 如果在发送第二传输模式指示之前所采用的传输方式为确认模式, 则 第二传输模式指示还用于指示接收端从确认模式转换为非确认模式传输指 定数据包和指定数据包的后续数据包。
若确认模式为本地确认模式, 接收端为发送端底层实体; 若确认模式 为自动重传请求确认模式, 接收端为接收端 RLC实体, 第二传输模式指示 还包括指定数据包的标识。
步骤 91B: 接收端向发送端反馈第二传输模式响应。
步骤 921B: 如果接收到指定数据包之前的数据包, 接收端从该指定数 据包开始采用非确认模式传输, 如果在接收第二传输模式指示之前所采用 的传输方式为确认模式, 接收端从确认模式转换为非确认模式传输从指定 数据包开始的多个连续数据包。
步骤 922B: 如果没有接收到指定数据包之前的数据包, 接收端启动重 排序事件, 重排序事件触发之前确认已接收到指定数据包之前的数据包, 接收端从该指定数据包开始采用非确认模式传输, 如果在接收第二传输模 式指示之前所采用的传输方式为确认模式, 接收端从确认模式转换为非确 认模式传输从指定数据包开始的多个连续数据包; 如果重排序事件触发之 后, 还未接收到指定数据包之前的数据包, 向发送端反馈发送失败状态报 告使发送端重传未接收到的数据包, 并重新启动重排序事件。
如果重排序事件触发之后, 还未接收到所述指定数据包之前的数据包, 向发送端反馈发送失败状态报告使所述发送端重传未接收到的数据包, 可 选的, 接收端还可重新启动重排序事件。
启动重排序事件可以是重传排序定时器, 重排序事件可以是重传排序 定时器。 在重排序定时器超时后如果还未接收到指定数据包之前的数据包, 由于接收端此时还处于 ARQ确认模式, 需要接收到数据包 b之后才能转换 为 UM模式, 因此接收端向发送端反馈发送失败状态报告使发送端重传还 没有接收到的数据包, 并重新启动重排序定时器, 直至接收到数据包 b。
图 9C为本发明实施例提供的再一种模式转换方法流程图。本实施例主 要说明从 ARQ确认模式转换为 UM模式的过程中发送端和接收端的交互 过程。 如图 9C所示, 本实施例提供的模式转换方法包括:
步骤 lg: 发送端 RLC实体发送数据包 c之前,确定从数据包 C开始多 个连续数据包采用 UM模式传输。
如图 8B所示, VT ( A ) 为 ARQ确认模式下待确认的数据包的 SN加 一, VT ( S ) 为 ARQ确认模式下待发送的数据包的 SN加一, VT ( MS ) 表示 ARQ确认模式下的发送上限, 从 VT (MS)到 VT ( A) 为发送窗口 大小的一半,。
步骤 2g: 发送端 RLC实体向接收端 RLC实体发送携带有数据包 C的 第二传输模式指示, 第二传输模式指示用于指示接收端 RLC实体从数据包 C开始采用 UM传输; 如果在发送第二传输模式指示之前所采用的传输方 式为 AM模式, 则所述第二传输模式指示还用于指示接收端 RLC 实体从 AM模式转换为 UM模式传输从数据包 C开始的多个连续数据包。
步骤 3g: 接收端 RLC实体接收到第二传输模式指示时, 确定还未接收 到数据包 C之前的数据包 b, 接收端 RLC实体启动重排序定时器, 在重排 序定时器超时前已接收到数据包 b, 根据第二传输模式指示从 ARQ确认模 式转换为 UM模式; 在重排序定时器超时后还未接收到数据包 b, 接收端 RLC 实体向发送端反馈发送失败状态报告使发送端重传数据包 b, 并重新 启动重排序定时器。
在重排序定时器超时后如果还未接收到数据包 b, 接收端此时还处于 ARQ确认模式, 需要接收到数据包 b之后才能转换为 UM模式, 因此接收 端向发送端反馈发送失败状态报告使发送端重传数据包 b,并重新启动重排 序定时器, 直至接收到数据包 b。
如图 8B所示, 从 ARQ确认模式转换为 UM模式的过程中, VR (H) 只有在成功接收到数据包 C之前的数据包 b之后, VR (H)按照顺时针方 向向下移动, 在 VR (H) 向下移动之后 VR (R)也跟随 VR (H)按照顺 时针方向向下移动。
如图 8B所示, VR (H)为 AM模式下接收窗的接收上限, 表示接收端 可接收到数据包的最大 SN+1; VR (R) 为 AM模式下接收窗的接收下限, 表示接收端可接收到数据包的最小 SN。 VR(X)表示 AM模式下从哪个数 据包开始启动重排序定时器(re-ordering timer )。 接收端从 UM模式转换为 ARQ确认模式后, VR (R) =C, 表示接收端可接收到数据包的最小 SN为 数据包 c的 SN。 从 VR ( MS )到 VR ( R ) 为 AM模式下接收端向发送端 反馈发送失败状态报告的窗口。 从 VR (R)到 VR (MR)为接收窗的一半。
步骤 4g:接收端 RLC实体接收到第二传输模式指示时,向发送端 RLC 实体反馈第二传输模式响应。
可选地, 步骤 4g也可在步骤 3g之前, 或者步骤 4g和步骤 3g同时进 行。
步骤 5g: 发送端 RLC实体接收到接收端 RLC实体的反馈第一传输模 式响应后, 从 ARQ确认模式转换为 UM模式。
步骤 6g:发送端 RLC实体没有接收到接收端关于数据包 C之前的数据 包 b的接收成功确认之前,发送端 RLC实体向接收端 RLC实体发送 SN小 于 VT ( MS ) 的数据包。
为了避免在发送端进入 UM模式后发送过多的数据包, 当发送端存在 至少一个已发送并需要被确认、 而没有被接收端确认的数据包时, 在发送 端设置一个大小等于 SN发送范围一半大小的发送窗, 该发送窗的下限为 第一个已发送并需要被确认、 而没有被接收端确认的数据包对应的 SN, 该 发送窗的上限为 VT ( MS ), 发送端不能使用超过该发送窗上限的 SN发送 数据包。
图 12A为本发明实施例提供的一种模式转换装置结构示意图。如图 12A 所示, 本实施例提供的位于发送端的模式转换装置包括: 确定模块 121 和 指示模块 122以及转换模块 123。
确定模块 121 , 用于向接收端发送数据包之前, 确定从指定数据包开始 的多个连续数据包采用确认模式传输;
指示模块 122, 用于向接收端发送该指定数据包之前, 向接收端发送第 一传输模式指示, 所述第一传输模式指示用于指示接收端从该指定数据包 开始采用确认模式传输; 如果在发送所述第一传输模式指示之前所采用的 传输方式为非确认模式, 则所述第一传输模式指示还用于指示接收端从非 确认模式转换为确认模式传输从所述指定数据包开始的多个连续数据包。
进一步, 若所述确认模式为本地确认模式, 所述接收端为发送端底层 实体, 所述第一传输模式指示还用于指示所述发送端底层实体向所述发送 端传输反馈从所述指定数据包开始的多个连续数据包的传输结果; 若所述 确认模式为自动重传请求确认模式, 所述接收端为接收端 RLC实体, 所述 第一传输模式指示还包括指定数据包的标识。
转换模块 123, 用于接收到接收端反馈的第一传输模式响应之后, 采用 确认模式传输; 如果在接收到该传输模式指示之前, 采用的是非确认模式, 则从非确认模式转换为确认模式。
本实施例的模块具体功能可参考图 7A和图 8A对应实施例中的描述, 在此不再赘述。
图 12B为本发明实施例提供的另一种模式转换装置结构示意图。 如图 12B所示,本实施例提供的位于接收端的模式转换装置包括:接收模块 124、 响应模块 125和转换模块 126。
接收模块 124, 用于接收发送端传输实体发送的第一传输模式指示, 所 述第一传输模式指示用于指示接收端从该指定数据包开始采用确认模式传 输; 如果在发送所述第一传输模式指示之前所采用的传输方式为非确认模 式, 则所述第一传输模式指示还用于指示接收端从非确认模式转换为确认 模式传输所述指定数据包和所述指定数据包的后续数据包。 进一步, 若所 述确认模式为自动重传请求确认模式, 所述第一传输模式指示还包括指定 数据包的标识。
响应模块 125, 用于向发送端反馈第一传输模式响应;
转换模块 126, 用于如果接收到所述指定数据包之前的数据包,从该指 定数据包开始采用确认模式传输, 如果在接收所述第一传输模式指示之前 所采用的传输方式为非确认模式, 从非确认模式转换为确认模式传输从所 述指定数据包开始的多个连续数据包;
转换模块 126, 还用于如果还没有接收到所述指定数据包之前的数据 包, 接收端启动重排序事件, 在重排序事件触发之后, 或, 重排序事件触 发之前确认已接收到所述指定数据包之前的数据包, 接收端从该指定数据 包开始采用确认模式传输, 如果在接收所述第一传输模式指示之前所采用 的传输方式为非确认模式, 从非确认模式转换为确认模式传输从所述指定 数据包开始的多个连续数据包。
本实施例的模块具体功能可参考图 7B和图 8A对应实施例中的描述, 在此不再赘述。
图 13A为本发明实施例提供的又一种模式转换装置结构示意图。 如图
13A所示,本实施例提供的位于发送端的模式转换装置包括:确定模块 131、 发送模块 132和转换模块 133。
确定模块 131 , 用于向接收端发送数据包之前, 确定从指定数据包开始 的多个连续数据包采用非确认模式传输。
发送模块 132, 用于向接收端发送该指定数据包之前, 向接收端发送第 二传输模式指示, 所述第二传输模式指示用于指示接收端从该指定数据包 开始采用非确认模式传输; 如果在发送所述第二传输模式指示之前所采用 的传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确 认模式转换为非确认模式传输从所述指定数据包开始的多个连续数据包。
进一步, 若所述确认模式为本地确认模式, 所述接收端为发送端底层 实体;若所述确认模式为自动重传请求确认模式,所述接收端为接收端 RLC 实体, 所述第二传输模式指示还包括指定数据包的标识。
转换模块 133 , 用于接收到接收端反馈的第二传输模式响应之后, 采用 非确认模式传输; 如果在接收到该传输模式指示之前, 采用的是确认模式, 则从确认模式转换为非确认模式。
进一步, 本实施例还包括: 限发模块, 用于没有接收到接收端反馈的 所述指定数据包之前的数据包的接收成功确认之前, 发送端发送序列号在 指定范围内的数据包。
本实施例的模块具体功能可参考图 9A和图 9C对应实施例中的描述, 在此不再赘述。
图 13B为本发明实施例提供的再一种模式转换装置结构示意图。 如图 13B所示, 本实施例提供的位于接收端的模式转换装置包括: 接收模块 134 和响应模块 135以及转换模块 136。
接收模块 134, 用于接收发送端传输实体发送的第二传输模式指示, 所 述第二传输模式指示用于指示接收端从该指定数据包开始采用非确认模式 传输; 如果在发送所述第二传输模式指示之前所采用的传输方式为确认模 式, 则所述第二传输模式指示还用于指示接收端从确认模式转换为非确认 模式传输从所述指定数据包开始的多个连续数据包;
响应模块 135 , 用于向发送端反馈第一传输模式响应。
进一步, 若所述确认模式为自动重传请求确认模式, 所述第二传输模 式指示还包括指定数据包的标识。
转换模块 136, 用于如果接收到所述指定数据包之前的数据包,接收端 从该指定数据包开始采用非确认模式传输, 如果在接收所述第二传输模式 指示之前所采用的传输方式为确认模式, 从确认模式转换为非确认模式传 输从所述指定数据包开始的多个连续数据包;
所述转换模块, 还用于如果没有接收到所述指定数据包之前的数据包, 接收端启动重排序事件, 重排序事件触发之前确认已接收到所述指定数据 包之前的数据包, 从该指定数据包开始采用非确认模式传输, 如果在接收 所述第二传输模式指示之前所采用的传输方式为确认模式, 从确认模式转 换为非确认模式传输从所述指定数据包开始的多个连续数据包; 如果重排 序事件触发之后, 还未接收到所述指定数据包之前的数据包, 向发送端反 馈发送失败状态报告使所述发送端重传未接收到的数据包, 并重新启动 重排序事件。
本实施例的模块具体功能可参考图 9B和图 9C对应实施例中的描述, 在此不再赘述。
实施例三
实施例三针对现有技术在采用确认模式传输过程中, 对于需要重传的 PDU没有排序的缺陷, 提供一种确认模式下的数据重传方法。
在现有技术中, 如果存在多个重传的 RLC PDU或分段 PDU, 发送端 传输实体对于重传 PDU的传输顺序没有限定, 可以是传输顺序可以是任意 的。 但接收端 RLC 实体只有在接收到第一个没有接收到的 RLC PDU 的 时候, 才能够递交 SN 大于该 RLC PDU之后的 PDU, 因此现有技术的实 现方式可能导致接收端緩存接收数据的时间较长, 进而导致数据在空口的 传输时延较长。
图 10为本发明实施例提供的一种确认模式下的数据重传方法流程图。 如图 10所示, 本实施例包括:
步骤 101: 发送端传输实体接收来自接收端实体反馈的传输失败报告。 发送端 RLC 实体接收到来自上层的 RLC SDU, 将所接收到的 RLC SDU封装成 RLC PDU, 并递交给 MAC层实体传输。 发送端 RLC 实体 通过接收端实体反馈的传输失败报告, 例如, 在 ARQ确认模式下, 接收到 接收端 RLC 实体反馈的传输失败报告; 在本地确认模式下, 接收到来自 发送端 MAC实体的反馈的传输失败报告。
步骤 102: 发送端传输实体根据所述传输失败报告确定传输失败的 PDU。
步骤 103: 发送端传输实体重新向发送端 MAC 实体下发传输失败的 PDU或传输失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优 先级高于后生成的传输失败的 PDU。
按照传输失败的 PDU的生成顺序,例如 SN (序列号, Sequence Number) 递增顺序, 发送端传输实体重新向发送端 MAC实体下发传输失败的 PDU 或传输失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级 高于后生成的传输失败的 PDU。 RLC将重传数据包按照重传顺序递交给 MAC层实体进行数据重传。
步骤 103也可以为:发送端传输实体识别传输失败的 PDU对应的 SDU, 按照传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实 体下发传输失败的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实 体接收到的传输失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
本实施例对重传的 PDU按照生成顺序进行排序, 使得先生成的 PDU 在传输失败时能优先重传, 从而早到达接收端, 使接收端可以提交该 PDU 之后已接收到的 PDU, 从而减少了接收端緩存已接收到的 PDU的时间, 图 14为本发明实施例提供的一种确认模式下的数据包重传装置结构示 意图。 如图 14所示, 本实施例包括: 报告接收模块 141、 识别模块 142和 重传模块 143。
报告接收模块 141 , 用于接收来自接收端实体反馈的传输失败报告; 识别模块 142, 用于根据所述传输失败报告确定传输失败的 PDU; 重传模块 143, 用于重新向发送端 MAC实体下发传输失败的 PDU或 传输失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高 于后生成的传输失败的 PDU。 或者, 识别传输失败的 PDU对应的 SDU, 按照传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实 体下发传输失败的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实 体接收到的传输失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
本实施例的模块具体功能可参考图 10对应实施例中的描述, 在此不再 赘述。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步 骤可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机 可读取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序 代码的介质。 最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对 其限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通 技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修 改, 或者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不 使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims

权利要求
1、 一种数据包发送方法, 其特征在于, 包括:
发送端传输实体从上层实体接收待发送的数据包;
根据所述上层实体下发的传输模式指示信息或所述数据包中的传输模 式指示信息, 所述发送端传输实体判断所述数据包的传输模式; 所述传输 模式指示信息根据所述数据包的传输要求设定;
若所述数据包的传输模式为确认模式, 所述发送端传输实体采用确认 模式向接收端发送所述数据包;
若所述数据包的传输模式为非确认模式, 所述发送端传输实体采用非 确认模式向接收端发送所述数据包。
2、 根据权利要求 1所述的方法, 其特征在于, 若所述数据包的传输模 式为确认模式, 发送端采用确认模式向接收端发送所述数据包包括:
发送端无线链路控制 RLC实体向发送端媒体访问控制 MAC实体下发 所述数据包, 以使发送端 MAC实体向接收端 MAC实体发送所述数据包; 若所述数据包的传输模式为确认模式, 所述发送端 RLC实体接收来自 接收端反馈的所述数据包的传输状态报告; 若根据所述数据包的传输状态 报告确定所述数据包传输失败, 发送端 RLC实体重新向发送端 MAC实体 下发所述数据包, 以使发送端 MAC实体重新向接收端 MAC实体发送所述 数据包。
3、 根据权利要求 2所述的方法, 其特征在于, 若所述数据包的传输模 式为本地确认模式, 所述发送端接收来自接收端反馈的所述数据包的传输 状态报告具体为:
在所述发送端 MAC实体接收到所述接收端 MAC实体发送所述数据包 的传输状态报告后, 所述发送端 RLC实体接收所述发送端 MAC实体反馈 的所述数据包的传输状态报告。
4、 根据权利要求 3所述的方法, 其特征在于, 在所述发送端 RLC实 体接收所述发送端 MAC实体反馈的所述数据包的传输状态报告之前,还包 括:
所述发送端 RLC实体或发送端控制层实体向所述发送端 MAC实体 发送所述数据包的发送结果反馈指示, 以使所述 MAC实体接收到所述接 收端 MAC实体发送的所述数据包的传输状态报告后向所述发送端 RLC实 体反馈。
5、 根据权利要求 2所述的方法, 其特征在于, 所述数据包的传输模式 为自动重传请求确认模式时, 所述发送端 RLC实体向发送端 MAC实体下 发所述数据包后, 所述发送端 RLC实体接收来自接收端反馈的所述数据包 的传输状态报告; 若根据所述数据包的传输状态报告确定所述数据包传输 失败, 发送端 RLC实体重新向发送端 MAC实体下发所述数据包包括: 发送端 RLC实体在所述数据包中添加反馈传输结果的指示信息, 以使 所述接收端 RLC实体接收到所述数据包后向所述 RLC实体反馈所述数据包 的接收成功确认;
发送端 RLC实体向发送端 MAC实体下发所述数据包后, 启动主动重 传事件, 若在所述数据包的主动重传事件触发之前没有接收到所述接收端 RLC实体发送的所述数据包的接收成功确认,发送端 RLC实体重新向发送 端 MAC实体下发所述数据包。
6、 根据权利要求 2、 3或 5所述的方法, 其特征在于, 发送端 RLC实 体重新向发送端 MAC实体下发所述数据包之前, 还包括:
RLC 实体更新传输顺序, 使得传输失败的数据包的发送优先级高于首 次发送的数据包的发送优先级。
7、 根据权利要求 2、 3或 5所述的方法, 其特征在于, 发送端 RLC实 体重新向发送端 MAC实体下发所述数据包包括:
重新向发送端 MAC 实体下发所述数据包中传输失败的协议数据单元 PDU或传输失败的 PDU对应的分段 PDU, 或者, 重新向发送端 MAC实体 下发传输失败的 PDU对应的业务数据单元 SDU所组装成的新 PDU。
8、 根据权利要求 7所述的方法, 其特征在于:
所述重新向发送端 MAC实体下发所述数据包中传输失败的 PDU或传 输失败的 PDU对应的分段 PDU具体为:按照传输失败的 PDU的生成顺序, 重新向发送端 MAC实体下发传输失败的 PDU或传输失败的 PDU对应的分 段 PDU, 使先生成的传输失败的 PDU优先级高于后生成的传输失败的 PDU; 或者,
重新向发送端 MAC实体下发传输失败的 PDU对应的 SDU所组装成 的新 PDU具体为: 按照传输失败的 SDU从所述上层实体的接收顺序, 重 新向发送端 MAC 实体下发传输失败的 PDU 对应的 SDU 所组装成的 新 PDU,使先从上层实体接收到的传输失败的 SDU优先级高于后从上层实 体接收到的传输失败的 SDU。
9、 一种参数配置方法, 其特征在于, 包括:
基站向终端发送混合传输模式配置参数, 包括混合传输模式标识和传 输参数, 所述混合传输模式配置参数用于指示所述终端中所述 RLC实体标 识对应的 RLC实体根据 RLC承载层中数据包的传输要求采用确认模式或非 确认模式传输所述数据包;
终端根据混合传输模式配置参数配置所述接收 RLC 实体标识对应的 RLC实体。
10、 一种数据包发送装置, 其特征在于, 包括:
接收模块, 用于从上层实体接收待发送的数据包;
模式确定模块, 用于根据所述上层实体下发的传输模式指示信息或所 述数据包中的传输模式指示信息, 判断所述数据包的传输模式; 所述传输 模式指示信息根据所述数据包的传输要求设定;
确认传输模块, 用于若所述数据包的传输模式为确认模式, 采用确认 模式向接收端发送所述数据包;
非确认传输模块, 用于若所述数据包的传输模式为非确认模式, 采用 非确认模式向接收端发送所述数据包。
11、 根据权利要求 10所述的装置, 其特征在于, 所述确认传输模块包 括:
下发单元,用于向发送端 MAC实体下发所述数据包,以使发送端 MAC 实体向接收端 MAC实体发送所述数据包;
反馈接收单元, 用于若所述数据包的传输模式为确认模式, 接收来自 接收端反馈的所述数据包的传输状态报告;
重发单元, 用于若根据所述数据包的传输状态报告确定所述数据包传 输失败, 重新向发送端 MAC实体下发所述数据包, 以使发送端 MAC实体 重新向接收端 MAC实体发送所述数据包。
12、 根据权利要求 11所述的装置, 其特征在于:
所述下发单元具体用于向发送端 MAC实体下发所述数据包,若所述数 据包的传输模式为本地确认模式, 向所述发送端 MAC实体发送所述数据 包的发送结果反馈指示, 以使所述 MAC实体接收到所述接收端 MAC实 体发送的所述数据包的传输状态报告后向所述发送端 RLC实体反馈; 所述反馈接收单元具体用于若所述数据包的传输模式为本地确认模 式, 在接收端 MAC实体发送所述数据包的传输状态报告后,接收所述发送 端 MAC实体反馈的所述数据包的传输状态报告。
13、 根据权利要求 11所述的装置, 其特征在于:
所述下发单元具体用于向发送端 MAC实体下发所述数据包,若所述数 据包的传输模式为自动重传请求确认模式时, 在所述数据包中添加反馈传 输结果的指示信息, 以使所述接收端 RLC实体接收到所述数据包后向所述 RLC实体反馈所述数据包的接收成功确认; 还用于向发送端 MAC实体下 发所述数据包后, 启动主动重传事件;
所述重发单元, 具体用于若在所述数据包的主动重传事件触发之前没 有接收到所述接收端 RLC实体发送的所述数据包的接收成功确认, 重新向 发送端 MAC实体下发所述数据包。
14、 根据权利要求 11、 12或 13所述的装置, 其特征在于, 所述重发 单元,还用于重新向发送端 MAC实体下发所述数据包之前,更新传输顺序, 使得传输失败的数据包的发送优先级高于首次发送的数据包的发送优先 级。
15、 根据权利要求 11、 12或 13所述的装置, 其特征在于, 所述重发 单元, 还用于按照传输失败的 PDU的生成顺序, 重新向发送端 MAC实体 下发所述数据包中传输失败的 PDU或传输失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高于后生成的传输失败的 PDU; 或者, 按照传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实 体下发传输失败的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实 体接收到的传输失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
16、 一种参数配置装置, 其特征在于, 用于向终端发送混合传输模式 配置参数, 包括混合传输模式标识和传输参数, 所述混合传输模式配置参 数用于指示所述终端中所述 RLC实体标识对应的 RLC实体根据 RLC承载 层中数据包的传输要求采用确认模式或非确认模式传输所述数据包。
17、 一种模式转换方法, 其特征在于, 包括: 发送端传输实体向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用确认模式传输;
发送端传输实体向接收端发送该指定数据包之前, 向接收端发送第一 传输模式指示, 所述第一传输模式指示用于指示接收端从该指定数据包开 始采用确认模式传输; 如果在发送所述第一传输模式指示之前所采用的传 输方式为非确认模式, 则所述第一传输模式指示还用于指示接收端从非确 认模式转换为确认模式传输从所述指定数据包开始的多个连续数据包; 发送端传输实体接收到接收端反馈的第一传输模式响应之后, 采用确 认模式传输; 如果在接收到该传输模式指示之前, 采用的是非确认模式, 则从非确认模式转换为确认模式。
18、 根据权利要求 17所述的方法, 其特征在于, 若所述确认模式为本 地确认模式, 所述接收端为发送端底层实体, 所述第一传输模式指示还用 于指示所述发送端底层实体向所述发送端传输反馈从所述指定数据包开始 的多个连续数据包的传输结果; 若所述确认模式为自动重传请求确认模式, 所述接收端为接收端 RLC实体, 所述第一传输模式指示还包括指定数据包 的标识。
19、 一种模式转换方法, 其特征在于, 包括:
接收端接收发送端传输实体发送的第一传输模式指示, 所述第一传输 模式指示用于指示接收端从该指定数据包开始采用确认模式传输; 如果在 发送所述第一传输模式指示之前所采用的传输方式为非确认模式, 则所述 第一传输模式指示还用于指示接收端从非确认模式转换为确认模式传输所 述指定数据包和所述指定数据包的后续数据包;
接收端向发送端反馈第一传输模式响应;
如果接收到所述指定数据包之前的数据包, 接收端从该指定数据包开 始采用确认模式传输, 如果在接收所述第一传输模式指示之前所采用的传 输方式为非确认模式, 接收端从非确认模式转换为确认模式传输从所述指 定数据包开始的多个连续数据包;
如果还没有接收到所述指定数据包之前的数据包, 接收端启动重排序 事件, 在重排序事件触发之后, 或, 重排序事件触发之前确认已接收到所 述指定数据包之前的数据包, 接收端从该指定数据包开始采用确认模式传 输, 如果在接收所述第一传输模式指示之前所采用的传输方式为非确认模 式, 接收端从非确认模式转换为确认模式传输从所述指定数据包开始的多 个连续数据包。
20、 根据权利要求 19所述的方法, 其特征在于, 若所述确认模式为本 地确认模式, 所述接收端为发送端底层实体, 所述发送端底层实体还向所 述发送端传输反馈从所述指定数据包开始的多个连续数据包的传输结果; 若所述确认模式为自动重传请求确认模式,所述接收端为接收端 RLC实体, 所述第一传输模式指示还包括指定数据包的标识。
21、 一种模式转换方法, 其特征在于, 包括:
发送端传输实体向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用非确认模式传输;
发送端传输实体向接收端发送该指定数据包之前, 向接收端发送第二 传输模式指示, 所述第二传输模式指示用于指示接收端从该指定数据包开 始采用非确认模式传输; 如果在发送所述第二传输模式指示之前所采用的 传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确认 模式转换为非确认模式传输从所述指定数据包开始的多个连续数据包; 发送端传输实体接收到接收端反馈的第二传输模式响应之后, 采用非 确认模式传输; 如果在接收到该传输模式指示之前, 采用的是确认模式, 则从确认模式转换为非确认模式。
22、 根据权利要求 21所述的方法, 其特征在于, 还包括:
发送端传输实体没有接收到接收端反馈的所述指定数据包之前的数据 包的接收成功确认之前, 发送端传输实体发送序列号在指定范围内的数据 包。
23、 根据权利要求 21或 22所述的方法, 其特征在于, 若所述确认模 式为本地确认模式, 所述接收端为发送端底层实体; 若所述确认模式为自 动重传请求确认模式, 所述接收端为接收端 RLC实体, 所述第二传输模式 指示还包括指定数据包的标识。
24、 一种模式转换方法, 其特征在于, 包括:
接收端接收发送端传输实体发送的第二传输模式指示, 所述第二传输 模式指示用于指示接收端从该指定数据包开始采用非确认模式传输; 如果 在发送所述第二传输模式指示之前所采用的传输方式为确认模式, 则所述 第二传输模式指示还用于指示接收端从确认模式转换为非确认模式传输从 所述指定数据包开始的多个连续数据包;
向发送端反馈第二传输模式响应;
如果接收到所述指定数据包之前的数据包, 接收端从该指定数据包开 始采用非确认模式传输, 如果在接收所述第二传输模式指示之前所采用的 传输方式为确认模式, 接收端从确认模式转换为非确认模式传输从所述指 定数据包开始的多个连续数据包;
如果没有接收到所述指定数据包之前的数据包, 接收端启动重排序事 件, 重排序事件触发之前确认已接收到所述指定数据包之前的数据包, 接 收端从该指定数据包开始采用非确认模式传输, 如果在接收所述第二传输 模式指示之前所采用的传输方式为确认模式, 接收端从确认模式转换为非 确认模式传输从所述指定数据包开始的多个连续数据包; 如果重排序事件 触发之后, 还未接收到所述指定数据包之前的数据包, 向发送端反馈发送 失败状态报告使所述发送端重传未接收到的数据包,并重新启动重排序事 件。
25、 根据权利要求 24所述的方法, 其特征在于, 若所述确认模式为本 地确认模式, 所述接收端为发送端底层实体; 若所述确认模式为自动重传 请求确认模式, 所述接收端为接收端 RLC实体, 所述第二传输模式指示还 包括指定数据包的标识。
26、 一种模式转换装置, 其特征在于, 包括:
确定模块, 用于向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用确认模式传输;
指示模块, 用于向接收端发送该指定数据包之前, 向接收端发送第一 传输模式指示, 所述第一传输模式指示用于指示接收端从该指定数据包开 始采用确认模式传输; 如果在发送所述第一传输模式指示之前所采用的传 输方式为非确认模式, 则所述第一传输模式指示还用于指示接收端从非确 认模式转换为确认模式传输从所述指定数据包开始的多个连续数据包; 转换模块, 用于接收到接收端反馈的第一传输模式响应之后, 采用确 认模式传输; 如果在接收到该传输模式指示之前, 采用的是非确认模式, 则从非确认模式转换为确认模式。
27、 根据权利要求 26所述的装置, 其特征在于, 若所述确认模式为本 地确认模式, 所述接收端为发送端底层实体, 所述第一传输模式指示还用 于指示所述发送端底层实体向所述发送端传输反馈从所述指定数据包开始 的多个连续数据包的传输结果; 若所述确认模式为自动重传请求确认模式, 所述接收端为接收端 RLC实体, 所述第一传输模式指示还包括指定数据包 的标识。
28、 一种模式转换装置, 其特征在于, 包括:
接收模块, 用于接收发送端传输实体发送的第一传输模式指示, 所述 第一传输模式指示用于指示接收端从该指定数据包开始采用确认模式传 输; 如果在发送所述第一传输模式指示之前所采用的传输方式为非确认模 式, 则所述第一传输模式指示还用于指示接收端从非确认模式转换为确认 模式传输所述指定数据包和所述指定数据包的后续数据包;
响应模块, 用于向发送端反馈第一传输模式响应;
转换模块, 用于如果接收到所述指定数据包之前的数据包, 从该指定 数据包开始采用确认模式传输, 如果在接收所述第一传输模式指示之前所 采用的传输方式为非确认模式, 从非确认模式转换为确认模式传输从所述 指定数据包开始的多个连续数据包;
转换模块, 还用于如果还没有接收到所述指定数据包之前的数据包, 接收端启动重排序事件, 在重排序事件触发之后, 或, 重排序事件触发之 前确认已接收到所述指定数据包之前的数据包, 接收端从该指定数据包开 始采用确认模式传输, 如果在接收所述第一传输模式指示之前所采用的传 输方式为非确认模式, 从非确认模式转换为确认模式传输从所述指定数据 包开始的多个连续数据包。
29、 根据权利要求 28所述的装置, 其特征在于, 若所述确认模式为自 动重传请求确认模式, 所述第一传输模式指示还包括指定数据包的标识。
30、 一种模式转换装置, 其特征在于, 包括:
确定模块, 用于向接收端发送数据包之前, 确定从指定数据包开始的 多个连续数据包采用非确认模式传输;
发送模块, 用于向接收端发送该指定数据包之前, 向接收端发送第二 传输模式指示, 所述第二传输模式指示用于指示接收端从该指定数据包开 始采用非确认模式传输; 如果在发送所述第二传输模式指示之前所采用的 传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确认 模式转换为非确认模式传输从所述指定数据包开始的多个连续数据包; 转换模块, 用于接收到接收端反馈的第二传输模式响应之后, 采用非 确认模式传输; 如果在接收到该传输模式指示之前, 采用的是确认模式, 则从确认模式转换为非确认模式。
31、 根据权利要求 30所述的装置, 其特征在于, 若所述确认模式为本 地确认模式, 所述接收端为发送端底层实体; 若所述确认模式为自动重传 请求确认模式, 所述接收端为接收端 RLC实体, 所述第二传输模式指示还 包括指定数据包的标识。
32、 根据权利要求 30或 31所述的装置, 其特征在于, 还包括: 限发模块, 用于没有接收到接收端反馈的所述指定数据包之前的数据 包的接收成功确认之前, 发送序列号在指定范围内的数据包。
33、 一种模式转换装置, 其特征在于, 包括:
接收模块, 用于接收发送端传输实体发送的第二传输模式指示, 所述 第二传输模式指示用于指示接收端从该指定数据包开始采用非确认模式传 输; 如果在发送所述第二传输模式指示之前所采用的传输方式为确认模式, 则所述第二传输模式指示还用于指示接收端从确认模式转换为非确认模式 传输从所述指定数据包开始的多个连续数据包;
响应模块, 用于向发送端反馈第二传输模式响应;
转换模块, 用于如果接收到所述指定数据包之前的数据包, 接收端从 该指定数据包开始采用非确认模式传输, 如果在接收所述第二传输模式指 示之前所采用的传输方式为确认模式, 从确认模式转换为非确认模式传输 从所述指定数据包开始的多个连续数据包;
所述转换模块, 还用于如果没有接收到所述指定数据包之前的数据包, 接收端启动重排序事件, 重排序事件触发之前确认已接收到所述指定数据 包之前的数据包, 从该指定数据包开始采用非确认模式传输, 如果在接收 所述第二传输模式指示之前所采用的传输方式为确认模式, 从确认模式转 换为非确认模式传输从所述指定数据包开始的多个连续数据包; 如果重排 序事件触发之后, 还未接收到所述指定数据包之前的数据包, 向发送端反 馈发送失败状态报告使所述发送端重传未接收到的数据包, 并重新启动 重排序事件。
34、 根据权利要求 33所述的装置, 其特征在于, 若所述确认模式为自 动重传请求确认模式, 所述第二传输模式指示还包括指定数据包的标识。
35、 一种确认模式下的数据重传方法, 其特征在于, 包括:
发送端传输实体接收来自接收端实体反馈的传输失败报告;
发送端传输实体根据所述传输失败报告确定传输失败的 PDU;
发送端传输实体重新向发送端 MAC实体下发传输失败的 PDU或传输 失败的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高于后 生成的传输失败的 PDU; 或者,
发送端传输实体识别传输失败的 PDU对应的 SDU, 按照传输失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实体下发传输失败 的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实体接收到的传输 失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
36、 一种确认模式下的数据包重传装置, 其特征在于, 包括: 报告接收模块, 用于接收来自接收端实体反馈的传输失败报告; 识别模块, 用于根据所述传输失败报告确定传输失败的 PDU;
重传模块, 用于重新向发送端 MAC实体下发传输失败的 PDU或传输失败 的 PDU对应的分段 PDU, 使先生成的传输失败的 PDU优先级高于后生成 的传输失败的 PDU。 或者, 识别传输失败的 PDU对应的 SDU, 按照传输 失败的 SDU从所述上层实体的接收顺序, 重新向发送端 MAC实体下发传 输失败的 PDU对应的 SDU所组装成的新 PDU, 使先从上层实体接收到 的传输失败的 SDU优先级高于后从上层实体接收到的传输失败的 SDU。
PCT/CN2013/072836 2012-03-19 2013-03-19 数据包发送方法、模式转换方法及装置 WO2013139249A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210072939.X 2012-03-19
CN201210072939.XA CN103326832B (zh) 2012-03-19 2012-03-19 数据包发送方法、参数配置方法及装置

Publications (1)

Publication Number Publication Date
WO2013139249A1 true WO2013139249A1 (zh) 2013-09-26

Family

ID=49195383

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/072836 WO2013139249A1 (zh) 2012-03-19 2013-03-19 数据包发送方法、模式转换方法及装置

Country Status (2)

Country Link
CN (1) CN103326832B (zh)
WO (1) WO2013139249A1 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871519A (zh) * 2015-01-23 2016-08-17 中兴通讯股份有限公司 数据包的重传方法及装置
US20160219458A1 (en) * 2015-01-26 2016-07-28 Qualcomm Incorporated Methods and apparatus for radio link control switching
US10440771B2 (en) * 2015-03-06 2019-10-08 Qualcomm Incorporated Conditional HARQ feedback
EP3506540A4 (en) * 2016-09-28 2019-09-18 Huawei Technologies Co., Ltd. DATA TRANSMISSION METHOD, NETWORK DEVICE, AND TERMINAL DEVICE
CN108282798B (zh) * 2017-01-06 2021-09-14 华为技术有限公司 通信方法和网络设备
CN108289007B (zh) * 2017-01-10 2022-04-15 中兴通讯股份有限公司 数据包传输方法及装置
CN110612776B (zh) * 2017-05-09 2021-06-04 华为技术有限公司 一种数据处理方法及终端设备、网络设备
CN112969223B (zh) * 2017-08-11 2022-09-30 中兴通讯股份有限公司 参数配置、功率确定方法及装置、通信节点
CN109788509B (zh) * 2017-11-15 2023-03-10 华为技术有限公司 连续数据包传输失败的规避方法及装置
CN110972211B (zh) 2018-09-28 2023-10-20 华为技术有限公司 一种功率控制的方法和装置
CN109474688B (zh) * 2018-11-27 2021-05-14 北京微播视界科技有限公司 即时通信网络请求消息的发送方法、装置、设备和介质
CN109842821A (zh) * 2018-12-25 2019-06-04 视联动力信息技术股份有限公司 一种视频数据传输的方法和装置
CN111756482B (zh) * 2019-03-29 2023-01-13 中国移动通信有限公司研究院 一种确认反馈方法、装置和计算机可读存储介质
CN110234124B (zh) * 2019-04-19 2022-04-01 维沃移动通信(深圳)有限公司 信息传输方法及终端设备
EP4017090B1 (en) * 2019-08-12 2023-09-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method and apparatus, device, and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101087171A (zh) * 2006-08-26 2007-12-12 华为技术有限公司 一种无线链路控制传输的方法及系统
CN101895372A (zh) * 2010-06-29 2010-11-24 中国科学院计算技术研究所 无线链路控制层确认模式下的数据传输方法
WO2011019427A2 (en) * 2009-08-13 2011-02-17 Research In Motion Limited Evolved universal terrestrial radio access acknowledged mode radio link control status report for segmented protocol data units

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101990240B (zh) * 2009-08-03 2013-05-08 中兴通讯股份有限公司 一种无线链路控制层的数据发送方法及数据发送系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101087171A (zh) * 2006-08-26 2007-12-12 华为技术有限公司 一种无线链路控制传输的方法及系统
WO2011019427A2 (en) * 2009-08-13 2011-02-17 Research In Motion Limited Evolved universal terrestrial radio access acknowledged mode radio link control status report for segmented protocol data units
CN101895372A (zh) * 2010-06-29 2010-11-24 中国科学院计算技术研究所 无线链路控制层确认模式下的数据传输方法

Also Published As

Publication number Publication date
CN103326832A (zh) 2013-09-25
CN103326832B (zh) 2017-11-24

Similar Documents

Publication Publication Date Title
WO2013139249A1 (zh) 数据包发送方法、模式转换方法及装置
US9860915B2 (en) Apparatus and method for moving a receive window in a radio access network
JP4981904B2 (ja) 媒体アクセス制御破棄通知
JP4965713B2 (ja) 無線通信システムにおけるエラー制御メッセージを処理するための方法及び装置
US8000256B2 (en) Method and apparatus for data transmission of radio link control layer in a mobile communication system
US7869396B2 (en) Data transmission method and data re-transmission method
JP4806030B2 (ja) 移動通信システムで信号を転送する方法
WO2007098676A1 (fr) Procédé de réassemblage de données dans un système de communication sans fil et appareil associé
WO2011047621A1 (zh) 基于重传机制的对头压缩数据包进行传输的方法和装置
US8300583B2 (en) Method for transmitting control information in a mobile communication system
WO2008025232A1 (fr) Procédé permettant la surveillance répétée d'une demande de répétition automatique hybride asynchrone d'une liaison montante améliorée
WO2015066923A1 (zh) 数据传输方法及装置
WO2010124435A1 (zh) 信息处理方法、系统及设备
WO2012100670A1 (zh) 一种数据包的重传方法及装置
KR20090038751A (ko) 고속데이터 전송을 위한 arq 과정의 수행방법
EP1871034A1 (en) Method and apparatus of packet discard in a wireless communications system
WO2015192322A1 (zh) 无线资源调度方法及装置
KR20090122962A (ko) 재송요구 송신방법 및 수신측 장치
WO2011079777A1 (zh) 数据传输的方法和网络侧设备
WO2014075284A1 (zh) 数据重传、反馈方法,以及相应的装置
WO2008133577A1 (en) Method for selectively discarding data units in a radio communication system
WO2013170464A1 (zh) 传输或接收上行sps业务数据的方法及用户设备、基站
WO2017117800A1 (zh) 数据发送和接收装置、方法以及通信系统
WO2011134232A1 (zh) Lte系统中用户设备的切换处理方法、装置和系统

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13763528

Country of ref document: EP

Kind code of ref document: A1