WO2020244642A1 - 一种冗余信息反馈方法及通信装置 - Google Patents

一种冗余信息反馈方法及通信装置 Download PDF

Info

Publication number
WO2020244642A1
WO2020244642A1 PCT/CN2020/094735 CN2020094735W WO2020244642A1 WO 2020244642 A1 WO2020244642 A1 WO 2020244642A1 CN 2020094735 W CN2020094735 W CN 2020094735W WO 2020244642 A1 WO2020244642 A1 WO 2020244642A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
pdcp
data packet
data packets
redundant information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/094735
Other languages
English (en)
French (fr)
Inventor
汤德龙
仇力炜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2020244642A1 publication Critical patent/WO2020244642A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a redundant information feedback method and communication device.
  • the uplink dynamic diversion is a common user plane data transmission mode.
  • the uplink data of user equipment (UE) can be shunted to the evolution node base station (eNB) through the 4G air interface, and to the next generation node B (gNB) through the 5G air interface.
  • the data finally converges at the anchor base station (gNB or eNB), and the anchor reorders the received data and transmits the data to the core network.
  • the anchor base station When the anchor base station receives a discontinuous data packet, it will start a timer. Before the timer expires, if the data packets are filled, the anchor base station continues to transmit the data packet to the core network; otherwise, the anchor base station needs to wait for the timer to expire before continuing to transmit the data packet.
  • timer If the timer is set too small, data packets that are not received with a large delay may be regarded as packet loss, causing abnormal handling at the application layer, resulting in a poor experience for the upper application. Therefore, a relatively large timer is generally set, and the anchor base station stops transmitting data packets during the running of the timer. During this period, the bandwidth between the anchor base station and the core network is in an idle state, and bandwidth is wasted seriously.
  • the embodiments of the present application provide a redundant information feedback method and a communication device, which can accurately determine whether the data packet is lost on the air interface or the transmission path between nodes, and take different treatments for two different lost data packets, so as to timely The timer for waiting for packet loss is terminated or the timer for waiting for packet loss is not started, so as to avoid waiting for packet loss for a long time, reduce bandwidth waste, save cost, and improve communication efficiency.
  • a redundant information feedback method is disclosed, which can be executed by a first communication device (a first node or a chip in the first node).
  • the first node is taken as an example for introduction.
  • the execution subject of this method can be replaced by the first communication device.
  • the first node sends one or more (for example, N) data packets to the second node, each of the one or more data packets includes the PDCP SN of the data packet; the first node Send redundant information to the second node, where the redundant information includes the one or more (for example, N) PDCP SNs, the one or more (for example, N) PDCP SNs and the one or more There are one (for example, N) data packets in one-to-one correspondence.
  • the second node By sending the PDCP SN of one or more data packets after sending one or more data packets, it is convenient for the second node to determine which data packets are lost on the transmission path between the nodes, except for the first node and the first node. For data packets lost on the transmission path between the two nodes, the second node finds that other unreceived packets are lost on the air interface when performing PDCP reordering, and the second node can then perform processing on these two different lost data packets. Different treatment.
  • the second node when the PDCP entity of the second node finds that the data packet received from the first node is not continuous, it starts a timer to wait for the data packet.
  • the second node may determine whether packet loss occurs when the first node sends multiple data packets to the second node according to the redundant information from the first node. Once the second node determines that there is a packet loss on the transmission path of the first node and the second node, it will skip the data packet when reordering the data packet. For example, if the timer for waiting for the data packet has been started, it will terminate the waiting for the data packet.
  • the second node can continue to deliver data packets to the core network; or, if the timer for waiting for the data packet has not yet started, the timer for waiting for the data packet is not started, and the currently running timer (waiting After other data packets) time out, the second node can continue to deliver data packets to the core network. It can be seen that the method provided by the embodiments of the present application can avoid waste of bandwidth caused by long-term waiting for lost data packets, and can reduce the time delay for the second node to send data to the core network element, which is beneficial to improving communication performance.
  • each of the one or more (for example, N) data packets further includes an identification sequence number of the data packet; redundancy
  • the information also includes the one or more (for example, N) identification serial numbers, and the one or more (for example, N) identification serial numbers have a one-to-one correspondence with the one or more (for example, N) PDCP SNs.
  • the second node after receiving multiple data packets, parses the data packets to obtain the identification serial numbers therein, and can further determine whether the received data packets are continuous according to the identification serial numbers, or can determine whether the first node and the second node are continuous Whether packets are lost on the node's transmission path.
  • the second node may also determine the PDCP SN of the packet loss according to the redundancy information.
  • the multiple identification sequence numbers are continuous.
  • the first node sends multiple data packets with consecutive identification sequence numbers to the second node.
  • the second node can determine whether the packets are lost according to the continuity of the data packets. For example, the data packets received by the second node from the first node are continuous, indicating that there is no packet loss on the transmission path between the first node and the second node; the data packets received by the second node from the first node are not continuous , Indicating that there is packet loss on the transmission path between the first node and the second node.
  • the third possible implementation manner of the first aspect according to the sending order of the one or more data packets, and the one or more The one or more identification sequence numbers corresponding to each data packet are continuous.
  • the first node may determine the identification sequence numbers of the data packets according to the packet sending sequence.
  • the identification sequence numbers of multiple data packets sent by the first node are also continuous.
  • the second node can determine whether the packet is lost according to whether the received data packet is continuous.
  • the redundant information is sent periodically.
  • the first node sends a piece of redundant information after sending one or more data packets, at least indicating the PDCP SN of the data packet sent this time, so that the second node can judge whether there is any loss based on the redundant information. Packets, the timer for waiting for packet loss is terminated, or the timer for waiting for packet loss is not started, so as to prevent the second node from occupying bandwidth for a long time but not transmitting data packets and wasting bandwidth resources.
  • the sending period of the redundant information is less than the duration of the PDCP discard timer.
  • the sending period of the redundant information is less than the duration of the PDCP discarding timer, and the second node can receive the redundant information before the PDCP discarding timer expires. Once it is found that the data packet that triggers the PDCP discarding timer has been lost, The timer is terminated in time to avoid wasting bandwidth resources for a long time.
  • the redundant information includes the last time the redundant information was sent, and the first node sent The one or more PDCP SNs corresponding to the one or more data packets one-to-one.
  • the first node after sending one or more data packets, the first node sends redundant information to the second node indicating the PDCP SN of the one or more data packets, so that the second node can determine according to the redundant information Whether one or more data packets sent by the first node are lost.
  • the timer is terminated in time to avoid wasting bandwidth resources for a long time.
  • the redundant information further includes the redundant information sent last time.
  • the first node may also send redundant information redundantly to improve the reliability of redundant information.
  • the redundant information sent by the first node in the i+1th time may also include the redundant information sent in the i-th time.
  • the second node can still determine the packet loss based on the redundant information.
  • the method further includes: the first node receives the PDCP discard timing from the second node The duration of the device.
  • the second node is responsible for converging data and reordering the data packets before delivering them to the core network. Therefore, the second node maintains the duration information of the PDCP discard timer.
  • the second node may send the duration of the PDCP discard timer to the first node, and the first node may set the period of sending redundancy information according to the duration of the PDCP discard timer, so that the second node receives the redundancy before the PDCP discard timer expires. More information.
  • the first node sends the redundant information There is a first threshold difference between the time at and the time at which the first node completes sending the one or more data packets.
  • the second node may cause the second node to mistakenly think that the data packet is lost, and jump during reordering. Pass the packet.
  • the first node sends a data packet and redundant information for a certain period of time. Try to ensure that the second node receives a data packet before receiving the redundant information associated with the data packet. This can prevent the second node from mistakenly thinking that the data packet is lost. Wrong reordering operation.
  • the first node is directed to the second node
  • Sending redundant information specifically includes:
  • the first node After the first node completes the sending of the one or more data packets, it first sends one or more other data packets, and then sends the redundant information to the second node.
  • the second node receives the redundant information associated with the data packet first, and then receives the data packet due to the influence of the network delay, it may cause the second node to mistakenly think that the data packet is lost, and jump during reordering. Pass the packet.
  • the first node sends data packets and redundant information at intervals of N data packets, as far as possible to ensure that the second node receives a certain data packet before receiving the redundant information associated with the data packet, which can prevent the second node from mistakenly thinking that the data packet is lost , To avoid wrong reordering operations.
  • the first node sends the information to the second Sending redundant information by a node specifically includes: the first node repeatedly sending the redundant information until confirmation information is received from the second node, where the confirmation information is used to confirm receipt of the redundant information.
  • the reliability of redundant information can be improved through repeated transmission.
  • the redundant information is carried in a service data packet, and the service data packet is different from the one or more data packets.
  • the redundant information may be carried in other data packets (the same type as the first one or more data packets sent by the first node, including service data) and sent to the gNB.
  • the eNB sends a data packet, it is accompanied by the PDCP SN of one or more data packets previously sent.
  • the redundant information is carried in a data packet other than a service data packet.
  • the first node may also construct a dedicated data packet to send redundant information.
  • a data packet may not include service data and is only used to carry redundant information.
  • a redundant information feedback method is disclosed.
  • the redundant information feedback method can be performed by a second communication device (a second node or a chip in the second node).
  • the second node is used as an example to introduce the method below. It should be noted that the execution subject of this method can be replaced with a second communication device.
  • the second node receives redundant information from the first node, the redundant information includes one or more (for example, N) packet data convergence protocol serial numbers PDCP SN; the one or more (for example, N) PDCP SN and One or more (for example, N) data packets sent by the first node to the second node have a one-to-one correspondence, and each of the one or more data packets (for example, N) includes the PDCP SN of the data packet.
  • the redundant information includes one or more (for example, N) packet data convergence protocol serial numbers PDCP SN
  • the one or more (for example, N) PDCP SN and
  • One or more (for example, N) data packets sent by the first node to the second node have a one-to-one correspondence, and each of the one or more data packets (for example, N) includes the PDCP SN of the data packet.
  • N is greater than or equal to M
  • the first node sends N data packets to the second node.
  • the second node may have received some or all of the one or more data packets, and there may be some data packets that the second node did not receive. To.
  • the above method may further include: the second node receives M data packets from the first node, each of the M data packets includes the packet data convergence protocol PDCP sequence number SN of the data packet, and M is greater than or equal to An integer of 1. Or, the second node may not receive the data packet from the first node. It can be understood that the N data packets sent by the first node are all lost. At this time, the second node only receives redundant information, including N PDCP SN numbers. , But does not include business data packages.
  • each of the one or more (for example, N) data packets sent by the first node further includes the information of the data packet Identification sequence number
  • each of the M data packets received by the second node includes the identification sequence number of the data packet.
  • the redundant information further includes the one or more (for example, N) identification sequence numbers, and the one or more (for example, N) identification sequence numbers are the same as the one or more (for example, N) PDCP SNs.
  • N identification sequence numbers
  • the identification sequence numbers are continuous.
  • the third possible implementation of the second aspect according to the sending order of the one or more (for example, N) data packets, the one or more (for example, N) identification serial numbers corresponding to the one or more (for example, N) data packets are continuous. However, since the second node only receives M data packets, the identification sequence numbers of the M data packets may not be continuous.
  • the redundant information is received periodically.
  • the first node sends the redundant information periodically, but the second node receives the redundant information sometimes, and other times it does not receive the redundant information, and the second node receives the redundant information not periodically.
  • the receiving period of the redundant information is less than the duration of the PDCP discard timer.
  • the second node receiving redundant information is not periodic, but the time interval between receiving redundant information twice is less than the duration of the PDCP discard timer.
  • the redundant information includes the information received from the first node after the last redundant information is received
  • the redundant information further includes the redundant information received last time.
  • the duration information of the PDCP discard timer is sent to the first node.
  • the method further includes: when the second aspect The node determines that the data packet corresponding to the first PDCP SN in the redundant information is not received, and when the second node performs PDCP reordering, it skips the data packet corresponding to the first PDCP SN, and the first PDCP The SN is one PDCP SN of the one or more PDCP SNs.
  • the N identification sequence numbers corresponding to the N data packets sent by the first node are continuous, however, since the second node only receives M data packets, the M identification sequence numbers corresponding to the M data packets are not continuous, and the method further includes: when the second node receives the multiple (for example, M) ) The continuity of the respective identification serial numbers determines that the first identification serial number is not received, and the first identification serial number is one of the plurality (for example, N) identification serial numbers, and the PDCP corresponding to the first identification serial number SN is the first PDCP SN, and when the second node performs PDCP reordering, the data packet corresponding to the first PDCP SN is skipped.
  • the eleventh possible implementation manner of the second aspect when the second node performs PDCP reordering, the data corresponding to the first PDCP SN is skipped
  • the packet includes: if the PDCP discard timer of the data packet corresponding to the first PDCP SN is started, stop the PDCP discard timer of the data packet corresponding to the first PDCP SN; or, if the first PDCP SN If the PDCP discard timer of the corresponding data packet is not started, then the PDCP discard timer of the data packet corresponding to the first PDCP SN is abandoned.
  • the method further includes: sending a PDCP SN greater than the first PDCP to the core network SN packet.
  • the method further includes: The first node sends confirmation information, where the confirmation information is used to confirm receipt of the redundant information.
  • the one or more data packets are data packets of a first data radio bearer, and the radio link control RLC layer of the first data radio bearer In the first node, the PDCP layer of the first data radio bearer is in the second node.
  • the data packets sent by the first node to the second node may be out of order, and the second node may sort the data packets received from the first node; or, the first node may use the first data wireless
  • the PDCP SN that bears the data packets sent to the second node is not continuous.
  • the second node can also receive data packets from other bearers (for example, the second bearer), and the second node can receive data packets through the first data radio bearer and the second bearer. The received data packets are mixed and sorted.
  • the communication between the MN and the UE can be realized through the first data radio bearer, and the communication between the SN and the UE can also be realized through the first data radio bearer.
  • the first data radio bearer may be a data radio bearer. There is only one PDCP entity corresponding to the first data radio bearer on the network side, but the first data radio bearer may correspond to two RLC bearers on the network side, and the two RLC bearers are in the MN. And SN (that is, offloaded bearer).
  • the first data radio bearer is a secondary cell group SCG bearer terminated by the master node MN, or, an offloaded bearer terminated by the master node MN, or a secondary node SN-terminated primary cell group MCG bearer, or SN-terminated offload bearer.
  • the first node is a distributed unit DU
  • the second node is a centralized CU.
  • a communication device which may be a first node or a chip in the first node.
  • the communication device may include units corresponding to the steps in the method of the first aspect described above, and reference may be made to the method of the first aspect described above.
  • the communication device includes: a communication unit configured to send one or more (for example, N) data packets to a second node, each of the one or more data packets includes the PDCP SN of the data packet.
  • the communication unit is further configured to send redundant information to the second node, where the redundant information includes the one or more PDCP SN, the one or more PDCP SN and the one or more data packets There is a one-to-one correspondence.
  • each of the one or more data packets further includes the identification sequence number of the data packet; the redundant information further includes the One or more identification serial numbers, and the one or more identification serial numbers have a one-to-one correspondence with the one or more PDCP SNs.
  • the multiple identification sequence numbers are continuous.
  • the same as the one or more The one or more identification sequence numbers corresponding to each data packet are continuous.
  • the redundant information is sent periodically.
  • the sending period of the redundant information is less than the duration of the PDCP discard timer.
  • the redundant information includes the last time the redundant information is sent, and the first node sends The one or more PDCP SNs corresponding to the one or more data packets one-to-one.
  • the redundant information further includes the redundant information sent last time.
  • the communication unit is further configured to receive the duration information of the PDCP discard timer from the second node.
  • the first node sends the redundant information There is a first threshold difference between the time at and the time at which the first node completes sending the one or more data packets.
  • the communication unit is specifically configured to complete the one or After the multiple data packets are sent, N other data packets are sent first, and then the redundant information is sent to the second node.
  • the communication unit is specifically configured to repeatedly send the Redundant information until the confirmation information is received from the second node, and the confirmation information is used to confirm receipt of the redundant information.
  • the redundant information is carried in a service data packet, and the service data packet is different from the one or more data packets.
  • the redundant information is carried in a data packet other than a service data packet.
  • one or more data packets sent by the first node to the second node may be recorded as N data packets, and N is an integer greater than or equal to 1.
  • a communication device which may be a first node or a chip in the first node.
  • the communication device may include units corresponding to the steps in the method of the second aspect described above, and reference may be made to the method of the second aspect described above.
  • the communication device includes: a communication interface for sending one or more data packets to a second node, each of the one or more data packets includes the PDCP SN of the data packet; the communication interface is also used for Send redundant information to the second node, where the redundant information includes the one or more PDCP SNs, and the one or more PDCP SNs and the one or more data packets are in a one-to-one correspondence.
  • each of the one or more data packets further includes the identification sequence number of the data packet; the redundant information further includes the One or more identification serial numbers, and the one or more identification serial numbers have a one-to-one correspondence with the one or more PDCP SNs.
  • the multiple identification sequence numbers are continuous.
  • the same as the one or more The one or more identification sequence numbers corresponding to each data packet are continuous.
  • the redundant information is sent periodically.
  • the sending period of the redundant information is less than the duration of the PDCP discard timer.
  • the redundant information includes the last time the redundant information was sent, and the first node sent The one or more PDCP SNs corresponding to the one or more data packets one-to-one.
  • the redundant information further includes the redundant information sent last time.
  • the communication interface is further configured to receive the duration information of the PDCP discard timer from the second node.
  • the first node sends the redundant information There is a first threshold difference between the time at and the time at which the first node completes sending the one or more data packets.
  • the communication interface is specifically used to complete the one or After the multiple data packets are sent, one or more other data packets are sent first, and then the redundant information is sent to the second node.
  • the communication interface is specifically used to repeatedly send the Redundant information until the confirmation information is received from the second node, and the confirmation information is used to confirm receipt of the redundant information.
  • the redundant information is carried in a service data packet, and the service data packet is different from the one or more data packets.
  • the redundant information is carried in a data packet other than a service data packet.
  • one or more data packets sent by the first node to the second node through the communication interface may be referred to as N data packets, and N is an integer greater than or equal to 1.
  • a communication device which may be a second node or a chip in the second node. It includes: a communication unit configured to receive redundant information from a first node, the redundant information includes one or more packet data convergence protocol serial numbers PDCP SN; the one or more PDCP SNs communicate with the first node to the One or more data packets sent by the second node have a one-to-one correspondence, and each data packet in the one or more data packets includes the PDCP SN of the data packet.
  • a communication unit configured to receive redundant information from a first node, the redundant information includes one or more packet data convergence protocol serial numbers PDCP SN; the one or more PDCP SNs communicate with the first node to the One or more data packets sent by the second node have a one-to-one correspondence, and each data packet in the one or more data packets includes the PDCP SN of the data packet.
  • the second node may have received part or all of the one or more data packets, and there may be some data packets that the second node did not receive.
  • the communication unit receives M data packets from the first node, and each data packet in the M data packets includes the packet data convergence protocol PDCP sequence number SN of the data packet, and M is greater than An integer equal to 1.
  • the second node may not receive the data packet from the first node. It can be understood that the N data packets sent by the first node are all lost. At this time, the second node only receives redundant information, including N PDCP SN numbers. , But does not include business data packages.
  • each of the one or more data packets further includes an identification sequence number of the data packet; the redundant information further includes The one or more identification sequence numbers, and the one or more identification sequence numbers have a one-to-one correspondence with the one or more PDCP SNs.
  • the identification sequence numbers are continuous.
  • the same as the one or more The one or more identification sequence numbers corresponding to the data packets are continuous.
  • the redundant information is received periodically.
  • the receiving period of the redundant information is less than the duration of the PDCP discard timer.
  • the redundant information includes the information received from the first node after the redundant information was received last time
  • the redundant information further includes the redundant information received last time.
  • the communication unit is further configured to send duration information of the PDCP discard timer to the first node.
  • a processing unit is further included.
  • the processing unit is configured to: The second node determines that the data packet corresponding to the first PDCP SN in the redundant information is not received, and when the second node performs PDCP reordering, skips the data packet corresponding to the first PDCP SN, so The first PDCP SN is one PDCP SN of the one or more PDCP SNs.
  • the multiple identification sequence numbers are continuous, and the processing unit is specifically configured to: when the second node is based on The continuity of the multiple identification sequence numbers determines that the first identification sequence number is not received, the first identification sequence number is one of the multiple identification sequence numbers, and the PDCP SN corresponding to the first identification sequence number is the first PDCP SN, when the second node performs PDCP reordering, skip the data packet corresponding to the first PDCP SN.
  • the processing unit when the second node performs PDCP reordering, is specifically configured to, if the first If the PDCP discard timer of the data packet corresponding to the PDCP SN is started, stop the PDCP discard timer of the data packet corresponding to the first PDCP SN; or, if the PDCP discard timer of the data packet corresponding to the first PDCP SN If it is not enabled, the PDCP discard timer of the data packet corresponding to the first PDCP SN is abandoned.
  • the communication unit is further configured to send a PDCP SN greater than the first PDCP to the core network SN packet.
  • the communication unit is further configured to: The first node sends confirmation information, where the confirmation information is used to confirm receipt of the redundant information.
  • a communication device which may be a second node or a chip in the second node. It includes: a communication unit configured to receive redundant information from a first node, the redundant information includes one or more packet data convergence protocol serial numbers PDCP SN; the one or more PDCP SNs communicate with the first node to the One or more data packets sent by the second node have a one-to-one correspondence, and each data packet in the one or more data packets includes the PDCP SN of the data packet.
  • a communication unit configured to receive redundant information from a first node, the redundant information includes one or more packet data convergence protocol serial numbers PDCP SN; the one or more PDCP SNs communicate with the first node to the One or more data packets sent by the second node have a one-to-one correspondence, and each data packet in the one or more data packets includes the PDCP SN of the data packet.
  • the second node may have received part or all of the one or more data packets, and there may be some data packets that the second node did not receive.
  • M data packets are received from the first node through a communication interface, each of the M data packets includes the packet data convergence protocol PDCP serial number SN of the data packet, and M is An integer greater than or equal to 1.
  • the second node may not receive the data packet from the first node. It can be understood that the N data packets sent by the first node are all lost. At this time, the second node only receives redundant information, including N PDCP SN numbers. , But does not include business data packages.
  • each of the one or more data packets further includes the identification sequence number of the data packet; the redundant information further includes The one or more identification sequence numbers, and the one or more identification sequence numbers have a one-to-one correspondence with the one or more PDCP SNs.
  • the identification sequence numbers are continuous.
  • the same The one or more identification sequence numbers corresponding to the data packets are continuous.
  • the redundant information is received periodically.
  • the receiving period of the redundant information is less than the duration of the PDCP discard timer.
  • the redundant information includes the information received from the first node after the redundant information was received last time
  • the redundant information further includes the redundant information received last time.
  • the communication unit is further configured to send duration information of the PDCP discard timer to the first node.
  • the ninth possible implementation manner of the sixth aspect further includes a processing unit, and the processing unit is configured to: The second node determines that the data packet corresponding to the first PDCP SN in the redundant information is not received, and when the second node performs PDCP reordering, skips the data packet corresponding to the first PDCP SN, so The first PDCP SN is one PDCP SN of the one or more PDCP SNs.
  • the multiple identification sequence numbers are continuous, and the processing unit is specifically configured to: when the second node is based on The continuity of the multiple identification sequence numbers determines that the first identification sequence number is not received, the first identification sequence number is one of the multiple identification sequence numbers, and the PDCP SN corresponding to the first identification sequence number is the first PDCP SN, when the second node performs PDCP reordering, skip the data packet corresponding to the first PDCP SN.
  • the processing unit when the second node performs PDCP reordering, is specifically configured to, if the first If the PDCP discard timer of the data packet corresponding to the PDCP SN is started, stop the PDCP discard timer of the data packet corresponding to the first PDCP SN; or, if the PDCP discard timer of the data packet corresponding to the first PDCP SN If it is not enabled, the PDCP discard timer of the data packet corresponding to the first PDCP SN is abandoned.
  • the communication unit is further configured to send a PDCP SN greater than the first PDCP to the core network SN data packet.
  • the communication unit is further configured to: The first node sends confirmation information, where the confirmation information is used to confirm receipt of the redundant information.
  • a communication device which is characterized in that it comprises a processor, which is coupled with a memory; and the memory is used to store a computer program.
  • the processor is configured to execute the computer program stored in the memory, so that the device executes the foregoing first aspect, any one of the possible implementation manners of the first aspect, the second aspect, and any one of the possible implementation manners of the second aspect.
  • a readable storage medium including a program or instruction.
  • the program or instruction is executed by a processor, such as the first aspect, any possible implementation of the first aspect, the second aspect, and the first aspect The method described in any one of the possible implementations in the second aspect.
  • a computer-readable storage medium including instructions, which when run on a computer, cause the computer to execute the first aspect and any one of the possible implementations of the first aspect, the second aspect, and the second aspect. The method described in any one of the possible implementation manners.
  • a computer program product including instructions, which when run on a computer, cause the computer to execute any of the above-mentioned first aspect and any one of the possible implementation manners of the first aspect, the second aspect, and the second aspect Any one of the possible implementation methods.
  • a wireless communication device including: instructions stored in the wireless communication device; when the wireless communication device runs on the device described in the third aspect to the sixth aspect, the device is caused to perform the implementation as described above
  • the wireless communication device is a chip.
  • an embodiment of the present application provides a chip that includes a processor and an interface circuit, the interface circuit is coupled to the processor, and the processor is used to run a computer program or instruction to implement the above-mentioned first aspect
  • the interface circuit is used to communicate with other modules outside the chip.
  • an embodiment of the present application provides a communication system.
  • the communication system includes a first node and a second node.
  • the first node sends one or more data packets to the second node, and each of the one or more data packets includes the PDCP SN of the data packet; the first node sends the The two nodes send redundant information, where the redundant information includes the one or more PDCP SNs, and the one or more PDCP SNs have a one-to-one correspondence with the one or more data packets.
  • FIG. 1A is an architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 1B is another architecture diagram of the communication system provided by an embodiment of this application.
  • FIG. 1C is another architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 1D is another architecture diagram of the communication system provided by an embodiment of this application.
  • FIG. 1E is another architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 1F is another architecture diagram of the communication system provided by an embodiment of this application.
  • FIG. 1G is a schematic diagram of a network-side protocol architecture provided by an embodiment of this application.
  • FIG. 1H is another architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 1I is another architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 1J is another architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 1K is another architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 2A is a structural block diagram of a communication device provided by an embodiment of this application.
  • 2B is a structural block diagram of DU and CU provided by an embodiment of this application.
  • FIG. 3 is a schematic flowchart of a redundant information feedback method provided by an embodiment of the application.
  • Figure 4 is a schematic diagram of a data packet provided by an embodiment of the application.
  • FIG. 5 is another schematic diagram of a data packet provided by an embodiment of the application.
  • FIG. 6 is another schematic diagram of a data packet provided by an embodiment of the application.
  • FIG. 7 is another schematic flowchart of a redundant information feedback method provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of a redundant information feedback method provided by an embodiment of the application.
  • FIG. 9 is another schematic diagram of a redundant information feedback method provided by an embodiment of the application.
  • FIG. 10 is another structural block diagram of a communication device provided by an embodiment of the application.
  • FIG. 11 is another structural block diagram of a communication device provided by an embodiment of this application.
  • the PDCP layer mainly processes RRC messages from the control plane and IP packets from the data plane, including: header compression and decompression, encryption/decryption, integrity protection, transmission of user data and control plane data, Reordering and retransmission processing, etc.
  • both the received data packet and the transmitted data packet are regarded as PDCP data packets.
  • the data packet received by the PDCP layer may be referred to as a PDCP service data unit (SDU)
  • the data packet sent by the PDCP layer may be referred to as a PDCP protocol data unit (PDU).
  • SDU PDCP service data unit
  • PDU PDCP protocol data unit
  • PDCP SN is the number of PDCP data packets, and different PDCP SNs are used to identify different PDCP data packets.
  • the PDCP SN of the PDCP data received by the PDCP layer may be continuous; in the case of poor network conditions, packet loss may occur.
  • the PDCP SN of the PDCP data packets received by the PDCP layer is Discontinuous. If the network delay is large, the PDCP SN of the PDCP data packet received by the PDCP layer may be out of order.
  • the embodiment of the present application provides a communication system.
  • the communication system may include at least two nodes, and the two nodes may be connected through an interface between the two nodes.
  • the two nodes can be two different access network devices, or different units on the same access network device.
  • these two nodes are centralized units (CU) in the access network device.
  • DU Distributed unit
  • the RLC layer of the node can send the data packet to the PDCP layer of another node through the interface between the nodes, and the PDCP layer of the other node will reorder and then reorder The latter data packet is sent to the core network.
  • the method provided in the embodiment of the present application is applicable to the communication system shown in FIG. 1A.
  • multiple (two sending nodes are taken as an example in FIG. 1A) sending nodes send data to one receiving node.
  • the sending node 1 sends data to the receiving node through the transmission link 1
  • the sending node 2 sends data to the receiving node through the transmission link 2.
  • the PDCP SN of the PDCP data packets received by the receiving node may be out of order, and the receiving node needs to reorder the received PDCP data packets.
  • packet loss may also occur on transmission link 1 and transmission link 2, that is, in the scenario of receiving node reordering, packet loss may occur on the transmission path between the sending and receiving nodes.
  • the sending node 1 can be a terminal, an access network device, or a unit in an access network device
  • the sending node 2 can be a terminal, an access network device, or a unit in an access network device
  • the receiving node can be an access network device.
  • the communication system shown in FIG. 1A supports dual connectivity (DC).
  • the method provided in the embodiment of the present application is applicable to the communication system shown in FIG. 1B.
  • Figure 1B only one sending node sends data to the receiving node.
  • the data packets sent by the sending node to the receiving node are out of order, and the receiving node needs to reorder the received data packets.
  • there may be packet loss on the transmission link between the sending node and the receiving node that is to say, in the scenario of reordering the receiving node, there is a possibility of packet loss on the transmission link.
  • the sending node may be an access network device or a unit in an access network device; the receiving node may be an access network device or a unit in an access network device.
  • the communication system shown in Figure 1B supports DC or single connection.
  • Figure 1C is a DC scenario to which the method provided in the embodiments of this application is applicable.
  • Figure 1C shows the evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA) and the new radio (NR) Dual Connectivity (E-UTRA-NR Dual Connectivity, EN-DC).
  • the core network element is an evolved packet core (EPC) network element
  • the master node (MN) is an eNB
  • the secondary node (SN) is a gNB.
  • the interface between the eNB, gNB and EPC network element is the s1 interface.
  • MN and SN can be connected through the X2 interface, and there can be a user plane connection between MN and SN; MN and core network elements can be connected through S1 interface, MN and core network elements can have user plane connections; SN11 and core network The network elements can be connected through the S1-U interface, and there can be user plane connections between the network elements of the SN core network.
  • Fig. 1D is a DC scenario to which the method provided in the embodiments of the present application is applicable.
  • Fig. 1D shows the evolved general land-based radio access (evolved) of the next generation (NG) radio access network (RAN).
  • NG next generation
  • E-UTRA Universal terrestrial radio access
  • NG-RAN E-UTRA-NR Dual Connectivity NGEN-DC
  • the core network element is the fifth generation (5G, 5th Generation) core network (5G core, 5GC) network element
  • the master node (MN) is the eNB
  • the secondary node (SN) ) Is gNB.
  • the interface between eNB, gNB and EPC network element is the s1 interface.
  • MN and SN can be connected through Xn interface, MN and SN can have user plane connection; MN and core network element can be connected through NG interface, MN and core network element can have user plane connection; SN and Core network elements can be connected through NG-U interfaces, and SN core network elements can have user plane connections.
  • Fig. 1E is a DC scenario to which the method provided in the embodiments of the present application is applicable.
  • Fig. 1E shows a dual connectivity (NR-E-UTRA dual connectivity, NE-DC) network architecture of NR and E-UTRA.
  • the core network element is a 5GC network element
  • MN is a gNB
  • SN is an eNB.
  • MN and SN can be connected, for example, through an Xn interface.
  • FIG. 1F is a DC scenario to which the method provided in the embodiment of the present application is applicable, and FIG. 1F shows the dual connectivity of NR and NR (NR-NR Dual Connectivity, NR-DC).
  • the core network element is a 5GC network element
  • MN is a gNB
  • SN11 is a gNB.
  • MN and SN can be connected, for example, through an Xn interface.
  • the MN can be connected to the core network element, for example, through the NG interface, there can be a user plane connection between the MN and the core network element;
  • the SN can be connected to the core network element, for example, NG-U interface, SN core network network elements can have user plane connections.
  • the communication systems applicable to the embodiments of the present application include, but are not limited to, the communication systems shown in FIGS. 1A to 1F.
  • the receiving node needs to reorder the data packets, and the scenarios where there is packet loss on the transmission link between the receiving and sending nodes all apply the method provided in the embodiment of this application, which is not limited in this application.
  • Fig. 1G a schematic diagram of a protocol architecture from the perspective of the network side. From the perspective of the network side (MN01 and SN11), there can be the following 6 types of user plane bearers. The following behavior examples respectively introduce the data flow direction of each bearer type. Those skilled in the art can understand that the uplink is similar to the downlink, and will not be repeated here.
  • the master cell group (MCG) terminated by the MN is carried.
  • PDCP packet data convergence protocol
  • RLC Radio Link Control
  • Media Access Media Access
  • Control, MAC media access control
  • the secondary cell group (SCG) terminated by the MN is carried.
  • Data is sent from the core network element to the MN, sent to the RLC layer of the SN via the PDCP layer of the MN, and sent to the terminal via the RLC layer and the MAC layer of the SN in turn.
  • Data is sent from the core network element to the MN.
  • the PDCP layer of the MN splits the data. Part of the data is sent to the terminal through the RLC layer and the MAC layer of the MN in turn, and the other part of the data is sent to the RLC layer of the SN, which in turn passes through the RLC layer of the SN.
  • the layer and MAC layer are sent to the terminal.
  • Data is sent from the core network element to the SN.
  • the PDCP layer of the SN splits the data. Part of the data is sent to the terminal through the RLC layer and the MAC layer of the SN, and the other part of the data is sent to the RLC layer of the MN, and then passes through the RLC layer of the MN.
  • the layer and MAC layer are sent to the terminal.
  • MCG bearer terminated by SN.
  • Data is sent from the core network element to the SN, sent to the RLC layer of the MN through the PDCP layer of the SN, and sent to the terminal through the RLC layer and the MAC layer of the MN in turn.
  • Data is sent from the core network element to the SN, and then sent to the terminal through the PDCP layer, RLC layer, and MAC layer of the SN.
  • the aforementioned MCG bearer relates to MCG air interface resources
  • SCG bearer relates to SCG air interface resources
  • Split bearer relates to MCG air interface resources and SCG air interface resources.
  • the PDCP entities of MN and SN can be NR PDCP entities.
  • the PDCP entity of MN can also be E-UTRA PDCP.
  • the core network element is a 5GC network element
  • there can be an SDAP layer on the PDCP layer of the MN and the data is sent from the core network element to the MN, and then reaches the PDCP layer of the MN through the SDAP layer of the MN;
  • the SDAP layer data is sent from the core network element to the SN11, and then reaches the PDCP layer of S1 through the SDAP layer of SN.
  • Figure 1H is a DC scenario to which the method provided in the embodiments of the present application is applicable.
  • Figure 1H shows the NSA DC Option 3 networking architecture.
  • the bearer type involved in this scenario is MN terminated Split bearer.
  • the dynamic offload mechanism is enabled. For example, the data sent by the UE arrives at the eNB via the LTE air interface, and arrives at the gNB via the NR air interface. The gNB needs to send received data packets to the eNB through the X2 interface between the base station and the base station.
  • the eNB needs to reorder the data packets received by the air interface and the data packets transmitted by the gNB, and then the eNB transmits the data packets to the core network. It should be noted that packet loss may occur when the gNB sends data packets to the eNB, that is, in the eNB reordering scenario, there may be packet loss on the transmission path between the gNB and the eNB, and it can also be considered that there is a possibility of packet loss on the X2 interface.
  • FIG. 1I shows the non-standalone (NSA) dual connectivity (DC) Option3x networking architecture.
  • NSA non-standalone
  • DC dual connectivity
  • the bearer type involved in this scenario is SN-terminated Split bearer.
  • the data sent by the UE reaches the evolution node base station (eNB) through the long term evolution (LTE) air interface, and reaches the next generation node B (gNB) through the NR air interface.
  • the eNB needs to send the received data packets to the gNB through the X2 interface between the base station and the base station.
  • LTE long term evolution
  • gNB next generation node B
  • the gNB needs to reorder the data packets received by the air interface and the data packets transmitted by the eNB, and then the gNB transmits the data packets to the core network. It should be noted that packet loss may occur when the eNB sends data packets to the gNB. That is to say, in the gNB reordering scenario, there may be packet loss on the transmission path between the gNB and the eNB, and it can also be considered that there is a possibility of packet loss on the X2 interface.
  • Fig. 1J is a DC scenario to which the method provided in the embodiments of the present application is applicable.
  • the dynamic offload mechanism is not enabled, and the bearer type involved in this scenario is the SCG bearer terminated by the MN.
  • the data packet sent by the UE reaches the gNB via the NR air interface. Due to air interface errors, some data packets need to be retransmitted, and some data packets are successfully transmitted at one time, so the data packets may be out of order after they reach the NR radio link control (RLC) entity.
  • the NR RLC entity does not reorder the data packets.
  • the LTE PDCP entity After receiving the data packet, it will be delivered to the LTE PDCP entity, and the LTE PDCP will reorder the packets.
  • the data packets sent by the gNB to the eNB are out of order at this time, and the eNB needs to reorder the received data packets before delivering them to the core network.
  • Packet loss may occur when the gNB sends data packets to the eNB.
  • FIG. 1K is a networking structure to which the method provided in the embodiment of the present application is applicable, and FIG. 1K shows a pure 5G networking.
  • the RAN base station is separated into two components, CU and DU, and the interface between CU and DU can be called F1 interface.
  • the data packets sent by the UE arrive at the distributed unit (DU) of the gNB out of order through the NR air interface, and the DU of the gNB forwards the out-of-order data packets to the centralized unit (CU) of the gNB through the F1 interface.
  • GNB CU reorders the received data packets. That is to say, in the scenario of receiving node reordering, there is a possibility of packet loss on the transmission path between the receiving and sending nodes, and it can also be considered that there is a possibility of packet loss on the F1 interface.
  • the transmission interface between the eNB and the gNB in the aforementioned NSA networking architecture is called the X2 interface; the air interface between the UE and the base station is called the UU interface.
  • the transmission path between nodes can be understood as links between nodes.
  • nodes can be connected through interfaces, and transmission paths between nodes can be understood as interfaces between nodes, which are connected to the network.
  • the transmission path between the device and the terminal can be understood as the air interface between the access network device and the terminal.
  • the UE needs to send data packets with PDCP SN 1 to 9 to the core network.
  • the UE sends data packets with PDCP SN 3, 6, and 9 to the eNB through the air interface.
  • the eNB sends data packets with PDCP and SN of 3, 6, and 9 to the gNB through the X2 interface.
  • the UE sends other messages to the gNB through the air interface.
  • the data packets with PDCP SN 3, 6, and 9 arrive at the gNB later than other packets.
  • a data packet with PDCP SN 1, 2 arrives at the gNB, it is directly delivered to the core network by the gNB.
  • the data packet with PDCP SN of 4 arrives at the gNB, because the data packet with PDCP SN of 3 does not reach the gNB, the PDCP SN is not continuous, and the gNB starts a timer to wait for the packet with PDCP SN of 3, and suspends sending data packets to the core network .
  • the gNB will deliver the data packet with PDCP SN of 3 to the core network, and then deliver the data packet with PDCP SN of 4 and 5 to the core network.
  • the data packet with PDCP SN of 3 still arrives at the gNB, and the gNB directly delivers the data packet with PDCP SN of 4 and 5 to the core network without waiting for the data packet with PDCP SN of 3.
  • the gNB directly delivers the data packet with PDCP SN of 4 and 5 to the core network without waiting for the data packet with PDCP SN of 3.
  • there is no data transmission between the gNB and the core network that is, the transmission bandwidth during this period of time is wasted.
  • the embodiment of the present application provides a method. After the first node sends one or more data packets to the second node, the first node also sends redundant information to the second node, and the redundant information includes the one or more data packets.
  • the PDCP SN of the package First, the second node can determine whether packet loss occurs when the first node sends multiple data packets to the second node according to the redundant information. Therefore, the second node can accurately determine whether the lost data packet occurred on the air interface or on the air interface. For the interface between nodes, the second node can choose different strategies to deal with lost data packets when reordering.
  • the second node can skip the data packet when reordering the data packet. For example, suppose the timer for waiting for the data packet has been started. , The timer for waiting for the data packet is terminated, and the second node can continue to deliver the data packet to the core network; or, if the timer for waiting for the data packet has not yet started, the timer for waiting for the data packet is not started, and it is currently running After the timer (waiting for other data packets) expires, the second node can continue to deliver data packets to the core network.
  • the loss The packet may occur on the air interface, and the second node can start a timer waiting for the data packet, wait for the missing data packet, and deliver the data packet to the core network until the timer expires. It can be seen that the method provided in the embodiment of the present application can accurately determine the transmission path where the packet is lost, and avoid the waste of bandwidth caused by waiting for the lost data packet for a long time, which is beneficial to improving the communication performance.
  • Fig. 2A is a structural block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 210 shown in Fig. 2A may be an access network device, for example, may be the first node or the second node involved in the embodiment of the present application.
  • the access network device includes at least one processor 2101, at least one memory 2102, at least one transceiver 2103, at least one network interface 2104, and one or more antennas 2105.
  • the processor 2101, the memory 2102, the transceiver 2103, and the network interface 2104 are connected, for example, by a bus. In the embodiment of the present application, the connection may include various interfaces, transmission lines, or buses, etc., which is not limited in this embodiment .
  • the antenna 2105 is connected to the transceiver 2103.
  • the network interface 2104 is used to connect the access network device to other communication devices through a communication link.
  • the network interface 2104 may include the network interface between the access network device and the core network element, such as the S1 interface.
  • the network interface may include A network interface between an access network device and other network devices (such as other access network devices or core network elements), such as an X2 or Xn interface.
  • the processor 2101 is mainly used to process communication protocols and communication data, and to control the entire access network equipment, execute software programs, and process data of the software programs, for example, to support the access network equipment to execute the description in the embodiments action.
  • the access network equipment may include a baseband processor and a central processing unit.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processing unit is mainly used to control the entire terminal device, execute software programs, and process software programs. data.
  • the processor 2101 in FIG. 2A can integrate the functions of a baseband processor and a central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit can also be independent processors and are interconnected by technologies such as a bus.
  • the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses.
  • the baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data can be built in the processor, or can be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the memory is mainly used to store software programs and data.
  • the memory 2102 may exist independently and is connected to the processor 2101.
  • the memory 2102 may be integrated with the processor 2101, for example, integrated in one chip.
  • the memory 2102 can store program codes for executing the technical solutions of the embodiments of the present application, and the processor 2101 controls the execution.
  • Various types of computer program codes executed can also be regarded as driver programs of the processor 2101.
  • Figure 2A shows only one memory and one processor. In an actual terminal device, there may be multiple processors and multiple memories.
  • the memory may also be referred to as a storage medium or storage device.
  • the memory may be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element, which is not limited in the embodiment of the present application.
  • the transceiver 2103 may be used to support the reception or transmission of radio frequency signals between the access network device and the terminal, and the transceiver 2103 may be connected to the antenna 2105.
  • the transceiver 2103 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 2105 can receive radio frequency signals, and the receiver Rx of the transceiver 2103 is used to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and convert the digital
  • the baseband signal or digital intermediate frequency signal is provided to the processor 2101, so that the processor 2101 performs further processing on the digital baseband signal or digital intermediate frequency signal, such as demodulation processing and decoding processing.
  • the transmitter Tx in the transceiver 2103 is also used to receive a modulated digital baseband signal or digital intermediate frequency signal from the processor 2101, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and pass it through a Or multiple antennas 2105 transmit the radio frequency signal.
  • the receiver Rx can selectively perform one or more stages of down-mixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal. The order of precedence is adjustable.
  • the transmitter Tx can selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal, the up-mixing processing and digital-to-analog conversion processing
  • the order of precedence is adjustable.
  • Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.
  • the transceiver may also be referred to as a transceiver unit, transceiver, transceiver, etc.
  • the device used to implement the receiving function in the transceiver unit can be regarded as the receiving unit
  • the device used to implement the transmitting function in the transceiver unit can be regarded as the transmitting unit. That is, the transceiver unit includes the receiving unit and the transmitting unit, and the receiving unit is also It can be called a receiver, an input port, a receiving circuit, etc., and a sending unit can be called a transmitter, a transmitter, or a transmitting circuit, etc.
  • the processor 2101 may call the code stored in the memory 2102 to perform the following functions: support the first node to send one or more data packets to the second node, each of the one or more data packets Each data packet includes the packet data convergence protocol serial number PDCP SN of the data packet;
  • the first node is supported to send redundant information to the second node, where the redundant information includes the one or more PDCP SNs, and the one or more PDCP SNs and the one or more data packets are one-to-one corresponding.
  • the second node is supported to receive the one or more data packets from the first node, and the second node is supported to determine whether there is a data packet loss on the transmission path between the first node and the second node according to the redundant information.
  • FIG. 2B is a structural block diagram of a CU and a DU provided in an embodiment of the present application, where the CU may be the second node described in the embodiment of the present application, and the DU may be the first node described in the embodiment of the present application.
  • the base station may include one or more DU 221 and one or more CU 222.
  • CU222 can communicate with NGcore (Next Generation Core Network, NC).
  • NC Next Generation Core Network
  • the DU 221 may include at least one antenna 2211, at least one radio frequency unit 2212, at least one processor 2213, and at least one memory 2214.
  • the DU 221 part is mainly used for the transmission and reception of radio frequency signals, the conversion between radio frequency signals and baseband signals, and part of baseband processing.
  • the CU222 may include at least one processor 2222 and at least one memory 2221.
  • CU222 and DU221 can communicate through interfaces, where the control plan interface can be Fs-C, such as F1-C, and the user plane (User Plan) interface can be Fs-U, such as F1-U.
  • the CU 222 part is mainly used for baseband processing and control of base stations.
  • the DU 221 and the CU 222 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the CU 222 is the control center of the base station, which may also be referred to as a processing unit, and is mainly used to complete baseband processing functions.
  • the CU 222 may be used to control the base station to execute the operation procedure of the network device in the foregoing method embodiment.
  • the baseband processing on the CU and DU can be divided according to the protocol layer of the wireless network, for example, the packet data convergence protocol (PDCP) layer and the functions of the above protocol layers are set in the CU, the protocol layer below PDCP, For example, functions such as the radio link control (RLC) layer and the media access control (MAC) layer are set in the DU.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • CU implements radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP) layer functions
  • DU implements radio link control (radio link control, RLC), media access Control (media access control, MAC) and physical (physical, PHY) layer functions.
  • the base station 60 may include one or more radio frequency units (RU), one or more DUs, and one or more CUs.
  • the DU may include at least one processor 2213 and at least one memory 2214
  • the RU may include at least one antenna 2211 and at least one radio frequency unit 2212
  • the CU may include at least one processor 2222 and at least one memory 2221.
  • the CU222 may be composed of one or more single boards, and multiple single boards may jointly support a wireless access network (such as a 5G network) with a single access indication, and may also support wireless access networks of different access standards.
  • Access network (such as LTE network, 5G network or other networks).
  • the memory 2221 and the processor 2222 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
  • the DU221 can be composed of one or more single boards.
  • Multiple single boards can jointly support a wireless access network with a single access indication (such as a 5G network), and can also support wireless access networks with different access standards (such as LTE network, 5G network or other network).
  • the memory 2214 and the processor 2213 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
  • the embodiment of the application provides a redundant information feedback method, which is applied to the communication system shown in FIG. 1A to FIG. 1F and FIG. 1H to FIG. 1K. As shown in FIG. 3, the method includes the following steps:
  • a first node sends one or more data packets to a second node, where each data packet in the one or more data packets includes the PDCP SN of the data packet.
  • one or more data packets sent by the first node to the second node may be recorded as N data packets, and each of the N data packets includes the PDCP SN of the data packet.
  • the second node may have received the N data packets sent by the first node, or the second node may only receive part of the N data packets.
  • the second node may receive one or more data packets received by the second node.
  • Data packets are called M data packets, each of the M data packets includes the PDCP SN of the data packet, N and M are both integers greater than or equal to 1, and N is greater than or equal to M.
  • the second node may not receive any of the N data packets, and at this time, the N data packets are lost on the transmission path between the first node and the second node.
  • the first node may send data packets to the second node, and the second node may sort the received data packets before submitting to the core network.
  • the first node and the second node may be access network devices.
  • the first node may be the sending node 1 or the sending node 2 in the communication system shown in FIG. 1A
  • the second node may be the receiving node in the communication system shown in FIG. 1A.
  • the first node is the MN in the communication system shown in Figs. 1C to 1E; or, the first node is the MN in the communication system shown in Figs. 1C to 1F, and the second node is the MN in the communication system shown in Figs. 1C to 1F SN; or, the first node is the gNB in the communication system shown in FIG. 1H, and the second node is the eNB in the communication system shown in FIG. 1H; or, the first node is the eNB in the communication system shown in FIG.
  • the node is the gNB in the communication system shown in FIG. 1I; or, the first node is the gNB in the communication system shown in FIG. 1J, and the second node is the gNB in the communication system shown in FIG. 1J.
  • the first node and the second node may be different units in an access network device, the first node may be a CU, and the second node may be a DU.
  • the first node is a DU in the communication system shown in FIG. 1K.
  • the second node is the CU in the communication system shown in Figure 1K.
  • the first node and the second node may respectively receive data packets through the air interface, and the first node may send the data packets received through the air interface to the second node.
  • the data packets finally converge at the second node, and the second node can reorder the data packets received by the air interface and the data packets sent by the first node, and transfer the data packets to the core network after the reordering.
  • the first node may be an eNB in the communication system shown in FIG. 1B
  • the second node may be a gNB in the communication system shown in FIG. 1B
  • the first node may be a gNB in the communication system shown in FIG. 1C
  • the second node may be an eNB in the communication system shown in FIG. 1C.
  • the first node may receive data packets through the air interface, and the first node may send the data packets received by its own air interface to the second node. Due to air interface error codes, the data packets received by the first node may be out of order, so the data packets sent by the first node to the second node are themselves out of order.
  • the second node After the second node receives the data packet from the first node, it can reorder the received data packet, and transfer the data packet to the core network after the reordering.
  • the first node may be a gNB in the communication system shown in FIG. 1E
  • the second node may be an eNB in the communication system shown in FIG. 1E.
  • the first node may be the DU in the architecture shown in FIG. 1F
  • the second node may be the CU in the communication system shown in FIG. 1F.
  • the data packet described in the embodiment of this application is a PDCP data packet
  • the PDCP layer (PDCP entity) of the second node receives the data packet sent by the first node, and rewrites the received data packet.
  • the message format of the PDCP data packet may be the format shown in FIG. 4.
  • the PDCP data packet includes the Internet Protocol (IP) header, the User Datagram Protocol (UDP) header, and the General Packet Radio Service Tunnelling Protocol User (GTPU) header.
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • GTPU General Packet Radio Service Tunnelling Protocol User
  • PDCP header includes the "PDCP sequence number field", and the "PDCP sequence number field" is used to fill the PDCP SN of the data packet.
  • the first node sends one or more data packets to the second node, and each data packet includes the PDCP SN of the data packet.
  • each data packet includes the PDCP SN of the data packet.
  • the first node sends a data packet with PDCP SN of 1 to the second node, and the data packet includes PDCP SN "1".
  • the "PDCP sequence number field" of the data packet with PDCP SN of 1 is filled with " 1".
  • the first node sends redundant information to the second node, where the redundant information includes the one or more PDCP SNs, and the one or more PDCP SNs and the one or more data packets are one One corresponding.
  • the redundant information here may be other names, such as the first information, which is not limited in the embodiment of the present application.
  • the first node in addition to sending one or more data packets to the second node, the first node also sends the PDCP SN of each of the one or more data packets to the second node, that is, the first node sends the second node to the second node.
  • the node sends one or more PDCP SN. It can be understood that the one or more PDCP SNs sent by the first node in step 302 and the one or more data packets sent by the first node in step 301 have a one-to-one correspondence.
  • the one or more PDCP SNs included in the redundant information may be recorded as N PDCP SNs, which correspond to the N data packets sent by the first node to the second node in S301.
  • the second node after the second node receives the redundant information, it can determine whether there is packet loss on the transmission path between the first node and the second node according to the redundant information. Skip (ignore) this packet when reordering.
  • the second node may compare the N PDCP SNs in the redundant information with the PDCP SN of the received M data packets. For any PDCP SN in the redundant information, the second node may determine whether to receive To the data packet corresponding to the PDCP SN.
  • the second node can determine whether there is a data packet corresponding to PDCP SN "1" in the received M data packets (that is, a data packet with PDCP SN "1"), if The M data packets received by the second node include a data packet with PDCP SN of "1", which means that the second node has received a data packet with PDCP SN of "1"; if the M data packets received by the second node If the data packet whose PDCP SN is "1" is not included, it means that the second node has not received the data packet whose PDCP SN is "1".
  • the second node determines that the data packet corresponding to the first PDCP SN in the redundant information is not received, and the second node performs PDCP reordering, skip the data packet corresponding to the first PDCP SN data pack.
  • the first PDCP SN is any one of the one or more PDCP SNs included in the redundant information.
  • the second node may compare one or more PDCP SNs corresponding to one or more received data packets with one or more PDCP SNs in the redundant information to determine whether there is a PDCP SN corresponding to the redundant information The data packet was not received.
  • the second node skips the data packet corresponding to the first PDCP SN, which may include but is not limited to the following two methods:
  • the first method is to stop the PDCP discard timer of the data packet corresponding to the first PDCP SN if the PDCP discard timer of the data packet corresponding to the first PDCP SN is started.
  • the second node receives the data packet from the first node, and can obtain the PDCP SN of each received data packet by parsing the data packet.
  • the obtained PDCP SN is continuous, that is, the received data packet is continuous.
  • the node delivers the received data packet to the core network.
  • the second node may determine that the received data packet is not continuous, for example, the missing PDCP SN is a data packet of the first PDCP SN.
  • the second node determines that the received data packet is not continuous, and starts a timer to wait for the unreceived data packet, that is, the PDCP SN is the data packet of the first PDCP SN.
  • the timer may be a PDCP discard timer, which is used to wait for a data packet that has not been received, and once the timer expires, it stops waiting for the data packet.
  • the embodiment of the present application does not limit the duration of the timer.
  • the second node When the second node receives redundant information, it obtains multiple PDCP SNs from the redundant information. The second node may also compare the PDCP SN in the redundant information with the parsed PDCP SN to determine whether the aforementioned unreceived data packet is lost. For example, the second node parses the redundant information to obtain the first PDCP SN, but does not receive the data packet in which the PDCP SN is the first PDCP SN, and it can be determined that the first node sends the data corresponding to the first PDCP SN to the second node Packet, but the second node does not receive the data packet corresponding to the first PDCP SN, the second node can determine that the data packet is a lost data packet.
  • the timer for waiting for the data packet is terminated and no longer waiting for the data packet.
  • the second node can stop the timer, no longer wait for the data packet whose PDCP SN is the first PDCP SN, continue to reorder the data packets, and ignore (skip) the data whose PDCP SN is the first PDCP SN during reordering Packets, reorder other received data packets, and deliver the reordered data packets to the core network, that is, send data packets with PDCP SN greater than the first PDCP SN to the core network.
  • the data packets received by the second node from the first node are: PDCP SN is "1", PDCP SN is "2", PDCP SN is "4", PDCP The data packet with SN of "5", the data packet with PDCP SN of "1” and the data packet with PDCP SN of "2" are directly delivered to the core network, and the data packet with PDCP SN of "4" is received.
  • the second node finds that the received data packets are not continuous, it starts the PDCP discard timer and waits for the data packet whose PDCP SN is "3".
  • the second node receives redundant information from the first node, and obtains 5 PDCP SNs from the redundant information, which are "1, 2, 3, 4, 5", and the second node determines the first node and the second node If there is a packet loss on the node's transmission path, and the data packet whose PDCP SN is "3" has been lost, the PDCP discard timer is immediately terminated and no longer waits for the data packet whose PDCP SN is "3".
  • the data packets whose PDCP SN is "4, 5" are reordered, and the data packets whose PDCP SN is "4, 5" after reordering are delivered to the core network.
  • the second node Since the data packet whose PDCP SN is "3" is lost on the transmission path between the first node and the second node, the second node does not need to spend too long waiting for the data packet, terminates the timing in time, and continues to deliver the data packet to the core network. Avoid wasting bandwidth resources and improve system performance.
  • the PDCP discard timer of the data packet corresponding to the first PDCP SN is not started, then the PDCP discard timer of the data packet corresponding to the first PDCP SN is abandoned.
  • the PDCP SN of each received data packet can be obtained by parsing the data packet.
  • the second node can determine that the received data packet is not continuous For example, if a data packet whose PDCP SN is the second PDCP SN is missing, the second node starts timer 1 and waits for a data packet whose PDCP SN is the second PDCP SN.
  • the second node When the second node receives the redundant information, since the redundant information includes the second PDCP SN, the second node can determine that the data packet corresponding to the second PDCP SN is a lost data packet. Subsequently, the second node continues to receive data packets from the first node, and again finds that the PDCP SN is not continuous, for example, the data packet corresponding to the first PDCP SN is missing. Assuming that the redundant information includes the first PDCP SN, the second node can determine that the data packet corresponding to the first PDCP SN is a lost data packet, and the second node does not start the timer to wait for the data packet corresponding to the first PDCP SN. It is also possible to wait for the data packet corresponding to the first PDCP SN within the effective duration of timer 1. It can avoid wasting a long time waiting for lost data packets, causing a waste of bandwidth resources.
  • the data packets received by the second node from the first node are: PDCP SN is "1", PDCP SN is "2", PDCP SN is "4", PDCP The data packet with SN of "5", the data packet with PDCP SN of "1” and the data packet with PDCP SN of "2" are directly delivered to the core network, and the data packet with PDCP SN of "4" is received.
  • the second node finds that the received data packets are not continuous, it starts the PDCP discard timer and waits for the data packet whose PDCP SN is "3".
  • the second node receives redundant information from the first node, and obtains 6 PDCP SNs from the redundant information, which are "1, 2, 3, 4, 5, 6", and the second node determines the first node and Packet loss occurs on the transmission path of the second node, and the data packet whose PDCP SN is "3" has been lost. Wait for the data packet whose PDCP SN is "3" within the valid duration of the above-mentioned PDCP discard timer.
  • the second node then receives the data packet with PDCP SN of "7" from the first node, the PDCP SN is not continuous, and the second node does not receive the data packet with PDCP SN of "6", but the redundant information includes PDCP SN "6" ", PDCP SN is "6" data packets are lost data packets.
  • the second node no longer starts a new timer to wait for a packet with PDCP SN of "6”, and can wait for a packet with PDCP SN of "6" within the valid duration of the timer waiting for a packet with PDCP SN of "3" . It is avoided that the second node spends a long time waiting for lost data packets and does not transmit data packets to the core network for a long time, which wastes bandwidth resources between the second node and the core network.
  • the first node may redundantly send the PDCP SN of the data packet to the second node through the same type of data packet.
  • one or more data packets sent by the first node to the second node are PDCP data packets, and the PDCP data packets carry service data.
  • the first node may also send the PDCP SN of the one or more data packets to the second node through other PDCP data packets.
  • the other PDCP data packet is different from the one or more data packets. It can be understood that after the first node sends one or more data packets to the second node, other PDCP data packets are used to carry redundant information.
  • the redundant information can be carried in a data packet that includes service data, and the data packet that includes service data is different from the one or more data packets, that is, the data packet that carries redundant information and the first node One or more data packets sent in step 301 are different.
  • redundant information may be filled in the extension header of the data packet.
  • the first node sends redundant information to the second node through different types of data packets.
  • a data packet carrying redundant information does not include service data, and the first node sends the redundant information in step 301
  • One or more data packets include business data, and the two are different types of data packets.
  • the first node may construct a data packet in a dedicated format (for example, the redundant information described in the embodiment of the present application) to send the PDCP SN of one or more data packets.
  • a dedicated format for example, the redundant information described in the embodiment of the present application
  • Fig. 5 is a possible format of a data packet carrying redundant information.
  • this data packet includes an IP header, a UDP header, a GTPU header, and redundant information in order from outside to inside.
  • the redundant information includes the first PDCP SN field, the second PDCP SN field...the Nth PDCP SN field.
  • the first PDCP SN field, the second PDCP SN field...the Nth PDCP SN field has a one-to-one correspondence with one or more data packets sent by the first node, and is used to fill the PDCP SN of the corresponding data packet.
  • the first PDCP SN field, the second PDCP SN field...the Nth PDCP SN field is included in the PDCP header of the data packet.
  • the first PDCP SN field is used to fill the PDCP SN of the first data packet in the one or more data packets. Assuming that the PDCP SN of the first data packet is 3, the first PDCP SN field can be filled with "11".
  • the first node may carry the identification sequence number of the data packet when sending the data packet, and the redundant information may also carry the identification sequence number of the data packet, which will be further described below.
  • the data packet sent by the first node in step 301 further includes the identification sequence number of the data packet.
  • the identification sequence number is used to identify the data packet, and can be any sequence number used to identify the data packet that is different from the PDCP SN.
  • the first node is numbered in the order in which packets are sent to the second node, and the identification sequence number of each data packet is determined.
  • the second node can confirm the transmission path of the first node and the second node according to the continuity of the identification sequence number Whether there is packet loss on the network.
  • the first node sends one or more data packets to the second node through the X2 interface, and the identification sequence number determined by the first node according to the packet data may be referred to as the X2 sequence number.
  • Each data packet sent by the first node may also include the X2 sequence number of the data packet.
  • the X2 sequence number is used to identify the data packet sent by the first node through the X2 interface.
  • the second node can sort the data packets received from the first node according to the X2 sequence number, and judge whether there is packet loss based on the continuity of the X2 sequence number.
  • the identification sequence number of the data packet may be filled in the extension header of the data packet.
  • the first node may fill in the identification sequence number of the data packet in the extension header when forming the packet.
  • the redundant information sent by the first node to the second node further includes one or more identification sequence numbers, and the one or more identification sequence numbers have a one-to-one correspondence with the one or more PDCP SNs. It should be noted that an identification sequence number and its corresponding PDCP SN are used to identify the same data packet.
  • Figure 6 is a possible format of redundant information.
  • Fig. 6 is a possible format of a data packet carrying redundant information.
  • this data packet includes an IP header, a UDP header, a GTPU header, and redundant information in order from the inside to the outside.
  • the redundant information may include the identification sequence number range and the first field, the second field... the Nth field.
  • the identification sequence number range is used to indicate the range of identification sequence numbers of multiple data packets corresponding to PDCP SN in the redundant information.
  • the identification sequence number range is "1-10", which means that the redundant information includes the PDCP SN of the 10 data packets with identification sequence numbers 1, 2, 3...10.
  • the first field, the second field...the Nth field has a one-to-one correspondence with one or more data packets sent by the first node, and is used to fill the PDCP SN and identification sequence numbers of the data packets corresponding to them.
  • the first field is used to fill the PDCP SN "110" of the first data packet and the identification sequence number "1" of the first data packet.
  • the data packet sent by the first node carries the identification sequence number of the data packet
  • the redundant information sent by the first node carries the identification sequence number of the data packet and the PDCP SN of the data packet.
  • the first node sends one or more data packets to the second node, and may also send redundant information to the second node.
  • the redundant information includes one or more PDCP SNs corresponding to the one or more data packets.
  • one or more identification serial numbers corresponding to one or more data packets Since the one or more data packets are continuously sent by the first node, the identification sequence numbers are determined according to the sequence of sending the data packets, and the identification sequence numbers of the multiple data packets sent by the first node are also continuous. It is understandable that multiple identification serial numbers in the redundant information are also continuous.
  • the second node After receiving the data packet, the second node can parse the identification sequence number of the data packet from the data packet, and can judge whether the received data packet is continuous according to the continuity of the identification sequence number. In addition, the redundant information can be combined to determine the PDCP SN of the unreceived data packet.
  • the second node receives a data packet, and after parsing the data packet, it is found that the data packet corresponding to the first identification sequence number is not received, and the PDCP SN corresponding to the first identification sequence number in the redundant information is the first PDCP SN, it is determined that the data packet corresponding to the first PDCP SN is not received.
  • the second node receives the data packet with the identification sequence number "1, 3, 4, 5", that is, does not receive the data packet with the identification sequence number "2”, and analyzes the redundant information to determine that it corresponds to the identification number "2"
  • the PDCP SN is "110", that is, the second node does not receive the data packet whose PDCP SN is "110".
  • the first node periodically sends redundant information, and the sending period of the redundant information is less than the duration of the PDCP discard timer.
  • the PDCP discard timer is a timer started when the first node finds that the received data packets are out of sequence (or missing), and the first node waits for unreceived data packets within the effective duration of the PDCP discard timer.
  • the second node may receive the redundancy information before the PDCP discard timer expires, and may also determine the first node and the second node based on the redundancy information. There is a packet loss on the transmission path of the node, and the PDCP discard timer waiting for the data packet is terminated, so that the second node can continue to deliver the data packet to the core network, avoiding waiting for the lost data packet for a long time, and leaving the bandwidth empty for a long time. Make reasonable use of bandwidth resources to improve communication performance.
  • the redundancy information includes the one or more PDCP SNs corresponding to the one or more data packets sent by the first node in a one-to-one correspondence after the last time the redundancy information is sent.
  • the redundant information sent by the first node each time is for the PDCP SN of the data packet sent by the first node to the second node after the last time the redundant information was sent to the second node.
  • the first node sends data packet 1 to data packet 4 to the second node, it sends redundant information to the second node indicating the PDCP SN of each data packet in data packet 1 to data packet 4.
  • the first node sends data packets 5 to 8 to the second node, and then sends redundant information indicating the PDCP SN of each of the data packets 5 to 8 to the second node.
  • the redundant information further includes the redundant information sent last time. For example, after the first node sends data packet 1 to data packet 4 to the second node, it sends redundant information to the second node indicating the PDCP SN of each data packet in data packet 1 to data packet 4. Subsequently, the first node sends data packet 5 to data packet 8 to the second node, and then sends redundant information to the second node indicating the PDCP SN of each data packet in data packet 1 to data packet 4, and data packet 5 to PDCP SN of each data packet in data packet 8.
  • the second node is a node that aggregates data packets and performs data packet reordering, and the second node maintains the duration information of the PDCP discard timer.
  • the second node may also send the duration information of the PDCP discard timer to the first node.
  • the first node receives the duration information of the PDCP discard timer from the second node, and may determine the PDCP discard timer according to the duration information of the PDCP discard timer.
  • the duration of the redundant information is set to be shorter than the duration of the PDCP discard timer.
  • the time when the first node sends the redundant information and the time when the first node completes the sending of the one or more data packets differ by a first threshold. That is, after the first node completes the sending of the one or more data packets, it sends redundant information to the second node at a certain interval, indicating the PDCP SN of the one or more data packets.
  • the second node receives the redundant information associated with the data packet first, and then receives the data packet, which may cause the second node to mistakenly think that the data packet is lost and skip it during reordering.
  • the packet The first node sends a data packet and redundant information for a certain period of time. Try to ensure that the second node receives a data packet before receiving the redundant information associated with the data packet. This can prevent the second node from mistakenly thinking that the data packet is lost. Wrong reordering operation.
  • the first node after the first node finishes sending the one or more data packets, it first sends N data packets including service data, and then sends the redundant information to the second node.
  • the second node receives the redundant information associated with the data packet first, and then receives the data packet, which may cause the second node to mistakenly think that the data packet is lost and skip it during reordering.
  • the packet The first node sends data packets and redundant information at intervals of several data packets. Try to ensure that the second node receives a data packet before receiving the redundant information associated with the data packet, which can prevent the second node from mistakenly thinking that the data packet is lost , To avoid wrong reordering operations.
  • the first node may repeatedly send the redundant information.
  • the first node may repeatedly send the redundant information until confirmation information is received from the second node, where the confirmation information is used to confirm receipt of the redundant information. That is, the first node can repeatedly send redundant information, and if it receives the confirmation information fed back by the second node, it stops sending the redundant information.
  • the data packets sent by the first node to the second node may be out of order, and the second node may sort the data packets received from the first node; or, the first node may use the first data wireless
  • the PDCP SN that bears the data packets sent to the second node is not continuous.
  • the second node can also receive data packets from other bearers (for example, the second bearer), and the second node can receive data packets through the first data radio bearer and the second bearer. The received data packets are mixed and sorted.
  • the one or more data packets sent by the first node are data packets carried by the first data radio.
  • the RLC layer of the first data radio bearer is in the first node
  • the PDCP layer of the first data radio bearer is in the second node. That is, the RLC layer of the first node groups and sends data packets, and the PDCP layer of the second node receives data packets from the RLC layer of the first node, and reorders the data packets when the data packets are not continuous.
  • the first data radio bearer is a secondary cell group (SCG) terminated by a master node (master node, MN), or a split (Split) bearer terminated by an MN, or a secondary node ( Secondary node, SN) terminated master cell group (master cell group, MCG) bearer, or SN terminated offload bearer.
  • SCG secondary cell group
  • MN master node
  • split split
  • the processor 2101 in the device (first node) shown in FIG. 2A calls the code in the memory 2102 to execute the method shown in FIG. 3.
  • the processor 2213 of the DU shown in FIG. 2B calls the code in the memory 2214 to execute the method shown in FIG. 3.
  • FIG. 3 The solution introduced in FIG. 3 will be further explained in conjunction with FIG. 7 to FIG. 9.
  • the content of FIG. 7 to FIG. 9 and the content of FIG. 3 can be mutually cited and referenced.
  • NSA DC Option3x networking is taken as an example.
  • the eNB sends data packets to the gNB, the data packets are consecutively numbered (hereinafter referred to as the X2 sequence number, which is the identification sequence number described in the embodiment of this application) , And indicate the correspondence between the X2 sequence number of the data packet and the PDCP SN through redundant information.
  • the gNB can judge whether the packet is lost according to the continuity of the number, and find the PDCP sequence number of the lost packet according to the status report, and find the corresponding sequence number in the PDCP reordering queue to avoid reordering.
  • the method provided by the embodiment of the present application includes the following steps:
  • the gNB receives from the NR air interface and receives all data packets except PDCP SN110, 120, 130 to 190, 200 before PDCP SN 200.
  • the UE sends the 10 data packets PDCP SN110, PDCP SN120, PDCP SN130...PDCP SN200 to the eNB through the LTE air interface, and the eNB receives these data packets through the LTE air interface.
  • PDCP SN XX represents a data packet whose PDCP SN is "XX”.
  • the eNB receives the PDCP SN 110, adds the X2 sequence number 1 to the PDCP SN 110, and sends the processed data packet to the gNB.
  • the gNB receives the PDCP SN 110, and transfers the data packets before the PDCP SN 110 and the PDCP SN 110 buffered by the gNB to the core network.
  • the eNB receives the PDCP SN 120, adds the X2 sequence number 2 to the PDCP SN 120, and sends the processed data packet to the gNB.
  • the gNB receives the PDCP SN 120, and the gNB transfers the buffered data packets before the PDCP SN 120 and the PDCP SN 120 to the core network.
  • the eNB receives the PDCP SN 130, adds the X2 sequence number 3 to the PDCP SN 130, and sends the processed data packet to the gNB.
  • PDCP SN 130 lost packets on the X2 interface and failed to reach the gNB.
  • the eNB continues to add the X2 sequence number to the sent data packet, and sends the processed data packet to the gNB until 10 data packets are sent.
  • the gNB After receiving the data packet, the gNB finds that the PDCP SN 130 is missing, starts a timer to wait for the PDCP SN 130, and stops delivering the data packet to the core network.
  • the eNB sends redundant information to the gNB after sending the 10 data packets of PDCP SN110 to PDCP SN200.
  • the redundant information includes the X2 serial numbers 1-10 of the 10 data packets PDCP SN110-PDCP SN200, and the 10 PDCP SNs corresponding to the X2 serial numbers 1-10, that is, 110-200.
  • the eNB can parse the data packet, obtain the PDCP SN of the data packet from the data packet, and add the PDCP SN of the data packet to the redundant information.
  • the eNB may also copy the 3 bytes of the header of the data packet and fill in the corresponding position in the redundant information.
  • the PDCP protocol 3GPP 36.323 and 3GPP 38.323
  • the PDCP SN exists within 3 bytes of the header of the PDCP data packet.
  • the embodiments of the present application do not limit this, and are suitable for the adjustment of the PDCP protocol, and the number of bytes copied can be adjusted accordingly.
  • the PDCP protocol stipulates that the PDCP SN exists in the first 4 bytes of the PDCP data packet, and the first 4 bytes of the PDCP data packet are copied and filled to the corresponding position of the redundant information.
  • redundant information can be periodically sent according to the number of data packets.
  • the eNB sends one redundant information every time 10 data packets are sent, carrying the PDCP SN and X2 sequence numbers of the 10 data packets.
  • send redundant information periodically at intervals for example, send one redundant information every 10ms.
  • the first node can set different sending periods according to factors such as the packet loss probability and transmission delay of the network.
  • the sending cycle can be N data packets or a time interval.
  • the gNB stops waiting for the PDCP SN130 timer, and reorders the buffered data packets other than PDCP SN130, and reorders the data packets after the reordering.
  • the data packet is passed to the core network.
  • the PDCP SN "130" indicates that the eNB sent the PDCP SN 130 data packet to the gNB on the X2 interface, but packet loss occurred between the eNB and the gNB, and the gNB did not receive it. To the data packet of PDCP SN 130.
  • the eNB sends redundant information to the gNB every multiple data packets.
  • the number of data packets included in the sending period of the redundant information can be greater than the number of PDCP SNs of the redundant information. Redundant information is sent later.
  • the redundancy information includes the PDCP SN of 6 data packets, and the eNB sends the redundancy information to the gNB after completing the transmission of the 8 data packets.
  • the gNB maintains a queue for packet loss monitoring.
  • the X2 sequence number of the data packet is used to identify the data packet in the queue, and the queue pointer points to the X2 sequence number of the data packet to be processed.
  • the eNB sends data packets with X2 sequence numbers 1-8 to the gNB, and the gNB receives these 8 data packets, and the queue pointer slides to 9.
  • the eNB sends redundant information 1 to the gNB, including the PDCP SN of the data packets with X2 sequence numbers 1 to 6, which are 110, 120, 130...160, respectively.
  • the gNB determines that there is no packet loss based on the redundant information 1.
  • the eNB sends the X2 serial number 9-16 data packet to the gNB, the X2 serial number 10 data packet is lost at the X2 port, the gNB does not receive the X2 serial number 10 data packet, and the queue pointer stops at 10. .
  • the eNB sends redundant information 2 to the gNB, including the PDCP SN of the data packet with X2 sequence numbers 7-12, which are 170, 180, 190...230, respectively.
  • the gNB analyzes the redundant information 2 and obtains that the PDCP SN corresponding to the data packet with the X2 sequence number of 10 is 1000.
  • the PDCP discard timer is currently enabled and the timer is triggered by a packet whose PDCP SN is 1000, that is, the timer is to wait for a packet whose PDCP SN number is 1000, and the gNB stops the timer and sets the PDCP SN Continuous data packets after 1000 are delivered to the core network; if the timer is not triggered by a data packet with PDCP SN 1000, a new timer is not started and waits for a data packet with PDCP SN 1000.
  • the eNB sends the redundant information 1 immediately after the data packet with the X2 sequence number of 6, assuming that the data packet with the X2 sequence number of 6 arrives at the gNB later than the redundant information 1 due to out-of-order transmission, it will cause An erroneous packet skipping action, that is, after the gNB parses the redundant information 1, it mistakenly believes that the data packet of X2 sequence number 6 is lost on the X2 port, and the data packet of X2 sequence number 6 is skipped during reordering, resulting in the upper layer protocol For example, mistakenly believe that the data packet with X2 sequence number 6 is lost, and retransmit the service layer.
  • the eNB When the eNB finishes sending the data packet with the X2 sequence number 8 and then sends the redundant information 1, assuming that the data packet with the X2 sequence number 6 is out of sequence, it will arrive at the gNB after the data packet with the X2 sequence number 7. Before the redundant information 1 reaches the gNB, it will not cause the wrong packet skipping action.
  • the degree of delay in sending redundant information can be set according to the disorder of the actual networking (for example, the delay of the X2 transmission link causes the X2 sequence number of the data packet received by the gNB to be out of order) If the disorder is more serious, you can set the number of delayed data packets to be larger, and delay a few more packets before sending redundant information; if the disorder is very low, you can set the number of delayed packets If it is confirmed that there will be no disorder on the network, it is not necessary to postpone the status report, that is, the number of data packets included in the sending cycle of the redundant information can be equal to the redundancy The number of PDCP SN of the information.
  • the method provided by the embodiment of the present application can avoid the waste of bandwidth caused by the lost data packet waiting for a long time, which is beneficial to the characteristic communication performance. At the same time, it can solve the problem of misoperation caused by the disorder of the X2 port, and improve the fault tolerance of the system by optimizing the way of sending redundant information.
  • the eNB can also solve the impact of redundant information packet loss on the X2 port in the following two ways, including:
  • the eNB when the eNB sends the jth redundant information, it repeatedly sends the j-1th redundant information.
  • the eNB After the eNB sends a data packet with the X2 sequence number 1-10 to the gNB at the X2 port, it sends the redundancy information 1 to the gNB, including 10 PDCP SNs corresponding to the data packet with the X2 sequence number 1-10.
  • the eNB sends X2 data packets with serial numbers 11-20 to gNB at port X2, and sends redundant information 1 and redundant information 2.
  • redundant information 2 includes 10 data packets corresponding to X2 serial numbers 11-20 PDCP SN.
  • the eNB sends a data packet with X2 serial number 21-30 to gNB at the X2 port, and sends redundant information 2 and redundant information 3.
  • redundant information 3 includes 10 data packets corresponding to X2 serial number 21-30 PDCP SN.
  • the eNB repeatedly sends redundant information until it receives the confirmation information from the gNB.
  • the eNB After the eNB sends a data packet with the X2 sequence number 1-10 to the gNB at the X2 port, it repeatedly sends the redundant information 1 to the gNB, including 10 PDCP SNs corresponding to the data packet with the X2 sequence number 1-10.
  • the eNB receives the confirmation message sent by the gNB.
  • the confirmation message is used to confirm that the gNB has received the redundancy message 1, and the eNB stops sending the redundancy message 1.
  • the eNB may decide to select the first or second method to send redundant information according to the transmission quality of the X2 port. If the transmission quality is poor and the packet loss rate of the X2 port is not high, the first method can be used to send redundant information; if the transmission quality is poor and the packet loss rate of the X2 port is higher, the second method can be used to send the redundancy information.
  • the method provided by the embodiment of the present application can avoid the waste of bandwidth caused by the lost data packet waiting for a long time, which is beneficial to the characteristic communication performance. At the same time, it can solve the problems caused by packet loss on the X2 port, and improve the fault tolerance of the system by optimizing the way of sending redundant information.
  • the eNB numbers the data packets according to the transmission order of the X2 port, and does not need to send redundant information separately, but carries the redundant information in other data packets and sends it to the gNB.
  • the eNB sends a data packet, it is accompanied by the PDCP SN of one or more data packets previously sent.
  • one or more PDCP SNs attached to the path can be filled in the extension header of the message.
  • the number of PDCP SN carried depends on the transmission quality. When the transmission quality is good, the probability of continuous packet loss is small, and the number of PDCP SNs carried is less; when the transmission quality is poor, the probability of continuous packet loss is greater, and the number of PDCP SNs carried is larger.
  • the first data packet sent by the eNB does not carry the PDCP SN of other data packets, and the gNB receives After reaching the data packet with PDCP SN of 1, it is found that the data packet with PDCP SN of 1 does not carry PDCP SN of other data packets. For example, if the extension header of the data packet is empty, it will be processed according to the existing process, and the continuous data packet Pass it to the core network.
  • the gNB receives the second data packet, that is, the data packet with PDCP SN 5 in the figure, analyzes the data packet, obtains PDCP SN "1" in its extension header, confirms that it has received the data packet with PDCP SN 1, and continues According to the existing process, the continuous data packets are delivered to the core network.
  • the gNB receives the third data packet, that is, the data packet with PDCP SN 8 in the figure, analyzes the data packet, obtains PDCP SN "3" in its extension header, confirms that it has not received the data packet with PDCP SN 3, and starts The timer waits for the data packet whose PDCP SN is 3, and suspends the delivery of the data packet to the core network.
  • the gNB receives the fourth message, that is, the data packet whose PDCP SN is 3 in the figure, and detects that the timer waiting for the data packet whose PDCP SN is 3 is running, and then terminates the timer. In addition, parse the data packet with PDCP SN of 3, obtain PDCP SN "5" in its extension header, and confirm that the data packet with PDCP SN of 5 has been received.
  • PDCP receives the fifth message: the data packet with PDCP SN 12 in the figure, parses the data packet, obtains PDCP SN "9" in its extension header, confirms that no data packet with PDCP SN 9 is received, and starts The timer waits for the data packet whose PDCP SN is 9 and suspends the delivery of the data packet to the core network. After waiting for the timer of the data packet whose PDCP SN is 9 to expire, construct a virtual packet to reorder, and deliver the reordered data packet to the core network.
  • the method provided by the embodiment of the present application can avoid the waste of bandwidth caused by the lost data packet waiting for a long time, which is beneficial to the characteristic communication performance. At the same time, the transmission resources of the X2 port can be reduced. With less cost, the problem of PDCP reordering caused by X2 port disorder and packet loss is solved, which leads to bandwidth waste.
  • FIG. 10 shows a possible structural schematic diagram of the communication device involved in the foregoing embodiment.
  • the communication device shown in FIG. 10 may be the first node or the second node described in the embodiment of the present application, or may be a component in the first node or the second node that implements the foregoing method, or may be applied to the first node or the second node.
  • the chip may be a System-On-a-Chip (SOC) or a baseband chip with communication function.
  • the communication device includes a processing unit 1101 and a communication unit 1102.
  • the processing unit may be one or more processors, and the communication unit may be a transceiver.
  • the processing unit 1101 is used to support the first node or the second node to perform internal processing, for example, assembling data packets; the processing unit 1101 is also used to support the second node (for example, gNB) to perform step 808, and/or used in this article Other processes of the described technology.
  • the second node for example, gNB
  • the communication unit 1102 is used to support communication between the communication device and other communication devices, for example, support the first node and the second node to perform steps 301 and 302, and support the first node to perform steps 802, 804, and 806. Step 807 and step 809, and/or other processes used in the techniques described herein.
  • the communication device includes: a processing module 1201 and a communication module 1202.
  • the processing module 1201 is used to control and manage the actions of the communication device, for example, to perform the steps performed by the above-mentioned processing unit 1101, and/or to perform other processes of the technology described herein.
  • the communication module 1202 is configured to perform the steps performed by the above-mentioned communication unit 1102, and supports interaction between the communication device and other devices, such as interaction with other terminal devices.
  • the communication device may further include a storage module 1203, and the storage module 1203 is used to store the program code and data of the communication device.
  • the processing module 1201 is a processor
  • the communication module 1202 is a transceiver
  • the storage module 1203 is a memory
  • the communication device is the communication device shown in FIG. 2A.
  • the embodiment of the present application provides a computer-readable storage medium, and the computer-readable storage medium stores instructions; the instructions are used to execute the method shown in FIG. 3.
  • the embodiment of the present application provides a computer program product including instructions, which when running on a communication device, causes the communication device to execute the method shown in FIG. 3.
  • a wireless communication device in an embodiment of the present application includes: instructions stored in the wireless communication device; when the wireless communication device runs on the communication device shown in FIG. 2A, FIG. 2B, FIG. 10, and FIG. The method shown in Figure 3.
  • the wireless communication device may be a chip.
  • An embodiment of the present application also provides a communication system, including: a first node and a second node.
  • the first node may be the communication device shown in FIG. 2A, FIG. 10, and FIG. 11 or the DU shown in FIG. 2B
  • the second node may be the communication device shown in FIG. 2A, FIG. 10, and FIG. It is the CU shown in Figure 2B.
  • the processor in the embodiment of the present application may include, but is not limited to, at least one of the following: central processing unit (CPU), microprocessor, digital signal processor (DSP), microcontroller (microcontroller unit, MCU) ), or various computing devices running software such as artificial intelligence processors.
  • Each computing device may include one or more cores for executing software instructions for calculation or processing.
  • the processor can be a single semiconductor chip, or it can be integrated with other circuits to form a semiconductor chip. For example, it can form an SoC (on-chip) with other circuits (such as codec circuits, hardware acceleration circuits, or various bus and interface circuits).
  • the processor can also include necessary hardware accelerators, such as field programmable gate array (FPGA) and PLD (programmable logic device) , Or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD programmable logic device
  • the memory in the embodiment of the present application may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory) , RAM) or other types of dynamic storage devices that can store information and instructions, and may also be Electrically Erasable Programmable-only Memory (EEPROM).
  • ROM read-only memory
  • RAM random access memory
  • EEPROM Electrically Erasable Programmable-only Memory
  • the memory can also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.) , A magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • CD-ROM compact disc read-only memory
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • a magnetic disk storage medium or other magnetic storage device or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • At least one refers to one or more.
  • Multiple means two or more.
  • And/or describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, both A and B exist, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are in an “or” relationship.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or plural items (a).
  • At least one item (a) of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • words such as “first” and “second” are used to distinguish the same items or similar items with substantially the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and order of execution, and words such as “first” and “second” do not limit the difference.
  • the disclosed database access device and method can be implemented in other ways.
  • the embodiments of the database access device described above are only illustrative.
  • the division of the modules or units is only a logical function division.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections through some interfaces, database access devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate parts may or may not be physically separate.
  • the parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of software products, which are stored in a storage medium It includes several instructions to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请实施例公开了一种冗余信息反馈方法及通信装置。包括：第一节点向第二节点发送一个或者多个数据包，每个数据包包括所述数据包的分组数据汇聚协议序列号PDCP SN；然后，第一节点向第二节点发送冗余信息，所述冗余信息包括所述一个或者多个数据包的PDCP SN，第二节点根据冗余信息可以确定第一节点与第二节点的传输路径上是否存在数据包丢失。

