WO2011020233A1 - 多跳中继通信系统中对下行数据传输控制的方法和装置 - Google Patents
多跳中继通信系统中对下行数据传输控制的方法和装置 Download PDFInfo
- Publication number
- WO2011020233A1 WO2011020233A1 PCT/CN2009/073308 CN2009073308W WO2011020233A1 WO 2011020233 A1 WO2011020233 A1 WO 2011020233A1 CN 2009073308 W CN2009073308 W CN 2009073308W WO 2011020233 A1 WO2011020233 A1 WO 2011020233A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet data
- convergence protocol
- protocol layer
- data convergence
- rlc
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 55
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000004891 communication Methods 0.000 title claims abstract description 7
- 238000012384 transportation and delivery Methods 0.000 claims abstract description 36
- 239000000872 buffer Substances 0.000 claims description 10
- 238000012790 confirmation Methods 0.000 claims description 5
- 230000007246 mechanism Effects 0.000 claims description 4
- 230000002776 aggregation Effects 0.000 claims 1
- 238000004220 aggregation Methods 0.000 claims 1
- 230000001360 synchronised effect Effects 0.000 abstract description 4
- 230000000875 corresponding effect Effects 0.000 description 60
- 101100476985 Schizosaccharomyces pombe (strain 972 / ATCC 24843) sdu1 gene Proteins 0.000 description 20
- 238000010586 diagram Methods 0.000 description 7
- 230000011218 segmentation Effects 0.000 description 5
- 230000003139 buffering effect Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 238000009432 framing Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000002596 correlated effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008713 feedback mechanism Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1874—Buffer management
-
- 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/1809—Selective-repeat protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1835—Buffer management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
- H04L1/1614—Details of the supervisory signal using bitmaps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
- H04L1/1621—Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers
-
- 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
- H04L2001/0092—Error control systems characterised by the topology of the transmission link
- H04L2001/0097—Relays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
Definitions
- the present invention relates to the field of communications, and in particular, to a method and apparatus for controlling downlink data transmission in a multi-hop relay communication system. Background technique
- multi-hop relay is adopted as the key technology for next-generation mobile networks.
- Relay Node such as a relay station (RS)
- RS relay station
- Layer problem For example, the relay station works at the network layer (that is, layer 3 relay, L3 relay), or works at the data link layer.
- the mobile terminal When a handover occurs, the mobile terminal still requires data transmission in sequence, so the downlink data buffered in the source base station or the relay station should be forwarded to the destination base station or relay station.
- the sequential transmission means that the order in which the receiving end delivers the data packet to the upper layer is the same as the order in which the transmitting end receives the data packet from the upper layer, and the order in which the transmitting end receives the data packet from the upper layer is the serial number of the data packet.
- the Packet Data Convergence Protocol (PDCP) is used to ensure the sequential transmission of downlink data.
- PDCP Packet Data Convergence Protocol
- the source base station sequentially forwards all the SDUs or PDUs of the downlink PDCP layer that are not confirmed by the terminal to the target base station, and the source base station will pass the S1 interface (the interface between the MME/S-GW network management system and the base station).
- S-GW Serving Gateway
- the scheme of relaying the RLC layer (RLC at layer 2, layer 2) is favored by many proposals.
- the so-called RLC layer relay that is, the relay station is a layer 2 device, and the relay station can provide services of the RLC layer, the MAC layer, and the PHY layer.
- the RLC layer relay if the original 3GPP mechanism is used, the sequential transmission of the downlink data may be destroyed at the time of handover.
- FIG. 1 is a schematic diagram showing a downlink data transmission scheme based on RLC layer relay in the prior art.
- Figure 1 shows the retransmission of hop-by-hop feedback retransmission (ARQ).
- ARQ hop-by-hop feedback retransmission
- the PDCP entity lb in the base station 1 provides a PDCP layer PDU to its lower layer RLC entity la.
- the RLC entity la of the base station 1 segments or connects the PDCP PDU to encapsulate one or more RLC PDUs, and provides the one or more RLC PDUs to the peer entity in the relay station 2a in step S11. That is, the RLC entity in the relay station 2a.
- the relay station 2a When the relay station 2a receives the one or more RLC PDUs, the relay station 2a transmits a corresponding positive acknowledgment message (ACK) or a negative acknowledgment message (NACK) to the RLC entity 1a of the base station 1 in step S12, and the retransmission ARQ mechanism is It is known to those skilled in the art. I will not repeat them here.
- ACK positive acknowledgment message
- NACK negative acknowledgment message
- the RLC entity la of the base station 1 After the RLC entity 1a of the base station 1 receives the ACK of all the RLC PDUs corresponding to one complete RLC SDU fed back by the relay station 2a, in step 13, the RLC entity la of the base station 1 provides an indication to the PDCP entity 1b of the base station 1 Information (indication), the indication information is used to indicate that the PDCP entity lb of the base station 1 discards the PDCP SDU corresponding to the RLC Service Data Unit (SDU).
- dication indication
- step S14 the PDCP entity lb of the base station 1 discards the PDCP SDU corresponding to the RLC SDU, and further, if the PDCP PDU is buffered in the PDCP entity lb of the base station 1, the PDCP entity of the base station 1 is further included in step S14. Lb discards the PDCP PDU corresponding to the RLC SDU. Then, in step S15, the RLC entity of the relay station 2a re-segmentes or re-synthesizes the received RLC SDU, and wishes to transmit the corresponding RLC PDU to the mobile terminal 3 in step S16. However, in FIG.
- step S16 is a dotted line, and there is a cross at the top, indicating that a handover occurs at this time, that is, the relay station 2a is not
- the RLC PDU is transmitted to the mobile terminal 3, and step S16 does not actually occur.
- step S17 the PDCP entity of the mobile terminal 3 does not receive the PDCP SDU.
- step S14 the PDCP entity lb of the base station 1 has discarded the PDCP SDU, resulting in the loss of the PDCP SDU during the handover.
- the foregoing handover includes handover within a cell, such as handover between a base station and a relay station under the jurisdiction of the base station, or handover of a mobile terminal between different relay stations under the jurisdiction of the same base station, including a cell Inter-switching, such as handover of a mobile terminal between different base stations (or relay stations under its jurisdiction).
- a cell Inter-switching such as handover of a mobile terminal between different base stations (or relay stations under its jurisdiction).
- step S15 may also occur before or between steps S12-S14.
- the PDCP entity lb of the base station 1 deletes the corresponding PDCP SDU after the PDCP PDU transmitted by the base station 1 is successfully received by the relay station 2a. However, at this time, the UE may not have received the PDCP SDU. If the UE switches at this time, all of these PDCP SDUs that have been successfully received by the relay but have not been successfully received by the mobile terminal will be lost.
- the relay station has a PDCP layer, so the PDCP entity in the relay station ensures the sequential transmission of the line data at the time of handover. Then, the PDCP SDU is buffered in the PDCP buffer of the relay station, and therefore, the PDCP SDU is not lost during the handover.
- the entry of the tunnel that forwards the PDCP SDU that is not transmitted to the mobile terminal to the target base station is a relay station, and therefore, the PDCP SDU that is not transmitted to the mobile terminal and the new data are first transmitted from the source base station to the relay station, and then the relay station is tunneled to The target base station, thus wasting valuable radio resources and also increases the switching time.
- Layer 3 trunks need to forward IP packets, and for some IP applications with a small payload size, IP header overhead is too large, such as VoIP services, messaging, and interactive games.
- Another example is the relay below the RLC layer. Since the RLC entity is responsible for ARQ retransmission, and the RLC entity is not included in the relay station below the RLC layer, an end-to-end ARQ is performed between the base station and the mobile terminal. Therefore, until the PDCP SDU is successful When the base station forwards to the mobile terminal, and the base station receives the ACK message from the mobile terminal, the base station discards the PDCP SDU.
- the size of its ARQ window is K times that of the single-hop ARQ retransmission scheme. Therefore, the existing SN length of the RLC PDU defined in 3GPP rel8 It may not be long enough.
- end-to-end ARQ retransmission limits downlink throughput because retransmission always starts from the base station; further, the segmentation is performed at the RLC layer, and the upper layer packet can be segmented to fit the MAC layer packet.
- the size, if there is no RLC entity, will lose the flexibility of scheduling.
- the hop-by-hop NACK feedback mechanism there is also a problem that the ARQ window size is large, causing the problem that the RLC SN length defined in 3GPP rel 8 may not be sufficient, and limiting the throughput of the network.
- the sender may not retransmit the RLC PDU. Therefore, it is necessary to design a mechanism for state synchronization of the two ends when the NACK message is lost, which will cause delay and downlink data transmission overhead.
- the mapping between RLC PDUs received by the relay station and the transmitted RLC PDUs needs to be maintained in the relay station, thus requiring additional complexity and buffer space. Summary of the invention
- the present invention proposes a method and apparatus.
- the RLC entity of the base station when the next hop network device of the base station is a relay station, receives the acknowledgement message from the access relay station for confirming that the at least one PDCP PDU has been delivered to the terminal of the mobile terminal. And sending an indication message to the PDCP entity of the base station, where the PDCP entity that triggers the base station discards the PDCP SDU corresponding to the at least one PDCP PDU.
- a terminal delivery acknowledgement message is generated when the access relay station receives a positive acknowledgment message from the mobile terminal for all RLC PDUs corresponding to the at least one PDCP PDU.
- the status information of whether the buffered RLC SDU between the relay station and the base station is confirmed can be synchronized in an implicit manner.
- a method for controlling downlink data transmission in a base station wherein the base station communicates with a mobile terminal via one or more relay stations, comprising the steps of: Road control layer to the path to the mobile terminal
- the upper relay station transmits the respective radio link control layer PDUs corresponding to the one or more packet data convergence protocol layer PDUs; and determines, at the radio link control layer, whether the terminal delivery acknowledgement message is received, where the terminal
- the acknowledgement message is sent to confirm that at least one of the one or more packet data convergence protocol layer PDUs has been delivered to the mobile terminal; after the radio link control layer receives the terminal acknowledgement message,
- the radio link control layer sends the indication information to the packet data convergence protocol layer, where the indication information is used to indicate that the packet data convergence protocol layer discards the cache corresponding to the at least one packet data convergence protocol layer SDU/PDU.
- Packet data convergence protocol layer SDU Packet data convergence protocol layer SDU;
- a method for assisting a base station to control downlink data transmission in a relay station includes the following steps: Transmitting, by the convergence protocol layer PDU, each radio link control layer PDU to the mobile terminal; determining whether the mobile terminal is received from the mobile terminal and corresponding to at least one of the one or more packet data convergence protocol layer PDUs a positive acknowledgement message of each radio link control layer PDU; when receiving the positive acknowledgement message, sending a terminal acknowledgement message to the base station, wherein the terminal acknowledgement message is used to confirm the at least one A packet data convergence protocol layer PDU has been delivered to the mobile terminal.
- FIG. 1 shows a schematic diagram of a downlink data transmission scheme based on RLC layer relay in the prior art
- FIG. 2 is a schematic diagram showing a downlink data transmission scheme based on RLC layer relay according to an embodiment of the present invention
- FIG. 3 is a schematic diagram showing a downlink data transmission scheme based on RLC layer relay, which is an example of transmission of two RLC SDUs according to an embodiment of the present invention
- FIG. 4 is a block diagram of an apparatus for an RLC layer relay based downlink data transmission scheme in accordance with an embodiment of the present invention.
- FIG. 2 there is shown a schematic diagram of a downlink data transmission scheme in accordance with an embodiment of the present invention.
- 2 shows a base station 1 and two relay stations 2a and 2b, wherein the relay station 2a is an intermediate relay station, the relay station 2a is a first hop relay station on the downlink, and the relay station 2b is an access relay station (access Relay sataion ), relay station 2b is the second hop relay station on the downlink, that is, the relay station closest to mobile terminal 3.
- the relay station 2b directly communicates with the mobile station 3.
- step S200 the PDCP entity 1b of the base station 1 transmits a PDCP PDU to the RLC entity 1a of the base station 1.
- the interaction of the information shown by the dashed lines following the arrow in step 200 is done by entities between different layers within the base station. Specifically, at the PDCP layer, the PDCP entity 1b of the base station 1 acquires the data packet transmitted by the IP layer, performs header compression based on, for example, the ROHC algorithm, and sequentially encapsulates the IP data packet in the order of transmission of the IP data packet, and puts the PDCP PDU header.
- the sequence number of the PDCP PDU is added in order, the serial number of the PDCP PDU is also sequentially increased, and data encryption is performed to finally form the RLC entity of the PDCP PDIL base station 1
- the PDCP layer lb from the upper layer, that is, the PDCP layer lb
- the PDCP PDUs are sequentially segmented and/or concatenated to generate sequential RLC PDUs corresponding to one or more PDCP PDUs.
- the information from the MAC layer may be based on radio resources allocated on the link between the base station 1 and the relay station 2a, such as time-frequency resources allocated for the link and transmission characteristics of the link such as link quality, and/or different The priority between the business is generated.
- the RLC entity la of the base station 1 transmits each RLC PDU corresponding to one or more PDCP PDUs to the next-level relay station on the path to the mobile terminal 3.
- the RLC entity la of the base station 1 transmits to the RLC entity of the relay station 2a the respective RLC PDUs corresponding to the one or more PDCP PDUs.
- the PDCP entity lb of the base station 1 can also cache the acquired PDCP SDU. There is no obvious relationship between the step of the buffering and the step of the RLC layer transmitting the RLC PDU to the relay station 2a.
- the PDCP entity lb may first transmit the PDCP PDU to the RLC entity 1a, and the RLC entity la splits/splices the PDCP PDU into one or After the multiple RLC PDUs are sent to the UE, the PDCP entity lb buffers the PDCP PDUs in order; or the PDCP entity lb first buffers the PDCP SDUs in order, and after the PDCP entity lb transmits the PDCP PDUs to the RLC entity la, the RLC entity la then disassembles the PDCP PDUs. Open/splicing into one or more RLC The PDU is sent to the UE.
- step S202 the RLC entity of the relay station 2a transmits an ACK corresponding to each RLC PDU transmitted by the RLC entity 1a of the base station 1 to the peer entity of the base station 1, that is, the RLC entity 1a of the base station 1, the specific ACK.
- the feedback process of /NACK is the same as that in the prior art, and therefore, it will not be described here.
- the relay station 2a may, based on the information of the MAC layer from the relay station 2a, for example, the received RLC from the base station 1 according to the size of the transmission block (TB) indicated by the MAC layer of the relay station 2a.
- One or more RLC SDUs of entity la are sequentially re-segmented and/or concatenation to generate sequential RLC PDUs corresponding to one or more RLC SDUs.
- the information from the MAC layer may be based on radio resources allocated on the link between the relay station 2a and the relay station 2b, such as time-frequency resources allocated for the link, and transmission characteristics of the link such as link quality, and / Or the priority between different businesses is generated.
- the resource allocation and/or transmission characteristics of the radio link between the base station 1 and the relay station 2a are likely to be different from the resource allocation and/or transmission characteristics of the radio link between the relay station 2a and the relay station 2b. Therefore, the RLC entity of the relay station 2a is also different in size from the RLC SDU segment size and the size of the segment of the RLC entity la of the base station 1 to the SDU of the RLC.
- step S204 the relay station 2a transmits a re-segmented and/or spliced RLC PDU corresponding to one or more RLC SDUs to the relay station 2b.
- step S205 the RLC entity of the relay station 2b transmits an ACK/NACK corresponding to each RLC PDU transmitted by the RLC entity of the relay station 2a to the RLC entity of the relay station 2a.
- the relay station 2b may, based on the information of the MAC layer from the relay station 2b, for example, the received RLC from the relay station 2a according to the size of the transmission block (TB) indicated by the MAC layer of the relay station 2b.
- One or more RLC SDUs of the entity are sequentially re-segmented and/or concatenated to generate respective RLC PDUs in sequence corresponding to one or more RLC SDUs.
- the relay station 2b transmits re-segmented and/or spliced respective RLC PDUs corresponding to one or more RLC SDUs to the mobile terminal 3.
- step S208 the access relay station 2b receives an ACK/NACK corresponding to each RLC PDU transmitted from the RLC entity of the relay station 2b, which is fed back from the mobile terminal 3.
- step S209 the relay station 2b judges whether or not the ACK of each RLC PDU corresponding to the RLC SDU from the mobile terminal 3 is received, that is, the relay station 2b judges whether or not all the RLCs corresponding to the RLC SDU from the mobile terminal 3 are received.
- ACK message of the PDU The RLC header of the RLC PDU includes indication information for indicating that the data portion of the RLC PDU includes several RLC SDUs or RLC SDU segments, and an end position of each RLC SDU or RLC SDU segment. Based on the above information, the RLC entity of the relay station 2b can determine when all RLC PDUs corresponding to a complete RLC SDU are received.
- the relay station 2b When the relay station 2b determines in step S210 that the ACK of each RLC PDU corresponding to the RLC SDU is received, the relay station 2b transmits a terminal service acknowledgement message (User Equipment Delivery Acknowlegment) to the relay station 2a, wherein the terminal delivers the acknowledgement message It is used to confirm that the RLC SDU has been delivered to the mobile terminal 3.
- the RLC SDU is a PDCP PDU.
- the RLC SDU is exchanged between the RLC entity and the PDCP entity
- the PDCP PDU is exchanged between the PDCP entity and the PDCP entity.
- step S211 the relay station 2a transmits the terminal delivery acknowledgement message to the RLC entity la of the base station 1.
- step S212 after the RLC entity 1a of the base station 1 receives the terminal acknowledgement message, the RLC entity 1a of the base station 1 sends indication information to the PDCP entity 1b of the base station 1, the indication information is used to indicate that the PDCP entity lb is discarded.
- the interaction of the indicated indication information indicated by the dashed line following the arrow in the PDCP SDIL step 212 of the buffer is performed by an entity between different layers inside the base station.
- the PDCP entity lb of the base station 1 discards the cache by the PDCP SDIL corresponding to the RLC SDU confirmed by the terminal acknowledgement message.
- the PDCP SDU is pure data information that is not encrypted, and the PDCP PDU is the data packet after the PDCP SDU is encrypted. Since the data encryption algorithms of the respective base stations are different, generally, the PDCP SDU is buffered in the base station, and at the time of handover, the source base station transmits the unencrypted PDCP SDU to the target base station.
- the step S211 further includes: deleting the PDCP PDU confirmed by the terminal delivery acknowledgement message from the cache.
- step S300 the PDCP entity lb of the base station 1 transmits two RLC SDUs to the RLC entity la of the base station 1, which are RLC SDU1 and RLC SDU2, respectively.
- the sequence number of the RLC SDU1 is smaller than the sequence number of the RLC SDU2. Therefore, in the subsequent segmentation and concatenation operations of each relay station, each relay station needs to ensure that the RLC SDU1 is always sorted before the RLC SDU2.
- the RLC SDU1 is indicated by a diagonal line to distinguish it from the RLC SDU2.
- the RLC entity la of the base station 1 is based on the information from the MAC layer of the base station 1, for example, according to the size of the Transmission Block (TB) indicated by the MAC layer and in the order of the sequence number (SN) of the PDCP PDU from the upper layer. That is, the PDCP PDU of the PDCP layer lb of the base station 1 is sequentially segmented and/or concatenation to generate three RLC PDUs, namely PI, P2 and P3.
- the RLC entity la of the base station 1 combines the first segment of the RLC SDU1 into the data portion of the RLC PDU P1, and splicing the last segment of the RLC SDU1 and the first segment of the RLC SDU2 into the data of the RLC PDU P2.
- the last segment of the RLC SDU 2 is formed into the data portion of the RLC PDU P3.
- the RLC header portion of each RLC PDU includes length information for indicating each RLC SDU segment included in the data portion of the RLC PDU, that is, a Length Indicator field, and further includes a data field for indicating the RLC PDU.
- step S301 the RLC entity la of the base station 1 sequentially transmits the RLC PDUs P1, P2, and P3 to the relay station 2a.
- step S302 when the relay station 2a passes the CRC check or the like to verify that the PI, P2 and P3 are successfully received, the RLC entity of the relay station 2a transmits the RLC entity la of the base station 1 to the RLC entity la of the base station 1 ACK corresponding to each RLC PDU PK P2 and P3.
- the relay station 2a may adopt a Stop-and-Wait (SAW) ARQ scheme, or may adopt a Go-Back-N ARQ scheme or a selective retransmission ARQ scheme to send an ACK message.
- SAW Stop-and-Wait
- the order of the RLC PDUs PI, P2 and P3 from the peer RLC entity la of the base station 1 correctly received by the RLC entity of the relay station 2a may be out of order, for example, the RLC entity of the relay station 2a first correctly receives the RLC SDU2 The corresponding RLC PDUs P2 and P3, because the check RLC PDU P1 is incorrect, the base station 1 is required to retransmit the RLC PDU P1, so the relay station 2a receives the RLC PDU P1 corresponding to the RLC SDU1.
- the RLC entity of the relay station 2a needs to reorder the received RLC PDUs, so that the reordered RLC PDUs are sequentially incremented according to the sequence number of the RLC PDUs, that is, in the order of increasing the sequence numbers of the RLC SDUs, That is, the order of RLC PDU1, PDU2, and PDU3.
- the order of the RLC PDUs received by the relay station 2a has been sequentially increased in the order of the SNs of the RLC PDUs, the above-described reordering steps may be omitted.
- the relay station 2a sequentially, according to the information of the MAC layer from the relay station 2a, sequentially, according to the size of the transport block (TB) indicated by the MAC layer, sequentially the RLC PDUs from the RLC entity la of the base station 1 are sequentially arranged. Segmentation and/or concatenation are performed to generate 5 RLC PDUs, namely ⁇ , ⁇ 2, ⁇ 3, ⁇ 4, and ⁇ 5.
- the RLC entity of the relay station 2a forms the first segment of the RLC SDU1 into the data portion of the RLC PDU
- the second segment of the RLC SDU1 constitutes the data portion of the RLC PDU P2
- the last one of the RLC SDU 1 Segmentation constitutes the data portion of the RLC PDU P3', which will be the first of the RLC SDU2
- the segments form the data portion of the RLC PDU P4'
- the last segment of the RLC SDU 2 constitutes the data portion of the RLC PDU P5'.
- the transmission characteristics of resources and links on the radio link between the base station 1 and the relay station 2a are different from the transmission characteristics of resources and links on the radio link between the relay station 2a and the relay station 2b. Therefore, the same RLC SDU1 and RLC SDU2 are different in the number of RLC PDUs divided by the RLC entity la of the base station and the number of RLC PDUs divided by the RLC entity of the relay station 2a.
- step S303 the relay station 2a transmits the re-segmented 5 RLC PDUs P, P2, P3, P4, and P5 to the relay station 2b.
- step S304 when the relay station 2b passes the CRC check or the like, and the verification succeeds in receiving ⁇ , ⁇ 2, ⁇ 3, ⁇ 4, and ⁇ 5, the RLC entity of the relay station 2b transmits the relay station 2a to the RLC entity of the relay station 2a.
- the relay station 2b sequentially performs the RLC PDUs of the RLC entities from the relay station 2a sequentially arranged according to the information of the MAC layer from the relay station 2b, for example, according to the size of the transmission block (TB) indicated by the MAC layer. Segmentation and/or concatenation to generate 3 RLC PDUs, ⁇ , ⁇ 2" and ⁇ 3". That is, the RLC entity of the relay station 2b combines all the RLC SDU1s into the data portion of the RLC PDU P1 ", the first segment of the RLC SDU2 constitutes the data portion of the RLC PDU P2", and the last segment of the RLC SDU2 constitutes the RLC. The data portion of the PDU P3". Therefore, in step S305, the relay station 2b transmits the re-segmented 3 RLC PDUs P1 ", P2" and P3" to the mobile terminal 3.
- step S306 the mobile terminal 3 checks the discovery error for the RLC PDU P1, and does not find an error for the P2" and P3" check. Therefore, the RLC entity of the mobile terminal 3 transmits to the RLC entity of the relay station 2b. P2 "and P3" ACK, ⁇ , NACK.
- step S307 the RLC entity of the relay station 2b retransmits the RLC PDU ⁇ .
- step S308 the mobile terminal 3 passes the check to find that the received RLC PDU P1 is "correct”, then the RLC entity of the mobile terminal 3 sends the RLC entity of the relay station 2b to the RLC entity of the relay station 2b.
- RLC PDU P1,, ACK the RLC entity of the relay station 2b
- an implicit RLC SDU indication may be employed. That is, the sequence number of the explicit RLC PDU is not required to be included in the terminal delivery message.
- the list sorts all unconfirmed RLC SDUs in order of increasing SNs of the RLC PDUs.
- the order of arrangement of the RLC SDUs is the same as the order of the PDCP layer lb buffer PDCP SDU of the base station 1.
- the PDCP layer 1b of the base station 1 maintains a list of buffered PDCP SDUs in the order of IP data packets acquired from the upper layer of the PDCP layer of the base station, that is, the IP layer.
- the RLC layer 1a of the base station also sequentially transmits the PDCP transmitted by the PDCP layer.
- the PDUs are grouped to generate RLC PDUs. Therefore, the list of the base stations 1 coincides with the order in the relay station 2b, and the starting positions are identical. Therefore, although the serial number of the RLC PDU is different from the serial number of the PDCP PDU, their order is the same. Therefore, the implicit relay station 2b that does not need the SN including the RLC PDU can be implemented by the first RLC SDU defined in the list of the relay station 2b being the first RLC SDU that has not been confirmed by the terminal acknowledgement message. Whether the RLC SDU between the base stations 1 is successfully synchronized with the information of the mobile terminal.
- the relay station 2b when the relay station 2b receives the RLC PDUs ⁇ , ⁇ 2, ⁇ 3, ⁇ 4, and ⁇ 5 from the relay station 2a, it first marks the corresponding RLC SDU1 and RLC SDU 2 as unacknowledged delivery terminals. , ie, UE unacknowlegement.
- the RLC SDU1 is the first unacknowledged PDCP PDU from the order of transmission by the base station
- the RLC SDU2 is the second unacknowledged PDCP PDU from the order of transmitting by the base station.
- the RLC SDU1 and the RLC SDU2 represent two PDCP PDUs that are consecutive in order of transmission from the base station starting from the first unacknowledged PDCP PDU in the order in which the base station transmits.
- the relay station 2b confirms receipt of all RLC PDUs corresponding to the RLC SDU1 and the RLC SDU 2 from the mobile terminal 3, that is, the relay station 2b receives the confirmation message of the RLC PDU ⁇ , ⁇ 2" and ⁇ 3" Thereafter, according to the Framing Indication included in the header of the RLC PDU, the relay station 2b knows that the first byte of the data portion of the RLC PDU is corresponding to an RLC.
- the first byte of the SDU and the last byte of the data portion of the RLC PDU ⁇ correspond to the last byte of the RLC SDU. According to the FI information of the header of the RLC PDU P2, the RLC PDU ⁇ 2" is known.
- the first byte of the data portion corresponds to the first byte of an RLC SDU and the last byte of the data portion of the RLC PDU ⁇ 2" corresponds to the non-last byte of the RLC SDU, and the relay station 2b according to the RLC PDU P3 "FI information of the header, the first byte of the data portion of the RLC PDU P3" corresponds to the non-first byte of an RLC SDU and the last byte of the data portion of the RLC PDU P3" corresponds The last byte of the RLC SDU.
- the RLC entity of the relay station 2b knows that the RLC PDU ⁇ corresponds to a complete RLC SDU, and the data portions of the RLC PDU P2" and RLC PDU P3" constitute a complete RLC SDU. Therefore, the RLC entity of the relay station 2b marks the RLC SDU1 and the RLC SDU2 as "being acknowledged to the terminal", for example, being UE acknowledged
- the RLC entity of the relay station 2b generates a terminal delivery message (UD ACK), and the terminal delivery message includes a plurality of PDCPs consecutively transmitted by the base station starting from the first unacknowledged PDCP PDU in the order of transmission by the base station.
- the number of PDUs that is, two.
- the relay station 2a transmits the UD ACK ( 2 ) to the RLC entity of the relay station 2a, wherein 2 in parentheses indicates that the base station transmits the first unacknowledged PDCP PDU in the order of transmission by the base station.
- the number of consecutive PDCP PDUs is two.
- the RLC entity of the relay station 2b marks the RLC SDU1 and the RLC SDU2 as "confirmed delivery terminals", for example, the UE acknowledged.
- step S311 the relay station 2a forwards the UD ACK ( 2 ) to the RLC entity la of the base station 1.
- step S312 after the RLC entity 1a of the base station 1 receives the terminal acknowledgement message, the RLC entity 1a of the base station 1 sends the indication information to the PDCP entity 1b of the base station 1, the indication information is used to indicate that the PDCP entity lb is discarded.
- step S313 the PDCP entity lb of the base station 1 discards the PDCP SDU corresponding to the first two PDCP PDUs confirmed by the terminal delivery acknowledgement message. If the first two PDCP PDUs are buffered in the base station, the base station 1 also deletes the corresponding PDCP PDU.
- the UD ACK message in the above embodiment is used to indicate that the first K RLC SDUs are acknowledged to be delivered to the terminal.
- the format of the UD ACK message may also be designed such that the UD ACK message does not need to carry the number of consecutive RLC SDUs of the acknowledged delivery terminal, that is, the UD ACK message indicates the relay station at this time. 2b performs a feedback terminal delivery acknowledgement message only for the first unacknowledged RLC SDU message in the list at a time.
- the relay station 2b when the relay station 2b receives the ACK message corresponding to the RLC SDU1, the relay station 2b immediately feeds back the UD ACK message to the relay station 2a, indicating that the first one of the UD ACK messages has not been acknowledged.
- the RLC SDU has been confirmed.
- the PDCP layer lb of the base station 1 deletes the cached first PDCP SDIL.
- the mobile terminal 3 has successfully received all of the RLC PDUs P2" and P3" corresponding to the RLC SDU 2, and the corresponding ACK is fed back in step S306.
- the relay station 2b must wait until receiving all the RLC PDUs corresponding to the RLC SDU1.
- the UD ACK message can be fed back to the base station.
- a bit map may be adopted.
- the relay station 2b receives an ACK of all RLC PDUs corresponding to the RLC SDU 2 from the mobile terminal 3, and receives the corresponding RLC SDU 1
- the NACK of the RLC PDU can set the first bit in the bitmap to 0, and the second bit to 1 to indicate that the UD ACK of the SDU 1 is not received, and the UD ACK of the SDU 2 is received.
- the UD ACK is sent.
- the relay station 2b transmitting the UD ACK message is not limited to the above-described bitmap mode or implicit manner. You can also use other information expressions to send UD ACK messages, for example. For example, the run-length (RLE) method is used.
- RLE run-length
- a tunnel needs to be established between the source base station, e.g., base station 1 and the target base station.
- the PDCP entity lb of the base station 1 will transmit to the PDCP entity of the target base station all PDCP SDILs that are not successfully acknowledged by the RLC entity la of the base station 1 for the mobile terminal to be accessed by the relay station, because only the RLC entity of the base station 1 receives
- the PDCP entity lb of the base station 1 transmits an indication message indicating the successful transmission of the PDCP PDU, and then the PDCP entity 1b of the base station 1 discards the corresponding PDCP SDU.
- the status information of whether the user data in the PDCP entity lb of the base station 1 is successfully received by the terminal is accurate because it is synchronized with the state of the mobile terminal, thereby avoiding the prior art, the base station 1 may not deliver the data in the mobile station.
- the data is discarded at the PDCP layer before the terminal, causing data loss during the handover. Therefore, it is possible to ensure the sequential transmission at the time of switching.
- FIG. 4 shows a block diagram of a device in accordance with an embodiment of the present invention.
- the control device 10 is located in the base station 1.
- the control device 10 includes a first transmitting device 100, a first determining device 101, a providing device 102, and a discarding device 103.
- the auxiliary device 20 is located in the relay station 2b.
- the auxiliary device 20 includes a second transmitting device 200, a second judging device 201, and a third transmitting device 202.
- the PDCP entity lb of the base station 1 transmits the PDCP PDU to the RLC entity la of the base station 1. Specifically, at the PDCP layer, the PDCP entity 1b of the base station 1 acquires the data packets transmitted by the IP layer, performs header compression based on, for example, the ROHC algorithm, and sequentially encapsulates the IP data packets in the order of transmission of the IP data packets, and puts the PDCP PDU header. (header), and sequentially add the sequence number of the PDCP PDU in the PDCP PDU header. The serial number of the PDCP PDU is also sequentially increased, and data encryption is performed to form PDCP PDIL.
- the RLC entity la of the base station 1 is based on the information of the MAC layer from the base station 1, for example, according to the size of the transmission block (TB) indicated by the MAC layer.
- the PDCP PDUs from the upper layer that is, the PDCP layer lb, are sequentially segmented and/or concatenated in the order of the sequence number (SN) of the PDCP PDUs to generate corresponding sequences corresponding to one or more PDCP PDUs.
- the information from the MAC layer may be based on radio resources allocated on the link between the base station 1 and the relay station 2a, such as time-frequency resources allocated for the link and transmission characteristics of the link such as link quality, and/or different The priority between the business is generated.
- the first transmitting device 100 transmits each RLC PDU corresponding to one or more PDCP PDUs to the next-level relay station on the path to the mobile terminal 3.
- the first transmitting device 100 transmits each RLC PDU corresponding to the one or more PDCP PDUs to the RLC entity of the relay station 2a.
- the PDCP entity 1b of the base station 1 may further include a memory for buffering the acquired PDCP SDIL.
- the step of storing the memory buffer has no obvious relationship with the step of transmitting the RLC PDU by the first transmitting device 100.
- the PDCP entity 1b may firstly forward to the RLC.
- the entity la transmits the PDCP PDU.
- the memory then buffers the PDCP PDUs in order; or the memory caches the PDCP SDUs in order, and the PDCP entity lbs to the RLC.
- the RLC entity la then splits/splices the PDCP PDU into one or more RLC PDUs and sends them to the UE.
- the second transmitting device 200 in the relay station 2b can refer to the information from the MAC layer of the relay station 2b, for example, according to the size of the transmission block (TB) indicated by the MAC layer of the relay station 2b, the received from the relay station 2a.
- One or more RLC SDUs of the RLC entity are sequentially re-segmented and/or concatenation to generate sequential RLC PDUs corresponding to one or more RLC SDUs.
- the information from the MAC layer may be based on radio resources allocated on the link between the relay station 2a and the relay station 2b, such as time-frequency resources allocated for the link, and transmission characteristics of the link such as link quality, and / Or the priority between different businesses is generated.
- the second transmitting device 200 transmits the re-segmentation and/or splicing to the mobile terminal 3.
- Each RLC PDU corresponding to one or more RLC SDUs.
- the access relay station 2b receives the ACK/NACK corresponding to each RLC PDU transmitted from the RLC entity of the relay station 2b fed back from the mobile terminal 3.
- the second judging means 201 judges whether or not an ACK of each RLC PDU corresponding to the RLC SDU from the mobile terminal 3 is received, that is, the second judging means 201 judges whether or not all of the RLC SDUs corresponding to the RLC SDU from the mobile terminal 3 are received.
- ACK message of the RLC PDU The RLC header of the RLC PDU includes indication information for indicating that the data portion of the RLC PDU includes several RLC SDUs or RLC SDU segments, and an end position of each RLC SDU or RLC SDU segment. Based on the above information, the second judging means 201 can judge when all RLC PDUs corresponding to a complete RLC SDU are received.
- the third transmitting means 202 transmits a terminal service acknowledgement message (User Equipment Delivery Acknowlegement) to the relay station 2a, wherein the terminal delivers the acknowledgement
- the message is used to confirm that the RLC SDU has been delivered to the mobile terminal 3.
- the RLC SDU is a PDCP PDU.
- the RLC SDU is exchanged between the RLC entity and the PDCP entity, and the PDCP PDU is exchanged between the PDCP entity and the PDCP entity.
- the relay station 2a transmits the terminal delivery confirmation message to the RLC entity la of the base station 1.
- the providing device 102 sends the indication information to the PDCP entity 1b of the base station 1, the indication information is used to indicate the PDCP.
- the entity lb discards the buffered PDCP SDU corresponding to the RLC SDU (PDCP PDU).
- the discarding device 103 discards the buffered PDCP SDU corresponding to the RLC SDU confirmed by the terminal delivery acknowledgement message.
- the PDCP SDU is pure data information that is not encrypted, and the PDCP PDU is a data packet that is encrypted by the PDCP SDU. Since the data encryption algorithms of the respective base stations are different, generally, the PDCP SDU is buffered in the base station, and at the time of handover, the source base station transmits the unencrypted PDCP SDU to the target base station. Of course, when the base station also caches the confirmation confirmed by the terminal delivery acknowledgement message The PDCP PDU, the discarding device 103 also deletes the PDCP PDU confirmed by the terminal delivery acknowledgement message from the cache.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/390,570 US20120140704A1 (en) | 2009-08-17 | 2009-08-17 | Method and apparatus for controlling downlink data transmission in a multi-hop relay communication system |
KR1020127006883A KR20120048019A (ko) | 2009-08-17 | 2009-08-17 | 멀티-홉 중계 통신 시스템에서 다운링크 데이터 전송 제어를 위한 방법 및 장치 |
CN200980159605.2A CN102449944B (zh) | 2009-08-17 | 2009-08-17 | 多跳中继通信系统中对下行数据传输控制的方法和装置 |
JP2012525011A JP2013502755A (ja) | 2009-08-17 | 2009-08-17 | マルチホップ・リレー通信システムにおいてダウンリンク・データ伝送を制御するための方法および装置 |
EP09848374.6A EP2469750A4 (en) | 2009-08-17 | 2009-08-17 | METHOD AND DEVICE FOR DOWNLINK DATA TRANSMISSION CONTROL IN A MULTI-HOP RELAY COMMUNICATION SYSTEM |
PCT/CN2009/073308 WO2011020233A1 (zh) | 2009-08-17 | 2009-08-17 | 多跳中继通信系统中对下行数据传输控制的方法和装置 |
BR112012003636A BR112012003636A2 (pt) | 2009-08-17 | 2009-08-17 | método e aparelho para controlar transmissão de dados para downlink em um sistema de comunicação de retransmissão com múltiplos saltos |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2009/073308 WO2011020233A1 (zh) | 2009-08-17 | 2009-08-17 | 多跳中继通信系统中对下行数据传输控制的方法和装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011020233A1 true WO2011020233A1 (zh) | 2011-02-24 |
Family
ID=43606535
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/073308 WO2011020233A1 (zh) | 2009-08-17 | 2009-08-17 | 多跳中继通信系统中对下行数据传输控制的方法和装置 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20120140704A1 (zh) |
EP (1) | EP2469750A4 (zh) |
JP (1) | JP2013502755A (zh) |
KR (1) | KR20120048019A (zh) |
CN (1) | CN102449944B (zh) |
BR (1) | BR112012003636A2 (zh) |
WO (1) | WO2011020233A1 (zh) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014075210A1 (zh) * | 2012-11-13 | 2014-05-22 | 华为技术有限公司 | 传输数据的方法、基站和用户设备 |
US20150031376A1 (en) * | 2012-02-17 | 2015-01-29 | Zte Corporation | Radio system and spectrum resource reconfiguration method thereof |
CN108024295A (zh) * | 2016-11-03 | 2018-05-11 | 中兴通讯股份有限公司 | 中继转移方法及装置、终端、基站 |
CN108476435A (zh) * | 2017-06-19 | 2018-08-31 | 北京小米移动软件有限公司 | 数据处理方法及装置、用户设备和计算机可读存储介质 |
CN110506404A (zh) * | 2017-05-05 | 2019-11-26 | 华为技术有限公司 | 一种数据接收状态报告方法及装置 |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130230059A1 (en) * | 2011-09-02 | 2013-09-05 | Qualcomm Incorporated | Fragmentation for long packets in a low-speed wireless network |
KR101667507B1 (ko) * | 2012-11-29 | 2016-10-18 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 데이터 전송 제어 방법, 장치 및 시스템 |
CN103888215B (zh) * | 2012-12-21 | 2017-11-28 | 华为技术有限公司 | 数据传输方法、装置及通信系统 |
US9648514B2 (en) * | 2013-08-09 | 2017-05-09 | Blackberry Limited | Method and system for protocol layer enhancements in data offload over small cells |
CN104518851A (zh) * | 2013-09-27 | 2015-04-15 | 中兴通讯股份有限公司 | 一种数据处理方法及装置 |
CN104853382B (zh) * | 2014-02-18 | 2020-08-25 | 中兴通讯股份有限公司 | 一种信息交互方法、系统以及基站 |
US20160013976A1 (en) * | 2014-07-14 | 2016-01-14 | Futurewei Technologies, Inc. | Wireless Through Link Traffic Reduction |
US9929847B2 (en) * | 2014-12-23 | 2018-03-27 | Qualcomm Incorporated | Shortened block acknowledgement with fragmentation acknowledgement signaling |
US10021596B2 (en) * | 2016-03-30 | 2018-07-10 | Industrial Technology Research Institute | Communication system, communication device, base station and method thereof for D2D communications |
CN107333298B (zh) * | 2016-04-29 | 2020-03-24 | 电信科学技术研究院 | 一种数据传输方法及相关设备 |
WO2017194161A1 (en) * | 2016-05-13 | 2017-11-16 | Telecom Italia S.P.A. | Method and system for loss mitigation during device to device communication mode switching |
US20180097918A1 (en) * | 2016-09-30 | 2018-04-05 | Mediatek Inc. | Segmentation and Concatenation for New Radio Systems |
RU2727866C1 (ru) | 2016-11-04 | 2020-07-24 | Бейдзин Сяоми Мобайл Софтвэр Ко., Лтд. | Способ и устройство для генерирования пакета протокольного блока данных (pdu) |
CN110140338B (zh) * | 2016-11-08 | 2022-03-18 | 瑞典爱立信有限公司 | 用户设备、传输点、由通信装置执行的方法 |
US10021586B1 (en) * | 2016-12-23 | 2018-07-10 | Intel IP Corporation | Pushing back packet not acknowledged by base station |
CN108632326B (zh) * | 2017-03-24 | 2020-10-30 | 电信科学技术研究院 | 一种协议数据单元传输数据的方法及装置 |
WO2019035670A1 (en) * | 2017-08-16 | 2019-02-21 | Samsung Electronics Co., Ltd. | METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING DOUBLE PACKETS IN A NEXT GENERATION MOBILE COMMUNICATION SYSTEM |
CN109842440B (zh) * | 2017-11-27 | 2021-08-27 | 华为技术有限公司 | 一种通信方法、通信节点和系统 |
CN115103402A (zh) * | 2018-05-10 | 2022-09-23 | 华为技术有限公司 | 数据处理的方法及设备 |
GB2574876A (en) * | 2018-06-21 | 2019-12-25 | Tcl Communication Ltd | Transmission techniques in a cellular network |
US20230147845A1 (en) * | 2018-06-21 | 2023-05-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Preventing / mitigating packet loss in iab systems |
WO2019245442A1 (en) * | 2018-06-21 | 2019-12-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Preventing/mitigating packet loss in integrated access backhaul (iab) networks |
CN110636549B (zh) * | 2018-06-21 | 2022-04-12 | 华为技术有限公司 | 数据传输方法、网络设备以及终端设备 |
KR20210022639A (ko) * | 2018-06-21 | 2021-03-03 | 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 | 시그널링 전송 방법, 장치 및 네트워크 디바이스 |
WO2020032129A1 (ja) * | 2018-08-08 | 2020-02-13 | 京セラ株式会社 | 中継装置 |
CN111490859A (zh) * | 2019-01-29 | 2020-08-04 | 普天信息技术有限公司 | 一种arq模式的切换方法及装置 |
WO2020178918A1 (ja) * | 2019-03-01 | 2020-09-10 | 三菱電機株式会社 | 無線通信システム |
CN112584428B (zh) * | 2019-09-27 | 2023-01-13 | 大唐移动通信设备有限公司 | 一种数据传输方法、装置及设备 |
CN112702752A (zh) * | 2020-12-22 | 2021-04-23 | 展讯通信(上海)有限公司 | 通信方法、装置及设备 |
WO2022170612A1 (en) * | 2021-02-11 | 2022-08-18 | Qualcomm Incorporated | Multiple feedback in relay-based communication |
CN116962306A (zh) * | 2022-04-19 | 2023-10-27 | 华为技术有限公司 | 数据传输的方法和通信装置 |
WO2024092657A1 (en) * | 2022-11-03 | 2024-05-10 | Nec Corporation | Method, device and computer storage medium of communication |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1437368A (zh) * | 2002-02-08 | 2003-08-20 | 华硕电脑股份有限公司 | 数据传输的确认方法 |
CN101383685A (zh) * | 2007-09-07 | 2009-03-11 | 华为技术有限公司 | 下行混合自动重传的方法、系统及装置 |
CN101471756A (zh) * | 2007-12-27 | 2009-07-01 | 上海无线通信研究中心 | 集中式调度的多跳中继下行系统中的harq方法 |
Family Cites Families (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101116277A (zh) * | 2005-02-07 | 2008-01-30 | 三星电子株式会社 | 用于请求/传送移动通信系统的状态报告的方法和设备 |
EP2787676B1 (en) * | 2005-12-22 | 2018-08-01 | InterDigital Technology Corporation | Method and apparatus for data security and automatic repeat request implementation in a wireless communication system |
AU2007268382B2 (en) * | 2006-05-29 | 2010-12-16 | Samsung Electronics Co., Ltd. | Retransmission apparatus and method in wireless relay communication system |
WO2007141617A1 (en) * | 2006-06-02 | 2007-12-13 | Nortel Networks Limited | Ranging regions for wireless communication relay stations |
CN101047431B (zh) * | 2006-06-22 | 2011-02-02 | 华为技术有限公司 | 在含有中继站的通信系统中实现混合自动重传的方法 |
KR100982688B1 (ko) * | 2006-09-13 | 2010-09-16 | 삼성전자주식회사 | 홉 단위 재전송을 적용하는 다중 홉 릴레이 시스템에서 패킷 버퍼링 장치 및 방법 |
CN101150498B (zh) * | 2006-09-18 | 2012-06-20 | 华为技术有限公司 | 多跳无线中继通信系统及其下行数据传输方法 |
KR101391899B1 (ko) * | 2006-09-19 | 2014-05-07 | 지티이 (유에스에이) 인크. | 무선 통신 시스템에서 멀티-홉 중계를 위한 프레임 구조 |
WO2008035935A1 (en) * | 2006-09-20 | 2008-03-27 | Samsung Electronics Co., Ltd. | Handover method and apparatus in a mobile communication system |
KR100938090B1 (ko) * | 2006-10-19 | 2010-01-21 | 삼성전자주식회사 | 이동통신 시스템에서 핸드오버 수행 방법 및 장치 |
US7983302B2 (en) * | 2006-11-07 | 2011-07-19 | Nokia Corporation | Control signaling techniques for wireless networks |
KR100976733B1 (ko) * | 2006-11-17 | 2010-08-18 | 삼성전자주식회사 | 멀티 홉 릴레이 시스템에서 효율적인 자동 재전송 요구 장치 및 방법 |
WO2008096304A2 (en) * | 2007-02-09 | 2008-08-14 | Nxp B.V. | Transmission method, transmitter and data processing system comprising a transmitter |
KR100907978B1 (ko) * | 2007-09-11 | 2009-07-15 | 엘지전자 주식회사 | 이동통신 시스템에서 pdcp 계층의 상태보고 전송 방법 및 수신장치 |
EP2051454A1 (en) * | 2007-10-17 | 2009-04-22 | Nokia Siemens Networks Oy | Method and device for data communication and communication system comprising such device |
EP2086142A3 (en) * | 2008-02-04 | 2012-10-10 | LG Electronics Inc. | Wireless communication method for transmitting a sequence of data units between a wireless device and a network |
US8018890B2 (en) * | 2008-06-25 | 2011-09-13 | Intel Corporation | Techniques using a hop-by-hop approach for automatic repeat request (ARQ) in wireless relay networks |
US9203564B2 (en) * | 2008-10-20 | 2015-12-01 | Qualcomm Incorporated | Data transmission via a relay station in a wireless communication system |
US8402334B2 (en) * | 2008-12-17 | 2013-03-19 | Research In Motion Limited | System and method for hybrid automatic repeat request (HARQ) functionality in a relay node |
CN102273246B (zh) * | 2009-01-29 | 2015-04-22 | 富士通株式会社 | 无线通信系统 |
JP2012520621A (ja) * | 2009-03-13 | 2012-09-06 | リサーチ イン モーション リミテッド | 中継受信同調化システムおよびその方法 |
RU2496263C2 (ru) * | 2009-03-17 | 2013-10-20 | Хуавэй Текнолоджиз Ко., Лтд. | Способ, устройство и система для отправки пакета данных |
US8687591B2 (en) * | 2009-04-27 | 2014-04-01 | Qualcomm Incorporated | Relay node user plane support |
EP2443870B1 (en) * | 2009-06-17 | 2014-10-15 | InterDigital Patent Holdings, Inc. | Method and apparatus for performing handover with a relay node |
-
2009
- 2009-08-17 EP EP09848374.6A patent/EP2469750A4/en not_active Withdrawn
- 2009-08-17 CN CN200980159605.2A patent/CN102449944B/zh active Active
- 2009-08-17 JP JP2012525011A patent/JP2013502755A/ja not_active Ceased
- 2009-08-17 WO PCT/CN2009/073308 patent/WO2011020233A1/zh active Application Filing
- 2009-08-17 KR KR1020127006883A patent/KR20120048019A/ko not_active Application Discontinuation
- 2009-08-17 BR BR112012003636A patent/BR112012003636A2/pt not_active IP Right Cessation
- 2009-08-17 US US13/390,570 patent/US20120140704A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1437368A (zh) * | 2002-02-08 | 2003-08-20 | 华硕电脑股份有限公司 | 数据传输的确认方法 |
CN101383685A (zh) * | 2007-09-07 | 2009-03-11 | 华为技术有限公司 | 下行混合自动重传的方法、系统及装置 |
CN101471756A (zh) * | 2007-12-27 | 2009-07-01 | 上海无线通信研究中心 | 集中式调度的多跳中继下行系统中的harq方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2469750A4 * |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150031376A1 (en) * | 2012-02-17 | 2015-01-29 | Zte Corporation | Radio system and spectrum resource reconfiguration method thereof |
US9578516B2 (en) * | 2012-02-17 | 2017-02-21 | Zte Corporation | Radio system and spectrum resource reconfiguration method thereof |
WO2014075210A1 (zh) * | 2012-11-13 | 2014-05-22 | 华为技术有限公司 | 传输数据的方法、基站和用户设备 |
US10110282B2 (en) | 2012-11-13 | 2018-10-23 | Huawei Technologies Co., Ltd. | Data transmission method, base station, and user equipment |
CN108024295A (zh) * | 2016-11-03 | 2018-05-11 | 中兴通讯股份有限公司 | 中继转移方法及装置、终端、基站 |
CN108024295B (zh) * | 2016-11-03 | 2022-04-19 | 中兴通讯股份有限公司 | 中继转移方法及装置、终端、基站 |
US11219091B2 (en) | 2017-05-05 | 2022-01-04 | Huawei Technologies Co., Ltd. | Data receiving status reporting method and apparatus |
CN110506404A (zh) * | 2017-05-05 | 2019-11-26 | 华为技术有限公司 | 一种数据接收状态报告方法及装置 |
CN114189901A (zh) * | 2017-05-05 | 2022-03-15 | 华为技术有限公司 | 一种数据接收状态报告方法及装置 |
US11672046B2 (en) | 2017-05-05 | 2023-06-06 | Huawei Technologies Co., Ltd. | Data receiving status reporting method and apparatus |
CN108476435B (zh) * | 2017-06-19 | 2021-07-27 | 北京小米移动软件有限公司 | 数据处理方法及装置、用户设备和计算机可读存储介质 |
WO2018232559A1 (zh) * | 2017-06-19 | 2018-12-27 | 北京小米移动软件有限公司 | 数据处理方法及装置、用户设备和计算机可读存储介质 |
CN108476435A (zh) * | 2017-06-19 | 2018-08-31 | 北京小米移动软件有限公司 | 数据处理方法及装置、用户设备和计算机可读存储介质 |
US11558494B2 (en) | 2017-06-19 | 2023-01-17 | Beijing Xiaomi Mobile Software Co., Ltd. | Method and apparatus for processing data, user equipment and computer-readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
EP2469750A4 (en) | 2014-07-02 |
EP2469750A1 (en) | 2012-06-27 |
BR112012003636A2 (pt) | 2016-03-22 |
CN102449944A (zh) | 2012-05-09 |
JP2013502755A (ja) | 2013-01-24 |
CN102449944B (zh) | 2015-11-25 |
US20120140704A1 (en) | 2012-06-07 |
KR20120048019A (ko) | 2012-05-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011020233A1 (zh) | 多跳中继通信系统中对下行数据传输控制的方法和装置 | |
KR101387537B1 (ko) | 성공적으로 수신했으나 헤더 압축 복원에 실패한 패킷의 처리 방법 | |
US9860915B2 (en) | Apparatus and method for moving a receive window in a radio access network | |
RU2461147C2 (ru) | Способ обработки радиопротокола в системе подвижной связи и передатчик подвижной связи | |
KR101387475B1 (ko) | 복수의 네트워크 엔터티를 포함하는 이동 통신시스템에서의 데이터 처리 방법 | |
EP2168270B1 (en) | A method for handling correctly received but header compression failed packets | |
KR20100053625A (ko) | 무선 통신 시스템에서의 핸드오버 동안 데이터의 계층 2 터널링 | |
JP5081900B2 (ja) | 再送要求送信方法及び受信側装置 | |
WO2007098676A1 (fr) | Procédé de réassemblage de données dans un système de communication sans fil et appareil associé | |
WO2014094613A1 (zh) | 数据传输方法、装置及通信系统 | |
WO2017185941A1 (zh) | 一种数据传输方法及相关设备 | |
JP2013513988A (ja) | 中継ハンドオーバ制御 | |
WO2007022694A1 (fr) | Pile de protocoles utilisateur et procede de transfert sans perte | |
JP3727198B2 (ja) | ゲートウェイ装置 | |
WO2017133595A1 (zh) | 数据处理的方法及装置 | |
JP2005102340A (ja) | ゲートウェイ装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200980159605.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09848374 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2009848374 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009848374 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13390570 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1456/CHENP/2012 Country of ref document: IN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012525011 Country of ref document: JP |
|
ENP | Entry into the national phase |
Ref document number: 20127006883 Country of ref document: KR Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112012003636 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112012003636 Country of ref document: BR Kind code of ref document: A2 Effective date: 20120217 |