Method and apparatus for timely dispatching

Abstract

Embodiments of the present application relate to a method and apparatus for timely scheduling. The method may include: configuring DRX configuration information; and preventing a MAC entity from entering an inactive time in response to a first MAC PDU not being transmitted in an uplink grant.

Description

Technical Field

[0001] The present application relates generally to wireless communication techniques, and more particularly to methods and apparatus for timely scheduling of uplink transmissions. Background Art

[0002] In the field of mobile communications, discontinuous reception (DRX) refers to a working mode for saving power consumption of user equipment (UE). For example, in DRX mode, the UE alternates between an active state and a sleep state (or an inactive state). The UE turns on the receiver only when it is in an active state to monitor and receive control information or downlink data from the base station (BS), and turns off the receiver when it is in a sleep state to stop receiving control information or downlink data. Therefore, the transmission delay when the UE is in an inactive state may be disadvantageous for data transmission, especially for networks that require low latency, such as ultra-reliable and low-latency communication (URLLC) services.

[0003] URLLC is one of several different types of use cases supported by the 5G NR standard as specified by 3GPP (3rd Generation Partnership Project) Release 15 (R15). URLLC will provide a variety of advanced services for latency-sensitive connected devices, such as factory automation, autonomous driving, industrial Internet and smart grids or robotic surgery. Summary of the invention

[0004] Embodiments of the present application provide a method and apparatus for timely scheduling of uplink transmissions.

[0005] An embodiment of the present application provides a method. The method may include: configuring DRX configuration information; and preventing a medium access control (MAC) entity from entering an inactive time in response to a first MAC protocol data unit (PDU) not being transmitted in an uplink grant.

[0006] In an embodiment of the present application, the MAC entity is configured with priorityBasedPrioritization, and the uplink grant in which the first MAC PDU is not transmitted is a de-prioritized grant. In this case, the method may further include: transmitting a second MAC PDU in a prioritized uplink grant without transmitting the first MAC PDU. The prioritized uplink grant is a configured grant. The de-prioritized uplink grant is received on a physical downlink control channel (PDCCH) and is addressed to a configured scheduling-radio network temporary identifier (CS-RNTI), and a hybrid automatic repeat request (HARQ) buffer of the identified process is not empty, or the de-prioritized uplink grant is a configured grant.

[0007] In an embodiment of the present application, the first MAC PDU is not transmitted in the uplink grant because listen-before-talk (LBT) fails after receiving downlink control information (DCI) indicating the uplink grant for retransmission.

[0008] In an embodiment of the present application, the DRX configuration information includes a value of drx-RetransmissionTimerUL, wherein preventing the MAC entity from entering the inactive time may include: starting the drx-RetransmissionTimerUL for the HARQ process of the second MAC PDU or the first MAC PDU.

[0009] In an embodiment of the present application, the DRX configuration information includes the value of drx-HARQ-RTT-TimerUL, wherein preventing the MAC entity from entering inactive time may include: updating and starting the drx-HARQ-RTT-TimerUL for the HARQ process of the second MAC PDU; or updating and / or starting the drx-HARQ-RTT-TimerUL for the HARQ process of the first MAC PDU.

[0010] In an embodiment of the present application, updating the drx-HARQ-RTT-TimerUL may include: setting the value of the drx-HARQ-RTT-TimerUL used for the HARQ process to a value less than the value of the drx-HARQ-RTT-TimerUL included in the DRX configuration information or to a value of "0".

[0011] In an embodiment of the present application, updating the drx-HARQ-RTT-TimerUL may include: updating the value of the drx-HARQ-RTT-TimerUL for the HARQ process using a differential value. In an embodiment, the value of the drx-HARQ-RTT-TimerUL for the HARQ process is updated using the value of the drx-HARQ-RTT-TimerUL-the differential value.

[0012] In an embodiment of the present application, the DRX configuration information includes a value for a new round trip time (RTT) timer, wherein the new RTT timer is configured according to the HARQ process and indicates the minimum duration before the MAC entity expects an uplink HARQ retransmission grant.

[0013] In an embodiment of the present application, the DRX configuration information includes a value of a new timer, wherein the activity time includes a time during which the new timer runs.

[0014] In an embodiment of the present application, an indication for enabling the method is added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI is added, or an additional bit is added to the current DCI.

[0015] Another embodiment of the present application provides an apparatus. The apparatus may include at least one non-transitory computer-readable medium having computer-executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver, and the at least one transmitter. The computer-executable instructions are programmed to implement the above method using the at least one receiver, the at least one transmitter, and the at least one processor.

[0016] Embodiments of the present application can effectively speed up retransmissions to handle de-prioritized uplink transmissions, especially when the de-prioritized MAC PDU is used for URLLC services. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to describe the manner in which the advantages and features of the present application are obtained, the description of the present application is presented by referring to specific embodiments of the present application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered as limiting the scope thereof.

[0018] Figure 1 A wireless communication system according to some embodiments of the present application is described;

[0019] Figure 2 An exemplary scenario of a failed scheduling of a de-prioritized MAC PDU according to some embodiments of the present application is described;

[0020] Figure 3 Another exemplary scenario illustrating failed scheduling of URLLC retransmissions on unlicensed spectrum (NR-U) according to some embodiments of the present application;

[0021] Figure 4 is a flow chart illustrating a method for timely scheduling of uplink switching according to some embodiments of the present application; and

[0022] Figure 5 Devices according to some embodiments of the present application are described. DETAILED DESCRIPTION

[0023] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be implemented by different embodiments, which are intended to be included in the spirit and scope of the present application.

[0024] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings.

[0025] Figure 1 A wireless communication system 100 according to some embodiments of the present application is illustrated.

[0026] refer to Figure 1 , the wireless communication system 100 may include a UE 101 and a BS 102. Figure 1 A specific number of UEs 101 and BSs 102 are depicted in FIG. 1 , but it should be considered that additional UEs 101 and BSs 102 may be available in the wireless communication system 100 .

[0027] BS 102 may be distributed over a geographic area and may communicate with a core network (CN) node. In some embodiments of the present application, BS 102 may also be referred to as an access point, access terminal, base station, base unit, macro cell, Node-B, evolved Node B (eNB), gNB, home Node-B, relay node or device, or described using other terms used in the art. BS 102 is typically part of a radio access network, which may include one or more controllers communicatively coupled to one or more corresponding BSs 102.

