User equipment modification to configuration grant retransmission timer
By modifying the configuration of the grant retransmission timer, the user equipment (UE) resolves the issue of not being able to meet high priority and low data transmission latency bounds, reduces uplink latency, and supports time-sensitive operations.
Patent Information
- Application Number
- CN202480014827.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-02
- Filing Date
- 2024-02-26
- Publication Date
- 2025-10-03
AI Technical Summary
The existing configuration grant retransmission timer configuration results in the user equipment (UE) being unable to meet high priority levels and low data transmission delay bounds, impacting time-sensitive operations.
The user equipment (UE) autonomously selects or negotiates with the network node to modify the configuration of the grant retransmission timer to reduce the uplink data transmission delay and meet the data transmission delay limit.
By modifying the configuration of the grant retransmission timer, the UE can reduce uplink data transmission delay, meet data transmission delay bounds, and support time-sensitive operations.
Smart Images

Figure CN120752872A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. non-provisional patent application No. 18 / 177,401, filed on March 2, 2023, entitled “USER EQUIPMENT MODIFICATION TO A CONFIGURED GRANT RETRANSMISSION TIMER,” which is hereby expressly incorporated herein by reference. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for modifying user equipment (UE) configuration grant retransmission timers. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention
[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE. The method may include determining a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget. The method may include sending a second indication of the modification.
[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE. The method may include receiving a second indication of a modification to the configuration for the configuration grant retransmission timer.
[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to cause the UE to receive a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE. The one or more processors may be configured to cause the UE to determine a modification to a configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget. The one or more processors may be configured to cause the UE to send a second indication of the modification.
[0010] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to cause the network node to send a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE. The one or more processors may be configured to cause the network node to receive a second indication of a modification to the configuration for the configuration grant retransmission timer.
[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to determine a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to send a second indication of the modification.
[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to receive a second indication of a modification to the configuration for the configuration grant retransmission timer.
[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE. The apparatus may include means for determining a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget. The apparatus may include means for sending a second indication of the modification.
[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE. The apparatus may also include means for receiving a second indication of a modification to the configuration for the configuration grant retransmission timer.
[0015] The various aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description.
[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.
[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order that the above-mentioned features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.
[0021] Figure 3 is a diagram illustrating an example of uplink configuration grant (CG) communication according to the present disclosure.
[0022] Figure 4 is a diagram illustrating an example of configuring a grant timer and configuring a grant retransmission timer according to the present disclosure.
[0023] Figure 5 is a diagram illustrating an example of a wireless communication procedure between a UE and a network node according to the present disclosure.
[0024] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.
[0025] Figure 7 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.
[0026] Figure 8 is a diagram of an example apparatus for wireless communications according to the present disclosure.
[0027] Figure 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0028] Some operations at a user equipment (UE) may be sensitive to and / or susceptible to longer data transmission delays. For illustration, uplink data transmission associated with a quality of service (QoS) flow may be configured with a high priority level and / or a low data transmission delay bound. A configuration grant (CG) may include a CG timer and / or a CG retransmission timer that causes the UE to fail to meet the high priority level and / or the low data transmission delay bound, thereby causing the UE to fail to support time-sensitive operations. For example, the CG timer and / or the CG retransmission timer may prevent the UE from continuously transmitting multiple different data packets based at least in part on the UE waiting for a retransmission process to complete.
[0029] Some techniques and apparatus described herein provide for UE modification of a configuration grant retransmission timer. In some aspects, a UE (e.g., UE 120) may autonomously select modification and / or reconfiguration of a CG retransmission timer associated with a CG assigned to the UE. The UE may select modification and / or reconfiguration based at least in part on a determination that a current configuration of CG retransmissions will cause the UE to fail to meet a data transmission latency bound. At times, the UE may communicate with a network node regarding modifications to the network node and / or one or more occasions for using the CG and modifications to the CG retransmission timer.
[0030] By sending a modification to the CG retransmission timer, the UE can mitigate uplink transmission delays that exceed a data transmission delay bound for operations that may be time-sensitive. For purposes of illustration, the modification can include shortening the periodicity of the CG retransmission timer and / or terminating the CG retransmission timer. As described below, modifying the CG retransmission timer can enable the UE to reduce uplink data transmission delays, meet data transmission delay bounds, and / or support time-sensitive operations.
[0031] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.
[0032] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0033] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.
[0034] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
[0035] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.
[0036] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).
[0037] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.
[0038] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communications between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.
[0039] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0040] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.
[0041] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.
[0042] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0043] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.
[0045] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency band falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.
[0047] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0048] In some aspects, a UE (e.g., UE 120) may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE; determine a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget; and send a second indication of the modification. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.
[0049] In some aspects, a network node (e.g., network node 110) may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may send a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE; and receive a second indication of a modification to the configuration for the configuration grant retransmission timer. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.
[0050] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.
[0051] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.
[0052] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).
[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.
[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.
[0055] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0056] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 4 to 9 ) any aspects of any of the methods described.
[0057] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 4 to 9 ) any aspects of any method described in the method.
[0058] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the UE 120 may perform one or more techniques associated with UE modification of the CG retransmission timer, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 6 The process of 600 Figure 7 700 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0059] In some aspects, a UE (e.g., UE 120) includes means for receiving a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE; means for determining a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget; and / or means for sending a second indication of the modification. Means for the UE to perform the operations described herein may include, for example, one or more of: the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.
[0060] In some aspects, a network node (e.g., network node 110) includes: means for sending a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE; and / or means for receiving a second indication of a modification to the configuration for the configuration grant retransmission timer. Means for the network node to perform the operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.
[0061] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0062] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.
[0063] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment may be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality may be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. A “network entity” or a “network node” may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).
[0064] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.
[0065] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
[0066] Figure 3 is a diagram illustrating an example 300 of uplink CG communication according to the present disclosure. CG communication may include periodic uplink communications configured for a UE so that a network node does not need to transmit separate downlink control information (DCI) to schedule each uplink communication, thereby saving signaling overhead.
[0067] As shown in example 300, the UE may be configured with a CG configuration for CG communication. For example, the UE may receive the CG configuration via a radio resource control (RRC) message sent by a network node. The CG configuration may indicate resource allocations associated with the CG uplink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, such that scheduled CG opportunities 305 for the UE occur periodically. In some examples, the CG configuration may identify a resource pool or multiple resource pools available to the UE for uplink transmission. The CG configuration may configure contention-free CG communication (e.g., where resources are dedicated to the UE for transmitting uplink communications) or contention-based CG communication (e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).
[0068] In a Type 1 CG, the network node may implicitly indicate CG activation and / or CG deactivation to the UE using RRC signaling, such as by sending an indication of the CG configuration. In a Type 2 CG, in addition to sending the CG configuration, the network node may also send signaling for activating and / or deactivating the use of the CG. For example, for a Type 2 CG and as Figure 3 As shown, the network node may send a CG activation DCI to the UE to activate the CG configuration for the UE. The network node may indicate communication parameters, such as MCS, resource block (RB) allocation and / or antenna port, in the CG activation DCI for CG physical uplink shared channel (PUSCH) communication to be sent in the scheduled CG opportunity 305. The UE may start transmitting in the CG opportunity 305 based at least in part on receiving the CG activation DCI. For example, starting from the next scheduled CG opportunity 305 after receiving the CG activation DCI, the UE may send PUSCH communication in the scheduled CG opportunity 305 using the communication parameters indicated in the CG activation DCI. The UE may avoid transmitting in the configured CG opportunity 305 before receiving the CG activation DCI.
[0069] Alternatively or additionally, the network node may send a CG reactivation DCI to the UE to change the communication parameters used for CG PUSCH communication. Based at least in part on receiving the CG reactivation DCI, the UE may begin using the communication parameters indicated in the CG reactivation DCI to transmit in scheduled CG opportunities 305. For example, starting with the next scheduled CG opportunity 305 after receiving the CG reactivation DCI, the UE may transmit PUSCH communication in scheduled CG opportunities 305 based at least in part on the communication parameters indicated in the CG reactivation DCI.
[0070] In some cases, such as when the network node needs to override scheduled CG communications for higher priority communications, the network node may send a CG elimination DCI to the UE to temporarily eliminate or deactivate one or more subsequent CG opportunities 305 for the UE. The CG elimination DCI may deactivate only one subsequent CG opportunity 305 or the subsequent N CG opportunities 305 (where N is an integer). The CG opportunities 305 following the one or more (e.g., N) CG opportunities 305 following the CG elimination DCI may remain activated. Based at least in part on receiving the CG elimination DCI, the UE may avoid transmitting in one or more (e.g., N) CG opportunities 305 following the receipt of the CG elimination DCI. As shown in example 300, the CG elimination DCI eliminates one subsequent CG opportunity 305 for the UE. After the CG opportunity 305 (or N CG opportunities) following the receipt of the CG elimination DCI, the UE may automatically resume transmitting in the scheduled CG opportunity 305.
[0071] The network node may send a CG release DCI to the UE to deactivate the CG configuration for the UE. The UE may stop transmitting in the scheduled CG occasions 305 based at least in part on receiving the CG release DCI. For example, the UE may avoid transmitting in any scheduled CG occasions 305 until another CG activation DCI is received from the network node. However, the CG elimination DCI may deactivate only one subsequent CG occasion 305 or the subsequent N CG occasions 305, and the CG release DCI deactivates all subsequent CG occasions 305 for a given CG configuration of the UE until the given CG configuration is reactivated by a new CG activation DCI.
[0072] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.
[0073] Figure 4 is a diagram illustrating an example 400 of a CG timer and a CG retransmission timer according to the present disclosure.
[0074] "Hybrid Automatic Repeat Request (HARQ)" may refer to a protocol in which a receiving device that detects errors and / or corruption in a message (e.g., bit errors that meet an error threshold) may implicitly or explicitly attempt to correct the errors and / or request retransmission of the message. For example, a receiving device may send a HARQ acknowledgement (ACK) to indicate that a message was received with an acceptable number of errors, and a HARQ negative acknowledgement (NACK) to indicate that a message was not successfully received. If the sending device does not receive a HARQ ACK and / or receives a HARQ NACK before a timer expires, the sending device may retransmit the message. Thus, a HARQ process may be a process of transmitting, receiving, and / or retransmitting data packets based at least in part on a HARQ protocol.
[0075] For about Figure 3 In the described CG uplink transmission, the UE (e.g., UE 120) may perform retransmissions based at least in part on a CG timer and / or a CG retransmission timer. In some aspects, the UE may use the CG timer to monitor and / or regulate the transmission (and reception) of data packets. For example, the CG timer may prevent the UE from updating the HARQ buffer with a new outgoing data packet until the current data packet has been successfully received or the CG timer has expired. Alternatively or additionally, the CG timer may limit the number of retransmissions that may be performed for a data packet. The UE may use the CG retransmission timer to monitor and / or regulate when retransmissions of data packets may be performed.
[0076] In some aspects, a CG timer and a CG retransmission timer are maintained according to the HARQ process (e.g., for the same HARQ process). With respect to the CG timer, the UE may not stop and / or terminate the CG timer after receiving a HARQ NACK, but may stop the CG timer after receiving a HARQ ACK. With respect to the CG retransmission timer, the UE may refrain from autonomously retransmitting data packets on CG resources while the associated CG retransmission timer is running and / or has not expired. That is, autonomous retransmission may be prohibited for the duration of the CG retransmission timer. After the CG timer expires, the UE may stop and / or terminate the CG retransmission timer.
[0077] The duration of the CG timer may be configured according to a configuration grant configuration. Alternatively or additionally, the duration of the CG retransmission timer may be configured according to a CG configuration. For illustration, the network node may indicate a first value for the CG timer duration and / or a second value for the CG retransmission timer in the CG configuration information. In some aspects, the second value and / or the second duration of the CG retransmission timer may be shorter than the first value and / or the first duration associated with the CG timer, and / or may be based at least in part on an integer multiple of a periodicity M, such as M, 2M, 3M, up to XM (where X is an integer).
[0078] Example 400 includes a data transmission timeline 402, a CG timer timeline 404, and a CG retransmission timer timeline 406. For each timeline, the horizontal axis represents time. Data transmission timeline 402 may be associated with data transmission and / or data retransmission by a UE, CG timer timeline 404 may be associated with a CG timer at the UE, and CG retransmission timer timeline 406 may be associated with one or more CG retransmission timers at the UE.
[0079] like Figure 4As shown, at time t0, the UE may send a data packet 408 (shown in solid white) to a receiving device (eg, to a network node via an uplink or to another UE via a sidelink). For illustration, the UE may use a method such as that described with respect to FIG. Figure 3 4. The UE may also transmit the data packet 408 using the air interface resources of the first CG uplink opportunity described above. As indicated by reference numeral 410, the UE may also start a UE timer at time t0. The CG timer may be configured to expire after a first duration 412. Thus, until the CG timer expires or a HARQ ACK is received, the UE may prevent the HARQ buffer from being overwritten by new data and / or may avoid transmitting a second, different data packet. Alternatively or additionally, and as indicated by reference numeral 414, the UE may start a first CG retransmission timer having a second duration 416.
[0080] At time t1, the first CG retransmission timer may expire. Based at least in part on the expiration of the first CG retransmission timer, the UE may identify and / or determine that the receiving device received the data packet 408 with an error and / or that the receiving device failed to receive the data packet 408. As an example, the UE may determine that the receiving device failed to receive the data packet 408 based at least in part on the expiration of the first CG retransmission timer and the failure to receive a HARQ ACK or a HARQ NACK. As another example, the UE may receive a HARQ NACK while the first CG retransmission timer is running and / or has not expired.
[0081] Prior to the expiration of the CG timer, the UE may send a first retransmission 418 (shown with a cross pattern) of data packet 408 at time t2. That is, the first retransmission 418 may include the same data packet as data packet 408, and the UE may use air interface resources associated with the second CG uplink opportunity to send the first retransmission 418. Alternatively or additionally, and as indicated by reference numeral 420, the UE may initiate and / or start a second CG retransmission timer configured to expire after the second duration 416. At time t3, the second CG retransmission timer may expire, and the UE may identify and / or determine that the receiving device received the first retransmission 418 with an error and / or failed to receive the first retransmission 418. Therefore, and based at least in part on the CG timer continuing and / or not expiring, the UE may send a second retransmission 422 at time t4. As indicated by reference numeral 424, the UE may also initiate and / or start a third CG retransmission timer at time t4. At time t5, the CG timer expires, and based at least in part on the expiration of the CG timer, the UE may terminate the third CG retransmission timer as described above. Thus, the UE may avoid transmitting any additional retransmissions based at least in part on data packet 408 .
[0082] Varying factors may contribute to the uplink data transmission latency experienced by the UE. As an example, a protocol stack at the UE may include a packet data convergence layer (PDCP) to receive and prepare user data for transmission. The PDCP layer may include an uplink PDCP queue for storing one or more data packets waiting to be transmitted by the UE. Sometimes, an uplink PDCP queue may introduce a waiting time that the UE experiences and / or observes as part of the uplink data transmission latency. For illustration, an uplink PDCP queue may store one or more data packets and / or delay the transmission of a data packet while the UE waits for a HARQ ACK, expiration of a CG timer, and / or expiration of a CG retransmission timer.
[0083] In some aspects, operations at the UE may be sensitive to and / or susceptible to longer data transmission delays. For illustration, uplink data transmission may be associated with a QoS flow configured with a high priority level and / or low data transmission delay bound that the uplink data transmission delay experienced by the UE fails to meet. Some non-limiting examples may include QoS flows associated with extended reality (XR), video and / or audio calls, ultra-reliable low latency communications (URLLC), autonomous driving, remote control of non-terrestrial equipment, and / or navigation. Although the CG retransmission timer may be configured based at least in part on a multiple of the periodicity, the network node that configures the duration of the CG retransmission timer may not be aware of the increased latency at the UE and may select a duration for the CG retransmission timer that results in the UE failing to meet the high priority level and / or low data transmission delay metric for the QoS flow (and / or other operations). The UE may be unable to modify the CG retransmission timer configured by the network node and mitigate the uplink data transmission delay, which also results in the UE failing to meet the specified high priority level and / or low data transmission delay metric.
[0084] Some techniques and apparatus described herein provide for UE modifications to a configuration grant retransmission timer. In some aspects, a UE (e.g., UE 120) may receive a first indication of a configuration for a CG retransmission timer associated with a CG assigned to the UE. The UE may determine, based at least in part on a remaining uplink delay budget, a modification to the configuration for the CG retransmission timer, such as a first modification to terminate the CG retransmission timer and / or a second modification to shorten the duration of the CG retransmission timer. As a non-limiting example, the UE may receive an update to at least a QoS configuration (e.g., a priority level, a delay limit, an error rate, and / or a bit rate) associated with a QoS flow, such as by receiving an indication of a 5G QoS identifier (5QI) value. Based at least in part on determining the modification, the UE may send (e.g., to a network node) a second indication of the modification.
[0085] By sending a modification to the CG retransmission timer, the UE can mitigate uplink transmission delays that exceed a data transmission delay bound for operations that may be time-sensitive. For illustration, shortening the periodicity of the CG retransmission timer and / or terminating the CG retransmission timer can also cause the UE to shorten the duration of the CG timer and / or send a second different data packet instead of the first data packet. That is, the UE can reduce the uplink data transmission delay associated with the second different data packet. Therefore, mitigating the uplink transmission delay can enable the UE to meet the data transmission delay bound and support time-sensitive operations.
[0086] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.
[0087] Figure 5 is a diagram illustrating an example 500 of a wireless communication procedure between a UE (eg, UE 120 ) and a network node (eg, network node 110 ) according to the present disclosure.
[0088] As indicated by reference numeral 510, the network node 110 may send a first indication of a CG configuration associated with a CG assigned to the UE, and the UE 120 may receive the first indication. For illustration, the network node 110 may send an indication of a frequency domain allocation for the CG, a time domain allocation for the CG, a first CG timer duration, and / or a first CG retransmission timer duration. Alternatively or additionally, the network node 110 may indicate a set of CG retransmission timer periodicities to the UE 120 as part of the CG configuration or in a separate transmission. For example, the network node 110 may indicate a different value of M for each CG retransmission timer periodicity in the set. The UE 120 may use the set of CG retransmission timer periodicities to select a modification to the CG retransmission timer, as described below. In some aspects, and as part of configuring the UE 120 with the CG, the network node 110 may configure the UE 120 with a CG retransmission timer without an uplink HARQ retransmission timer. Configuring UE 120 without a separate uplink HARQ retransmission timer can implicitly indicate to UE 120 to use the CG retransmission timer as the uplink HARQ retransmission timer and / or to configure the separate uplink HARQ retransmission timer to have the same duration as the CG retransmission timer. In other aspects, network node 110 can direct UE 120 to use the CG retransmission timer instead of a separate HARQ retransmission timer. Configuring UE 120 without a HARQ retransmission timer can reduce the number of times UE 120 wakes up for unnecessary retransmission monitoring, such as when UE 120 and network node 110 are communicating in an environment with a high signal-to-noise ratio (SNR). Reducing the number of times UE 120 wakes up can preserve and / or extend the battery life of UE 120.
[0089] As indicated by reference numeral 520, the network node 110 and the UE 120 may communicate with each other based at least in part on the CG. As one example, for a Type 1 CG, the UE 120 may use one or more uplink opportunities associated with the CG to send one or more uplink transmissions without receiving an explicit and / or separate activation instruction from the network node 110. As another example, for a Type 2 CG, the network node 110 may send a CG activation DCI, and based at least in part on receiving the CG activation DCI, the UE 120 may use one or more uplink opportunities to send one or more uplink transmissions.
[0090] As indicated by reference numeral 530, UE 120 may identify an operational change. As an example of an operational change, UE 120 may receive (e.g., from network node 110) an update to at least one 5QI and / or QoS configuration associated with a QoS flow, such as a change to any combination of a priority level, a delay limit, an error rate, and / or a bit rate. Alternatively or additionally, UE 120 may detect execution of an application and / or a change in an application mode at UE 120 that changes the operational bounds at UE 120 (e.g., changes the priority level, delay limit, error rate, and / or bit rate). For example, the change in application mode may include activation of a video call, activation of an augmented reality mode, activation of a virtual reality mode, and / or activation of a navigation mode, which may reduce and / or shorten the delay limit and / or delay bound and / or increase the data throughput bound.
[0091] Alternatively or additionally, based at least in part on the identification operation change, the UE may evaluate the uplink delay budget, the experienced uplink delay delay and / or the remaining uplink delay to determine whether to modify the CG retransmission timer. For example, the UE may experience an internal uplink delay based at least in part on the delay and / or time span between the arrival of an uplink data packet at the PDCP protocol layer and / or the PDCP queue and the time when the uplink data packet is sent (e.g., the time when the uplink grant is available). Therefore, the uplink delay experienced by the UE and / or the experienced uplink delay delay may be an internal delay at the UE. The UE may compare the (internal) experienced uplink delay delay with the uplink delay budget (e.g., configured by the network node 110), such as by calculating the remaining uplink delay budget and / or the remaining uplink delay in the uplink delay budget. For example, the UE may subtract the value of the experienced uplink delay delay from the value of the uplink delay budget to generate the remaining uplink delay budget and / or the remaining uplink delay. In some aspects, the UE may determine to modify the CG retransmission timer based at least in part on the remaining uplink delay budget not meeting the delay threshold. That is, the remaining uplink delay budget may be too small to meet the delay threshold and / or may indicate that the uplink delay is too tight to meet the delay bound at the UE.
[0092] As another example, UE 120 may calculate the remaining uplink delay based at least in part on two or more logical channels. For illustration, UE 120 may communicate with network node 110 based at least in part on the use of multiple logical channels, and each logical channel may have a different delay bound. Therefore, the UE may select the shortest and / or minimum delay bound associated with the multiple logical channels to ensure that the UE can meet all delay bounds associated with the multiple logical channels. That is, the UE may identify the minimum and / or shortest delay bound among the multiple delay bounds to determine whether the remaining uplink delay will enable the UE to meet the minimum delay bound and then meet other longer delay bounds. If the UE cannot meet the minimum delay bound, the UE may determine to modify the CG retransmission timer.
[0093] In some aspects, UE 120 may determine to modify the CG retransmission timer based at least in part on a quality metric (e.g., RSSI, RSRP, and / or bit error rate). For example, a quality metric that meets a quality threshold may indicate to UE 120 that a retransmission between UE 120 and network node 110 is unlikely to occur. Thus, UE 120 may determine to modify the CG retransmission timer in scenarios where the quality threshold is met.
[0094] As indicated by reference numeral 540, the UE 120 may determine a modification to the CG retransmission timer. As an example, the UE may determine to terminate and / or disable the CG retransmission timer based at least in part on a remaining uplink delay failing to meet a delay bound for an application, logical channel, and / or QoS flow. Alternatively or additionally, the UE 120 may determine to terminate and / or disable the CG retransmission timer based at least in part on a quality metric meeting a quality threshold. In other examples, the UE 120 may determine a change to the periodicity of the CG retransmission timer, such as in a scenario where the quality metric fails to meet the quality threshold. For illustration, the UE 120 may determine to shorten or extend the duration of the periodicity associated with the CG retransmission timer based at least in part on a delay bound being shortened or increased, respectively, and / or a quality metric indicating that retransmission between the UE 120 and the network node 110 is more likely. In some aspects, the UE 120 may determine to skip one or more uplink opportunities associated with the CG. For example, UE 120 may determine a duration to increase the periodicity of the CG retransmission timer and subsequently extend the periodicity by changing a decrement factor of the CG retransmission timer and / or by skipping one or more uplink opportunities. Alternatively or additionally, UE 120 may indicate that the CG retransmission timer may be disabled, may be modified, has been disabled (e.g., by UE 120), and / or has been modified (e.g., by UE 120), such as by setting a field (e.g., a bit field) in uplink control information (UCI) and / or configuration grant uplink control information (CG-UCI) to a specific value (e.g., "1" or "0"). CG-UCI may be a type of UCI included in each CG PUSCH transmission.
[0095] The UE 120 may autonomously adapt and / or change the periodicity of the CG retransmission timer based at least in part on the experienced uplink delay, such as by selecting a periodicity that enables the UE to meet the uplink delay bound. In some aspects, the UE 120 may select a periodicity from a set of retransmission timer periodicities indicated by the network node 110, as described with respect to reference numeral 510. The UE 120 may determine to use the same change in the periodicity and / or duration of the CG retransmission timer for the HARQ retransmission timer associated with the CG and / or HARQ process. However, in other aspects, the UE 120 may determine a second different periodicity change and / or a second different duration of the HARQ retransmission timer based at least in part on selecting a change to the CG retransmission timer.
[0096] As indicated by reference numeral 550, UE 120 may send an indication of the modification, and network node 110 may receive the indication. The indication of the modification may specify any combination of termination of the CG retransmission timer, a change in the periodicity of the CG retransmission timer, and / or a preferred periodicity change of the CG retransmission timer. For example, UE 120 may indicate an autonomous periodicity change and / or termination of the CG retransmission timer that has been implemented by UE 120, or may indicate one or more preferred periodicity changes to the CG retransmission timer from which network node 110 may select, as described below.
[0097] UE 120 may send an indication of the modification in layer 1 signaling, layer 2 signaling and / or layer 3 signaling. As an example, layer 1 signaling may include UCI and / or CG-UCI. As another example, layer 2 signaling may include a medium access control (MAC) control element (CE) and / or layer 3 signaling may include an RRC message. UE 120 may select and / or use a particular type of signaling to send the indication based at least in part on the current CG state. For example, the UE may send an indication of the modification in layer 1 signaling based at least in part on the expiration of the first transmission opportunity of the CG. That is, if the first transmission opportunity has passed, the UE may use layer 1 signaling to send the indication, which may provide the network node 110 with more time to reallocate future CG opportunity resources to other UEs. For illustration, layer 1 signaling may be faster than layer 2 and / or layer 3 signaling, so that the network node 110 receives the indication in time to reallocate resources to another UE.
[0098] In some aspects, the UE 120 may determine to modify and / or send an indication of the modification based at least in part on the allowed update duration. For example, after selecting a first modification to the CG retransmission timer and sending an indication of the first modification, additional modifications to the CG retransmission timer may not be allowed. Thus, the UE 120 may send a first indication of the first modification within the allowed update duration and refrain from selecting and / or sending a second modification associated with the CG retransmission timer within the allowed update duration. That is, the UE 120 will refrain from selecting and / or sending the second modification until the allowed update duration expires, which allowed update duration may be periodic.
[0099] As shown in reference numeral 560, the network node 110 may reconfigure one or more aspects of the CG, such as the periodicity of a CG retransmission timer associated with the CG and / or the duration of the CG timer. For example, based at least in part on receiving an indication of a modification to the CG retransmission timer as described with respect to reference numeral 550, the network node 110 may adapt and / or modify the duration associated with the CG timer (e.g., extend or shorten) according to the modification to the CG retransmission timer. That is, the network node 110 may send a reconfiguration instruction to the UE 120 indicating the modification of the CG timer. Alternatively or additionally, the network node 110 may reconfigure the duration of the CG retransmission timer based at least in part on the modification indicated by the UE 120. For example, the UE 120 may indicate one or more preferred periodicity changes to the CG retransmission timer, and the network node 110 may reconfigure the CG retransmission timer (and / or the CG timer) by selecting one of the preferred periodicity changes and sending a reconfiguration instruction to the UE 120. In some aspects, the network node 110 may calculate a remaining packet delay budget based at least in part on the modification indicated by the UE 120 and reconfigure the CG retransmission timer (and / or CG timer) for the next uplink CG opportunity associated with the retransmission. For example, the nominal packet delay budget P may be based at least in part on the QoS framework and / or the 5QI value. Alternatively or additionally, the nominal packet delay budget P may be based at least in part on the protocol data unit (PDU) set delay budget. The experienced delay D may be observed by the network node 110 (and / or indicated to the network node 110 by the UE 120), and the network node 110 may calculate the remaining packet delay budget as the difference in PD. The network node 110 may reconfigure the CG retransmission timer and / or CG timer based at least in part on the difference satisfying a reconfiguration threshold.
[0100] However, in other aspects, UE 120 may modify the CG retransmission timer autonomously and without requiring reconfiguration instructions from network node 110.
[0101] As indicated by reference numeral 570, the network node 110 and the UE 120 may communicate with each other based at least in part on the modification. As an example, the UE 120 may apply the CG retransmission timer duration modification to the CG retransmission timer and send one or more retransmissions based at least in part on the CG retransmission timer duration modification. Alternatively or additionally, the UE 120 may apply the CG timer duration modification as described above. In some aspects, the UE 120 may also apply the CG retransmission timer duration modification to a HARQ retransmission timer associated with the HARQ process and the CG. However, in other aspects, the modification to the CG retransmission timer duration may be independent of and / or distinct from the modification to the HARQ retransmission timer duration.
[0102] As described above, the UE 120 may determine a duration to shorten or increase the periodicity of the CG retransmission timer. In some aspects, the UE 120 may implicitly indicate an extension of the periodicity by changing a decrement factor of the CG retransmission timer. As an example, the UE 120 may increase the periodicity of the CG retransmission timer by decrementing the CG retransmission timer based at least in part on one or more uplink opportunities of the CG and avoiding decrementing the configuration grant retransmission timer based at least in part on one or more downlink opportunities. Alternatively or additionally, the UE 120 may use a periodicity selected from a set of retransmission timer periodicities, and the network node 110 may blindly decode the periodicity by monitoring the duration between retransmissions. The UE 120 may indicate that the CG retransmission timer may be modified, may be disabled, has been disabled (e.g., by the UE 120), and / or has been modified (e.g., by the UE 120) by setting a field in the UCI and / or CG-UCI.
[0103] As indicated by reference numeral 580, the UE 120 may iteratively detect operational changes and / or iteratively determine modifications to the CG retransmission timer. For illustration, the UE 120 may detect deactivation of a voice call, deactivation of an augmented reality mode, deactivation of a virtual reality mode, and / or deactivation of a navigation mode that results in an increase in the delay margin as an operational change. The UE 120 may calculate and / or generate an updated delay threshold (e.g., an updated delay threshold indicating tolerance for longer uplink data transmission delays) based at least in part on detecting the operational change. The UE may calculate the remaining uplink delay budget described above, determine that the remaining uplink delay budget satisfies the updated delay threshold, and determine an increase in the periodicity of the CG retransmission timer as a modification. Accordingly, and based at least in part on iteratively determining the modification, the UE 120 may send an indication of the (updated) modification to the network node 110 and / or communicate with the network node 110 based at least in part on the (updated) modification to the CG retransmission timer and the CG.
[0104] As indicated by reference numeral 590, the network node 110 may reallocate one or more air interface resources associated with the CG to a second UE (e.g., another UE 120). For example, the UE may indicate expiration of the CG reconfiguration timer, and the network node 110 may reallocate one or more air interface resources associated with the CG, such as air interface resources associated with uplink opportunities for retransmission, to the other UE. The reallocation of air interface resources may increase data throughput and / or reduce data transmission latency within the wireless network based at least in part on the network node 110 having more air interface resources available to the other UE more quickly (e.g., relative to not reallocating unused CG resources). Alternatively or additionally, by autonomously modifying the CG retransmission timer and / or autonomously requesting modification of the CG retransmission timer, the UE 120 may mitigate uplink transmission delays that exceed a data transmission latency bound for operations that may be time-sensitive. Thus, mitigating uplink transmission delays may enable the UE to meet data transmission latency bounds and support time-sensitive operations.
[0105] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.
[0106] Figure 6 is a diagram illustrating an example process 600, performed, for example, by a UE, in accordance with the present disclosure. Example process 600 is an example in which a UE (eg, UE 120) performs operations associated with UE modification of a configuration grant retransmission timer.
[0107] like Figure 6 As shown, in some aspects, process 600 may include receiving a first indication for configuration of a configuration grant retransmission timer associated with a configuration grant assigned to a UE (block 610). For example, a UE (e.g., using Figure 8 Depicted receiving component 802 and / or communications manager 806) can receive a first indication for configuration of a configuration grant retransmission timer associated with a configuration grant assigned to a UE, as described above.
[0108] like Figure 6 As further shown, in some aspects, process 600 may include determining a modification to a configuration for configuring a grant retransmission timer based at least in part on the remaining uplink delay budget (block 620). Figure 8 The depicted communications manager 806) may determine modifications to a configuration for configuring a grant retransmission timer based at least in part on a remaining uplink delay budget, as described above.
[0109] like Figure 6As further shown, in some aspects, process 600 may include sending a second indication of the modification (block 630). For example, a UE (e.g., using Figure 8 The depicted sending component 804 and / or communications manager 806) can send a second indication of the modification, as described above.
[0110] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0111] In the first aspect, the second indication is indicated in at least one of the UCI or the CG-UCI.
[0112] In a second aspect, determining the modification based at least in part on the remaining uplink delay budget includes determining that the remaining uplink delay budget fails to satisfy a latency threshold.
[0113] In a third aspect, the modification includes configuring expiration of a grant retransmission timer.
[0114] In a fourth aspect, the modification comprises a change to the periodicity of configuring a grant retransmission timer.
[0115] In a fifth aspect, the change to the periodicity of the configuration grant retransmission timer includes at least one of shortening the duration of the periodicity or lengthening the duration of the periodicity.
[0116] In a sixth aspect, the modifying comprises skipping one or more uplink opportunities associated with the configuration grant.
[0117] In a seventh aspect, sending a first indication of the modification comprises sending the first indication in at least one of layer 1 signaling, layer 2 signaling, or layer 3 signaling.
[0118] In an eighth aspect, sending a first indication of the modification comprises sending the first indication in layer 1 signaling based at least in part on sending the first indication of the modification after a first transmission opportunity of a configuration grant.
[0119] In a ninth aspect, layer 1 signaling includes uplink control information.
[0120] In a tenth aspect, layer 2 signaling includes MAC CE.
[0121] In an eleventh aspect, layer 3 signaling includes RRC messages.
[0122] In a twelfth aspect, sending the first indication of the modification comprises sending the first indication of the modification based at least in part on an allowed update duration.
[0123] In a thirteenth aspect, the modification is a first modification, sending a first indication of the modification includes sending the first indication of the first modification within an allowed update duration, and process 600 includes avoiding sending a second modification associated with configuring a grant retransmission timer within the allowed update duration.
[0124] In a fourteenth aspect, the allowed update duration is periodic.
[0125] In a fifteenth aspect, process 600 includes calculating uplink latency and determining that the uplink latency fails to meet a latency threshold, and determining the modification includes determining to disable a configuration grant retransmission timer as the modification based at least in part on the uplink latency failing to meet the latency threshold.
[0126] In a sixteenth aspect, calculating uplink delay is based at least in part on an experienced uplink delay value.
[0127] In a seventeenth aspect, calculating uplink latency is based at least in part on a minimum delay associated with two or more logical channels.
[0128] In an eighteenth aspect, the configuration for configuring a grant retransmission timer includes a first retransmission timer periodicity, and the process 600 includes receiving a set of retransmission timer periodicities, and selecting a second retransmission timer periodicity from the set of retransmission timer periodicities and serving as the modification.
[0129] In a nineteenth aspect, the modification comprises a timer duration modification, and process 600 comprises applying the timer duration modification to a configuration grant retransmission timer and a HARQ retransmission timer associated with the HARQ process and the configuration grant.
[0130] In a twentieth aspect, the modification is a first modification, and process 600 includes determining a second modification to the HARQ retransmission timer based at least in part on determining the first modification.
[0131] In a twenty-first aspect, process 600 includes receiving a second configuration associated with a configuration grant timer, the second configuration based at least in part on the modification, and the configuration grant timer is associated with the configuration grant.
[0132] In a twenty-second aspect, process 600 includes generating an updated latency threshold based at least in part on a change at a UE; determining that a remaining uplink delay budget satisfies the updated latency threshold; and increasing a periodicity of a configured grant retransmission timer.
[0133] In a twenty-third aspect, the change comprises an update to at least one QoS configuration associated with the QoS flow.
[0134] In a twenty-fourth aspect, increasing the periodicity comprises increasing the periodicity implicitly and based at least in part on changing a decrement factor of a configured grant retransmission timer.
[0135] In a twenty-fifth aspect, changing the decrement factor includes decrementing a configured grant retransmission timer based at least in part on one or more uplink opportunities, and refraining from decrementing the configured grant retransmission timer based at least in part on one or more downlink opportunities.
[0136] In a twenty-sixth aspect, process 600 includes using a configuration grant retransmission timer instead of a HARQ retransmission timer.
[0137] although Figure 6 Example blocks of process 600 are shown, but in some aspects, process 600 may include Figure 6 The blocks depicted may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.
[0138] Figure 7 is a diagram illustrating an example process 700, performed, for example, by a network node, in accordance with the present disclosure. Example process 700 is an example in which a network node (eg, network node 110) performs operations associated with UE modification of a configuration grant retransmission timer.
[0139] like Figure 7 As shown, in some aspects, process 700 may include sending a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE (block 710). For example, a network node (e.g., using Figure 9 Depicted transmitting component 904 and / or communications manager 906) can transmit a first indication of configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE, as described above.
[0140] like Figure 7 As further shown, in some aspects, process 700 may include receiving a second indication of a modification to a configuration for configuring a grant retransmission timer (block 720). For example, a network node (e.g., using Figure 9 Depicted receiving component 902 and / or communications manager 906) can receive a second indication of a modification to the configuration for configuring the grant retransmission timer, as described above.
[0141] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0142] In a first aspect, process 700 includes reallocating one or more air interface resources associated with a configuration grant to a second UE.
[0143] In a second aspect, the modification includes disabling a configuration grant retransmission timer.
[0144] In a third aspect, the modification comprises a change to the periodicity of a configuration grant retransmission timer.
[0145] In a fourth aspect, the change to the periodicity of the configuration grant retransmission timer includes at least one of shortening the duration of the periodicity or lengthening the duration of the periodicity.
[0146] In a fifth aspect, the modification comprises at least one of: terminating a configuration grant retransmission timer early, or skipping one or more uplink opportunities associated with the configuration grant.
[0147] In a sixth aspect, receiving a first indication of the modification comprises receiving the first indication in at least one of layer 1 signaling, layer 2 signaling, or layer 3 signaling.
[0148] In a seventh aspect, receiving a first indication of the modification comprises receiving the first indication of the modification in layer 1 signaling after configuring a first transmit opportunity of the grant.
[0149] In an eighth aspect, process 700 includes sending a set of retransmission timer periodicities, and receiving a second retransmission timer periodicity included in the set of retransmission timer periodicities as a second indication of a modification.
[0150] In a ninth aspect, process 700 includes determining a second configuration associated with a configuration grant timer, the second configuration based at least in part on the modification, the configuration grant timer associated with the configuration grant; and sending a third indication of the second configuration.
[0151] In a tenth aspect, the modification indicates a request to terminate a configuration grant retransmission timer, and process 700 includes configuring a second configuration grant assigned to the UE that adjusts configuration of the configuration grant retransmission timer.
[0152] In an eleventh aspect, process 700 includes configuring a grant retransmission timer without configuring a HARQ retransmission timer.
[0153] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 The blocks depicted may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.
[0154] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication according to the present disclosure. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802, a sending component 804, and / or a communication manager 806, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 806 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 140. As shown, the device 800 can communicate with another device 808 such as a UE or a network node (such as a CU, DU, RU, or base station) using a receiving component 802 and a sending component 804.
[0155] In some aspects, the apparatus 800 may be configured to perform Figures 4 to 7 Additionally or alternatively, the apparatus 800 may be configured to perform one or more of the processes described herein such as Figure 6 In some aspects, Figure 8 The device 800 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the UE described. Figure 8 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.
[0156] The receiving component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 808. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.
[0157] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the apparatus 808. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 808. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmitting component 804 can be co-located with the receiving component 802 in a transceiver.
[0158] The communications manager 806 can support the operation of the receiving component 802 and / or the sending component 804. For example, the communications manager 806 can receive information associated with configuring the receipt of communications by the receiving component 802 and / or the sending of communications by the sending component 804. Additionally or alternatively, the communications manager 806 can generate and / or provide control information to the receiving component 802 and / or the sending component 804 to control the receipt and / or sending of communications.
[0159] Receiving component 802 may receive a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a UE. Communications manager 806 may determine a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget. Transmitting component 804 may transmit a second indication of the modification.
[0160] The communications manager 806 may calculate the uplink latency.
[0161] The communications manager 806 may determine that the uplink latency fails to meet the latency threshold.
[0162] Receiving component 802 can receive a second configuration associated with a configuration grant timer associated with the configuration grant, the second configuration based at least in part on the modification.
[0163] Communications manager 806 can generate an updated latency threshold based at least in part on the change at the UE.
[0164] Communications manager 806 may determine that the remaining uplink delay budget satisfies the updated latency threshold.
[0165] The communications manager 806 may increase the periodicity of the configured grant retransmission timer.
[0166] The communication manager 806 may use the configuration grant retransmission timer instead of the HARQ retransmission timer.
[0167] Figure 8 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 8 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 8 Two or more components shown may be implemented in a single component, or Figure 8 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The illustrated set of components (one or more) may be described as being executable by Figure 8 Another group of components is shown performing one or more functions.
[0168] Figure 9 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902, a sending component 904, and / or a communication manager 906, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 906 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 150. As shown, the device 900 can communicate with another device 908, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 902 and a sending component 904.
[0169] In some aspects, the apparatus 900 may be configured to perform the Figures 4 to 7 Additionally or alternatively, the apparatus 900 may be configured to perform one or more of the processes described herein such as Figure 7 In some aspects, Figure 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the described network node. Figure 9 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.
[0170] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 908. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the receiving component 902 and / or the transmitting component 904 may include or be included in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 900 via one or more communication links, such as a backhaul link, a midhaul link, and / or a fronthaul link.
[0171] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 908. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 908. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 908. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmitting component 904 can be co-located with the receiving component 902 in a transceiver.
[0172] The communications manager 906 can support the operation of the receiving component 902 and / or the sending component 904. For example, the communications manager 906 can receive information associated with configuring the receipt of communications by the receiving component 902 and / or the sending of communications by the sending component 904. Additionally or alternatively, the communications manager 906 can generate and / or provide control information to the receiving component 902 and / or the sending component 904 to control the receipt and / or sending of communications.
[0173] Transmitting component 904 can transmit a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE.Receiving component 902 can receive a second indication of a modification to the configuration for the configuration grant retransmission timer.
[0174] Transmitting component 904 can transmit a set of retransmission timer periodicities.
[0175] Receiving component 902 can receive a second retransmission timer periodicity included in the set of retransmission timer periodicities as a second indication of a modification.
[0176] Communications manager 906 may determine a second configuration associated with a configuration grant timer associated with the configuration grant, the second configuration based at least in part on the modification.
[0177] Sending component 904 can send a third indication of the second configuration.
[0178] The communication manager 906 may configure the grant retransmission timer without configuring the HARQ retransmission timer.
[0179] Figure 9 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 9 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 9 Two or more components shown may be implemented in a single component, or Figure 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The illustrated set of components (one or more) may be described as being executable by Figure 9 Another group of components is shown performing one or more functions.
[0180] The following provides an overview of some aspects of the disclosure:
[0181] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to the UE; determining a modification to the configuration for the configuration grant retransmission timer based at least in part on a remaining uplink delay budget; and sending a second indication of the modification.
[0182] Aspect 2: The method according to aspect 1, wherein the second indication is indicated in at least one of the following: uplink control information (UCI), or configuration grant uplink control information (CG-UCI).
[0183] Aspect 3: The method according to any one of aspects 1 to 2, wherein determining the modification based at least in part on the remaining uplink delay budget includes determining that the remaining uplink delay budget fails to meet a latency threshold.
[0184] Aspect 4: The method according to any one of aspects 1 to 3, wherein the modification comprises termination of the configuration grant retransmission timer.
[0185] Aspect 5: The method according to any one of aspects 1 to 4, wherein the modification comprises a change in the periodicity of the configuration grant retransmission timer.
[0186] Aspect 6: The method according to aspect 5, wherein the change to the periodicity of the configuration grant retransmission timer comprises at least one of: shortening the duration of the periodicity, or lengthening the duration of the periodicity.
[0187] Aspect 7: The method according to any one of aspects 1 to 6, wherein the modification comprises skipping one or more uplink opportunities associated with the configuration grant.
[0188] Aspect 8: The method according to any one of aspects 1 to 7, wherein sending the first indication of the modification comprises sending the first indication in at least one of the following: layer 1 signaling, layer 2 signaling, or layer 3 signaling.
[0189] Aspect 9: The method of aspect 8, wherein sending the first indication of the modification comprises sending the first indication in the layer 1 signaling based at least in part on sending the first indication of the modification after a first sending opportunity of the configuration grant.
[0190] Aspect 10: The method according to aspect 8, wherein the layer 1 signaling includes uplink control information.
[0191] Aspect 11: The method of aspect 8, wherein the layer 2 signaling comprises a medium access control (MAC) control element (CE).
[0192] Aspect 12: The method according to aspect 8, wherein the layer 3 signaling includes a radio resource control (RRC) message.
[0193] Aspect 13: The method of any one of aspects 1 to 12, wherein sending the first indication of the modification comprises sending the first indication of the modification based at least in part on an allowed update duration.
[0194] Aspect 14: A method according to Aspect 13, wherein the modification is a first modification, wherein sending the first indication of the modification includes: sending the first indication of the first modification within the allowed update duration, and wherein the method also includes: avoiding sending a second modification associated with the configuration grant retransmission timer within the allowed update duration.
[0195] Aspect 15: The method according to aspect 13, wherein the allowed update duration is periodic.
[0196] Aspect 16: The method of any one of aspects 1 to 15, further comprising: calculating an uplink delay; and determining that the uplink delay fails to meet a delay threshold, wherein determining the modification comprises: determining to disable the configuration grant retransmission timer as the modification based at least in part on the uplink delay failing to meet the delay threshold. In some aspects, determining the modification comprises: determining to disable the configuration grant retransmission timer as the modification based at least in part on the uplink delay failing to meet the delay threshold.
[0197] Aspect 17: The method of aspect 16, wherein calculating the uplink delay is based at least in part on an experienced uplink delay value.
[0198] Aspect 18: The method of aspect 16, wherein calculating the uplink delay is based at least in part on a minimum delay associated with two or more logical channels.
[0199] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the configuration for configuring the grant retransmission timer includes a first retransmission timer periodicity, and wherein the method further includes: receiving a set of retransmission timer periodicities; and selecting a second retransmission timer periodicity from the set of retransmission timer periodicities and as the modification.
[0200] Aspect 20: A method according to any one of Aspects 1 to 19, wherein the modification includes a timer duration modification, and the method further includes: applying the timer duration modification to the configuration grant retransmission timer and a hybrid automatic repeat request (HARQ) retransmission timer associated with the HARQ process and the configuration grant.
[0201] Aspect 21: A method according to any one of aspects 1 to 20, wherein the modification is a first modification, and the method further comprises: determining a second modification of a hybrid automatic repeat request (HARQ) retransmission timer based at least in part on determining the first modification.
[0202] Aspect 22: The method according to any one of aspects 1 to 21, further comprising: receiving a second configuration associated with a configuration grant timer, the second configuration being based at least in part on the modification, the configuration grant timer being associated with the configuration grant.
[0203] Aspect 23: According to the method described in any one of Aspects 1 to 22, the method also includes: generating an updated delay threshold based at least in part on the changes at the UE; determining that the remaining uplink delay budget meets the updated delay threshold; and increasing the periodicity of the configured grant retransmission timer.
[0204] Aspect 24: The method of aspect 23, wherein the change comprises an update to at least one quality of service (QoS) configuration associated with a QoS flow.
[0205] Aspect 25: The method of aspect 23, wherein increasing the periodicity comprises increasing the periodicity implicitly and based at least in part on changing a decrement factor of the configured grant retransmission timer.
[0206] Aspect 26: A method according to Aspect 25, wherein changing the decrement factor includes: decrementing the configuration grant retransmission timer based at least in part on one or more uplink opportunities; and avoiding decrementing the configuration grant retransmission timer based at least in part on one or more downlink opportunities.
[0207] Aspect 27: The method according to any one of aspects 1 to 26, further comprising: using the configuration grant retransmission timer instead of using a hybrid automatic repeat request (HARQ) retransmission timer.
[0208] Aspect 28: A method of wireless communication performed by a network node, the method comprising: sending a first indication of a configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a user equipment (UE); and receiving a second indication of a modification of the configuration for the configuration grant retransmission timer.
[0209] Aspect 29: The method of aspect 28, further comprising reallocating one or more air interface resources associated with the configuration grant to a second UE.
[0210] Aspect 30: The method according to any one of aspects 28 to 29, wherein the modification comprises disabling the configuration grant retransmission timer.
[0211] Aspect 31: The method according to any one of aspects 28 to 30, wherein the modification comprises a change in the periodicity of the configuration grant retransmission timer.
[0212] Aspect 32: The method according to aspect 31, wherein the change to the periodicity of the configuration grant retransmission timer comprises at least one of: shortening the duration of the periodicity, or lengthening the duration of the periodicity.
[0213] Aspect 33: The method according to any one of aspects 28 to 32, wherein the modification comprises at least one of: terminating the configuration grant retransmission timer early, or skipping one or more uplink opportunities associated with the configuration grant.
[0214] Aspect 34: The method according to any one of aspects 28 to 33, wherein receiving the first indication of the modification comprises receiving the first indication in at least one of the following: layer 1 signaling, layer 2 signaling, or layer 3 signaling.
[0215] Aspect 35: The method according to aspect 34, wherein receiving the first indication of the modification comprises: receiving the first indication of the modification in the layer 1 signaling after the first transmission opportunity of the configuration grant.
[0216] Aspect 36: The method according to any one of Aspects 28 to 35 further includes: sending a set of retransmission timer periodicities; and receiving a second retransmission timer period included in the set of retransmission timer periods as the second indication of the modification.
[0217] Aspect 37: A method according to any one of Aspects 28 to 36, the method further comprising: determining a second configuration associated with a configuration grant timer, the second configuration being at least partially based on the modification, the configuration grant timer being associated with the configuration grant; and sending a third indication of the second configuration.
[0218] Aspect 38: A method according to any one of Aspects 28 to 37, wherein the modification indication is used to terminate the request for the configuration grant retransmission timer; and the method further includes: configuring a second configuration grant assigned to the UE for adjusting the configuration of the configuration grant retransmission timer.
[0219] Aspect 39: The method according to any one of aspects 28 to 38, further comprising: configuring the configuration grant retransmission timer without configuring a hybrid automatic repeat request (HARQ) retransmission timer.
[0220] Aspect 40: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 27.
[0221] Aspect 41: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 28 to 39.
[0222] Aspect 42: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 27.
[0223] Aspect 43: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 28 to 39.
[0224] Aspect 44: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 27.
[0225] Aspect 45: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 28 to 39.
[0226] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 27.
[0227] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 28 to 39.
[0228] Aspect 48: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 27.
[0229] Aspect 49: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 28 to 39.
[0230] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.
[0231] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.
[0232] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0233] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).
[0234] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a first indication for configuration of a configuration grant retransmission timer associated with a configuration grant assigned to the UE; determining a modification to said configuration for said configured grant retransmission timer based at least in part on a remaining uplink delay budget; as well as A second indication of the modification is sent.
2. The apparatus of claim 1 , wherein the second indication is indicated in at least one of the following: Uplink Control Information (UCI), or Configuration Grant Uplink Control Information (CG-UCI).
3. The apparatus of claim 1 , wherein to determine the modification based at least in part on the remaining uplink delay budget, the one or more processors are configured to: It is determined that the remaining uplink delay budget fails to meet a delay threshold.
4. The apparatus of claim 1, wherein the modification comprises expiration of the configuration grant retransmission timer.
5. The apparatus of claim 1, wherein the modification comprises a change to a periodicity of the configuration grant retransmission timer.
6. The apparatus of claim 1 , wherein to send the first indication of the modification, the one or more processors are configured to: The first indication of the modification is sent based at least in part on an allowed update duration.
7. The apparatus of claim 1 , wherein the one or more processors are further configured to: Calculate uplink latency; and Determining that the uplink delay fails to meet a delay threshold, Wherein, in order to determine the modification, the one or more processors are configured to: The modification is determined to disable the configuration grant retransmission timer based at least in part on the uplink latency failing to satisfy the latency threshold.
8. The apparatus of claim 1 , wherein the configuration for configuring the grant retransmission timer comprises a first retransmission timer periodicity, and wherein the one or more processors are further configured to: a set of receive retransmission timer periodicities; and A second retransmission timer periodicity is selected from the set of retransmission timer periodicities and serves as the modification.
9. The apparatus of claim 1 , wherein the one or more processors are further configured to: A second configuration associated with a configuration grant timer associated with the configuration grant is received, the second configuration being based at least in part on the modification.
10. The apparatus of claim 1 , wherein the one or more processors are further configured to: generating an updated latency threshold based at least in part on an operational change at the UE; determining that the remaining uplink delay budget satisfies the updated delay threshold; and Increase the periodicity of the configuration grant retransmission timer.
11. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: sending a first indication of configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a user equipment (UE); and A second indication of a modification to the configuration for the configured grant retransmission timer is received.
12. The apparatus of claim 11 , wherein the one or more processors are further configured to: One or more air interface resources associated with the configuration grant are reallocated to a second UE.
13. The apparatus of claim 11, wherein the one or more processors are further configured to disable the configuration grant retransmission timer.
14. The apparatus of claim 11, wherein the modification comprises a change to a periodicity of the configuration grant retransmission timer.
15. The apparatus of claim 11 , wherein to receive the first indication of the modification, the one or more processors are configured to receive the first indication in at least one of: Layer 1 signaling, Layer 2 signaling, or Layer 3 signaling.
16. The apparatus of claim 11, wherein the one or more processors are further configured to: Send a set of retransmission timer periodicities; and A second retransmission timer periodicity included in the set of retransmission timer periodicities is received as the second indication of the modification.
17. The apparatus of claim 11, wherein the one or more processors are further configured to: determining a second configuration associated with a configuration grant timer, the second configuration being based at least in part on the modification, the configuration grant timer being associated with the configuration grant; and A third indication of the second configuration is sent.
18. The apparatus of claim 11, wherein the one or more processors are further configured to: A second configuration grant assigned to the UE is configured to adjust the configuration grant retransmission timer.
19. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first indication for configuration of a configuration grant retransmission timer associated with a configuration grant assigned to the UE; determining a modification to said configuration for said configured grant retransmission timer based at least in part on a remaining uplink delay budget; as well as A second indication of the modification is sent.
20. The method of claim 19, wherein determining the modification based at least in part on the remaining uplink delay budget comprises: It is determined that the remaining uplink delay budget fails to meet a delay threshold.
21. The method of claim 19, wherein the modification comprises at least one of: The configuration grants expiration of the retransmission timer, The configuration grants periodic changes of the retransmission timer.
22. The method of claim 19, wherein sending the first indication of the modification comprises: The first indication of the modification is sent based at least in part on an allowed update duration.
23. The method of claim 19, wherein the configuration for configuring the grant retransmission timer comprises a first retransmission timer periodicity, and wherein the method further comprises: Receive retransmission timer periodicity set; as well as A second retransmission timer periodicity is selected from the set of retransmission timer periodicities and serves as the modification.
24. The method of claim 19, wherein the modification comprises a timer duration modification, and the method further comprises: The timer duration modification is applied to the configuration grant retransmission timer and a hybrid automatic repeat request (HARQ) retransmission timer associated with a HARQ process and the configuration grant.
25. The method of claim 19, wherein the modification is a first modification, and the method further comprises: A second modification of a hybrid automatic repeat request (HARQ) retransmission timer is determined based at least in part on determining the first modification.
26. The method of claim 19, further comprising: A second configuration associated with a configuration grant timer associated with the configuration grant is received, the second configuration being based at least in part on the modification.
27. A method of wireless communication performed by a network node, the method comprising: sending a first indication of configuration for a configuration grant retransmission timer associated with a configuration grant assigned to a user equipment (UE); as well as A second indication of a modification to the configuration for the configured grant retransmission timer is received.
28. The method according to claim 27, wherein the method further comprises: One or more air interface resources associated with the configuration grant are reallocated to a second UE.
29. The method of claim 27, wherein receiving the first indication of the modification comprises: The first indication of the modification is received in layer 1 signaling after a first transmit opportunity of the configuration grant.
30. The method of claim 27, further comprising: determining a second configuration associated with a configuration grant timer, the second configuration being based at least in part on the modification, the configuration grant timer being associated with the configuration grant; as well as A third indication of the second configuration is sent.