Artificial intelligence enabled automatic repeat request

Abstract

Methods, systems, and devices are described for wireless communication. A wireless device can receive a configuration including a first set of one or more parameters for an automatic repeat request (ARQ) process associated with a radio link control (RLC) entity of the wireless device. At least one parameter of the first set of one or more parameters is associated with a plurality of values. The wireless device can select a value of the plurality of values based at least in part on a second set of one or more parameters. The wireless device can transmit a negative acknowledgement (NACK) for a protocol data unit (PDU) of a set of one or more PDUs, and discard the PDU based at least in part on the at least one NACK and the selected value of the plurality of values for the ARQ process.

Description

Cross-references

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 609,673, filed March 19, 2024, entitled “ARTIFICIAL INTELLIGENCE-ENABLED AUTOMATIC REPEAT REQUEST”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0002] The following content relates to wireless communication, including Automatic Repeat Request (ARQ) enabled by artificial intelligence (AI). Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses that support automated repeat requests (ARQ) enabled by artificial intelligence (AI).

[0005] A method for wireless communication by a wireless device is described. The method may include: receiving control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with a Radio Link Control (RLC) entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values; selecting a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters; sending at least one negative acknowledgment (NACK) for at least one PDU from a set of one or more Protocol Data Units (PDUs) associated with the RLC entity of the wireless device; and discarding the at least one PDU based on the at least one NACK for the at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0006] A wireless device for wireless communication is described. The wireless device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to cause the wireless device to: receive control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values; select a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters; send at least one NACK for at least one PDU from the set of one or more PDUs associated with the RLC entity of the wireless device; and discard the at least one PDU based on the at least one NACK for the at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0007] Another wireless device for wireless communication is described. The wireless device may include: components for receiving control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values; components for selecting a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters; components for transmitting at least one NACK for at least one PDU from the set of one or more PDUs associated with the RLC entity of the wireless device; and components for discarding the at least one PDU based on the at least one NACK for the at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values; select a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters; send at least one NACK for at least one PDU from the set of one or more PDUs associated with the RLC entity of the wireless device; and discard the at least one PDU based on the at least one NACK for the at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0009] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, the at least one PDU includes one or more of at least one RLC Service Data Unit (SDU) or a portion of the at least one RLC SDU, the at least one RLC SDU or the portion of the at least one RLC SDU corresponding to a minimum sequence number, wherein discarding the at least one PDU may include operations, features, components, or instructions for discarding the at least one RLC SDU or the portion of the at least one RLC SDU at least in part based on the elapsed time of a threshold duration.

[0010] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for updating at least one parameter in the first set of one or more parameters based on discarding the at least one RLC SDU or a portion of the at least one RLC SDU and based on a sequence number associated with the at least one RLC SDU, wherein the at least one parameter is associated with a reception time window for the set of one or more PDUs.

[0011] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: updating a reception time window for one or more PDUs based on at least one NACK for the at least one PDU and according to a selected value from a set of values ​​for the ARQ procedure associated with the RLC entity of the wireless device; and sending an indication to a second wireless device of the updated reception time window for the one or more PDUs.

[0012] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, the second set of one or more parameters indicates one or more of the following: a drop time window that enables the wireless device to drop a certain number of PDUs in the set of one or more PDUs; a counter associated with tracking the number of PDUs dropped; a drop rate associated with the number of PDUs dropped in the set of one or more PDUs during the drop time window; or a timer that indicates a threshold duration between at least one first PDU and at least one second PDU in the set of one or more PDUs that are dropped.

[0013] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a status report via the RLC entity of the wireless device, the status report including one or more NACKs of the at least one NACK for the at least one PDU, wherein the status report includes at least one status PDU, and wherein the at least one status PDU includes at least one field indicating a sequence number associated with the at least one PDU.

[0014] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, the serial number associated with the at least one PDU corresponds to the start of a discard time window that enables the wireless device to discard a certain number of PDUs in the set of one or more PDUs, and the serial number associated with the at least one PDU begins from the last reported discarded serial number associated with at least one second PDU.

[0015] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, the at least one state PDU indicates one or more of the following: a count associated with a certain number of PDUs discarded in the set of one or more PDUs during a discard time window, or a discard rate of a certain number of PDUs discarded in the set of one or more PDUs during the discard time window.

[0016] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: generating a control PDU comprising a set of one or more fields, wherein at least one field in the set of one or more fields includes an indication of a discard event corresponding to the discard of the at least one PDU and the associated sequence number of the at least one PDU, wherein the control protocol data unit includes a priority higher than that of other PDUs associated with the logical control channel (LCH); and transmitting the control PDU to a second wireless device at least in part based on the absence of a polling bit or in response to the discard of the at least one PDU.

[0017] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: determining whether the number of discarded PDUs in the set of one or more PDUs meets a threshold; declaring an RLF event based on the fact that the number of discarded PDUs in the set of one or more PDUs meets the threshold; and sending an indication of the RLF event to a second wireless device.

[0018] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, the first set of one or more parameters includes inputs to a learning model for the ARQ process, the second set of one or more parameters includes outputs of the learning model for the ARQ process, and the selected value among the plurality of values ​​for the ARQ process may be based on the inputs and outputs of the learning model.

[0019] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, at least one parameter in the first set of one or more parameters includes at least one threshold number of dropped PDUs, at least one Packet Data Convergence Protocol (PDCP) state, at least one Hybrid Automatic Repeat Request (HARQ) state, at least one traffic flow state, at least one radio condition, or at least one observed downlink assignment, and wherein the at least one threshold number of dropped PDUs, the at least one PDCP state, the at least one HARQ state, the at least one traffic flow state, the at least one radio condition, or the at least one observed downlink assignment corresponds to the input of the learning model, and the method, apparatus, and nontransitory computer-readable media may include additional operations, features, components, or instructions for: declaring an RLF event based on one or more of the at least one threshold number of dropped PDUs or the output of the learning model for the ARQ process; and sending an indication of the RLF event to a second wireless device.

[0020] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: suppressing the reset of a recombination timer associated with the set of one or more PDUs based on the output of the learning model used for the ARQ process; and terminating the recombination timer based on the serial number associated with the at least one PDU and the output of the learning model used for the ARQ process.

[0021] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting an instruction to the PDCP entity of the wireless device to discard the at least one PDU, wherein the instruction indicates a sequence number associated with the at least one PDU, and wherein the PDCP entity of the wireless device maps the sequence number associated with the at least one PDU to a corresponding PDCP sequence number, terminating the reordering of sequence numbers associated with the set of one or more PDUs, populating the sequence number with a dummy PDU, or updating the reordering time window associated with the set of one or more PDUs, or a combination thereof.

[0022] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: generating a report associated with the learning model, wherein the report includes a set of one or more logs associated with the processing of one or more PDUs in the set of one or more PDUs according to the learning model; sending the report associated with the learning model to a second wireless device, wherein the second wireless device includes a network entity, the network entity including a base station or server associated with the learning model, wherein at least one log in the set of one or more logs indicates a fourth set of one or more parameters corresponding to the output of the learning model, the fourth set of one or more parameters including one or more of the following: latency associated with the processing of the set of one or more PDUs; the number of retransmissions associated with the set of one or more PDUs; the quality of service (QoS) associated with the set of one or more PDUs based on the first set of one or more parameters and the second set of one or more parameters; and the quality of the PDU session based on the third set of one or more parameters.

[0023] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a report to a second wireless device, the report including capability information indicating whether the wireless device supports the learning model, the capability information including one or more bit fields, and wherein the capability information may be based on performance metrics associated with the learning model, and wherein the control signaling indicating the configuration is received based on the capability information indicating whether the wireless device supports the learning model.

[0024] In some examples of the methods, wireless devices, and nontransitory computer-readable media described herein, the first set of one or more parameters includes one or more of the following: a first threshold number of PDUs allowed to be dropped in the set of one or more PDUs; a drop time window that enables the wireless device to drop a certain number of PDUs in the set of one or more PDUs; a first threshold duration between dropping at least one first PDU and at least one second PDU in the set of one or more PDUs; a second threshold number of PDUs allowed to be dropped in the set of one or more PDUs before declaring an RLF event; a second threshold duration for dropping sequence numbers; an indication for enabling or disabling the learning model; one or more QoS flows associated with the learning model; or a third threshold duration for dropping sequence numbers associated with corresponding PDUs.

[0025] Some examples of the methods, wireless devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: determining the number of discarded PDUs in the set of one or more PDUs, wherein each discarded PDU may be associated with a corresponding sequence number; and sending control signaling to a second wireless device indicating one or more of the number of discarded PDUs and at least one second NACK associated with the number of discarded PDUs. Attached Figure Description

[0026] Figure 1 An example of an AI-enabled ARQ wireless communication system is shown, according to one or more aspects of this disclosure.

[0027] Figure 2 An example of an ARQ network architecture that supports AI enablement is shown in accordance with one or more aspects of this disclosure.

[0028] Figure 3 A block diagram of an AI-enabled ARQ UE is shown, according to one or more aspects of this disclosure.

[0029] Figures 4 to 10An example of an ARQ process flow that supports AI enablement according to one or more aspects of this disclosure is shown.

[0030] Figure 11 An example of an AI-enabled ARQ wireless communication system is shown, according to one or more aspects of this disclosure.

[0031] Figure 12 An example of an ARQ process flow that supports AI enablement according to one or more aspects of this disclosure is shown.

[0032] Figure 13 and Figure 14 A block diagram of an AI-enabled ARQ device is shown, according to one or more aspects of this disclosure.

[0033] Figure 15 A block diagram of an AI-enabled ARQ communication manager is shown, according to one or more aspects of this disclosure.

[0034] Figure 16 A diagram of a system including an AI-enabled ARQ device is shown according to one or more aspects of this disclosure.

[0035] Figure 17 A flowchart illustrating an ARQ method for enabling AI according to one or more aspects of this disclosure is shown. Detailed Implementation

[0036] Wireless devices can be equipped with protocol stacks to support various functionalities associated with wireless communication. Protocol stacks can include various protocol layers. An example of a protocol layer is the RLC layer (also referred to herein as the RLC entity). The RLC layer can perform the delivery of upper-layer protocol data units (PDUs) according to one or more modes, including: Acknowledgment mode (AM), Unacknowledgment mode (UM), and Transparent mode. ™ Based on the data transmission mode configured for the RLC entity, the RLC layer can be referred to as a TM RLC entity, UMRLC entity, or AM RLC entity. The RLC layer can receive RLC Service Data Units (SDUs) from and / or send RLC Service Data Units (SDUs) to higher protocol layers in the wireless device's protocol stack. The RLC layer performs error correction through ARQ, RLC SDU concatenation, segmentation and reassembly, RLC data PDU resegmentation, RLC data PDU reordering, duplicate detection, RLC reconstruction, and protocol error detection and recovery.

[0037] In some cases, the RLC layer may experience excessive loss of RLC SDUs in the UM, especially when relying solely on HARQ. In other cases, the RLC layer may experience increased latency in the AM due to retransmissions associated with RLC SDUs and RLC data PDUs (e.g., each retransmission may be associated with a reassembly timer), resegmentation, reordering delays, etc. In some cases, this can lead to high variability in round-trip latency (RTT) and excessive memory usage. In other cases, this can cause the RLC layer to declare an RLF event due to meeting thresholds or buffer limits at the radio device as described herein. Additionally, in some cases, the RLC layer may experience inefficient use of resources associated with monitoring RLC SDUs. For example, the RLC layer may receive a subset of RLC SDUs during the receive time window and continue to attempt to receive another subset of RLC SDUs during the receive time window. In some cases, the RLC layer may be unable to update (e.g., modify, adjust) the receive time window until all RLC SDUs are received at the RLC layer. Therefore, the RLC layer may continue to request lost RLC SDUs.

[0038] Various aspects of this disclosure relate to enabling wireless devices (e.g., the RLC layer of a wireless device) to support the processing of RLC SDUs and / or RLC data PDUs based on a learned model (e.g., an artificial intelligence (AI) / machine learning (ML) model). The learned model can improve the efficient processing (e.g., discarding) of RLC SDUs and / or RLC data PDUs. In some examples, the learned model enables the wireless device to support efficient monitoring of congestion levels and dynamically adjust parameters used for the processing (e.g., discarding) of RLC SDUs and / or RLC data PDUs. Additionally, the wireless device may be configured with one or more parameters and constraints for the learned model. In some examples, the wireless device may maintain and report logs for tracking the performance of the learned model, particularly logs related to the processing of RLC SDUs and / or RLC data PDUs.

[0039] By enabling wireless devices to support the processing of RLC SDUs and / or RLC data PDUs based on a learning model (e.g., an AI / ML model), wireless devices can mitigate unnecessary retransmissions of RLC SDUs and / or RLC data PDUs, etc., as described herein. It should be understood that other models or data structures (e.g., tables) can be used to support and enable wireless devices (e.g., the RLC layer of the wireless device) to support the processing (e.g., discarding) of RLC SDUs and / or RLC data PDUs as described herein.

[0040] The various aspects of this disclosure are first described in the context of a wireless communication system. Further illustrations, system diagrams, and flowcharts relating to AI-enabled ARQ are provided, and these diagrams are further described with reference to these figures.

[0041] Figure 1 An example of an AI-enabled ARQ wireless communication system 100 is shown according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0042] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0043] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0044] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0045] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0046] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0047] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) (such as CU 160), a Distributed Unit (DU) (such as DU 165), a Radio Unit (RU) (such as RU 170), a RAN Intelligent Controller (RIC) (such as RIC 175) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system (such as SMO system 180), or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0048] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more Cu) can connect to DU 165 (e.g., one or more Du) or RU 170 (e.g., one or more Ru) or some combination thereof, and Du 165, Ru 170, or both can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different Ru, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0049] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include IAB mobile terminals (IAB-MTs) controlled (e.g., scheduled) by one or more Dus (e.g., Du 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more Dus (e.g., Du 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0050] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other Cus (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0051] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may be relayed for Ue transmissions via other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. The IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB nodes (e.g., IAB node 104) to receive signaling from parent IAB nodes (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB nodes to send signals to child IAB nodes or UE 115.

[0052] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by the DU 165 of IAB node 104.

[0053] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0054] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0055] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a repeater, and network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0056] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0057] In some examples, such as in carrier aggregation configurations, carriers may have acquisition or control signaling that coordinates operation against other carriers. Carriers may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. Carriers may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or carriers may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0058] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0059] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0060] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0061] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0062] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0063] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0064] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0065] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0066] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0067] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast to macro cells, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also support communication via one or more cells using one or more component carriers.

[0068] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0069] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies can be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0070] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0071] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0072] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0073] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where each UE 115 sends to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0074] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure such as roadside units, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, Ru 170) using vehicle-to-network (V2N) communication, or communicate with both.

[0075] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0076] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0077] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0078] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0079] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0080] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0081] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Beam directions may be identified (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) by transmission along different beam directions for later transmission or reception by network entity 105.

[0082] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., network entity 105 or UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0083] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0084] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined by listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0085] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0086] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., ARQ). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device can provide HARQ feedback in subsequent time slots or according to a different time interval.

[0087] Figure 2An example of an AI-enabled ARQ network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify examples of one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more Cu 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). Cu 160-a may communicate with one or more Du 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). Du 165-a may communicate with one or more Ru 170-a via a corresponding fronthaul communication link 168-a. Ru 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple Ru 170-a simultaneously.