[0028] UE 101 may communicate directly with BS 102 via uplink communication signals. UE 101 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal or device, or described using other terms used in the art.

[0029] In some embodiments of the present application, for example, UE 101 may include (but is not limited to) computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smart TVs (e.g., TVs connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle-mounted computers, network devices (e.g., routers, switches, and modems), Internet of Things (IoT) devices, Industrial Internet of Things (IIoT) devices, etc.

[0030] According to some embodiments of the present application, for example, UE 101 may include (but is not limited to) a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network.

[0031] In addition, in some embodiments of the present application, for example, UE 101 may include (but is not limited to) a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc.

[0032] The wireless communication system 100 may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a network based on time division multiple access (TDMA), a network based on code division multiple access (CDMA), a network based on orthogonal frequency division multiple access (OFDMA), a long term evolution (LTE) network, a network based on 3GPP, a network based on 3GPP 5G, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0033] In some embodiments of the present application, the wireless communication system 100 is compatible with the 5G New Radio of the 3GPP protocol, wherein the BS 102 transmits data using an OFDM modulation scheme on the DL, and the UE 101 transmits data using a single carrier frequency division multiple access (SC-FDMA) or OFDM scheme on the UL. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX, WiFi, and other protocols.

[0034] In some embodiments of the present application, BS 102 may communicate using other communication protocols, such as the IEEE 802.11 series of wireless communication protocols. Further, in some embodiments of the present application, BS 102 may communicate on a licensed spectrum, while in other embodiments, BS 102 may communicate on an unlicensed spectrum. The present application is not intended to be limited to implementations of any particular wireless communication system architecture or protocol. In still other embodiments of the present application, BS 102 may communicate with UE 101 using 3GPP 5G protocols.

[0035] The following describes how UE 101 performs a DRX process. When performing DRX, UE 101 needs to configure the value of the timer according to the DRX configuration information from BS 102. For example, BS 102 may transmit the DRX configuration information to UE 101 via ConnectionReconfiguration or RRCConnection Setup or RRCConnectionReestablishment. The timer may include an on-duration timer, an inactivity timer, a HARQ RTT timer, a retransmission timer, etc. The value of the timer may be indicated by the number of time slots or symbols. For example, the value of the on-duration timer may be used to indicate the minimum length of time that the UE remains in the active state after entering the active state. The value of the inactivity timer may be used to indicate how long the UE remains active after receiving the scheduling signaling of the physical downlink control channel (PDCCH). The value of the HARQ RTT timer may be used to indicate the minimum round trip time (TTI) before the UE expects a HARQ retransmission, and when the HARQ RTT timer is running, the UE does not need to monitor the PDCCH; and when the HARQ RTT timer expires, the UE resumes PDCCH reception. The value of the retransmission timer may be used to indicate the maximum number of subframes for continuously monitoring the PDCCH starting from the subframe in which the UE expects to receive a downlink retransmission.

[0036] In 3GPP TS38.321, DRX is specified as follows:

[0037] 5.7 Discontinuous Reception (DRX)

[0038] When configuring a DRX cycle, the active time includes the following times:

[0039] - drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer (as described in clause 5.1.5) is running; or

[0040] - A Scheduling Request is sent on the PUCCH and is pending (as described in clause 5.4.4); or

[0041] -After successfully receiving a random access response for a random access preamble that was not selected by the MAC entity among the contention-based random access preambles (as described in clause 5.1.4), a Physical Downlink Control Channel (PDCCH) indicating a new transmission of the C-RNTI addressed to the MAC entity has not been received.

[0042] ...omitted...

[0043] When DRX is configured, the MAC entity shall:

[0044] ...omitted...

[0045] 1> If the MAC PDU is transmitted in a configured uplink grant:

[0046] 2> Then after the first repetition of the corresponding PUSCH transmission ends, start in the first symbol

[0047] drx-HARQ-RTT-TimerUL for the corresponding HARQ process;

[0048] 2> Then stop the drx-RetransmissionTimerUL for the corresponding HARQ process.

[0049] ...omitted...

[0050] 1> If the MAC entity is in active time:

[0051] 2> then monitor the PDCCH as specified in TS 38.213 [6];

[0052] ...omitted...

[0053] 2> If PDCCH indicates UL transmission:

[0054] 3> Then after the first repetition of the corresponding PUSCH transmission ends, the drx-HARQ-RTT-TimerUL for the corresponding HARQ process is started in the first symbol;

[0055] 3> Then stop the drx-RetransmissionTimerUL for the corresponding HARQ process. 2> If PDCCH indicates a new transmission (DL or UL):

[0056] 3> Start or restart drx-InactivityTimer in the first symbol after PDCCH reception ends.

[0057] At the 3GPP RAN2#107 meeting, regarding NR-IIOT, after discussion, the following agreement was reached:

[0058] Data Data prioritization (using CG):

[0059] Same priority ordering resolution for Configured Grant (CG) to CG conflicts and CG to Dynamic Grant (DG) conflicts

[0060] Extends LCP restrictions by allowing restrictive mapping between LCH and certain CG configurations.

[0061] The LCP limit of DG needs to be enhanced to take reliability into account, detailing FFS.

[0062] No need to define UE processing time in MAC

[0063] For resource conflicts between several new transmissions or new transmissions and retransmissions, the same UE prioritization behavior should apply.

[0064] RAN2 assumes that the MAC PDU recovery method in grant prioritization can be reused for PUSCH to SR conflicts.

[0065] The case where the highest priority of two conflicting grants is equal is handled as follows: for CG DG conflicts, DG takes precedence, otherwise to what extent FFS is specified.

[0066] At the 3GPP RAN2#108 meeting, regarding NR-IIOT, after discussion, the following agreement was reached:

[0067] UE autonomous (re)transmission:

[0068] TP works as a baseline (may need to fix some details)

[0069] UE autonomously transmits the de-prioritized PDU as a new transmission in CG resources from the same CG configuration (different CG configuration FFS)

[0070] The new CG uses the same HARQ process as the deprioritized CG.

[0071] The autonomous (re)transmission feature is optional.

