[go: up one dir, main page]

WO2015176748A1 - Indication d'état de fenêtre de réception pour une unité de données en paquets - Google Patents

Indication d'état de fenêtre de réception pour une unité de données en paquets Download PDF

Info

Publication number
WO2015176748A1
WO2015176748A1 PCT/EP2014/060349 EP2014060349W WO2015176748A1 WO 2015176748 A1 WO2015176748 A1 WO 2015176748A1 EP 2014060349 W EP2014060349 W EP 2014060349W WO 2015176748 A1 WO2015176748 A1 WO 2015176748A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication
packet data
data unit
computer program
window
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/EP2014/060349
Other languages
English (en)
Inventor
Guillaume DECARREAU
Henri Markus Koskinen
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.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
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 Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Priority to PCT/EP2014/060349 priority Critical patent/WO2015176748A1/fr
Publication of WO2015176748A1 publication Critical patent/WO2015176748A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using 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
    • 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • 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/1864—ARQ related signaling

Definitions

  • Knowledge of packet reception can be important in packet-based communications. For example, certain packet-based communication systems may benefit from signaling of an indication of reception-window status at reception of a packet data unit outside a reception window.
  • Dual connectivity is one aspect of long term evolution (LTE) as described in third generation partnership project (3GPP) RP-132069 and 3GPP TR 36.842, each of which is hereby incorporated herein by reference in its entirety.
  • 3GPP third generation partnership project
  • RP-132069 3GPP TR 36.842
  • PDCP packet data convergence protocol
  • the reordering window in a PDCP entity configured for reordering can be pushed by Last_Submitted_PDCP_RX_SN similarly to the way specified for PDCP mapped on radio link control (RLC) acknowledged mode (AM).
  • RLC radio link control
  • an indication of the updated reordering-window status can be transmitted in the form of a PDCP status report.
  • Such a pushed reordering window may have various characteristics. If the pushed window from the currently specified PDCP mapped on RLC AM were used and combined with a reordering timer, then it would operate as follows. When a PDU outside the window is received, the COUNT value associated with the service data unit (SDU) may be assumed to be behind the current reordering window, but may not be used as a further COUNT-value reference. Furthermore, the PDU/SDU can be discarded.
  • SDU service data unit
  • the legacy PDCP protocol specifies status reporting.
  • the UE shall, if the radio bearer is configured by upper layers to send a PDCP status report in the uplink, compile a status report after processing the PDCP Data PDUs that are received from lower layers due to the re-establishment of the lower layers, and submit it to lower layers as the first PDCP PDU for the transmission. This is accomplished by setting the first missing sequence (FMS) field to the PDCP SN of the first missing PDCP SDU.
  • FMS first missing sequence
  • this is accomplished by, if there is at least one out-of- sequence PDCP SDU stored, allocating a Bitmap field of length in bits equal to the number of PDCP SNs from and not including the first missing PDCP SDU up to and including the last out-of-sequence PDCP SDUs, rounded up to the next multiple of 8. Moreover, this is accomplished by setting as '0' in the corresponding position in the bitmap field for all PDCP SDUs that have not been received as indicated by lower layers, and optionally PDCP SDUs for which decompression have failed. Furthermore, this is accomplished by indicating in the bitmap field as ⁇ ' for all other PDCP SDUs.
  • a method can include receiving a packet data unit outside a current reception window. The method can also include preparing, upon receiving the packet data unit, an indication of reception window status to be transmitted to a peer protocol entity.
  • a method can include receiving an indication of reception window status from a user equipment. The method can also include determining an edge of a transmission window based on the indication.
  • a non-transitory computer-readable medium can be encoded with instructions that, when executed in hardware, perform the above-described methods.
  • a computer program product can encode instructions that, when executed in hardware, perform the above-described methods.
  • An apparatus can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with that least one processor, cause the apparatus at least to receive a packet data unit outside a current reception window.
  • the at least one memory and the computer program code can also be configured to, with that least one processor, cause the apparatus at least to prepare, upon receiving the packet data unit, an indication of reception window status to be transmitted to a peer protocol entity.
  • An apparatus in certain embodiments, can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with that least one processor, cause the apparatus at least to receive an indication of reception window status from a user equipment.
  • the at least one memory and the computer program code can also be configured to, with that least one processor, cause the apparatus at least to determine an edge of a transmission window based on the indication.
  • an apparatus can include means for receiving a packet data unit outside a current reception window.
  • the apparatus can also include means for preparing, upon receiving the packet data unit, an indication of reception window status to be transmitted to a peer protocol entity.
  • an apparatus can include means for receiving an indication of reception window status from a user equipment.
  • the apparatus can also include means for determining an edge of a transmission window based on the indication.
  • Figure 1 illustrates a method according to certain embodiments.
  • Figure 2 illustrates a system according to certain embodiments.
  • a packet data convergence protocol (PDCP) packet data unit (PDU) sent by a Master eNode B (MeNB) to a secondary eNB (SeNB) for transmission to a user equipment (UE) can be lost on the X2 interface.
  • PDCP packet data convergence protocol
  • MeNB Master eNode B
  • SeNB secondary eNB
  • the pushed PDCP reordering window may stop for the expiry time of a reordering timer to wait for the missing PDU.
  • the MeNB is not aware of the previous loss, the MeNB can go on to transmit further PDCP PDUs that fall outside the UE's PDCP reordering window.
  • the UE may discard such PDUs. However, the transmission of those PDUs may still be acknowledged (ACKed) by the UE at the underlying RLC layer, indication of which is conveyed to the MeNB. As a result, the MeNB can discard the corresponding PDCP service data units (SDUs), meaning that they cannot later be retransmitted, either.
  • SDUs PDCP service data units
  • the expiry of the timer can trigger sending an indication of the updated reordering-window status in the form of a PDCP status report. While such an approach may aim to bring the MeNB back to synchronization (sync) with the status of the reordering window at the UE, the trigger with the reordering-timer expiry may not provide the earliest possible occasion to bring the MeNB back to sync.
  • an indication of the reordering-window status can be transmitted to a peer protocol entity when a packet data unit (PDU) outside the current reordering window is received.
  • the network can configure a user equipment (UE) to send such indication in case of a too early PDU.
  • the PDU can be considered too early when the SN of the PDU is interpreted as being ahead of the current window.
  • the network can configure the UE to send the indication in case of a too late PDU.
  • the PDU can be considered too late when the PDU is interpreted as being behind the current window.
  • a timer can be configured to prohibit the transmission of a subsequent indication.
  • a UE can transmit a PDCP status report containing at least an FMS field. To the peer entity this report with this field can implicitly indicate a current value of the state variable Last_Submitted_PDCP_RX_SN.
  • the state variable Last_Submitted_PDCP_RX_SN can function as a lower edge of a reordering window.
  • a bitmap indicating reception status of individual PDUs may optionally be included.
  • This status report when received, can be interpreted as specified for legacy PDCP operation. Thus, in certain embodiments not even the FMS field by itself may be interpreted as a retransmission request.
  • the network can configure the UE so that the UE can send the indication only if the PDU is early.
  • the indication can be sent if the sequence number (SN) of the PDU is ahead of the re-ordering window.
  • This condition for the SN can be defined such that the SN falls within the SN-space quadrant immediately ahead of the window. For example, the SN can fall within the quadrant between Last_Submitted_PDCP_RX_SN + Reordering window and Last_Submitted_PDCP_RX_SN + 3 * Reordering_window/2 (mod 1 +maximum_PDCP_SN).
  • the network can also configure the UE so that the UE can send the indication only if the PDU is late.
  • the indication can be sent if the SN of the PDU is behind the re- ordering window.
  • This condition for the SN can be defined such that the SN falls within the SN-space quadrant immediately behind the window. For example, the SN can fall within the quadrant between Last_Submitted_PDCP_RX_SN + 3 * Reordering_window/2 and Last_Submitted_PDCP_RX_SN + 2 * Reordering_window (mod 1 +maximum_PDCP_SN).
  • a timer can be configured with the following behavior.
  • the timer can be started when an indication is sent with a cause of out of window PDU reception. If the timer is running, no indication is sent with the cause above, although optionally an indication can be sent with another cause. When the timer expires, sending indication with the cause above is permitted again.
  • Figure 1 illustrates a method according to certain embodiments.
  • a method can include, at 1 10, receiving a packet data unit outside a current reception window, such as a current reordering window.
  • the method can also include, at 120, preparing, upon receiving the packet data unit, an indication of reception window status, for example reordering window status, to be transmitted to a peer protocol entity.
  • the preparing the indication is performed contingent on the packet data unit being received too early.
  • the method can include, at 122, determining that the packet data unit is received too early when a sequence number of the packet data unit is interpreted as being ahead of the current reception window.
  • the preparing the indication can be performed contingent on the packet data unit being received too late.
  • the method can include, at 124, determining that the packet data unit is received too late when a sequence number of the packet data unit is interpreted as being behind the current reception window.
  • the method can further include, at 130, transmitting the indication to the peer protocol entity.
  • the transmitting the indication can include transmitting a packet data convergence protocol status report containing at least a field indicating the sequence number of a first missing service data unit.
  • the method can additionally include, at 140, starting a timer upon transmitting the indication.
  • the method can also include, at 150, prohibiting a subsequent indication before expiration of the timer.
  • the method can also optionally include, at 160, including, with the indication, a bitmap indicating reception status of individual packet data units.
  • Timing of transmission, or any other condition for transmission, of the indication can be configured by the network.
  • a device can be configured by the network to perform the method.
  • the expiry time/value of the prohibit timer may be configured by an eNB, such as an MeNB.
  • the method can also include, at 170, receiving an indication of reception window status, for example reordering window status, from a user equipment.
  • the method can also include, at 180, determining an edge of a transmission window based on the indication.
  • the determining the edge can include determining a lower edge, an upper edge, or both the edge and the upper edge.
  • Figure 2 illustrates a system according to certain embodiments of the invention.
  • a system may include multiple devices, such as, for example, at least one UE 210, at least one MeNB 220 or other base station or access point, and at least one SENB 230 or other base station or access point.
  • UE 210, MeNB 220, SENB 230, and a plurality of other user equipment may be present.
  • Other configurations are also possible, including those with multiple base stations, such as MeNBs.
  • the UE 210 may be equipped for dual connectivity.
  • Each of these devices may include at least one processor, respectively indicated as
  • At least one memory may be provided in each device, as indicated at
  • the memory may include computer program instructions or computer code contained therein.
  • the devices may also include positioning hardware, such as global positioning system (GPS) or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device.
  • positioning hardware such as global positioning system (GPS) or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device.
  • GPS global positioning system
  • MEMS micro electrical mechanical system
  • Other sensors are also permitted and may be included to determine location, elevation, orientation, and so forth, such as barometers, compasses, and the like.
  • transceivers 216, 226, and 236 may be provided, and each device may also include at least one antenna, respectively illustrated as 217, 227, and 237.
  • the device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple radio access technologies.
  • MIMO multiple input multiple output
  • MeNB 220 and SENB 230 may additionally or solely be configured for wired communication, and in such a case antennas 227, 237 would also illustrate any form of communication hardware, without requiring a conventional antenna.
  • Transceivers 216, 226, and 236 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that is configured both for transmission and reception.
  • Processors 214, 224, and 234 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors.
  • Memories 215, 225, and 235 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors.
  • the computer program instructions stored in the memory and which may be processed by the processors may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as UE 210, MeNB 220, and SENB 230, to perform any of the processes described above (see, for example, Figure 1 ). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.
  • Figure 2 illustrates a system including a UE, MeNB, and SENB
  • embodiments of the invention may be applicable to other configurations, and configurations involving additional elements.
  • certain embodiments provide for signaling an indication of PDCP reception-window status at reception of PDU outside window for split bearers, such that the MeNB can be brought back to sync with the status of the reordering window at the UE.
  • Certain embodiments may have various benefits and/or advantages.
  • the trigger for action according to certain embodiments can easily be arranged by transmitting properly numbered PDU(s) to the protocol entity.
  • sending of an indication according to certain embodiments at reception of such PDUs may be readily observed and/or tested.

