Enhanced data recovery process

Abstract

Example embodiments of the present disclosure relate to enhanced data recovery. In a method, a first device transmits, to a second device via a first protocol layer of the second device, a feedback message for a first data packet from the second device. If it is determined that a first bearer in an unacknowledged mode (UM) of a second protocol layer is activated, the first device performs at least one of: receiving, from the second protocol layer of the second device, a retransmission of the first data packet without receiving a retransmission of a data packet associated with the UM; receiving, from the first protocol layer of the second device, a retransmission of a second data packet associated with the UM; receiving, from the second protocol layer of the second device, a retransmission of the second data packet associated with the UM after transmitting the feedback message.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more particularly to methods, apparatuses, devices, and computer-readable storage media for enhancing data recovery processes. Background Technology

[0002] A communication network can serve as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile communication networks or wireless communication networks are examples of communication networks. Communication devices can be provided with services by application servers.

[0003] Data recovery is a function of cellular communication systems since the first generation (1G). In wireless communication systems, multiple data recovery loops at different protocol layers are used to ensure reliable delivery of user data. In 5G New Radio (NR), at the radio protocol layer, Hybrid Automatic Repeat Request (HARQ) is used within the Physical (PHY) and Media Access Control (MAC) layers to ensure reliability. Furthermore, Automatic Repeat Request (ARQ) is used at the Radio Link Control (RLC) layer to further enhance reliability. Summary of the Invention

[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: 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 at least: transmit a feedback message of a first data packet from the second apparatus to the second apparatus via a first protocol layer; and if it is determined that a first bearer in the unacknowledged mode (UM) of the second protocol layer is activated, perform at least one of the following: receive a retransmission of the first data packet from the second protocol layer of the second apparatus without receiving a retransmission of a data packet associated with UM; receive a retransmission of a second data packet associated with UM from the first protocol layer of the second apparatus; and receive a retransmission of the second data packet associated with UM from the second protocol layer of the second apparatus after transmitting the feedback message.

[0005] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: 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 at least: receive a feedback message from a first apparatus via a first protocol layer of the second apparatus, the first data packet being destined for the first apparatus; and if it is determined that a first bearer in the unacknowledged mode (UM) of the second protocol layer is activated for the first apparatus, perform at least one of the following: transmit a retransmission of the first data packet from the second protocol layer of the second apparatus to the first apparatus without transmitting a retransmission of a data packet associated with the UM; transmit a retransmission of a second data packet associated with the UM from the first protocol layer of the second apparatus to the first apparatus; and, upon receiving the feedback message, transmit a retransmission of the second data packet associated with the UM from the second protocol layer of the second apparatus to the first apparatus.

[0006] In a third aspect of this disclosure, a method is provided. The method includes: transmitting a feedback message of a first data packet, the first data packet originating from the second device, to the second device via a first protocol layer; and if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated, performing at least one of the following: receiving a retransmission of the first data packet from the second protocol layer of the second device without receiving a retransmission of a data packet associated with the UM; receiving a retransmission of a second data packet associated with the UM from the first protocol layer of the second device; and receiving a retransmission of the second data packet associated with the UM from the second protocol layer of the second device after transmitting the feedback message.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving a feedback message from a first device via a first protocol layer of a second device, the first data packet being destined for the first device; and if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated for the first device, performing at least one of the following: transmitting a retransmission of the first data packet from the second protocol layer of the second device to the first device without transmitting a retransmission of a data packet associated with the UM; transmitting a retransmission of a second data packet associated with the UM from the first protocol layer of the second device to the first device; and, upon receiving the feedback message, transmitting a retransmission of the second data packet associated with the UM from the second protocol layer of the second device to the first device.

[0008] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for transmitting a feedback message of a first data packet from the second apparatus to the second apparatus via a first protocol layer; and components for performing at least one of the following if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated: receiving a retransmission of the first data packet from the second protocol layer of the second apparatus without receiving a retransmission of a data packet associated with UM; receiving a retransmission of a second data packet associated with UM from the first protocol layer of the second apparatus; and receiving a retransmission of the second data packet associated with UM from the second protocol layer of the second apparatus after transmitting the feedback message.

[0009] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving a feedback message from a first apparatus via a first protocol layer of the second apparatus, the first data packet being destined for the first apparatus; and components for performing at least one of the following if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated for the first apparatus: transmitting a retransmission of the first data packet from the second protocol layer of the second apparatus to the first apparatus without transmitting a retransmission of a data packet associated with the UM; transmitting a retransmission of a second data packet associated with the UM from the first protocol layer of the second apparatus to the first apparatus; and transmitting a retransmission of the second data packet associated with the UM from the second protocol layer of the second apparatus to the first apparatus after receiving the feedback message.

[0010] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a third aspect.

[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.

[0012] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0013] Some exemplary embodiments will now be described with reference to the accompanying drawings, wherein: Figure 1 An example communication environment in which example embodiments of the present disclosure may be implemented is shown; Figure 2A An example diagram of the Radio Access Network (RAN) Layer 2 (L2) protocol layer associated with Hybrid Automatic Repeat Request (HARQ) and Automatic Repeat Request (ARQ) is shown. Figure 2B Example signaling flows for different error scenarios in HARQ caused by poor channel conditions are shown; Figure 3 An example signaling flow of an enhanced data recovery process according to some example embodiments of this disclosure is shown; Figure 4 Another example signaling flow is shown for an enhanced data recovery process according to some example embodiments of this disclosure; Figure 5 Example signaling flows for data packet transmission for RLC UM according to some example embodiments of this disclosure are shown; Figure 6 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 8 Another flowchart of a method implemented at a first device according to some example embodiments of the present disclosure is shown; Figure 9 Another flowchart of a method implemented at a second device according to some example embodiments of the present disclosure is shown; Figure 10 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 11 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0014] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0015] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, without implying any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0017] References to "an embodiment," "an embodiment," "an example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment includes that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is to be noted that those skilled in the art will recognize, whether explicitly described or not, that such features, structures, or characteristics apply in conjunction with other embodiments.

[0018] It should be understood that although the terms “first,” “second,” etc., may be used before nouns 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 restrict the order of the nouns. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0019] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, wherein a list of two or more elements combined with “and” or “or” means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0020] As used herein, unless explicitly stated otherwise, the “responding to A” execution step does not indicate that the step is executed immediately after “A” occurs, and may include one or more intermediate steps.

[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “covering,” as used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0022] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implemented with purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.

[0023] This definition of "circuit" applies to all uses of the term in this application. As a further example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or portions of hardware circuitry or servers and their accompanying software and / or firmware implementations. For example, where applicable to certain claim elements, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0024] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols, and / or any other currently known or under development protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, future types of communication technologies and systems that can implement this disclosure will inevitably emerge. The scope of this disclosure should not be considered limited to the systems described above.

[0025] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header End (RH), Remote Radio Header End (RRH), relay, Integrated Access and Backhaul (IAB) node, low-power node (such as femtoseconds, picoseconds), non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary Earth orbit (GEO) satellites), spacecraft network equipment, etc., depending on the terminology and technology applied. In some example embodiments, the low Earth orbit (RAN) separation architecture includes centralized units (CUs) and distributed units (DUs). An IAB node includes: a mobile terminal (IAB-MT) portion that behaves similarly to a UE towards its parent node, and a DU portion that behaves similarly to a base station towards the next-hop IAB node.

[0026] The term "terminal device" refers to any end device with wireless communication capabilities. As an example and not a limitation, a terminal device can refer to communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless client devices (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0027] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time-domain, frequency-domain, and / or code-domain resources that enable communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0028] As used herein, the term "ARQ" refers to an error control and packet recovery method used for data transmission, in which the receiver sends an alarm to the sender if a packet is lost, allowing the sender to retransmit the lost packet. Retransmission is performed at the RLC layer. RLC uses ARQ technology to ensure reliable data delivery and adapts packets according to radio conditions (such as segmentation).

[0029] The term "HARQ" refers to an error correction mechanism that combines forward error correction (FEC) with ARQ. In NR, the MAC sublayer supports error correction and / or repetition through HARQ. The HARQ function ensures delivery between peer entities at Layer 1 (L1).

[0030] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. In the communication environment 100, a plurality of devices, including a first device 110 and a second device 120, communicate with each other.

