Techniques for operating timers related to uplink transmissions
By introducing a conditional triggering mechanism into the cellular wireless communication system and dynamically adjusting the timer, the problem of low resource utilization efficiency in user equipment is solved, and more efficient uplink transmission and power consumption optimization are achieved.
Patent Information
- Application Number
- CN202410614837.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-17
- Publication Date
- 2024-11-22
AI Technical Summary
In existing cellular wireless communication systems, the timer configuration of user equipment is not flexible enough, resulting in low resource utilization efficiency, especially in the uplink transmission where there is unnecessary power consumption and latency.
By introducing a condition-triggered mechanism in the user equipment, the start and stop of the timer are dynamically adjusted according to the delay information and priority of the data unit, thereby optimizing the timer configuration for uplink transmission, including the management of the CG timer and DRX timer.
It improved resource utilization efficiency, reduced unnecessary power consumption, ensured the timely transmission of important data, and enhanced the overall performance of the system.
Smart Images

Figure CN119011098A_ABST
Abstract
Description
[0001] Cross-references to other applications
[0002] This application claims priority to U.S. Provisional Application No. 63 / 467,858, filed on May 19, 2023, entitled “TECHNOLOGIES FOR OPERATING TIMERS RELATED TO UPLINK TRANSMISSIONS,” which is incorporated herein by reference in its entirety for all purposes. Technical Field
[0003] The present application relates generally to cellular communication networks, and in particular to techniques for operating a timer associated with uplink transmissions. Background Art
[0004] In a cellular wireless communication system, a user equipment (UE) may utilize several timers to track operations. Some timers may control resource utilization by allowing or preventing the UE from performing certain operations. It is desirable to configure timers that improve resource utilization of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Figure 1 A network environment according to some embodiments is shown.
[0006] Figure 2 A timing diagram according to some embodiments is shown.
[0007] Figure 3 A timing diagram according to some embodiments is shown.
[0008] Figure 4 An operational flow / algorithm structure according to some embodiments is shown.
[0009] Figure 5 An operational flow / algorithm structure according to some embodiments is shown.
[0010] Figure 6 An operational flow / algorithm structure according to some embodiments is shown.
[0011] Figure 7 An operational flow / algorithm structure according to some embodiments is shown.
[0012] Figure 8 A user device according to some embodiments is shown.
[0013] Fig. 9 A network node according to some embodiments is shown. DETAILED DESCRIPTION
[0014] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of explanation rather than limitation, specific details, such as specific structures, architectures, interfaces and / or technologies, are set forth to provide a thorough understanding of the various aspects of some embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that the various aspects of various aspects can be practiced in other examples that deviate from these specific details. In some cases, the description of well-known equipment, circuits and methods is omitted so that the description of various aspects will not be obscured by unnecessary details. For the purpose of this document, the phrase "A or B" refers to (A), (B) or (A and B), and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".
[0015] The following is a glossary of terms that may be used in this disclosure.
[0016] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), and / or a digital signal processor (DSP). In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these aspects, the combination of hardware elements and program code may be referred to as a specific type of circuit.
[0017] As used herein, the term "processor circuit" refers to, is a part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or a circuit that records, stores, or transmits digital data. The term "processor circuit" may refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.
[0018] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces; for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.
[0019] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.
[0020] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.
[0021] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computer, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computer, storage or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.
[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.
[0023] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.
[0024] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.
[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.
[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single content of an information element or a data element that contains content. An information element may include one or more additional information elements.
[0027] Figure 1 A network environment 100 according to some embodiments is shown. The network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN). In some embodiments, the BS 108 is a next generation node B (gNB) providing one or more 3GPP new radio (NR) cells. In other embodiments, the BS 108 is an evolved node B (eNB) providing one or more long term evolution (LTE) cells. The air interface via which the UE 104 and the BS 108 communicate may be compatible with 3GPP technical specifications (TS), such as those defining fifth generation (5G) NR or later system standards (e.g., sixth generation (6G) standards).
[0028] BS 108 may send control information to UE in downlink control information (DCI) on physical downlink control channel (PDCCH). BS 108 may send control information for all UEs in its network, or may send dedicated control information for a specific UE (e.g., UE 104). However, UE 104 may not know the location, structure, or scrambling code of its dedicated DCI. Therefore, UE 104 monitors PDCCH to obtain public or dedicated DCI. Monitoring PDCCH is based on trial-and-error methods such as blind decoding.
[0029] UE 104 may continuously monitor the PDCCH even when BS 108 is not sending any data to UE 104. Continuous monitoring of the PDCCH may consume a significant amount of power, thereby reducing the battery life of UE 104.
[0030] The BS 108 may configure discontinuous reception (DRX) to the UE 104. DRX allows the UE 104 to periodically enter a DRX inactive mode during a DRX off duration or DRX off cycle. When in the DRX inactive mode, the UE 104 does not monitor the PDCCH. The DRX off cycle is known to the BS 108, so the BS 108 may not send any information to the UE 104 during the UE's DRX off cycle. When the UE 104 is not in a DRX off cycle, the UE is in a DRX on cycle or DRX active mode, during which the UE 104 may monitor the PDCCH.
[0031] BS108 may configure one or more timers 140 associated with DRX to UE 104. BS 108 may configure timer 140 using configuration 110 signaling. In one example, a timer in one or more timers 140 may track a DRX on cycle. When the timer expires, UE 104 may transition to DRX inactive mode. For example, drx-onDurationTimer tracks the DRX on cycle during which UE 104 remains active and may monitor PDCCH. If UE 104 does not receive PDCCH during DRX on, the UE may transition to DRX inactive mode when drx-onDurationTimer expires. UE 104 may remain in DRX inactive mode until the next DRX on duration begins. UE 104 may start a round trip time (RTT) timer in one or more timers 140 that tracks the time during which UE 104 may not expect to receive DCI from BS 108 after UL transmission. For example, the UE 104 may track the RTT using drx-HARQ-RTT-TimerUL. The UE 104 may start a retransmission timer in one or more timers 140 to track the time when the UE 104 should monitor the PDCCH for retransmission requests associated with the UL transmission. For example, when drx-HARQ-RTT-TimerUL expires, the UE 104 may start drx-RetransmissionTimerUL. While drx-RetransmissionTimerUL is running, the UE should be in DRX active mode to monitor the PDCCH, and when drx-RetransmissionTimerUL expires or stops or when a retransmission grant is received, the UE should return to DRX inactive mode.
[0032] The UL transmission may be associated with a hybrid automatic repeat request (HARQ) process. The HARQ process may provide reliable communication by combining error correction and retransmission. For example, the BS 108 may send a UL grant 120 to the UE 104 indicating the resources to be used for the UL transmission, including a HARQ process identifier (HARQ PID). If the UL transmission is not received by the BS 108, for example, it is not successfully decoded, the BS 108 may request a retransmission. For example, the BS 108 may send another UL grant 120 to the UE 104 indicating that no new data should be transmitted and including an indication of the HARQ PID. Therefore, in the event of a retransmission request received from the BS 108, the UE 104 may need to monitor the PDCCH after each UL transmission.
[0033] UL traffic that needs to be transmitted periodically (such as XR attitude updates) may require frequent UL scheduling and resource allocation. In one example, the UE 104 may send a scheduling request for each UL transmission. In response to the scheduling request, the BS 108 will send a UL grant 120, such as through a dynamic UL grant, to allocate resources for the UL transmission 130 or for the transmission of a buffer status report (BSR) 150.
[0034] In another example, the BS 108 may allocate resources for more than one UL transmission. In one example, the BS 108 may allocate UL resources to be periodically used by the UE 104 for UL transmissions. For example, the BS 108 may use configuration grant (CG) scheduling for the UL transmissions 130, thereby eliminating the need for scheduling requests by the UE 104 and resource allocations by the BS 108 for each UL transmission 130. The BS 108 may send a configuration 110 message (e.g., a CG) to the UE 104 to pre-allocate resources to the UE 104 for the UL transmissions 130. The configuration 110 may allocate one or more HARQ processes to the CG.
[0035] In a conventional system, an UL transmission may trigger the UE to start a timer 140, such as a CG timer. The UE 104 may start the CG timer on the first orthogonal frequency division multiplexing (OFDM) symbol of a physical uplink shared channel (PUSCH) transmission. The CG timer may be associated with the PUSCH transmission and the HARQ PID of the PUSCH transmission. When the CG timer associated with the HARQ process is running, the UE may not use the CG resources associated with the same HARQ PID.
[0036] The UE 104 may send a buffer status report (BSR) 150 to the base station 108 to indicate the amount of uplink data that the UE 104 has to transmit. The BSR 150 may be transmitted as a medium access control (MAC) control element (CE) on a physical uplink shared channel (PUSCH). The BSR 150 may be associated with a logical channel (LCH) or a logical channel group (LCG) having one or more LCHs. Upon receiving the BSR, the BS 108 may determine an appropriate amount of uplink (UL) resources for the UE 104. The BS 108 may then transmit an uplink grant to the UE 104. The UE 104 may use the UL grant for subsequent UL transmissions.
[0037] UE 104 may transmit a regular BSR, a periodic BSR, or a padding BSR. A regular BSR may be triggered when new uplink data for an LCH in an LCG becomes available in the MAC buffer and the LCH has a higher priority than any other LCH with buffered data or no other LCH has buffered data. A regular BSR may also be triggered when a retransmission BSR timer (retxBSR-Timer) expires and the LCH includes buffered data to be transmitted. The retransmission BSR timer may be used to avoid a deadlock situation that may occur when the base station 108 fails to receive the BSR, but the UE 104 believes that the BSR transmission was successful. Therefore, the retransmission BSR timer provides a limited time period for the UE 104 to wait for an uplink grant before retransmitting the BSR. The retransmission BSR timer is started when the BSR is multiplexed into a MAC protocol data unit (PDU).
[0038] Existing BSRs only provide information about buffer sizes. The BSR may also include other buffer delay information to facilitate delay-aware scheduling with latency constraints. For example, the BSR may include how long data from one or more LCHs has been queued, the amount of time remaining before a delivery deadline for data buffered in one or more LCHs, the estimated time before the end of packet transmission, or an indication of whether data from one or more logical channels is considered urgent data. In one example, an indicator associated with a data unit may determine the urgency of the data unit.
[0039] Different data units may be buffered in the buffers of an LCH or LCG. For example, data units may belong to different PDU sets with different delivery deadlines. Due to jitter, data units may arrive at the buffers at different times. Furthermore, data units may be associated with different QoS flows. Data units may be buffered in different LCHs or LCGs with different delay information.
[0040] In general, a data unit may be any portion of the buffered data. In some instances, a data unit may refer to: a packet data convergence protocol (PDCP) service data unit (SDU) or a PDCP PDU, a group of multiple PDCP SDUs or a PDCP PDU, a radio link control (RLC) PDU or an RLC SDU, an RLC SDU segment, a group of multiple RLC PDUs, a group of multiple RLS SDUs, a group of RLS SDU segments, a PDU set, a group of PDU sets, or a portion of the buffered data associated with a particular QoS flow.
[0041] A data unit or packet may belong to an important PDU set or a non-important PDU set. In one example, an indicator associated with a PDU set may determine the importance level of the PDU set.
[0042] Consider a CG timer running after an UL transmission on the CG associated with the HARQ process. In addition, consider buffering important or urgent data units of delay-sensitive traffic flows for transmission on the CG when the CG timer blocks CG resources. In some embodiments, the UE 104 may determine that the transmission of important or urgent data may override the CG timer and allocate CG resources for the UL transmission, thereby ignoring the CG timer.
[0043] The CG timer value (e.g., how long the CG timer should run after a CG PUSCH transmission) may be preconfigured or fixed. The CG timer may be running even after an UL transmission is delivered. In another embodiment, the UE 104 may determine that operation of the CG timer is unnecessary. For example, the duration of the CG timer is unnecessarily long, and therefore the CG timer is set to a different value.
[0044] The duration of the DRX retransmission timer may be configurable or fixed. In one example, the UL PDU may have reached its delivery deadline before the DRX retransmission timer expires. In one embodiment, the UE 104 may stop the DRX retransmission timer or adjust its duration.
[0045] In some embodiments, the UE may select a value for a specific timer that may be started with an uplink transmission, or stop a running timer even before the running timer expires. The UE may select a timer value using delay information of data units in the LCH buffer or a deadline associated with a PDU stored in the HARQ buffer.
[0046] The network may configure N timer values or remaining times for delivery of a PDU. When a UL PDU is scheduled for transmission, the UE may select the remaining time or timer value from the N values configured for the PDU. The UE may multiplex uplink control information (UCI) including a field indicating the selected value. The selected value may indicate when the UL PDU is considered "outdated" or when a timer started for the UL PDU (e.g., a CG timer or a DRX timer) will stop or expire.
[0047] The embodiments and examples are applicable to sidelink communications. The DRX timer may be a sidelink-specific DRX timer, such as drx-RetransmissionTimerSL or drx-HARQ-RTT-TimerSL. Similarly, the embodiments may be applicable to a CG retransmission timer, such as cg-RetransmissionTimer, or a CG short data transfer (SDT) retransmission timer, such as cg-SDT-RetransmissionTimer.
[0048] Figure 2 A timing diagram 200 is shown according to some embodiments. Timing diagram 200 is an example of CG 240. CG 240 may include multiple CGs 250-1:4 (collectively referred to as CG 250) and CGs 260-1:3 (collectively referred to as CG 260). CG 250 may include time and frequency resources that share the same HARQ PID (e.g., HARQ PID=0) for PUSCH transmission. CG 260 may include time and frequency resources that share the same HARQ PID (HARQ PID=1) for a subset of CGs. CG 250 may have a different HARQ PID from CG 260.
[0049] The UE may send a PUSCH transmission within CG 250-1. The transmitted packet may be associated with the CG 250-1 HARQ process (e.g., HARQ PID=0) and may be stored in a HARQ buffer. In a conventional system, a PUSCH transmission may trigger the UE to start a CG timer. The CG timer may be associated with the PUSCH transmission and the HARQ PID of the PUSCH transmission. For example, in the case of a PUSCH transmission on CG 250-1 at 210, the UE may start the CG timer at time marker 210 or at any time between time markers 210 and 220. Wherein time marker 210 may be a time associated with the first OFDM symbol, and time marker 220 may be a time associated with the last OFDM symbol of the PUSCH transmission. The CG timer may be associated with the HARQ PID of CG 250-1. While the CG timer associated with the HARQ process is running, the UE may not use the CG resources associated with the same HARQ PID. For example, consider a PUSCH transmission within CG 250-1. The PUSCH transmission may trigger a CG timer at 210. The CG timer may expire at 216. When the CG timer is running between 210 and 216, the UE may not use UL grants associated with the same HARQ PID as CG 250-1 (e.g., HARQ PID=0). Therefore, because the CG timer is running and CGs 250-2 and 250-3 have the same HARQ PID as CG 250-1, CGs 250-2 and 250-3 may not be used for UL transmission. However, once the CG timer expires at 216, CG 250-4 may be used for PUSCH transmission.
[0050] The UE may use CG 260 for UL transmissions even if the CG timer for PUSCH transmission at 210 is running. Because CG 260 is associated with a HARQ PID that is different from the HARQ PID associated with the CG timer and CG 250-1. Consider that the UE sends a UL PUSCH transmission on CG 260-1 at time mark 220. The UE may start a second CG timer associated with CG 260-1 and its HARQ PID. While the second timer is running, the UE may not use the UL granted resources associated with the HARQ PID associated with CG 260-2 (i.e., HARQ PID=1). Therefore, the UE may not send a PUSCH transmission associated with HARQ PID=1 at CG 260-2 or 260-3.
[0051] In another example, consider the above example of a PUSCH transmission at 210. The PDU transmitted at 210 may be stored in a HARQ buffer associated with HARQ PID=0. At 242, the UE may determine that a data unit from the LCH has been queued for a long time and is critical for the data to be transmitted. However, the UE may not use a subsequent CG with HARQ PID=0 because the associated CG timer is still running.
[0052] In another example, consider the above example of a PUSCH transmission at 210. The PDU transmitted at 210 may be stored in a HARQ buffer associated with HARQ PID = 0. At 244, the UE may determine that the delivery deadline for the PDU transmitted at 210 has been reached and the BS has not requested a retransmission. A CG timer running beyond 244 may unnecessarily block the CG associated with HARQ PID = 0.
[0053] In one embodiment, the UE may check whether the CG timer associated with the HARQ process of the CG is running. If the CG timer is not running, the UE delivers an uplink grant to the HARQ entity for further processing. Otherwise, if the CG timer is running, for example, the uplink transmission on the CG has the CG timer enabled, the corresponding transmitted PDU is stored in the HARQ buffer. The UE may evaluate whether at least one of the following conditions is met.
[0054] The first condition is met when the amount of data from the LCH of the CG that can be mapped to the radio link control (RLC) buffer exceeds the capacity threshold. The network can configure the capacity threshold. For example, the BS can send a radio resource control (RRC) message to configure the capacity threshold. The capacity threshold can be zero.
[0055] The second condition is met when the buffer delay of data from at least one LCH that can be mapped to the CG exceeds the delay threshold. The network can configure the delay threshold. For example, the BS can send an RRC message to configure the delay threshold.
[0056] The third condition is met when the remaining time before the delivery deadline of data from at least one LCH that can be mapped to the CG exceeds the time threshold. The network can configure the time threshold. For example, the BS can send an RRC message to configure the delay threshold.
[0057] The fourth condition is met when data from at least one LCH that can be mapped to the CG is considered urgent or critical. A parameter can be associated with the data or LCH to indicate the degree of urgency.
[0058] The fifth condition is met when data from at least one LCH that can be mapped to the CG belongs to a PDU set with an importance level above or below the importance threshold. A parameter can be associated with the data, the corresponding PDU set, or the LCH to indicate the importance level. The network can configure the importance threshold. For example, the BS can send an RRC message to configure the importance threshold.
[0059] The sixth condition is satisfied when the LCH that can be mapped to the CG has a priority higher than the priority threshold. The network can configure the priority threshold. For example, the BS can send an RRC message to configure the priority threshold.
[0060] The seventh condition is met when the buffer delay of data from at least one LCH mapped to the transmitted PDU stored in the HARQ buffer exceeds the delay threshold. The network may configure the delay threshold. For example, the BS may send an RRC message to configure the delay threshold. The delay may be the amount of time that the data has arrived from the upper layer or the amount of time that the data has been stored in the HARQ buffer.
[0061] The eighth condition is met when the remaining time before the delivery deadline of data from at least one LCH mapped to the transmitted PDU stored in the HARQ buffer is less than the time threshold. The network can configure the time threshold. For example, the BS can send an RRC message to configure the time threshold.
[0062] The ninth condition is met when the delivery deadline of data from at least one LCH mapped to the transmitted PDU stored in the HARQ buffer - or other data associated with the data, such as data in the same PDU set - has passed. The network may configure the delivery deadline or may be defined in the 3GPP Technical Specification (TS). For example, the BS may send an RRC message to configure the delivery deadline. The delivery deadline may be implicitly indicated by the discard timer value configured for the data radio bearer of the LCH.
[0063] The tenth condition is satisfied when data from at least one LCH mapped to the transmitted PDU stored in the HARQ buffer belongs to a set of PDUs whose importance level is higher or lower than the importance threshold. The network may configure the importance threshold. For example, the BS may send an RRC message to configure the importance threshold.
[0064] If one or more of the above ten conditions are met, the UE may deliver the CG to the HARQ entity for further processing. When an uplink grant is delivered to the HARQ entity, this may mean that the HARQ entity may use the resources specified in the UL grant to transmit data. When an uplink grant is delivered to the HARQ entity for a new transmission, the UE may multiplex uplink control information (UCI) with the new transmission. The UCI may notify the BS that the new transmission overwrites the HARQ process. The BS may refresh the soft buffer corresponding to the HARQ process. The UE may send UCI via a separate control channel on the same or different component carriers. For example, the UE may multiplex UCI with a new transmission on the PUSCH, or send UCI on the physical uplink control channel (PUCCH). With the new transmission, the UE may restart the CG timer.
[0065] In another embodiment, the BS may receive delay information for a specific LCH. For example, the BS may receive a BSR with delay information. The BS may also receive information about CG resources used to transmit data from the LCH. For example, the BS may configure LCH mapping restrictions to the UE. The BS may receive a PDU corresponding to the LCH on resources associated with the CG. The BS may successfully decode the PDU and determine that retransmission of the PDU stored in the UE's HARQ buffer and the BS's soft buffer is unnecessary. If retransmission is no longer required, the BS may provide a dynamic grant (DG) for a new transmission associated with the same HARQ process as the received PDU. The DG may have an explicit indication that the UE refreshes the HARQ buffer, stops running the CG timer associated with the PDU, or stops the DRX-related timer. The UE receives the DG and may refresh the HARQ buffer or stop running the CG timer corresponding to the HARQ process.
[0066] In one embodiment, the network may configure one or more CG timer values to the UE. The CG timer value may determine how long the CG timer should run. The UE may select the CG timer value for uplink transmission based on the buffer delay information of the data to be transmitted in the PDU.
[0067] In one embodiment, the UE may be configured to determine the CG timer value when a particular LCH or MAC CE is multiplexed into a PDU for uplink transmission. When the PDU does not include data from a particular LCH or when the PDU does not include any user data (e.g., only a padding BSR MAC CE is included in the PDU), the UE may select a default CG timer value.
[0068] In one embodiment, the UE may be configured to determine the CG timer value when a condition of the buffer status of a particular LCH multiplexed into a PDU for uplink transmission is met. The buffer status may include buffer size, buffer delay, remaining time before a deadline, or the presence of data for an important PDU set.
[0069] In one embodiment, the UE may select the CG timer value based on the maximum or minimum buffer delay among all data units (e.g., MAC SDUs) or a subset of data units multiplexed into the PDU.
[0070] In one embodiment, the UE may select the CG timer value based on the minimum or maximum remaining time before the deadline among all data units (e.g., MAC SDUs) or a subset of data units multiplexed into the PDU.
[0071] In one embodiment, the UE may select the CG timer value based on the presence or amount of urgent or critical data units (e.g., MAC SDUs) among all data units or a subset of data units multiplexed into the PDU.
[0072] In one embodiment, the UE may select the CG timer value based on the corresponding LCH priority of all data units (eg, MAC SDUs) or a subset of data units multiplexed into the PDU. The corresponding LCH is the LCH whose data is multiplexed into the PDU.
[0073] In one embodiment, the UE may select a CG timer value based on the corresponding PDU set importance of all data units (e.g., MAC SDUs) or a subset of data units multiplexed into a PDU.
[0074] In one embodiment, the UE may select a CG timer value equal to zero, which is equivalent to not starting the CG timer with the transmission of the PDU.
[0075] In one embodiment, the UE may transmit a PDU, store the PDU in a corresponding HARQ buffer, and start a CG timer associated with the HARQ process. The UE may be prohibited from using CG resources with the same HARQ process to prevent the UE from overwriting the PDU stored in the HARQ buffer, as the stored PDU may be needed for retransmission. While the CG timer is still running, the delivery deadline of the data in the stored PDU may be reached, such as exceeding the packet delay budget of the data. The UE may stop the running CG timer based on the delay information of the data in the stored PDU.
[0076] In one embodiment, the UE may be configured to stop a running CG timer earlier than its default expiration time when a particular LCH or MAC CE is multiplexed into a stored PDU. If the stored PDU does not include any data from a particular LCH, the UE may not stop the running CG timer in advance before it expires. For example, if a particular LCH or MAC CE is multiplexed, the UE may receive an RRC configuration that enables the UE to stop the running timer in advance. Alternatively or additionally, the UE may stop the running CG timer based on the state of another timer (e.g., a DRX timer) associated with the HARQ process of the corresponding HARQ buffer. For example, the CG timer may be stopped when a DRX timer associated with the same HARQ process stops or expires.
[0077] The UE may evaluate whether at least one of the following conditions is met. If one or more of the following conditions are met, the UE may stop the running CG timer.
[0078] The first condition is met when a delivery deadline of at least one of the data units in the stored PDU (eg, all data units or a subset of data units) has been reached.
[0079] The second condition is met when the remaining time before the delivery deadline of at least one of the data units in the stored PDU (e.g., all data units or a subset of data units) is shorter than the deadline threshold. The network may configure the deadline threshold. For example, the BS may send a radio resource control (RRC) message to configure the deadline threshold.
[0080] The third condition is met when the shortest remaining time before the delivery deadline among all data units or data unit subsets in the stored PDU is shorter than the remaining time threshold. The network can configure the remaining time threshold. For example, the BS can send a radio resource control (RRC) message to configure the remaining time threshold.
[0081] The fourth condition is met when the stored PDUs do not include any data from any significant PDU set of at least one of the LCHs or data radio bearers (DRBs) (eg, all LCHs or DRBs, or a subset of the LCHs or DRBs).
[0082] The fifth condition is met when the DRX timer associated with the HARQ process of the stored PDU stops or expires.
[0083] Figure 3 A timing diagram 300 according to some embodiments is shown. At 310, the UE receives DCI on the PDCCH during a DRX on cycle, and the UE may need to remain active for possible UL transmissions or downlink (DL) transmissions. The UE may start a timer to track the time during which the UE remains active and monitors the PDCCH. In one example, the UE may not enter DRX inactive mode as long as the activity timer is running. For example, a drx-InactivityTimer keeps the UE in an active state after receiving the DCI. The UE may remain in an active state and monitor the PDCCH until the drx-InactivityTimer expires.
[0084] The received DCI may be associated with an UL transmission. For example, the DCI may include an UL grant, and the UE may transmit data on the PUSCH based on the UL grant. At time marker 320, the UE starts an uplink transmission (e.g., a PUSCH transmission), which may continue until 340. The UE may enter a DRX off cycle at 330.
[0085] After the UE makes an UL transmission, at 340, the BS may take some time to process the UL transmission and send a retransmission request. In some instances, the time required to receive, process, and respond to an UL (or DL) transmission may be referred to as a round trip time (RTT). The UE may not expect to receive DCI from the BS during this time. The UE may start a round trip time (RTT) timer that tracks the time during which the UE may not expect to receive DCI from the BS after the UL transmission. When the round trip timer is running, if the DRX on timer (e.g., drx-onDurationTimer) expires, the UE may enter a DRX inactive mode. Similarly, when the round trip timer is running, if the UE is in a DRX inactive mode, the UE may remain in this state. For example, the UE may start a drx-HARQ-RTT-TimerUL timer after the UL transmission at 340 to track the round trip time. The UE may expect to receive a retransmission request from the BS after the drx-HARQ-RTT-TimerUL expires at 350. Therefore, if the UE performs UL transmission during the DRX off cycle, the UE may remain in the DRX off cycle until the drx-HARQ-RTT TimerUL expires (or until the next DRX on cycle begins). When drx-HARQ-RTT-TimerUL expires, if the UE is still in the DRX off cycle, the UE may interrupt the DRX off cycle and monitor the PDCCH for potential retransmission requests from the BS.
[0086] Once the round trip timer expires, at 350, the UE may begin monitoring the PDCCH for potential retransmission requests from the BS. Even if the UE is in DRX inactive mode, the UE may transition to an active state and begin monitoring the PDCCH when the round trip timer expires. The UE may start a retransmission timer to track the time when the UE should monitor the PDCCH for retransmission requests associated with UL transmissions. For example, when the drx-HARQ-RTT-TimerUL expires at 350, the UE may start a drx-RetransmissionTimerUL, which tracks the duration required for the UE to monitor the PDCCH. When the drx-RetransmissionTimerUL expires at 360, if the DRX off cycle (monitored by another timer) has not expired, the UE may enter (or re-enter) the DRX inactive mode.
[0087] In one embodiment, the network may configure one or more DRX timer values to the UE. The DRX timer value may determine how long the DRX timer should run. The UE may select a DRX timer value based on buffer delay information of the data to be transmitted in the PDU. The DRX timer may be a DRX retransmission timer (e.g., drx-retransmissionTimerUL) or a DRX RRT timer (e.g., drx-HARQ-RTT-TimerlUL). In one example, the UE may select a DRX timer value equal to zero, which is equivalent to not starting a DRX timer with the transmission of the PDU.
[0088] In one embodiment, the UE may be configured to determine the DRX timer value when a specific LCH or MAC CE is multiplexed into a PDU for uplink transmission. When the PDU does not include data from a specific LCH or when the PDU does not include any user data (e.g., only a filler BSR MAC CE is included in the PDU), the UE may select a default DRX timer value.
[0089] In one embodiment, the UE may be configured to determine the DRX timer value when a condition of the buffer status of a particular LCH multiplexed into a PDU for uplink transmission is met. The buffer status may include buffer size, buffer delay, remaining time before a deadline, or the presence of data in an important PDU set.
[0090] In one embodiment, the UE may select the DRX timer value based on the maximum or minimum buffer delay among all data units (eg, MAC SDUs) or a subset of data units multiplexed into a PDU.
[0091] In one embodiment, the UE may select the DRX timer value based on the minimum or maximum remaining time before a deadline among all data units (eg, MAC SDUs) or a subset of data units multiplexed into a PDU.
[0092] In one embodiment, the UE may select a DRX timer value based on the presence or amount of urgent or critical data units (eg, MAC SDUs) among all data units or a subset of data units multiplexed into the PDU.
[0093] In one embodiment, the UE may select a DRX timer value based on the corresponding LCH priority of all data units (eg, MAC SDUs) or a subset of data units multiplexed into the PDU. The corresponding LCH is the LCH whose data is multiplexed into the PDU.
[0094] In one embodiment, the UE may select a DRX timer value based on the corresponding PDU set importance of all data units (eg, MAC SDUs) or a subset of data units multiplexed into a PDU.
[0095] In one embodiment, the UE may transmit a PDU, start a DRX timer, and store the PDU in a corresponding HARQ buffer. The UE may stop a running DRX timer based on the delay information of the data in the stored PDU. Alternatively or additionally, the UE may stop a running DRX timer based on the state of another timer (e.g., a CG timer) associated with a HARQ process of the corresponding HARQ buffer. For example, the DRX timer may be stopped when a CG timer associated with the same HARQ process stops or expires. When the DRX timer stops, the UE may terminate a DRX active mode or enter a DRX inactive mode.
[0096] In one embodiment, the UE may be configured to stop a running DRX timer when a particular LCH or MAC CE is multiplexed into a stored PDU. If the stored PDU does not include any data from a particular LCH, the UE may not stop the running DRX timer prematurely before it expires. For example, the UE may receive an RRC configuration that enables the UE to stop the running DRX timer.
[0097] The UE may evaluate whether at least one of the following conditions is met. If one or more of the following conditions are met, the UE may stop the running DRX timer earlier than its default expiration time. The running DRX timer may be a DRX retransmission timer or a DRX HARQ RTT timer.
[0098] The first condition is met when a delivery deadline of at least one of the data units in the stored PDU (eg, all data units or a subset of data units) has been reached.
[0099] The second condition is met when the remaining time before the delivery deadline of at least one of the data units in the stored PDU (e.g., all data units or a subset of data units) is shorter than the deadline threshold. The network may configure the deadline threshold. For example, the BS may send a radio resource control (RRC) message to configure the deadline threshold.
[0100] The third condition is met when the shortest remaining time before the delivery deadline among all data units or data unit subsets in the stored PDU is shorter than the remaining time threshold. The network can configure the remaining time threshold. For example, the BS can send a radio resource control (RRC) message to configure the remaining time threshold.
[0101] The fourth condition is met when the stored PDUs do not include any data from any significant PDU set of at least one of the LCHs or data radio bearers (DRBs) (eg, all LCHs or DRBs, or a subset of the LCHs or DRBs).
[0102] The fifth condition is met when the CG timer associated with the HARQ process of the stored PDU stops or expires.
[0103] In one embodiment, if the UE stops a DRX HARQ RTT timer (eg, drx-HARQ-RTT-TimerUL) before it expires, the UE may also refrain from starting a subsequent DRX retransmission timer (eg, drx-RetransmissionTimerUL).
[0104] Figure 4 An operational flow / algorithm structure 400 according to some embodiments is shown. The operational flow / algorithm structure 400 is an example of a method to be implemented by a UE to deliver a CG to a corresponding HARQ process. The operational flow / algorithm structure 400 may be implemented by a UE (e.g., UE 104, UE 800) or a component thereof (e.g., processor 804).
[0105] The operational flow / algorithm structure 400 may include: At 404, receiving a configuration related to processing an uplink grant. The UE may receive a configuration that enables the UE to deliver an uplink grant to a HARQ entity based on a condition of delay information of a data unit. The data unit may be associated with the last transmission whose PDU was stored in the HARQ buffer or associated with an upcoming transmission. Delivering the uplink grant to the HARQ entity may override the HARQ process and ignore the running timer, thereby preventing the UE from delivering the UL grant to the HARQ entity.
[0106] The operational flow / algorithm structure 400 may include, at 406, processing a CG. The CG may be associated with a HARQ PID. In one example, the operational flow / algorithm structure 400 may include, at 406, processing a UL grant, such as a dynamic grant or a CG.
[0107] The operational flow / algorithm structure 400 may include, at 408, determining whether a CG timer associated with the HARQ process of the CG is running. A running CG timer may indicate that there has been an UL transmission on the CG associated with the same HARQ PID and that the corresponding PDU is stored in the HARQ buffer. If the CG timer associated with the HARQ process of the CG is not running, the operational flow / algorithm structure 400 may proceed to 410. However, if the CG timer associated with the HARQ process of the CG is running, the operational flow / algorithm structure 400 may proceed to 412.
[0108] The operational flow / algorithm structure 400 may include delivering the CG to the HARQ entity at 410. When there is no running CG timer associated with the HARQ process, the CG resources are available for UL transmission and the UE may deliver the CG to the HARQ entity.
[0109] The operation flow / algorithm structure 400 may include: at 412, determining whether a condition related to delay information of a data unit in the HARQ buffer is met. The condition of the delay information of the data unit may include: the amount of data from the logical channel associated with the CG is greater than the capacity threshold, the buffer delay of the data from the logical channel associated with the CG is greater than the delay threshold; the remaining time before the delivery deadline of the data from the logical channel associated with the CG is less than the time threshold; the data from the logical channel associated with the CG is urgent data; the data from the logical channel associated with the CG is associated with a set of packet data units (PDUs) with an importance level greater than the importance threshold; the priority of the logical channel associated with the CG is greater than the priority threshold; or the delivery deadline of the data from the logical channel associated with the CG expires. If the condition related to the delay information of the data unit is not met, the operation flow / algorithm structure 400 may proceed to 414. However, if the condition related to the delay information of the data unit is met, the operation flow / algorithm structure 400 may proceed to 416.
[0110] The operational flow / algorithm structure 400 may include: at 414, delivering the CG to the HARQ entity.
[0111] The operational flow / algorithm structure 400 may include: at 416, not delivering the CG to the HARQ entity.
[0112] Figure 5An operational flow / algorithm structure 500 according to some embodiments is shown. The operational flow / algorithm structure 500 is an example of a method to be implemented by a BS to rewrite a HARQ process at a UE based on the UE's delay information. The operational flow / algorithm structure 500 may be implemented by a BS (e.g., BS 108, BS 900, or a component thereof (e.g., processor 904)).
[0113] The operational flow / algorithm structure 500 may include: at 504, receiving delay information of the LCH, wherein the LCH is associated with the CG.
[0114] The operational flow / algorithm structure 500 may include receiving a transmission of data including an LCH, at 506. The transmission may be associated with a HARQ PID and indicate that a CG timer associated with the CG is running at the UE.
[0115] The operational flow / algorithm structure 500 may include, at 508, determining whether retransmission is required. The BS may decode the received data. Successful decoding of the received data may not require retransmission of the data by the UE. However, if the BS cannot decode the received data, the BS may request the UE to retransmit the data. If the BS determines that retransmission is required, the flow / algorithm structure 500 proceeds to 510. If the BS determines that retransmission is not required, the flow / algorithm structure 500 proceeds to 512.
[0116] The operation flow / algorithm structure 500 may include, at 510, sending a retransmission request to the UE.
[0117] The operational flow / algorithm structure 500 may include sending a dynamic grant associated with the HARQ PID and an indication to ignore a timer associated with the CG or a timer associated with the HARQ PID at 512. The dynamic grant may include instructions to stop a timer associated with the CG or the HARQ PID.
[0118] Figure 6 An operational flow / algorithm structure 600 according to some embodiments is shown. The operational flow / algorithm structure 600 is an example of a method to be implemented by a UE to select a timer value based on buffer delay information. The operational flow / algorithm structure 600 may be implemented by a UE (e.g., UE 104, UE 800) or a component thereof (e.g., processor 804).
[0119] The operation flow / algorithm structure 600 may include receiving a configuration related to selecting a timer value for UL transmission at 604. The UE may receive a configuration that enables the UE to select a timer value based on delay information or conditions of a data unit. The data unit may be associated with an upcoming transmission. The timer value may be associated with a CG timer or a DRX-related timer (e.g., a DRX HARQ RTT timer or a DRX retransmission timer).
[0120] The operational flow / algorithm structure 600 may also include generating a PDU for UL transmission at 606. The PDU may include one or more data units.
[0121] The operational flow / algorithm structure 600 may include, at 608, determining whether a condition for selecting a timer value is satisfied. When the condition is not satisfied, the operational flow / algorithm structure 600 proceeds to 610. If the condition is satisfied, the operational flow / algorithm structure 600 proceeds to 612. The conditions include: the PDU includes data from a first LCH; the PDU includes emergency data; the PDU includes data from a second LCH having a priority greater than a priority threshold; or an importance level associated with the PDU is greater than an importance threshold.
[0122] The operational flow / algorithm structure 600 may include selecting a default timer value at 610. The UE may select a timer value from one or more values configured by the BS.
[0123] The operation flow / algorithm structure 600 may include, at 612, selecting a timer value based on delay information of the data units in the PDU. The delay information may include a maximum or minimum buffer delay of the data units in the PDU or a minimum or maximum remaining time before a deadline of the data units in the PDU. The operation flow / algorithm structure 600 may proceed from 610 or 612 to 614.
[0124] The operational flow / algorithm structure 600 may include, at 614, starting or restarting a timer after a UL transmission.
[0125] Figure 7 An operational flow / algorithm structure 700 according to some embodiments is shown. The operational flow / algorithm structure 700 is an example of a method to be implemented by a UE to stop a timer based on buffer delay information of a stored PDU. The operational flow / algorithm structure 700 may be implemented by a UE (e.g., UE 104, UE 800) or a component thereof (e.g., processor 804).
[0126] The operation flow / algorithm structure 700 may include: At 704, receiving a configuration related to selecting a timer value for UL transmission. The UE may receive a configuration that enables the UE to stop the timer based on a condition or delay information of the data unit. The data unit may be associated with a PDU stored in a HARQ buffer. The timer may be a CG timer or a DRX related timer, such as a DRX HARQ RTT timer or a DRX retransmission timer.
[0127] The operation flow / algorithm structure 700 may also include generating a PDU for UL transmission at 706. The PDU may be created by multiplexing one or more data units, and each data unit may be associated with an LCH. The UE may transmit the PDU in an uplink transmission, start a timer associated with the uplink transmission, and store the PDU in a HARQ buffer.
[0128] The operational flow / algorithm structure 700 may include, at 708, determining whether the stored PDU includes data from a specific LCH. The UE may be configured with an indication of the specific LCH. For example, the UE may receive an RRC message including an indication of the specific LCH. If the stored PDU includes data from the specific LCH, the operational flow / algorithm structure 700 proceeds to 710. If the stored PDU does not include data from the specific LCH, the operational flow / algorithm structure 700 proceeds to 712.
[0129] The delay information may include a delivery deadline of a data unit in one or more data units in the PDU; a remaining time before the delivery deadline of a data unit in the one or more data units in the PDU; or the shortest longest remaining time before the delivery deadline of a data unit in one or more data units in the PDU.
[0130] The operational flow / algorithm structure 700 may include, at 710, not stopping a running timer.
[0131] The operational flow / algorithm structure 700 may include, at 712, determining whether a condition for stopping the timer is met. The condition may include that the stored PDU does not include a data unit from a particular LCH, or that a data unit in one or more data units is not associated with a set of PDUs having an importance level less than a threshold or is not associated with an importance level. If the condition for stopping the timer is met, the operational flow / algorithm structure 700 proceeds to 716. If the condition for stopping the timer is not met, the operational flow / algorithm structure 700 proceeds to 714.
[0132] The operational flow / algorithm structure 700 may include, at 714, continuing the timer to run.
[0133] The operational flow / algorithm structure 700 may also include, at 716, stopping the timer.
[0134] Figure 8 UE 800 according to some embodiments is shown. UE 800 may be similar to Figure 1 UE 104 and is substantially interchangeable therewith.
[0135] UE 800 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a camcorder), a wearable device (e.g., a smart watch), or an IoT device.
[0136] UE 800 may include a processor 804, an RF interface circuit 808, a memory / storage device 812, a user interface 816, a sensor 820, a driver circuit 822, a power management integrated circuit (PMIC) 824, an antenna structure 826, and a battery 828. The components of UE 800 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Figure 8 The block diagram of UE 800 is intended to show a high-level view of certain of the components of UE 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.
[0137] Components of the UE 800 may be coupled to various other components via one or more interconnects 832, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connection that allows various circuit components (on a common or different chip or chipset) to interact with each other.
[0138] The processor 804 may include processor circuits such as a baseband processor circuit (BB) 804A, a central processor unit circuit (CPU) 804B, and a graphics processor unit circuit (GPU) 804C. The processor 804 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 812) to cause the UE 800 to perform operations as described herein.
[0139] Processor 804 may perform operations associated with selecting timer values and starting or stopping CG-related or DRX-related timers consistent with the embodiments described herein.
[0140] In some embodiments, the baseband processor circuit 804A can access the communication protocol stack 836 in the memory / storage device 812 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 804A can access the communication protocol stack 836 to perform the following operations: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer and NAS layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 808.
[0141] The baseband processor circuit 804A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
[0142] The memory / storage device 812 may include one or more non-transitory computer-readable media, which include instructions (e.g., communication protocol stack 836) that can be executed by one or more processors in the processor 804 to enable the UE 800 to perform various operations described herein. The memory / storage device 812 includes any type of volatile or non-volatile memory that can be distributed throughout the UE 800. In some embodiments, some of the memory / storage devices in the memory / storage device 812 may be located on the processor 804 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 812 are located outside the processor 804, but can be accessed via a memory interface. The memory / storage device 812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.
[0143] The RF interface circuit 808 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 800 to communicate with other devices through a radio access network. The RF interface circuit 808 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, and control circuits.
[0144] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 826 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 804.
[0145] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 826.
[0146] In various embodiments, the RF interface circuit 808 may be configured to transmit / receive signals in a manner compatible with NR access technology.
[0147] Antenna 826 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 826 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input / multiple output communications. Antenna 826 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, or a phased array antenna. Antenna 826 may have one or more panels designed for a specific frequency band (including a frequency band in FR1 or FR2).
[0148] The user interface circuit 816 includes various input / output (I / O) devices designed to enable the user to interact with the UE 800. The user interface 816 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual device for accepting input, especially including one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, (multiple) actuator positions or other similar information). The output device circuit may include any number or combination of audio or visual displays, especially including one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs) and multi-character visual outputs) or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 800.
[0149] Sensors 820 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.
[0150] The driver circuit 822 may include software elements and hardware elements for controlling a specific device embedded in the UE 800, attached to the UE 800, or otherwise communicatively coupled to the UE 800. The driver circuit 822 may include various drivers, thereby allowing other components to interact with or control various I / O devices that may be present in the UE 800 or connected to the UE. For example, the driver circuit 822 may include a circuit for facilitating coupling a universal integrated circuit card (UICC) or a universal subscriber identity module (USIM) to the UE 800. For additional examples, the driver circuit 822 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining a sensor reading of the sensor circuit 820 and controlling and allowing access to the sensor circuit 820, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.
[0151] The PMIC 824 may manage the power provided to various components of the UE 800. Specifically, with respect to the processor 804, the PMIC 824 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.
[0152] In some embodiments, the PMIC 824 may control or otherwise be a part of various power saving mechanisms of the UE 800, including DRX, as discussed herein.
[0153] The battery 828 can power the UE 800, but in some examples, the UE 800 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 828 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 828 can be a typical lead-acid automobile battery.
[0154] Fig. 9 A network node 900 is shown according to some embodiments. The network node 900 may be similar to and substantially interchangeable with a base station 108, a device implementing one of the network hops, an integrated access and backhaul (IAB) node, a network controlled repeater, or a server in a core network or an external data network.
[0155] The network node 900 may include a processor 904 , RF interface circuitry 908 (if implemented as an access node), core network (CN) interface circuitry 912 , memory / storage circuitry 916 , and antenna structures 926 .
[0156] Components of network node 900 may be coupled to various other components via one or more interconnects 928 .
[0157] The processor 904, RF interface circuit 908, memory / storage circuit 916 (including communication protocol stack 910), antenna structure 926 and interconnect 928 may be similar to those of reference Figure 8 Like named elements are shown and described.
[0158] Processor 904 may perform operations associated with selecting a timer value to start or stop a CG-related or DRX-related timer consistent with the embodiments described herein.
[0159] The CN interface circuit 912 may provide a connection to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). The network connection may be provided to / from the network node 900 via optical fiber or wireless backhaul. The CN interface circuit 912 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 912 may include multiple controllers for providing connections to other networks using the same or different protocols.
[0160] In some embodiments, the network node 900 may be coupled to a transmit receive point (TRP) using an antenna structure 926, a CN interface circuit, or other interface circuitry.
[0161] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.
[0162] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.
[0163] Example
[0164] In the following sections, additional exemplary aspects are provided.
[0165] Embodiment 1 includes a method to be implemented by a user equipment (UE), the method comprising: receiving a configuration that enables the UE to deliver an uplink grant to a hybrid automatic repeat request (HARQ) entity based on a condition of delay information of a data unit; processing a configuration grant (CG) associated with a HARQ process identifier (HARQ PID); determining whether a CG timer associated with the HARQ PID is running; determining whether the condition of the delay information of the data unit is met; and determining whether to deliver the CG to the HARQ entity based on the determination of whether the condition of the delay information of the data unit is met.
[0166] Embodiment 2 includes a method according to embodiment 1 or some other embodiments of the present invention, wherein determining whether the condition of the delay information of the data unit is met includes: determining that the condition of the delay information of the data unit is met, and the method also includes: delivering the CG to the HARQ entity.
[0167] Embodiment 3 includes a method according to embodiment 1 or 2 or some other embodiments of the present invention, wherein the condition of the delay information of the data unit includes: the amount of data from the logical channel associated with the CG is greater than a capacity threshold; the buffer delay of the data from the logical channel associated with the CG is greater than a delay threshold; the remaining time before the delivery deadline of the data from the logical channel associated with the CG is less than a time threshold; the data from the logical channel associated with the CG is urgent data; the data from the logical channel associated with the CG is associated with a set of packet data units (PDUs) whose importance level is greater than an importance threshold; the priority of the logical channel associated with the CG is greater than a priority threshold; or the delivery deadline of the data from the logical channel associated with the CG expires.
[0168] Embodiment 4 includes a method according to any one of embodiments 1 to 3 or some other embodiments herein, wherein the data unit is a first data unit from the logical channel (LCH) or a second data unit associated with the LCH and stored in a buffer of the HARQ entity.
[0169] Embodiment 5 includes a method according to any one of embodiments 1 to 4 or some other embodiments herein, further comprising: sending uplink control information (UCI) to indicate that a HARQ process associated with the HARQ PID is overwritten.
[0170] Embodiment 6 includes a method according to any one of embodiments 1 to 5 or some other embodiments herein, wherein the configuration is included in a radio resource control (RRC) message.
[0171] Embodiment 7 includes a method to be implemented by a base station (BS), the method comprising: receiving delay information of a logical channel (LCH) from a user equipment (UE); receiving a transmission of data including the LCH from the UE, the transmission being associated with a hybrid automatic repeat request (HARQ) process identifier (ID); determining whether retransmission is required; and sending a dynamic grant associated with the HARQ PID to the UE, the dynamic grant comprising an indication of ignoring a timer associated with a configuration grant or a HARQ process associated with the HARQ PID.
[0172] Embodiment 8 includes the method according to embodiment 7 or some other embodiments herein, wherein the dynamic grant will include an instruction to flush the HARQ buffer associated with the HARQ PID.
[0173] Embodiment 9 includes a method according to embodiment 7 or 8 or some other embodiments herein, wherein the dynamic grant will include an instruction to stop the timer associated with the configuration grant or the HARQ PID.
[0174] Embodiment 10 includes a method to be implemented by a user equipment (UE), the method comprising: receiving a configuration that enables the UE to select a value of a timer based on a condition or buffer delay information of data to be transmitted via an uplink transmission; generating a packet data unit (PDU) for uplink transmission; and selecting the value of the timer based on the buffer delay information of the PDU.
[0175] Embodiment 11 includes a method according to embodiment 10 or some other embodiments herein, wherein the timer is a configuration grant timer, a discontinuous reception (DRX) retransmission timer for uplink, or a DRX round trip time timer for uplink.
[0176] Embodiment 12 comprises a method according to embodiment 10 or 11 or some other embodiments herein, wherein the configuration includes an indication of a first logical channel (LCH), and the condition includes the condition including: the PDU includes data from the first LCH; the PDU includes emergency data; the PDU includes data from a second LCH having a priority greater than a priority threshold; or an importance level associated with the PDU is greater than an importance threshold.
[0177] Embodiment 13 includes a method according to any one of embodiments 10 to 12 or some other embodiments herein, wherein the buffer delay information will include: the maximum or minimum buffer delay of the data unit in the PDU; or the minimum or maximum remaining time before the deadline of the data unit in the PDU.
[0178] Embodiment 14 includes the method according to any one of embodiments 10 to 13 or some other embodiments of the present invention, and also includes: receiving one or more timer values, wherein the selecting the value of the timer includes: selecting the value of the timer from the one or more timer values.
[0179] Embodiment 15 includes a method according to any one of embodiments 10 to 14 or some other embodiments herein, further comprising: generating an uplink control message including an indication of the value of the timer; and sending the uplink control message to a base station (BS).
[0180] Embodiment 16 includes a method of operating a user equipment (UE), the method comprising: receiving a configuration that enables the UE to stop a timer based on a condition or buffer delay information associated with a stored packet data unit (PDU); generating the PDU from one or more data units associated with an uplink transmission; transmitting the PDU in the uplink transmission; starting the timer; storing the PDU in a hybrid automatic repeat request (HARQ) buffer; and stopping the timer based on the buffer delay information of the one or more data units in the PDU.
[0181] Embodiment 17 includes a method according to embodiment 16 or some other embodiments herein, wherein the timer is a configuration grant timer, a discontinuous reception (DRX) retransmission timer for uplink, or a DRX round trip time timer for uplink.
[0182] Embodiment 18 comprises a method according to embodiment 16 or 17 or some other embodiments herein, wherein the configuration includes an indication of a logical channel (LCH), and the condition includes the condition including: the PDU includes a data unit from the LCH; or the data unit in one or more data units is associated with a set of PDUs whose importance level is less than a threshold or is not associated with the importance level.
[0183] Embodiment 19 includes a method according to any one of embodiments 16 to 18 or some other embodiments herein, wherein the buffer delay information will include: the delivery deadline of the data unit of the one or more data units in the PDU; the remaining time before the delivery deadline of the data unit of the one or more data units in the PDU; or the shortest remaining time before the delivery deadline of the data unit of the one or more data units in the PDU.
[0184] Embodiment 20 includes a method according to any one of embodiments 16 to 19 or some other embodiments herein, further comprising: generating an uplink control message including an indication to stop the timer; and sending the uplink control message to a base station (BS).
[0185] Another embodiment may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in accordance with or related to any of Embodiments 1 to 20, or any other method or process described herein.
[0186] Another embodiment may include a method, technique or process described or related to any one of Embodiments 1 to 20 or a portion or component thereof.
[0187] Another embodiment may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any one of Embodiments 1 to 20.
[0188] Another embodiment comprises a signal according to or in connection with any one of embodiments 1 to 20, or a portion or component thereof.
[0189] Another embodiment may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or related to any one of embodiments 1 to 20, or otherwise described in the present disclosure.
[0190] Another embodiment may include a signal encoded with data as described or related to any one of embodiments 1 to 20, or a portion or component thereof, or described in other ways in this disclosure.
[0191] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any of Embodiments 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.
[0192] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or portion thereof, described or related to any one of Embodiments 1 to 20.
[0193] Another embodiment may include a computer program including instructions, wherein execution of the program by the processing element will cause the processing element to perform a method, technique or process described or related to any one or part of Embodiments 1 to 20.
[0194] Another embodiment may include a signal in a wireless network as shown and described herein.
[0195]
[0013] Another embodiment may include a method of communicating in a wireless network as shown and described herein.
[0196]
[0013] Another embodiment may include a system for providing wireless communications as shown and described herein.
[0197]
[0013] Another embodiment may include an apparatus for providing wireless communications as shown and described herein.
[0198] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various aspects.
[0199] Although the above aspects have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.
Claims
1. A method, comprising: Processing a configuration that enables determining whether to deliver an uplink grant to a hybrid automatic repeat request (HARQ) entity based on a condition of delay information of a data unit; Processing a Configuration Grant (CG) associated with a HARQ Process Identifier (HARQ PID); determining whether a CG timer associated with the HARQ PID is running; determining whether the condition of the delay information of the data unit is satisfied; as well as Whether to deliver the CG to the HARQ entity is determined based on whether the condition of the delay information of the data unit is satisfied.
2. The method according to claim 1, wherein the determining whether the condition of the delay information of the data unit is satisfied comprises: determining the condition satisfying the delay information of the data unit, and the method further comprising: The CG is delivered to the HARQ entity.
3. The method according to claim 1, wherein the condition of the delay information of the data unit comprises: the amount of data from a logical channel associated with the CG is greater than a capacity threshold; a buffer delay of data from a logical channel associated with the CG is greater than a delay threshold; The remaining time before the delivery deadline of data from the logical channel associated with the CG is less than a time threshold; Data from a logical channel associated with the CG is emergency data; Data from a logical channel associated with the CG is associated with a set of packet data units (PDUs) having an importance level greater than an importance threshold; The priority of the logical channel associated with the CG is greater than the priority threshold; or The delivery deadline for data from the logical channel associated with the CG expires.
4. The method of claim 3, wherein the data unit is a first data unit from the logical channel (LCH) or a second data unit associated with the LCH and stored in a buffer of the HARQ entity.
5. The method according to claim 1, further comprising: Uplink control information (UCI) is generated to indicate that a HARQ process associated with the HARQ PID is overwritten.
6. The method according to any one of claims 1 to 5, wherein the configuration is included in a Radio Resource Control (RRC) message.
7. A method comprising: Processing delay information of a logical channel (LCH) received from a user equipment (UE); processing a transmission received from the UE including data of the LCH, the transmission being associated with a hybrid automatic repeat request (HARQ) process identifier (HARQ PID); determining whether retransmission is required; and A dynamic grant associated with the HARQ PID is generated for transmission to the UE, the dynamic grant including an indication to ignore a timer associated with a configuration grant or a HARQ process associated with the HARQ PID.
8. The method of claim 7, wherein the dynamic grant will include instructions to flush a HARQ buffer associated with the HARQ PID.
9. The method according to any one of claims 7 or 8, wherein the dynamic grant will include an instruction to stop the timer associated with the configuration grant or the HARQ PID.
10. A baseband processor, comprising: A processing circuit, the processing circuit being configured to: processing a configuration received from a base station that will enable selection of a value for the timer based on a condition or buffer delay information for data to be transmitted over an uplink; generating a packet data unit (PDU) for uplink transmission; as well as selecting the value of the timer based on the buffer delay information of the PDU or the condition; and Interface circuitry is provided for communicatively coupling the processing circuitry to components of a device.
11. The baseband processor of claim 10, wherein the timer is a configuration grant timer, a discontinuous reception (DRX) retransmission timer for uplink, or a DRX round trip time timer for uplink.
12. The baseband processor of claim 10, wherein the configuration comprises an indication of a first logical channel (LCH), and the condition comprises: The PDU includes data from the first LCH; The PDU includes emergency data; The PDU includes data from a second LCH with a priority greater than a priority threshold; or An importance level associated with the PDU is greater than an importance threshold.
13. The baseband processor of claim 10, wherein the buffer delay information comprises: the maximum or minimum buffer delay for data units in the PDU; or The minimum or maximum remaining time before the deadline of the data unit in the PDU.
14. The baseband processor of claim 10, wherein the processing circuit is further configured to: Receiving one or more timer values, wherein said selecting said value of said timer comprises: The value of the timer is selected from the one or more timer values.
15. The baseband processor according to any one of claims 10 to 14, wherein the processing circuit is further configured to: An uplink control message is generated including an indication of the value of the timer, the uplink control message being transmitted to a base station (BS).
16. One or more computer-readable media having instructions that, when executed, cause a processing circuit to: receiving a configuration that enables stopping a timer based on a condition or buffer delay information associated with a stored packet data unit (PDU); generating a PDU from one or more data units associated with an uplink transmission, the PDU to be transmitted to a base station (BA) in the uplink transmission; Starting the timer; storing the PDU in a hybrid automatic repeat request (HARQ) buffer; as well as The timer is stopped based on the buffer delay information of the one or more data units in the PDU.
17. The one or more computer-readable media of claim 16, wherein the timer is a configuration grant timer, a discontinuous reception (DRX) retransmission timer for uplink, or a DRX round trip time timer for uplink.
18. The one or more computer-readable media of claim 16, wherein the configuration comprises an indication of a logical channel (LCH), and the condition comprises: The PDU includes a data unit from the LCH; or The data unit of the one or more data units is associated with a set of PDUs having an importance level less than a threshold or is not associated with the importance level.
19. The one or more computer-readable media of claim 16, wherein the buffer delay information comprises: a delivery deadline of a data unit of the one or more data units in the PDU; the time remaining before a delivery deadline for the data unit of the one or more data units in the PDU; or A minimum or maximum remaining time before the delivery deadline of the data unit of the one or more data units in the PDU.
20. One or more computer-readable media according to any one of claims 16 to 19, wherein the instructions, when executed, further cause the processing circuit to: An uplink control message including an indication to stop the timer is generated, and the uplink control message is to be transmitted to a base station (BS).