[0088] Each network entity in network entity 105 of network architecture 200 (e.g., Cu 160-a, Du 165-a, Ru170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0089] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0090] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more Ru 170-a units. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional breakdown, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0091] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a units to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0092] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, Cu 160-a, Du 165-a, Ru 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more Ru 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0093] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updates, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via the A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) connecting one or more Cu 160-a, one or more Du 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b.

[0094] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0095] Figure 3 A block diagram 300 of a UE 115-b supporting AI-enabled ARQ according to one or more aspects of this disclosure is shown. UE 115-b may be as described herein with reference to the respective references. Figure 1 and Figure 2 Examples of various aspects of the described UE 115. UE 115-b can be implemented as described in the reference. Figure 1 The wireless communication system 100 described herein. Additionally or alternatively, UE 115-b may implement as referenced herein. Figure 2 The various aspects of the network architecture 200 described, or those aspects that can be implemented.

[0096] exist Figure 3 In the example, UE 115-b may support a learning model management process 302 associated with one or more learning models for enabling AI-based ARQ. The learning model management process 302 may include one or more of the following: a (re)configuration phase 305, an activation phase 310, a training phase 315 (also referred to as an inference phase), a deactivation phase 320, or a monitoring phase 325. The one or more learning models for enabling AI-based ARQ may be stored locally at UE 115-b (e.g., one or more memories storing processor-executable code for enabling AI-based ARQ of at least one learning model). Alternatively, UE 115-b may obtain (e.g., download) the one or more learning models for enabling AI-based ARQ, for example, via network entity 105 or base station 140, which may be as referred to herein respectively. Figure 1 and Figure 2 Examples of network entity 105 or base station 140 described.

[0097] One or more operations of the learning model management process 302 may be implemented by the UE 115-b or components as described herein (e.g., one or more memories storing processor-executable code, one or more processors coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE 115-b to perform operations associated with AI-enabled ARQ). In the following description of the learning model management process 302, one or more operations performed by the UE 115-b may be performed in a different order or at different times. Some operations may also be omitted from the learning model management process 302, and other operations may be added to the learning model management process 302.

[0098] During the (re)configuration phase 305, UE 115-b may receive a set of one or more configurations from network entity 105 or base station 140. This set of configurations includes a set of one or more parameters for configuring or reconfiguring one or more learning models (e.g., AI / ML models) for enabling AI-based ARQ. UE 115-b may receive a request message from network entity 105 or base station 140 for configuring or reconfiguring one or more learning models for enabling AI-based ARQ. This request may include a set of one or more configurations and one or more identifiers associated with the one or more learning models for enabling AI-based ARQ. UE 115-b may send a response message to network entity 105 or base station 140, including an acknowledgment of the request message.

[0099] In some examples, a set of one or more parameters can be used to manage (e.g., train, update, modify) one or more learning models. In other examples, the set of one or more parameters can be inputs to one or more learning models (e.g., for inference of one or more learning models). In still other examples, the set of one or more parameters can be used to monitor one or more performance metrics (also known as Key Performance Indicators (KPIs)) for one or more learning models. Additionally or alternatively, the set of one or more configurations may include one or more RRC configurations (e.g., one or more measurement configurations, one or more MAC configurations, etc.).

[0100] During activation phase 310, UE 115-b may activate at least one learning model for AI-enabled ARQ (e.g., to perform at least one action associated with AI-enabled ARQ). During training phase 315, UE 115-b may train at least one learning model for AI-enabled ARQ at least partially based on a set of one or more inputs (e.g., a set of one or more parameters) to obtain a set of one or more outputs. During deactivation phase 320, UE 115-b may deactivate at least one learning model (e.g., to perform at least one action associated with AI-enabled ARQ).

[0101] During monitoring phase 325, UE 115-b may monitor (e.g., track) the performance of at least one learning model. One or more of network entity 105, base station 140, or UE 115-b may share (e.g., transmit, receive, exchange) feedback associated with the performance of at least one learning model used for AI-enabled ARQ. Performance may be associated with system performance (e.g., spectral efficiency, power consumption, latency, etc.) or model performance (e.g., prediction accuracy, resource usage, inference latency, etc.). In some examples, one or more of network entity 105, base station 140, or UE 115-b may trigger a handover event that includes, for example, switching (e.g., changing) from at least one learning model to at least one different learning model based at least partially on feedback associated with the performance of at least one learning model. In some other examples, one or more of network entity 105, base station 140, or UE 115-b may update the training of at least one learning model used for AI-enabled ARQ based at least partially on feedback associated with the performance of at least one learning model.

[0102] UE 115-b may switch from at least one learning model to a different learning model, at least in part, based on functionality supported by at least one different learning model (e.g., actions associated with AI-enabled ARQ). In some examples, UE 115-b may receive a request message from network entity 105 or base station 140 for switching to at least one different learning model. The request message may indicate an identifier associated with at least one different learning model for AI-enabled ARQ, and UE 115-b may identify at least one different learning model, at least in part, based on that identifier. During the activation phase 310 of the learning model management process 302, UE 115-b may activate at least one different learning model for AI-enabled ARQ (e.g., a different AI / ML model). Additionally, during the deactivation phase 320, UE 115-b may deactivate at least one learning model (e.g., the current AI / ML model).

[0103] Additionally or alternatively, during monitoring phase 325, UE 115-b may trigger a handover event at least in part based on changes in one or more parameters of UE 115-b (e.g., number of antennas, number of carriers, etc.). In some examples, UE 115-b may trigger a handover event at least in part based on changes in UE 115-b's location (e.g., from an indoor environment to an outdoor environment, or vice versa). In some other examples, UE 115-b may trigger a handover event at least in part based on changes in services (e.g., network slicing, QoS flow, sessions, etc.).

[0104] Therefore, UE 115-b can be configured to support the management (e.g., configuration, reconfiguration, activation, deactivation, monitoring, reporting, etc.) of one or more learning models used to enable AI in ARQ.

[0105] Figure 4 An example of an ARQ process flow 400 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 400 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, the process flow 400 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 400 may include UE 115-c and base station 140-a, which may be examples of UE 115 and base station 140 as described herein. In the following description of process flow 400, operations between UE 115-c and base station 140-a may be transmitted in a different order than shown, or operations performed by UE 115-c and base station 140-a may be performed in a different order or at different times. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.

[0106] exist Figure 4 In the example, UE 115-c may support providing base station 140-a with indications of one or more learning models for AI-enabled ARQ, including one or more features of AI-enabled ARQ supported by UE 115-c. At 405, base station 140-a may send a request message (e.g., UE capability query), and UE 115-c may receive the request message. UE 115-c may determine a set of one or more UE capabilities for AI-enabled ARQ in response to the UE capability query. For example, UE 115-c may determine whether UE 115-c supports AI / ML functionality, including one or more learning models (e.g., AI / ML models) or one or more features associated with one or more learning models for AI-enabled ARQ.

[0107] At 410, in response to the request message, UE 115-c may send a response message (e.g., UE capability information), and base station 140-a may receive the response message. The UE capability information may include a set of one or more features supported by UE 115-c for AI-enabled ARQ. In some examples, the UE capability information may include a set of one or more identifiers associated with one or more learning models supported by UE 115-c for AI-enabled ARQ. Additionally or alternatively, the UE capability information may include at least one field (e.g., information element (IE), flag, etc.) indicating whether the corresponding learning model is loaded (e.g., initialized, stored, cached, etc.) at UE 115-c. Additionally or alternatively, the UE capability information may include a set of one or more identifiers associated with one or more learning model structures for AI-enabled ARQ, or a set of one or more parameters of one or more features associated with one or more learning model structures for AI-enabled ARQ.

[0108] Therefore, UE 115-c can be configured to support the exchange of UE capability information associated with one or more learning models used for AI-enabled ARQ.

[0109] Figure 5 An example of an ARQ process flow 500 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 500 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, the process flow 500 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 500 may include UE 115-d and base station 140-b, which may be examples of UE 115 and base station 140 as described herein. In the following description of process flow 500, operations between UE 115-d and base station 140-b may be transmitted in a different order than the example order shown, or operations performed by UE 115-d and base station 140-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0110] exist Figure 5In the example, UE 115-d may support providing UE Assistance Information (UAI) to base station 140-b. More specifically, UE 115-d may support sending a UAI to base station 140-b for managing one or more learning models used to enable AI-based ARQ. At 505, UE 115-d may send the UAI and base station 140-b may receive the UAI, which may indicate one or more restrictions (also referred to as restricted UE capabilities) associated with one or more learning models used to enable AI-based ARQ. For example, restricted UE capabilities may include a set of one or more learning models, a set of one or more identifiers associated with the set of one or more learning models, or both. In some examples, restricted UE capabilities may exclude a set of one or more identifiers. In some examples, UE 115-d may indicate a request to adjust (e.g., reduce, lower, increase) the concurrency of one or more learning models. For example, UE 115-d may indicate a threshold number of concurrency associated with one or more learning models used to enable AI-based ARQ (e.g., " maxAIMLconcurrency-Preference (”).

[0111] UE 115-d may generate and send a UAI to base station 140-b based at least in part on conditions (e.g., events). Examples of one or more conditions may include, but are not limited to: UE 115-d's battery level meeting a battery level threshold, one or more processors of UE 115-d having a processor usage level meeting a processor usage level threshold, or one or more processors of UE 115-d having a heat level meeting a heat level threshold. For example, UE 115-d may send a UAI to base station 140-b at least in part based on one or more of the following to manage (e.g., disable, activate) one or more learning models for AI-enabled ARQ at UE 115-d: UE 115-d's battery level meeting a battery level threshold, one or more processors of UE 115-d having a processor usage level meeting a processor usage level threshold, or one or more processors of UE 115-d having a heat level meeting a heat level threshold.

[0112] Additionally or alternatively, in some examples, the UAI may include a request for a set of one or more configurations associated with one or more learning models for enabling AI-based ARQ. In some examples, UE 115-d may request a set of one or more configurations associated with one or more learning models for enabling AI-based ARQ from base station 140-b, at least in part, based on a change in the environment of UE 115-d. In some other examples, UE 115-d may request a set of one or more configurations associated with one or more learning models for enabling AI-based ARQ from base station 140-b, at least in part, based on a change in the state of UE 115-d (e.g., a change between one or more of idle, inactive, or connected states).

[0113] In other examples, UE 115-d may request a set of one or more configurations associated with one or more learning models for AI-enabled ARQ from base station 140-b, at least in part, based on session establishment associated with a network slice. For example, UE 115-d may establish a session associated with a network slice (e.g., a PDU session) and request a set of one or more configurations associated with one or more learning models for AI-enabled ARQ from base station 140-b. In some other examples, UE 115-d may request a set of one or more configurations associated with one or more learning models for AI-enabled ARQ from base station 140-b, at least in part, based on a change in the geographic coverage area of ​​UE 115-d. For example, UE 115-d may enter a new geographic coverage area of ​​a cell, a Public Land Mobile Network (PLMN), and request a set of one or more configurations associated with one or more learning models for AI-enabled ARQ from base station 140-b.

[0114] At least one configuration from a set of one or more configurations is associated with supplying network data as input for one or more learning models (e.g., AI / ML models). In some examples, at least one configuration may indicate at least one identifier associated with at least one learning model that supports using network data as input to the at least one learning model. In some examples, UE 115-d may, for example, request network data from base station 140-b (e.g., on demand) via UAI based at least in part on a set of one or more configurations associated with supplying network data as input for one or more learning models (e.g., AI / ML models).

[0115] At point 510, one or more of UE 115-d or base station 140-b may configure or reconfigure at least one learning model for enabling AI-based ARQ. For example, base station 140-b may select at least one learning model for enabling AI-based ARQ to be disabled at UE 115-d, at least partially based on UAI, and send control signaling (e.g., RRC, MAC-CE, DCI) to disable at least one learning model for enabling AI-based ARQ. For example, base station 140-b may determine and select which learning model to disable at UE 115-d, at least partially based on UAI, and send control signaling (e.g., RRC, MAC-CE, DCI) instructing UE 115-d to disable at least one learning model for enabling AI-based ARQ. Additionally or alternatively, base station 140-b may determine and select which learning model to configure or reconfigure and activate at UE 115-d, at least partially based on UAI. For example, base station 140-b may determine and select which learning model to activate at UE 115-d based at least in part on UAI, and send control signaling (e.g., RRC, MAC-CE, DCI) instructing UE 115-d to activate at least one learning model for enabling AI ARQ.

[0116] Therefore, UE 115-d can be configured to support UAI switching for managing AI-enabled ARQ.

[0117] Figure 6 An example of an ARQ process flow 600 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 600 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, process flow 600 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 600 may include UE 115-e and base station 140-c, which may be corresponding examples of UE 115 and base station 140 as described herein. Additionally, process flow 600 may include a storage library 602 (e.g., a database) storing one or more learning models for AI-enabled ARQ. In the following description of process flow 600, operations between UE 115-e, base station 140-c, and storage library 602 may be sent in a different order than the example order shown, or operations performed by UE 115-e, base station 140-c, and storage library 602 may be performed in a different order or at different times. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0118] exist Figure 6In the example, one or more of UE 115-e or base station 140-c may support the execution of process 603 (e.g., a model configuration process), which may include the exchange of a set of one or more configurations (or a set of one or more parameters) associated with one or more learning models for enabling AI-ARQ. The set of one or more configurations (or a set of one or more parameters) associated with one or more learning models for enabling AI-ARQ may be stored at storage 602 (e.g., a database, etc.), and base station 140-c may obtain the set of one or more configurations (or the set of one or more parameters) from storage 602.

[0119] At 605, base station 140-c may send an RRC configuration message and UE 115-e may receive the RRC configuration message, which may include one or more sets of configurations (or one or more sets of parameters) associated with one or more learning models for AI-enabled ARQ. During procedure 603, base station 140-c may send the RRC configuration message and UE 115-e may receive the RRC configuration message; this procedure may be an RRC configuration procedure. In some examples, UE 115-e may configure one or more learning models for AI-enabled ARQ via Layer 3 (L3) of UE 115-e and at least in part based on one or more sets of configurations (or one or more sets of parameters) received in the RRC configuration message. At 610, for example, at least in part based on the RRC configuration message, UE 115-e may send an RRC configuration complete message and base station 140-c may receive the RRC configuration complete message. An RRC configuration completion message may indicate the completion of process 603 (e.g., the RRC configuration process), which includes configuring one or more learning models for enabling AI-based ARQ.

[0120] exist Figure 6In some examples, additionally or alternatively, at least one configuration from a set of one or more configurations may be used by base station 140-c to supply network data to UE 115-e for input to one or more learning models (e.g., AI / ML models). In some examples, at least one configuration may indicate at least one identifier associated with at least one learning model that supports network data as input to the at least one learning model. In some examples, UE 115-e may request base station 140-c to activate or deactivate the supply of network data as input to at least one learning model via MAC-CE. In some examples, UE 115-e may receive network data via unicast and on a physical downlink channel (e.g., physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH)), and base station 140-c may transmit this network data. In some other examples, UE 115-e may receive network data via MAC-CE or RRC messages, and base station 140-c may transmit this network data. In other examples, UE 115-e can receive network data via system information or multicast service (MBS), and base station 140-c can send (e.g., broadcast) this network data.