[0031] In some example embodiments, if the first device 110 is a terminal device and the second device 120 is a network device serving the terminal device, the transmission direction from the second device 120 to the first device 110 is referred to as the downlink (DL), and the transmission direction from the first device 110 to the second device 120 is referred to as the uplink (UL). In the DL, the second device 120 is a transmission (TX) device (or transmitter), and the first device 110 is a reception (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 is an RX device (or receiver).

[0032] exist Figure 1In the example, the second device 120 has a certain coverage area, which can be referred to as a service area or cell (not shown). The first device 110 is located in the cell covered by the second device 120. In the communication environment 100, the second device 120 can transmit data and control information to the first device 110, and the first device 110 can also transmit data and control information to the second device 120.

[0033] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not constitute any limitation. The communication environment 100 may include any appropriate number of devices configured to implement the exemplary embodiments of this disclosure.

[0034] In the following description, for illustrative purposes, some example embodiments will be described in which the first device 110 operates as a terminal device and the second device 120 operates as a network device. However, in some example embodiments, the operations described in association with the terminal device may be implemented at the network device or other devices, and the operations described in association with the network device may also be implemented at the terminal device or other devices.

[0035] Communication in communication environment 100 may be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols, wireless local area network communication protocols (such as those used by the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), and / or any other currently known or future-developed protocols. Furthermore, communication may utilize any suitable wireless communication technology, including 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 Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0036] Research into the upcoming 6G system has already been initiated in several projects, such as the EU's Hexa-X II project. Building on these projects, the wireless industry has begun pre-standardization activities.

[0037] In some mechanisms, ARQ and HARQ procedures have been proposed. Figure 2A Example Figure 200 shows the RAN L2 protocol layer (for UE and gNB) associated with HARQ and ARQ. Figure 2AAs shown, at the RLC layer, ARQ procedure 210 is an error control procedure that controls (multiple) errors through (multiple) retransmissions. Within the MAC and PHY layers, HARQ feedback procedure 220 is an error correction procedure that corrects received packets through (multiple) retransmissions and combining retransmitted packets.

[0038] HARQ feedback is a fast and frequent mechanism that corrects transmission errors, resulting in a low end-to-end round-trip time (RTT). However, HARQ binary feedback is susceptible to errors. Since HARQ feedback is a one-bit operation, this bit can be flipped, leading to ACK to NACK or NACK to ACK errors.

[0039] Figure 2B Example signaling flows 230 are shown for different error scenarios in HARQ caused by poor channel conditions. Signaling flow 230 involves the gNB's PHY layer 232, radio channel 234, and the UE's PHY layer 236. (Example signaling flow 230 is not provided in the original text.) Figure 2B As shown, in step 1, a packet is lost. In step 2, the UE's PHY layer 236 transmits a NACK to the gNB. However, due to poor channel conditions or high interference, this NACK becomes an ACK. Therefore, the gNB's PHY layer 232 receives an ACK. This type of NACK-to-ACK error can lead to unreliable packet delivery.

[0040] Furthermore, errors from ACK to NACK can lead to wasted resources. For example, in step 5, the transmitting party (such as the PHY layer 232 of the gNB) transmits a PDSCH to the receiving party (such as the PHY layer 236 of the UE). In step 6, the receiving party fails to detect the transmission and sends a NACK. In step 7, the PHY layer 232 of the gNB can retransmit the transmission (such as a HARQ retransmission) to the PHY layer 236 of the UE. The receiving party has acknowledged the (re)transmission and sent an ACK. However, in step 8, the transmitting party misinterprets the ACK as a NACK. Therefore, the transmitting party can perform a HARQ retransmission in step 9. This HARQ retransmission at step 9 wastes resources. The MCS changes during HARQ retransmission are complex and often not implemented, which can lead to HARQ failure (e.g., for UEs at the cell edge).

[0041] While low error probabilities can be achieved using HARQ feedback, this comes at the cost of transmission power and resources. While attempting to keep this cost within a reasonable range, a residual HARQ error rate of approximately 1% is incurred. This error rate may be too high for applications. For example, Transmission Control Protocol (TCP) with high data rates requires near-error-free packet delivery to the TCP layer. TCP assumes that packet errors are caused by congestion in the network and triggers congestion avoidance mechanisms that utilize reduced data rates. Therefore, a combination of ARQ and HARQ is used in 5G to achieve a good balance between low RTT and moderate feedback overhead (these two components complement each other) under dynamically changing channel conditions.

[0042] This is a reliable mechanism for recovery from packet loss, implemented at the RLC layer. Status reports and Protocol Data Unit (PDU) retransmissions depend on the RLC sequence number, and the feedback (i.e., the RLC status (STATUS) PDU) is protected by Cyclic Redundancy Check (CRC).

[0043] HARQ memory is organized into slotted memory groups, and the contents of these memory groups need to be maintained during the active states of (multiple) HARQ processes. The size of the HARQ memory depends on the UE's capabilities. The more active HARQ processes there are, the larger the set of memory groups that must be kept powered.

[0044] When HARQ processing is disabled or restricted according to rules, a significant portion of HARQ memory resources can be released. Additionally, write and read cycles (such as direct memory access (DMA)) can also be saved. This is a significant benefit for UE power savings.

[0045] For DL ​​and UL in non-terrestrial networks (NTN), the possibility of disabling HARQ has been introduced. For DL, HARQ feedback can be disabled for each HARQ procedure, and when DL is received for that procedure, the UE does not send feedback and does not start the HARQ RTT timer or retransmission (retx) timer for discontinuous reception (DRX).

[0046] For UL, HARQ mode A / B can be configured for each HARQ procedure and for each logical channel (LCH). The Logical Channel Priority (LCP) procedure only multiplexes data from (multiple) LCHs that are allowed to use the corresponding HARQ mode into the UL authorization for that HARQ procedure. Similar to DL, for HARQ mode B, HARQ RTT timers and retransmission timers are not started for DRX.

[0047] In the LCP for each LCH, allowedHARQ-mode is supported, which sets the allowed UL HARQ modes for transmission. For DRX operation, downlinkHARQ-FeedbackDisabled (Optional) is a configuration for disabling HARQ feedback for each DL HARQ process; uplinkHARQ-Mode (Optional) is a configuration for setting HARQmodeA or HARQmodeB for each UL HARQ process; disableCG-RetransmissionMonitoring (Optional) is used to enable UL transport disabling for configured uplink authorization. drx-HARQ-RTT-TimerUL Configuration.

[0048] In some mechanisms, if the serving cell is configured with downlinkHARQ-FeedbackDisabled And if the corresponding HARQ procedure is configured to enable HARQ feedback, then for the corresponding HARQ procedure HARQ-RTT-TimerDL- NTN It can be set to equal to drx-HARQ-RTT-TimerDL Including the latest available UE-gNB RTT value, and for the corresponding HARQ procedure HARQ-RTT-TimerDL-NTN It can be started in the first symbol after the corresponding transmission carrying DL HARQ feedback has ended. Otherwise, for the corresponding HARQ procedure... drx-HARQ-RTT-TimerDL It can be started in the first symbol after the corresponding transmission carrying DL HARQ feedback has ended.

[0049] In some mechanisms, if a MAC PDU is transmitted during uplink grant configuration and no LBT failure indication is received from the lower layer, the serving cell is configured with... uplinkHARQ-Mode And if the corresponding HARQ procedure is configured as HARQModeA Then, for the corresponding HARQ process HARQ-RTT-TimerUL-NTN It can be set to equal to drx- HARQ-RTT-TimerUL Add the latest available UE-gNB RTT value. If configured... drx-LastTransmissionUL Then, for the corresponding HARQ process HARQ-RTT-TimerUL-NTN Starts in the first symbol after the last transmission (within a bundle) of the corresponding PUSCH transmission. Otherwise, for the corresponding HARQ procedure... HARQ-RTT-TimerUL-NTN It can be started in the first symbol after the first transmission (within a bundle) of the corresponding PUSCH transmission has ended.

[0050] If the MAC PDU is not transmitted in the configured uplink grant, or if an LBT failure indication is received from a lower layer, and if uplink grant is not configured for this purpose. disableCG-RetransmissionMonitoring And if configured drx-LastTransmissionUL Then, for the corresponding HARQ process drx-HARQ-RTT-TimerULStarts in the first symbol after the last transmission (within a bundle) of the corresponding PUSCH transmission. Otherwise, for the corresponding HARQ procedure... drx-HARQ-RTT-TimerUL It can be started in the first symbol after the first transmission (within a bundle) of the corresponding PUSCH transmission has ended.

[0051] Several mechanisms enhance the configuration-free (CG) authorization for Extended Reality (XR). For example, Release 18 specifies a scheme that partially reuses the NTN solution, disabling the HARQ RTT timer for each CG configuration, with the following differences: NTN supports no-retransmission HARQ (i.e., HARQ mode B) for both CG and dynamic authorization, and configures it for each HARQ procedure; NTN also introduces an LCP restriction, limiting which LCHs can use HARQ mode B, while this restriction is not needed for XR because the CG restriction can be reused. In the XR discussion of Release 19, the introduction of dynamic control over whether a CG is a no-HARQ retransmission is proposed.