Description

一种冗余信息反馈方法及通信装置
本申请要求于2019年6月5日提交国家知识产权局、申请号为201910488397.6、申请名称为“一种冗余信息反馈方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉通信领域，尤其涉及一种冗余信息反馈方法及通信装置。
背景技术
第五代(5 th generation，5G)非独立(non standalone，NSA)组网中，上行动态分流是常见的用户面数据传输模式。这种模式下，用户设备(user equipment，UE)的上行数据可以分流通过4G空口到达演进基站(evolution node basestation，eNB)，通过5G空口到达下一代基站(next generation node B，gNB)。数据最终在锚点基站(gNB或eNB)汇合，由锚点进行对接收到的数据进行重排序，并将数据传递给核心网。
当锚点基站收到不连续的数据包时，会启动一个定时器。在定时器超时之前，如果数据包被补齐，锚点基站则继续向核心网传递数据包；否则锚点基站需要等定时器超时，才会继续传递数据包。
如果定时器设置的太小，则可能将延迟较大未接收到的数据包当作丢包，引起应用层的异常处理，造成上层应用的体验较差。因此，一般会设置比较大的定时器，在定时器运行期间锚点基站停止传数据包，这段时间内锚点基站与核心网之间的带宽处于空闲状态，带宽浪费严重。
发明内容
本申请实施例提供一种冗余信息反馈方法及通信装置，可以准确地确定数据包丢失在空口上还是节点之间的传输路径上，对两种不同的丢失数据包采取不同的处理，从而及时终止等待丢包定时器或不开启等待丢包的定时器，避免长时间等待丢包，减少带宽浪费，节约成本，提升通信效益。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，公开了一种冗余信息反馈方法，该方法可以由第一通信装置(第一节点或者第一节点中的芯片执行)，下面以第一节点为例进行介绍，需要说明的是，该方法的执行主体可以换成第一通信装置。包括：第一节点向第二节点发送一个或者多个(例如N个)数据包，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN；所述第一节点向所述第二节点发送冗余信息，所述冗余信息包括所述一个或者多个(例如N个)PDCP SN，所述一个或者多个(例如N个)PDCP SN和所述一个或者多个(例如N个)数据包是一一对应的。
通过在发送一个或者多个数据包后，再发送该一个或者多个数据包的PDCP SN，便于第二节点确定哪些数据包在节点之间的传输路径上丢失了，从而除了第一节点和第二节点之间的传输路径上丢失的数据包，第二节点在进行PDCP重排序时发现其他没有接收的包是在空口上丢失的，进而第二节点可以对这两种不同的丢失数据包进行不同的处理。
本申请实施例提供的方法中，第二节点的PDCP实体发现从第一节点接收到的数据包不连续时，启动定时器等待数据包。同时，第二节点可以根据来自第一节点的冗余信息确定在第一节点向第二节点发送多个数据包时，是否出现丢包。第二节点一旦判断第一节点和第二节点传输路径上出现丢包，则在重排序数据包时跳过该数据包，例如，假设已开启了等待该数据包的定时器，则终止等待该数据包的定时器，第二节点可以继续向核心网投递数据包；或者，还未开始等待该数据包的定时器，则不开启等待数据包的定时器，在当前已运行的定时器(等待其他数据包)超时之后，第二节点可以继续向核心网投递数据包。可见，本申请实施例提供的方法可以避免长时间等待丢失的数据包造成带宽的浪费，并且能够减少第二节点向核心网网元发送数据的时延，有利于提升通信性能。
结合第一方面，在第一方面的第一种可能的实现方式中，所述一个或者多个(例如N个)数据包中的每个数据包还包括所述数据包的标识序号；冗余信息还包括所述一个或者多个(例如N个)标识序号，所述一个或者多个(例如N个)标识序号与所述一个或者多个(例如N个)PDCP SN是一一对应的。
本申请实施例中，第二节点接收多个数据包之后，解析数据包获取其中的标识序号，进一步可以根据标识序号确定接收到的数据包的是否连续，或者，可以确定第一节点和第二节点的传输路径上是否丢包。另外，第二节点还可以根据冗余信息确定丢包的PDCP SN。
结合第一方面的第一种可能的实现方式中，在第一方面的第二种可能的实现方式中，所述多个标识序号是连续的。
本申请实施例中，第一节点向第二节点发送多个标识序号连续的数据包，第二节点从第一节点接收数据包之后，可以根据数据包的连续性来判断是否丢包。例如，第二节点从第一节点接收到的数据包是连续的，表明第一节点和第二节点之间的传输路径上没有丢包；第二节点从第一节点接收到的数据包不连续，表明第一节点和第二节点之间的传输路径上有丢包。
结合第一方面的第一或第二种可能的实现方式中，在第一方面的第三种可能的实现方式中，按照所述一个或者多个数据包的发送顺序，与所述一个或者多个数据包一一对应的所述一个或者多个标识序号是连续的。
本申请实施例中，第一节点可以根据发包顺序确定数据包的标识序号，在第一节点连续发包时，第一节点发送的多个数据包的标识序号也是连续的。相应的，第二节点可以根据接收到的数据包是否连续，判断是否丢包。
结合第一方面或第一方面的第一至第三种可能的实现方式中的任意一种，在第一方面的第四种可能的实现方式中，所述冗余信息是周期性发送的。
本申请实施例中，第一节点在发送一个或多个数据包之后会发送一个冗余信息，至少指示本次发送的数据包的PDCP SN，使得第二节点可以根据冗余信息判断是否有丢包，终止等待丢包的定时器，或者不开启等待丢包的定时器，避免由此导致的第二节点长时间占用带宽但不进行数据包传递，浪费带宽资源。
结合第一方面的第五种可能的实现方式，在第一方面的第六种可能的实现方式中，所述冗余信息的发送周期小于PDCP丢弃定时器的时长。
本申请实施例中，冗余信息的发送周期小于PDCP丢弃定时器的时长，第二节点可以在PDCP丢弃定时器超时之前接收到冗余信息，一旦发现触发PDCP丢弃定时器的数据包已丢失，则及时终止定时器，避免长时间浪费带宽资源。
结合第一方面的第五或第六种可能的实现方式，在第一方面的第七种可能的实现方式中，所述冗余信息包括上一次发送冗余信息后，所述第一节点发送的所述一个或者多个数据包一一对应的所述一个或者多个PDCP SN。
本申请实施例中，第一节点在发送一个或多个数据包之后，向第二节点发送冗余信息指示所述一个或多个数据包的PDCP SN，使得第二节点可以根据冗余信息判断第一节点发送的一个或多个数据包是否有丢失。一旦发现触发PDCP丢弃定时器的数据包已丢失，则及时终止定时器，避免长时间浪费带宽资源。
结合第一方面的第六种可能的实现方式，在第一方面的第七种可能的实现方式中，所述冗余信息还包括所述上一次发送的冗余信息。
本申请实施例中，第一节点还可以冗余发送冗余信息，提高冗余信息的可靠性。例如，第一节点在第i+1次发送的冗余信息中也可以包括第i次发送的冗余信息，在出现连续丢包时，第二节点仍可以根据冗余信息判断丢包。
结合第一方面的第五种可能的实现方式，在第一方面的第六种可能的实现方式中，所述方法还包括：所述第一节点从所述第二节点接收所述PDCP丢弃定时器的时长信息。
本申请实施例中，第二节点负责对汇聚数据，并对数据包进行重排序之后投递给核心网，因此第二节点维护有PDCP丢弃定时器的时长信息。第二节点可以将PDCP丢弃定时器的时长发送给第一节点，第一节点可以根据PDCP丢弃定时器的时长设置发送冗余信息的周期，使得第二节点在PDCP丢弃定时器超时之前接收到冗余信息。
结合第一方面或第一方面的第一至第三种可能的实现方式中的任意一种，在第一方面的第九种可能的实现方式中，所述第一节点发送所述冗余信息的时刻与所述第一节点完成所述一个或者多个数据包的发送的时刻之间相差第一阈值。
本申请实施例中，假设受网络延迟的影响，第二节点先接收数据包关联的冗余信息，再接收数据包，有可能导致第二节点误以为该数据包丢失，在重排序的时候跳过该数据包。第一节点发送数据包和冗余信息间隔一定时间，尽可能保证第二节点接收某个数据包之后才接收与该数据包关联的冗余信息，可以避免第二节点误以为数据包丢失，避免错误的重排序操作。
结合第一方面或第一方面的第一至第三种可能的实现方式中的任意一种，在第一方面的第十种可能的实现方式中，所述第一节点向所述第二节点发送冗余信息具体包括：
所述第一节点完成所述一个或者多个数据包的发送后，先发送一个或者多个其他数据包，再向所述第二节点发送所述冗余信息。
本申请实施例中，假设受网络延迟的影响，第二节点先接收数据包关联的冗余信息，再接收数据包，有可能导致第二节点误以为该数据包丢失，在重排序的时候跳过该数据包。第一节点发送数据包和冗余信息间隔N个数据包，尽可能保证第二节点接收某个数据包之后才接收与该数据包关联的冗余信息，可以避免第二节点误以为数据 包丢失，避免错误的重排序操作。
结合第一方面或第一方面的第一至第三种可能的实现方式中的任意一种，在第一方面的第十一种可能的实现方式中，所述第一节点向所述第二节点发送冗余信息具体包括：所述第一节点重复发送所述冗余信息，直至从所述第二节点接收确认信息，所述确认信息用于确认收到所述冗余信息。
本申请实施例中，可以通过重复传输提高冗余信息的可靠性。
结合第一方面，在第一方面的第十二种可能的实现方式中，所述冗余信息携带在业务数据包中，所述业务数据包与所述一个或者多个数据包不同。
本申请实施例中，可以将冗余信息携带在其他数据包(与第一节点发送的第一个或多个数据包的类型相同，包括业务数据)中发送给gNB。eNB在发送数据包时，随路附带之前发送的一个或多个数据包的PDCP SN。
结合第一方面，在第一方面的第十三种可能的实现方式中，所述冗余信息携带在除业务数据包以外的数据包中。
本申请实施例中，第一节点还可以构造专用的数据包来发送冗余信息，这种数据包可以不包括业务数据，仅用于携带冗余信息。
第二方面，公开了一种冗余信息反馈方法，该冗余信息反馈方法可以由第二通信装置(第二节点或者第二节点中的芯片执行)，下面以第二节点为例进行介绍，需要说明的是，该方法的执行主体可以换成第二通信装置。包括：第二节点从第一节点接收冗余信息，冗余信息包括一个或者多个(例如N个)分组数据汇聚协议序列号PDCP SN；所述一个或者多个(例如N个)PDCP SN与所述第一节点向所述第二节点发送的一个或者多个(例如N个)数据包一一对应，所述一个或者多个数据包(例如N个)中的每个数据包包括所述数据包的PDCP SN。
可以理解，N大于等于M，第一节点向第二节点发送N个数据包，第二节点可能接收到了该一个或者多个数据包中的部分或者全部，可能存在一些数据包第二节点没有接收到。
上述方法还可以包括：第二节点从第一节点接收M个数据包，所述M个数据包中的每个数据包包括所述数据包的分组数据汇聚协议PDCP序列号SN，M为大于等于1的整数。或者，第二节点可以没有从第一节点接收到数据包，可以理解，第一节点发送的N个数据包都丢失了，此时第二节点只接收到冗余信息，包括N个PDCP SN号，但不包括业务数据包。
结合第二方面，在第二方面的第一种可能的实现方式中，第一节点发送的所述一个或者多个(例如N个)数据包中的每个数据包还包括所述数据包的标识序号，第二节点接收的所述M个数据包中的每个数据包包括所述数据包的标识序号。所述冗余信息还包括所述一个或者多个(例如N个)标识序号，所述一个或者多个(例如N个)标识序号与所述一个或者多个(例如N个)PDCP SN是一一对应的。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述标识序号是连续的。
结合第二方面的第一或第二种可能的实现方式，在第二方面的第三种可能的实现方式中，按照所述一个或者多个(例如N个)数据包的发送顺序，与所述一个或者多 个(例如N个)数据包一一对应的所述一个或者多个(例如N个)标识序号是连续的。但是，由于第二节点只接收到M个数据包，M个数据包各自的标识序号可能是不连续的。
结合第二方面或第二方面的第一至第三种可能的实现方式中的任一种，在第二方面的第四种可能的实现方式中，所述冗余信息是周期性接收的。或者，第一节点发送冗余信息是周期性发送的，但是第二节点一些时候收到冗余信息，另一些时候没有收到冗余信息，第二节点接收冗余信息不是周期性的。
结合第二方面的第四种可能的实现方式，在第二方面的第五种可能的实现方式中，所述冗余信息的接收周期小于PDCP丢弃定时器的时长。或者，第二节点接收冗余信息不是周期性的，但相邻两次接收冗余信息之间的时间间隔小于PDCP丢弃定时器的时长。
结合第二方面的第四或第五种可能的实现方式，在第二方面的第六种可能的实现方式中，所述冗余信息包括上一次接收冗余信息后，从所述第一节点接收的所述一个或者多个(例如M个)数据包一一对应的所述一个或者多个(例如M个)PDCP SN。
结合第二方面的第六种可能的实现方式，在第二方面的第七种可能的实现方式中，所述冗余信息还包括所述上一次接收的冗余信息。
结合第二方面的第五种可能的实现方式，在第二方面的第八种可能的实现方式中，向所述第一节点发送所述PDCP丢弃定时器的时长信息。
结合第二方面或第二方面的第一至第八种可能的实现方式中的任意一种，在第二方面的第九种可能的实现方式中，所述方法还包括：当所述第二节点确定未接收到所述冗余信息中的第一PDCP SN对应的数据包，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包，所述第一PDCP SN为所述一个或者多个PDCP SN中的一个PDCP SN。
结合第二方面的第二种可能的实现方式，在第二方面的第十种可能的实现方式中，所述第一节点发送的N个数据包一一对应的N个标识序号是连续的，但由于第二节点只接收到M个数据包，M个数据包各自对应的M个标识序号是不连续的，所述方法还包括：当所述第二节点根据所述多个(例如M个)各自的标识序号的连续性确定未接收到第一标识序号，所述第一标识序号为所述多个(例如N个)标识序号中的一个标识序号，所述第一标识序号对应的PDCP SN为第一PDCP SN，则所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包。
结合第二方面的第十种可能的实现方式，在第二方面的第十一种可能的实现方式中，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包，包括：若所述第一PDCP SN对应的数据包的PDCP丢弃定时器已开启，则停止所述第一PDCP SN对应的数据包的PDCP丢弃定时器；或者，若所述第一PDCP SN对应的数据包的PDCP丢弃定时器未开启，则放弃开启所述第一PDCP SN对应的数据包的PDCP丢弃定时器。
结合第二方面的第十或第十一种可能的实现方式，在第二方面的第十二种可能的实现方式中，所述方法还包括：向核心网发送PDCP SN大于所述第一PDCP SN的数据包。
结合第二方面或第二方面的第一至第十二种可能的实现方式中的任意一种，在第二方面的第十三种可能的实现方式中，所述方法还包括：向所述第一节点发送确认信息，所述确认信息用于确认收到所述冗余信息。
结合第二方面或第一方面，在一种可能的实现方式中，所述一个或者多个数据包为第一数据无线承载的数据包，所述第一数据无线承载的无线链路控制RLC层在所述第一节点，所述第一数据无线承载的PDCP层在所述第二节点。
本申请实施例中，第一节点发往第二节点的数据包本身可能存在乱序，第二节点可以对从第一节点接收到的数据包进行排序；或，第一节点通过第一数据无线承载向第二节点发送的数据包的PDCP SN不连续，第二节点还可以从其它承载(例如，第二承载)接收数据包，第二节点可以将通过第一数据无线承载、第二承载收到的数据包进行混合并排序。
需要说明的是，通过第一数据无线承载可以实现MN与UE通信，也可以通过第一数据无线承载实现SN与UE通信。第一数据无线承载可以是数据无线承载，第一数据无线承载在网络侧对应的PDCP实体只有一个，但是第一数据无线承载在网络侧可能对应两个RLC承载，该两个RLC承载分别在MN和SN上(即分流承载)。
结合第二方面或第一方面，在一种可能的实现方式中，所述第一数据无线承载为主节点MN终结的辅小区组SCG承载，或，主节点MN终结的分流承载，或辅节点SN终结的主小区组MCG承载，或，SN终结的分流承载。
结合第二方面或第一方面，在一种可能的实现方式中，所述第一节点为分布单元DU，所述第二节点为集中CU。
第三方面，公开了一种通信装置，可以是第一节点或第一节点中的芯片。该通信装置可以包括与上述第一方面的方法中的步骤对应的单元，可以参考上述第一方面的方法。该通信装置包括：通信单元，用于向第二节点发送一个或者多个(例如，N个)数据包，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN；通信单元还用于，向所述第二节点发送冗余信息，所述冗余信息包括所述一个或者多个PDCP SN，所述一个或者多个PDCP SN和所述一个或者多个数据包是一一对应的。
结合第三方面，在第三方面的第一种可能的实现方式中，所述一个或者多个数据包中的每个数据包还包括所述数据包的标识序号；冗余信息还包括所述一个或者多个标识序号，所述一个或者多个标识序号与所述一个或者多个PDCP SN是一一对应的。
结合第三方面的第一种可能的实现方式中，在第三方面的第二种可能的实现方式中，所述多个标识序号是连续的。
结合第三方面的第一或第二种可能的实现方式中，在第三方面的第三种可能的实现方式中，按照所述一个或者多个数据包的发送顺序，与所述一个或者多个数据包一一对应的所述一个或者多个标识序号是连续的。
结合第三方面或第三方面的第一至第三种可能的实现方式中的任意一种，在第三方面的第四种可能的实现方式中，所述冗余信息是周期性发送的。
结合第三方面的第五种可能的实现方式，在第三方面的第六种可能的实现方式中，所述冗余信息的发送周期小于PDCP丢弃定时器的时长。
结合第三方面的第五或第六种可能的实现方式，在第三方面的第七种可能的实现 方式中，所述冗余信息包括上一次发送冗余信息后，所述第一节点发送的所述一个或者多个数据包一一对应的所述一个或者多个PDCP SN。
结合第三方面的第六种可能的实现方式，在第三方面的第七种可能的实现方式中，所述冗余信息还包括所述上一次发送的冗余信息。
结合第三方面的第五种可能的实现方式，在第三方面的第六种可能的实现方式中，通信单元还用于，从第二节点接收所述PDCP丢弃定时器的时长信息。
结合第三方面或第三方面的第一至第三种可能的实现方式中的任意一种，在第三方面的第九种可能的实现方式中，所述第一节点发送所述冗余信息的时刻与所述第一节点完成所述一个或者多个数据包的发送的时刻之间相差第一阈值。
结合第三方面或第三方面的第一至第三种可能的实现方式中的任意一种，在第三方面的第十种可能的实现方式中，通信单元具体用于，完成所述一个或者多个数据包的发送后，先发送N个其他数据包，再向所述第二节点发送所述冗余信息。
结合第三方面或第三方面的第一至第三种可能的实现方式中的任意一种，在第三方面的第十一种可能的实现方式中，通信单元，具体用于重复发送所述冗余信息，直至从所述第二节点接收确认信息，所述确认信息用于确认收到所述冗余信息。
结合第三方面，在第三方面的第十二种可能的实现方式中，所述冗余信息携带在业务数据包中，所述业务数据包与所述一个或者多个数据包不同。
结合第三方面，在第三方面的第十三种可能的实现方式中，所述冗余信息携带在除业务数据包以外的数据包中。
本申请实施例第三方面中，第一节点向第二节点发送的一个或多个数据包可以记为N个数据包，N为大于或等于1的整数。
第四方面，公开了一种通信装置，可以是第一节点或第一节点中的芯片。该通信装置可以包括与上述第二方面的方法中的步骤对应的单元，可以参考上述第二方面的方法。该通信装置包括：通信接口，用于向第二节点发送一个或者多个数据包，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN；通信接口还用于，向所述第二节点发送冗余信息，所述冗余信息包括所述一个或者多个PDCP SN，所述一个或者多个PDCP SN和所述一个或者多个数据包是一一对应的。
结合第四方面，在第四方面的第一种可能的实现方式中，所述一个或者多个数据包中的每个数据包还包括所述数据包的标识序号；冗余信息还包括所述一个或者多个标识序号，所述一个或者多个标识序号与所述一个或者多个PDCP SN是一一对应的。
结合第四方面的第一种可能的实现方式中，在第四方面的第二种可能的实现方式中，所述多个标识序号是连续的。
结合第四方面的第一或第二种可能的实现方式中，在第四方面的第三种可能的实现方式中，按照所述一个或者多个数据包的发送顺序，与所述一个或者多个数据包一一对应的所述一个或者多个标识序号是连续的。
结合第四方面或第四方面的第一至第三种可能的实现方式中的任意一种，在第四方面的第四种可能的实现方式中，所述冗余信息是周期性发送的。
结合第四方面的第五种可能的实现方式，在第四方面的第六种可能的实现方式中，所述冗余信息的发送周期小于PDCP丢弃定时器的时长。
结合第四方面的第五或第六种可能的实现方式，在第四方面的第七种可能的实现方式中，所述冗余信息包括上一次发送冗余信息后，所述第一节点发送的所述一个或者多个数据包一一对应的所述一个或者多个PDCP SN。
结合第四方面的第六种可能的实现方式，在第四方面的第七种可能的实现方式中，所述冗余信息还包括所述上一次发送的冗余信息。
结合第四方面的第五种可能的实现方式，在第四方面的第六种可能的实现方式中，通信接口还用于，从第二节点接收所述PDCP丢弃定时器的时长信息。
结合第四方面或第四方面的第一至第三种可能的实现方式中的任意一种，在第四方面的第九种可能的实现方式中，所述第一节点发送所述冗余信息的时刻与所述第一节点完成所述一个或者多个数据包的发送的时刻之间相差第一阈值。
结合第四方面或第四方面的第一至第三种可能的实现方式中的任意一种，在第四方面的第十种可能的实现方式中，通信接口具体用于，完成所述一个或者多个数据包的发送后，先发送一个或多个个其他数据包，再向所述第二节点发送所述冗余信息。
结合第四方面或第四方面的第一至第三种可能的实现方式中的任意一种，在第四方面的第十一种可能的实现方式中，通信接口，具体用于重复发送所述冗余信息，直至从所述第二节点接收确认信息，所述确认信息用于确认收到所述冗余信息。
结合第四方面，在第四方面的第十二种可能的实现方式中，所述冗余信息携带在业务数据包中，所述业务数据包与所述一个或者多个数据包不同。
结合第四方面，在第四方面的第十三种可能的实现方式中，所述冗余信息携带在除业务数据包以外的数据包中。
本申请实施例第四方面中，第一节点通过通信接口向第二节点发送的一个或或者多个数据包可以称为N个数据包，N为大于或等于1的整数。
第五方面，公开了一种通信装置，可以是第二节点或第二节点中的芯片。包括：通信单元，用于从第一节点接收冗余信息，冗余信息包括一个或者多个分组数据汇聚协议序列号PDCP SN；所述一个或者多个PDCP SN与所述第一节点向所述第二节点发送的一个或者多个数据包一一对应，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN。
需要说明的是，第一节点向第二节点发送N个数据包，第二节点可能接收到了该一个或者多个数据包中的部分或者全部，可能存在一些数据包第二节点没有接收到。
一种可能的实现方式中，通信单元从第一节点接收M个数据包，所述M个数据包中的每个数据包包括所述数据包的分组数据汇聚协议PDCP序列号SN，M为大于等于1的整数。或者，第二节点可以没有从第一节点接收到数据包，可以理解，第一节点发送的N个数据包都丢失了，此时第二节点只接收到冗余信息，包括N个PDCP SN号，但不包括业务数据包。
结合第五方面，在第五方面的第一种可能的实现方式中，所述一个或者多个数据包中的每个数据包还包括所述数据包的标识序号；所述冗余信息还包括所述一个或者多个标识序号，所述一个或者多个标识序号与所述一个或者多个PDCP SN是一一对应的。
结合第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中， 所述标识序号是连续的。
结合第五方面的第一或第二种可能的实现方式，在第五方面的第三种可能的实现方式中，按照所述一个或者多个数据包的发送顺序，与所述一个或者多个数据包一一对应的所述一个或者多个标识序号是连续的。
结合第五方面或第五方面的第一至第三种可能的实现方式中的任一种，在第五方面的第四种可能的实现方式中，所述冗余信息是周期性接收的。
结合第五方面的第四种可能的实现方式，在第五方面的第五种可能的实现方式中，所述冗余信息的接收周期小于PDCP丢弃定时器的时长。
结合第五方面的第四或第五种可能的实现方式，在第五方面的第六种可能的实现方式中，所述冗余信息包括上一次接收冗余信息后，从所述第一节点接收的所述一个或者多个数据包一一对应的所述一个或者多个PDCP SN。
结合第五方面的第六种可能的实现方式，在第五方面的第七种可能的实现方式中，所述冗余信息还包括所述上一次接收的冗余信息。
结合第五方面的第五种可能的实现方式，在第五方面的第八种可能的实现方式中，通信单元还用于，向所述第一节点发送所述PDCP丢弃定时器的时长信息。
结合第五方面或第五方面的第一至第八种可能的实现方式中的任意一种，在第五方面的第九种可能的实现方式中，还包括处理单元，处理单元用于，当所述第二节点确定未接收到所述冗余信息中的第一PDCP SN对应的数据包，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包，所述第一PDCP SN为所述一个或者多个PDCP SN中的一个PDCP SN。
结合第五方面的第二种可能的实现方式，在第五方面的第十种可能的实现方式中，所述多个标识序号是连续的，处理单元具体用于，当所述第二节点根据所述多个标识序号的连续性确定未接收到第一标识序号，所述第一标识序号为所述多个标识序号中的一个标识序号，所述第一标识序号对应的PDCP SN为第一PDCP SN，则所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包。
结合第五方面的第十种可能的实现方式，在第五方面的第十一种可能的实现方式中，所述第二节点进行PDCP重排序时，处理单元具体用于，若所述第一PDCP SN对应的数据包的PDCP丢弃定时器已开启，则停止所述第一PDCP SN对应的数据包的PDCP丢弃定时器；或者，若所述第一PDCP SN对应的数据包的PDCP丢弃定时器未开启，则放弃开启所述第一PDCP SN对应的数据包的PDCP丢弃定时器。
结合第五方面的第十或第十一种可能的实现方式，在第五方面的第十二种可能的实现方式中，通信单元还用于，向核心网发送PDCP SN大于所述第一PDCP SN的数据包。
结合第五方面或第五方面的第一至第十二种可能的实现方式中的任意一种，在第五方面的第十三种可能的实现方式中，通信单元还用于，向所述第一节点发送确认信息，所述确认信息用于确认收到所述冗余信息。
第六方面，公开了一种通信装置，可以是第二节点或第二节点中的芯片。包括：通信单元，用于从第一节点接收冗余信息，冗余信息包括一个或者多个分组数据汇聚协议序列号PDCP SN；所述一个或者多个PDCP SN与所述第一节点向所述第二节点 发送的一个或者多个数据包一一对应，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN。
需要说明的是，第一节点向第二节点发送N个数据包，第二节点可能接收到了该一个或者多个数据包中的部分或者全部，可能存在一些数据包第二节点没有接收到。
一种可能的实现方式中，通过通信接口从第一节点接收M个数据包，所述M个数据包中的每个数据包包括所述数据包的分组数据汇聚协议PDCP序列号SN，M为大于等于1的整数。或者，第二节点可以没有从第一节点接收到数据包，可以理解，第一节点发送的N个数据包都丢失了，此时第二节点只接收到冗余信息，包括N个PDCP SN号，但不包括业务数据包。
结合第六方面，在第六方面的第一种可能的实现方式中，所述一个或者多个数据包中的每个数据包还包括所述数据包的标识序号；所述冗余信息还包括所述一个或者多个标识序号，所述一个或者多个标识序号与所述一个或者多个PDCP SN是一一对应的。
结合第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，所述标识序号是连续的。
结合第六方面的第一或第二种可能的实现方式，在第六方面的第三种可能的实现方式中，按照所述一个或者多个数据包的发送顺序，与所述一个或者多个数据包一一对应的所述一个或者多个标识序号是连续的。
结合第六方面或第六方面的第一至第三种可能的实现方式中的任一种，在第六方面的第四种可能的实现方式中，所述冗余信息是周期性接收的。
结合第六方面的第四种可能的实现方式，在第六方面的第五种可能的实现方式中，所述冗余信息的接收周期小于PDCP丢弃定时器的时长。
结合第六方面的第四或第五种可能的实现方式，在第六方面的第六种可能的实现方式中，所述冗余信息包括上一次接收冗余信息后，从所述第一节点接收的所述一个或者多个数据包一一对应的所述一个或者多个PDCP SN。
结合第六方面的第六种可能的实现方式，在第六方面的第七种可能的实现方式中，所述冗余信息还包括所述上一次接收的冗余信息。
结合第六方面的第五种可能的实现方式，在第六方面的第八种可能的实现方式中，通信单元还用于，向所述第一节点发送所述PDCP丢弃定时器的时长信息。
结合第六方面或第六方面的第一至第八种可能的实现方式中的任意一种，在第六方面的第九种可能的实现方式中，还包括处理单元，处理单元用于，当所述第二节点确定未接收到所述冗余信息中的第一PDCP SN对应的数据包，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包，所述第一PDCP SN为所述一个或者多个PDCP SN中的一个PDCP SN。
结合第六方面的第二种可能的实现方式，在第六方面的第十种可能的实现方式中，所述多个标识序号是连续的，处理单元具体用于，当所述第二节点根据所述多个标识序号的连续性确定未接收到第一标识序号，所述第一标识序号为所述多个标识序号中的一个标识序号，所述第一标识序号对应的PDCP SN为第一PDCP SN，则所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包。
结合第六方面的第十种可能的实现方式，在第六方面的第十一种可能的实现方式中，所述第二节点进行PDCP重排序时，处理单元具体用于，若所述第一PDCP SN对应的数据包的PDCP丢弃定时器已开启，则停止所述第一PDCP SN对应的数据包的PDCP丢弃定时器；或者，若所述第一PDCP SN对应的数据包的PDCP丢弃定时器未开启，则放弃开启所述第一PDCP SN对应的数据包的PDCP丢弃定时器。
结合第六方面的第十或第十一种可能的实现方式，在第六方面的第十二种可能的实现方式中，通信单元还用于，向核心网发送PDCP SN大于所述第一PDCP SN的数据包。
结合第六方面或第六方面的第一至第十二种可能的实现方式中的任意一种，在第六方面的第十三种可能的实现方式中，通信单元还用于，向所述第一节点发送确认信息，所述确认信息用于确认收到所述冗余信息。
第七方面，公开了一种通信装置，其特征在于，包括处理器，处理器与存储器耦合；存储器，用于存储计算机程序。处理器，用于执行存储器中存储的计算机程序，以使得装置执行如上述第一方面、第一方面任意一种可能的实现方式、第二方面以及第二方面任意一种可能的实现方式所述的方法。
第八方面，公开了一种可读存储介质，包括程序或指令，当程序或指令被处理器运行时，如上述第一方面、第一方面任意一种可能的实现方式、第二方面以及第二方面任意一种可能的实现方式所述的方法。
第九方面，公开了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述第一方面以及第一方面任意一种可能的实现方式、第二方面以及第二方面任意一种可能的实现方式所述的方法。
第十方面，公开了一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行如上述第一方面以及第一方面任意一种可能的实现方式、第二方面以及第二方面任意一种可能的实现方式所述的方法。
第十一方面，公开了一种无线通信装置，包括：无线通信装置中存储有指令；当无线通信装置在上述第三方面至第六方面所述的装置上运行时，使得装置执行如上述实现上述第一方面以及第一方面任意一种可能的实现方式、第二方面以及第二方面任意一种可能的实现方式所述的方法，无线通信装置为芯片。
第十二方面，本申请实施例提供了一种芯片，该芯片包括处理器和接口电路，该接口电路和该处理器耦合，该处理器用于运行计算机程序或指令，以实现如上述第一方面以及第一方面任意一种可能的实现方式、第二方面以及第二方面任意一种可能的实现方式所述的方法，该接口电路用于与该芯片之外的其它模块进行通信。
第十三方面，本申请实施例提供一种通信系统，该通信系统包括第一节点和第二节点。示例的，第一节点向第二节点发送一个或者多个数据包，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN；所述第一节点向所述第二节点发送冗余信息，所述冗余信息包括所述一个或者多个PDCP SN，所述一个或者多个PDCP SN和所述一个或者多个数据包是一一对应的。
附图说明
图1A为本申请实施例提供的通信系统的架构图；
图1B为本申请实施例提供的通信系统的另一架构图；
图1C为本申请实施例提供的通信系统的另一架构图；
图1D为本申请实施例提供的通信系统的另一架构图；
图1E为本申请实施例提供的通信系统的另一架构图；
图1F为本申请实施例提供的通信系统的另一架构图；
图1G为本申请实施例提供的网络侧角度的协议架构的示意图；
图1H为本申请实施例提供的通信系统的另一架构图；
图1I为本申请实施例提供的通信系统的另一架构图；
图1J为本申请实施例提供的通信系统的另一架构图；
图1K为本申请实施例提供的通信系统的另一架构图；
图2A为本申请实施例提供的通信装置的结构框图；
图2B为本申请实施例提供的DU、CU的结构框图；
图3为本申请实施例提供的冗余信息反馈方法的流程示意图；
图4为本申请实施例提供的数据包的示意图；
图5为本申请实施例提供的数据包的另一示意图；
图6为本申请实施例提供的数据包的另一示意图；
图7为本申请实施例提供的冗余信息反馈方法的另一流程示意图；
图8为本申请实施例提供的冗余信息反馈方法的示意图；
图9为本申请实施例提供的冗余信息反馈方法的另一示意图；
图10为本申请实施例提供的通信装置的另一结构框图；
图11为本申请实施例提供的通信装置的另一结构框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
首先对本申请实施例涉及的术语进行解释说明：
(1)分组数据汇聚协议(packet data convergence protocol，PDCP)层
PDCP层主要对来自控制面的RRC消息和来自数据面的IP包进行处理，包括：对接收到的数据进行头部压缩和解压缩、加密/解密、完整性保护、传输用户数据和控制面数据、重排序和重传处理等。
(2)PDCP数据包
对于PDCP层，接收到的数据包、发送的数据包均认为是PDCP数据包。其中，PDCP层接收的数据包可以称为PDCP服务数据单元(service data unit，SDU)，PDCP层发送的数据包可以称为PDCP协议数据单元(protocol data unit，PDU)。
(3)PDCP序列号(sequence number，SN)
PDCP SN是PDCP数据包的编号，不同的PDCP SN用于标识不同的PDCP数据包。在网络状况良好的情况下，PDCP层收到的PDCP数据的PDCP SN可能是连续的；在网络状况不佳的情况下，可能会出现丢包，PDCP层收到的PDCP数据包的PDCP SN是不连续的。如果网络延迟较大，PDCP层收到的PDCP数据包的PDCP SN有可能是乱序的。
本申请实施例提供了一种通信系统，在该通信系统中可以包括至少两个节点，两 个节点可以通过两个节点之间的接口相连。这两个节点可以是不同的两个接入网设备，也可以是同一个接入网设备上的不同单元，例如，这两个节点为接入网设备中的集中单元(centralized unit，CU)、分布单元(distributed unit，DU)。一个节点从UE接收到数据包后，该节点的可以通过接口向另一个节点发送数据包，另一个节点会将数据包进行重排序，然后发送给核心网。例如，一个节点从空口接收到数据包后，该节点的RLC层可以通过节点之间的接口向另一个节点的PDCP层发送数据包，另一个节点的PDCP层会进行重排序，然后将重排序后的数据包发送给核心网。
下面结合图1A至图1K对上述通信系统进行举例。
本申请实施例提供的方法适用于图1A所示的通信系统。参考图1A，多个(图1A中以两个发送节点作为示例)发送节点向一个接收节点发送数据。其中，发送节点1通过传输链路1向接收节点发送数据，发送节点2通过传输链路2向接收节点发送数据。由于传输链路1、传输链路2上的时延不同可能导致接收节点接收到的PDCP数据包的PDCP SN是乱序的，接收节点需要对接收到的PDCP数据包进行重新排序。另外，传输链路1、传输链路2上也有可能出现丢包，也就是说，在接收节点重排序场景下，收发节点之间的传输路径上可能出现丢包。图1A中，发送节点1可以是终端、接入网设备或者接入网设备中的单元；发送节点2可以是终端、接入网设备或者接入网设备中的单元；接收节点可以是接入网设备或者接入网设备中的单元。图1A所示的通信系统支持双连接(dual connectivity，DC)。
本申请实施例提供的方法适用于图1B所示的通信系统。图1B中只有一个发送节点向接收节点发送数据。发送节点向接收节点发送的数据包本身就是乱序的，接收节点需要对接收到的数据包进行重新排序。另外，发送节点和接收节点之间的传输链路上可能存在丢包，也就是说接收节点重排序场景下，传输链路存在丢包的可能性。图1B中，发送节点可以是接入网设备或者接入网设备中的单元；接收节点可以是接入网设备或者接入网设备中的单元。图1B所示的通信系统支持DC或单连接。
图1C是本申请实施例提供的方法适用的一种DC场景，图1C所示为演进的通用陆基无线接入(Evolved Universal Terrestrial Radio Access，E-UTRA)及新空口(New Radio，NR)的双连接(E-UTRA-NR Dual Connectivity，EN-DC)。如图1C所示，核心网网元是演进分组核心网(evolved packet core，EPC)网元，主节点(master node，MN)是eNB，辅节点(secondary node，SN)是gNB。eNB、gNB与EPC网元之间的接口为s1接口。
MN和SN可以通过X2接口相连，MN和SN之间可以有用户面连接；MN与核心网网元可以通过S1接口相连，MN与核心网网元之间可以有用户面连接；SN11与核心网网元可以通过S1-U接口相连，SN核心网网元之间可以有用户面连接。
图1D是本申请实施例提供的方法适用的一种DC场景，图1D所示为下一代(nextgeneration，NG)无线接入网络(radio access network，RAN)演进的通用陆基无线接入(evolved universal terrestrial radio access，E-UTRA)及NR的双连接(NG-RAN E-UTRA-NR Dual Connectivity，NGEN-DC)。如图1G所示，核心网网元是是第五代(5G，5th Generation)核心网(5G core，5GC)网元，主节点(master node，MN)是eNB，辅节点(secondary node，SN)是gNB。eNB、gNB与EPC网元之间的接口 为s1接口。
MN和SN之间可以通过Xn接口相连，MN和SN之间可以有用户面连接；MN与核心网网元可以通过NG接口相连，MN与核心网网元之间可以有用户面连接；SN与核心网网元可以通过NG-U接口相连，SN核心网网元之间可以有用户面连接。
图1E是本申请实施例提供的方法适用的一种DC场景，图1E所示为NR及E-UTRA的双连接(NR-E-UTRA dual connectivity，NE-DC)网络架构。参考图1E，核心网网元是5GC网元，MN是gNB，SN是eNB。MN和SN可以相连，例如通过Xn接口连接。MN和SN之间可以有用户面连接；MN与核心网网元可以相连，例如通过NG接口。MN与核心网网元之间可以有用户面连接；SN与核心网网元可以相连，例如通过NG-U接口，SN核心网网元之间可以有用户面连接。
图1F是本申请实施例提供的方法适用的一种DC场景，图1F所示为NR与NR的双连接(NR-NR Dual Connectivity，NR-DC)。参考图1I，核心网网元是5GC网元，MN是gNB，SN11是gNB。MN和SN可以相连，例如通过Xn接口。MN和SN之间可以有用户面连接；MN与核心网网元可以相连，例如通过NG接口，MN与核心网网元之间可以有用户面连接；SN与核心网网元可以相连，例如通过NG-U接口，SN核心网网元之间可以有用户面连接。
需要强调的是，本申请实施例适用的通信系统包括但不限于上述图1A～图1F所示的通信系统。接收节点需要对数据包进行重排序，且收发节点之间的传输链路上存在丢包的场景都适用本申请实施例提供的方法，本申请对此不作限制。
图1G所示，一种网络侧角度的协议架构的示意图，从网络侧(MN01和SN11)的角度，可以有如下6种类型的用户面承载。下面以下行为例分别介绍了每种承载类型的数据流向，本领域技术人员可以理解的是，上行与下行类似，在此不再赘述。
1、MN终结的主小区组(Master Cell Group，MCG)承载。
数据从核心网网元下发至MN，依次经过MN的分组数据汇聚协议(packet data convergence protocol，PDCP)、无线链路层控制协议(Radio Link Control，RLC)层和媒体接入控制(Media Access Control，MAC)层发送至终端。
2、MN终结的辅小区组(Secondary Cell Group，SCG)承载。
数据从核心网网元下发至MN，经过MN的PDCP层发送至SN的RLC层，依次经过SN的RLC层和MAC层发送至终端。
3、MN终结的分流(Split)承载。
数据从核心网网元下发至MN，MN的PDCP层对数据进行分流，一部分数据依次经过MN的RLC层和MAC层发送至终端，另一部分数据发送至SN的RLC层，依次经过SN的RLC层和MAC层发送至终端。
4、SN终结的Split承载。
数据从核心网网元下发至SN，SN的PDCP层对数据进行分流，一部分数据依次经过SN的RLC层和MAC层发送至终端，另一部分数据发送至MN的RLC层，依次经过MN的RLC层和MAC层发送至终端。
5、SN终结的MCG承载。
数据从核心网网元下发至SN，经过SN的PDCP层发送至MN的RLC层，依次 经过MN的RLC层和MAC层发送至终端。
6、SN终结的SCG承载。
数据从核心网网元下发至SN，依次经过SN的PDCP层、RLC层和MAC层发送至终端。
上述MCG承载涉及MCG空口资源，SCG承载涉及SCG空口资源，Split承载涉及MCG空口资源和SCG空口资源。
可选的，在上述多种承载类型中，MN和SN的PDCP实体可以是NR PDCP实体，此外，在EN-DC下的MN终结的MCG承载中，MN的PDCP实体还可以是E-UTRA PDCP。当核心网网元是5GC网元时，MN的PDCP层上可以有SDAP层，数据从核心网网元下发至MN，经过MN的SDAP层到达MN的PDCP层；SN的PDCP层上可以有SDAP层，数据从核心网网元下发至SN11，经过SN的SDAP层到达S1的PDCP层。
以下结合具体承载类型对本申请实施例涉及的通信系统进行说明。图1H是本申请实施例提供的方法适用的一种DC场景，图1H所示为NSA DC Option3组网架构，该场景涉及的承载类型为MN终结的Split承载。在NSA DC Option3组网中，开启动态分流机制。示例的，UE发出的数据，经LTE空口到达eNB，经NR空口到达gNB。gNB需要通过基站与基站之间的X2接口向eNB发送接收到的数据包，eNB需要对空口接收到的数据包以及gNB传递的数据包进行重新排序，之后eNB将数据包传递给核心网。需要说明的是，gNB向eNB发送数据包时可能出现丢包，也就是说eNB重排序场景下，gNB和eNB之间的传输路径上有丢包可能，也可以认为X2接口存在丢包可能。
本申请实施例提供的方法适用于图1I所示的通信系统。图1I所示为非独立(non standalone，NSA)双连接(dual connectivity，DC)Option3x组网架构。在NSA DC Option3x组网中，开启动态分流机制，该场景涉及的承载类型为SN终结的Split承载。示例的，参考图1B，UE发出的数据，经长期演进(long term evolution，LTE)空口到达演进基站(evolution node basestation，eNB)，经NR空口到达下一代基站(next generation node B，gNB)。eNB需要通过基站与基站之间的X2接口向gNB发送接收到的数据包，gNB需要对空口接收到的数据包以及eNB传递的数据包进行重新排序，之后gNB将数据包传递给核心网。需要说明的是，eNB向gNB发送数据包时可能出现丢包，也就是说gNB重排序场景下，gNB和eNB之间的传输路径上有丢包可能，也可以认为X2接口存在丢包可能。
图1J是本申请实施例提供的方法适用的一种DC场景，图1J所示的NSA DC Option3组网中，未开启动态分流机制，该场景涉及的承载类型为MN终结的SCG承载。参考图1J，UE发出的数据包经NR空口到达gNB。因为空口误码，有些数据包需要重传，有些数据包是一次传输成功，所以数据包到达NR无线链路控制层(redio link control，RLC)实体后可能是乱序的。NR RLC实体不对数据包进行重排序，收到数据包后会投递给LTE PDCP实体，由LTE PDCP对报文做重排序。也就是说，此时gNB发给eNB的数据包本身就是乱序的，eNB需要对接收到的数据包进行重排序，之后投递给核心网。gNB向eNB发送数据包时可能出现丢包，也就是说eNB重排序场 景下，gNB和eNB之间的传输路径上有丢包可能，也可以认为X2接口存在丢包可能。
例如，图1K是本申请实施例提供的方法适用的组网结构，图1K所示为纯粹的5G组网。云无线接入网设备(Cloud radio access network，Cloud RAN)架构下，将RAN基站分离成CU、DU两个组成部分，CU、DU之间的接口可以称为F1接口。Cloud RAN架构下UE发出的数据包经NR空口乱序到达gNB的分布单元(distributed unit，DU)，gNB的DU将乱序的数据包经F1接口转发给gNB的集中单元(centralized unit，CU)，gNB的CU对接收到的数据包做重排序。也就是说接收节点重排序场景下，收发节点之间的传输路径上有丢包可能，也可以认为F1接口存在丢包可能。
另外，上述NSA组网架构eNB和gNB之间的传输接口称为X2接口(X2 interface)；UE和基站之间的空口接口称为UU接口(UU Interface)。
需要说明的是，节点之间的传输路径，可以理解为节点之间的链路，例如，节点之间可以通过接口连接，节点之间的传输路径可以理解为节点之间的接口，接入网设备与终端之间的传输路径，可以理解为接入网设备和终端之间的空口。
以图1I所示的通信系统为例，假设UE需要向核心网发送PDCP SN分别为1～9的数据包，其中，UE通过空口向eNB发送PDCP SN为3、6、9的数据包，由eNB通过X2接口向gNB发送PDCP SN为3、6、9的数据包。UE通过空口向gNB发送其它报文。假设UE和eNB之间的传输链路的传输时延较大，PDCP SN为3、6、9的数据包晚于其它报文到gNB。PDCP SN为1、2的数据包报文到达gNB时，被gNB直接传递给核心网。PDCP SN为4的数据包到达gNB的时候，由于PDCP SN为3的数据包未到达gNB，PDCP SN不连续，gNB启动定时器等待PDCP SN为3的数据包，并暂停向核心网发送数据包。
如果在定时器超时前PDCP SN为3的数据包到达gNB，gNB则将PDCP SN为3的数据包则3投递给核心网，并接着将PDCP SN为4、5的数据包投递给核心网。
如果定时器超时，PDCP SN为3的数据包还到达gNB，gNB则直接向核心网投递PDCP SN为4、5的数据包，不再等待PDCP SN为3的数据包。在等待PDCP SN为3的数据包的过程中，gNB和核心网之间是没有数据传输的，也就是说，这段时间的传输带宽浪费了。
本申请实施例提供一种方法，第一节点向第二节点发送一个或者多个数据包后，第一节点还会向第二节点发送冗余信息，该冗余信息包括该一个或者多个数据包的PDCP SN。首先，第二节点可以根据冗余信息确定在第一节点向第二节点发送多个数据包时，是否出现丢包，从而，第二节点可以准确地确定丢失的数据包发生在空口还是发生在节点之间的接口，第二节点在重排序时可以选择不同的策略应对丢失数据包。其次，第二节点一旦判断第一节点和第二节点之间的传输路径上出现丢包，可以在重排序数据包时跳过该数据包，例如，假设已开启了等待该数据包的定时器，则终止等待该数据包的定时器，第二节点可以继续向核心网投递数据包；或者，还未开始等待该数据包的定时器，则不开启等待数据包的定时器，在当前已运行的定时器(等待其他数据包)超时之后，第二节点可以继续向核心网投递数据包，当第二节点确定丢包不是发生在第一节点和第二节点之间的传输路径上，说明丢包可能发生在空口上，第二节点可以开启等待该数据包的定时器，等待该丢失的数据包，直到定时器超时，才 向核心网投递数据包。可见，本申请实施例提供的方法可以准确得判断发生丢包的传输路径，并且避免长时间等待丢失的数据包造成带宽的浪费，有利于提升通信性能。
图2A是本申请实施例提供的通信装置的结构框图，图2A所示的通信装置210可以是接入网设备，例如，可以是本申请实施例涉及的第一节点或第二节点。
接入网设备包括至少一个处理器2101、至少一个存储器2102、至少一个收发器2103、至少一个网络接口2104和一个或多个天线2105。处理器2101、存储器2102、收发器2103和网络接口2104相连，例如通过总线相连，在本申请实施例中，所述连接可包括各类接口、传输线或总线等，本实施例对此不做限定。天线2105与收发器2103相连。网络接口2104用于使得接入网设备通过通信链路，与其它通信设备相连，例如网络接口2104可以包括接入网设备与核心网网元之间的网络接口，例如S1接口，网络接口可以包括接入网设备和其他网络设备(例如其他接入网设备或者核心网网元)之间的网络接口，例如X2或者Xn接口。
处理器2101主要用于对通信协议以及通信数据进行处理，以及对整个接入网设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持接入网设备执行实施例中所描述的动作。接入网设备可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。图2A中的处理器2101可以集成基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储器中，由处理器执行软件程序以实现基带处理功能。
存储器主要用于存储软件程序和数据。存储器2102可以是独立存在，与处理器2101相连。可选的，存储器2102可以和处理器2101集成在一起，例如集成在一个芯片之内。其中，存储器2102能够存储执行本申请实施例的技术方案的程序代码，并由处理器2101来控制执行，被执行的各类计算机程序代码也可被视为是处理器2101的驱动程序。
图2A仅示出了一个存储器和一个处理器。在实际的终端设备中，可以存在多个处理器和多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以为与处理器处于同一芯片上的存储元件，即片内存储元件，或者为独立的存储元件，本申请实施例对此不做限定。
收发器2103可以用于支持接入网设备与终端之间射频信号的接收或者发送，收发器2103可以与天线2105相连。收发器2103包括发射机Tx和接收机Rx。具体地，一个或多个天线2105可以接收射频信号，该收发器2103的接收机Rx用于从天线接收所述射频信号，并将射频信号转换为数字基带信号或数字中频信号，并将该数字基带信号或数字中频信号提供给所述处理器2101，以便处理器2101对该数字基带信号或 数字中频信号做进一步的处理，例如解调处理和译码处理。此外，收发器2103中的发射机Tx还用于从处理器2101接收经过调制的数字基带信号或数字中频信号，并将该经过调制的数字基带信号或数字中频信号转换为射频信号，并通过一个或多个天线2105发送所述射频信号。具体地，接收机Rx可以选择性地对射频信号进行一级或多级下混频处理和模数转换处理以得到数字基带信号或数字中频信号，所述下混频处理和模数转换处理的先后顺序是可调整的。发射机Tx可以选择性地对经过调制的数字基带信号或数字中频信号时进行一级或多级上混频处理和数模转换处理以得到射频信号，所述上混频处理和数模转换处理的先后顺序是可调整的。数字基带信号和数字中频信号可以统称为数字信号。
收发器也可以称为收发单元、收发机、收发装置等。可选的，可以将收发单元中用于实现接收功能的器件视为接收单元，将收发单元中用于实现发送功能的器件视为发送单元，即收发单元包括接收单元和发送单元，接收单元也可以称为接收机、输入口、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
一种可能的实现方式中，处理器2101可以调用存储器2102中存储的代码执行以下功能：支持第一节点向第二节点发送一个或者多个数据包，所述一个或者多个数据包中的每个数据包包括所述数据包的分组数据汇聚协议序列号PDCP SN；
支持第一节点向所述第二节点发送冗余信息，所述冗余信息包括所述一个或者多个PDCP SN，所述一个或者多个PDCP SN和所述一个或者多个数据包是一一对应的。
支持第二节点从第一节点接收所述一个或多个数据包，支持第二节点根据冗余信息确定第一节点与第二节点的传输路径上是否存在数据包丢失。
图2B是本申请实施例提供CU、DU的结构框图，其中，CU可以是本申请实施例所述的第二节点，DU可以是本申请实施例所述的第一节点。
示例的，参考图2B，基站可包括一个或多个DU 221和一个或多个CU 222。CU222可以与NG core(下一代核心网，NC)通信。
所述DU 221可以包括至少一个天线2211，至少一个射频单元2212，至少一个处理器2213和至少一个存储器2214。所述DU 221部分主要用于射频信号的收发以及射频信号与基带信号的转换，以及部分基带处理。CU222可以包括至少一个处理器2222和至少一个存储器2221。CU222和DU221之间可以通过接口进行通信，其中，控制面(Control plan)接口可以为Fs-C，比如F1-C，用户面(User Plan)接口可以为Fs-U，比如F1-U。
所述CU 222部分主要用于进行基带处理，对基站进行控制等。所述DU 221与CU 222可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。所述CU 222为基站的控制中心，也可以称为处理单元，主要用于完成基带处理功能。例如所述CU 222可以用于控制基站执行上述方法实施例中关于网络设备的操作流程。
具体的，CU和DU上的基带处理可以根据无线网络的协议层划分，例如分组数据汇聚层协议(packet data convergence protocol，PDCP)层及以上协议层的功能设置在CU，PDCP以下的协议层，例如无线链路控制(radio link control，RLC)层和媒体接入控制(media access control，MAC)层等的功能设置在DU。又例如，CU实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence  protocol，PDCP)层的功能，DU实现无线链路控制(radio link control，RLC)、媒体接入控制(media access control，MAC)和物理(physical，PHY)层的功能。
此外，可选的，基站60可以包括一个或多个射频单元(RU)，一个或多个DU和一个或多个CU。其中，DU可以包括至少一个处理器2213和至少一个存储器2214，RU可以包括至少一个天线2211和至少一个射频单元2212，CU可以包括至少一个处理器2222和至少一个存储器2221。
在一个实例中，所述CU222可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述存储器2221和处理器2222可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。所述DU221可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述存储器2214和处理器2213可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
本申请实施例提供一种冗余信息反馈方法，应用于图1A～图1F、图1H～图1K所示的通信系统，如图3所示，所述方法包括以下步骤：
301、第一节点向第二节点发送一个或者多个数据包，所述一个或者多个数据包中的每个数据包包括所述数据包的PDCP SN。
本申请实施例中，第一节点向第二节点发送的一个或者多个数据包可以记为N个数据包，所述N个数据包中的每个数据包包括所述数据包的PDCP SN。第二节点可能接收到了第一节点发送的N个数据包，或者，第二节点仅接收到所述N个数据包中的部分数据包，例如，可以将第二节点接收到的一个或者多个数据包称为M个数据包，所述M个数据包中的每个数据包包括所述数据包的PDCP SN，N和M均为大于等于1的整数，N大于等于M。或者，第二节点可能没有接收到N个数据包中的任一个，此时N个数据包在第一节点和第二节点之间的传输路径上丢失了。
需要说明的是，第一节点可以向第二节点发送数据包，第二节点可以对接收到的数据包进行排序之后再递交给核心网。第一节点、第二节点可以是接入网设备，例如，第一节点可以是图1A所示通信系统中的发送节点1或发送节点2，第二节点为图1A所示通信系统中的接收节点；或者，第一节点为图1B所示通信系统中的发送节点，第二节点为图1B所示通信系统中的接收节点；或者，第一节点为图1C～1F所示通信系统中的SN，第二节点为图1C～1E所示通信系统中的MN；或者，第一节点为图1C～1F所示通信系统中的MN，第二节点为图1C～1F所示通信系统中的SN；或者，第一节点为图1H所示通信系统中的gNB，第二节点为图1H所示通信系统中的eNB；或者，第一节点为图1I所示通信系统中的eNB，第二节点为图1I所示通信系统中的gNB；或者，第一节点为图1J所示通信系统中的gNB，第二节点为图1J所示通信系统中的gNB。或者，第一节点和第二节点可以是一个接入网设备中的不同单元，第一节点可以是CU，第二节点可以是DU，例如，第一节点为图1K所示通信系统中的DU，第二节点为图 1K所示通信系统中的CU。
在数据分流场景中，第一节点、第二节点分别可以通过空口接收数据包，并且第一节点可以向第二节点发送自己通过空口接收到的数据包。数据包最终在第二节点汇聚，第二节点可以对空口接收到的数据包、第一节点发送的数据包进行重排序，重排序之后将数据包传递给核心网。例如，第一节点可以是图1B所示通信系统中的eNB，第二节点可以是图1B所示通信系统中的gNB；或者，第一节点可以是图1C所示通信系统中的gNB，第二节点可以是图1C所示通信系统中的eNB。
在数据未分流的场景中，第一节点可以通过空口接收数据包，第一节点可以将自己空口接收到的数据包发送给第二节点。由于空口误码，第一节点接收到的数据包有可能是乱序的，因此第一节点发送给第二节点的数据包本身就是乱序的。第二节点从第一节点接收数据包之后，可以对接收到的数据包进行重排序，重排序之后将数据包传递给核心网。例如，第一节点可以是图1E所示通信系统中的gNB，第二节点可以是图1E所示通信系统中的eNB。或者，第一节点可以是图1F所示架构中的DU，第二节点可以是图1F所示通信系统中的CU。
一种可能的实现方式中，本申请实施例所述的数据包为PDCP数据包，第二节点的PDCP层(PDCP实体)接收第一节点发送的数据包，并对接收到的数据包进行重排序。示例的，PDCP数据包的报文格式可以是图4所示的格式。参考图4，PDCP数据包包括网络协议(internet protocol，IP)头、用户数据包协议(user datagram protocol，UDP)头、通用分组无线服务隧道协议用户(general packet radio service tunnelling protocol user，GTPU)头、PDCP头、扩展头以及业务数据字段。其中，PDCP头包括“PDCP序列号字段”，“PDCP序列号字段”用于填充数据包的PDCP SN。
示例的，第一节点向第二节点发送一个或多个数据包，每个数据包都包括该数据包的PDCP SN。示例的，第一节点向第二节点发送PDCP SN为1的数据包，该数据包中包括PDCP SN“1”，例如，PDCP SN为1的数据包的“PDCP序列号字段”填充的是“1”。
302、第一节点向所述第二节点发送冗余信息，所述冗余信息包括所述一个或者多个PDCP SN，所述一个或者多个PDCP SN和所述一个或者多个数据包是一一对应的。
这里冗余信息可以为其他名称，例如第一信息等，本申请实施例对此不作限定。
具体实现中，第一节点除了向第二节点发送了一个或多个数据包，还向第二节点发送这一个或多个数据包中每一个数据包的PDCP SN，即第一节点向第二节点发送一个或多个PDCP SN。可以理解的是，第一节点在步骤302发送的一个或者多个PDCP SN与第一节点在步骤301发送的一个或者多个数据包是一一对应的。
冗余信息包括的所述一个或者多个PDCP SN可以记为N个PDCP SN，与S301中第一节点向第二节点发送的N个数据包一一对应。
一种可能的实现方式中，第二节点收到冗余信息之后，可以根据冗余信息确定第一节点和第二节点之间的传输路径上是否有丢包，在确定丢包后，可以在重排序的时候跳过(忽略)这个数据包。
示例性地，第二节点可以将冗余信息中的N个PDCP SN与接收到的M个数据包的PDCP SN进行比较，针对冗余信息中的任意一个PDCP SN，第二节点可以判断是 否接收到该PDCP SN对应的数据包。例如，冗余信息包括PDCP SN“1”，第二节点可以判断接收到的M个数据包中是否存在PDCP SN“1”对应的数据包(即PDCP SN为“1”的数据包)，若第二节点接收到的M个数据包中包括PDCP SN为“1”的数据包，则代表第二节点接收到了PDCP SN为“1”的数据包；若第二节点接收到的M个数据包中不包括PDCP SN为“1”的数据包，则代表第二节点未接收到PDCP SN为“1”的数据包。
示例的，当所述第二节点确定未接收到所述冗余信息中的第一PDCP SN对应的数据包，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包。其中，所述第一PDCP SN为冗余信息包括的一个或者多个PDCP SN中的任一个PDCP SN。
例如，第二节点可以将接收到的一个或者多个数据包对应的一个或者多个PDCP SN与冗余信息中的一个或者多个PDCP SN进行对比，确定是否存在冗余信息中的PDCP SN对应的数据包没有接收到。
具体实现中，第二节点跳过第一PDCP SN对应的数据包，可以包括但不限于以下两种方式：
第一种、若所述第一PDCP SN对应的数据包的PDCP丢弃定时器已开启，则停止所述第一PDCP SN对应的数据包的PDCP丢弃定时器。
第二节点从第一节点接收数据包，通过解析数据包可以获取接收到的每个数据包的PDCP SN，当获取到的PDCP SN是连续的，即接收到的数据包是连续的，第二节点则向核心网投递接收到的数据包。当获取到的PDCP SN不连续，第二节点可以确定接收到的数据包不连续，例如，缺失PDCP SN为第一PDCP SN的数据包。
第二节点确定接收到的数据包不连续，则启动定时器等待未收到的数据包，即PDCP SN为第一PDCP SN的数据包。需要说明的是，所述定时器可以是PDCP丢弃定时器，用于等待未接收到的数据包，一旦定时器超时才停止等待该数据包。本申请实施例对定时器的时长不做限制。
当第二节点接收冗余信息，从冗余信息中获取多个PDCP SN。第二节点还可以对比冗余信息中的PDCP SN和解析出的PDCP SN，确定上述未收到的数据包是否丢失。例如，第二节点解析冗余信息获取到了第一PDCP SN，但为未接收到PDCP SN为第一PDCP SN的数据包，可以确定第一节点向第二节点发送了第一PDCP SN对应的数据包，但是第二节点未接收到第一PDCP SN对应的数据包，第二节点则可以确定该数据包为丢失的数据包。一旦确定未收到的数据包为丢失的数据包，则终止该等待该数据包的定时器，不再等待该数据包。例如，第二节点可以定时器终止，不再等待PDCP SN为第一PDCP SN的数据包，继续进行数据包重排序，并在重排序时忽略(跳过)PDCP SN为第一PDCP SN的数据包，将接收到的其他数据包进行重排序，并将重排序之后的数据包传递给核心网，即向核心网发送PDCP SN大于所述第一PDCP SN的数据包。
又一示例中，假设第二节点从第一节点接收的数据包为：PDCP SN为“1”的数据包、PDCP SN为“2”的数据包、PDCP SN为“4”的数据包以及PDCP SN为“5”的数据包，接收到PDCP SN为“1”的数据包、PDCP SN为“2”的数据包直接投递给核心网，接收到PDCP SN为“4”的数据包后，第二节点发现接收到的数据包不连续，则启动PDCP丢 弃定时器，等待PDCP SN为“3”的数据包。
随后，第二节点从第一节点接收冗余信息，从冗余信息中获取5个PDCP SN，分别为“1、2、3、4、5”，第二节点则确定第一节点和第二节点的传输路径上出现了丢包，PDCP SN为“3”的数据包已丢失，则立即终止PDCP丢弃定时器，不再等待PDCP SN为“3”的数据包。对PDCP SN为“4、5”的数据包进行重排序，并将重排序后的PDCP SN为“4、5”的数据包传递给核心网。由于PDCP SN为“3”的数据包在第一节点和第二节点的传输路径上丢失，第二节点则无需花费过长时间等待该数据包，及时终止定时，继续向核心网投递数据包，避免浪费带宽资源，提升系统性能。
第二种、若所述第一PDCP SN对应的数据包的PDCP丢弃定时器未开启，则放弃开启所述第一PDCP SN对应的数据包的PDCP丢弃定时器。
当第二节点从第一节点接收数据包，通过解析数据包可以获取接收到的每个数据包的PDCP SN，当获取到的PDCP SN不连续，第二节点可以确定接收到的数据包不连续，例如，缺失PDCP SN为第二PDCP SN的数据包，第二节点则开启定时器1等待PDCP SN为第二PDCP SN的数据包。
当第二节点接收到冗余信息，由于冗余信息中包括第二PDCP SN，第二节点可以判断第二PDCP SN对应的数据包为丢失的数据包。后续第二节点继续从第一节点接收数据包，再次发现PDCP SN不连续，例如，缺失第一PDCP SN对应的数据包。假设冗余信息中包括第一PDCP SN，第二节点可以确定第一PDCP SN对应的数据包为丢失的数据包，第二节点不再开启定时器等待第一PDCP SN对应的数据包，在上述定时器1的有效时长内也可以等待第一PDCP SN对应的数据包。能够避免浪费较长时间等待丢失的数据包，造成带宽资源的浪费。
又一示例中，假设第二节点从第一节点接收的数据包为：PDCP SN为“1”的数据包、PDCP SN为“2”的数据包、PDCP SN为“4”的数据包以及PDCP SN为“5”的数据包，接收到PDCP SN为“1”的数据包、PDCP SN为“2”的数据包直接投递给核心网，接收到PDCP SN为“4”的数据包后，第二节点发现接收到的数据包不连续，则启动PDCP丢弃定时器，等待PDCP SN为“3”的数据包。
随后，第二节点从第一节点接收冗余信息，从冗余信息中获取6个PDCP SN，分别为“1、2、3、4、5、6”，第二节点则确定第一节点和第二节点的传输路径上出现了丢包，PDCP SN为“3”的数据包已丢失，在上述PDCP丢弃定时器的有效时长内等待PDCP SN为“3”的数据包。
第二节点接着从第一节点接收PDCP SN为“7”的数据包，PDCP SN不连续，第二节点未收到PDCP SN为“6”的数据包，但是冗余信息中包括PDCP SN“6”，PDCP SN为“6”的数据包为丢失的数据包。第二节点不再启动新的定时器等待PDCP SN为“6”的数据包，可以在等待PDCP SN为“3”的数据包的定时器的有效时长内等待PDCP SN为“6”的数据包。避免第二节点花费较长时间等待丢失的数据包，长时间不向核心网传递数据包，浪费了第二节点与核心网之间的带宽资源。
下面对冗余信息的携带方式做进一步的说明。
一种可能的实现方式中，第一节点可以通过同类型数据包向第二节点冗余发送数据包的PDCP SN。例如，第一节点向第二节点发送的一个或多个数据包为PDCP数据 包，PDCP数据包携带业务数据。第一节点还可以通过其他PDCP数据包向第二节点发送上述一个或多个数据包各自的PDCP SN。该其他PDCP数据包与该一个或者多个数据包不同。可以理解，第一节点向第二节点发送一个或者多个数据包后，再通过其他PDCP数据包携带冗余信息。
可以理解的是，冗余信息携带可以在包括业务数据的数据包中，所述包括业务数据的数据包与所述一个或者多个数据包不同，即携带冗余信息的数据包和第一节点在步骤301发送的一个或多个数据包不同。
示例的，参考图4所示的数据包格式，冗余信息可以填充在数据包的扩展头。
另一种可能的实现方式中，第一节点通过不同类型的数据包向第二节点发送冗余信息，例如，携带冗余信息的数据包不包括业务数据，而第一节点在步骤301发送的一个或多个数据包包括业务数据，二者是不同类型的数据包。
示例的，第一节点可以构造专用格式的数据包(例如，本申请实施例所述的冗余信息)来发送一个或者多个数据包的PDCP SN。示例的，图5是携带冗余信息的数据包一种可能的格式，参考图5，这种数据包由外到内依次是IP头、UDP头、GTPU头、冗余信息。参考图5，冗余信息包括第一PDCP SN字段、第二PDCP SN字段…第N PDCP SN字段。其中，第一PDCP SN字段、第二PDCP SN字段…第N PDCP SN字段与第一节点发送的一个或者多个数据包一一对应，用于填充与其对应的数据包的PDCP SN。一种可能的实现方式中，第一PDCP SN字段、第二PDCP SN字段…第N PDCP SN字段包括在数据包的PDCP头中。
示例的，第一PDCP SN字段用于填充所述一个或者多个数据包中的第一数据包的PDCP SN。假设第一数据包的PDCP SN为3，第一PDCP SN字段可以填充“11”。
可选的，第一节点在发送数据包时，可以携带数据包的标识序号，冗余信息还可以携带数据包的标识序号，下面对此做进一步的说明。
可选的，第一节点在步骤301发送的数据包还包括数据包的标识序号。其中，标识序号用于标识数据包，可以是和PDCP SN不同的任何一种用于标识数据包的序号。一种可能的实现中，第一节点按向第二节点发包顺序来编号，确定各个数据包的标识序号，第二节点可以按照这个标识序号的连续性确认第一节点和第二节点的传输路径上是否有丢包。
例如，第一节点通过X2接口向第二节点发送一个或多个数据包，第一节点按照发包数据确定的标识序号可以称为X2序列号。第一节点发送的每个数据包还可以包括数据包的X2序列号。X2序列号用于标识第一节点通过X2接口发送的数据包，第二节点可以根据X2序列号排序从第一节点接收到的数据包，根据X2序列号的连续性判断是否有丢包。
一种可能的实现方式中，数据包的标识序号可以填充在数据包的扩展头。示例的，在图3所示数据包结构中，第一节点在组包时，可以在扩展头填充数据包的标识序号。
可选的，第一节点向第二节点发送的冗余信息还包括一个或者多个标识序号，所述一个或者多个标识序号与所述一个或者多个PDCP SN是一一对应的。需要说明的是，一个标识序号与其对应的PDCP SN用于标识同一个数据包。
一种可能的实现方式中，冗余信息中PDCP SN和标识序号也是对应存在的。示例 的，图6是冗余信息的一种可能的格式。图6是携带冗余信息的数据包的一种可能的格式，参考图6，这种数据包由内到外依次包括IP头、UDP头、GTPU头以及冗余信息。其中，冗余信息可以包括标识序号范围以及第一字段、第二字段…第N字段。其中，标识序号范围用于指示冗余信息中的PDCP SN对应的多个数据包的标识序号的范围。示例的，标识序号范围是“1～10”，代表冗余信息中包括了标识序号为1、2、3…10这10个数据包的PDCP SN。另外，第一字段、第二字段…第N字段与第一节点发送的一个或者多个数据包一一对应，用于填充与其对应的数据包的PDCP SN和标识序号。例如，第一字段用于填充第一数据包的PDCP SN“110”以及第一数据包的标识序号“1”。
可选的，假设第一节点发送的数据包携带数据包的标识序号，且第一节点发送的冗余信息携带数据包的标识序号和数据包的PDCP SN。示例的，第一节点向第二节点发送一个或多个数据包，还可以向第二节点发送冗余信息，冗余信息中包括所述一个或多个数据包对应的一个或多个PDCP SN，以及一个或多个数据包对应的一个或多个标识序号。由于所述一个或多个数据包是第一节点连续发送的，按照数据包发送顺序确定标识序号，第一节点发送的多个数据包的标识序号也是连续的。可以理解的是，冗余信息中的多个标识序号也是连续的。
第二节点接收数据包后可以从数据包中解析数据包的标识序号，可以根据标识序号的连续性判断接收到的数据包是否连续。另外，还可以结合冗余信息，确定未接收到的数据包的PDCP SN。
例如，第二节点接收数据包，解析数据包之后发现没有接收到第一标识序号对应的数据包，且所述冗余信息中与所述第一标识序号对应的PDCP SN为所述第一PDCP SN，则确定未接收到所述第一PDCP SN对应的数据包。示例的，第二节点接收到标识序号为“1、3、4、5”的数据包，即未接收到标识序号为“2”的数据包，解析冗余信息确定与标识序号“2”对应的PDCP SN为“110”，即第二节点未接收到PDCP SN为“110”的数据包。
下面对冗余信息的发送时机作进一步的说明。
可选的，第一节点周期性发送冗余信息，并且冗余信息的发送周期小于PDCP丢弃定时器的时长。其中，PDCP丢弃定时器是第一节点发现接收到的数据包乱序(或缺失)时启动的定时器，第一节点在PDCP丢弃定时器的有效时长内等待未接收到的数据包。
可以理解的是，由于冗余信息的发送周期小于PDCP丢弃定时器的时长，第二节点可以在PDCP丢弃定时器超时前接收到冗余信息，还可以根据冗余信息确定第一节点和第二节点的传输路径上出现了丢包，进而终止等待数据包的PDCP丢弃定时器，使得第二节点可以继续向核心网投递数据包，避免长时间等待丢失的数据包，长时间留空带宽，能够合理利用带宽资源，提升通信性能。
可选的，所述冗余信息包括上一次发送冗余信息后，所述第一节点发送的所述一个或者多个数据包一一对应的所述一个或者多个PDCP SN。
示例的，第一节点每次发送的冗余信息都是为了向第二节点上一次发送冗余信息后，第一节点向第二节点发送的数据包的PDCP SN。例如，第一节点向第二节点发送数据包1～数据包4之后，向第二节点发送冗余信息指示数据包1～数据包4中每一个数 据包的PDCP SN。随后，第一节点向第二节点发送数据包5～数据包8，之后向向第二节点发送冗余信息指示数据包5～数据包8中每一个数据包的PDCP SN。
可选的，所述冗余信息还包括上一次发送的冗余信息。例如，第一节点向第二节点发送数据包1～数据包4之后，向第二节点发送冗余信息指示数据包1～数据包4中每一个数据包的PDCP SN。随后，第一节点向第二节点发送数据包5～数据包8，之后向向第二节点发送冗余信息指示数据包1～数据包4中每一个数据包的PDCP SN，以及数据包5～数据包8中每一个数据包的PDCP SN。
可选的，第二节点是汇聚数据包，执行数据包重排序的节点，第二节点维护PDCP丢弃定时器的时长信息。第二节点还可以向第一节点发送PDCP丢弃定时器的时长信息，第一节点从所述第二节点接收PDCP丢弃定时器的时长信息，可以根据PDCP丢弃定时器的时长信息确定PDCP丢弃定时器的时长，进而设置冗余信息的发送周期小于PDCP丢弃定时器的时长。
可选的，第一节点发送所述冗余信息的时刻与所述第一节点完成所述一个或者多个数据包的发送的时刻之间相差第一阈值。也就是说，第一节点在完成所述一个或多个数据包的发送之后，间隔一定时间再向第二节点发送冗余信息，指示所述一个或多个数据包的PDCP SN。
可以理解的是，假设受网络延迟的影响，第二节点先接收数据包关联的冗余信息，再接收数据包，有可能导致第二节点误以为该数据包丢失，在重排序的时候跳过该数据包。第一节点发送数据包和冗余信息间隔一定时间，尽可能保证第二节点接收某个数据包之后才接收与该数据包关联的冗余信息，可以避免第二节点误以为数据包丢失，避免错误的重排序操作。
可选的，所述第一节点完成所述一个或者多个数据包的发送后，先发送N个包括业务数据的数据包，再向所述第二节点发送所述冗余信息。
可以理解的是，假设受网络延迟的影响，第二节点先接收数据包关联的冗余信息，再接收数据包，有可能导致第二节点误以为该数据包丢失，在重排序的时候跳过该数据包。第一节点发送数据包和冗余信息间隔数个数据包，尽可能保证第二节点接收某个数据包之后才接收与该数据包关联的冗余信息，可以避免第二节点误以为数据包丢失，避免错误的重排序操作。
可选的，所述第一节点可以重复发送所述冗余信息。
可选的，所述第一节点可以重复发送所述冗余信息，直至从所述第二节点接收确认信息，所述确认信息用于确认收到所述冗余信息。也就是说，第一节点可以重复发送冗余信息，如果接收到了第二节点反馈的确认信息，则停止发送冗余信息。
本申请实施例中，第一节点发往第二节点的数据包本身可能存在乱序，第二节点可以对从第一节点接收到的数据包进行排序；或，第一节点通过第一数据无线承载向第二节点发送的数据包的PDCP SN不连续，第二节点还可以从其它承载(例如，第二承载)接收数据包，第二节点可以将通过第一数据无线承载、第二承载收到的数据包进行混合并排序。
需要说明的是，第一节点发送的一个或者多个数据包为第一数据无线承载的数据包。另外，所述第一数据无线承载的RLC层在所述第一节点，所述第一数据无线承载 的PDCP层在所述第二节点。也就是说，第一节点的RLC层组包、发送数据包，第二节点的PDCP层从第一节点的RLC层接收数据包，并在数据包不连续时，对数据包进行重排序。
一种可能的实现方式中，第一数据无线承载为主节点(master node，MN)终结的辅小区组(secondary cell group，SCG)承载，或MN终结的分流(Split)承载，或辅节点(secondary node，SN)终结的主小区组(master cell group，MCG)承载，或，SN终结的分流承载。
一种可能的实现方式中，图2A所示装置(第一节点)中的处理器2101调用存储器2102中的代码，执行图3所示的方法。
或者，图2B所示的DU的处理器2213调用存储器2214中的代码，执行图3所示的方法。
下面结合图7至图9对图3介绍的方案进行进一步的说明，图7至图9的内容可以与图3的内容相互引用和参考。
一种可能的实现方式中，NSA DC Option3x组网为例，eNB在向gNB发送数据包时，对数据包进行连续编号(以下称为X2序列号，即本申请实施例所述的标识序号)，并通过冗余信息指示数据包的X2序列号和PDCP SN之间的对应关系。gNB可以根据接收端依据编号的连续性判断是否丢包，并依据状态报告找到丢包的PDCP序列号，并在PDCP重排序队列里面找到对应序列号做规避重排序的动作。具体地，参考图7，本申请实施例提供的方法包括如下步骤：
801、gNB从NR空口接收，收到PDCP SN 200之前除了PDCP SN110、120、130～190、200以外的所有数据包。
需要说明的是，UE通过LTE空口向eNB发送PDCP SN110、PDCP SN120、PDCP SN130…PDCP SN200这10个数据包，eNB从LTE空口接收这些数据包。
本申请实施例中，“PDCP SN XX”，代表PDCP SN为“XX”的数据包。
802、eNB收到PDCP SN 110，在PDCP SN 110中增加X2序列号1，并向gNB发送处理后的数据包。
803、gNB收到PDCP SN 110，将gNB缓存的PDCP SN 110以前的数据包以及PDCP SN 110传递给核心网。
804、eNB收到PDCP SN 120，在PDCP SN 120中增加X2序列号2，并向gNB发送处理后的数据包。
805、gNB收到PDCP SN 120，gNB将缓存的PDCP SN 120以前的数据包以及PDCP SN 120传递给核心网。
806、eNB收到PDCP SN 130，在PDCP SN 130中增加X2序列号3，并向gNB发送处理后的数据包。PDCP SN 130在X2接口丢包了，未能到达gNB。
807、eNB继续在发送的数据包中增加X2序列号，并向gNB发送处理后的数据包，直到发送完10个数据包。
808、gNB收到数据包后发现缺失PDCP SN 130，开启定时器等待PDCP SN 130，并中止向核心网投递数据包。
809、eNB在发送完送PDCP SN110～PDCP SN200这10个数据包之后，向gNB 发送冗余信息。冗余信息包括PDCP SN110～PDCP SN200这10个数据包的X2序列号1～10，以及X2序列号1～10对应的10个PDCP SN，即110～200。
具体实现中，eNB可以解析数据包，从数据包中获取到数据包的PDCP SN，在冗余信息中增加数据包的PDCP SN。
eNB也可以拷贝数据包的头部3个字节填入冗余信息中相应的位置。参照PDCP协议(3GPP 36.323和3GPP 38.323)，PDCP SN存在于PDCP数据包的头部3个字节以内。本申请实施例对此不作限制，适用于PDCP协议的调整，可以相应调整拷贝的字节数。例如，PDCP协议规定PDCP SN存在于PDCP数据包的前4个字节，则拷贝PDCP数据包的前4个字节填充至冗余信息的相应位置。
另外，可以按照数据包数量进行周期性发送冗余信息，例如，eNB每发送10个数据包就发送一个冗余信息，携带这10个数据包的PDCP SN和X2序列号。
或者，按时间间隔周期性发送冗余信息，例如，间隔10ms发送一个冗余信息。
需要说明的是，第一节点可以根据网络的丢包概率和传输时延等因素设置不同的发送周期。其中，发送周期可以是N个数据包，也可以是时间间隔。
810、gNB根据冗余信息PDCP SN130报文是在X2接口丢失的数据包，则停止等待PDCP SN130的定时器，对缓存的其他除PDCP SN130以外的数据包进行重排序，并将重排序之后的数据包传递给核心网。
具体实现中，如果冗余信息中包括“130”这一PDCP SN，则表明eNB在X2接口向gNB发送了PDCP SN 130这一数据包，但是eNB与gNB之间出现丢包，gNB并未收到PDCP SN 130这一数据包。
依旧以NSA DC Option3x组网作为示例，假设eNB每隔多个数据包向gNB发送一个冗余信息，冗余信息的发送周期包括的数据包的数量可以大于冗余信息的PDCP SN的数量，即将冗余信息延后发送。示例的，冗余信息中包括6个数据包的PDCP SN，eNB完成8个数据包的发送之后，向gNB发送冗余信息。
一种可能的实现中，gNB维护了一个队列进行丢包监测，队列中以数据包的X2序列号标识数据包，并且队列指针指向的是待处理的数据包的X2序列号。具体的监测过程参考图8。如图8所示，eNB向gNB发送了X2序列号为1～8的数据包，gNB收到这8个数据包，队列指针滑动到9。eNB向gNB发送冗余信息1，包括X2序列号为1～6的数据包的PDCP SN，分别为110、120、130…160。gNB根据冗余信息1确定没有丢包。
接着，eNB向gNB发送了X2序列号为9～16的数据包，X2序列号为10的数据包在X2口丢失，gNB未收到X2序列号为10的数据包，队列指针指针停在10。eNB向gNB发送冗余信息2，包括X2序列号为7～12的数据包的PDCP SN，分别为170、180、190…230。gNB解析冗余信息2，获取到X2序列号为10的数据包对应的PDCP SN为1000。
如果当前已经开启了PDCP丢弃定时器，且该定时器是PDCP SN为1000的数据包触发的，即该定时器是为了等待PDCP SN号为1000的数据包，gNB则停止定时器，将PDCP SN号为1000以后的连续数据包传递给核心网；如果该定时器不是PDCP SN为1000的数据包触发的，则不启动新的定时器，等待PDCP SN号为1000的数据包。
可以理解的是，如果eNB在X2序列号为6的数据包之后立即发送完冗余信息1，假设X2序列号为6的数据包因传输乱序晚于冗余信息1到达gNB，则会引起一次错误的跳包动作，即gNB解析冗余信息1之后误以为X2序列号为6的数据包在X2口上丢失了，在重排序的时候跳过X2序列号为6的数据包，导致上层协议的误操作，例如，误认为X2序列号为6的数据包丢失，并进行业务层的重传。
当eNB在X2序列号为8的数据包完成发送之后，再发送完冗余信息1，假设X2序列号为6的数据包乱序，会在X2序列号为7的数据包之后到达gNB，仍然早于冗余信息1到达gNB，不会导致错误的跳包动作。
需要说明的是，冗余信息延后发送的程度可依据实际组网的乱序情况(例如，X2传输链路的时延，导致gNB接收到的数据包的X2序列号是错乱的)进行设置，如果乱序情况越严重，可以将延后的数据包数量设置的大一些，多延后几个数据包再发送冗余信息；如果乱序程度很低，可以将延后的数据包数量设置的小一些，少延后几个报文；如果确认网络上不会存在乱序，则可以不做状态报告的延后发送，即冗余信息的发送周期包括的数据包的数量可以等于冗余信息的PDCP SN的数量。
本申请实施例提供的方法，可以避免长时间等待丢失的数据包造成带宽的浪费，有利于特征通信性能。同时，可以解决X2口乱序导致的误操作问题，通过优化冗余信息的发送方式，提升了系统的容错性。
依旧以NSA DC Option3x组网作为示例，eNB还可以通过以下两种方式，解决冗余信息在X2口丢包带来的影响，具体包括：
第一种、eNB发送第j个冗余信息时，重复发送第j-1个冗余信息。
示例的，eNB在X2口向gNB发送X2序列号为1-10的数据包之后，向gNB发送冗余信息1，包括X2序列号为1-10的数据包对应的10个PDCP SN。
eNB在X2口向gNB发送X2序列号为11-20的数据包，发送冗余信息1以及冗余信息2，其中，冗余信息2包括X2序列号为11-20的数据包对应的10个PDCP SN。
eNB在X2口向gNB发送X2序列号为21-30的数据包，发送冗余信息2以及冗余信息3，其中，冗余信息3包括X2序列号为21-30的数据包对应的10个PDCP SN。
后续流程依次类推，本申请实施例不做赘述。
第二种、eNB重复发送冗余信息，直至收到gNB的确认信息。
示例的，eNB在X2口向gNB发送X2序列号为1-10的数据包之后，向gNB重复发送冗余信息1，包括X2序列号为1-10的数据包对应的10个PDCP SN。
eNB接收gNB发送的确认信息，确认信息用于确认gNB接收到了冗余信息1，eNB则停止发送冗余信息1。
需要说明的是，eNB可以根据X2口传输质量来决策选择上述第一或第二种方式发送冗余信息。如果传输质量稍差，X2口丢包率不高，则可采用第一种方式发送冗余信息；如果传输质量较差，X2口丢包率较高，则可采用第二种方式发送冗余信息。
本申请实施例提供的方法，可以避免长时间等待丢失的数据包造成带宽的浪费，有利于特征通信性能。同时，可以解决X2口丢包导致的问题，通过优化冗余信息的发送方式，提升了系统的容错性。
依旧以NSA DC Option3x组网作为示例，eNB根据X2口的发送顺序对数据包进 行编号，也不需要单独发送冗余信息，而是将冗余信息携带在其他数据包中发送给gNB。eNB在发送数据包时，随路附带之前发送的一个或多个数据包的PDCP SN。参考图4所示，可以在报文的扩展头填充随路附带的一个或多个PDCP SN。携带的PDCP SN的数量取决于传输质量。当传输质量较好，连续丢包的概率小，携带的PDCP SN的数量少一些；当传输质量较差，连续丢包的概率大，携带的PDCP SN的数量多一些。
示例的，参见图9(图示中数字为数据包的PDCP SN)，eNB发送的第一个数据包(即图中PDCP SN为1的数据包)不携带其他数据包的PDCP SN，gNB接收到PDCP SN为1的数据包之后，解析发现PDCP SN为1的数据包未携带其他数据包的PDCP SN，例如，数据包的扩展头为空，则按照现有流程处理，将连续的数据包传递给核心网。
gNB接收到第二个数据包，即图中PDCP SN为5的数据包，解析该数据包，在其扩展头获取到PDCP SN“1”，确认已接收到PDCP SN为1的数据包，继续按照现有流程处理，将连续的数据包传递给核心网。
gNB接收到第三个数据包，即图中PDCP SN为8的数据包，解析该数据包，在其扩展头获取到PDCP SN“3”，确认未接收到PDCP SN为3的数据包，启动定时器等待PDCP SN为3的数据包，暂停向核心网传递数据包。
gNB收到第四个报文，即图中PDCP SN为3的数据包，监测到等待PDCP SN为3的数据包的定时器正在运行，则终止该定时器。另外，解析PDCP SN为3的数据包，在其扩展头获取到PDCP SN“5”，确认已接收到PDCP SN为5的数据包。
PDCP收到第五个报文：即图中PDCP SN为12的数据包，解析该数据包，在其扩展头获取到PDCP SN“9”，确认未接收到PDCP SN为9的数据包，启动定时器等待PDCP SN为9的数据包，暂停向核心网传递数据包。在等待PDCP SN为9的数据包的定时器超时之后，构造虚包进行重排序，向核心网传递重排序之后的数据包。
本申请实施例提供的方法，可以避免长时间等待丢失的数据包造成带宽的浪费，有利于特征通信性能。同时，可以减少X2口的传输资源。通过更少的代价，解决了X2口乱序和丢包引起的PDCP重排序，导致带宽浪费的问题。
在采用对应各个功能划分各个功能模块的情况下，图10示出上述实施例中所涉及的通信装置的一种可能的结构示意图。图10所示的通信装置可以是本申请实施例所述的第一节点或第二节点，也可以是第一节点或第二节点中实现上述方法的部件，或者，也可以是应用于第一节点或第二节点中的芯片。所述芯片可以是片上系统(System-On-a-Chip，SOC)或者是具备通信功能的基带芯片等。如图10所示，通信装置包括处理单元1101以及通信单元1102。处理单元可以是一个或多个处理器，通信单元可以是收发器。
处理单元1101，用于支持第一节点或第二节点执行内部处理，例如，组装数据包；处理单元1101还用于支持第二节点(例如，gNB)执行步骤808，和/或用于本文所描述的技术的其它过程。
通信单元1102，用于支持该通信装置与其他通信装置之间的通信，例如，支持第一节点、第二节点执行步骤301和步骤302，支持第一节点执行步骤802、步骤804、步骤806、步骤807以及步骤809，和/或用于本文所描述的技术的其它过程。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应 功能模块的功能描述，在此不再赘述。
示例性的，在采用集成的单元的情况下，本申请实施例提供的通信装置的结构示意图如图11所示。在图11中，该通信装置包括：处理模块1201和通信模块1202。处理模块1201用于对通信装置的动作进行控制管理，例如，执行上述处理单元1101执行的步骤，和/或用于执行本文所描述的技术的其它过程。通信模块1202用于执行上述通信单元1102执行的步骤，支持通信装置与其他设备之间的交互，如与其他终端装置之间的交互。如图11所示，通信装置还可以包括存储模块1203，存储模块1203用于存储通信装置的程序代码和数据。
当处理模块1201为处理器，通信模块1202为收发器，存储模块1203为存储器时，通信装置为图2A所示的通信装置。
本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令；指令用于执行如图3所示的方法。
本申请实施例提供一种包括指令的计算机程序产品，当其在通信装置上运行时，使得通信装置执行如图3所示的方法。
本申请实施例一种无线通信装置，包括：无线通信装置中存储有指令；当无线通信装置在图2A、图2B、图10、图11所示的通信装置上运行时，使得通信装置执行如图3所示的方法。该无线通信装置可以为芯片。
本申请实施例还提供一种通信系统，包括：第一节点和第二节点。示例性的，第一节点可以是图2A、图10、图11所示的通信装置或是图2B所示的DU，第二节点可以是图2A、图10、图11所示的通信装置或是图2B所示的CU。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将数据库访问装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
本申请实施例中的处理器，可以包括但不限于以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。该处理器可以是个单独的半导体芯片，也可以跟其他电路一起集成为一个半导体芯片，例如，可以跟其他电路(如编解码电路、硬件加速电路或各种总线和接口电路)构成一个SoC(片上系统)，或者也可以作为一个ASIC的内置处理器集成在所述ASIC当中，该集成了处理器的ASIC可以单独封装或者也可以跟其他电路封装在一起。该处理器除了包括用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
本申请实施例中的存储器，可以包括如下至少一种类型：只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically erasable programmabler-only memory， EEPROM)。在某些场景下，存储器还可以是只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
本申请中，“至少一个”是指一个或者多个。“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
在本申请所提供的几个实施例中，应该理解到，所揭露的数据库访问装置和方法，可以通过其它的方式实现。例如，以上所描述的数据库访问装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，数据库访问装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (28)

  1. 一种冗余信息反馈方法，其特征在于，包括：
    第一节点向第二节点发送N个数据包，所述N个数据包中的每个数据包包括所述数据包的分组数据汇聚协议PDCP序列号SN，N为大于等于1的整数；
    所述第一节点向所述第二节点发送冗余信息，所述冗余信息包括N个PDCP SN，所述N个PDCP SN和所述N个数据包是一一对应的。
  2. 根据权利要求1所述的方法，其特征在于，所述N个数据包中的每个数据包还包括所述数据包的标识序号；
    所述冗余信息还包括N个标识序号，所述N个标识序号与所述N个PDCP SN是一一对应的。
  3. 根据权利要求2所述的方法，其特征在于，按照所述N个数据包的发送顺序，与所述N个数据包一一对应的所述N个标识序号是连续的。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述冗余信息是周期性发送的，所述冗余信息的发送周期小于PDCP丢弃定时器的时长。
  5. 根据权利要求4所述的方法，其特征在于，所述N个数据包为所述第一节点上一次向所述第二节点发送冗余信息后，所述第一节点向所述第二节点发送的。
  6. 根据权利要求5所述的方法，其特征在于，所述冗余信息还包括上一次发送的冗余信息。
  7. 根据权利要求4-6任一项所述的方法，其特征在于，所述方法还包括：所述第一节点从所述第二节点接收所述PDCP丢弃定时器的时长信息。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，
    所述第一节点发送所述冗余信息的时刻与所述第一节点完成所述N个数据包的发送的时刻之间相差第一阈值；或者，
    所述第一节点完成所述N个数据包的发送后，先发送一个或者多个其他数据包，再向所述第二节点发送所述冗余信息。
  9. 一种冗余信息反馈方法，其特征在于，包括：
    第二节点从第一节点接收M个数据包，所述M个数据包中的每个数据包包括所述数据包的分组数据汇聚协议PDCP序列号SN，M为大于等于1的整数；
    所述第二节点从所述第一节点接收冗余信息，所述冗余信息包括N个PDCP SN，N为大于等于1的整数，N大于等于M，所述N个PDCP SN包括与所述M个数据包一一对应的M个PDCP SN。
  10. 根据权利要求9所述的方法，其特征在于，所述M个数据包中的每个数据包还包括所述数据包的标识序号；
    所述冗余信息还包括N个标识序号，所述N个标识序号与所述N个PDCP SN是一一对应的。
  11. 根据权利要求9或者10所述的方法，其特征在于，所述冗余信息是周期性接收的，所述冗余信息的接收周期小于PDCP丢弃定时器的时长。
  12. 根据权利要求11所述的方法，其特征在于，所述M个数据包为所述第二节点上一次从所述第二节点接收冗余信息后，所述第二节点从所述第一节点接收的。
  13. 根据权利要求12所述的方法，其特征在于，所述冗余信息还包括上一次接收的冗余信息。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，向所述第一节点发送所述PDCP丢弃定时器的时长信息。
  15. 根据权利要求9-14任一项所述的方法，其特征在于，所述方法还包括：
    当所述第二节点确定未接收到所述冗余信息中的第一PDCP SN对应的数据包，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包，所述第一PDCP SN为所述N个PDCP SN中的一个PDCP SN。
  16. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    当所述第二节点根据所述M个数据包各自的标识序号的连续性确定未接收到第一标识序号对应的数据包，所述第一标识序号为所述N个标识序号中的一个标识序号，所述第一标识序号对应的PDCP SN为第一PDCP SN，则所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包。
  17. 根据权利要求15或者16所述的方法，其特征在于，所述第二节点进行PDCP重排序时，跳过所述第一PDCP SN对应的数据包，包括：
    若所述第一PDCP SN对应的数据包的PDCP丢弃定时器已开启，则停止所述第一PDCP SN对应的数据包的PDCP丢弃定时器；或者，
    若所述第一PDCP SN对应的数据包的PDCP丢弃定时器未开启，则放弃开启所述第一PDCP SN对应的数据包的PDCP丢弃定时器。
  18. 根据权利要求15-17任一项所述的方法，其特征在于，所述方法还包括：
    向核心网发送PDCP SN大于所述第一PDCP SN的数据包。
  19. 根据权利要求1-8任一项所述的方法，其特征在于，所述N个数据包为第一数据无线承载的数据包，所述第一数据无线承载的无线链路控制RLC层在所述第一节点，所述第一数据无线承载的PDCP层在所述第二节点。
  20. 根据权利要求9-18任一项所述的方法，其特征在于，所述M个数据包为第一数据无线承载的数据包，所述第一数据无线承载的无线链路控制RLC层在所述第一节点，所述第一数据无线承载的PDCP层在所述第二节点。
  21. 根据权利要求19或者20所述的方法，其特征在于，所述第一数据无线承载为主节点MN终结的辅小区组SCG承载，或，主节点MN终结的分流承载，或辅节点SN终结的主小区组MCG承载，或，SN终结的分流承载。
  22. 根据权利要求19或者20所述的方法，其特征在于，所述第一节点为分布单元DU，所述第二节点为集中CU。
  23. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器耦合；
    存储器，用于存储计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1至22中任一项所述的方法。
  24. 一种计算机可读存储介质，包括程序或指令，当所述程序或指令被处理器运行时，如权利要求1至22中任意一项所述的方法被执行。
  25. 一种计算机程序产品，其特征在于，所述计算机程序产品包括指令，当所述指令 被运行时，使得如权利要求1至22任一项所述的方法被执行。
  26. 一种装置，其特征在于，所述装置用于执行权利要求1-22任一项所述的方法。
  27. 一种芯片，其特征在于，所述芯片包括处理器和接口电路，所述接口电路和所述处理器耦合，所述处理器用于运行计算机程序或指令，使得如权利要求1至22任一项所述的方法被执行。
  28. 一种通信系统，其特征在于，所述通信系统包括用于执行权利要求1至8任一项方法所述的第一节点和权利要求9至22任一项方法所述的第二节点。