[0121] Additionally or alternatively, at least one configuration from a set of one or more configurations may be used to supply UE data to base station 140-c as input for one or more learning models (e.g., AI / ML models). In some examples, at least one configuration may indicate at least one identifier associated with at least one learning model that supports using UE data as input to the at least one learning model. Base station 140-c may request activation or deactivation from UE 115-e via MAC-CE to supply UE data as input to at least one learning model. In some examples, UE 115-e may transmit UE data via unicast and on a physical uplink channel (e.g., Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH)), and base station 140-c may receive this UE data. In some other examples, UE 115-e may transmit UE data via MAC-CE or RRC messages, and base station 140-c may receive this UE data.

[0122] At 615, base station 140-c may transmit a signal (also referred to as an activation signal or deactivation signal) for activating or deactivating one or more learning models for AI-enabled ARQ during process 613 (e.g., an activation / deactivation process for one or more learning models for AI-enabled ARQ), and UE 115-e may receive this signal. In some examples, base station 140-c may transmit a signal for activating or deactivating one or more learning models for AI-enabled ARQ via Layer 2 (L2) of UE 115-e, and UE 115-e may receive this signal. For example, base station 140-c may transmit a MAC-CE, and UE 115-e may receive this MAC-CE, which activates or deactivates one or more learning models for AI-enabled ARQ. In some examples, the activation or deactivation of one or more learning models for AI-enabled ARQ may be based at least in part on a handover event, as referenced herein. Figures 3 to 5 As described.

[0123] Therefore, one or more of the UE 115-e or base station 140-c can be configured to support managing AI-enabled ARQ at least in part based on one or more learning models for enabling AI ARQ via MAC-CE activation or deactivation, which allows for flexible management of AI-enabled ARQ.

[0124] Figure 7 An example of an ARQ process flow 700 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 700 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, process flow 700 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 700 may include UE 115-f, base station 140-d, and core network 130-a, which may be corresponding examples of UE 115, base station 140, and core network 130 as described herein. Additionally, process flow 700 may include a storage library 702 (e.g., a database) storing one or more learning models for AI-enabled ARQ. In the following description of process flow 700, operations between UE 115-f, base station 140-d, core network 130-a, and storage library 702 may be sent in a different order than the example order shown, or operations performed by UE 115-f, base station 140-d, core network 130-a, and storage library 702 may be performed in a different order or at different times. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0125] exist Figure 7In the examples, one or more of UE 115-f, base station 140-d, or core network 130-a may support the execution of one or more procedures 703 or 713, which may include exchanging a set of one or more configurations (or a set of one or more parameters) associated with one or more learning models for enabling AI ARQ. For example, one or more of UE 115-f, base station 140-d, or core network 130-a may support the execution of one or more procedures, which may include exchanging a set of one or more configurations (or a set of one or more parameters) associated with one or more learning models for enabling AI ARQ, at least in part based on the state of UE 115-f (e.g., idle state, inactive state). In some examples, one or more of UE 115-f, base station 140-d, or core network 130-a may support activating or deactivating one or more learning models for enabling AI ARQ for inference during the state of UE 115-f. For example, one or more of UE 115-f, base station 140-d, or core network 130-a may support activating or deactivating one or more learning models for AI-enabled ARQ to perform inference (e.g., training) on ​​one or more learning models for AI-enabled ARQ, as well as cell selection, cell reselection, RLF recovery, measurement operations, and random access channel operations (e.g., beam selection, random access channel timing (RO), etc.).

[0126] At 705, during process 703 (e.g., RRC process 703, NAS process 713), base station 140-d may transmit a set of one or more non-UE-specific configurations, and UE 115-f may receive such a set of one or more non-UE-specific configurations. For example, base station 140-d may broadcast system information including a set of one or more non-UE-specific configurations for enabling AI-based ARQ, and UE 115-f may receive such system information. The system information may include a System Information Block (SIB). The set of one or more non-UE-specific configurations may include one or more sets of one or more parameters, which may be associated with a set of one or more learning models for enabling AI-based ARQ, and include a set of one or more identifiers associated with the set of one or more learning models for enabling AI-based ARQ, etc.

[0127] Additionally or alternatively, at 710-a, for example via unicast transmission, base station 140-d may transmit a set of one or more UE-specific configurations for enabling AI-based ARQ, and UE 115-f may receive such a set of one or more UE-specific configurations. For example, base station 140-d may transmit an RRC message including a set of one or more UE-specific configurations for enabling AI-based ARQ, and UE 115-f may receive such an RRC message. The set of one or more UE-specific configurations may include one or more sets of one or more parameters, which may be associated with a set of one or more learning models, including a set of one or more identifiers associated with the set of one or more learning models for enabling AI-based ARQ. In some examples, the RRC message may be an RRC release message during an RRC release procedure. In some examples, at 710-b, one or more of the UE 115-f, base station 140-d, or core network 130-a (e.g., one or more network functions associated with core network 130-a) may exchange one or more NAS messages associated with a set of one or more UE-specific configurations.

[0128] At point 715, base station 140-d may transmit a signal (also referred to as an activation signal or deactivation signal) for activating or deactivating one or more learning models for AI-enabled ARQ during process 713 (e.g., an activation / deactivation process for one or more learning models for AI-enabled ARQ), and UE 115-f may receive this signal. In some examples, base station 140-d may transmit a signal for activating or deactivating one or more learning models for AI-enabled ARQ, and UE 115-f may receive this signal. For example, base station 140-d may transmit a MAC-CE, and UE 115-f may receive this MAC-CE, which activates or deactivates one or more learning models for AI-enabled ARQ, and inference (e.g., training) of one or more learning models may be performed during the idle or inactive state of UE 115-f. Thus, activating or deactivating one or more learning models for AI-enabled ARQ may be at least partially based on the idle or inactive state of UE 115-f.

[0129] Therefore, one or more of the UE 115-f, base station 140-d, or core network 130-a can support the activation or deactivation of one or more learning models for AI-enabled ARQ and the inference of one or more learning models for AI-enabled ARQ during the idle or inactive state of the UE 115-f.

[0130] Figure 8An example of an ARQ process flow 800 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 800 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, the process flow 800 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 800 may include UE 115-g, base station 140-e, and base station 140-f, which may be corresponding examples of UE 115 and base station 140 as described herein. In the following description of process flow 800, operations between UE 115-g, base station 140-e, and base station 140-f may be transmitted in a different order than the example order shown, or operations performed by UE 115-g, base station 140-e, and base station 140-f may be performed in a different order or at different times. Some operations may be omitted from process flow 800, and other operations may be added to process flow 800.

[0131] exist Figure 8 In the example, one or more of UE 115-g, base station 140-e, and base station 140-f may support managing AI-enabled ARQ during UE 115-g's mobility (also referred to as UE mobility). More specifically, one or more of UE 115-g, base station 140-e, and base station 140-f may support managing the AI / ML functionality of the AI-enabled ARQ associated with UE 115-g during a handover process that may include switching (e.g., transferring) the connection of UE 115-g from base station 140-e (also referred to as the source base station) to base station 140-f (also referred to as the target base station) while maintaining the ongoing AI / ML functionality of the AI-enabled ARQ.

[0132] At 805, one or more of the UE 115-g or base station 140-e may perform active inference (e.g., training) of one or more learning models for AI-enabled ARQ. The inference (e.g., training) of one or more learning models for AI-enabled ARQ may be based at least in part on one or more sets of one or more configurations for AI-enabled ARQ configured by base station 140-e, including one or more sets of one or more parameters.

[0133] At 810, during handover preparation 812, base station 140-e may send a handover request message and base station 140-f may receive the handover request message, which may include context information (e.g., AI / ML context) associated with one or more learning models for enabling AI-based ARQ. At 815, during handover preparation 812, base station 140-f may send a handover request confirmation message and base station 140-e may receive the handover request confirmation message, which may include one or more sets of one or more configurations for enabling AI-based ARQ configured by base station 140-f, including one or more sets of one or more parameters. In other words, base station 140-f can provide one or more sets of AI / ML configurations for UE 115-g to apply after handover from base station 140-e to base station 140-f. In some examples, base station 140-e may determine, at least in part, a set of one or more configurations for enabling AI ARQ based on context information (e.g., AI / ML context) received from base station 140-f, including one or more sets of one or more parameters. Additionally or alternatively, base station 140-e may determine, at least in part, a set of one or more configurations for enabling AI ARQ based on one or more of the UE capabilities of UE 115-g or the network capabilities of base station 140-f, including one or more sets of one or more parameters. In some examples, one or more of UE 115-g or base station 140-f may support some or all of the AI / ML functionality (e.g., enabling one or more features associated with at least one learning model).

[0134] At point 820, base station 140-e may send an RRC reconfiguration message, and UE 115-g may receive the RRC reconfiguration message. This RRC reconfiguration message includes a set of one or more configurations configured by base station 140-f for enabling AI-based ARQ, including one or more sets of one or more parameters. At point 825, one or more of UE 115-g, base station 140-e, or base station 140-f may complete a handover (e.g., a handover of UE 115-g from base station 140-e to base station 140-f).

[0135] Therefore, one or more of UE 115-g, base station 140-e, or base station 140-f can support the management of AI-enabled ARQ during the mobility of UE 115-g.

[0136] Figure 9 An example of an ARQ process flow 900 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 900 can be implemented as referenced. Figure 1The wireless communication system 100 is described in various aspects. Additionally or alternatively, process flow 900 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 900 may include UE 115-h and base station 140-g, which may be corresponding examples of UE 115 and base station 140 as described herein. In the following description of process flow 900, operations between UE 115-h and base station 140-g may be transmitted in a different order than the example order shown, or operations performed by UE 115-h and base station 140-g may be performed in a different order or at different times. Some operations may also be omitted from process flow 900, and other operations may be added to process flow 900.

[0137] exist Figure 9 In the example, one or more of UE 115-h or base station 140-g may support activating and deactivating one or more learning models for AI-enabled ARQ based at least in part on feedback reported by UE 115-h that is associated with one or more learning models for AI-enabled ARQ.

[0138] At 905, during procedure 903 (RRC procedure), base station 140-g may send an RRC message including a set of one or more RRC configurations, and UE 115-h may receive the RRC message. This set of one or more RRC configurations may include a set of one or more parameters. In some examples, one or more parameters in the set of one or more parameters may include one or more performance KPIs or one or more system KPIs, or a combination thereof. In some other examples, one or more parameters in the set of one or more parameters may include one or more monitoring events (e.g., thresholds, conditions). In other examples, one or more parameters in the set of one or more parameters may include one or more reporting events, reporting periodicity, etc. At 910, during procedure 903 (RRC procedure), UE 115-h may send an RRC configuration complete message, and base station 140-g may receive the RRC configuration complete message.

[0139] At 915-a, base station 140-g can transmit input data and UE 115-h can receive this input data, which may be input to one or more learning models for AI-enabled ARQ at UE 115-h. In some examples, base station 140-g can transmit input data and UE 115-h can receive this input data via one or more unicast transmissions. For example, at 915-a, 915-b, and 915-c, base station 140-g can transmit input data via one or more unicast transmissions, and UE 115-h can receive input data via one or more unicast transmissions. In some other examples, base station 140-g can broadcast input data via one or more broadcast transmissions, and UE 115-h can receive this input data, as referenced herein. Figures 3 to 8 As described. For example, at 915-a, 915-b, and 915-c, base station 140-g may transmit input data via one or more broadcast transmissions, and UE 115-h may receive input data via one or more broadcast transmissions.

[0140] At point 920, UE 115-h can monitor one or more events (e.g., threshold fulfillment, condition fulfillment) associated with one or more learning models used to enable AI ARQ. At point 925, UE 115-h can send a report based at least in part on one or more events, and base station 140-g can receive the report. For example, during reporting event 922, UE 115-h can send a report, and base station 140-g can receive the report. The report may indicate one or more performance KPIs or one or more system KPIs, or a combination thereof.

[0141] At 930-a, during a handover or deactivation event 928, one or more of UE 115-h or base station 140-g may switch between one or more learning models for AI-enabled ARQ, as described herein. For example, one or more of UE 115-h or base station 140-g may activate at least one of the one or more learning models for AI-enabled ARQ based at least in part on one or more reported performance KPIs or one or more reported system KPIs or a combination thereof. Additionally or alternatively, at 930-b, one or more of UE 115-h or base station 140-g may activate or deactivate at least one of the one or more learning models for AI-enabled ARQ based at least in part on one or more reported performance KPIs or one or more reported system KPIs or a combination thereof.

[0142] Therefore, one or more of the UE 115-h or base station 140-g can support activating and deactivating one or more learning models for enabling AI ARQ based at least in part on feedback reported by the UE 115-h that is associated with one or more learning models for enabling AI ARQ.

[0143] Figure 10 An example of an ARQ process flow 1000 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 1000 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, the process flow 1000 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 1000 may include UE 115-i and base station 140-h, which may be corresponding examples of UE 115 and base station 140 as described herein. In the following description of process flow 1000, operations between UE 115-i and base station 140-h may be transmitted in a different order than the example order shown, or operations performed by UE 115-i and base station 140-h may be performed in a different order or at different times. Some operations may be omitted from process flow 1000, and other operations may be added to process flow 1000.

[0144] exist Figure 10 In the example, one or more of the UE 115-i or base station 140-h may support activating and deactivating one or more learning models for enabling AI ARQ based at least in part on one or more learning models for enabling AI ARQ monitored by base station 140-h.

[0145] At point 1005, during procedure 1002 (RRC procedure), base station 140-h may send an RRC message including a set of one or more RRC configurations, and UE 115-i may receive the RRC message. This set of one or more RRC configurations may include a set of one or more parameters. In some examples, one or more parameters in the set of one or more parameters may include one or more performance KPIs or one or more system KPIs, or a combination thereof. At point 1010, during procedure 1002 (RRC procedure), UE 115-i may send an RRC configuration complete message, and base station 140-h may receive the RRC configuration complete message.

[0146] At 1015-a, base station 140-h can receive input data and UE 115-i can transmit this input data, which may be input to one or more learning models for AI-enabled ARQ at base station 140-h. In some examples, base station 140-h can receive input data via one or more unicast transmissions, and UE 115-i can transmit this input data. For example, at 1015-a, 1015-b, and 1015-c, base station 140-h can receive input data via one or more unicast transmissions, and UE 115-i can transmit input data via one or more unicast transmissions. At 1020, base station 140-h can monitor one or more events (e.g., threshold satisfaction, condition fulfillment) associated with one or more learning models for AI-enabled ARQ at base station 140-h.

[0147] At 1025-a, one or more of UE 115-i or base station 140-h may switch between one or more learning models for AI-enabled ARQ, at least in part, based on one or more events and during a handover or deactivation event 1022, as described herein. For example, one or more of UE 115-i or base station 140-h may activate at least one of the one or more learning models for AI-enabled ARQ, at least in part, based on one or more events as described herein. Additionally or alternatively, at 1025-b, one or more of UE 115-i or base station 140-h may deactivate at least one of the one or more learning models for AI-enabled ARQ, at least in part, based on one or more events as described herein.

[0148] Therefore, one or more of the UE 115-i or base station 140-h can support activating and deactivating one or more learning models for enabling AI ARQ based at least in part on one or more learning models for enabling AI ARQ monitored by base station 140-h.