[0052] In some mechanisms, local NACK (e.g., HARQ NACK sent from MAC to RLC to trigger an early retransmission) was initially introduced as an implementation option in 3GPP's RLC and MAC specifications in version 8. However, it was subsequently removed because it was not suitable as a pure implementation layer without configuration from the gNB.

[0053] Generally, HARQ performs better under poor channel conditions due to its faster feedback and retransmission mechanisms; while ARQ performs better under good channel conditions because there are fewer packet losses, so ARQ feedback and retransmission are sufficient.

[0054] Activating both ARQ and HARQ feedback and retransmission mechanisms introduces resource or processing overhead at both the transmitter and receiver sides. Furthermore, under current 5G NR operation, RLC Acknowledgment Mode (AM) retransmissions are only triggered after the maximum HARQ retransmission is reached, which obviously increases overall latency, undesirable for applications with short packet delay budgets (PDB). Therefore, using two levels of feedback and retransmission mechanisms for ARQ and HARQ is not necessary and may even degrade overall end-to-end (E2E) performance. HARQ and ARQ mechanisms present several problems. These problems can be overcome by merging the HARQ and ARQ processes and optimizing the feedback and retransmission mechanisms to achieve efficient error recovery.

[0055] To address at least some of the aforementioned problems or other potential issues, several solutions regarding merged ARQ and HARQ have been proposed. In these solutions, a first device (such as a terminal device) generates a feedback message for a first data packet originating from a second device (such as a network device) at a first protocol layer of the first device. The first device transmits the feedback message for the first data packet to the second device via the first protocol layer of the second device. For example, the feedback message could be a HARQ feedback message. The first device receives retransmissions of the first data packet from the second device via a second protocol layer, but does not receive retransmissions of the first data packet from the second device's first protocol layer. For example, the retransmission of the first data packet could be an ARQ retransmission via an RLC layer. HARQ retransmissions may not be triggered by the feedback message. That is, the first device does not receive retransmissions from the second device's first protocol layer. In this way, the feedback message triggers retransmissions via the second protocol layer. HARQ feedback and RLC ARQ retransmissions can be merged. This merged ARQ and HARQ process can efficiently handle error recovery for data packet transmissions.

[0056] In another solution, a first device (such as a terminal device) transmits a feedback message for a first data packet, originating from the second device, to a second device (such as a network device) via a first protocol layer of the second device. For example, the feedback message could be a HARQ feedback message. The second device determines whether a first bearer in the unacknowledged mode (UM) of the second protocol layer is active for the first device. If the first bearer in the UM is active, the second device performs at least one of the following: retransmits the first data packet from the second protocol layer of the second device to the first device without retransmitting the data packet associated with the UM; retransmits the second data packet associated with the UM from the first protocol layer of the second device to the first device; and, after receiving the feedback message, retransmits the second data packet associated with the UM from the second protocol layer of the second device to the first device. Accordingly, the first device performs at least one of the following: receives the retransmission of the first data packet from the second protocol layer of the second device without receiving the retransmission of the data packet associated with the UM; receives the retransmission of the second data packet associated with the UM from the first protocol layer of the second device; and, after transmitting the feedback message, receives the retransmission of the second data packet associated with the UM from the second protocol layer of the second device. In this way, if the RLC UM mode bearer is active, several operations will be performed. Therefore, the transmission of data packets can be enhanced.

[0057] Several solutions for merged ARQ and HARQ have been briefly described. The principles and implementation of this disclosure will be described in detail below. It should be noted that... Figure 3 , Figure 4 and Figure 5The order of steps shown is for illustrative purposes only and not a limitation. Steps can be performed in any suitable manner, or combined or omitted. See also: Figure 3 , Figure 4 and Figure 5 The described exemplary embodiments can be implemented individually or combined in any way. For example, one or more exemplary embodiments shown in a single figure can be combined with one or more exemplary embodiments shown in one or more other figures.

[0058] Figure 3 Example signaling flow 300 for merged ARQ and HARQ is shown according to some example embodiments of this disclosure. Signaling flow 300 relates to Figure 1 The first device 110 and the second device 120 in the middle.

[0059] In operation, the first device 110 generates (305) a feedback message for a first data packet from the second device 120 at its first protocol layer. The first data packet is a data packet transmitted from the second device 120 to the first device 110. That is, the second device 120 is a transmitter for the first data packet, and the first device 110 is a receiver for the first data packet. The first device 110 transmits (310) the feedback message for the first data packet from the second device 120 to the second device 120 via the first protocol layer of the second device 120. The second device 120 receives (315) the feedback message accordingly. The second device 120 decodes the received feedback message at the first protocol layer of the second device 120. As an example, the feedback message may be a HARQ feedback message via the PHY layer, or any other suitable feedback message. In response to receiving (315) and decoding the feedback message, the second device 120 transmits (320) a retransmission of the first data packet from the second protocol layer of the second device 120 to the first device 110. As an example, the second protocol layer can be an RLC layer, and the retransmission can be an RLCARQ retransmission. The first device 110 receives (325) this retransmission from the second protocol layer, but does not receive a retransmission of the first data packet from the first protocol layer of the second device 120. That is, the feedback message does not trigger a retransmission at the first protocol layer. The second device 120 may not generate a retransmission at the first protocol layer. That is, the feedback message may trigger a retransmission via the second protocol layer (such as an RLC ARQ retransmission). The feedback message may not trigger a retransmission from the first protocol layer (such as a HARQ retransmission).

[0060] In this way, HARQ feedback schemes (or L1-based feedback) can be used for ARQ feedback, and ARQ can be used for retransmission. That is, ARQ retransmission can be triggered based on HARQ feedback. HARQ-level retransmission and RLC status reporting can be disabled or unnecessary. In other words, the HARQ and ARQ processes can be merged. This merged ARQ and HARQ process (also known as the data recovery process) can efficiently handle error recovery for data packet transmissions. It should be understood that the description of combining feedback messages as HARQ feedback messages and retransmissions as ARQ retransmissions are some example embodiments, but these example embodiments are for illustrative purposes only and do not constitute any limitation. Feedback and retransmission can also be other suitable feedback and retransmissions via other suitable protocol layers or processes.

[0061] In some example embodiments, the feedback message of the first data packet may be transmitted over the Physical Uplink Shared Channel (PUSCH) via a Media Access Control (MAC) control element (MAC CE), or multiplexed over the PUSCH or over the Physical Uplink Control Channel (PUCCH). For example, the feedback message may be transmitted via a MAC transport block (TB). The MAC TB may be transmitted via at least one of a code block or a group of code blocks. The code block or group of code blocks is mapped to a HARQ procedure associated with the first data packet.

[0062] Alternatively, in some example embodiments, the feedback message for the first data packet can be transmitted on the Physical Uplink Control Channel (PUCCH). For downlink data transmission, HARQ feedback can be sent on the PUCCH or on the PUSCH (multiplexed on the PUSCH, similar to NR, or via MAC CE). If blind or autonomous transmission via a first protocol layer is configured, the first device 110 can perform error correction for multiple retransmissions received by the first device 110.

[0063] In some example embodiments, the second device 120 may maintain a mapping between at least two of the following: a logical channel identifier or a protocol data unit identifier of the second protocol layer, a transport block or protocol data unit of the first protocol layer, or a code block or group of code blocks. A transport block may be a MAC PDU. The second device 120 may process feedback messages by disposing of an entity of the first protocol layer of the second device 120. For example, this entity may be a MAC entity. The second device 120 may map feedback messages to protocol data units of the second protocol layer of the second device 120. The second device 120 may indicate the feedback message to the corresponding entity of the second protocol layer of the second device 120.

[0064] Alternatively or additionally, in some scenarios, the first device 110 may transmit a second data packet to the second device 120. That is, the first device 110 is the transmitter and the second device 120 is the receiver. In this case, the second device 120 may transmit (330) an authorization message to the first device 110 for the second data packet destined for the second device 120. The authorization message may include a new data indicator (NDI) indicating whether the second data packet has been previously transmitted. For example, the NDI may be 1 or 0. The first device 110 may receive (335) the authorization message. If the NDI indicates that the second data packet has not been previously transmitted, the first device 110 may transmit (340) a retransmission of the second data packet to the second device 120 via the second protocol layer of the second device 120, without transmitting a retransmission of the second data packet from the first protocol layer of the first device. That is, the first device 110 may not generate a retransmission of the second data packet at the first protocol layer. The authorization message with the NDI may not trigger a retransmission from the first protocol layer. The second device 120 can receive (345) retransmissions via the second protocol layer. That is, an authorization message can trigger an RLC ARQ retransmission. A HARQ retransmission can be triggered without an authorization message.

[0065] For uplink data transmission, there is no explicit HARQ feedback sent to the first device 110. However, if the first device 110 receives a new grant along with an NDI bit set to "1", the first device 110 can treat the feedback as a HARQ ACK; otherwise, it can treat it as a HARQ NACK, and this can be used to trigger an RLC retransmission.