[0072] It may happen that the next CG resource is not available for retransmission due to UE processing time constraints (no consensus on whether this is a borderline case or a mainstream case). The timeline constraints are left to UE implementation (we do not specify new numbers, but something can be specified).

[0073] If the network has scheduled retransmission grant for the PDU, then the UE should not perform autonomous transmission of the PDU. Do we specify some time limit for FFS.

[0074] LCP restriction enhancements:

[0075] RRC configures the LCH in LogicalChannelConfig (as currently restricted by LCH) with one or more allowed L1 priority values ​​(eg in allowedPriorityLevels list), which applies at least to mapping to DG, for CGFFS.

[0076] UE internal priority sorting for overlapping grants:

[0077] For CGCG conflicts and CGDG conflicts, taking into account LCH restrictions and data availability, the priority value of the uplink grant (UL-SCH resource) is the highest priority of the LCH multiplexed or multiplexable in the MAC PDU.

[0078] If the PUCCH resources used for the transmission timing of SR overlap with the UL-SCH resources, then if the priority of the LCH triggering the SR is higher, then based on the comparison of the priority of the LCH triggering the SR with the priority value of the UL-SCH resources (where the priority value is determined as in the previous protocol), the transmission of the SR is allowed (gives priority).

[0079] For CG-CG conflicts with equal priority, the priority ordering depends on the UE implementation.

[0080] For SR-data collisions with equal priority, UL-SCH (ie, data) is prioritized.

[0081] In the above protocol, CG is the abbreviation of configured grant, and DG is the abbreviation of dynamic grant. It is expected that 5G networks will support applications that require URLLC services. In order to support these types of applications, 5G-NR introduces an unauthorized uplink transmission feature, i.e., data transmission without authorization transmission (TWG) or resource request. Therefore, once the BS activates the uplink grant to the UE, if the UE does not receive a deactivation indication of the uplink grant, it will always use the resources specified by the uplink grant for uplink transmission, where the uplink grant is the CG. DG is used for dynamic scheduling, and once the UE has data to transmit, the BS transmits the uplink grant to the UE in response to the UE's scheduling request.

[0082] As described in the above protocol, conflict scenarios have been identified for intra-UE prioritization and multiplexing. In addition, some conclusions have been drawn related to handling de-prioritized transmissions. For example, a de-prioritized MAC PDU can be scheduled by the network as a retransmission PDU before autonomous transmission. This can be understood as accelerating the retransmission of the de-prioritized MAC PDU.

[0083] However, due to the impact of DRX in certain scenarios, such accelerated retransmission may fail. Figure 2 An exemplary scenario of failed scheduling of de-prioritized MAC PDUs according to an embodiment of the present disclosure is described.

[0084] like Figure 2 As shown in , a DRX cycle for a UE is configured. In the present application, the UE may include one MAC entity, two MAC entities, or more MAC entities. For ease of explanation, the following disclosure is described with respect to one MAC entity.

[0085] like Figure 2 As shown in , in duration T1, the drx-onDurationTimer is started and the MAC entity can monitor the PDCCH.

[0086] During duration T2, a CG-CG conflict with equal priority occurs. Figure 2 In , CG1 represents the first MAC PDU transmitted in the first configured grant, and CG2 represents the second MAC PDU transmitted in the second configured grant. The first MAC PDU and the second MAC PDU have the same priority. For example, they are both used for URLLC service. Figure 2 In the embodiment of the present invention, the first MAC PDU is a prioritized MAC PDU and the second MAC PDU is a de-prioritized MAC PDU, and therefore the BS can receive the first MAC PDU and does not transmit the second MAC PDU. The BS can identify the CG-CG conflict. From the perspective of the network and QoS of IIOT, the network preferably schedules uplink retransmission for the hybrid automatic repeat request (HARQ) process 2 of the second MAC PDU as quickly as possible.

[0087] However, if Figure 2As shown in , according to the DRX specified in TS38.321, in duration T3, the drx-HARQ-RTT-TimerUL for the HARQ process 1 of the first MAC PDU is started, and the drx-RetransmissionTimerUL for the HARQ process 1 of the first MAC PDU is stopped. As a result, the MAC entity enters inactive time. Even if downlink control information (DCI) for scheduling retransmission of HARQ process 2 of the second MAC PDU is transmitted from the BS, the MAC entity does not monitor the PDCCH and cannot receive the DCI. Therefore, the MAC entity cannot enter active time and cannot receive the DCI for scheduling retransmission of HARQ process 2 of the second MAC PDU until duration T4 in which drx-RetransmissionTimerUL is started. Therefore, in the example Figure 2 In the case shown in , the goal of accelerating retransmission for de-prioritized MAC PDUs cannot be achieved.

[0088] In another example, a conflict for retransmission may occur between a high priority CG and a low priority DG. For example, a MAC PDU transmitted in the CG may correspond to a URLLC service, and a MAC PDU transmitted in the DG may correspond to an enhanced mobile broadband (eMBB) service. When the BS receives a MAC PDU transmitted in the CG, the BS may identify a conflict for retransmission between the high priority CG and the low priority DG. That is, the de-prioritized MAC PDU in the low priority DG is not transmitted. Therefore, the BS will schedule retransmission for the de-prioritized MAC PDU. However, similar to reference Figure 2 In the described and illustrated situation, the MAC entity enters the inactive time during the duration T3. Even if the DCI for scheduling the retransmission of the HARQ process 2 of the de-prioritized MAC PDU in the low priority DG is transmitted from the BS, the MAC entity does not monitor the PDCCH and cannot receive the DCI. Therefore, the goal of accelerating the retransmission of the de-prioritized retransmitted MAC PDU cannot be achieved.

[0089] In yet another example, a conflict may occur between a DG for retransmission and a CG with the same priority. For example, when the BS receives a MAC PDU transmitted in a DG, the BS may identify the conflict. That is, the de-prioritized MAC PDU in the CG is not transmitted. Therefore, the BS will schedule a retransmission for the de-prioritized MAC PDU. However, similar to reference Figure 2In the described and illustrated situation, the MAC entity enters the inactive time during the duration T3. Even if the DCI for the retransmission of the HARQ process 2 for scheduling the de-prioritized MAC PDU in the CG is transmitted from the BS, the MAC entity does not monitor the PDCCH and cannot receive the DCI. Therefore, the goal of accelerating the retransmission for the de-prioritized retransmission MAC PDU cannot be achieved.