[0149] Figure 11 An example of an AI-enabled ARQ wireless communication system 1100 according to one or more aspects of this disclosure is shown. In some examples, the wireless communication system 1100 may implement as referenced herein. Figure 1 The described aspects of the wireless communication system 100, or aspects that may be implemented therein, are also described. Additionally or alternatively, the wireless communication system 1100 may be implemented as referenced herein. Figure 2 The network architecture 200 described herein may be implemented by or comprise various aspects of the network architecture 200. For example, the wireless communication system 1100 may include a UE 115-j and a base station 140-i, which may be as referenced herein. Figure 1Examples of the described UE 115 and base station 140. The wireless communication system 1100 can support 3G, 4G, 5G or higher radio access technologies.

[0150] UE 115-j and base station 140-i may perform wireless communication (e.g., receiving, acquiring, transmitting, or outputting one or more of control information or data) via communication link 125-a, which may be as referenced herein. Figure 1 An example of the described communication link 125. In Figure 11 In the example, UE 115-j may be equipped with (e.g., configured) at least one protocol stack 1110 to support receiving, acquiring, transmitting, or outputting one or more of control information or data. The at least one protocol stack 1110 may include one or more protocol layers, which may be ordered in a layered architecture. In some examples, the at least one protocol stack 1110 may be associated with one or more of the control plane (and may be referred to as the control plane protocol stack) or the user plane (and may be referred to as the user plane protocol stack). The at least one protocol stack 1110 may include one or more of the NAS layer 1115, RRC layer 1120, PDCP layer 1125, RLC layer 1130, MAC layer 1135, or PHY layer 1140.

[0151] NAS layer 1115 may be able to, be configured to, or be operable to support mobility, authentication, and bearer management for UE 115-j served by base station 140-i. RRC layer 1120 may be able to, be configured to, or be operable to support the establishment, configuration, and maintenance of a connection between UE 115-j and base station 140-i, which supports radio bearers for user plane data. Additionally, RRC layer 1120 may be able to, be configured to, or be operable to support the establishment, configuration, and maintenance of a connection between network entity 105 or core network 130, which supports, as referenced herein... Figure 1 The described radio bearer is for user plane data. PDCP layer 1125 may be, configured, or operable to support header compression, sequential delivery, encryption and integrity protection, delivery of user plane and control plane data, and deduplication. Additionally or alternatively, PDCP layer 1125 may be, configured, or operable to support routing of split barriers.

[0152] RLC layer 1130 may be able to, be configured to, or be operable to support the delivery of upper-layer PDUs according to one or more modes, including AM, UN, and TM. RLC layer 1130 may perform error correction via ARQ, RLC SDU concatenation, segmentation and reassembly, RLC data PDU resegmentation, RLC data PDU reordering, duplication detection, RLC reconstruction, and protocol error detection and recovery. RLC layer 1130 of UE 115-j may receive RLC SDUs from and / or send RLC SDUs to higher protocol layers (e.g., PDCP layer 1125) of at least one protocol stack 1110 of UE 115-j, and send RLC PDUs to and / or receive RLC PDUs from a peer RLC entity, such as base station 140-i, via a lower layer (e.g., PHY layer 1140) of at least one protocol stack 1110 of UE 115-j.

[0153] MAC layer 1135 may be configured or operable to support priority handling and multiplexing of logical channels to transport channels. Additionally, MAC layer 1135 may be configured or operable to support error detection, error correction, or both, to support retransmission and improve link efficiency. PHY layer 1140 may be configured or operable to support mapping transport channels to physical channels. Additionally, PHY layer 1140 may be configured or operable to support decoding / decoding, modulation / demodulation, multi-antenna mapping, etc.

[0154] In some cases, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may experience excessive loss of RLCSDUs in UM, particularly when relying solely on HARQ. In other cases, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may experience increased latency in AM due to retransmissions associated with RLC SDUs and RLC data PDUs (e.g., each retransmission may be associated with a reassembly timer), resegmentation, reordering delays, etc. In some cases, this may lead to high variability in round-trip time (RTT) and excessive use of UE 115-j's memory 1145. In some other cases, this may cause UE 115-j (e.g., RLC layer 1130 including UE 115-j) to declare an RLF event because certain threshold or buffer limits, as described herein, are reached at UE 115-j (e.g., RLC layer 1130 including UE 115-j).

[0155] Additionally, in some cases, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may experience inefficient use of resources associated with monitoring a set 1165 of one or more PDUs. For example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may receive a subset of PDUs from the set 1165 of one or more PDUs during a reception time window, and may continue to attempt to receive a subset of PDUs from the set 1165 of one or more PDUs during the reception time window. In some examples, the reception time window may be defined by the parameter " Rx_Window This indicates that it can be defined by one or more RLC state variables, which include " Rx_Next "and" Rx_Next_Highest In some cases, UE115-j (e.g., RLC layer 1130 including UE115-j) may be unable to update (e.g., modify, adjust) its reception time window until all PDUs in set 1165 of one or more PDUs are received at UE115-j (e.g., RLC layer 1130 including UE115-j). Therefore, UE115-j (e.g., RLC layer 1130 including UE115-j) may continue to send reports (e.g., status reports) to base station 140-i requesting a subset of PDUs in set 1165 of one or more PDUs (e.g., each PDU in the subset of PDUs in set 1165 of one or more PDUs may be associated with a corresponding sequence number).

[0156] The report may indicate the corresponding sequence number associated with each PDU in a subset of PDUs in a set of one or more PDUs 1165. UE 115-j (e.g., RLC layer 1130 including UE 115-j) may ultimately receive a subset of PDUs during the reception time window. However, in some cases, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may not receive a subset of PDUs in a set of one or more PDUs 1165 during the reception time window, and therefore, UE 115-j (e.g., RLC layer 1130 including UE 115-j) or base station 140-i may declare an RLF event. Since a subset of PDUs in one or more PDU sets 1165 arrives at UE 115-j after its packet delay budget (PDB) (e.g., including RLC layer 1130 of UE 115-j), this may lead to inefficient use of the channel between UE 115-j and base station 140-i, which may negatively impact the receive time window (e.g., TCP window) and may result in premature RLF events.

[0157] In some cases, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may send a false acknowledgment (ACK) (also referred to as a “fake ACK”) to base station 140-i for one or more sequence numbers associated with one or more PDUs (one or more RLC SDUs and / or RLC data PDUs) in a set 1165 of one or more PDUs. In some cases, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may send a fake ACK to trigger (e.g., enable, induce, activate) a transmission time window to base station 140-i (e.g., “…”). Tx_Window The base station 140-i may change (e.g., update, modify, adjust) the transmission time window (e.g., "") when it receives a false ACK from UE 115-j (e.g., including RLC layer 1130 of UE 115-j). Tx_Window Sending time window (e.g., ""). Tx_Window The change of "" can be based at least in part on a false ACK, which may present some challenges. For example, base station 140-i may not be aware of one or more sequence numbers associated with one or more PDUs (one or more RLC SDUs and / or RLC data PDUs) discarded (e.g. abandoned) by UE 115-j (e.g., including RLC layer 1130 of UE 115-j) in a set 1165 of one or more PDUs. Additionally, no information (e.g., KPIs) is exchanged between UE 115-j (e.g., including RLC layer 1130 of UE 115-j) and base station 140-i.

[0158] exist Figure 11 In the example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can support autonomously discarding one or more PDUs (e.g., RLC SDU, RLC data PDU) from a set 1165 of one or more PDUs, and report the updated reception time window of UE 115-j to base station 140-i (e.g., " Rx_Window ") and the updated reception time window for base station 140-i based at least in part on UE 115-j (e.g., " Rx_Window To update the transmission time window of base station 140-i (e.g., " Tx_WindowThe request is made to receive a time window. For example, the reception time window may be based on the number of PDUs in the set 1165 of one or more PDUs. In other words, the duration of the reception time window may be based on the number of PDUs in the set 1165 of one or more PDUs (e.g., sequence number). For example, the reception time window may have a first duration based on the set 1165 of one or more PDUs; however, based on discarding one or more PDUs in the set 1165 of one or more PDUs (e.g., the discarded sequence number), the reception time window may have a second duration less than the first duration. Additionally or alternatively, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may support autonomous management of the reception buffer of UE 115-j. UE 115-j (e.g., RLC layer 1130 including UE 115-j) may support autonomous discarding of one or more PDUs in the set 1165 of one or more PDUs according to at least one learning model (e.g., AI / ML model). By making UE 115-j (e.g., including UE 115-j) The RLC layer 1130 of 115-j can support the autonomous discarding of one or more PDUs (e.g., RLC SDU, RLC data PDU). UE 115-j (e.g., the RLC layer 1130 including UE 115-j) can mitigate unnecessary retransmission of one or more PDUs in a set 1165 of one or more PDUs.

[0159] Additionally or alternatively, by enabling UE 115-j (e.g., RLC layer 1130 including UE 115-j) to support the autonomous discarding of one or more PDUs (e.g., RLC SDUs, RLC data PDUs) from set 1165, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can experience efficient use of resources. For example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can continue to perform wireless communication (e.g., uplink communication, downlink communication) on the channel in response to mitigating unnecessary retransmissions of one or more PDUs from set 1165. Additionally or alternatively, by enabling UE 115-j (e.g., RLC layer 1130 including UE 115-j) to support the autonomous discarding of one or more PDUs (e.g., RLC SDUs, RLC data PDUs) from set 1165, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can eliminate or reduce the occurrence of RLF events. Additionally or alternatively, by enabling UE 115-j (e.g., RLC layer 1130 including UE 115-j) to support the autonomous discarding of one or more PDUs (e.g., RLC SDUs, RLC data PDUs) from set 1165, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can maintain the size of the reception time window (e.g., TCP window) used for receiving wireless communications (e.g., packets, PDUs).

[0160] UE 115-j may be equipped with memory 1145 and processor 1155. At least one or more of the protocol stack 1110, memory 1145, or processor 1155 may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (or interfaces). Memory 1145 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1150. Processor 1155 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs)) or any combination thereof.

[0161] Processor 1155 may be configured to execute computer-readable instructions stored in memory 1145 to cause UE 115-j to perform various functions. For example, code 1150 may (e.g., based at least in part on a set of one or more configurations) include instructions that, when executed by at least one processor 1160, cause UE 115-j (e.g., one or more protocol layers of at least one protocol stack 1110) to perform the various functions (e.g., actions) described herein. The set of one or more configurations may include one or more of the following: at least one rule (e.g., a drop rule), at least one parameter associated with multiple values ​​(e.g., a range of values), a set of one or more other parameters, etc. For example, code 1150 may be associated with one or more learning models (e.g., AI / ML models). Figure 11 In the example, code 1150 may include instructions that, when executed by at least one processor 1160, cause UE 115-j (e.g., RLC layer 1130 including UE 115-j) to process one or more PDUs (RLC SDUs and / or RLC data PDUs) in a set 1165 of one or more PDUs based on one or more learning models (e.g., one or more AI / ML models) and at least one value from a plurality of values ​​(e.g., value ranges) of at least one parameter. For example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may discard (e.g., abandon) one or more portions of received or unreceived PDUs (RLC SDUs and / or RLC data PDUs) in the set 1165 of one or more PDUs. One or more learning models (e.g., one or more AI / ML models) used to enable AI ARQ can improve the efficient processing (e.g., dropping, discarding) of one or more PDUs in a set 1165 of one or more PDUs at UE 115-j (e.g., RLC layer 1130 including UE 115-j).

[0162] exist Figure 11 In the example, UE 115-j may send a report including capability information (e.g., UE capability information), and base station 140-i may receive this report. This capability information indicates whether UE 115-j supports AI / ML functionality, including one or more learning models for AI-enabled ARQ. Capability information may include one or more information elements (IEs), fields (e.g., bit fields), etc. For example, one or more IEs or fields may include identifiers for the learning models for AI-enabled ARQ supported by UE 115-j, features for the learning models for AI-enabled ARQ supported by UE 115-j, or other context for the learning models for AI-enabled ARQ supported by UE 115-j (e.g., tags, metadata, timestamps, etc.), etc.

[0163] Additionally or alternatively, UE 115-j may be configured to estimate the probability distribution of at least one quality metric (e.g., Quality of Service (QoS)) associated with a data traffic flow (e.g., one or more PDUs (RLC SDUs and / or RLC Data PDUs)) based at least in part on drop status or drop policy. Additionally or alternatively, UE 115-j may be configured to estimate the probability distribution (or average value) of at least one latency metric associated with a data traffic flow (e.g., one or more PDUs (RLC SDUs and / or RLC Data PDUs)). Additionally or alternatively, UE 115-j may be configured to determine the accuracy of one or more learning models for AI-enabled ARQ associated with a data traffic flow (e.g., one or more PDUs (RLC SDUs and / or RLC Data PDUs)).

[0164] Base station 140-i may generate, determine, or select one or more configurations from a set of one or more configurations associated with one or more learning models for enabling AI / ML functionality (including one or more learning models for enabling AI ARQ) based at least in part on capability information (e.g., UE capability information) indicating whether UE 115-j supports AI / ML functionality (including one or more learning models for enabling AI ARQ). Base station 140-i may transmit at least one configuration (e.g., RRC configuration) from the set of one or more configurations associated with at least one learning model for enabling AI ARQ, and UE 115-j may receive at least one configuration. At least one configuration may enable UE 115-j (e.g., RLC layer 1130 including UE 115-j) to process (e.g., discard, abandon) a portion of received or undelivered PDUs (i.e., unreceived PDUs) (RLC SDUs and / or RLC data PDUs) from a set 1165 of one or more PDUs via at least one learning model for enabling AI ARQ. Additionally, the set of one or more configurations may include reporting configurations for one or more of the status PDUs or one or more discarded PDUs reported by UE 115-j (e.g., periodically or non-periodically), as described herein.