Landscapes

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

Abstract

Selon l'invention, la connaissance de la réception de paquets peut être importante dans les communications en mode paquet. Par exemple, certains systèmes de communication en mode paquet peuvent bénéficier de la signalisation d'une indication d'un état de fenêtre de réception à la réception d'une unité de données en paquets en dehors d'une fenêtre de réception. Un procédé peut comprendre recevoir une unité de données en paquets en dehors d'une fenêtre de réception actuelle. Le procédé peut également comprendre préparer, à la réception de l'unité de données en paquets, une indication d'état de fenêtre de réception à transmettre à une entité de protocole homologue.
PCT/EP2014/060349 2014-05-20 2014-05-20 Indication d'état de fenêtre de réception pour une unité de données en paquets Ceased WO2015176748A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/060349 WO2015176748A1 (fr) 2014-05-20 2014-05-20 Indication d'état de fenêtre de réception pour une unité de données en paquets

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/060349 WO2015176748A1 (fr) 2014-05-20 2014-05-20 Indication d'état de fenêtre de réception pour une unité de données en paquets

Publications (1)

Publication Number Publication Date
WO2015176748A1 true WO2015176748A1 (fr) 2015-11-26

Family

ID=50828884

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/060349 Ceased WO2015176748A1 (fr) 2014-05-20 2014-05-20 Indication d'état de fenêtre de réception pour une unité de données en paquets