PCT/CN2020/094735 2019-06-05 2020-06-05 一种冗余信息反馈方法及通信装置 Ceased WO2020244642A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910488397.6A CN110278058B (zh) 2019-06-05 2019-06-05 一种冗余信息反馈方法及通信装置
CN201910488397.6 2019-06-05

Publications (1)

Publication Number Publication Date
WO2020244642A1 true WO2020244642A1 (zh) 2020-12-10

Family

ID=67960542

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094735 Ceased WO2020244642A1 (zh) 2019-06-05 2020-06-05 一种冗余信息反馈方法及通信装置

Country Status (2)

Country Link
CN (1) CN110278058B (zh)
WO (1) WO2020244642A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278058B (zh) * 2019-06-05 2020-11-03 华为技术有限公司 一种冗余信息反馈方法及通信装置
CN114600499B (zh) * 2019-10-03 2026-01-20 捷开通讯(深圳)有限公司 集成接入与回传的用户界面
CN112770267B (zh) * 2019-10-21 2022-05-13 华为技术有限公司 一种通信方法、装置和系统
CN112804037B (zh) * 2021-03-23 2021-06-29 四川创智联恒科技有限公司 一种pdcp层数反馈方法
CN113316190B (zh) * 2021-05-10 2023-08-01 上海仝心电子科技有限公司 一种智慧云盒及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106101108A (zh) * 2016-06-15 2016-11-09 贵阳朗玛信息技术股份有限公司 媒体数据包的发送、恢复方法及装置
US20170288821A1 (en) * 2016-03-29 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in a communication system
CN107359968A (zh) * 2016-05-10 2017-11-17 电信科学技术研究院 一种单层序列号的数据传输方法及装置
CN108632899A (zh) * 2017-03-17 2018-10-09 华为技术有限公司 一种数据传输方法、数据发送设备及数据接收设备
WO2018237001A1 (en) * 2017-06-20 2018-12-27 Intel IP Corporation DEVICES AND METHODS FOR TRIGGERING FLOW CONTROL AND INFORMATION RETURN
CN110278058A (zh) * 2019-06-05 2019-09-24 华为技术有限公司 一种冗余信息反馈方法及通信装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100571107C (zh) * 2005-10-10 2009-12-16 华为技术有限公司 一种数据包丢失的检测方法和检测装置
CN101127763B (zh) * 2006-09-07 2011-06-22 中兴通讯股份有限公司 一种传输信令二层对等适配层序号恢复同步的方法
JP4250654B2 (ja) * 2006-11-17 2009-04-08 株式会社東芝 通信装置、通信方法および通信プログラム
KR101345944B1 (ko) * 2007-03-02 2013-12-27 삼성전자주식회사 무선 통신 시스템에서 패킷 재전송을 요청하는 장치 및방법
CN100571217C (zh) * 2007-09-19 2009-12-16 腾讯科技（深圳）有限公司 一种在数据传输过程中抵抗丢包的方法、收发装置及系统
CN102025717B (zh) * 2010-09-10 2013-09-11 香港城市大学深圳研究院 一种传输多媒体数据的方法
CN104519524A (zh) * 2013-09-26 2015-04-15 中兴通讯股份有限公司 一种基于多流传输的数据排序方法及接收装置
CN109348508B (zh) * 2013-11-11 2022-04-12 华为技术有限公司 数据传输方法及装置
CN103684923B (zh) * 2013-12-24 2017-10-17 华为技术有限公司 一种丢包测量的方法及网络设备
CN104243097A (zh) * 2014-09-19 2014-12-24 东软集团股份有限公司 基于卫星网络的数据传输方法及系统
CN108540273B (zh) * 2017-03-01 2021-08-13 杭州海康威视数字技术股份有限公司 一种数据包重传的方法和装置
CN107104760B (zh) * 2017-04-13 2020-09-08 腾讯科技（深圳）有限公司 一种传输数据包的方法、客户端以及服务器

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170288821A1 (en) * 2016-03-29 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in a communication system
CN107359968A (zh) * 2016-05-10 2017-11-17 电信科学技术研究院 一种单层序列号的数据传输方法及装置
CN106101108A (zh) * 2016-06-15 2016-11-09 贵阳朗玛信息技术股份有限公司 媒体数据包的发送、恢复方法及装置
CN108632899A (zh) * 2017-03-17 2018-10-09 华为技术有限公司 一种数据传输方法、数据发送设备及数据接收设备
WO2018237001A1 (en) * 2017-06-20 2018-12-27 Intel IP Corporation DEVICES AND METHODS FOR TRIGGERING FLOW CONTROL AND INFORMATION RETURN
CN110278058A (zh) * 2019-06-05 2019-09-24 华为技术有限公司 一种冗余信息反馈方法及通信装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION.: "Flow control enhancements for X2.", 3GPP TSG RAN WG3 NR#2 ADHOC, R3-172296., 29 June 2017 (2017-06-29), XP051302243, DOI: 20200819165814A *