[0165] At least one configuration may include a first set of one or more parameters for the ARQ process (e.g., AI-enabled ARQ). The first set of one or more parameters for AI-enabled ARQ may include at least one parameter (e.g., " max_ drop The at least one parameter can indicate that UE 115-j (e.g., RLC layer 1130 including UE 115-j) can be within a time window (also referred to as ""). DroppingWindowThe threshold number (e.g., maximum number) of PDUs discarded (e.g., abandoned) during the period. The first set of one or more parameters for enabling AI ARQ may include at least one parameter (e.g., " DroppingWindow The at least one parameter can indicate a time window in which UE 115-j (e.g., RLC layer 1130 including UE 115-j) tracks (e.g., counts) for max_drop The number of PDUs (RLC SDUs and / or RLC data PDUs). Alternatively, the first set of one or more parameters for enabling AI's ARQ may include at least one parameter (e.g., " DroppingProhibitWindow "), at least one parameter may indicate that UE 115-j (e.g., RLC layer 1130 including UE 115-j) may be within a time window (e.g., " DroppingWindow The threshold number (e.g., minimum number) of PDUs (RLCSDUs and / or RLC data PDUs) discarded (e.g., abandoned) during the period. Additionally or alternatively, one or more parameters of the first set of ARQs used to enable AI may include at least one parameter (e.g., " DroppingProhibitTimer The at least one parameter can be configured to correspond to the duration of the discarding of PDUs (RLC SDUs and / or RLC data PDUs) by UE 115-j (e.g., RLC layer 1130 including UE 115-j).

[0166] The first set of one or more parameters may include at least one parameter (e.g., " RLFThreshold The at least one parameter may indicate that UE 115-j (e.g., RLC layer 1130 including UE 115-j) or base station 140-i may be in a time window (also referred to as ""). RLFWindow The threshold number of replays performed during the period (e.g., the maximum number). The first set of one or more parameters may include at least one parameter (e.g., "..."). RLFWindow The at least one parameter can indicate a time window in which the number of PDUs (RLC SDUs and / or RLC data PDUs) that can be tracked (e.g., counted) by UE 115-j (e.g., RLC layer 1130 including UE 115-j) or base station 140-i can be determined to determine whether an RLF event is declared.

[0167] The first set of one or more parameters may include at least one parameter (e.g., " minTime-to-drop The at least one parameter can indicate a threshold time (e.g., a minimum time) before UE 115-j (e.g., RLC layer 1130 including UE 115-j) can discard (e.g., abandon) PDUs (RLC SDUs and / or RLC data PDUs). For example, the minTime-to- drop One or more HARQ procedures may be allowed to be completed at one or more of UE 115-j or base station 140-i. In some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may discard (e.g., abandon) one or more PDUs in a set 1165 with a time window (e.g., " Rx_Next ”, also known as “ Rx_Window The PDU associated with the lowest sequence number in ). In this example, minTime-to-drop It may have a recombination timer (e.g., " t-Reassembly The same start and stop conditions apply. In some examples, at least one learning model for AI-enabled ARQ (e.g., code 1150) may include (e.g., at least partially based on at least one configuration) instructions that, when executed by the at least one processor 1160, cause UE 115-j (e.g., RLC layer 1130 including UE 115-j) to select one or more PDUs from a set 1165 of one or more PDUs for discarding (e.g., abandoning). In other words, at least one learning model for AI-enabled ARQ may cause UE 115-j (e.g., RLC layer 1130 including UE 115-j) to select one or more sequence numbers associated with one or more PDUs (RLC SDUs and / or RLC data PDUs) from a set 1165 of one or more PDUs for discarding. In some examples, the order in which one or more PDUs from a set 1165 of one or more PDUs are discarded (e.g., abandoned) may be random.

[0168] In these examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can be configured with RLC state variables (e.g., " Rx_Dropping UE 115-j (e.g., RLC layer 1130 including UE 115-j) may associate the RLC state variable with one or more sequence numbers, which are associated with one or more PDUs (RLC SDUs and / or RLC data PDUs) in a set 1165 for discarding (e.g., abandoning). In some examples, the RLC state variable (e.g., " Rx_Dropping ") can be less than or equal to another RLC state variable (e.g., " Rx_Next_ Status_Trigger The other RLC state variable was triggered in a set of one or more PDUs 1165. t- ReassemblyThe value of the sequence number is the sequence number associated with the PDU (RLC SDU). In other words, the sequence number can be associated with one or more ongoing HARQ procedures. In some examples, UE 115-j associates the RLC state variable (e.g., " Rx_Dropping When assigning a sequence number to a PDU associated with a set of one or more PDUs in set 1165, therefore, minTime-to-drop A minimum duration is defined for UE 115-j (e.g., RLC layer 1130 including UE 115-j) to wait before discarding the sequence number associated with the PDU, allowing base station 140-i to retransmit via HARQ. Figure 11 In the example, base station 140-i can configure UE 115-j to either discard (e.g., abandon) the PDU with the lowest sequence number in a set of one or more PDUs 1165 or to autonomously (e.g., freely) discard (e.g., abandon) the PDUs in a set of one or more PDUs 1165 regardless of the lowest sequence number.

[0169] Additionally or alternatively, the first set of one or more parameters may include at least one parameter (e.g., " AIML_ Allowed The at least one parameter can enable or disable AI / ML functionality at UE 115-j. A first set of one or more parameters may include at least one parameter (e.g., "..."). QoSFlowAllowed The at least one parameter can indicate to UE 115-j that one or more service flows (e.g., QoS flows) can be applied to it with AI / ML functionality. The first set of one or more parameters may include at least one parameter (e.g., " maxTime-to-drop "), at least one parameter may indicate that UE 115-j may (e.g., in) discard (e.g., abandon) PDUs (RLC SDUs and / or RLC data PDUs) before UE 115-j discards (e.g., abandons) them. Rx_Next (e.g., maximum time) the threshold time (e.g., maximum time) for waiting for PDUs (RLC SDUs and / or RLC data PDUs).

[0170] In some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may be configured to select, for example, at least one value from a plurality of values ​​associated with at least one parameter in a first set of one or more parameters, based on a learning model for enabling AI-based ARQ. Each parameter in the first set of one or more parameters may be associated with a corresponding range of values. UE 115-j (e.g., RLC layer 1130 including UE 115-j) may select a value for at least one parameter in the first set of one or more parameters based on a learning model for enabling AI-based ARQ and one or more parameters in a second set of one or more parameters. UE 115-j (e.g., RLC layer 1130 including UE 115-j) may process one or more PDUs in a set 1165 of one or more PDUs based on the selected value of the learning model for enabling AI-based ARQ and for at least one parameter in the first set of one or more parameters.

[0171] UE 115-j (e.g., RLC layer 1130 including UE 115-j) can manage (e.g., maintain, update, adjust, modify) one or more RLC state variables from the set of RLC state variables. One or more RLC state variables may include... Rx_ Next , Rx_Next_Status_Trigger , Rx_Highest_Status and Rx_Next_Highest etc. Rx_Next It can store the value of the sequence number following the last PDU received in a set of one or more PDUs 1165. Rx_ Next It can be used with the receiving time window (e.g., Rx_Window The bottom edge of ) corresponds to the bottom edge of ). Rx_Next The value can be initially set to 0, and is set whenever UE 115-j (e.g., RLC layer 1130 including UE 115-j) receives one or more PDUs in a set 1165 containing a value equal to 0. Rx_Next When updating the PDU (RLC SDU) with the value of the sequence number, it is possible to update the value of the sequence number of the PDU. Rx_Next The value of . Rx_Next_Status_ Trigger A reassembly timer may be triggered in a set of one or more PDUs 1165 (e.g., " t-Reassembly The value of the serial number following the serial number of the PDU (RLC SDU). Rx_Highet_Status It can store the highest possible value of a sequence number associated with a set of one or more PDUs 1165. Rx_Next_HighestIt can store the value of the sequence number following the sequence number of the highest sequence number of the received PDU (RLC SDU) in a set of one or more PDUs 1165.

[0172] In some cases, as described herein, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may not be configured to update (e.g., adjust, change, move) the reception time window. Rx_Window (For example,[ Rx_Next , Rx_ Next_Highest In some cases, Rx_Next_Status_Trigger It may be associated with the first lost PDU in a set of one or more PDUs 1165, for example, since the last PDU state was sent (e.g., UE 115-j (e.g., RLC layer 1130 including UE 115-j) may have been in the reception time window). Rx_Window (For example,[ Rx_Next , Rx_Highest_ Status During the reception time window, one or more NACKs are indicated, and it may be waiting for the retransmission of one or more PDUs associated with one or more NACKs. In some cases, the reception time window... Rx_Window (For example,[ Rx_Next_Status_ Trigger , Rx_Next_Highest ]) can be associated with one or more PDUs in a set of one or more PDUs 1165 that are undergoing transmission (i.e., the corresponding sequence number may still be undergoing HARQ retransmission and may arrive at UE 115-j out of order (e.g., the RLC layer 1130 including UE 115-j)).

[0173] In some examples, UE 115-j may be configured with a second set of one or more parameters associated with at least one learning model for AI-enabled ARQ, and process (e.g., maintain, update, modify, adjust, track) the second set of one or more parameters associated with the at least one learning model for AI-enabled ARQ. In some examples, some parameters in a first set of one or more parameters may be part of a second set of one or more parameters. In some other examples, some parameters in a second set of one or more parameters may be part of a first set of one or more parameters. The second set of one or more parameters may include at least one parameter (e.g., " Dropping_ WindowThe parameter indicates the number of PDUs (RLC SDUs) that UE 115-j considers when counting the discarded sequence numbers associated with a set 1165 of one or more PDUs. For example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can be obtained from... Dropping_Window The length range (e.g., Dropping_Window First length Dropping_Window Select the second length, etc. Dropping_Window The length of the second set of one or more parameters. This second set may include at least one parameter (e.g., "..."). Drop_Count "), where at least one parameter indicates in Dropping Window The cumulative number of PDUs (RLC SDUs) dropped in the set 1165 of one or more PDUs. For example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can be dropped from... Drop Count Select from the range Drop Count In other words, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can be Dropping Window Select the threshold count for the PDU (RLC SDU). A second set of one or more parameters may include at least one parameter (e.g., "... Drop rate "), where at least one parameter indicates in Dropping Window The rate at which one or more PDUs in the set 1165 are discarded during the period. Therefore, Drop rate Can be at least partially based on Drop Count exist Dropping Window Quantization calculations on (i.e., Drop Count / Dropping Window A second set of one or more parameters may include at least one parameter (e.g., " Drop Prohibit Timer The parameter at least one indicates the duration that UE 115-j must wait between at least two PDU drops. For example, UE 115-j (e.g., RLC layer 1130 including UE 115-j) can be used for Dropping Window Select the rate for discarding PDUs (RLC SDUs) from the rate range.

[0174] exist Figure 11In the example, when UE 115-j discards at least one PDU in the set 1165 of one or more PDUs, UE 115-j (e.g., including RLC layer 1130 of UE 115-j) may update one or more RLC state variables in the RLC state variables. In other words, UE 115-j (e.g., including RLC layer 1130 of UE 115-j) may update the reception time window for the set 1165 of one or more PDUs (e.g., Rx (Window). For example, when UE 115-j discards the sequence number associated with at least one PDU in a set 1165 of one or more PDUs. x At that time, UE 115-j can update one or more RLC state variables from a set of one or more RLC state variables. For example, if the sequence number x equal Rx Next (For example, the tail end of the reception time window is discarded), then UE 115-j (e.g., RLC layer 1130 including UE 115-j) can Rx Next Updated to have greater than Rx Next The corresponding serial number of the first PDU (RLC SDU) associated with the serial number (i.e., the current serial number) Rx Next UE 115-j can transmit a receive time window for an update to a set 1165 for one or more PDUs (e.g., Rx The UE 115-j may receive an instruction from the base station 140-i (Window). Additionally, the UE 115-j may update one or more parameters in a first set of parameters and / or a second set of parameters, and provide the base station 140-i with an indication of the one or more updated parameters.

[0175] UE 115-j can generate a status report and send it to base station 140-i. This status report indicates information associated with one or more discarded (e.g., abandoned) PDUs in a set of one or more PDUs 1165. For example, RLC layer 1130 of UE 115-j can generate and output a status PDU 1172, which indicates information associated with one or more discarded (e.g., abandoned) PDUs in a set of one or more PDUs 1165. Status PDU 1172 may indicate one or more discarded sequence numbers associated with one or more discarded (e.g., abandoned) PDUs in a set of one or more PDUs 1165. In some examples, one or more discarded sequence numbers may be obtained from... Dropping WindowThe count begins at the beginning. In some other examples, one or more discarded sequence numbers may begin with the last reported discarded sequence number. Additionally or alternatively, status PDU 1172 may indicate one or more of the following: a count associated with one or more discarded (e.g., abandoned) PDUs in the set 1165 of one or more PDUs (e.g., "..."). Drop Count "), or the discard rate associated with one or more discarded (e.g., abandoned) PDUs in a set of one or more PDUs 1165 (e.g., " Drop Rate In some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may be configured to individually indicate the PDUs (discarded sequence numbers) and / or the count or drop rate, or a combination thereof.

[0176] Additionally or alternatively, UE 115-j may generate a control PDU 1174 (also referred to as a "discarded PDU") and send it to base station 140-i. This control PDU may include a set of one or more fields indicating information associated with one or more discarded (e.g., abandoned) PDUs in a set of one or more PDUs 1165. For example, the set of one or more fields may include one or more control fields (e.g., a data / control (D / C) field indicating whether a PDU in the set of one or more PDUs 1165 is an RLC data PDU or an RLC control PDU), one or more control PDU type (CPT) fields, one or more fields indicating the discarded sequence number associated with the discarded PDU in the set of one or more PDUs 1165, etc. Dropped SN "field, and one or more " Dropped Count The control PDU 1174 can correspond to the highest priority of the LCH channel. Alternatively, UE 115-j can indicate this to base station 140-i. Dropped Count And PDUs dropped via ACK in a set 1165 of one or more PDUs. UE 115-j (e.g., RLC layer 1130 including UE 115-j) may declare an RLF event, for example, at least in part, based on the number of dropped PDUs (dropped sequence numbers) in the set 1165 of one or more PDUs satisfying a threshold (e.g., greater than or equal to a threshold). The threshold may be configured in at least one configuration of a set of one or more configurations, or at least one learning model for AI-enabled ARQ may output a value for the threshold.

[0177] UE 115-j (e.g., RLC layer 1130 including UE 115-j) can manage reconfiguration timers (e.g., " t- ReassemblyIn some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may manage the recombination timer (e.g., ") based on at least one learning model for AI-enabled ARQ at UE 115-j (e.g., one or more parameters from a first set of one or more parameters and / or a second set of one or more parameters) at UE 115-j (e.g., RLC layer 1130 including UE 115-j) t-Reassembly UE 115-j (e.g., RLC layer 1130 including UE 115-j) may, at least in part, identify or detect a lost sequence number associated with a corresponding PDU (RLC SDU) in a set 1165 of one or more PDUs, in RX Next Highest The reassembly timer is enabled (e.g., started, activated, triggered). In some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may, at least in part, identify or detect the receive sequence number associated with the corresponding PDU (RLC SDU) in a set 1165 of one or more PDUs until... RX Next Status Trigger Up to now, in RX Next Highest Disable (e.g., stop, deactivate) the reconfiguration timer.

[0178] UE 115-j (e.g., including RLC layer 1130 of UE 115-j) can transmit status PDU 1172, and base station 140-i can receive the status PDU, and UE 115-j (e.g., including RLC layer 1130 of UE 115-j) can... RX Next Status Trigger The sequence number is updated (e.g., moved) to the first undelivered (e.g., unreceived) sequence number. In some examples, if the sequence number associated with the corresponding PDU (RLC SDU) in the set 1165 of one or more PDUs is discarded, UE115-j (e.g., RLC layer 1130 including UE115-j) can expect that the sequence number is less than RX Next Status Trigger (For example, with sufficient confidence, the sequence number has not undergone HARQ (retransmission)).

[0179] UE 115-j (e.g., RLC layer 1130 including UE 115-j) may suppress the reset of the reorganization timer. In some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may suppress the reset of the reorganization timer associated with a set 1165 of one or more PDUs based on a learning model for enabling AI-enabled ARQ. The reorganization timer may be unaffected by discarding one or more PDUs in the set 1165 of one or more PDUs, and discarding one or more PDUs in the set 1165 of one or more PDUs may not affect the status PDU 1172 report. In some other examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may, for example, at least in part, base its reset on the sequence number associated with the corresponding PDU in the set 1165 of one or more PDUs being equal to... Rx Next and / or Rx Next Status Trigger To terminate (e.g., stop) the reassembly timer. Therefore, one or more PDUs in the set 1165 of discarded PDUs may be processed as an ACK by UE 115-j (e.g., RLC layer 1130 including UE 115-j). In some examples, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may send a status PDU 1172 or a control PDU 1174 in response to a discard event (e.g., discarding one or more PDUs in the set 1165 of PDUs). Additionally or alternatively, UE 115-j (e.g., RLC layer 1130 including UE 115-j) may send the control PDU 1174 at least in part based on the absence of a polling bit received earlier from base station 140-i at UE 115-j (e.g., RLC layer 1130 including UE 115-j).

[0180] UE 115-j can be configured to activate (e.g., enable) or deactivate (e.g., disable) the learning model for AI-enabled ARQ at UE 115-j (e.g., including RLC layer 1130 of UE 115-j) according to one or more granularity levels. A first granularity level may be associated with activating or deactivating the learning model for AI-enabled ARQ at the UE level (i.e., device level). For example, UE 115-j can be configured to activate or deactivate the learning model for AI-enabled ARQ for the logical channel (LCH) associated with UE 115-j (e.g., including RLC layer 1130 of UE 115-j). A second granularity level may be associated with activating or deactivating the learning model for AI-enabled ARQ at the user plane level or control plane level. For example, UE 115-j can be configured to activate or deactivate the learning model for AI-enabled ARQ for either the user plane protocol stack or the control plane protocol stack of UE 115-j. The third granularity level can be associated with activating or deactivating the learning model for AI-enabled ARQ at the protocol layer level associated with UE 115-j. For example, UE 115-j can be configured to activate or deactivate the learning model for AI-enabled ARQ for UE 115-j's PDCP layer 1125 and / or UE 115-j's RLC layer 1130, etc. The fourth granularity level can be associated with activating or deactivating the learning model for AI-enabled ARQ at the parameter level. For example, UE 115-j can be configured to activate or deactivate the learning model for AI-enabled ARQ for a set of one or more parameters associated with UE 115-j's RLC layer 1130 (e.g., reception time window (“…”). Rx Window (e.g.,) activate or deactivate the learning model for AI-enabled ARQ. Additionally or alternatively, UE 115-j may be configured to activate or deactivate the learning model for AI-enabled ARQ for a set of one or more parameters associated with the RLC layer 1130 of UE 115-j, based at least in part on one or more received PDUs (RLC SDUs and / or RLC data PDUs), one or more HARQ events, or one or more state PDUs or combinations thereof in a set of one or more PDUs 1165.

[0181] exist Figure 11In the example, UE 115-j may generate a report 1175 associated with at least one learning model for AI-enabled ARQ and send it to base station 140-i. Report 1175 may include one or more logs associated with one or more PDUs (RLCSDUs and / or RLC data PDUs) in a set of one or more PDUs 1165, processed (e.g., dropped, discarded) according to the at least one learning model for AI-enabled ARQ. Additionally or alternatively, the one or more logs may include timing information, such as the latency (e.g., average, estimate) of processing (e.g., dropping, discarding, receiving) the set of one or more PDUs 1165 or the one or more PDUs (RLC SDUs and / or RLC data PDUs) in the set of one or more PDUs 1165. For example, one or more logs may indicate the average latency of processing (e.g., discarding, abandoning, receiving) of sequence numbers associated with one or more PDUs in a set 1165 of one or more PDUs or one or more PDUs (RLC SDUs and / or RLC data PDUs) during a PDU session (or per PDU session).

[0182] Additionally or alternatively, one or more logs may include statistics, such as the number of retransmissions of one or more PDUs (RLC SDUs and / or RLC data PDUs) in the set 1165 of one or more PDUs, for example, until a particular PDU (e.g., sequence number) is received. In some examples, the statistics may be based at least in part on one or more channel conditions (e.g., radio conditions, etc.). Additionally or alternatively, one or more logs may include quality information, such as the QoS of a PDU session based at least in part on a policy associated with processing (e.g., dropping, discarding, receiving) the set 1165 of one or more PDUs. For example, QoS may be based at least in part on a TCP window or as a receive time window (e.g., " Rx Window The trajectory between the application of one or more KPI metrics as a function of the PDU session. Additionally, quality information may indicate the impact of the processing (e.g., discarding, abandoning, receiving) of one or more PDUs by UE 115-j (e.g., PDCP layer 1125 including UE 115-j) of a set 1165 of PDUs. Additionally or alternatively, one or more logs may include KPI information, such as the average value of processed PDUs (RLC SDUs and / or RLC data PDUs) in the set 1165 of one or more PDUs used for a PDU session.

[0183] Therefore, a report 1175 including one or more logs can facilitate one or more of UE 115-j or base station 140-i obtaining information about the impact of one or more of UE 115-j or base station 140-i on wireless communication in relation to a set 1165 of processing (e.g., discarding, abandoning, receiving) one or more PDUs. For example, one or more of UE 115-j or base station 140-i can identify the impact on QoS based at least in part on the report 1175 including one or more logs. One or more of UE 115-j or base station 140-i can determine whether to discard a single PDU (sequence number) and maintain a channel for wireless communication (e.g., receiving, transmitting) for other PDUs with low latency. For example, one or more of UE 115-j or base station 140-i can analyze the QoS (e.g., discarding policy, QoS) associated with discarded PDUs via at least one learning model for AI-enabled ARQ.

[0184] UE 115-j may determine, at least in part, a reception time window (e.g., “…”) associated with UE 115-j (e.g., the RLC layer 1130 including UE 115-j) based on a report 1175 including one or more logs. Rx Window The prediction of the delay for one or more packets (e.g., a set of one or more PDUs, 1165). UE 115-j may apply HARQ information and / or bearer information, PDU information of other received PDUs (e.g., sequence numbers), etc., to predict p(T). SN, Latency |Observation window, HARQ event), and UE 115-j (e.g., RLC layer 1130 including UE 115-j) can determine if the expected delay is greater than a threshold (e.g., greater than PDB or timer (e.g., " t_Reordering If a timer is used, then one or more PDUs in the set 1165 of PDUs can be discarded.

[0185] One or more protocol layers of UE 115-j can exchange information with one or more other protocol layers of UE 115-j. For example, RLC layer 1130 of UE 115-j can exchange information with PDCP layer 1125 of UE 115-j. Figure 11In the example, RLC layer 1130 may output information to UE 115-j's PDCP layer 1125 indicating one or more PDUs (e.g., one or more sequence numbers of one or more PDUs) in a set 1165 discarded by UE 115-j's RLC layer 1130. UE 115-j's PDCP layer 1125 may map the information (e.g., one or more sequence numbers of one or more PDUs (RLC SDUs and / or RLC data PDUs)) to one or more sequence numbers at UE 115-j's PDCP layer 1125 (e.g., one or more sequence numbers associated with one or more PDCP PDUs associated with one or more PDUs (RLC SDUs and / or RLC data PDUs)). Additionally or alternatively, the PDCP layer 1125 of UE 115-j may stop (e.g., deactivate, disable) a timer, such as based at least in part on information (e.g., one or more sequence numbers of one or more PDUs) from a set 1165 indicating one or more PDUs discarded by the RLC layer 1130 of UE 115-j. t- Reordering Timer.

[0186] Additionally or alternatively, the PDCP layer 1125 of UE 115-j may use one or more dummy PDCP PDUs to manually fill one or more sequence numbers of one or more PDUs (RLC SDUs and / or RLC data PDUs). Alternatively, for example, if no other sequence numbers of one or more PDUs (RLC SDUs and / or RLC data PDUs) are lost, the PDCP layer 1125 of UE 115-j may advance (e.g., adjust, move) the reordering time window of the PDCP layer 1125 of UE 115-j (e.g., " Window Size In some examples, one or more protocol layers of UE 115-j may exchange information with one or more protocol layers of base station 140-i (e.g., as described above). For example, RLC layer 1130 may exchange information with PDCP layer of base station 140-i (e.g., as described above). Additionally or alternatively, one or more protocol layers of base station 140-i may exchange information with one or more protocol layers of UE 115-j (e.g., as described above). For example, RLC layer of base station 140-i may exchange information with PDCP layer 1125 of UE 115-j.

[0187] Therefore, the wireless communication system 1100, including one or more of UE 115-j or base station 140-i, can support the processing of PDUs (RLC SDUs and / or RLC data PDUs) according to a learning model (e.g., an AI / ML model) for enabling AI-based ARQ, and UE 115-j or base station 140-i can experience reduced latency due to the early termination of PDU (RLC SDU and / or RLC data PDU) retransmissions, etc. It should be understood that alternative techniques may be implemented to support improvements to one or more aspects of this disclosure.

[0188] Figure 12 An example of an ARQ process flow 1200 supporting AI enablement according to one or more aspects of this disclosure is shown. Process flow 1200 can be implemented as referenced. Figure 1 The wireless communication system 100 is described in various aspects. Additionally or alternatively, process flow 1200 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein may include, or be implemented by, various aspects. Process flow 1200 may include UE 115-k and base station 140-j, which may be examples of UE 115 and base station 140 as described herein. In the following description of process flow 1200, operations between UE 115-k and base station 140-j may be transmitted in a different order than the example order shown, or operations performed by UE 115-k and base station 140-j may be performed in a different order or at different times. Some operations may also be omitted from process flow 1200, and other operations may be added to process flow 1200.

[0189] At 1205, base station 140-j can send control signaling, and UE 115-k can receive this control signaling, which indicates the configuration of a first set of parameters including one or more parameters for an ARQ procedure associated with the RLC entity of UE 115-k. At least one parameter in the first set of one or more parameters may be associated with multiple values ​​(e.g., a range of values). At 1210, UE 115-k can select, at least in part, a value from the multiple values ​​for the ARQ procedure associated with the RLC entity of UE 115-k based on a second set of one or more parameters, as referenced herein. Figure 11 As described. A second set of one or more parameters may include at least one parameter (e.g., " Dropping Window The parameter indicates the number of PDUs (RLC SDUs) that UE 115-k considers when counting discarded sequence numbers associated with a set of one or more PDUs. For example, UE 115-k may be able to... Dropping Window The length range (e.g., Dropping Window First length Dropping WindowSelect the second length, etc. Dropping Window The length of the second set of one or more parameters. This second set may include at least one parameter (e.g., "..."). Drop Count "), where at least one parameter indicates in Dropping Window The cumulative number of PDUs (RLC SDUs) dropped from the set of one or more PDUs. For example, UE 115-k can be obtained from... Drop Count Select from the range Drop Count In other words, UE 115-k can target Dropping Window Select the threshold count for the PDU (RLCSDU). A second set of one or more parameters may include at least one parameter (e.g., "... Drop rate "), where at least one parameter indicates in Dropping Window The rate at which one or more PDUs in a set are dropped during the period. For example, UE 115-k can drop from a set of PDUs used for Dropping Window Select the rate for discarding PDUs (RLCSDUs) from the rate range.

[0190] At 1215, UE 115-k may send at least one NACK for at least one PDU in a set of one or more PDUs, and base station 140-j may receive the at least one NACK. At 1220, UE 115-k may discard at least one PDU based at least in part on at least one NACK and a selected value from a plurality of values ​​used for ARQ.

[0191] Figure 13 A block diagram 1300 of an AI-enabled ARQ device 1305 according to one or more aspects of this disclosure is shown. Device 1305 may be an example of aspects of network entity 105, base station 140, or UE 115 as described herein. Device 1305 may include receiver 1310, transmitter 1315, and communication manager 1320. Device 1305, or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, communication manager 1320), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0192] Receiver 1310 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, or related to AI-enabled ARQ). The information may be transmitted to other components of device 1305. Receiver 1310 may utilize a single antenna or a collection of antennas.

[0193] Transmitter 1315 may provide components for transmitting signals generated by other components of device 1305. For example, transmitter 1315 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to AI-enabled ARQ, including packets, user data, control information, or any combination thereof. In some examples, transmitter 1315 may be co-located with receiver 1310 in a transceiver module. Transmitter 1315 may utilize a single antenna or a collection of multiple antennas.

[0194] The communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be examples of components used to perform various aspects of AI-enabled ARQ as described herein. For example, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0195] In some examples, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0196] Additionally or alternatively, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as a component for performing the functions described in this disclosure).

[0197] In some examples, the communication manager 1320 may be configured to use a receiver 1310, a transmitter 1315, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0198] Communication manager 1320 may support wireless communication according to examples disclosed herein. For example, communication manager 1320 may be capable of, configured to, or operable to support components for receiving control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of device 1305, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values. Communication manager 1320 may be capable of, configured to, or operable to support components for selecting a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters. Communication manager 1320 may be capable of, configured to, or operable to support components for transmitting at least one NACK for at least one PDU from the set of one or more PDUs associated with the RLC entity of device 1305. Communication manager 1320 may be capable of, configured to, or operable to support components for discarding at least one PDU based on at least one NACK for at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0199] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 (e.g., at least one processor that controls or is otherwise coupled to receiver 1310, transmitter 1315, communication manager 1320, or a combination thereof) can support techniques for reducing processing and lowering power consumption.

[0200] Figure 14 A block diagram 1400 of an AI-enabled ARQ device 1405 is shown according to one or more aspects of this disclosure. Device 1405 may be an example of a device 1305 as described herein, or an aspect of a network entity 105, base station 140, or UE 115. Device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Device 1405 or one or more components of device 1405 (e.g., receiver 1410, transmitter 1415, communication manager 1420) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0201] Receiver 1410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with AI-enabled ARQ). The information may be transmitted to other components of device 1405. Receiver 1410 may utilize a single antenna or a collection of antennas.

[0202] Transmitter 1415 may provide components for transmitting signals generated by other components of device 1405. For example, transmitter 1415 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to AI-enabled ARQ, including packets, user data, control information, or any combination thereof. In some examples, transmitter 1415 may be co-located with receiver 1410 in a transceiver module. Transmitter 1415 may utilize a single antenna or a collection of multiple antennas.

[0203] Device 1405 or its various components may be examples of parts used to perform various aspects of AI-enabled ARQ as described herein. For example, communication manager 1420 may include configuration component 1425, parameter component 1430, feedback component 1435, protocol component 1440, or any combination thereof. Communication manager 1420 may be examples of aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to use receiver 1410, transmitter 1415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or integrate in combination with receiver 1410, transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0204] Communication manager 1420 can support wireless communication according to examples disclosed herein. Configuration component 1425 is capable of, configured to, or operable to support components for receiving control signaling indicative of a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of device 1405, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values. Parameter component 1430 is capable of, configured to, or operable to support components for selecting a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters. Feedback component 1435 is capable of, configured to, or operable to support components for transmitting at least one NACK for at least one PDU from the set of one or more PDUs associated with an RLC entity of device 1405. Protocol component 1440 is capable of, configured to, or operable to support components for discarding at least one PDU based on at least one NACK for at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0205] Figure 15 A block diagram 1500 of a communication manager 1520 supporting AI-enabled ARQ according to one or more aspects of this disclosure is shown. The communication manager 1520 may be an example of a communication manager 1320, a communication manager 1420, or aspects thereof as described herein. The communication manager 1520 or its various components may be examples of parts for performing various aspects of AI-enabled ARQ as described herein. For example, the communication manager 1520 may include a configuration component 1525, a parameter component 1530, a feedback component 1535, a protocol component 1540, a time window component 1545, a reporting component 1550, a status component 1555, an event component 1560, a timer component 1565, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0206] Communication manager 1520 can support wireless communication according to examples disclosed herein. Configuration component 1525 is capable of, configured to, or operable to support components for receiving control signaling instructing a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of a wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values. Parameter component 1530 is capable of, configured to, or operable to support components for selecting a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters. Feedback component 1535 is capable of, configured to, or operable to support components for sending at least one NACK for at least one PDU from the set of one or more PDUs associated with an RLC entity of a wireless device. Protocol component 1540 is capable of, configured to, or operable to support components for discarding at least one PDU based on at least one NACK for at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0207] In some examples, at least one PDU includes one or more of at least one RLC SDU or a portion of at least one RLC SDU. In some examples, at least one RLC SDU or a portion of at least one RLC SDU corresponds to a minimum sequence number. In some examples, to support the discarding of at least one PDU, protocol component 1540 is capable, configured, or operable to support components for discarding at least one RLC SDU or a portion of at least one RLC SDU at least in part based on the elapsed duration of a threshold time.

[0208] In some examples, parameter component 1530 is capable of, configured to, or operable to support a component for updating at least one parameter in a first set of one or more parameters based on discarding at least one RLC SDU or a portion of at least one RLC SDU and based on a sequence number associated with at least one RLC SDU. In some examples, at least one parameter is associated with a reception time window for the set of one or more PDUs.

[0209] In some examples, the time window component 1545 is capable of, configured to, or operable to support components for updating a receive time window for a set of one or more PDUs based on at least one NACK for at least one PDU and according to a selected value from a set of values ​​for an ARQ procedure associated with the RLC entity of the wireless device. In some examples, the time window component 1545 is capable of, configured to, or operable to support components for transmitting an indication to a second wireless device of the updated receive time window for the set of one or more PDUs.

[0210] In some examples, the second set of one or more parameters indicates one or more of the following: a drop time window that enables the wireless device to drop a certain number of PDUs from a set of one or more PDUs; a counter associated with tracking the number of PDUs dropped; a drop rate associated with a certain number of PDUs dropped from a set of one or more PDUs during the drop time window; or a timer that indicates a threshold duration between at least one first PDU and at least one second PDU from a set of one or more PDUs dropped.

[0211] In some examples, the reporting component 1550 is capable of, configured to, or operable to support components for transmitting status reports via an RLC entity of a wireless device, the status report including one or more NACKs of at least one NACK for at least one PDU, wherein the status report includes at least one status PDU, and wherein the at least one status PDU includes at least one field indicating a sequence number associated with the at least one PDU.

[0212] In some examples, the sequence number associated with at least one PDU corresponds to the start of a discard time window that allows the wireless device to discard a certain number of PDUs from a set of one or more PDUs. In some examples, the sequence number associated with at least one PDU begins with the last reported discarded sequence number associated with at least one second PDU.

[0213] In some examples, at least one state PDU indicates one or more of the following: a count associated with a certain number of PDUs discarded in a set of one or more PDUs during a discard time window, or a discard rate of a certain number of PDUs discarded in a set of one or more PDUs during a discard time window.

[0214] In some examples, state component 1555 is capable of, configured to, or operable to support components for generating a set of control PDUs including one or more fields. In some examples, at least one field in the set of one or more fields includes an indication of a discard event corresponding to the discarding of at least one PDU and its associated sequence number. In some examples, the control PDU includes a higher priority than other PDUs associated with the Logical Control Channel (LCH). In some examples, state component 1555 is capable of, configured to, or operable to support components for transmitting control PDUs to a second wireless device. In some examples, state component 1555 is capable of, configured to, or operable to support components for transmitting control PDUs to a second wireless device, at least partially based on the absence of a polling bit or in response to the discarding of at least one PDU.

[0215] In some examples, event component 1560 is capable of, configured to, or operable to support means for determining whether the number of dropped PDUs in a set of one or more PDUs meets a threshold. In some examples, event component 1560 is capable of, configured to, or operable to support means for declaring an RLF event based on the number of dropped PDUs in a set of one or more PDUs meeting a threshold. In some examples, event component 1560 is capable of, configured to, or operable to support means for sending an indication of an RLF event to a second wireless device.

[0216] In some examples, a first set of one or more parameters includes the inputs to the learning model used for the ARQ process. In some examples, a second set of one or more parameters includes the outputs of the learning model used for the ARQ process. In some examples, the selected values ​​for the ARQ process from a set of multiple values ​​are based on both the inputs and outputs of the learning model.

[0217] In some examples, at least one parameter in a first set of one or more parameters includes at least one threshold number of dropped PDUs, at least one PDCP state, at least one hybrid ARQ state, at least one traffic flow state, at least one radio condition, or at least one observed downlink assignment, and wherein the at least one threshold number of dropped PDUs, at least one PDCP state, at least one hybrid ARQ state, at least one traffic flow state, at least one radio condition, or at least one observed downlink assignment corresponds to the input of the learning model. In some examples, at least one threshold number of dropped PDUs, and the event component 1560 is capable, configured, or operable to support components for declaring an RLF event based on one or more of the at least one threshold number of dropped PDUs or the output of the learning model for the ARQ process. In some examples, at least one threshold number of dropped PDUs, and the event component 1560 is capable, configured, or operable to support components for sending an indication of an RLF event to a second wireless device.

[0218] In some examples, timer component 1565 is capable of, configured to, or operable to support components for suppressing the reset of a reconfiguration timer associated with a set of one or more PDUs based on the output of a learning model used for the ARQ process. In some examples, timer component 1565 is capable of, configured to, or operable to support components for terminating a reconfiguration timer associated with a set of one or more PDUs based on a sequence number associated with at least one PDU and the output of a learning model used for the ARQ process.

[0219] In some examples, state component 1555 is capable of, configured to, or operable to support components for outputting an indication to the PDCP entity of the wireless device to discard at least one PDU, wherein the indication indicates a sequence number associated with at least one PDU. In some examples, the PDCP entity of the wireless device maps the sequence number associated with at least one PDU to a corresponding PDCP sequence number. In some examples, the PDCP entity of the wireless device terminates the reordering of sequence numbers associated with a set of one or more PDUs. In some examples, the PDCP entity of the wireless device populates the sequence numbers with dummy PDUs. In some examples, the PDCP entity of the wireless device updates the reordering time window associated with a set of one or more PDUs, or a combination thereof.

[0220] In some examples, the reporting component 1550 is capable of, configured to, or operable to support components for generating reports associated with a learning model, wherein the reports include a set of one or more logs associated with the processing of one or more PDUs in a set of one or more PDUs according to the learning model. In some examples, the reporting component 1550 is capable of, configured to, or operable to support components for transmitting reports associated with the learning model to a second wireless device. In some examples, the second wireless device includes a network entity including a base station or server associated with the learning model. In some examples, at least one log in the set of one or more logs indicates a fourth set of one or more parameters corresponding to the output of the learning model, the fourth set of one or more parameters including one or more of the following: latency associated with the processing of the set of one or more PDUs; the number of retransmissions associated with the set of one or more PDUs; the quality of service (QoS) associated with the set of one or more PDUs based on a first set of one or more parameters and a second set of one or more parameters; or the quality of the PDU session based on a third set of one or more parameters.

[0221] In some examples, the reporting component 1550 is capable of, configured to, or operable to support components for sending a report to a second wireless device, the report including capability information indicating whether the wireless device supports the learning model. This capability information includes one or more bit fields, and the capability information is based on performance metrics associated with the learning model. In some examples, control signaling indicating configuration is received based on the capability information indicating whether the wireless device supports the learning model.

[0222] In some examples, the first set of one or more parameters includes one or more of the following: a first threshold number of PDUs allowed to be dropped in the set of one or more PDUs; a drop time window that enables the wireless device to drop a certain number of PDUs in the set of one or more PDUs; a first threshold duration between dropping at least one first PDU and at least one second PDU in the set of one or more PDUs; a second threshold number of PDUs allowed to be dropped in the set of one or more PDUs before declaring an RLF event; a second threshold duration for dropping sequence numbers; an indication for enabling or disabling the learning model; one or more Quality of Service (QoS) flows associated with the learning model; or a third threshold duration for dropping sequence numbers associated with the corresponding PDU.

[0223] In some examples, event component 1560 is capable of, configured to, or operable to support components for determining the number of discarded PDUs in a set of one or more PDUs, wherein each discarded PDU is associated with a corresponding sequence number. In some examples, event component 1560 is capable of, configured to, or operable to support components for sending control signaling to a second wireless device, the control signaling indicating one or more of the number of discarded PDUs and at least one second NACK associated with the number of discarded PDUs.

[0224] Figure 16 A diagram of a system 1600 including a device 1605 supporting AI-enabled ARQ is shown according to one or more aspects of this disclosure. Device 1605 may be an example of device 1305, device 1405, or network entity 105, base station 140, or UE 115 as described herein, or a component including such devices. Device 1605 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof). Device 1605 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1620, an input / output (I / O) controller (e.g., I / O controller 1610), a transceiver 1615, one or more antennas 1625, at least one memory 1630, code 1635, and at least one processor 1640. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1645).

[0225] I / O controller 1610 manages the input and output signals of device 1605. I / O controller 1610 can also manage peripheral devices not integrated into device 1605. In some cases, I / O controller 1610 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1610 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1610 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1610 may be implemented as part of one or more processors, such as at least one processor 1640. In some cases, a user may interact with the device 1605 via the I / O controller 1610 or via hardware components controlled by the I / O controller 1610.

[0226] In some cases, device 1605 may include a single antenna. However, in other cases, device 1605 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1615 may communicate bidirectionally via one or more antennas 1625 using a wired or wireless link as described herein. For example, transceiver 1615 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1615 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1625 for transmission; and demodulating packets received from one or more antennas 1625. Transceiver 1615, or transceiver 1615 and one or more antennas 1625, may be an example of transmitter 1315, transmitter 1415, receiver 1310, receiver 1410, or any combination thereof or components thereof as described herein.

[0227] At least one memory 1630 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1630 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1635. Code 1635 may include instructions that, when executed by at least one processor 1640, cause device 1605 to perform the various functions described herein. Code 1635 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1635 may not be directly executable by at least one processor 1640, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1630 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0228] At least one processor 1640 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1640 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 1640. At least one processor 1640 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1630) to cause device 1605 to perform various functions (e.g., functions or tasks that support AI-enabled ARQ). For example, device 1605 or components of device 1605 may include at least one processor 1640 and at least one memory 1630 coupled to or coupled to the at least one processor 1640, the at least one processor 1640 and the at least one memory 1630 being configured to perform the various functions described herein. In some examples, at least one processor 1640 may include multiple processors, and at least one memory 1630 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, the multiple memories being configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1640 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1640) and memory circuitry (which may include at least one memory 1630)) or components that receive or obtain input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1640 or a processing system including at least one processor 1640 may be configured, capable of being configured, or operable to cause device 1605 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 1635 (e.g., processor-executable code) stored in at least one memory 1630 or otherwise.