[0066] In some example embodiments, the first device 110 can process the authorization message by disposing of an entity at a first protocol layer (e.g., MAC) of the first device 110. The first device 110 can map the authorization message to a protocol data unit at a second protocol layer of the first device 110. The first device 110 can indicate the authorization message to the corresponding entity at the second protocol layer of the first device 110.

[0067] The first device 110 can maintain a mapping between the following: logical channel identifier or protocol data unit identifier of the second protocol layer, media access control transport block or protocol data unit, and code block or code block group.

[0068] In some example embodiments, the first device 110 may transmit capability information regarding support for merged ARQ and HARQ procedures to the second device. Indication of support for merged ARQ / HARQ procedures may be included as part of a UE capability message. In this way, the network can be informed whether the first device 110 supports merged ARQ and HARQ procedures.

[0069] The second device 120 can transmit a configuration of the merged ARQ and HARQ procedures to the first device 110. This configuration may include at least one condition for activating or deactivating the merged ARQ and HARQ procedures. The network can configure rules / guidelines for activating / deactivating the merged ARQ and HARQ procedures at the UE based on UE capabilities and / or application requirements and / or service or QoS requirements. The first device 110 can activate or deactivate the merged ARQ and HARQ procedures based on this configuration. For example, the merging of ARQ and HARQ procedures can be dynamically activated or deactivated based on the scenario. The procedure can be deactivated during handover, or if an RLC UM mode bearer is active, etc. During good radio conditions, merged ARQ and HARQ can be activated for DRBs. This function (i.e., merged ARQ and HARQ) can be deactivated during handover, when a voice bearer is active, or for DRBs requiring lower reliability and lower throughput, etc. The first device 110 can activate or deactivate the procedure based on rules or guidelines received from the network. The first device 110 can transmit an indication to the second device 120 to activate or deactivate the merged ARQ and HARQ procedures. For example, when the merged ARQ and HARQ procedures are activated or deactivated, the first device 110 can indicate this to the network via MAC CE or uplink control information (UCI) or any other suitable message (such as RRC signaling).

[0070] In some example embodiments, the second device 120 may transmit a trigger message to the first device 110 for activating or deactivating the merged ARQ and HARQ procedures. The first device 110 may activate or deactivate the merged ARQ and HARQ procedures based on the trigger message. For example, the network may activate or deactivate the procedures via an RRC message, a MAC CE sent to the first device 110, or any other suitable message or signaling.

[0071] In some example embodiments, the second device 120 may transmit a configuration for blind HARQ retransmission or autonomous HARQ retransmission of the first data packet to the first device 110. In response to receiving the configuration for blind HARQ retransmission or autonomous HARQ retransmission, the first device 110 may perform blind HARQ retransmission or autonomous HARQ retransmission.

[0072] In some of the example embodiments described above, HARQ feedback can be used to trigger retransmissions at the RLC level, eliminating the need for HARQ retransmissions and RLC status reports. A single feedback and retransmission mechanism will exist, saving resources and processing overhead on both the transmitter and receiver sides. Only one feedback type will exist: HARQ feedback. RLC ARQ feedback via status reports may not be necessary. Only one retransmission type will exist: RLC ARQ retransmission. There will be no HARQ-level retransmissions. Reliability will improve under poor radio conditions due to faster feedback (HARQ feedback) and ARQ retransmissions (which will ensure a more robust MCS can be selected for packet retransmissions). Early triggering of RLC retransmissions helps reduce the Packet Error Rate (PER).

[0073] Compared to HARQ-level retransmissions, retransmissions will have a slight delay, which may affect throughput. This can be mitigated by increasing the number of configured HARQ procedures to maintain the desired throughput (the maximum number of HARQ procedures supported in 5G is 16).

[0074] HARQ feedback on the PUCCH is not always CRC protected, and toggling can lead to packet loss or unwanted retransmissions. This can be mitigated by increasing the number of HARQ feedback bits and adding CRC, or by applying other optimizations to the HARQ feedback. Another option is to multiplex the HARQ feedback on the PUSCH or transmit it via MAC CE. In some embodiments, error correction or combination for HARQ retransmissions will not be possible at the receiver.

[0075] In the example embodiment, ARQ and HARQ are combined using either HARQ feedback received at the gNB via the MAC CE on the PUSCH, or feedback multiplexed on the PUSCH. The MAC TB is transmitted via code blocks (CB) / code block groups (CBG), which are mapped to different HARQ procedures. The receiver sends HARQ feedback on the PUSCH. Since RLC relies on HARQ feedback for retransmission and Tx window operations, RLC status reporting is not required. The transmitter can maintain a mapping between: RLC PDU / LCH ID, MAC TB / subPDU / subPDU number, and CB / CBG (code block groups). This mapping is required upon receiving HARQ feedback for ARQ retransmission or RLC Tx window update. The transport MAC entity can process the feedback and map it to the RLC PDU, and the feedback (i.e., ACK / NACK) is sent to the corresponding RLC entity.

[0076] For the TX side, there is no HARQ-level retransmission. For the Rx side, since there is no HARQ retransmission, there is no error correction mechanism, and no reassembly is performed. Using this configuration, the Tx side does not need to store packets for HARQ retransmissions. The Rx side does not need to store received packets for reassembly; for example, this can reduce the memory occupied by the UE side.

[0077] For the Tx side, blind retransmission or autonomous retransmission (physical layer) can be configured at the HARQ layer. This option can be dynamically activated for certain scenarios, such as high reliability services, or when RLC AM mode bearers and UM mode bearers are multiplexed onto the same TB.

[0078] In this way, the HARQ feedback flip problem can be eliminated. The modulation and coding scheme (MCS) is not modified for HARQ retransmissions, which can lead to HARQ failures under poor radio conditions or at cell edges. This problem can be avoided by performing retransmissions at the MAC / RLC level. New MAC CEs can be introduced. For example, the MAC header format can be modified (e.g., defining a separate segment), because the HARQ feedback MAC CE can always exist in the MAC TB or as a MAC (sub)header.

[0079] When the merged ARQ and HARQ processes are active, RLC polling and status reporting can be disabled. HARQ retransmission can be disabled. Blind HARQ retransmission can be triggered, which can be configured by the network.

[0080] Alternatively, in this embodiment, ARQ and HARQ are combined using either HARQ feedback received at the gNB on the PUCCH, or HARQ feedback derived at the UE based on UL authorization and DCI received on the PDCCH. Packets are transmitted normally via the HARQ procedure. The receiver may send HARQ feedback on the PUCCH (for downlink data transmissions), or derive implicit HARQ feedback at the UE (for uplink data transmissions).

[0081] Since RLC status reporting is not required, it can be disabled. RLC relies on HARQ feedback for retransmissions and Tx window operations.

[0082] The transmitter can maintain a mapping between the following: RLC PDU / LCH ID, MAC TB / subPDU / subPDU number, and CB / CBG. This mapping is required upon receiving HARQ feedback for ARQ retransmission or RLC Tx window update.

[0083] The transmitter can process feedback and map it to an RLC PDU, and send the feedback (i.e., ACK / NACK) to the corresponding RLC entity.

[0084] For the Tx side, blind retransmission or autonomous retransmission (physical layer) can be configured at the HARQ layer. This option can be dynamically activated for certain scenarios, such as high reliability services, or when RLC AM mode bearers and UM mode bearers are multiplexed onto the same TB.

[0085] For the Rx side, if blind retransmission is configured, an error correction mechanism will be applied. If the blind retransmission is not acknowledged (NACK), ARQ retransmission (RLC-level retransmission) can be triggered.

[0086] In this way, the MAC header format will not be affected because HARQ feedback is processed at the physical layer, which is the same as its current processing method in 5G. RLC polling and status reporting can be disabled when the merged ARQ / HARQ process is active. HARQ retransmission can be disabled. Blind retransmission can be triggered, which should be configured by the network.

[0087] Figure 4 Example signaling flow 400 for merged ARQ and HARQ is shown according to some example embodiments of this disclosure. Signaling flow 400 relates to Figure 1 The first device 110 and the second device 120 in the middle.

[0088] In operation, for success case 410, HARQ transmission of data packets is transmitted from the PHY layer of the second device 120 to the PHY layer of the first device 110. If the data packets are successfully decoded, the first device 110 can transmit a HARQ ACK to the second device 120 via the PHY layer. The RLC transmission window can be updated based on the receipt of (multiple) ACKs.

[0089] In failure scenario 420, if HARQ transmission to the first device 110 fails on the radio interface, data packets are lost. The first device 110 can transmit a HARQ NACK to the second device 120 via the PHY layer. The HARQ feedback can be indicated to the MAC layer, and the CB or CBG number or MAC sub-PDU number can be mapped to the LCH ID or RLC PDU SN. Therefore, RLC PDU retransmission can be triggered. Retransmission of (multiple) RLC PDUs to the second device 120 can be triggered.