[0090] Figure 3 Another exemplary scenario of failed scheduling of URLLC retransmission on NR-U according to an embodiment of the present disclosure is described. URLLC on unlicensed spectrum is proposed as Rel-17 scope of IIOT.

[0091] like Figure 3 As shown in , in duration T1, the UE receives a DCI indicating an uplink grant for uplink retransmission on the unlicensed spectrum. However, uplink retransmission on the unlicensed spectrum may be blocked due to a busy channel (e.g., due to a failed listen-before-talk (LBT)). In addition, after receiving the DCI, in duration T2, the drx-RetransmissionTimerUL of the corresponding HARQ process for uplink retransmission is stopped, and the drx-HARQ-RTT-TimerUL for the corresponding HARQ process is not started. In addition, in durations T3 and T4, there is no transmission of CG or scheduling request (SR). As a result, the MAC entity is in an inactive time and the PDCCH is not monitored, so that the DCI for retransmission cannot be received. The DCI for retransmission can be received in the next drx-onDurationTimer operation (within duration T5).

[0092] Therefore, it is necessary to accelerate retransmission to handle de-prioritized uplink transmissions, especially when the de-prioritized MAC PDU is used for URLLC services (e.g., in Figure 2 In the case of ), timely scheduling of retransmissions of blocked uplink transmissions is necessary, especially when it is used for URLLC services (e.g., in Figure 3 in the case of ).

[0093] Figure 4 is a flow chart illustrating a method for timely scheduling of uplink transitions according to some embodiments of the present application. Figure 4 The method described in can be implemented by a UE.

[0094] like Figure 4As shown in FIG. 4 , in step 401, the MAC entity may configure DRX configuration information. Prior to step 401, the UE may receive the DRX configuration information from the BS and perform DRX according to the DRX configuration information. The DRX configuration information may include values ​​of timers, such as drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerUL, ra-ContentionResolutionTimer, etc. Therefore, the UE may perform DRX according to the values ​​of the timers.

[0095] In step 402, in response to the fact that no MAC PDU is transmitted in an uplink grant, the MAC entity is prevented from entering an inactive time.

[0096] In some embodiments, in order to prevent the MAC entity from entering an inactive time, the conditions for starting the drx-RetransmissionTimerUL are modified.

[0097] In some embodiments, DRX configuration information is configured, or specifically, DRX configuration information is configured using indication A. In addition, the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capabilities, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule that supports priority-based resource conflict prioritization as a new feature of IIOT WI, and may be configured for backward compatibility and separation from existing text for UEs that do not support this feature.

[0098] In an embodiment, a resource conflict occurs. For example, a MAC PDU (hereinafter referred to as "PDU1") is not transmitted in an uplink grant, and the uplink grant is a deprioritized uplink grant. The deprioritized uplink grant is received on the PDCCH and is addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty; while another MAC PDU (hereinafter referred to as "PDU2") is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process of PDU2. For example, the MAC entity starts the drx-RetransmissionTimerUL for the corresponding HARQ process of PDU2 in the first symbol after receiving the deprioritized uplink grant on the PDCCH. In another embodiment, in order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process of PDU1. For example, the MAC entity starts the drx-RetransmissionTimerUL for the corresponding HARQ process for PDU1 in the first symbol after receiving the de-prioritized uplink grant on the PDCCH.

[0099] In another embodiment, a resource conflict occurs. For example, PDU1 is not transmitted in an uplink grant, and the uplink grant is a deprioritized uplink grant. The deprioritized uplink grant is a configured grant; while PDU2 is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process of PDU2. For example, the MAC entity starts the drx-RetransmissionTimerUL for the corresponding HARQ process of PDU2 in the first symbol of the deprioritized uplink grant. In another embodiment, in order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process of PDU1. For example, the MAC entity starts the drx-RetransmissionTimerUL for the corresponding HARQ process of PDU1 in the first symbol of the deprioritized uplink grant.

[0100] In some embodiments, DRX configuration information is configured in NR-U, or DRX configuration information is configured using indication B. Indication B may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication B may indicate that the optimal DRX rule in NR-U may be configured for backward compatibility and separated from the existing text for UEs that do not support this feature. In an embodiment, in uplink transmission, after the MAC entity receives a DCI indicating an uplink grant for retransmission of PDU1, PDU1 is not transmitted in the uplink grant due to LBT failure. In order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process for PDU1. For example, the MAC entity starts the drx-RetransmissionTimerUL for the corresponding HARQ process for PDU1 in the first / last symbol of the uplink grant.

[0101] In some embodiments, to prevent the MAC entity from entering an inactive time, the conditions for starting the drx-RetransmissionTimerUL are simply modified.

[0102] In some embodiments, DRX configuration information is configured or DRX configuration information is configured using indication A, and the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule for prioritization that supports priority-based resource conflicts as a new feature of IIOT WI, which may be configured for backward compatibility and separated from existing texts of UEs that do not support this feature. In an embodiment, a resource conflict occurs. For example, PDU1 is not transmitted in an uplink grant, the uplink grant is a deprioritized uplink grant, and PDU2 is transmitted in a prioritized uplink grant. The deprioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, or the deprioritized uplink grant is a configured grant. To prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process of PDU2. In another embodiment, to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-RetransmissionTimerUL for the HARQ process of PDU1.

[0103] In some embodiments, in order to prevent the MAC entity from entering an inactive time, the drx-HARQ-RTT-TimerUL per HARQ process is updated or configured. In some embodiments, the value of drx-HARQ-RTT-TimerUL may be described as indicating "a value indicating the number of symbols of the bandwidth part (BWP) of the transport block to be transmitted. If indication A is indicated, the value may be modified according to the HARQ process."