[0229] Communication manager 1620 may support wireless communication according to examples disclosed herein. For example, communication manager 1620 may be capable of, configured to, or operable to support components for receiving control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of device 1605, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values. Communication manager 1620 may be capable of, configured to, or operable to support components for selecting a value from the set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters. Communication manager 1620 may be capable of, configured to, or operable to support components for transmitting at least one NACK for at least one PDU from the set of one or more PDUs associated with the RLC entity of device 1605. Communication manager 1620 may be capable of, configured to, or operable to support components for discarding at least one PDU based on at least one NACK for at least one PDU and the selected value from the set of multiple values ​​for the ARQ procedure.

[0230] By including or configuring a communication manager 1620 according to an example as described herein, device 1605 can support techniques for reducing latency, reducing power consumption, extending battery life, and improving the utilization of processing power.

[0231] In some examples, the communication manager 1620 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1615, one or more antennas 1625, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported by or executed by at least one processor 1640, at least one memory 1630, code 1635, or any combination thereof. For example, code 1635 may include instructions that can be executed by at least one processor 1640 to cause the device 1605 to perform various aspects of AI-enabled ARQ as described herein, or at least one processor 1640 and at least one memory 1630 may be otherwise configured to perform or support such operations individually or jointly.

[0232] Figure 17 A flowchart illustrating a method 1700 for supporting AI-enabled ARQ according to one or more aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity, base station, or UE or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 16The described network entity 105, base station 140, or UE 115 performs the functions described. In some examples, network entity 105, base station 140, or UE 115 may execute a set of instructions to control the functional elements of network entity 105, base station 140, or UE 115 to perform the described functions. Additionally or alternatively, network entity 105, base station 140, or UE 115 may use dedicated hardware to perform aspects of the described functions.