[0090] Already combined Figures 3 to 4 Several embodiments of merged ARQ and HARQ are described. These embodiments enable efficient handling of data packet error recovery.

[0091] Figure 5An example signaling stream 500 for data packet transmission for RLC UM is illustrated according to some example embodiments of this disclosure. Signaling stream 500 relates to... Figure 1 The first device 110 and the second device 120 in the middle.

[0092] In operation, the first device 110 transmits (410) a feedback message of a first data packet from the second device 120 to the second device 120 via a first protocol layer. For example, the feedback message is generated at the first protocol layer of the first device 110, such as the PHY layer of the first device 110. Correspondingly, the second device 120 receives (415) the feedback message via its first protocol layer. The second device 120 can decode the received feedback message at its first protocol layer. For example, the feedback message can be a HARQ feedback message via the PHY layer.

[0093] First device 110 determines (420) whether a first bearer in the unacknowledged mode (UM) of the second protocol layer is activated. Similarly, second device 120 determines (430) whether a bearer in the UM of the second protocol layer is activated for first device 110. For example, second device 120 may determine (430) whether an RLC UM bearer is activated for first device 110.

[0094] If the bearer for UM is activated, the second device 120 performs at least one operation. In an embodiment, at least one operation may be: transmitting (440) a retransmission of the first data packet from the second protocol layer of the second device 120 to the first device 110, without transmitting a retransmission of the data packet associated with UM. Accordingly, the first device 110 receives (445) a retransmission of the first data packet from the second protocol layer of the second device 120, without receiving a retransmission of the data packet associated with UM. That is, no UM data retransmission is received from the second device 120. A HARQ feedback message may trigger an RLC ARQ retransmission, and the UM data retransmission is not performed.

[0095] In another embodiment, at least one operation may be: transmitting (440) a retransmission of a second data packet associated with UM from the first protocol layer of the second device 120 to the first device 110. The first device 110 receives (445) the retransmission of the second data packet associated with UM from the first protocol layer of the second device 120. For example, the retransmission(s) of the RLC UM data packet may be a blind HARQ retransmission or a spontaneous HARQ retransmission.

[0096] In another embodiment, at least one operation may be: after receiving the (415) feedback message, transmitting (440) a retransmission of the second data packet associated with UM from the second protocol layer of the second device 120 to the first device 110. After transmitting the (410) feedback message, the first device 110 receives (445) the retransmission of the second data packet associated with UM from the second protocol layer of the second device 120.

[0097] In some example embodiments, the feedback message includes a HARQ feedback message via the physical protocol layer. Retransmission of the first data packet can be an RLC retransmission of the first data packet. HARQ retransmission is not triggered by the HARQ feedback message.

[0098] In some example embodiments, the retransmission of the second data packet of RLC UM can be a retransmission of the RLC PDU of the second data packet after the transmission of the HARQ feedback message. The retransmission of the second data packet can be received separately from the data packets in AM in the MAC PDU and without multiplexing with the data packets in AM. The retransmission of the second data packet can be stored by the RLC protocol of the second device 120 and transmitted to the first device 110 after the feedback message is received.

[0099] In some example embodiments, the first device 110 may transmit a third data packet to the second device 120. The second device 120 may transmit an authorization message to the first device for the third data packet destined for the second device 120. The authorization message includes an NDI indicating whether the third data packet was previously transmitted. The first device 110 may receive the authorization message.

[0100] If the NDI indicates that the third data packet has not been previously transmitted, the first device 110 can transmit a retransmission of the third data packet to the second device 120 via the second protocol layer of the second device 120. That is, an authorization message can trigger an RLC retransmission, and an authorization message may not trigger a HARQ retransmission. The second device 120 can receive the retransmission of the third data packet via the second protocol layer of the second device 120.

[0101] In some example embodiments, the first device 110 may disable the retransmission of third data packets to the second device 120 via the first protocol layer. That is, HARQ retransmission may be disabled.

[0102] In some example embodiments, the first device 110 may perform blind or autonomous retransmission of the third data packet to the second device 120 via the first protocol layer. Alternatively or additionally, the first device 110 may perform RLC PDU retransmission of the third data packet after receiving an authorization message. For example, the retransmission of the third data packet may be transmitted separately from and without multiplexing with the data packets in the AM in the MAC PDU. The retransmission of the third data packet may be stored by the RLC protocol and transmitted to the second device 120 after receiving an authorization message.

[0103] In some example embodiments, if no bearer in the UM of the second protocol layer is activated for the first device 110, the second device 120 may deactivate blind retransmission or autonomous retransmission of data packets via the first protocol layer.

[0104] The combined ARQ and HARQ solution considers a bearer configured in RLC AM mode (i.e., ARQ is enabled). However, the first device 110 may have multiple active bearers simultaneously, one in AM mode and another in UM mode. In this case, since HARQ retransmission is disabled in this method, there will be no retransmission means for RLC UM mode bearers. Therefore, several methods for handling retransmissions when a UM mode bearer is active for the first device 110 are given below.

[0105] In the example, in the case of merged ARQ and HARQ, there will be no retransmission of UM data, which may result in a small number of packet losses.

[0106] In another embodiment, when an RLC UM mode bearer exists, blind HARQ retransmission or autonomous HARQ retransmission can be dynamically activated, and when only an RLC AM mode bearer exists for the first device 110, blind HARQ retransmission or autonomous HARQ retransmission can be dynamically deactivated.

[0107] In another embodiment, the first device 110 may perform RLCPDU retransmission for UM mode packets based on HARQ feedback (this is an implementation aspect). This embodiment may require RLC storage of RLC UM mode bearer packets until HARQ feedback is received. RLC UM mode packet retransmission does not violate current 5G RLC protocol rules because it is an implementation-level handling of packets.

[0108] UM data can be sent separately in a MAC PDU (i.e., not multiplexed with AM data). HARQ retransmission can be performed only for UM data. This can be slightly more complex and may also affect the throughput of the AM bearer.

[0109] When a UM DRB exists, ARQ and HARQ merging can be deactivated. Merging ARQ and HARQ can only be enabled when an AM DRB exists.

[0110] In some example embodiments, the first device 110 may receive from the second device 120 a configuration including at least one of the following: a condition for activating or deactivating at least one condition for activating or deactivating retransmission via a first protocol layer or a condition for activating or deactivating retransmission via a second protocol layer based on an authorization message. The first device 110 may activate or deactivate retransmission via the second protocol layer, such as RLC retransmission, based on this configuration. The first device 110 may also activate or deactivate blind or autonomous retransmission via the first protocol layer, such as blind HARQ retransmission or autonomous HARQ retransmission, based on this configuration. For example, the first device 110 may enable or disable blind HARQ retransmission or autonomous HARQ retransmission based on criteria specified for UM mode bearer handling. In this way, an appropriate retransmission procedure can be activated.

[0111] The first device 110 can transmit an instruction to the second device 120 to activate or deactivate retransmission, such as RLC retransmission, blind HARQ retransmission, or autonomous HARQ retransmission. In this way, the network can be notified of the activated retransmission process.

[0112] It should be understood that some example specifications, signaling flows, and embodiments are provided above, and the detailed description may vary. It should be understood that these signaling flows 300, 400, and / or 500 can be used individually or in any suitable combination. Some example embodiments, operations, or features described for one of these signaling flows 300, 400, and / or 500 can be applied to another signaling flow within these signaling flows. A portion of one of the aforementioned signaling flows 300, 400, and / or 500 can be applied in combination with a portion of another signaling flow. It should also be understood that these signaling flows 300, 400, and / or 500 can involve any other suitable operations or signaling not shown. Utilizing these signaling flows, and similar signaling flows, can enhance the CSI processing framework for AI / ML-enabled temporal beam prediction.

[0113] Figure 6 A flowchart of an example method 600 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 600 will be discussed from... Figure 1 The angle of the first device 110 in the middle is described.

[0114] In frame 610, the first device 110 generates a feedback message for a first data packet at the first protocol layer, the first data packet originating from the second device.

[0115] In frame 620, the first device 110 transmits a feedback message of a first data packet from the second device to the second device via a first protocol layer of the second device.

[0116] In block 630, the first device 110 receives a retransmission of the first data packet from the second device at the second protocol layer, but does not receive a retransmission of the first data packet from the second device at the first protocol layer.

[0117] In some example embodiments, the feedback message of the first data packet is transmitted via a Media Access Control (MAC) control element on the Physical Uplink Shared Channel (PUSCH), or multiplexed on the PUSCH.

[0118] In some example embodiments, the feedback message is transmitted via a MAC transport block (TB), which is transmitted via at least one of a block or group of blocks that is mapped to a Hybrid Automatic Repeat Request (HARQ) process associated with the first data packet.