[0104] In some embodiments, DRX configuration information is configured or DRX configuration information is configured using indication A. In addition, the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule for supporting priority-based resource conflict prioritization as a new feature of IIOT WI, which may be configured for backward compatibility and separated from the existing text of UEs that do not support this feature. In an embodiment, PDU1 is not transmitted in an uplink grant, and the uplink grant is a de-prioritized uplink grant. In addition, the de-prioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, or the de-prioritized uplink grant is a configured grant, and PDU2 is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering the inactive time, in an embodiment, the MAC entity sets the value of the drx-HARQ-RTT-TimerUL for the HARQ process of PDU2 to a value less than the value of the drx-HARQ-RTT-TimerUL included in the DRX configuration information or to a value of "0", and starts the drx-HARQ-RTT-TimerUL for the HARQ process of PDU2, for example, starting the drx-HARQ-RTT-TimerUL for the HARQ process of PDU2 in the first symbol after the end of the first repetition of the corresponding prioritized PUSCH transmission. When this HARQ process is completed, the drx-HARQ-RTT-TimerUL of the corresponding HARQ process is set back to the value configured by RRC.

[0105] Alternatively, in another embodiment, the MAC entity starts the drx-HARQ-RTT-TimerUL for the HARQ process for PDU1. For example, the MAC entity starts the drx-HARQ-RTT-TimerUL for the HARQ process for PDU1 after an uplink grant is received on the PDCCH or in the first symbol of a configured uplink grant.

[0106] In another embodiment, the MAC entity first sets the value of the drx-HARQ-RTT-TimerUL for the HARQ process of PDU1 to a value less than the value of the drx-HARQ-RTT-TimerUL included in the DRX configuration information or to a value of "0", and then starts the drx-HARQ-RTT-TimerUL for the HARQ process of PDU1. For example, the MAC entity starts the drx-HARQ-RTT-TimerUL for the HARQ process of PDU1 after an uplink grant is received on the PDCCH or in the first symbol of a configured uplink grant. When the HARQ process is completed, the drx-HARQ-RTT-TimerUL of the corresponding HARQ process is set back to the value configured by RRC.

[0107] In some embodiments, DRX configuration information is configured in NR-U, or DRX configuration information is configured using indication B. Indication B may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI, and indication B may indicate that the optimal DRX rule in NR-U may be configured for backward compatibility and separated from the existing text of UEs that do not support this feature. In one embodiment, after the MAC entity receives a DCI indicating an uplink grant for retransmission of PDU1, the uplink transmission (e.g., PDU1) is not transmitted in the uplink grant due to a failed LBT. In order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-HARQ-RTT-TimerUL for the HARQ process for PDU1. Alternatively, in another embodiment, the MAC entity first sets the value of the drx-HARQ-RTT-TimerUL for the HARQ process of PDU1 to a value less than the value of the drx-HARQ-RTT-TimerUL included in the DRX configuration information or to a value of "0", and then, starts the drx-HARQ-RTT-TimerUL for the HARQ process of PDU1, for example, starting the drx-HARQ-RTT-TimerUL for the HARQ process of PDU1 in the first / last symbol of the uplink grant.

[0108] In some embodiments, to prevent the MAC entity from entering an inactive time, a drx-HARQ-RTT-TimerUL is started with a delta value (eg, delta-RTT-TimerUL) for de-prioritized uplink grants.

[0109] In some embodiments, DRX configuration information is configured or DRX configuration information is configured using indication A, and the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. Indication A may indicate the best DRX rule for supporting priority-based resource conflict prioritization as a new feature of IIO TWI, which may be configured for backward compatibility and separated from the existing text of UEs that do not support this feature. In an embodiment, PDU1 is not transmitted in an uplink grant, and the uplink grant is a de-prioritized uplink grant. The de-prioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, while PDU2 is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In an embodiment, in order to prevent the MAC entity from entering an inactive time, the MAC entity will use drx-HARQ-RTT-TimerUL-delta-RTT-TimerUL (the value of delta-RTT-TimerUL is included in the DRX configuration information transmitted from the BS) to update the drx-HARQ-RTT-TimerUL of the corresponding HARQ process for PDU1 (or PDU 2), and start the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1 (or PDU 2), for example, starting the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1 (or PDU 2) in the first symbol after the uplink grant received on the PDCCH.

[0110] In another embodiment, PDU1 is not transmitted in an uplink grant, the uplink grant is a de-prioritized uplink grant, the de-prioritized uplink grant is a configured grant, and PDU2 is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering inactive time, in an embodiment, the MAC entity will use drx-HARQ-RTT-TimerUL-delta-RTT-TimerUL (the value of delta-RTT-TimerUL is included in the DRX configuration information) to update the drx-HARQ-RTT-TimerUL of the corresponding HARQ process for PDU1 (or PDU2), and start the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1 (or PDU 2), for example, start the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1 (or PDU 2) in the first symbol of the configured uplink grant.

[0111] In some embodiments, DRX configuration information is configured in NR-U, or DRX configuration information is configured using indication B. Indication B may be added to the DRX configuration information, or an additional bit for UE capabilities, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. Indication B may indicate that the optimal DRX rule in NR-U may be configurable for backward compatibility and separated from existing text for UEs that do not support this feature. In an embodiment, after the MAC entity receives a DCI indicating an uplink grant for retransmission of PDU1, an uplink transmission (e.g., PDU1) is not transmitted in the uplink grant due to a failed LBT. In order to prevent the MAC entity from entering inactive time, the MAC entity will use drx-HARQ-RTT-TimerUL-delta-RTT-TimerUL (the value of delta-RTT-TimerUL is included in the DRX configuration information) to update the drx-HARQ-RTT-TimerUL of the corresponding HARQ process for PDU1, and start the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1, for example, start the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1 in the first / last symbol of the corresponding uplink grant.

[0112] In some embodiments, to prevent the MAC entity from entering an inactive time, the drx-HARQ-RTT-TimerUL is simply updated using a delta value.

[0113] In some embodiments, DRX configuration information is configured, or specifically, DRX configuration information is configured using indication A. In addition, the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule for supporting priority-based resource conflict prioritization as a new feature of IIOT WI, and may be configured for backward compatibility and separation from existing text of UEs that do not support this feature. In an embodiment, for example, PDU1 is not transmitted in an uplink grant, the uplink grant is a deprioritized uplink grant, and PDU2 is transmitted in a prioritized uplink grant. The deprioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, or the deprioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering inactive time, the MAC entity will first use drx-HARQ-RTT-TimerUL-delta-RTT-TimerUL (the value of delta-RTT-TimerUL is included in the DRX configuration information) to update the drx-HARQ-RTT-TimerUL of the corresponding HARQ process for PDU1 (or PDU 2), and then start the drx-HARQ-RTT-TimerUL of the HARQ process for PDU1 (or PDU2).