[0233] At 1705, the method may include receiving control signaling indicating a configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of a wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a set of multiple values. Operation of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to [reference needed]. Figure 15 The configuration component 1525 described is used to execute.

[0234] At 1710, the method may include selecting values ​​from a set of multiple values ​​for the ARQ procedure based on a second set of one or more parameters. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 15 The parameter component 1530 described is used for execution.

[0235] At 1715, the method may include sending at least one NACK for at least one PDU from a set of one or more PDUs associated with the RLC entity of the wireless device. The operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference needed]. Figure 15 The described feedback component 1535 is executed.

[0236] At 1720, the method may include discarding at least one PDU based on at least one NACK for at least one PDU and a selected value from a set of multiple values ​​used for the ARQ procedure. The operation of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be derived from references... Figure 15 The described protocol component 1540 is executed.

[0237] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0238] The following provides an overview of the various aspects of this disclosure:

[0239] Aspect 1: A method for wireless communication at a wireless device, the method comprising: receiving control signaling indicating a configuration, the configuration including a first set of one or more parameters for an ARQ procedure associated with an RLC entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a plurality of values; selecting a value from the plurality of values ​​for the ARQ procedure based at least in part on a second set of one or more parameters; sending at least one NACK for at least one PDU from a set of one or more PDUs associated with the RLC entity of the wireless device; and discarding the at least one PDU based at least in part on the at least one NACK for the at least one PDU and the selected value from the plurality of values ​​for the ARQ procedure.

[0240] Aspect 2: According to the method of aspect 1, wherein the at least one PDU comprises one or more of at least one RLC SDU or a portion of the at least one RLC SDU, wherein the at least one RLC SDU or the portion of the at least one RLC SDU corresponds to a minimum sequence number, and wherein discarding the at least one PDU comprises: discarding the at least one RLC SDU or the portion of the at least one RLC SDU at least in part based on the elapsed time of a threshold.

[0241] Aspect 3: According to the method of aspect 2, the method further includes: updating at least one parameter in the first set of one or more parameters at least in part based on discarding the at least one RLC SDU or a portion of the at least one RLC SDU and at least in part based on a sequence number associated with the at least one RLCSDU, wherein the at least one parameter is associated with a reception time window for the set of one or more PDUs.

[0242] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: updating the reception time window for the set of one or more PDUs based at least in part on the at least one NACK and a selected value among the plurality of values ​​for the ARQ procedure; and sending an indication to a second wireless device of the updated reception time window for the set of one or more PDUs.

[0243] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first set of one or more parameters indicates one or more of the following: a drop time window, the drop time window enabling the wireless device to drop a certain number of PDUs in the set of one or more PDUs; a counter associated with tracking the certain number of PDUs dropped; a drop rate associated with a certain number of PDUs dropped in the set of one or more PDUs during the drop time window; or a timer indicating a threshold duration between at least one first PDU and at least one second PDU in the set of one or more PDUs dropped.