Country Status (1)

Country Link
WO (1) WO2015176748A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110537379A (zh) * 2017-02-24 2019-12-03 三星电子株式会社 用于在无线通信系统中的基站之间进行数据发送的设备和方法
CN112187415A (zh) * 2019-07-04 2021-01-05 大唐移动通信设备有限公司 一种重复传输维护方法、终端及网络设备
CN112673674A (zh) * 2018-06-21 2021-04-16 捷开通讯(深圳)有限公司 蜂窝网络中的传输技术
WO2023087145A1 (fr) * 2021-11-16 2023-05-25 Lenovo (Beijing) Limited Procédés et appareils de gestion de réordonnancement de pdcp

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification (Release 11)", 3GPP STANDARD; 3GPP TS 36.323, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V11.2.0, 14 March 2013 (2013-03-14), pages 1 - 27, XP050692247 *
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification (Release 11)", 3GPP STANDARD; 3GPP TS 36.322, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V11.0.0, 17 September 2012 (2012-09-17), pages 1 - 39, XP050649155 *
SAMSUNG, NOKIA CORPORATION, NOKIA SIEMENS NETWORKS: "Handling poll in received PDU which is a duplicate or outside receiving window", 18 August 2008 (2008-08-18), pages 1 - 4, XP002735841, Retrieved from the Internet <URL:www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_63/Docs/R2-084498.zip> [retrieved on 20150211] *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110537379A (zh) * 2017-02-24 2019-12-03 三星电子株式会社 用于在无线通信系统中的基站之间进行数据发送的设备和方法
EP3585094A4 (fr) * 2017-02-24 2020-03-04 Samsung Electronics Co., Ltd. Dispositif et procédé de transmission de données entre des stations de base dans un système de communication sans fil
US11184798B2 (en) 2017-02-24 2021-11-23 Samsung Electronics Co., Ltd. Device and method for data transmission between base stations in wireless communication system
CN110537379B (zh) * 2017-02-24 2023-04-07 三星电子株式会社 用于在无线通信系统中的基站之间进行数据发送的设备和方法
CN112673674A (zh) * 2018-06-21 2021-04-16 捷开通讯(深圳)有限公司 蜂窝网络中的传输技术
CN112187415A (zh) * 2019-07-04 2021-01-05 大唐移动通信设备有限公司 一种重复传输维护方法、终端及网络设备
CN112187415B (zh) * 2019-07-04 2022-06-28 大唐移动通信设备有限公司 一种重复传输维护方法、终端及网络设备
US12107691B2 (en) 2019-07-04 2024-10-01 Datang Mobile Communications Equipment Co., Ltd. Duplication transmission maintaining method, terminal and network device
WO2023087145A1 (fr) * 2021-11-16 2023-05-25 Lenovo (Beijing) Limited Procédés et appareils de gestion de réordonnancement de pdcp
GB2627904A (en) * 2021-11-16 2024-09-04 Lenovo Beijing Ltd Methods and apparatuses for PDCP reordering management