[0114] In some embodiments, if the DRX configuration information is configured using indication A and the MAC entity is configured using priorityBasedPrioritization, the value of drx-HARQ-RTT-TimerUL may be configured according to the HARQ process, and it may be described as indicating "the value of the number of symbols of the BWP of the transmission block. If indication A is indicated, the value is configured according to the HARQ process."

[0115] In some embodiments, if the DRX configuration information is configured using indication B, and after the MAC entity receives a DCI indicating an uplink grant for retransmission of a MAC PDU, the MAC PDU is not transmitted in the uplink grant due to a failed LBT, then the value of drx-HARQ-RTT-TimerUL may be configured according to the HARQ process, and it may be described as indicating "a value indicating the number of symbols of the BWP for transmitting a transport block. If indication B is indicated, then the value is configured according to the HARQ process."

[0116] In some embodiments, in order to prevent the MAC entity from entering an inactive time, a new RTT timer is introduced, for example, drx-HARQ-RTT-TimerUL-deprioritized, which is used to deprioritize uplink grants. The new RTT timer is configured according to the uplink HARQ process, indicating the minimum duration before the MAC entity expects an uplink HARQ retransmission grant, and the uplink HARQ process is not a prioritized HARQ process, or the uplink HARQ process is a deprioritized HARQ process.

[0117] In some embodiments, DRX configuration information is configured, or specifically, DRX configuration information is configured using indication A. In addition, the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule for supporting priority-based resource conflict prioritization as a new feature of IIOT WI, and may be configured for backward compatibility and separation from existing text of UEs that do not support this feature. In an embodiment, for example, PDU1 is not transmitted in an uplink grant, and the uplink grant is a de-prioritized uplink grant. The de-prioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, while PDU2 is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering the inactive time, the MAC entity will start the drx-HARQ-RTT-TimerUL-deprioritized of the corresponding HARQ process for PDU1, for example, the MAC entity will start the drx-HARQ-RTT-TimerUL-deprioritized of the corresponding HARQ process for PDU1 in the first symbol after the uplink grant received on the PDCCH, or in the first symbol after the end of the first repeated grant of the corresponding uplink transmission. Start the drx-HARQ-RTT-TimerUL-deprioritized of the corresponding HARQ process for PDU1. In another embodiment, for example, PDU1 is not transmitted in the uplink grant, the uplink grant is a deprioritized uplink grant, the deprioritized uplink grant is a configured grant, and PDU2 is transmitted in the prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering the inactive time, the MAC entity will start the drx-HARQ-RTT-TimerUL-deprioritized of the corresponding HARQ process for PDU 1 in the first symbol of the configured uplink grant. And then, if the drx-HARQ-RTT-TimerUL-deprioritized expires, the MAC entity will start the drx-RetransmissionTimerUL of the corresponding HARQ process for PDU 1 in the first symbol after the expiration of the drx-HARQ-RTT-TimerUL-deprioritized.

[0118] In some embodiments, after receiving a DCI indicating an uplink grant for retransmission, an expected uplink retransmission corresponding to an uplink HARQ process is not transmitted due to a failed LBT. A new RTT timer drx-HARQ-RTT-TimerUL-deprioritized is introduced, which is used to cancel the prioritized uplink grant. The new RTT timer is configured according to the HARQ process and indicates the minimum duration before an uplink HARQ retransmission grant is expected by the MAC entity. In an embodiment, DRX configuration information is configured in NR-U, or DRX configuration information is configured using indication B. Indication B may be added to the DRX configuration information, or an additional bit for UE capabilities, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. Indication B may indicate that the optimal DRX rule in NR-U may be configurable for backward compatibility and separation from existing text for UEs that do not support this feature. In an embodiment, after the MAC entity receives a DCI indicating an uplink grant for retransmission of PDU1, the uplink transmission (e.g., PDU1) is not transmitted in the uplink grant due to failed LBT. In order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-HARQ-RTT-TimerUL-deprioritized of the corresponding HARQ process for PDU 1, for example, start it in the first / last symbol of the corresponding PUSCH grant. And then, if the drx-HARQ-RTT-TimerUL-deprioritized expires, the MAC entity will start the drx-RetransmissionTimerUL of the corresponding HARQ process for PDU 1 in the first symbol after the expiration of drx-HARQ-RTT-TimerUL-deprioritized.

[0119] In some embodiments, to prevent the MAC entity from entering a time of inactivity, a new RTT timer, drx-HARQ-RTT-TimerUL-deprioritized, is simply applied.

[0120] In some embodiments, DRX configuration information is configured, or specifically, DRX configuration information is configured using indication A. In addition, the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule for supporting priority-based resource conflict prioritization as a new feature of IIOT WI, and may be configured for backward compatibility and separation from existing text of UEs that do not support this feature. In an embodiment, for example, PDU1 is not transmitted in an uplink grant, the uplink grant is a deprioritized uplink grant, and PDU2 is transmitted in a prioritized uplink grant. The deprioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, or the deprioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering inactive time, the MAC entity will start the drx-HARQ-RTT-TimerUL-deprioritized for the HARQ process of PDU1. And then, if the drx-HARQ-RTT-TimerUL-deprioritized expires, the MAC entity will start the drx-RetransmissionTimerUL for the corresponding HARQ process of PDU 1 in the first symbol after the expiration of the drx-HARQ-RTT-TimerUL-deprioritized.

[0121] In some embodiments, in order to prevent the MAC entity from entering an inactive time, a new timer, such as drx-InactivityTimer-deprioritized, is introduced, which is used to cancel the prioritized uplink grant. The new timer is configured according to the uplink HARQ process, and the value of drx-InactivityTimer-deprioritized can indicate the duration after deciding the timing to cancel the prioritized uplink grant, and is configured according to the UL HARQ process or according to the MAC entity.

[0122] In the case where drx-InactivityTimer-deprioritized is introduced, when the DRX cycle is configured, the MAC entity is considered to be in the active time when drx-InactivityTimer-deprioritized is running. That is, in the case where drx-InactivityTimer-deprioritized is introduced, when the DRX cycle is configured, the active time may include the time when drx-onDurationTimer or drx-InactivityTimer or drx-InactivityTimer-deprioritized or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running.