[0119] In some example embodiments, the feedback message of the first data packet is transmitted on the Physical Uplink Control Channel (PUCCH).

[0120] In some example embodiments, method 600 further includes performing error correction for multiple retransmissions received by the first device based on blind or autonomous transmission configured via a first protocol layer.

[0121] In some example embodiments, method 600 further includes maintaining a mapping between: a logical channel identifier or a protocol data unit identifier of a second protocol layer, a media access control transport block or a protocol data unit, and a code block or a group of code blocks.

[0122] In some example embodiments, method 600 further includes: receiving from the second device an authorization message for a second data packet destined for the second device, the authorization message including a new data indicator indicating whether the second data packet has been previously transmitted; and, based on the new data indicator indicating that the second data packet has not been previously transmitted, transmitting a retransmission of the second data packet to the second device via a second protocol layer of the second device, instead of transmitting a retransmission of the second data packet from the first protocol layer of the first device 110.

[0123] In some example embodiments, method 600 further includes: processing the authorization message by a media access control entity of the first device; mapping the authorization message to a protocol data unit of a second protocol layer of the first device; and indicating the authorization message to a corresponding entity of the second protocol layer of the first device.

[0124] In some example embodiments, the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes a Radio Link Control (RLC) Automatic Repeat Request (ARQ) retransmission of the first data packet, and the HARQ retransmission is not triggered based on the HARQ feedback message.

[0125] In some example embodiments, method 600 further includes transmitting to the second device at least one of the following: capability information for supporting merged ARQ and HARQ procedures, and an indication to activate or deactivate merged ARQ and HARQ procedures.

[0126] In some example embodiments, method 600 further includes receiving from the second device at least one of the following: a configuration of a merged ARQ and HARQ process, the configuration including at least one condition for activating or deactivating the merged ARQ and HARQ process; a trigger message for activating or deactivating the merged ARQ and HARQ process; and a configuration for blind HARQ retransmission or autonomous HARQ retransmission of the first data packet.

[0127] In some example embodiments, method 600 further includes activating or deactivating the merged ARQ and HARQ procedures based on the configuration of the merged ARQ and HARQ procedures.

[0128] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.

[0129] Figure 7 A flowchart of an example method 700 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 700 will be discussed from... Figure 1 The angle of the second device 120 in the description is as follows.

[0130] In frame 710, the second device 120 receives a feedback message of a first data packet from the first device via the first protocol layer of the second device, the first data packet being sent from the second device to the first device.

[0131] In frame 720, the second device 120 decodes the feedback message at the first protocol layer.

[0132] In block 730, the second device 120 transmits retransmissions of the first data packet from the second protocol layer of the second device to the first device, without transmitting retransmissions of the first data packet from the first protocol layer of the second device.

[0133] In some example embodiments, method 700 further includes: transmitting to a first device an authorization message for a second data packet destined for a second device, the authorization message including a new data indicator indicating whether the second data packet was previously transmitted; and receiving a retransmission of the second data packet from the first device via a second protocol layer of the second device, without receiving a retransmission of the second data packet from a first protocol layer of the first device.

[0134] In some example embodiments, the feedback message of the first data packet is received on the Physical Uplink Shared Channel (PUSCH) via the Media Access Control Element (MAC CE), or multiplexed on the PUSCH.

[0135] In some example embodiments, the feedback message is received via a MAC transport block (TB) via at least one of a code block or a group of code blocks, which is mapped to a Hybrid Automatic Repeat Request (HARQ) procedure associated with the first data packet.

[0136] In some example embodiments, the feedback message for the first data packet is received on the Physical Uplink Control Channel (PUCCH).

[0137] In some example embodiments, method 700 further includes maintaining a mapping between at least two of the following: a logical channel identifier or a protocol data unit identifier of a second protocol layer, a media access control transport block or a protocol data unit, a code block or a group of code blocks.

[0138] In some example embodiments, method 700 further includes: processing the feedback message by a media access control entity of the second device; mapping the feedback message to a protocol data unit of a second protocol layer of the second device; and indicating the feedback message to a corresponding entity of the second protocol layer of the second device.

[0139] In some example embodiments, the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes a Radio Link Control (RLC) Automatic Repeat Request (ARQ) retransmission of the first data packet, and the HARQ retransmission is not triggered based on the HARQ feedback message.

[0140] In some example embodiments, method 700 further includes receiving from the first device at least one of the following: capability information for supporting merged ARQ and HARQ procedures, and an indication to activate or deactivate merged ARQ and HARQ procedures.

[0141] In some example embodiments, method 700 further includes disabling at least one of the following: HARQ retransmission of the first data packet, RLC polling, and status reporting.

[0142] In some example embodiments, method 700 further includes transmitting to the first device at least one of the following: a configuration of a merged ARQ and HARQ process, the configuration including at least one condition for activating or deactivating the merged ARQ and HARQ process; a trigger message for activating or deactivating the merged ARQ and HARQ process; and a configuration for blind HARQ retransmission or autonomous HARQ retransmission of the first data packet.

[0143] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.

[0144] Figure 8 A flowchart of an example method 800 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 800 will be discussed from... Figure 1 The angle of the first device 110 in the middle is described.

[0145] In frame 810, the first device 110 transmits a feedback message of a first data packet to the second device via the first protocol layer of the second device, the first data packet originating from the second device.

[0146] In block 820, if it is determined that the first bearer in the unacknowledged mode (UM) of the second protocol layer is activated, the first device 110 performs at least one of the following: receiving a retransmission of the first data packet from the second protocol layer of the second device without receiving a retransmission of the data packet associated with UM; receiving a retransmission of the second data packet associated with UM from the first protocol layer of the second device; and receiving a retransmission of the second data packet associated with UM from the second protocol layer of the second device after transmitting a feedback message.

[0147] In some example embodiments, the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes a Radio Link Control (RLC) retransmission of the first data packet, and the HARQ retransmission is not triggered by the HARQ feedback message.

[0148] In some example embodiments, the retransmission of the second data packet includes at least one of the following: blind HARQ retransmission or autonomous HARQ retransmission of the second data packet, and retransmission of the RLC Protocol Data Unit (PDU) of the second data packet after transmitting the HARQ feedback message.

[0149] In some example embodiments, the retransmission of the second data packet is received separately from the data packets in Acknowledgment Mode (AM) in the Media Access Control Protocol (MAC) Data Unit and without multiplexing with the data packets in AM.

[0150] In some example embodiments, method 800 further includes: receiving from the second device an authorization message for a third data packet destined for the second device, the authorization message including a new data indicator indicating whether the third data packet has been previously transmitted; and retransmitting the third data packet to the second device via a second protocol layer of the second device based on the new data indicator indicating that the third data packet has not been previously transmitted.

[0151] In some example embodiments, method 800 may further include: disabling retransmission of the third data packet to the second device via the first protocol layer; performing blind retransmission or autonomous retransmission of the third data packet to the second device via the first protocol layer; and performing RLC protocol data unit (PDU) retransmission of the third data packet after receiving the authorization message.

[0152] In some example embodiments, the retransmission of the third data packet is carried out separately from the data packets in Acknowledgment Mode (AM) in the Media Access Control Protocol (MAC) Data Unit and is not multiplexed with the data packets in AM.

[0153] In some example embodiments, the retransmission of the third data packet is stored by the Radio Link Control (RLC) protocol and transmitted to the second device after an authorization message is received.

[0154] In some example embodiments, method 800 further includes receiving from the second device a configuration including at least one of the following: a condition for activating or deactivating at least one condition for activating or deactivating blind retransmission or autonomous retransmission via a first protocol layer, or a condition for activating or deactivating retransmission based on an authorization message via a second protocol layer.

[0155] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.

[0156] Figure 9 A flowchart of an example method 900 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 900 will be discussed from... Figure 1 The angle of the second device 120 in the description is as follows.

[0157] In frame 910, the second device 120 receives a feedback message of a first data packet from the first device via the first protocol layer of the second device, and the first data packet is sent from the second device to the first device.

[0158] In block 920, if it is determined that the first bearer in the unacknowledged mode (UM) of the second protocol layer is activated for the first device, the second device 120 performs at least one of the following: retransmits a first data packet from the second protocol layer of the second device to the first device without retransmitting a data packet associated with UM; retransmits a second data packet associated with UM from the first protocol layer of the second device to the first device; and retransmits a second data packet associated with UM from the second protocol layer of the second device to the first device after receiving a feedback message.

[0159] In some example embodiments, the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes a Radio Link Control (RLC) retransmission of the first data packet, and the HARQ retransmission is not triggered by the HARQ feedback message.

[0160] In some example embodiments, the retransmission of the second data packet includes at least one of the following: blind retransmission or autonomous HARQ retransmission of the second data packet, or retransmission of the RLC protocol data unit (PDU) of the second data packet after receiving a HARQ feedback message.