Similar Documents

Publication Publication Date Title
KR101988190B1 (ko) 이중 접속 네트워크에서의 패킷 데이터 컨버젼스 프로토콜(pdcp) 강화
JP6262991B2 (ja) ユーザ装置及び方法
US10498361B2 (en) Methods and apparatuses for group transmissions
CN110476445B (zh) 利用分离承载的分组数据汇聚协议窗口
KR102721539B1 (ko) 통신시스템에서의 데이터 처리 방법
EP3111579B1 (fr) Procédé et appareil de déclenchement d&#39;un rapport d&#39;état d&#39;accusé de réception dans un système de communication sans fil
EP2952035B1 (fr) Procédé et appareil pour transmettre un rapport d&#39;état de commande de liaison radio dans un système de communication basé sur de multiples technologies d&#39;accès radio
EP3310091A1 (fr) Station de base secondaire, station mobile, procédé de commande de communication et station de base maître
HK1218677A1 (zh) 协议数据单元的递送
CN110235398A (zh) 用于部分重传的方法
TW200935812A (en) Status reporting for retransmission protocol
KR20150139599A (ko) 무선 통신 시스템, 이동국, 기지국 및 무선 통신 방법
EP3319257B1 (fr) Reconfiguration de porteuse sans perte à partir de l&#39;utilisation d&#39;un numéro de séquence plus longue à plus courte
WO2016049850A1 (fr) Procédé de transmission de données de liaison montante et dispositif associé
WO2016127666A1 (fr) Procédé de délestage de paquets de données rlc, et station de base
WO2015176748A1 (fr) Indication d&#39;état de fenêtre de réception pour une unité de données en paquets
TWI607635B (zh) 處理用於非執照頻帶的混合自動重傳請求運作的裝置及方法
US20120201151A1 (en) Layer 2 ACK And NACK Status Reporting
JP6685295B2 (ja) 基地局
TWI674024B (zh) 處理雙連結中承載改變的裝置及方法
TWI660644B (zh) 處理一交遞的裝置
EP3484081B1 (fr) Procédé et dispositif de retransmission de données
WO2016189978A1 (fr) Dispositif d&#39;utilisateur et station de base
US10396966B2 (en) Per-protocol data unit delivery-path indication
EP3718231B1 (fr) Algorithme harq amélioré pour liaisons à grand temps de propagation aller-retour

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

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

Country of ref document: EP

Kind code of ref document: A1