Also Published As

Publication number Publication date
CN110278058A (zh) 2019-09-24
CN110278058B (zh) 2020-11-03

Similar Documents

Publication Publication Date Title
CN110278058B (zh) 一种冗余信息反馈方法及通信装置
US12034539B2 (en) Block acknowledgment operation for multi-link WLAN
EP3528409B1 (en) Method and system for improving wireless link efficiency
EP4542905A2 (en) Switching between packet duplication operating modes
CN118511645A (zh) 下一代移动通信系统中支持小区组激活或去激活的报头压缩或解压缩过程的方法和设备
CN114189901A (zh) 一种数据接收状态报告方法及装置
US11134518B2 (en) Cooperative multi-band operation schemes in wireless local area networks
CN108809540B (zh) 数据处理方法及设备
WO2017185941A1 (zh) 一种数据传输方法及相关设备
KR20190097963A (ko) 무선 통신 시스템에서 데이터 송수신 방법 및 장치
WO2021208863A1 (zh) 数据传输方法及通信装置
WO2024199047A1 (zh) 一种通信方法及装置
EP3790213B1 (en) Mac-based hybrid automatic repeat request (harq)
CN115968003A (zh) 一种数据传输方法及通信装置
JP7673811B2 (ja) 基地局及び無線端末装置
WO2025112835A1 (zh) 一种容错数据传输的方法和通信装置
TWI852131B (zh) 執行上行鏈路資料壓縮的方法和使用者設備
WO2020101807A2 (en) Methods and apparatus aggregating multiple wireless communications channels for flexible full-duplex communications
US12494869B2 (en) Burst transmission of data packets with feedback
WO2022218314A1 (zh) 信息处理方法、终端、芯片及存储介质
CN113950812B (zh) 超低有限延迟的多无线媒体接入控制
WO2021134106A2 (en) Methods and apparatus for efficient packet transmission
CN120812772B (zh) 通信方法及通信装置
US20260046674A1 (en) Method and device for reporting multiple pieces of delay status information in wireless communication system
RU2780218C1 (ru) Способ отправки данных с помощью двух базовых станций 5g new radio

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

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

Country of ref document: EP

Kind code of ref document: A1