[0161] In some example embodiments, the retransmission of the second data packet is carried out separately from the data packets in Acknowledgment Mode (AM) in the Media Access Control Protocol (MAC) Data Unit and is not multiplexed with the data packets in AM.

[0162] In some example embodiments, the retransmission of the second data packet is stored by the Radio Link Control (RLC) protocol and transmitted to the first device after a feedback message is received.

[0163] In some example embodiments, method 900 further includes: if it is determined that no bearer is activated for the first device in the UM of the second protocol layer, then deactivate blind retransmission or autonomous retransmission of data packets via the first protocol layer.

[0164] In some example embodiments, method 900 further includes: transmitting to a first device an authorization message for a third data packet destined for a second device, the authorization message including a new data indicator indicating whether the third data packet has been previously transmitted; and receiving a retransmission of the third data packet from the first device via a second protocol layer of the second device based on the new data indicator indicating that the third data packet has not been previously transmitted.

[0165] In some example embodiments, method 900 further includes transmitting to the first device a configuration including at least one of the following: a condition for activating or deactivating blind retransmission or autonomous retransmission via a first protocol layer, or a condition for activating or deactivating retransmission based on an authorization message via a second protocol layer.

[0166] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.

[0167] In some example embodiments, a first means capable of performing any of method 600 (e.g. Figure 1 The first device 110 may include a component for performing a corresponding operation of method 600. This component may be implemented in any suitable form. For example, the component may be implemented as a circuit or a software module. The first device may be implemented as... Figure 1 The first device 110, or included in Figure 1 In the first device 110.

[0168] In some example embodiments, the first device includes: components for generating a feedback message of a first data packet at a first protocol layer of the first device, the first data packet originating from a second device; components for transmitting the feedback message of the first data packet from the second device to the second device via the first protocol layer of the second device; and components for receiving retransmissions of the first data packet from the second device at a second protocol layer without receiving retransmissions of the first data packet from the first protocol layer of the second device.

[0169] In some example embodiments, a second means capable of performing any of the methods 700 (e.g. Figure 1 The second device 120 may include a component for performing the corresponding operation of method 700. This component may be implemented in any suitable form. For example, the component may be implemented as a circuit or a software module. The second device may be implemented as... Figure 1 The second device 120, or included in Figure 1 The second device 120 in the middle.

[0170] In some example embodiments, the second device includes: components for receiving a feedback message of a first data packet from the first device via a first protocol layer of the second device, the first data packet being sent from the second device to the first device; components for decoding the feedback message at the first protocol layer; and components for transmitting a retransmission of the first data packet from the second protocol layer of the second device to the first device without transmitting the retransmission of the first data packet via the first protocol layer of the second device.

[0171] In some example embodiments, a first means capable of performing any of the methods 800 (e.g. Figure 1 The first device 110 may include a component for performing a corresponding operation of method 800. This component may be implemented in any suitable form. For example, the component may be implemented as a circuit or a software module. The first device may be implemented as... Figure 1 The first device 110, or included in Figure 1 In the first device 110.

[0172] In some example embodiments, the first device includes: components for transmitting a feedback message of a first data packet from the second device to the second device via a first protocol layer of the second device; and components for performing at least one of the following if it is determined that a first bearer in the unacknowledged mode (UM) of the second protocol layer is activated: receiving a retransmission of the first data packet from the second protocol layer of the second device without receiving a retransmission of a data packet associated with UM; receiving a retransmission of a second data packet associated with UM from the first protocol layer of the second device; and receiving a retransmission of the second data packet associated with UM from the second protocol layer of the second device after transmitting the feedback message.

[0173] In some example embodiments, a second means capable of performing any of the methods 900 (e.g. Figure 1 The second device 120 may include a component for performing the corresponding operation of method 900. This component can be implemented in any suitable form. For example, the component can be implemented as a circuit or a software module. The second device can be implemented as... Figure 1 The second device 120, or included in Figure 1 The second device 120 in the middle.

[0174] In some example embodiments, the second device includes: components for receiving a feedback message from the first device via a first protocol layer of the second device, the first data packet being destined for the first device; and components for performing at least one of the following if it is determined that a first bearer in the unacknowledged mode (UM) of the second protocol layer is activated for the first device: transmitting a retransmission of the first data packet from the second protocol layer of the second device to the first device without transmitting a retransmission of a data packet associated with the UM; transmitting a retransmission of a second data packet associated with the UM from the first protocol layer of the second device to the first device; and transmitting a retransmission of the second data packet associated with the UM from the second protocol layer of the second device to the first device after receiving the feedback message.

[0175] Figure 10 This is a simplified block diagram of a device 1000 suitable for implementing exemplary embodiments of the present disclosure. Device 1000 may be provided to implement a communication device, such as... Figure 1 The first device 110 or the second device 120 shown. As shown, the device 1000 includes one or more processors 1010, one or more memories 1020 coupled to the processors 1010, and one or more communication modules 1040 coupled to the processors 1010.

[0176] Communication module 1040 is used for bidirectional communication. Communication module 1040 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 1040 may include at least one antenna.

[0177] As a non-limiting example, processor 1010 can be any type suitable for a local technology network and can include one or more of the following as non-limiting examples: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1000 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0178] Memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, miniature optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that will not be maintained during power outages.

[0179] Computer program 1030 includes computer-executable instructions that are executed by an associated processor 1010. The instructions of program 1030 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1030 may be stored in memory, such as ROM 1024. Processor 1010 can perform any suitable actions and processes by loading program 1030 into RAM 1022.

[0180] Example embodiments of this disclosure can be implemented by means of program 1030, so that device 1000 can perform as described in the reference. Figures 3 to 9 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0181] In some example embodiments, program 1030 may be tangibly included in a computer-readable medium, which may be included in device 1000 (such as in memory 1020) or other storage device accessible to device 1000. Device 1000 may load program 1030 from the computer-readable medium into RAM 1022 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein refers to a limitation on the medium itself (i.e., tangible, not tactile) rather than a limitation on data storage persistence (e.g., RAM vs. ROM).

[0182] Figure 11 An example of a computer-readable medium 1100 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1100 stores a program 1030 thereon.

[0183] In general, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, and others can be implemented in firmware or software executed by a controller, microprocessor, or other computing device. While various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as examples of non-limiting examples.

[0184] Some exemplary embodiments of this 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 a program module, which are executed in a device on a target physical or virtual processor to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. The machine-executable instructions for the program module can execute on a local device or a distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0185] Program code for implementing the methods of this 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, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0186] In the context of this disclosure, computer program code or related data may be carried on any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0187] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any suitable combination thereof. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0188] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that they be performed in the specific order shown or sequentially, or that all the operations shown be performed in order to achieve the desired result. In some cases, multitasking and parallel processes can be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, they should not be considered as limiting the scope of this disclosure, but rather as a description of features that may be specific to certain embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0189] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

[0190] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0191] Clause 1. A first means for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first means to at least: transmit a feedback message of a first data packet from the second means to the second means via a first protocol layer of the second means; and if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated, perform at least one of the following: receive a retransmission of the first data packet from the second protocol layer of the second means without receiving a retransmission of a data packet associated with UM; receive a retransmission of a second data packet associated with UM from the first protocol layer of the second means; and receive a retransmission of the second data packet associated with UM from the second protocol layer of the second means after transmitting the feedback message.

[0192] Clause 2. The first apparatus according to Clause 1, wherein the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes Radio Link Control (RLC) retransmission of the first data packet, and the HARQ retransmission is not triggered by the HARQ feedback message.

[0193] Clause 3. The first apparatus according to Clause 2, wherein the retransmission of the second data packet includes at least one of the following: blind HARQ retransmission or autonomous HARQ retransmission of the second data packet, and retransmission of the RLC Protocol Data Unit (PDU) of the second data packet after transmitting the HARQ feedback message.

[0194] Clause 4. The first apparatus according to Clause 2 or 3, wherein the retransmission of the second data packet is received separately from and without multiplexing with the data packets in the Acknowledgment Mode (AM) in the Media Access Control Protocol (MAC) Data Unit.

[0195] Clause 5. The first device according to any one of Clauses 1 to 4, wherein the first device is further caused to: receive from the second device an authorization message for a third data packet destined for the second device, the authorization message including a new data indicator indicating whether the third data packet has been previously transmitted; and retransmit the third data packet to the second device via a second protocol layer of the second device based on the new data indicator indicating that the third data packet has not been previously transmitted.

[0196] Clause 6. The first device according to Clause 5, wherein the first device is further caused to perform one of the following: disable retransmission of the third data packet to the second device via the first protocol layer; perform blind retransmission or autonomous retransmission of the third data packet to the second device via the first protocol layer; or perform RLC protocol data unit (PDU) retransmission of the third data packet after receiving an authorization message.