[0123] In an embodiment, DRX configuration information is configured or DRX configuration information is configured using indication A. In addition, the MAC entity is configured using priorityBasedPrioritization. Indication A may be added to the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. In addition, indication A may indicate the best DRX rule for supporting priority-based resource conflict prioritization as a new feature of IIOT WI, and may be configured for backward compatibility and separation from existing text of UEs that do not support this feature. In an embodiment, for example, PDU1 is not transmitted in an uplink grant, and the uplink grant is a de-prioritized uplink grant. The de-prioritized uplink grant is received on the PDCCH and addressed to the CS-RNTI, and the HARQ buffer of the identified process is not empty, or the de-prioritized uplink grant is a configured grant, and PDU2 is transmitted in a prioritized uplink grant, and the prioritized uplink grant is a configured grant. In order to prevent the MAC entity from entering inactive time, the MAC entity will start drx-InactivityTimer-deprioritized for the corresponding HARQ process in the first symbol after the uplink grant is deemed to be a deprioritized uplink grant or a configured uplink grant that is not deemed to be prioritized. Alternatively, in another embodiment, after a deprioritized MAC PDU containing an LCH associated with an allowedprioritylevel equal to 1 or an allowedprioritylevel indicating a low priority is stored in the HARQ process, the MAC entity will start drx-InactivityTimer-deprioritized for the corresponding HARQ process in the first symbol. The allowedprioritylevel indicates the priority of the LCH that supports priority-based resource conflict sorting as a new feature of the IIOT WI, which can be configured for backward compatibility and separation from existing text of UEs that do not support this feature.

[0124] During the activation of drx-InactivityTimer-deprioritized, the MAC entity may receive a PDCCH indicating a retransmission of a HARQ process and the previous uplink grant of the MAC PDU in the HARQ buffer is a deprioritized uplink grant, or a new transmission in a configured uplink grant and the previous uplink grant of the MAC PDU in the HARQ buffer is a deprioritized uplink grant, and then the MAC entity will stop drx-InactivityTimer-deprioritized for the corresponding HARQ process in the first symbol after the deprioritized MAC PDU in the transmission HARQ process.

[0125] In some embodiments, after receiving a DCI indicating an uplink grant for retransmission, an expected uplink retransmission corresponding to an uplink HARQ process is not transmitted due to a failed LBT. A new timer drx-InactivityTimer-deprioritized is introduced, which is used to cancel the prioritized uplink grant. The value of drx-InactivityTimer-deprioritized may indicate a duration after deciding the timing to cancel the prioritized uplink grant, and is configured according to the uplink HARQ process or according to the MAC entity.

[0126] In some embodiments, in the case where drx-InactivityTimer-deprioritized is introduced, when configuring the DRX cycle, the DRX configuration information is configured in NR-U or the DRX configuration information is configured using indication B. The activity time may include the time when drx-onDurationTimer or drx-InactivityTimer or drx-InactivityTimer-deprioritized or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running. Indication B may be added to the DRX configuration information, or an additional bit for UE capabilities, or a new MAC control element (CE), or a new DCI may be added, or an additional bit may be added to the current DCI. Indication B may indicate that the best DRX rule in NR-U may be configured for backward compatibility and separated from the existing text of UEs that do not support this feature. In an embodiment, after the MAC entity receives a DCI indicating an uplink grant for retransmission of PDU1, the uplink transmission (e.g., PDU1) is not transmitted in the uplink grant due to a failed LBT. In order to prevent the MAC entity from entering the inactivity time, the MAC entity shall start the drx-InactivityTimer-deprioritized of the corresponding HARQ process for PDU1 in the first / last symbol of the corresponding uplink grant.

[0127] During the activation of drx-InactivityTimer-deprioritized, the MAC entity may receive a PDCCH indicating a retransmission for a previously failed transmission, and then the MAC entity will stop drx-InactivityTimer-deprioritized for the corresponding HARQ process in the first symbol after the previously failed MAC PDU (due to LBT failure) in the transmission HARQ process.

[0128] Therefore, through the embodiments described above, even if a collision occurs or an uplink transmission fails, scheduling of retransmissions can be accelerated or allowed.

[0129] In the above description, although the indication A or the indication B is described, it should be understood that the indication A or the indication B may be referred to as other names.

[0130] Figure 5 In some embodiments of the present disclosure, the device 500 may be as follows: Figure 1 UE 101 described in or other embodiments of the present application.

[0131] like Figure 5 As shown in , the apparatus 500 may include a receiver 501, a transmitter 503, a processor 505, and a non-transitory computer-readable medium 507. The non-transitory computer-readable medium 507 has computer-executable instructions stored therein. The processor 505 is configured to be coupled to the non-transitory computer-readable medium 507, the receiver 501, and the transmitter 503. It should be considered that, according to practical requirements, in some other embodiments of the present application, the apparatus 500 may include more computer-readable media, receivers, transmitters, and processors. In some embodiments of the present application, the receiver 501 and the transmitter 503 are integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 500 may further include an input device, a memory, and / or other components.

[0132] In some embodiments of the present application, the non-transitory computer-readable medium 507 may have computer-executable instructions stored thereon to cause a processor to implement a method according to an embodiment of the present application.

[0133] Those skilled in the art should understand that with the development and advancement of technology, the terms described in this application may change and should not affect or limit the principles and spirit of this application.

[0134] Those of ordinary skill in the art will appreciate that the steps of the methods described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In addition, in some aspects, the steps of the method may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium that may be incorporated into a computer program product.

[0135] Although the present disclosure has been described with its specific embodiments, it is apparent that many alternatives, modifications and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, all elements of each figure are not necessarily required for the operation of the disclosed embodiments. For example, a person of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as described herein are intended to be illustrative, not restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0136] In this document, the term "comprise" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements not only include those elements, but also may include other elements that are not clearly listed or inherent to such processes, methods, articles or equipment. In the absence of more constraints, the element starting with "one" or the like does not exclude the existence of additional identical elements in the process, method, article or equipment included in the element. In addition, the term "another" is defined as at least the second or more. As used herein, the term "comprise", "have" and the like are defined as "comprises".

Claims

