Mechanism for radio link failure trigger
By generating RLC status reports and adjusting RLF triggers based on PDCP layer indications, the mechanism addresses unnecessary RLC retransmissions and improper RLF triggers, optimizing network performance and reducing latency in communication networks.
Patent Information
- Application Number
- PCT/EP2026/060639
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-13
- Publication Date
- 2026-11-12
AI Technical Summary
Current communication networks face issues with unnecessary radio link control (RLC) retransmissions and improper radio link failure (RLF) triggers, particularly in low latency applications, leading to resource wastage, increased latency, and frequent RLF procedures.
Implementing a mechanism where a receiving side RLC entity generates RLC status reports based on indications from the PDCP layer, allowing for quick identification of PDUs no longer expected by upper layers, and adjusting RLF triggers using timers and counters to avoid unnecessary retransmissions and ensure proper RLF triggers.
This approach reduces unnecessary RLC retransmissions, conserves radio resources, minimizes latency, and maintains efficient network connectivity by avoiding frequent RLF triggers, thus enhancing user experience and network efficiency.
Smart Images

Figure EP2026060639_12112026_PF_FP_ABST
Abstract
Description
MECHANISM FOR RADIO LINK FAILURE TRIGGERFIELD
[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for avoiding unnecessary radio link control (RLC) retransmission and ensuring proper radio link failure (RLF) triggers.BACKGROUND
[0002] In a communication network, the packet data convergence protocol (PDCP) layer is responsible for in-order packet delivery. The reordering mechanism in the PDCP layer buffers a received service data unit (SDU). The PDCP layer refrains from forwarding the SDU to higher layers until all SDUs with lower sequence numbers have been successfully delivered.
[0003] When the PDCP entity detects a missed packet, the PDCP entity initiates the t-Reordering timer. Until this timer expires, the PDCP entity awaits the recovery of the missed packet through the radio link control (RLC) automatic repeat request (ARQ) or hybrid automatic repeat request (HARQ) retransmission mechanism. The RLC layer plays a role in recovering the missed packet by sending a status report to the transmitter entity.
[0004] Once the t-Reordering timer expires, the PDCP entity discards any packets that were recovered after that point. For each retransmission of a packet by the transmitting RLC entity, a retransmission counter is incremented. When this counter reaches the configured threshold value (“maxRetxThreshold”), an RLF is triggered.SUMMARY
[0005] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to: receive, at a first layer of the first apparatus from a second layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer; and based on the first indication, start, at the first layer, a second timer for triggering a radio link failure, RLF.
[0006] In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to: transmit, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0007] In a third aspect of the present disclosure, there is provided a method. The methodcomprises: receiving, at a first layer of the first apparatus from a second layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer; and based on the first indication, starting at the first layer, a second timer for triggering a radio link failure, RLF.
[0008] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0009] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, at a first layer of the first apparatus from a second layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer; and means for based on the first indication, starting at the first layer, a second timer for triggering a radio link failure, RLF.
[0010] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0011] In a seventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third aspect.
[0012] In an eighth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.
[0013] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0015] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0016] FIG. 2A to FIG. 2F illustrate a schematic diagram of RLC and packet data convergence protocol (PDCP) receiver window operations;
[0017] FIG. 3 illustrates a signalling flow of a radio resource control (RRC) based RLF recovery procedure;
[0018] FIG. 4 illustrates an example signalling flow of a communication between the first apparatus and the second apparatus in accordance with some example embodiments of the present disclosure;
[0019] FIG. 5 illustrates another example signalling flow of a communication between the first apparatus and the second apparatus in accordance with some example embodiments of the present disclosure;
[0020] FIG. 6 illustrates an example signalling flow of the proposed mechanism for avoiding unnecessary RLC retransmission and ensuring proper RLF triggers in accordance with some example embodiments of the present disclosure;
[0021] FIG. 7 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0022] FIG. 8 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0023] FIG. 9 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0024] FIG. 10 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0025] FIG. 11 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0026] FIG. 12 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0027] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0028] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0030] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature,structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0031] It shall be understood that although the terms “first,” “second,”..., etc. in front of noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0032] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0033] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0034] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0035] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry) and(b) combinations of hardware ci rcuit(s) and software, such as (as applicable):(i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and(ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause anapparatus, such as a mobile device, computing device, or server, to perform various functions) and(c) any or all portions hardware circuit(s), such as a microprocessor(s), processor(s) and / or quantum processor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0036] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0037] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0038] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. AnIAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0039] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.
[0040] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0041] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 100, a plurality of communication devices, including a terminal device 110 and a network device 120, can communicate with each other. In the example of FIG. 1, the terminal device 110 may be a UE and the network device 120 may be a base station serving the UE. The serving area of the network device 120 may be called a cell 102.
[0042] It is to be understood that the number of devices and their connections shown in FIG. 1 areonly for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the network device 120 may be another device than a network device. Although illustrated as a terminal device, the terminal device 110 may be another device than a terminal device.
[0043] In the following, for the purpose of illustration, some example embodiments are described with the terminal device 110 operating as a UE and the network device 120 operating as a base station. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.
[0044] In some example embodiments, a transmission direction from the network device 120 to the terminal device 110 is referred to as a downlink (DL), while a transmission direction from the terminal device 110 to the network device 120 is referred to as an uplink (UL). In DL, the network device 120 is a transmitting (TX) device (or a transmitter) and the terminal device 110 is a receiving (RX) device (or a receiver). In UL, the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver).
[0045] Communications in the communication environment 100 may be implemented according to any proper communication protocol (s), comprising, but not limited to, cellular communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0046] Currently, in the communication network, the in-order delivery of packet is performed by the PDCP layer. Reordering mechanism buffers a received service data unit (SDU) and does not forward it to higher layers until all lower numbered SDUs have been delivered. Once a missed packet is detected by the PDCP entity, it may start t-Reordering timer and until the timer is expired PDCP may wait for the missed packets to be recovered by RLC or hybrid automatic repeat request (HARQ) retransmission mechanism. RLC layer may recover the missed packets by sending its status report to the transmitter entity. The packets recovered after t-Reordering timer expiry may be discarded by thePDCP entity. For each retransmission of a packet by transmitting RLC entity, the retransmission counter is incremented, and when the retransmission counter reaches the threshold limit “maxRetxThreshold” which is configured by the gNB, a radio link failure may be triggered.
[0047] With expected significant rise in latency critical applications, the end-to-end delay of packets is expected to be low. It is reasonable to expect that such applications (low latency applications) may have lower values of t-Reordering timer configured at PDCP layer based on the application requirements.
[0048] RLF at L2 layer is triggered by RLC layer based on “maxRetxThreshold” value. When a packet is retransmitted for maxRetxThreshold times, RLF may be triggered. When maxRetxThreshold is configured as small values to match t-Reordering timer at PDCP layer, for example, for low latency applications, this may lead to issues like early and / or unwanted triggering of RLF. Triggering of RLF at RLC layer initiates L3 (RRC) procedure.
[0049] FIG. 2A to FIG. 2F illustrate a schematic diagram of RLC and PDCP receiver window operations. In the following, as for RLC entity of the receiver (RX RLC), RX_NEXT may refer to a receive state variable which holds the value of the SN following the last in-sequence completely received RLC SDU, and it serves as the lower edge of the receiving window. RX_NEXT is initially set to 0, and is updated whenever the AM RLC entity receives an RLC SDU with SN equal to RX_NEXT. RX_NEXT_STATUS_TRIGGER may refer to a t-Reassembly state variable which holds the value of the SN following the SN of the RLC SDU which triggered t-Reassembly. RX_HIGHEST_STATUS may refer to a maximum status transmit state variable which holds the highest possible value of the SN which may be indicated by “ACK_SN” when a status PDU needs to be constructed. RX_HIGHEST_STATUS is initially set to 0. RX_NEXT_HIGHEST may refer to a highest received state variable which holds the value of the SN following the SN of the RLC SDU with the highest SN among received RLC SDUs. RX_NEXT_HIGHEST is initially set to 0.
[0050] As for PDCP entity of the receiver (RX PDCP), RX_NEXT may refer to a state variable indicates the count value of the next PDCP SDU expected to be received. The initial value of RX_NEXT is 0. RX_DELIV may refer to a state variable indicates the count value of the first PDCP SDU not delivered to the upper layers but still waited for. The initial value of RXJDELIV is 0. RX_REORD may refer to a state variable indicates the count value following the count value associated with the PDCP data PDU which triggered t-Reordering.
[0051] As shown in FIG. 2A, at point of time T1, the packet 210 is received at PDCP entity (RX PDCP) and RLC entity (RX RLC) of the receiver.
[0052] As shown in FIG. 2B, at point of time T2, the packet 210, packet 220 and packet 230 are received at the PDCP entity and RLC entity of the receiver. In this case, the RXJDELIV is updated to SN of packet 240.
[0053] As shown in FIG. 2C, at point of time T3, the packet 240 is not received at the PDCP entity and RLC entity of the receiver. Thus, in response to packet(s) with higher SN such as packet 250 and packet 260 are received, a t-Reorderi ng timer and a reassembly timer is started, the RX_DELIV is still pointed to SN of packet 240, RX_NEXT for RLC points to SN of packet 240, and RX_HIGHEST_STATUS points to SN of packet 240. In addition, RX.NEXT and RX.REORD for PDCP are updated to SN of packet 270.
[0054] As shown in FIG. 2D, at point of time T4, the t-Reorderi ng timer is running, the packet 240 is still not received and the packet 270 is not received at the PDCP entity and RLC entity of the receiver. The reassembly timer expires and a status reported is triggered, then the reassembly timer is started again. In this case, RXJDELIV holds on SN of packet 240, RX_NEXT for RLC holds on SN of packet 240, and RX_HIGHEST_STATUS is updated to SN of packet 270.
[0055] As shown in FIG. 2E, at point of time T5, the t-Reorderi ng timer is still running, the packet 240 and the packet 270 are still not received at the PDCP entity and RLC entity of the receiver. The RX-DELIV and RX.NEXT for RLC holds on SN of packet 240, and RX_HIGHEST_STATUS is updated.
[0056] As shown in FIG, 2F, at point of time T6, the t-Reordering timer is expired for packet 240, the packet 240 and the packet 270 are still not received at the PDCP entity and RLC entity of the receiver. The RX_DELIV is updated to SN of packet 270, but at RLC, RX_NEXT still holds on SN of packet 240 until it is recovered or RLF is triggered by transmitter RLC entity. This is not ideal when RLC max retransmission (maxRetxThreshold) is configured to lower values to match lower t-Reordering timer value.
[0057] With small values of t-Reordering timer, it is not an optimized behaviour to have large “maxRetxThreshold” value at RLC layer configured. Once the t-Reordering timer is expired at PDCP, the PDCP window is moved forward and the missed packets recovered by RLC after movement of the PDCP window may be discarded by PDCP due to those being out-of-window. This may lead to wastage of radio resources due to unnecessary RLC retransmission. In addition, due to such unnecessary retransmission, there may be delay for transmitting new packets, which may increase end-to-end latency of a packet.
[0058] It is not an optimized behaviour to have small “maxRetxThreshold” value either, as this may cause RLF to be triggered much frequently and early once there are “maxRetxThreshold” number of RLC retransmission for a packet. Therefore, there is a high probability that even for UE which is not in poor signalling coverage and which does not have real issues with RLC retransmissions, the RLF procedure may still end up being triggered very frequently.
[0059] The RLF causes layer 3 (L3) (i.e., RRC) procedure to be triggered for a recovery. FIG. 3 illustrates a signalling flow 300 of a RRC based RLF recovery procedure. As shown in FIG. 3, a UE 310 transmits (3010) a RRC reestablishment request to a network 320 to initiate the RRCreestablishment. After receiving the RRC reestablishment request, the network 320 transmits (3020) RRC reestablishment message to the UE 310. The RRC reestablishment message may include configuration information for the RRC reestablishment. After receiving the RRC reestablishment message from the network 320, the UE 310 performs the operation related to the RRC reestablishment and then transmits (3030) RRC reestablishment complete message to the network 320 to indicate that the RRC reestablishment is complete. Since the RRC based RLF recovery procedure is a costly and time-consuming procedure, unnecessarily invoking such a procedure for only a few numbers of RLC packet retransmissions may not only cause signalling overhead but also introduce unwanted delay and interruption, thereby increasing latency of packets.
[0060] Currently, it is not possible for bearers with small value of t-reordering timer configured, not to waste radio resources (for unnecessary retransmissions) and at the same time to ensure proper RLF triggers. If RLF triggers are too tight or eliminated entirely, unresolved radio link quality issues may cause extended periods of poor connectivity and performance degradation in user experience. If RLF triggers are too loose, it may result in frequent and unnecessary RLF and reconnection procedures, leading to delay in data delivery, unnecessary signalling overhead, thereby reducing network efficiency and user experience.
[0061] In accordance with some example embodiments of the present disclosure, there is provided a solution for avoiding unnecessary RLC retransmission and ensuring proper RLF triggers. In this solution, a receiving side RLC entity may generate RLC status reports based on an indication from PDCP layer. In addition, new triggering of RLF at RLC or PDCP layer is proposed. With the proposed solution, the receiving side RLC entity can quickly identify that a PDU is no longer expected by upper layer so it can indicate positive acknowledgement for the PDU when constructing a RLC status report. In this way, unnecessary retransmission can be avoided.
[0062] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0063] FIG. 4 illustrates an example signalling flow 400 of communication between the first apparatus 410 and the second apparatus 440 in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the signalling flow 400 will be described with reference to FIG. 1, for example, some example embodiments are described by using the terminal device 110 and the network device 120. In some example embodiments, the first apparatus 410 may include the terminal device 110 such as a UE, and the second apparatus 440 may include the network device 120 such as a base station or gNB serving the UE. In some other example embodiments, the first apparatus 410 may include the network device 120 such as a base station or gNB, and the second apparatus 440 may include the terminal device 110 such as a UE served by the gNB. The first apparatus 410 include a first layer 420 and a second layer 430, and the second layer 430 is upperthan the first layer 420 in the user plane protocol stack. In some examples, the first layer 420 may be a RLC layer, and the second layer 430 may be a PDCP layer. It is noted that the first layer 420 may be any proper layer other than RLC layer and the second layer 430 may be any proper layer other than PDCP layer.
[0064] For example, the first layer may be referred to as a first protocol layer. For example, the second layer may be referred to as a second protocol layer.
[0065] The first apparatus 410 may obtain a set of parameters for a timer (referred to as “second timer” hereinafter) for triggering a RLF and a counter for triggering the RLF. In some example embodiments, the set of parameters may be predetermined or preconfigured. Alternatively, the first apparatus 410 may receive (4010) the set of parameters for the second timer and the counter for triggering the RLF from the second apparatus 440. For example, the set of parameters may be received via one of: RRC message or medium access control, MAC, control element, CE. The set of parameters may include a first threshold for the counter for triggering the RLF and / or an expiring time of the second timer for triggering the RLF.
[0066] In some example embodiments, the second apparatus 440 may transmit (4020) a set of data units, and at least one data unit in the set of data units is not received by the first apparatus 410. If the at least one data unit is not received before a first timer for the at least one data unit at the second layer 430 expires, the second layer 430 of the first apparatus 410 transmits (4030) a first indication to the first layer 420 of the first apparatus 410. In other words, the first layer 420 receives (4030) the first indication from the second layer 430. In this case, the first indication indicates that the first timer for the at least one data unit at the second layer 430 has expired.
[0067] Moreover, the first layer 420 starts (4040) the second timer for triggering the RLF based on the first indication. In some example embodiments, based on a reception of the first indication from the second layer 430, the first layer 420 may increase (4050) a value of a counter for triggering the RLF by a predetermined number. For example, the value of the counter is set to 0 before receiving the first indication, and after receiving the first indication, the value of the counter is increased by 1. In some other example embodiments, based on a reception of a second indication from the second layer 430, the first layer 420 may increase the value of the counter by the predetermined number. In this case, the second indication may indicate that the first timer for another data unit at the second layer 430 has expired.
[0068] In some example embodiments, based on the first indication, the first layer 420 may determine (4060) that the at least one data unit is considered as received at the first layer 420. In addition, the first layer 420 may refrain (4070) from triggering a retransmission of the at least one data unit based on the determining. In this way, unnecessary retransmission can be avoided.
[0069] In some example embodiments, if the second timer for triggering the RLF expires and thevalue of the counter for triggering the RLF is smaller than a first threshold, the first layer 420 may determine that the RLF is not triggered. Moreover, the first layer 420 may reset the second timer and the counter for triggering the RLF. In this way, unnecessary retransmission can be avoided.
[0070] In some other example embodiments, if the value of the counter for triggering the RLF reaches or exceeds the first threshold before the second timer for triggering the RLF expires, the first layer 420 may trigger the RLF. Moreover, the first layer 420 may reset the second timer and the counter for triggering the RLF. In this way, proper RLF can be triggered.
[0071] In some example embodiments, the first layer 420 may trigger (4080) a status report. The first layer 420 may generate (4090) the status report which indicates that data units up to the at least one data unit have been received by the first apparatus 410. In this case, data units up to the at least one data unit may refer to data units with sequence number (SN) not larger than the SN of the at least one data unit. For example, if the SN of the at least one data unit is 10, the data units up to the at least one data unit may include data units with SN not larger than 10. For example, SN not larger than 10 comprises the following sequence numbers: 10, 9, 8, 7, etc. It means that data units up to the at least one data unit also include the at least one data unit. Furthermore, the first layer 420 may transmit (4100) the status report to the second apparatus 440. In this way, it can avoid wasting transmission resources.
[0072] In some example embodiments, the first indication may include a highest SN among a set of unreceived data units within a reordering window defined by the first timer. For example, the first indication may include the highest PDCP SN among the PDCP SNs of which corresponding PDCP PDUs have not been received. For example, if the SNs of unreceived PDCP PDUs include 5, 7 and 9, the first indication may include 9 which is the highest SN among the unreceived data units. Alternatively, the first indication may include a SN corresponding to an unreceived data unit within the reordering window defined by the first timer. As an example, the first indication may include one PDCP SN corresponds to a PDCP PDU has not been received.
[0073] In some example embodiments, the first layer 420 may determine a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived data unit. Moreover, the first layer 420 may determine that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first layer 420. In addition, the first layer 420 may generate a status report indicating positive acknowledgement for SNs of the set of data units. For example, the first layer 420 may set positive acknowledgement for SNs of the set of data units.
[0074] In some example embodiments, if a delay-sensitive application is running on the first apparatus 410, the first apparatus 410 may determine to apply the second timer for triggering the radio link failure. In some other example embodiments, if a delay-sensitive application is not running on thefirst apparatus 410, the first apparatus 410 may determine not to apply the second timer for triggering the radio link failure or stop applying the second timer. In other words, the first layer 420 and the second layer 430 may be configured or activated to apply the proposed mechanism when a delaysensitive application is running. Conversely, the proposed mechanism may be deactivated if the delaysensitive application is not running.
[0075] In some other example embodiments, if the first apparatus 410 is a network device and the second apparatus 440 is a terminal device, the first apparatus 410 may determine whether the application is delay-sensitive based on information from the second apparatus 440 and / or core network. For example, when launching an application data session, the second apparatus 440 may send a PDU establishment request to the first apparatus 410 or another core network entity, including a corresponding 5QI (5G QoS identifier). Based on the 5QI, the first apparatus 410 may determine whether the QoS flow is delay-sensitive. Alternatively, this information may be provided by core network such as application function.
[0076] FIG. 5 illustrates an example signalling flow 500 of communication between the first apparatus 510 and the second apparatus 540 in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the signalling flow 500 will be described with reference to FIG. 1, for example, some example embodiments are described by using the terminal device 110 and the network device 120. In some example embodiments, the first apparatus 510 may include the terminal device 110 such as a UE, and the second apparatus 540 may include the network device 120 such as a base station or gNB serving the UE. In some other example embodiments, the first apparatus 510 may include the network device 120 such as a base station or gNB, and the second apparatus 540 may include the terminal device 110 such as a UE served by the gNB. The first apparatus 510 include a first layer 520 and a second layer 530, and the second layer 530 is upper than the first layer 520 in the user plane protocol stack. In some examples, the first layer 520 may be a RLC layer, and the second layer 530 may be a PDCP layer. It is noted that the first layer 420 may be any proper layers other than RLC layer and the second layer 430 may be any proper layers other than PDCP layer.
[0077] The first apparatus 510 may obtain a set of parameters for a timer (referred to as “second timer” hereinafter) for triggering a RLF and a counter for triggering the RLF. In some example embodiments, the set of parameters may be predetermined. Alternatively, the first apparatus 510 may receive (5010) the set of parameters for the second timer and the counter for triggering the RLF from the second apparatus 540. For example, the set of parameters may be received via one of RRC signalling or MAC CE. The set of parameters may include a first threshold for the counter for triggering the RLF and / or an expiring time of the second timer for triggering the RLF.
[0078] In some example embodiments, the second apparatus 520 may transmit (5020) a set of dataunits to the first apparatus 510, and at least one data unit in the set of data units is not received by the first apparatus 510. If a first timer for the at least one data unit at the second layer 530 expires, the second layer 530 starts (5030) the second timer for triggering the RLF. In some example embodiments, if the first timer expires, the second layer 530 may increase (5040) a value of a counter for triggering the RLF by a predetermined number. For example, the value of the counter is set to 0 before the first timer expires, and after the first timer expires, the value of the counter is increased by 1. In some other example embodiments, if the first timer for another data unit at the second layer 530, the second layer 530 may increase the value of the counter by the predetermined number.
[0079] In some example embodiments, if the first timer expires, the first apparatus 510 may perform a transmission of a first indication from the second layer 530 to the first layer 520. In other words, the first layer 520 may receive (5050) a first indication from the second layer 530. In this case, the first indication indicates that the first timer for the at least one data unit at the second layer 530 has expired. Moreover, based on the first indication, the first layer 520 may determine (5060) that the at least one data unit is considered as received at the first layer 520. In addition, the first layer 520 may refrain (5070) from triggering a retransmission of the at least one data unit based on the determining. In this way, unnecessary retransmission can be avoided.
[0080] In some example embodiments, if the second timer for triggering the RLF expires and the value of the counter for triggering the RLF is smaller than a first threshold, the second layer 530 may determine that the RLF is not triggered. Moreover, the second layer 530 may reset the second timer and the counter for triggering the RLF. In this way, unnecessary retransmission can be avoided.
[0081] In some other example embodiments, if the value of the counter for triggering the RLF reaches or exceeds the first threshold before the second timer for triggering the RLF expires, the second layer 530 may trigger the RLF. Moreover, the second layer 530 may reset the second timer and the counter for triggering the RLF. In this way, proper RLF can be triggered.
[0082] In some example embodiments, the first layer 520 may trigger (5080) a status report. The first layer 520 may generate (5090) the status report which indicates that data units up to the at least one data unit have been received by the first apparatus 510. In this case, data units up to the at least one data unit may refer to data units with SN not larger than the SN of the at least one data unit. It means that data units up to the at least one data unit also include the at least one data unit. Furthermore, first layer 520 may transmit (5100) the status report to the second apparatus 540. In this way, unnecessary retransmission can be avoided.
[0083] In some example embodiments, the first indication may include a highest SN among a set of unreceived data units within a reordering window defined by the first timer. For example, the first indication may include the highest PDCP SN among the PDCP SNs of which corresponding PDCP PDUs have not been received. Alternatively, the first indication may include a SN corresponding to anunreceived data unit within the reordering window defined by the first timer. As an example, the first indication may include one PDCP SN corresponds to a PDCP PDU has not been received.
[0084] In some example embodiments, the first layer 520 may determine a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived data unit. Moreover, the first layer 520 may determine that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first layer 520. In addition, the first layer 520 may generate a status report indicating positive acknowledgement for the SNs of the set of data units. For example, the first layer 520 may set positive acknowledgement for the SNs of the set of data units.
[0085] In some example embodiments, if a delay-sensitive application is running on the first apparatus 510, the first apparatus 510 may determine to apply the second timer for triggering the radio link failure. In some other example embodiments, if a delay-sensitive application is not running on the first apparatus 510, the first apparatus 510 may determine not to apply the second timer for triggering the radio link failure or stop applying the second timer. In other words, the first layer 520 and the second layer 530 may be configured or activated to apply the proposed mechanism when a delaysensitive application is running. Conversely, the proposed mechanism may be deactivated if the delaysensitive application is not running.
[0086] In some other example embodiments, if the first apparatus 510 is a network device and the second apparatus 540 is a terminal device, the first apparatus 510 may determine whether the application is delay-sensitive based on information from the second apparatus 540 or core network. For example, when launching an application data session, the second apparatus 540 may send a PDU establishment request to the first apparatus 510 or another core network entity, including a corresponding 5QI (5G QoS identifier). Based on the 5QI, the first apparatus 510 may determine whether the QoS flow is delay-sensitive. Alternatively, this information may be provided by core network such as application function.
[0087] FIG. 6 illustrates an example signalling flow 600 of the proposed mechanism for avoiding unnecessary RLC retransmission and ensuring proper RLF triggers in accordance with some example embodiments of the present disclosure. The example signalling flow 600 is an implementation of the example signalling flow 400 of FIG. 4 or the example signalling flow 500 of FIG. 5. In particular, in the example embodiments discussed with respect to FIG. 4, a transmitting device 610 is an example of the second apparatus 440 shown in FIG. 4, and a receiving device 620 is an example of the first apparatus 410 shown in FIG. 4. In addition, a RLC entity 630 in the receiving device 620 is an example of the first layer 420 in the first apparatus 410, and a PDCP entity 640 in the receiving device 620 is an example of the second layer 430 in the first apparatus 410. In the example embodiments discussed with respect to FIG. 5, a transmitting device 610 is an example of the second apparatus 540 shownin FIG. 5, and a receiving device 620 is an example of the first apparatus 510 shown in FIG. 5. In addition, a RLC entity 630 in the receiving device 620 is an instance of the first layer 520 in the first apparatus 510, and a PDCP entity 640 in the receiving device 620 is an instance of the second layer 530 in the first apparatus 510. For example, the RLC entity 630 may be referred to as a receiving side of the RLC within the first layer 520 in the first apparatus 510. For example, the PDCP entity 640 may be referred to as a receiving PDCP entity within the second layer 530 in the first apparatus 510.
[0088] As shown in FIG. 6, the PDCP entity 640 and the RLC entity 630 are configured (6010) to apply the proposed mechanism. In this case, the PDCP entity 640 is configured to send an indication to the RLC entity 630 when the t-Reordering timer regarding at least one unreceived RLC PDU expires. The RLC entity 630 is configured to consider that at least one unreceived RLC SDU has been received when receiving an indication from the upper layer, that is, PDCP entity 640, and the indication indicates that the t-Reordering timer for this at least one unreceived RLC SDU has expired. I n addition, the PDCP entity 640 or the RLC entity 630 is further configured to start RLF trigger timer and count, with two parameters t-RLFtriggering and maxReorderingExp.
[0089] Then transmitting device 610 transmits (6020) a set of data units to the receiving device 620, the set of data units includes RLC PDU #k and RLC PDUs with SN greater and smaller than #k, and at least the RLC PDU #k is not received by the receiving device 620. The t-Reordering regarding at least one unreceived RLC PDU, for example, PDU #k, expires (6030) at the PDCP entity 6040. Furthermore, the PDCP entity 6040 indicates (6040) RLC entity 630 that the t-Reordering regarding the unreceived RLC PDU #k expires. After receiving the indication, the RLC entity 630 considers (6050) the unreceived RLC PDU #k has been received even though it hasn’t been received actually.
[0090] In one option for RLF triggered at RLC entity 630, the RLC entity 630 starts (6060) t-RLFtriggering timer when receiving the indication and increments the count each time such an indication is received. If the t-RLFtriggering timer expires and the count for such indications does not reach maxReorderingExp, the RLC entity 630 may determine (6070A) that RLF is not triggered, and both timer and count are reset. Alternatively, if the count for such indications reaches or exceeds maxReorderingExp before the t-RLFtriggering timer expires, the RLC entity 630 may determine (6070B) that RLF is triggered at RLC entity, and both timer and count are reset.
[0091] In another option for RLF triggered at the PDCP entity 640, the PDCP entity 640 starts (6080) t-RLFtriggering timer when the t-Reordering regarding at least one unreceived RLC PDU expires and increments the count each time the t-Reordering expires. If the t-RLFtriggering timer expires and the count for t-Reordering expirations does not reach maxReorderingExp, the PDCP entity 640 may determine (6090A) that RLF is not triggered, and both timer and count are reset. Alternatively, if the count for t-Reordering expirations reaches or exceeds maxReorderingExp before the t-RLFtriggering timer expires, the PDCP entity 640 may determine (6090B) that RLF is triggered at the PDCP entity640, and both timer and count are reset.
[0092] The RLC status report may be trigged (6100) at the RLC entity 630. The RLC entity 630 may then construct (6110) a RLC status report with setting positive acknowledgement for SN of RLC PDU #k. In addition, the RLC entity 630 transmits (6120) the RLC status report to the transmitting device 610. The transmitting device 610 may determine (6130) that there is no need to retransmit RLC PDU #k.
[0093] FIG. 7 shows a flowchart of an example method 700 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the terminal device 110 or network device 120 in FIG. 1.
[0094] At block 710, a first layer of the first apparatus receives from a second layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer.
[0095] At block 720, based on the first indication, the first layer starts a second timer for triggering a radio link failure, RLF.
[0096] In some example embodiments, the method 700 further comprises: determining, at the first layer based on the first indication, that the at least one data unit is considered as received at the first layer; and based on the determining, refraining at the first layer, from triggering a retransmission of the at least one data unit.
[0097] In some example embodiments, the method 700 further comprises: based on a reception of the first indication or a second indication from the second layer of the first apparatus, increasing at the first layer, a value of a counter for triggering the RLF by a predetermined number, wherein the second indication indicates that the first timer for another data unit at the second layer of the first apparatus has expired.
[0098] In some example embodiments, the method 700 further comprises: in accordance with a determination that the second timer for triggering the RLF expires and the value of the counter for triggering the RLF is smaller than a first threshold, determining, at the first layer, that the RLF is not triggered; and resetting, at the first layer, the second timer and the counter for triggering the RLF.
[0099] In some example embodiments, the method 700 further comprises: in accordance with a determination that the value of the counter for triggering the RLF reaches or exceeds a first threshold before the second timer for triggering the RLF expires, triggering the RLF by the first layer; and resetting, at the first layer, the second timer and the counter for triggering the RLF.
[0100] In some example embodiments, the method 700 further comprises: triggering a status report by the first layer of the first apparatus; generating, at the first layer, the status report indicating that data units up to the at least one data unit have been received by the first apparatus; and transmitting,to a second apparatus, the status report.
[0101] In some example embodiments, the method 700 further comprises: receiving, from a second apparatus, a set of data units excluding the at least one data unit; and in accordance with a determination that the at least one data unit is not received before the first timer expires, performing a transmission of the first indication from the second layer of the first apparatus to the first layer of the first apparatus.
[0102] In some example embodiments, the first indication comprises a highest sequence number, SN, among a set of unreceived data units within a reordering window defined by the first timer. Alternatively, the first indication comprises an SN corresponding to an unreceived data unit within the reordering window defined by the first timer.
[0103] In some example embodiments, the method 700 further comprises: determining, at the first layer of the first apparatus, a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived data unit; determining, at the first layer, that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first layer; and generating, at the first layer, a status report indicating positive acknowledgement for SNs of the set of data units.
[0104] In some example embodiments, the method 700 further comprises: in accordance with a determination that a delay-sensitive application is running on the first apparatus, determining at the first layer, to apply the second timer for triggering the radio link failure; or in accordance with a determination that a delay-sensitive application is not running on the first apparatus, determining not to apply the second timer for triggering the radio link failure.
[0105] In some example embodiments, a set of parameters for the second timer and the counter for triggering the RLF are predetermined, wherein the set of parameters comprise at least one of: the first threshold for the counter for triggering the RLF, or an expiring time of the second timer for triggering the RLF.
[0106] In some example embodiments, the method 700 further comprises: receiving, from a second apparatus, a set of parameters for the second timer and the counter for triggering the RLF, wherein the set of parameters comprise at least one of: an expiring time of the second timer for triggering the RLF, or the first threshold for the counter for triggering the RLF.
[0107] In some example embodiments, the set of parameters is received via one of: radio resource control, RRC, or medium access control, MAC, control element, CE.
[0108] In some example embodiments, the first layer is a radio link control, RLC, layer, and the second layer is a packet data convergence protocol, PDCP, layer.
[0109] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device, or wherein the first apparatus comprises a networkdevice and the second apparatus comprises a terminal device.
[0110] FIG. 8 shows a flowchart of an example method 800 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the terminal device 110 or network device 120 in FIG. 1.
[0111] At block 810, the second apparatus transmits to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0112] FIG. 9 shows a flowchart of an example method 900 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the terminal device 110 or network device 120 in FIG. 1.
[0113] At block 910, in accordance with a determination that a first timer for at least one data unit at a second layer of the first apparatus expires, the second layer of the first apparatus starts a second timer for triggering a radio link failure, RLF.
[0114] In some example embodiments, the method 900 further comprises: receiving, at a first layer of the first apparatus from the second layer of the first apparatus, a first indication indicating that the first timer for the at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer; determining, at the first layer based on the first indication, that the at least one data unit is considered as received at the first layer; and based on the determining, refraining at the first layer, from triggering a retransmission of the at least one data unit.
[0115] In some example embodiments, the method 900 further comprises: in accordance with a determination that the first timer for the at least one data unit at the second layer of the first apparatus expires or the first timer for another data unit at the second layer of the first apparatus expires, increasing at the second layer, a value of a counter for triggering the RLF by a predetermined number.
[0116] In some example embodiments, the method 900 further comprises: in accordance with a determination that the second timer for triggering the RLF expires and the value of the counter for triggering the RLF is smaller than a first threshold, determining, at the second layer, that the RLF is not triggered; and resetting, at the second layer, the second timer and the counter for triggering the RLF.
[0117] In some example embodiments, the method 900 further comprises: in accordance with a determination that the value of the counter for triggering the RLF reaches or exceeds a first threshold before the second timer for triggering the RLF expires, triggering the RLF by the second layer; and resetting, at the second layer, the second timer and the counter for triggering the RLF.
[0118] In some example embodiments, the method 900 further comprises: triggering a status report by the first layer of the first apparatus; generating the status report indicating that data units up to the at least one data unit have been received by the first apparatus; and transmitting, to a second apparatus, the status report.
[0119] In some example embodiments, the method 900 further comprises: receiving, from a second apparatus, a set of data units excluding the at least one data unit; and in accordance with a determination that the at least one data unit is not received before the first timer expires, performing a transmission of the first indication from the second layer of the first apparatus to the first layer of the first apparatus.
[0120] In some example embodiments, the first indication comprises a highest sequence number, SN, among a set of unreceived data units within a reordering window defined by the first timer. Alternatively, the first indication comprises an SN corresponding to an unreceived data unit within the reordering window defined by the first timer.
[0121] In some example embodiments, the method 900 further comprises: determining, at the first layer of the first apparatus, a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived unit; determining that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first layer; and generating a status report indicating positive acknowledgement for SNs of the set of data units.
[0122] In some example embodiments, the method 900 further comprises: in accordance with a determination that a delay-sensitive application is running on the first apparatus, determining at the second layer, to apply the second timer for triggering the radio link failure; or in accordance with a determination that a delay-sensitive application is not running on the first apparatus, determining not to apply the second timer for triggering the radio link failure.
[0123] In some example embodiments, a set of parameters for the second timer and the counter for triggering the RLF are predetermined, wherein the set of parameters comprise at least one of: the first threshold for the counter for triggering the RLF, or an expiring time of the second timer for triggering the RLF.
[0124] In some example embodiments, the method 900 further comprises: receiving, from a second apparatus, a set of parameters for the second timer and the counter for triggering the RLF, wherein the set of parameters comprise at least one of: an expiring time of the second timer for triggering the RLF, or the first threshold for the counter for triggering the RLF.
[0125] In some example embodiments, the set of parameters is received via one of: radio resource control, RRC, or medium access control, MAC, control element, CE.
[0126] In some example embodiments, the first layer is a radio link control, RLC, layer, and the second layer is a packet data convergence protocol, PDCP, layer.
[0127] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device, or wherein the first apparatus comprises a network device and the second apparatus comprises a terminal device.
[0128] FIG. 10 shows a flowchart of an example method 1000 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the terminal device 110 or network device 120 in FIG. 1.
[0129] At block 1010, the second apparatus transmits, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0130] In some example embodiments, a first apparatus capable of performing any of the method 700 (for example, the terminal device 110 or network device 120 in FIG. 1 ) may comprise means for performing the respective operations of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the terminal device 110 or network device 120 in FIG. 1.
[0131] In some example embodiments, the first apparatus comprises means for receiving, at a first layer of the first apparatus from a second layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer; and means for based on the first indication, starting at the first layer, a second timer for triggering a radio link failure, RLF.
[0132] In some example embodiments, the first apparatus further comprises: means for determining, at the first layer based on the first indication, that the at least one data unit is considered as received at the first layer; and means for based on the determining, refraining at the first layer, from triggering a retransmission of the at least one data unit.
[0133] In some example embodiments, the first apparatus further comprises: means for based on a reception of the first indication or a second indication from the second layer of the first apparatus, increasing at the first layer, a value of a counter for triggering the RLF by a predetermined number, wherein the second indication indicates that the first timer for another data unit at the second layer of the first apparatus has expired.
[0134] In some example embodiments, the first apparatus further comprises: in accordance with a determination that the second timer for triggering the RLF expires and the value of the counter for triggering the RLF is smaller than a first threshold, means for determining, at the first layer, that the RLF is not triggered; and means for resetting, at the first layer, the second timer and the counter fortriggering the RLF.
[0135] In some example embodiments, the first apparatus further comprises: in accordance with a determination that the value of the counter for triggering the RLF reaches or exceeds a first threshold before the second timer for triggering the RLF expires, means for triggering the RLF by the first layer; and means for resetting, at the first layer, the second timer and the counter for triggering the RLF.
[0136] In some example embodiments, the first apparatus further comprises: means for triggering a status report by the first layer of the first apparatus; means for generating, at the first layer, the status report indicating that data units up to the at least one data unit have been received by the first apparatus; and means for transmitting, to a second apparatus, the status report.
[0137] In some example embodiments, the first apparatus further comprises: means for receiving, from a second apparatus, a set of data units excluding the at least one data unit; and means for in accordance with a determination that the at least one data unit is not received before the first timer expires, performing a transmission of the first indication from the second layer of the first apparatus to the first layer of the first apparatus.
[0138] In some example embodiments, the first indication comprises a highest sequence number, SN, among a set of unreceived data units within a reordering window defined by the first timer, or wherein the first indication comprises an SN corresponding to an unreceived data unit within the reordering window defined by the first timer.
[0139] In some example embodiments, the first apparatus further comprises: means for determining, at the first layer of the first apparatus, a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived data unit; means for determining, at the first layer, that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first layer; and means for generating, at the first layer, a status report indicating positive acknowledgement for SNs of the set of data units.
[0140] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that a delay-sensitive application is running on the first apparatus, determining at the first layer, to apply the second timer for triggering the radio link failure; or means for in accordance with a determination that a delay-sensitive application is not running on the first apparatus, determining not to apply the second timer for triggering the radio link failure.
[0141] In some example embodiments, a set of parameters for the second timer and the counter for triggering the RLF are predetermined. Alternatively, the set of parameters comprise at least one of: the first threshold for the counter for triggering the RLF, or an expiring time of the second timer for triggering the RLF.
[0142] In some example embodiments, the first apparatus further comprises: means for receiving, from a second apparatus, a set of parameters for the second timer and the counter for triggering theRLF, wherein the set of parameters comprise at least one of: an expiring time of the second timer for triggering the RLF, or the first threshold for the counter for triggering the RLF.
[0143] In some example embodiments, the set of parameters is received via one of: radio resource control, RRC, or medium access control, MAC, control element, CE.
[0144] In some example embodiments, the first layer is a radio link control, RLC, layer, and the second layer is a packet data convergence protocol, PDCP, layer.
[0145] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device, or wherein the first apparatus comprises a network device and the second apparatus comprises a terminal device.
[0146] In some example embodiments, a second apparatus capable of performing any of the method 800 (for example, the terminal device 110 or network device 120 in FIG. 1 ) may comprise means for performing the respective operations of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the terminal device 110 or network device 120 in FIG. 1.
[0147] In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0148] In some example embodiments, a first apparatus capable of performing any of the method 900 (for example, the terminal device 110 or network device 120 in FIG. 1 ) may comprise means for performing the respective operations of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the terminal device 110 or network device 120 in FIG. 1.
[0149] In some example embodiments, the first apparatus comprises means for in accordance with a determination that a first timer for at least one data unit at a second layer of the first apparatus expires, starting a second timer for triggering a radio link failure, RLF, at the second layer of the first apparatus.
[0150] In some example embodiments, the first apparatus further comprises: means for receiving, at a first layer of the first apparatus from the second layer of the first apparatus, a first indication indicating that the first timer for the at least one data unit at the second layer has expired, wherein the second layer is upper than the first layer; means for determining, at the first layer based on the first indication, that the at least one data unit is considered as received at the first layer; and means for based on the determining, refraining at the first layer, from triggering a retransmission of the at leastone data unit.
[0151] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that the first timer for the at least one data unit at the second layer of the first apparatus expires or the first timer for another data unit at the second layer of the first apparatus expires, increasing at the second layer, a value of a counter for triggering the RLF by a predetermined number.
[0152] In some example embodiments, the first apparatus further comprises: in accordance with a determination that the second timer for triggering the RLF expires and the value of the counter for triggering the RLF is smaller than a first threshold, means for determining, at the second layer, that the RLF is not triggered; and means for resetting, at the second layer, the second timer and the counter for triggering the RLF.
[0153] In some example embodiments, the first apparatus further comprises: in accordance with a determination that the value of the counter for triggering the RLF reaches or exceeds a first threshold before the second timer for triggering the RLF expires, means for triggering the RLF by the second layer; and means for resetting, at the second layer, the second timer and the counter for triggering the RLF.
[0154] In some example embodiments, the first apparatus further comprises: means for triggering a status report by the first layer of the first apparatus; means for generating the status report indicating that data units up to the at least one data unit have been received by the first apparatus; and means for transmitting, to a second apparatus, the status report.
[0155] In some example embodiments, the first apparatus further comprises: means for receiving, from a second apparatus, a set of data units excluding the at least one data unit; and means for in accordance with a determination that the at least one data unit is not received before the first timer expires, performing a transmission of the first indication from the second layer of the first apparatus to the first layer of the first apparatus.
[0156] In some example embodiments, the first indication comprises a highest sequence number, SN, among a set of unreceived data units within a reordering window defined by the first timer, or wherein the first indication comprises an SN corresponding to an unreceived data unit within the reordering window defined by the first timer.
[0157] In some example embodiments, the first apparatus further comprises: means for determining, at the first layer of the first apparatus, a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived unit; means for determining that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first layer; and means for generating a status report indicating positive acknowledgement for SNs of the set of data units.
[0158] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that a delay-sensitive application is running on the first apparatus, determining at the second layer, to apply the second timer for triggering the radio link failure; or means for in accordance with a determination that a delay-sensitive application is not running on the first apparatus, determining not to apply the second timer for triggering the radio link failure.
[0159] In some example embodiments, a set of parameters for the second timer and the counter for triggering the RLF are predetermined, wherein the set of parameters comprise at least one of: the first threshold for the counter for triggering the RLF, or an expiring time of the second timer for triggering the RLF.
[0160] In some example embodiments, the first apparatus further comprises: means for receiving, from a second apparatus, a set of parameters for the second timer and the counter for triggering the RLF, wherein the set of parameters comprise at least one of: an expiring time of the second timer for triggering the RLF, or the first threshold for the counter for triggering the RLF.
[0161] In some example embodiments, the set of parameters is received via one of: radio resource control, RRC, or medium access control, MAC, control element, CE.
[0162] In some example embodiments, the first layer is a radio link control, RLC, layer, and the second layer is a packet data convergence protocol, PDCP, layer.
[0163] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device, or wherein the first apparatus comprises a network device and the second apparatus comprises a terminal device.
[0164] In some example embodiments, a second apparatus capable of performing any of the method 1000 (for example, the terminal device 110 or network device 120 in FIG. 1 ) may comprise means for performing the respective operations of the method 1000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the terminal device 110 or network device 120 in FIG. 1.
[0165] In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
[0166] FIG. 11 is a simplified block diagram of a device 1100 that is suitable for implementing example embodiments of the present disclosure. The device 1100 may be provided to implement a communication device, for example, the terminal device 110 or the network device 120 as shown in FIG. 1. As shown, the device 1100 includes one or more processors 1110, one or more memories 1120 coupled to the processor 1110, and one or more communication modules 1140 coupled to theprocessor 1110.
[0167] The communication module 1140 is for bidirectional communications. The communication module 1140 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1140 may include at least one antenna.
[0168] The processor 1110 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0169] The memory 1120 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1124, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 1122 and other volatile memories that will not last in the power-down duration.
[0170] A computer program 1130 includes computer executable instructions that are executed by the associated processor 1110. The instructions of the program 1130 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1130 may be stored in the memory, e.g., the ROM 1124. The processor 1110 may perform any suitable actions and processing by loading the program 1130 into the RAM 1122.
[0171] The example embodiments of the present disclosure may be implemented by means of the program 1130 so that the device 1100 may perform any process of the disclosure as discussed with reference to FIG. 4 to FIG. 10. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0172] In some example embodiments, the program 1130 may be tangibly contained in a computer readable medium which may be included in the device 1100 (such as in the memory 1120) or other storage devices that are accessible by the device 1100. The device 1100 may load the program 1130 from the computer readable medium to the RAM 1122 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation ondata storage persistency (e.g., RAM vs. ROM).
[0173] FIG. 12 shows an example of the computer readable medium 1200 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1200 has the program 1130 stored thereon.
[0174] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0175] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machineexecutable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0176] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0177] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0178] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0179] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable subcombination.
[0180] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
29WHAT IS CLAIMED IS:
1. A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to:receive, at a first protocol layer of the first apparatus from a second protocol layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second protocol layer has expired, wherein the second protocol layer is upper than the first protocol layer; andbased on the first indication, start, at the first protocol layer, a second timer for triggering a radio link failure, RLF.
2. The first apparatus of claim 1, wherein the first apparatus is caused to:determine, at the first protocol layer based on the first indication, that the at least one data unit is considered as received at the first protocol layer; andbased on the determining, refrain, at the first protocol layer, from triggering a retransmission of the at least one data unit.
3. The first apparatus of claim 1 or 2, wherein the first apparatus is caused to:based on a reception of the first indication or a second indication from the second protocol layer of the first apparatus, increase, at the first protocol layer, a value of a counter for triggering the RLF by a predetermined number, wherein the second indication indicates that the first timer for another data unit at the second protocol layer of the first apparatus has expired.
4. The first apparatus of claim 3, wherein the first apparatus is caused to:in accordance with a determination that the second timer for triggering the RLF expires and the value of the counter for triggering the RLF is smaller than a first threshold,determine, at the first protocol layer, that the RLF is not triggered; andreset, at the first protocol layer, the second timer and the counter for triggering the RLF.
5. The first apparatus of claim 3, wherein the first apparatus is caused to:in accordance with a determination that the value of the counter for triggering the RLF reaches or exceeds a first threshold before the second timer for triggering the RLF expires,trigger the RLF by the first protocol layer; andreset, at the first protocol layer, the second timer and the counter for triggering the RLF.
6. The first apparatus of any preceding claim, wherein the first apparatus is caused to: trigger a status report by the first protocol layer of the first apparatus;generate, at the first protocol layer, the status report indicating that data units up to the at least one data unit have been received by the first apparatus; andtransmit, to a second apparatus, the status report.
7. The first apparatus of any preceding claim, wherein the first apparatus is caused to: receive, from a second apparatus, a set of data units excluding the at least one data unit; and in accordance with a determination that the at least one data unit is not received before the first timer expires, perform a transmission of the first indication from the second protocol layer of the first apparatus to the first protocol layer of the first apparatus.
8. The first apparatus of any preceding claim, wherein the first indication comprises a highest sequence number, SN, among a set of unreceived data units within a reordering window defined by the first timer, orwherein the first indication comprises an SN corresponding to an unreceived data unit within the reordering window defined by the first timer.
9. The first apparatus of any preceding claim, wherein the first apparatus is caused to: determine, at the first protocol layer of the first apparatus, a corresponding data unit SN based on a data unit SN in the first indication corresponding to an unreceived data unit;determine, at the first protocol layer, that a set of data units with SNs smaller than or equal to the corresponding data unit SN are considered to be received at the first protocol layer; and generate, at the first protocol layer, a status report indicating positive acknowledgement for SNs of the set of data units.
10. The first apparatus of any preceding claim, wherein the first apparatus is caused to: in accordance with a determination that a delay-sensitive application is running on the first apparatus, determine, at the first protocol layer, to apply the second timer for triggering the radio link failure; orin accordance with a determination that a delay-sensitive application is not running on the first apparatus, determine not to apply the second timer for triggering the radio link failure.
11. The first apparatus of any preceding claim, wherein a set of parameters for the second timer and the counter for triggering the RLF are predetermined, wherein the set of parameters comprise at least one of: the first threshold for the counter for triggering the RLF, or an expiring time of the second timer for triggering the RLF.
12. The first apparatus of any of claims 1 to 10, wherein the first apparatus is caused to: receive, from a second apparatus, a set of parameters for the second timer and the counter for triggering the RLF, wherein the set of parameters comprise at least one of: an expiring time of the second timer for triggering the RLF, or the first threshold for the counter for triggering the RLF.
13. The first apparatus of claim 12, wherein the set of parameters is received via one of: radio resource control, RRC, or medium access control, MAC, control element, CE.
14. The first apparatus of any preceding claim, wherein the first protocol layer is a radio link control, RLC, layer, and the second protocol layer is a packet data convergence protocol, PDCP, layer.
15. The first apparatus of any preceding claim, wherein the first apparatus comprises a terminal device and the second apparatus comprises a network device, orwherein the first apparatus comprises a network device and the second apparatus comprises a terminal device.
16. A second apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to:transmit, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
17. A method comprising:receiving, at a first protocol layer of a first apparatus from a second protocol layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second protocol layer has expired, wherein the second protocol layer is upper than the first protocol layer; and based on the first indication, starting at the first protocol layer, a second timer for triggering a radio link failure, RLF.
18. A method comprising:transmitting, at a second apparatus and to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
19. A first apparatus comprising:means for receiving, at a first protocol layer of the first apparatus from a second protocol layer of the first apparatus, a first indication indicating that a first timer for at least one data unit at the second protocol layer has expired, wherein the second protocol layer is upper than the first protocol layer; andmeans for based on the first indication, starting at the first protocol layer, a second timer for triggering a radio link failure, RLF.
20. A second apparatus comprising:means for transmitting, to a first apparatus, a set of parameters for a timer and a counter for triggering a radio link failure, RLF, wherein the set of parameters comprise at least one of: an expiring time of the timer for triggering the RLF, or a first threshold for the counter for triggering the RLF.
21. A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 17 or the method of claim 18.