[0197] Clause 7. The first apparatus according to Clause 6, wherein the retransmission of the third data packet is transmitted separately from and without multiplexing with the data packets in the Acknowledgment Mode (AM) in the Media Access Control Protocol (MAC) Data Unit.

[0198] Clause 8. The first device according to Clause 6, wherein retransmission of the third data packet is stored by the Radio Link Control (RLC) protocol and transmitted to the second device after a grant message is received.

[0199] Clause 9. The first device according to any one of Clauses 1 to 8, wherein the first device is further caused to receive from the second device a configuration including at least one of the following: for activating or deactivating at least one condition for blind retransmission or autonomous retransmission via the first protocol layer, or for activating or deactivating at least one condition for retransmission based on an authorization message via the second protocol layer.

[0200] Clause 10. The first device according to any one of Clauses 1 to 9, wherein the first device includes terminal equipment and the second device includes network equipment.

[0201] Clause 11. A second means for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second means to at least: receive a feedback message from a first means via a first protocol layer of the second means, the first data packet being destined for the first means; and if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated for the first means, perform at least one of the following: transmit a retransmission of the first data packet from the second protocol layer of the second means to the first means without transmitting a retransmission of a data packet associated with the UM; transmit a retransmission of a second data packet associated with the UM from the first protocol layer of the second means to the first means; and, upon receiving the feedback message, transmit a retransmission of the second data packet associated with the UM from the second protocol layer of the second means to the first means.

[0202] Clause 12. The second apparatus according to Clause 11, wherein the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes a Radio Link Control (RLC) retransmission of the first data packet, and the HARQ retransmission is not triggered by the HARQ feedback message.

[0203] Clause 13. The second apparatus according to Clause 12, wherein the retransmission of the second data packet includes at least one of the following: blind retransmission or autonomous HARQ retransmission of the second data packet, wherein the RLC protocol data unit (PDU) of the second data packet is retransmitted after receiving a HARQ feedback message.

[0204] Clause 14. The second apparatus according to Clause 12 or 13, wherein the retransmission of the second data packet is transmitted separately from and without multiplexing with the data packets in the Acknowledgment Mode (AM) in the Media Access Control Protocol Data Unit.

[0205] Clause 15. The second device according to Clause 12 or 13, wherein the retransmission of the second data packet is stored by the Radio Link Control (RLC) protocol and transmitted to the first device after a feedback message is received.

[0206] Clause 16. The second device according to any one of Clauses 11 to 15, wherein the second device is further caused to: deactivate blind retransmission or autonomous retransmission of data packets via the first protocol layer if it is determined that no bearer in the UM of the second protocol layer is activated for the first device.

[0207] Clause 17. The second device according to any one of Clauses 11 to 16, wherein the second device is further caused to: transmit to the first device an authorization message for a third data packet destined for the second device, the authorization message including a new data indicator indicating whether the third data packet has been previously transmitted; and receive a retransmission of the third data packet from the first device via a second protocol layer of the second device based on the new data indicator indicating that the third data packet has not been previously transmitted.

[0208] Clause 18. The second apparatus according to any one of Clauses 11 to 17, wherein the second apparatus is further caused to transmit to the first apparatus a configuration including at least one of the following: for activating or deactivating at least one condition for blind retransmission or autonomous retransmission via the first protocol layer, or for activating or deactivating at least one condition for retransmission based on an authorization message via the second protocol layer.

[0209] Clause 19. The second device according to any one of Clauses 11 to 18, wherein the first device includes terminal equipment and the second device includes network equipment.

[0210] Clause 20. A method for communication, comprising: at a first device, transmitting a feedback message of a first data packet, the first data packet originating from the second device, to the second device via a first protocol layer of the second device; and if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated, performing at least one of the following: receiving a retransmission of the first data packet from the second protocol layer of the second device without receiving a retransmission of a data packet associated with the UM; receiving a retransmission of a second data packet associated with the UM from the first protocol layer of the second device; and receiving a retransmission of the second data packet associated with the UM from the second protocol layer of the second device after transmitting the feedback message.

[0211] Clause 21. A method for communication, comprising: at a second device, receiving, via a first protocol layer of the second device, a feedback message for a first data packet destined for the first device; and if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated for the first device, performing at least one of the following: transmitting a retransmission of the first data packet from the second protocol layer of the second device to the first device without transmitting a retransmission of a data packet associated with the UM; transmitting a retransmission of a second data packet associated with the UM from the first protocol layer of the second device to the first device; and, upon receiving the feedback message, transmitting a retransmission of the second data packet associated with the UM from the second protocol layer of the second device to the first device.

[0212] Clause 22. A first apparatus for communication, comprising: a component for transmitting a feedback message of a first data packet from the second apparatus to the second apparatus via a first protocol layer; and a component for performing at least one of the following if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated: receiving a retransmission of the first data packet from the second protocol layer of the second apparatus without receiving a retransmission of a data packet associated with the UM; receiving a retransmission of a second data packet associated with the UM from the first protocol layer of the second apparatus; and receiving a retransmission of the second data packet associated with the UM from the second protocol layer of the second apparatus after transmitting the feedback message.

[0213] Clause 23. A second means for communication, comprising: a component for receiving a feedback message of a first data packet from a first means via a first protocol layer of the second means, the first data packet being destined for the first means; and a component for performing at least one of the following if it is determined that a first bearer in an unacknowledged mode (UM) of the second protocol layer is activated for the first means: transmitting a retransmission of the first data packet from the second protocol layer of the second means to the first means without transmitting a retransmission of a data packet associated with the UM; transmitting a retransmission of a second data packet associated with the UM from the first protocol layer of the second means to the first means; and transmitting a retransmission of the second data packet associated with the UM from the second protocol layer of the second means to the first means after receiving the feedback message.

[0214] Clause 24. A computer-readable medium including instructions stored thereon for causing a device to perform at least the method described in accordance with Clause 20 or Clause 21.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: A feedback message of a first data packet is transmitted to the second device via the first protocol layer of the second device, the first data packet originating from the second device; as well as If it is determined that the first bearer in the unacknowledged mode (UM) of the second protocol layer is active, then perform at least one of the following: The second protocol layer of the second device receives retransmissions of the first data packet, but does not receive retransmissions of data packets associated with the UM; Receive retransmission of the second data packet associated with the UM from the first protocol layer of the second device; After transmitting the feedback message, a retransmission of the second data packet associated with the UM is received from the second protocol layer of the second device.

2. The first apparatus of claim 1, wherein the feedback message includes a Hybrid Automatic Repeat Request (HARQ) feedback message via the physical protocol layer, and the retransmission of the first data packet includes Radio Link Control (RLC) retransmission of the first data packet, and the HARQ retransmission is not triggered by the HARQ feedback message.

3. The first apparatus according to claim 2, wherein the retransmission of the second data packet comprises at least one of the following: Blind HARQ retransmission or autonomous HARQ retransmission of the second data packet. After transmitting the HARQ feedback message, the RLC protocol data unit (PDU) of the second data packet is retransmitted.

4. The first apparatus according to claim 2 or 3, wherein the retransmission of the second data packet is received separately from the data packet in Acknowledgment Mode (AM) in Media Access Control Protocol Data Unit and without multiplexing the data packet in AM.

5. The first device according to any one of claims 1 to 3, wherein the first device is further caused to: Receive an authorization message from the second device for a third data packet destined for the second device, the authorization message including a new data indicator indicating whether the third data packet was previously transmitted; and Based on the new data indicator indicating that the third data packet has not been previously transmitted, a retransmission of the third data packet is transmitted to the second device via the second protocol layer of the second device.

6. The first device according to claim 5, wherein the first device is further caused to perform one of the following: Disabling the retransmission of the third data packet to the second device via the first protocol layer; Perform blind or autonomous retransmission of the third data packet to the second device via the first protocol layer; Upon receiving the authorization message, the RLC protocol data unit (PDU) of the third data packet is retransmitted.

7. The first apparatus of claim 6, wherein the retransmission of the third data packet is transmitted separately from the data packets in Acknowledgment Mode (AM) in Media Access Control Protocol (MAC) Data Unit and is not multiplexed with the data packets in AM mode.

8. The first apparatus of claim 6, wherein the retransmission of the third data packet is stored by the Radio Link Control (RLC) protocol and transmitted to the second apparatus after the authorization message is received.

9. The first device according to any one of claims 1 to 3, wherein the first device is further caused to: Receive a configuration from the second device including at least one of the following: At least one condition is used to activate or deactivate blind or autonomous retransmissions via the first protocol layer, or Used to activate or deactivate at least one condition for retransmission of the authorized message via the second protocol layer.

10. The first device according to any one of claims 1 to 3, wherein the first device includes a terminal device, and the second device includes a network device.

Images