1. A method comprising: Configure discontinuous reception (DRX) configuration information; and Preventing a media access control (MAC) entity from entering an inactive time in response to a first MAC protocol data unit (PDU) not being transmitted in an uplink grant due to a listen-before-talk (LBT) failure after receiving downlink control information (DCI) indicating the uplink grant for retransmission.

2. The method of claim 1 , wherein the MAC entity is configured with priority-based prioritization, and the uplink grant in which the first MAC PDU is not transmitted is a de-prioritized grant, and the method further comprises: A second MAC PDU is transmitted in a prioritized uplink grant without transmitting the first MAC PDU. The method of claim 2 , wherein the prioritized uplink grant is a configured grant.

4. A method according to claim 2 or 3, wherein the de-prioritized uplink grant is received on a physical downlink control channel (PDCCH) and is addressed to a configured scheduling-radio network temporary identifier (CS-RNTI), and the HARQ buffer of the identified hybrid automatic repeat request (HARQ) process of the first MAC PDU is not empty.

5. The method of claim 2 or 3, wherein the de-prioritized uplink grant is a configured grant.

6. The method according to claim 2, wherein the DRX configuration information includes a value of drx-RetransmissionTimerUL, wherein preventing the MAC entity from entering an inactive time comprises: Start the drx-RetransmissionTimerUL for the HARQ process of the second MAC PDU or the first MAC PDU.

7. The method according to claim 2, wherein the DRX configuration information includes a value of drx-HARQ-RTT-TimerUL, wherein preventing the MAC entity from entering an inactive time comprises: Updating and starting the drx-HARQ-RTT-TimerUL for the HARQ process of the second MAC PDU; or Update and / or start the drx-HARQ-RTT-TimerUL for the HARQ process of the first MAC PDU.

8. The method of claim 7, wherein updating the drx-HARQ-RTT-TimerUL comprises: The value of the drx-HARQ-RTT-TimerUL for the HARQ process is set to a value smaller than the value of the drx-HARQ-RTT-TimerUL included in the DRX configuration information or to a value of "0".

9. The method of claim 7, wherein updating the drx-HARQ-RTT-TimerUL comprises: The value of the drx-HARQ-RTT-TimerUL for the HARQ process is updated using the delta value.

10. The method of claim 9, wherein updating the drx-HARQ-RTT-TimerUL comprises: The value of the drx-HARQ-RTT-TimerUL for the HARQ process is updated using the value of drx-HARQ-RTT-TimerUL minus the delta value.

11. The method of claim 1, wherein the DRX configuration information comprises a value for a new round trip time (RTT) timer, wherein the new RTT timer is configured according to a HARQ process and indicates a minimum duration before the MAC entity expects an uplink HARQ retransmission grant.

12. The method according to claim 1, wherein the DRX configuration information comprises a value of a new timer, wherein an active time comprises a time for which the new timer runs.

13. The method according to claim 1, wherein an indication for enabling the method is added in the DRX configuration information, or an additional bit for UE capability, or a new MAC control element (CE), or a new DCI is added, or an additional bit is added in the current DCI.

14. A device for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the apparatus to: Configure discontinuous reception (DRX) configuration information; and Preventing a media access control (MAC) entity from entering an inactive time in response to a first MAC protocol data unit (PDU) not being transmitted in an uplink grant due to a listen-before-talk (LBT) failure after receiving downlink control information (DCI) indicating the uplink grant for retransmission.

15. The apparatus of claim 14, wherein the MAC entity is configured with priority-based prioritization, and the uplink grant in which the first MAC PDU is not transmitted is a de-prioritized grant, and the at least one processor is further configured to cause the apparatus to: A second MAC PDU is transmitted in a prioritized uplink grant without transmitting the first MAC PDU.

16. The apparatus of claim 15, wherein the prioritized uplink grant is a configured grant.

17. An apparatus according to claim 15 or 16, wherein the de-prioritized uplink grant is received on a physical downlink control channel (PDCCH) and is addressed to a configured scheduling-radio network temporary identifier (CS-RNTI), and a HARQ buffer of the identified hybrid automatic repeat request (HARQ) process of the first MAC PDU is not empty.

18. The apparatus of claim 15 or 16, wherein the de-prioritized uplink grant is a configured grant.

19. The apparatus of claim 15, wherein the DRX configuration information comprises a value of drx-RetransmissionTimerUL, wherein to prevent the MAC entity from entering an inactive time, the at least one processor is further configured to cause the apparatus to: Start the drx-RetransmissionTimerUL for the HARQ process of the second MAC PDU or the first MAC PDU.

20. The apparatus of claim 15, wherein the DRX configuration information comprises a value of drx-HARQ-RTT-TimerUL, wherein to prevent the MAC entity from entering an inactive time, the at least one processor is further configured to cause the apparatus to: Updating and starting the drx-HARQ-RTT-TimerUL for the HARQ process of the second MAC PDU; or Update and / or start the drx-HARQ-RTT-TimerUL for the HARQ process of the first MAC PDU.

21. The apparatus of claim 20, wherein to update the drx-HARQ-RTT-TimerUL, the at least one processor is further configured to cause the apparatus to: The value of the drx-HARQ-RTT-TimerUL for the HARQ process is set to a value smaller than the value of the drx-HARQ-RTT-TimerUL included in the DRX configuration information or to a value of "0".

22. The apparatus of claim 20, wherein to update the drx-HARQ-RTT-TimerUL, the at least one processor is further configured to cause the apparatus to: The value of the drx-HARQ-RTT-TimerUL for the HARQ process is updated using the delta value.

23. The apparatus of claim 22, wherein to update the drx-HARQ-RTT-TimerUL, the at least one processor is further configured to cause the apparatus to: The value of the drx-HARQ-RTT-TimerUL for the HARQ process is updated using the value of drx-HARQ-RTT-TimerUL minus the delta value.

24. The apparatus of claim 14, wherein the DRX configuration information comprises a value for a new round trip time (RTT) timer, wherein the new RTT timer is configured according to a HARQ process and indicates a minimum duration before the MAC entity expects an uplink HARQ retransmission grant.

25. The apparatus of claim 14, wherein the DRX configuration information comprises a value of a new timer, wherein an active time comprises a time for which the new timer runs.

26. The apparatus of claim 14, wherein an additional bit for UE capability, or a new MAC Control Element (CE), or a new DCI is added in the DRX configuration information, or an additional bit is added in a current DCI.

Images