[0244] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: transmitting a status report via the RLC entity of the wireless device, the status report including one or more NACKs of the at least one NACK for the at least one PDU, wherein the status report includes at least one status PDU, and wherein the at least one status PDU includes at least one field indicating a sequence number associated with the at least one PDU.

[0245] Aspect 7: According to the method of aspect 6, wherein the sequence number associated with the at least one PDU corresponds to the start of a discard time window, the discard time window enabling the wireless device to discard a certain number of PDUs in the set of one or more PDUs, or the sequence number associated with the at least one PDU starts from the last reported discarded sequence number associated with at least one second PDU.

[0246] Aspect 8: The method according to any one of Aspects 6 to 7, wherein the at least one state PDU indicates one or more of the following: a count associated with a certain number of PDUs discarded in the set of one or more PDUs during a discard time window, or a discard rate of a certain number of PDUs discarded in the set of one or more PDUs during the discard time window.

[0247] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: generating a control PDU comprising a set of one or more fields, wherein at least one field in the set of one or more fields includes an indication of a discard event corresponding to the discard of the at least one PDU and an associated sequence number of the at least one PDU, wherein the control PDU includes a priority higher than that of other PDUs associated with the LCH; and transmitting the control PDU to a second wireless device, wherein the control PDU is transmitted to the second wireless device at least in part based on the absence of a polling bit or in response to the discard of the at least one PDU.

[0248] Aspect 10: The method according to any one of aspects 1 to 9, the method further comprising: determining whether the number of discarded PDUs in the set of one or more PDUs satisfies a threshold; declaring an RLF event based at least in part on the fact that the number of discarded PDUs in the set of one or more PDUs satisfies the threshold; and sending an indication of the RLF event to a second wireless device.

[0249] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the first set of one or more parameters includes inputs to a learning model for the ARQ process, wherein the second set of one or more parameters includes outputs to the learning model for the ARQ process, and wherein the selected value among the plurality of values ​​for the ARQ process is at least partially based on the inputs to the learning model and the outputs of the learning model.

[0250] Aspect 12: The method according to aspect 11, wherein at least one parameter in the first set of one or more parameters includes at least one threshold number of dropped PDUs, at least one PDCP state, at least one HARQ state, at least one traffic flow state, at least one radio condition, or at least one observed downlink assignment, and wherein the at least one threshold number of dropped PDUs, the at least one PDCP state, the at least one HARQ state, the at least one traffic flow state, the at least one radio condition, or the at least one observed downlink assignment corresponds to the input of the learning model, the method further comprising: declaring an RLF event at least in part based on one or more of the at least one threshold number of dropped PDUs or the output of the learning model for the ARQ process; and sending an indication of the RLF event to a second wireless device.

[0251] Aspect 13: The method according to any one of Aspects 11 to 12, the method further comprising: suppressing the reset of a recombination timer associated with the set of one or more PDUs based on the output of the learning model for the ARQ process; or terminating the recombination timer associated with the set of one or more PDUs based at least in part on a sequence number associated with the at least one PDU and based on the output of the learning model for the ARQ process.

[0252] Aspect 14: The method according to any one of Aspects 11 to 13, the method further comprising: outputting an indication to a PDCP entity of the wireless device to discard the at least one PDU, wherein the indication indicates a sequence number associated with the at least one PDU, wherein the PDCP entity of the wireless device maps the sequence number associated with the at least one PDU to a corresponding PDCP sequence number, terminating the reordering of sequence numbers associated with the set of one or more PDUs, filling the sequence number with a dummy PDU, or updating a reordering time window associated with the set of one or more PDUs, or a combination thereof.

[0253] Aspect 15: The method according to any one of Aspects 11 to 14, the method further comprising: generating a report associated with the learning model, wherein the report includes a set of one or more logs associated with processing of one or more PDUs in the set of one or more PDUs according to the learning model; and sending the report associated with the learning model to a second wireless device, wherein the second wireless device includes a network entity including a base station or server associated with the learning model, wherein at least one log in the set of one or more logs indicates a fourth set of one or more parameters corresponding to the output of the learning model, the fourth set of one or more parameters including one or more of the following: latency associated with processing of the set of one or more PDUs; the number of retransmissions associated with the set of one or more PDUs; QoS associated with the set of one or more PDUs based at least in part on the first set of one or more parameters and the second set of one or more parameters; or the quality of a PDU session based at least in part on the third set of one or more parameters.

[0254] Aspect 16: The method according to any one of Aspects 11 to 15, the method further comprising: sending a report to a second wireless device, the report including capability information indicating whether the wireless device supports the learning model, the capability information including one or more bit fields, and wherein the capability information is based at least in part on a performance metric associated with the learning model, wherein the control signaling indicating the configuration is received at least in part based on the capability information indicating whether the wireless device supports the learning model.

[0255] Aspect 17: The method according to any one of Aspects 11 to 16, wherein the first set of one or more parameters includes one or more of the following: a first threshold number of PDUs allowed to be dropped in the set of one or more PDUs, a drop time window that enables the wireless device to drop a certain number of PDUs in the set of one or more PDUs, a first threshold duration between dropping at least one first PDU and at least one second PDU in the set of one or more PDUs, a second threshold number of PDUs allowed to be dropped before declaring an RLF event in the set of one or more PDUs, a second threshold duration for dropping sequence numbers, an indication for enabling or disabling the learning model, one or more QoS flows associated with the learning model, or a third threshold duration for dropping sequence numbers associated with the corresponding PDU.

[0256] Aspect 18: The method according to any one of aspects 1 to 17, the method further comprising: determining a number of discarded PDUs in the set of one or more PDUs, wherein each discarded PDU is associated with a corresponding sequence number; and sending control signaling to a second wireless device, the control signaling indicating one or more of the number of discarded PDUs and at least one second NACK associated with the number of discarded PDUs.

[0257] Aspect 19: A wireless device for wireless communication, the wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the wireless device to perform a method according to any one of Aspects 1 to 18.

[0258] Aspect 20: A wireless device for wireless communication, the wireless device comprising at least one component for performing the method according to any one of aspects 1 to 18.

[0259] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 18.

[0260] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0261] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0262] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0263] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0264] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0265] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0266] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0267] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0268] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0269] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0270] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless device, the wireless device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the wireless device: Receive control signaling indicating a configuration, the configuration including a first set of one or more parameters for an automatic repeat request procedure associated with the radio link control entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a plurality of values; The value for the automatic repeating request process is selected from the plurality of values ​​based at least in part on a second set of one or more parameters; Send at least one negative acknowledgment for at least one protocol data unit in a set of one or more protocol data units associated with the radio link control entity of the wireless device; and The at least one protocol data unit is discarded at least in part based on at least one negative acknowledgment for the at least one protocol data unit and a selected value among the plurality of values ​​used in the automatic repeat request process.

2. The wireless device of claim 1, wherein the at least one protocol data unit comprises one or more of at least one radio link control service data unit or a portion of the at least one radio link control service data unit, wherein the at least one radio link control service data unit or the portion of the at least one radio link control service data unit corresponds to a minimum sequence number, and wherein, in order to discard the at least one protocol data unit, the one or more processors are capable of operating individually or jointly to execute the code to cause the wireless device to: The at least one radio link control service data unit or a portion thereof is discarded, at least in part, based on the elapsed duration of a threshold.

3. The wireless device of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: At least one parameter in the first set of parameters is updated at least partially based on discarding the at least one Radio Link Control Service Data Unit or a portion thereof, and at least partially based on the sequence number associated with the at least one Radio Link Control Service Data Unit. The at least one parameter is associated with a reception time window for the set of one or more protocol data units.

4. The wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: The reception time window for the set of one or more protocol data units is updated at least in part based on the at least one negative acknowledgment and a selected value from the plurality of values ​​used in the automatic repeat request process; and Send an indication to a second wireless device of an updated receive time window for the set of one or more protocol data units.

5. The wireless device of claim 1, wherein the second set of one or more parameters indicates one or more of the following: A discard time window that enables the wireless device to discard a certain number of protocol data units from the set of one or more protocol data units; A counter, which is associated with tracking a certain number of protocol data units that have been discarded; Drop rate, which is associated with a certain number of protocol data units dropped in the set of one or more protocol data units during the drop time window; or A timer that indicates a threshold duration between at least one first protocol data unit and at least one second protocol data unit in the set of one or more protocol data units to be discarded.

6. The wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: A status report is transmitted via the radio link control entity of the wireless device. The status report includes one or more negative acknowledgments among the at least one negative acknowledgment for the at least one protocol data unit. The status report includes at least one status protocol data unit, and the at least one status protocol data unit includes at least one field indicating a sequence number associated with the at least one protocol data unit.

7. The wireless device of claim 6, wherein the sequence number associated with the at least one protocol data unit corresponds to the start of a discard time window, the discard time window enabling the wireless device to discard a certain number of protocol data units in the set of one or more protocol data units, or wherein the sequence number associated with the at least one protocol data unit begins from the last reported discarded sequence number associated with at least one second protocol data unit.

8. The wireless device of claim 6, wherein the at least one state protocol data unit indicates a count associated with a certain number of protocol data units dropped in the set of one or more protocol data units during a drop time window, or a drop rate of a certain number of protocol data units dropped in the set of one or more protocol data units during the drop time window.

9. The wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: Generate a control protocol data unit comprising a set of one or more fields, wherein at least one field in the set of one or more fields includes an indication of a discard event corresponding to the discard of the at least one protocol data unit and an associated sequence number of the at least one protocol data unit, wherein the control protocol data unit includes a priority higher than that of other protocol data units associated with a logical control channel; and The control protocol data unit is sent to the second wireless device at least in part based on the absence of a polling bit or in response to discarding the at least one protocol data unit.

10. The wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: Determine whether the number of dropped protocol data units in the set of one or more protocol data units meets a threshold; A radio link failure event is declared at least in part based on the number of dropped protocol data units in the set of one or more protocol data units satisfying the threshold. as well as Send an indication of the radio link failure event to the second wireless device.

11. The wireless device of claim 1, wherein the first set of one or more parameters includes inputs to a learning model for the automatic repeat request process, and wherein the second set of one or more parameters includes outputs to the learning model for the automatic repeat request process, and The selected value among the plurality of values ​​used in the automatic repeat request process is at least partially based on the input of the learning model and the output of the learning model.

12. The wireless device of claim 11, wherein at least one parameter in the first set of one or more parameters includes at least one threshold number of dropped protocol data units, at least one packet convergence protocol state, at least one hybrid automatic repeat request state, at least one traffic flow state, at least one radio condition, or at least one observed downlink assignment, and wherein the at least one threshold number of dropped protocol data units, the at least one packet convergence protocol state, the at least one hybrid automatic repeat request state, the at least one traffic flow state, the at least one radio condition, or the at least one observed downlink assignment corresponds to the input of the learning model, and wherein the one or more processors are further capable of operating individually or jointly to execute the code to enable the wireless device to: A radio link failure event is declared at least in part based on one or more of the at least one threshold number of discarded protocol data units or the output of the learning model used for the automatic repeat request process; and Send an indication of the radio link failure event to the second wireless device.

13. The wireless device of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: Based on the output of the learning model used in the automatic repeat request process, suppress the resetting of the recombination timer associated with the set of one or more protocol data units; or The recombination timer is terminated at least in part based on the sequence number associated with the at least one protocol data unit and the output of the learning model used for the automatic repeat request process.

14. The wireless device of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: The packet data convergence protocol entity of the wireless device outputs an indication to discard the at least one protocol data unit, wherein the indication indicates a sequence number associated with the at least one protocol data unit. The packet data convergence protocol entity of the wireless device maps the sequence number associated with the at least one protocol data unit to a corresponding packet data convergence protocol sequence number, terminates the reordering of the sequence numbers associated with the set of one or more protocol data units, populates the sequence numbers with dummy protocol data units, or updates the reordering time window associated with the set of one or more protocol data units, or a combination thereof.

15. The wireless device of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: Generate a report associated with the learning model, wherein the report includes a set of one or more logs associated with the processing of one or more protocol data units in the set of one or more protocol data units according to the learning model; as well as The report associated with the learning model is sent to a second wireless device, wherein the second wireless device includes a network entity, the network entity including a base station or server associated with the learning model. At least one log from the set of one or more logs indicates a fourth set of one or more parameters corresponding to the output of the learning model, wherein the fourth set of one or more parameters includes one or more of the following: The latency associated with the processing of the set of one or more protocol data units; The number of retransmissions associated with the set of one or more protocol data units; The Quality of Service (QoS) associated with the set of one or more protocol data units, at least in part based on the first set of one or more parameters and the second set of one or more parameters; or The quality of a protocol data unit session is based at least in part on a third set of parameters.

16. The wireless device of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: A report is sent to a second wireless device, the report including capability information indicating whether the wireless device supports the learning model, the capability information including one or more bit fields, and wherein the capability information is at least partially based on performance metrics associated with the learning model. The control signaling indicating the configuration is received at least in part based on the capability information indicating whether the wireless device supports the learning model.

17. The wireless device of claim 11, wherein the first set of one or more parameters comprises one or more of the following: a first threshold number of protocol data units allowed to be dropped in the set of one or more protocol data units; a drop time window enabling the wireless device to drop a certain number of protocol data units in the set of one or more protocol data units; a first threshold duration between dropping at least one first protocol data unit and at least one second protocol data unit in the set of one or more protocol data units; a second threshold number of protocol data units allowed to be dropped in the set of one or more protocol data units before declaring a radio link failure event; a second threshold duration for dropping sequence numbers; an indication for enabling or disabling the learning model; one or more quality of service (QoS) streams associated with the learning model; or a third threshold duration for dropping sequence numbers associated with corresponding protocol data units.

18. The wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the wireless device to: Determine the number of discarded protocol data units in the set of one or more protocol data units, wherein each discarded protocol data unit is associated with a corresponding sequence number; and A control signaling is sent to a second wireless device, the control signaling indicating one or more of the number of protocol data units dropped and at least one second negative acknowledgment associated with the number of dropped protocol data units.

19. A method for performing wireless communication at a wireless device, the method comprising: Receive control signaling indicating a configuration, the configuration including a first set of one or more parameters for an automatic repeat request procedure associated with the radio link control entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a plurality of values; The value for the automatic repeating request process is selected from the plurality of values ​​based at least in part on a second set of one or more parameters; Send at least one negative acknowledgment for at least one protocol data unit in a set of one or more protocol data units associated with the radio link control entity of the wireless device; as well as The at least one protocol data unit is discarded at least in part based on at least one negative acknowledgment for the at least one protocol data unit and a selected value among the plurality of values ​​used in the automatic repeat request process.

20. A wireless device for wireless communication, the wireless device comprising: Components for receiving control signaling indicating a configuration, the configuration including a first set of one or more parameters for an automatic repeat request procedure associated with the radio link control entity of the wireless device, wherein at least one parameter in the first set of one or more parameters is associated with a plurality of values; A component for selecting a value from the plurality of values ​​for the automatic repeating request process based at least in part on a second set of one or more parameters; A component for transmitting at least one negative acknowledgment for at least one protocol data unit in a set of one or more protocol data units associated with the radio link control entity of the wireless device; and A component for discarding the at least one protocol data unit based at least in part on at least one negative acknowledgment for the at least one protocol data unit and a selected value from the plurality of values ​​used in the automatic repeat request process.

Images