Schemes in HARQ mode ae HARQ mode b in IoT

Description

1 / 39 SCHEMES IN HARQ MODE AE HARQ MODE B IN IOT CROSS-REFERENCE TO RELATED REQUEST(S)

[001] This application claims the benefits of PCT Application Number PCT / CN2023 / 086931, entitled “SCHEDULING RESTRICTION FOR DISABLING HARQ FEEDBACK AND HARQ A / B IN IOT NTN” and filed on April 7, 2023, which is expressly incorporated by reference herein in its entirety. TECHNICAL FIELD

[002] This disclosure relates generally to communication systems and, more particularly, to techniques for monitoring downlink control information by user equipment in different Hybrid Automatic Repeat Request (HARQ) modes. BACKGROUND

[003] The statements in this section provide only basic information relating to this disclosure and may not constitute prior art.

[004] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users sharing the available system resources. Examples of such multiple access technologies include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and synchronous time division code division multiple access (TD-SCDMA).

[005] These multiple access technologies have been adopted in several telecommunications standards to provide a protocol Petition 870250095215, dated 10 / 17 / 2025, page 9 / 59 2 / 39 common standard that allows different wireless devices to communicate at the municipal, national, regional, and even global levels. An example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of an ongoing evolution of mobile broadband enacted by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further enhancements in 5G NR technology. These enhancements may also be applicable to other multiple access technologies and telecommunications standards that employ these technologies. SUMMARY

[006] The following is a simplified summary of one or more aspects in order to provide a basic understanding of them. This summary does not constitute a comprehensive overview of all aspects covered and is not intended to identify the key or critical elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified way, as a prelude to the more detailed description that will be presented later.

[007] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an UE. The UE transmits a first uplink signal to a network. The UE begins monitoring downlink control information (DCI) from the network at a point in time that corresponds to at least one halfduplex guard period after the first uplink signal transmission is complete. The UE transmits a second uplink signal to the network without receiving Hybrid Automatic Repeat Request (HARQ) feedback regarding the first. Petition 870250095215, dated 10 / 17 / 2025, page 10 / 59 3 / 39 Uplink signal from the network.

[008] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an UE. The UE receives a downlink signal from a network. The UE refrains from transmitting Hybrid Automatic Repeat Request (HARQ) feedback relating to the downlink signal to the network. The UE monitors the downlink control information (DCI) from the network at a predetermined time after the downlink signal reception is complete.

[009] For the purposes set out above and related, the one or more aspects comprise the features described in detail below, and particularly highlighted in the claims. The following description and accompanying drawings present in detail certain illustrative features of the one or more aspects. These features are, however, indicative of only some of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[010] Figure 1 is a diagram that illustrates an example of a wireless communications system and an access network.

[011] Figure 2 is a diagram that illustrates a base station communicating with a UE on an access network.

[012] Figure 3 illustrates an example of the logical architecture of a distributed access network.

[013] Figure 4 illustrates an example of the physical architecture of a distributed access network.

[014] Figure 5 is a diagram showing an example of a DL-centered slot.

[015] Figure 6 is a diagram showing an example of a UL-centered slot.

[016] Figure 7 is a diagram that illustrates a UE if Petition 870250095215, dated 10 / 17 / 2025, page 11 / 59 4 / 39 communicating on a non-terrestrial network (NTN).

[017] Figure 8 is a diagram that illustrates communications between a UE and a base station.

[018] Figure 9 is a diagram illustrating a UE monitoring the physical Downlink Control Channel (PDCCH) after receiving a PDSCH.

[019] Figure 10 is a diagram that illustrates a UE monitoring PDCCH after transmitting a PUSCH.

[020] Figure 11 is a flowchart of a method for transmitting uplink signals.

[021] Figure 12 is a flowchart of a method for monitoring downlink control information (DCI). DETAILED DESCRIPTION

[022] The detailed description presented below, in connection with the attached drawings, is intended to describe various configurations and not to represent the only configurations in which the concepts described in this document can be applied. The detailed description includes specific details with the aim of providing a complete understanding of the various concepts. However, it will be evident to those skilled in the art that these concepts can be applied without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[023] Several aspects of telecommunications systems will now be presented with reference to various devices and methods. These devices and methods will be described in detail below and illustrated in the attached drawings by means of various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as elements). These elements can be implemented by means of electronic hardware, computer software, or any combination thereof. The implementation of these elements as hardware or software depends on the application. Petition 870250095215, dated 10 / 17 / 2025, page 12 / 59 5 / 39 specific and design constraints imposed on the system as a whole.

[024] By way of example, an element, or any portion of an element, or any combination of elements, may be implemented as a processing system that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute software.Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description language, or otherwise.

[025] Thus, in one or more exemplary aspects, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or code in a computer-readable medium. Computer-readable medium includes computer storage medium. Storage medium can be any available medium that can be accessed by a computer. By way of Petition 870250095215, dated 10 / 17 / 2025, page 13 / 59 6 / 39 For example, and not as a limitation, such computer-readable media may comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[026] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also called a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160 and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high-power cellular base station) and / or small cells (low-power cellular base station). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[027] Base stations 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (EUTRAN)) can interact with the EPC 160 via backhaul links 132 (e.g., SI interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interact with the core network 190 via backhaul links 184. In addition to other functions, base stations 102 can perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., transfer, dual connectivity), coordination of Petition 870250095215, dated 10 / 17 / 2025, page 14 / 59 7 / 39 Intercell interference, connection definition and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, broadcast multicast multimedia service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and alert message delivery. Base stations 102 can communicate directly or indirectly (e.g., via EPC 160 or core network 190) with each other via backhaul links 134 (e.g., X2 interface). Backhaul links 134 can be wired or wireless.

[028] Base stations 102 can communicate wirelessly with UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved B Nodes (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).Communication links 120 between base stations 102 and UEs 104 may include uplink (UL) transmissions (also called reverse link) from a UE 104 to a base station 102 and / or downlink (DL) transmissions (also called forward link) from a base station 102 to a UE 104. Communication links 120 may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmission diversity. Communication links may be via one or more carriers. Base stations 102 / UEs 104 may use spectrum up to 7 MHz (e.g., 5, 10, 15, etc.). Petition 870250095215, dated 10 / 17 / 2025, p. 15 / 59 8 / 39 20, 100, 400, etc. MHz) of bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be called a primary cell (PCell) and a secondary component carrier may be called a secondary cell (SCell).

[029] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use the DL / UL WWAN spectrum. D2D communication link 158 can use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication can be done through a variety of wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, IEEE 802.11-based Wi-Fi, LTE, or NR.

[030] The wireless communications system may also include a Wi-Fi access point (AP) 150 communicating with Wi-Fi stations (STAs) 152 via communication links 154 in an unlicensed 5 GHz frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a free channel assessment (CCA) prior to communication in order to determine if the channel is available.

[031] The 102' small cell can operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the 102' small cell Petition 870250095215, dated 10 / 17 / 2025, p. 16 / 59 9 / 39 can employ NR and use the same unlicensed 5 GHz frequency spectrum used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, can increase the coverage and / or capacity of the access network.

[032] A base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate in a traditional spectrum below 6 GHz, at millimeter wave (mmW) frequencies and / or frequencies close to mmW in communication with UE 104. When the gNB 180 operates at mmW or near mmW frequencies, it may be called an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this range may be called millimeter waves. Near mmW waves may extend to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also known as the centimeter wave.Communications using the mmW / near mmW radio frequency band (e.g., 3 GHz - 300 GHz) exhibit extremely high path loss and short range. The mmW 180 base station can use 182 beamforming with UE 104 to compensate for the extremely high path loss and short range.

[033] Base station 180 can transmit a beamform signal to UE 104 in one or more transmission directions 108a. UE 104 can receive the beamform signal from base station 180 in one or more reception directions 108b. UE 104 can also transmit a beamform signal to base station 180 in one or more transmission directions. Base station 180 can receive the beamform signal from UE 104 in one or more reception directions. The base station Petition 870250095215, dated 10 / 17 / 2025, p. 17 / 59 10 / 39 180 / UE 104 can perform beam training to determine the best receive and transmit directions for each of the 180 / UE 104 base stations. The transmit and receive directions for base station 180 may or may not be the same. The transmit and receive directions for UE 104 may or may not be the same.

[034] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Service Gateway 166, a Multimedia Broadcast Multicast Service Gateway (MBMS) 168, a Multicast Broadcast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides carrier and connection management. All user Internet Protocol (IP) packets are transferred through Service Gateway 166, which in turn is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Services 176.IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and / or other IP services. BM-SC 170 may provide functions for provisioning and delivering MBMS user services. BM-SC 170 may serve as an entry point for MBMS transmission from content providers, may be used to authorize and initiate MBMS Carrier Services on a public terrestrial mobile network (PLMN), and may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Broadcast Multicast Single Frequency Network (MBSFN) area broadcasting a specific service and may be responsible for session management (start / end) and collection of billing information related to eMBMS. Petition 870250095215, dated 10 / 17 / 2025, page 18 / 59 11 / 39

[035] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Location Management Function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may be in communication with a Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UEs 104 and the core network 190. Generally, SMF 194 provides QoS flow and session management. All user internet protocol (IP) packets are transferred through UPF 195. UPF 195 provides UE IP address allocation as well as other functions. UPF 195 is connected to IP Services 197. IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and / or other IP services.

[036] The base station may also be called gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit-receive point (TRP) or some other suitable terminology. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104.Examples of EU 104 include a mobile phone, a smartphone, a phone with a session initiation protocol (SIP), a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electricity meter, a gasoline pump, a large or small household appliance, a health device, an implant, a sensor / actuator, a display, or any other device with... Petition 870250095215, dated 10 / 17 / 2025, page 19 / 59 12 / 39 similar operation. Some of the UE 104 may be called IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be called a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, appliance, user agent, mobile client, client, or some other suitable terminology.

[037] Although this disclosure may refer to New Radio (NR) 5G, it may be applicable to other similar areas, such as LTE, LTE Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other wireless / radio access technologies.

[038] Figure 2 is a block diagram of a base station 210 communicating with a UE 250 in an access network. In the DL, IP packets from the EPC 160 can be provided to a controller / processor 275. The controller / processor 275 implements the functionalities of layers 3 and 2. Layer 3 includes a radio resource control (RRC) layer and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.The 275 controller / processor provides RRC layer functionality associated with broadcast transmission of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), radio access intertechnology mobility (RAT), and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, etc.). Petition 870250095215, dated 10 / 17 / 2025, page 20 / 59 13 / 39 decryption, integrity protection, integrity verification) and transfer support functions; RLC layer functionality associated with the transfer of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs into transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling and prioritization of logical channels.

[039] The 216 transmit processor (TX) and the 270 receive processor (RX) implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical layer (PHY), may include error detection in transport channels, forward error correction (FEC) encoding / decoding of transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The 216 TX processor manages mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams.Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a stream of OFDM symbols in the time domain. The OFDM stream is pre-coded. Petition 870250095215, dated 10 / 17 / 2025, page 21 / 59 14 / 39 spatially to produce multiple spatial streams. Channel estimates from a channel estimator 274 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by UE 250. Each spatial stream can then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX can modulate an RF carrier with a respective spatial stream for transmission.

[040] In UE 250, each receiver 254RX receives a signal through its respective antenna 252. Each receiver 254RX retrieves information modulated on an RF carrier and provides the information to the receiving processor (RX) 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality associated with various signal processing functions. The RX processor 256 can perform spatial processing on the information to retrieve any spatial streams destined for UE 250. If multiple spatial streams are destined for UE 250, they can be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The signal in the frequency domain comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 210. These soft decisions can be based on channel estimates computed by channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by base station 210 on the physical channel. The data and... Petition 870250095215, dated 10 / 17 / 2025, page 22 / 59 15 / 39 control signals are then provided to the controller / processor 259, which implements the functionalities of layers 3 and 2.

[041] The controller / processor 259 can be associated with a memory 260 that stores program codes and data. The memory 260 can be called the computer-readable medium. In the UL, the controller / processor 259 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 259 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[042] Similar to the functionality described in connection with DL transmission by base station 210, controller / processor 259 provides RRC layer functionality associated with system information acquisition (e.g., MIB, SIBs), RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU transfer, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs into TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[043] Channel estimates derived by a 258 channel estimator from a reference or feedback signal Petition 870250095215, dated 10 / 17 / 2025, page 23 / 59 The 16 / 39 transmitted by base station 210 can be used by the TX processor 268 to select the appropriate encoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 268 can be provided to different antennas 252 via separate transmitters 254TX. Each transmitter 254TX can modulate an RF carrier with a corresponding spatial stream for transmission. The UL transmission is processed at base station 210 in a manner similar to that described in connection with the receiver function in UE 250. Each receiver 218RX receives a signal via its respective antenna 220. Each receiver 218RX retrieves information modulated on an RF carrier and provides the information to an RX processor 270.

[044] The controller / processor 275 can be associated with a memory 276 that stores program codes and data. The memory 276 can be called the computer-readable medium. In the UL, the controller / processor 275 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to retrieve IP packets from the UE 250. IP packets from the controller / processor 275 can be supplied to the EPC 160. The controller / processor 275 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[045] New radio (NR) may refer to radios configured to operate under a new air interface (e.g., different from Orthogonal Frequency Division Multiple Access (OFDMA) based air interfaces) or fixed transport layer (e.g., different from Internet Protocol (IP)). NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and may include support for half-duplex operation using time-division duplexing (TDD). NR may include Enhanced Mobile Broadband service. Petition 870250095215, dated 10 / 17 / 2025, page 24 / 59 17 / 39 (eMBB) targeting wide bandwidth (e.g., 80 MHz and beyond), millimeter waves (mmW) targeting high carrier frequency (e.g., 60 GHz), massive MTC (mMTC) targeting backward compatible MTC techniques and / or mission-critical targeting ultra-reliable low-latency communications service (URLLC).

[046] A single-component carrier bandwidth of 100 MHz can be supported. In one example, NR resource blocks (RBs) can span 12 subcarriers with a subcarrier bandwidth of 60 kHz at a duration of 0.25 ms or a bandwidth of 30 kHz at a duration of 0.5 ms (similarly, 50 MHz bandwidth for 15 kHz SCS at a duration of 1 ms). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR slots) with a length of 10 ms. Each slot can indicate a link direction (i.e., DL or UL) for data transmission, and the link direction for each slot can be dynamically switched. Each slot can include DL / UL data as well as DL / UL control data. The UL and DL slots for NR can be as described in more detail below in relation to Figures 5 and 6.

[047] An NR RAN may include a central unit (CU) and distributed units (DUs). An NR BS (e.g., gNB, 5G Node B, Node B, transmit-receive point (TRP), access point (AP)) may correspond to one or more BSs. NR cells may be configured as access cells (ACells) or data-only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) may configure the cells. DCells may be cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or transfer. In some cases, DCells may not transmit synchronization signals (SS); in some cases, DCells may transmit SS. NR BSs may transmit downlink signals to Petition 870250095215, dated 10 / 17 / 2025, page 25 / 59 18 / 39 UEs, indicating the cell type. Based on the cell type indication, the UE can communicate with the NR BS. For example, the UE can determine which NR BSs to consider for cell selection, access, transfer, and / or measurement based on the indicated cell type.

[048] Figure 3 illustrates an example of a distributed RAN logical architecture 300, according to aspects of this disclosure. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be a central unit (CU) of the distributed RAN. The backhaul interface for the next-generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface for neighboring next-generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be called BSs, NR BSs, B Nodes, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with a cell.

[049] TRPs 308 can be a distributed unit (DU). TRPs can be connected to one ANC (ANC 302) or to more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, the TRP can be connected to more than one ANC. A TRP can include one or more antenna ports. TRPs can be configured to serve traffic individually (e.g., dynamic selection) or jointly (e.g., joint transmission) to a UE.

[050] The local architecture of the distributed RAN 300 can be used to illustrate the definition of fronthaul. The architecture can be defined to support fronthaul solutions in different types of deployment. For example, the architecture can be based on the capabilities of the transmission network (e.g., bandwidth, latency, and / or jitter). The architecture can share resources and / or components with LTE. In some aspects, the next-generation AN (NG-AN) 310 can support connectivity. Petition 870250095215, dated 10 / 17 / 2025, page 26 / 59 19 / 39 dual with NR. The NG-AN can share a common fronthaul for LTE and NR.

[051] The architecture can allow cooperation between and between TRPs 308. For example, cooperation can be predefined within a TRP and / or between TRPs via ANC 302. According to some aspects, no interface between TRPs may be required / present.

[052] According to some aspects, a dynamic configuration of split logic functions may be present in the distributed RAN 300 architecture. The PDCP, RLC and MAC protocols can be adaptively placed in the ANC or TRP.

[053] Figure 4 illustrates an example of the physical architecture of a distributed RAN 400, according to aspects of this disclosure. A centralized network unit (C-CU) 402 can host core network functions. The C-CU can be centrally deployed. The functionality of the C-CU can be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle maximum capacity. A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can have distributed deployment. The C-RU can be located closer to the network edge. A distributed unit (DU) 406 can host one or more TRPs. The DU can be located at the network edges with radio frequency (RF) functionality.

[054] Figure 5 is a 500 diagram showing an example of a DL-centered slot. The DL-centered slot may include a 502 control portion. The 502 control portion may exist in the initial or initial portion of the DL-centered slot. The 502 control portion may include various scheduling information and / or control information corresponding to various portions of the DL-centered slot. In some configurations, the 502 control portion may be a physical DL control channel (PDCCH), as indicated in Figure 5. The DL-centered slot may also include Petition 870250095215, dated 10 / 17 / 2025, page 27 / 59 20 / 39 a DL 504 data portion. The DL 504 data portion may sometimes be referred to as the DL-centric slot payload. The DL 504 data portion may include the communication resources used to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE). In some configurations, the DL 504 data portion may be a physical DL shared channel (PDSCH).

[055] The DL-centered slot may also include a common UL 506 portion. The common UL 506 portion may sometimes be referred to as a UL burst, common UL burst, and / or various other suitable terms. The common UL 506 portion may include feedback information corresponding to various other portions of the DL-centered slot. For example, the common UL 506 portion may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and / or various other suitable types of information. The common UL 506 portion may include additional or alternative information such as information pertaining to Random Access Channel (RACH) procedures, Scheduling Requests (SRs), and various other suitable types of information.

[056] As illustrated in Figure 5, the end of the DL 504 data portion can be separated in time from the beginning of the common UL 506 portion. This time separation may sometimes be called a gap, guard period, guard interval, and / or various other suitable terms. This separation provides time for the switching from DL communication (e.g., receive operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). A person skilled in the art will understand that the above is only one example of a DL-centric slot, and alternative structures with similar features may Petition 870250095215, dated 10 / 17 / 2025, page 28 / 59 21 / 39 to exist without necessarily deviating from the aspects described in this document.

[057] Figure 6 is a diagram 600 showing an example of a UL-centered slot. The UL-centered slot may include a control portion 602. The control portion 602 may exist in the initial or initial portion of the UL-centered slot. The control portion 602 in Figure 6 may be similar to the control portion 502 described above with reference to Figure 5. The UL-centered slot may also include a UL data portion 604. The UL data portion 604 may sometimes be called the payload of the UL-centered slot. The UL portion may refer to the communication resources used to communicate UL data from the subordinate entity (e.g., UE) to the escalating entity (e.g., UE or BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).

[058] As illustrated in Figure 6, the end of the control portion 602 can be separated in time from the beginning of the UL data portion 604. This temporal separation may sometimes be called a gap, guard period, guard interval, and / or various other suitable terms. This separation provides time for the switching from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centered slot may also include a common UL portion 606. The common UL portion 606 in Figure 6 may be similar to the common UL portion 506 described above with reference to Figure 5. The common UL portion 606 may additionally or alternatively include information pertaining to the channel quality indicator (CQI), probe reference signals (SRSs), and various other suitable types of information.A person skilled in the art will understand that the above is just one example of a UL-centric slot and that alternative structures with features exist. Petition 870250095215, dated 10 / 17 / 2025, p. 29 / 59 22 / 39 similar examples may exist without necessarily deviating from the aspects described in this document.

[059] In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using side-link signals. Real-world applications of such side-link communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and / or various other suitable applications. Generally, a side-link signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes.In some examples, side link signals can be communicated using licensed spectrum (unlike wireless local area networks, which typically use unlicensed spectrum).

[060] Figure 7 is a diagram 700 illustrating a UE communicating on a non-terrestrial network (NTN). In this example, a UE 704 is communicating with a base station 702 via a satellite 730 and a gateway 740. Furthermore, the UE 704 may be an IoT device.

[061] In the NTN scenario, the round-trip delay between UE 704 and satellite 730 is very large due to the long distance, especially when satellite 730 is in a geostationary orbit with an orbital altitude of 35,000 km. This large round-trip delay significantly reduces the data transfer rate.

[062] To mitigate this impact and save on power consumption, version 18 of 3GPP introduced the feature of Petition 870250095215, dated 10 / 17 / 2025, p. 30 / 59 23 / 39 Disabling HARQ feedback on the downlink (DL). When DL HARQ feedback is disabled, the network (base station 702) can directly schedule the next transmission without waiting for HARQ feedback from UE 704, significantly improving the transmission rate by saving time spent waiting for HARQ feedback.

[063] In the uplink (UL), HARQ mode A and HARQ mode B were introduced. HARQ mode A corresponds to the previous mode with HARQ feedback, where UE 704 sends a packet to the network, and the network sends feedback represented by an uplink grant to UE 704. That is, similar to legacy mode, the network will reschedule UE 704 after receiving the previous UL transmission. The network may instruct UE 704 to retransmit the last UL packet or transmit a new UL packet, depending on the decoding result. Upon receiving a data packet, the base station (BS) will confirm successful reception and send an ACK. If a NACK is sent by the BS, UE will retransmit the same packet.

[064] HARQ B mode, on the other hand, corresponds to the deactivation of HARQ feedback. In HARQ B mode, when the UE 704 sends data to the network, the network can directly schedule the next uplink data before receiving the previous uplink data. Upon receiving the uplink schedule, the UE 704 can directly send the next uplink data packet, even if the previous packet has not yet arrived at the network. This process makes the entire flow more compact, saving time.

[065] When HARQ A / B mode and HARQ feedback disable are adopted, scheduling constraints, such as when to start and stop PDCCH monitoring after UL / DL transmission and when to start the DL / UL HARQ RTT timer or the DRX idle timer, need to be enhanced accordingly. Petition 870250095215, dated 10 / 17 / 2025, p. 31 / 59 24 / 39

[066] In the legacy system, due to the large round-trip delay, UE 704 only read the PDCCH when it arrived in time to receive the next appointment. Now, with the reduced interval, the PDCCH monitoring restrictions also need to be changed accordingly.

[067] To resolve these issues, it is necessary to improve scheduling constraints, specifically PDCCH scheduling constraints and PDCCH monitoring constraints.

[068] Figure 8 is an 800 diagram illustrating communications between an UE 804 and a base station 802. In certain scenarios, the UE 804 is connected to the base station 802 via a terrestrial network. The UE 804 communicates signals directly with a Transmit and Receive Point (TRP) of the base station 802. In certain scenarios, the UE 804 is connected to the base station 802 via an NTN, as illustrated in Figure 7. Furthermore, in this example, the UE 804 may be an NB-IoT device. The UE 804 may have a structure similar to that of the UE 250. The base station 802 may have a structure similar to that of the base station 210.

[069] In an initial configuration, when operating in HARQ B mode, the UE 804 is not expected to receive transmissions during Type B half-duplex guard periods. For Type B half-duplex FDD operation, guard periods, each termed a half-duplex guard subframe, are created by the UE by not receiving a downlink subframe immediately preceding an uplink subframe from the same UE and by not receiving a downlink subframe immediately following an uplink subframe from the same UE. Type B half-duplex guard periods may refer to a specific 1 millisecond (ms) time interval. In NB-IoT, the UE 804 operates in half-duplex mode, not full-duplex mode, therefore it receives 1 ms to switch between uplink and downlink transmissions.

[070] Previously, without HARQ B mode, the UE 804 only read the Petition 870250095215, dated 10 / 17 / 2025, p. 32 / 59 25 / 39 NPDCCH was expected when an uplink grant was anticipated. However, with the introduction of HARQ B mode, UE 804 can read the PDCCH 1 ms after the previous uplink transmission has been sent.

[071] In HARQ B mode, after sending an uplink transmission, the UE 804 waits 1 ms and immediately starts monitoring the NPDCCH. This allows the UE 804 to quickly send the next uplink transmission, significantly reducing the waiting time compared to HARQ A mode.

[072] In HARQ A mode, the UE 804 waits for a longer time, specified as K_mac+3subframes, where K_mac is a value configured by the network. The network cannot send downlink data before this time, therefore there is no need for the UE 804 to monitor the NPDCCH beforehand.

[073] HARQ B mode allocates uplink-downlink switching time and allows for immediate NPDCCH monitoring afterward. This improvement in scheduling constraints allows for faster uplink transmissions and improves overall system efficiency.

[074] This 1 ms interval applies regardless of whether the next received DCI is in N0 or N1 format. In other words, the DCI format that the UE 804 receives next does not affect this 1 ms interval. The N0 and N1 DCI formats are downlink control information formats used to schedule uplink and downlink transmissions, respectively. The N0 DCI format is a specific DCI format used for uplink grant (NPUSCH Scheduling). The N1 DCI format is a specific DCI format used for DL ​​Scheduling (NPDSCH Scheduling). The N1 DCI format is for all NPDSCH (user data and SIBs), except NPDSCH that carry paging and for triggering PRACH (non-contention based). Furthermore, the N1 DCI format can Petition 870250095215, dated 10 / 17 / 2025, page 33 / 59 26 / 39 schedule the HARQ ACK / NACK transmitted in NPUSCH.

[075] Additionally, if the NB-IoT UE 804 is configured with the top-layer parameter 'twoHARQ-ProcessesConfig' and has an NPUSCH transmission terminating in subframe n, one or more of the following options may apply:

[076] UE 804 does not need to receive transmissions during Type B half-duplex guard periods for FDD.

[077] If the corresponding NPUSCH transmission is scheduled by the NPDCCH with DCI format N1 in an NTN service cell, UE 804 is not expected to receive an NPDCCH with DCI format N0 / N1 for the same HARQ process ID in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+Kmac+3.

[078] If the corresponding NPUSCH transmission is scheduled by the NPDCCH with DCI format N0 with upper layer configuration as HARQModeA in an NTN service cell, the UE 804 is not expected to receive an NPDCCH with DCI format N0 / N1 for the same HARQ process ID in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+Kmac+3.

[079] If in a non-NTN service cell, UE 804 is not expected to receive an NPDCCH with DCI format N0 / N1 for the same HARQ process ID as the NPUSCH transmission in any subframe starting from subframe n+1 to subframe n+3.

[080] If the NB-IoT UE 804 is not configured with the top-tier parameter 'twoHARQ-ProcessesConfig', the following conditions apply:

[081] If the NB-IoT UE 804 has an NPUSCH transmission terminating in subframe n, the UE 804 does not need to monitor NPDCCH in any subframe from subframe n+1 to subframe n+3.

[082] If the NB-IoT UE 804 has an NPUSCH transmission scheduled by NPDCCH with DCI N1 format ending in a subframe nor an NTN service cell, the UE 804 does not need to monitor. Petition 870250095215, dated 10 / 17 / 2025, p. 34 / 59 27 / 39 NPDCCH in any downlink subframe that overlaps with the uplink subframe n+1 to subframe n + Kmac+ 3.

[083] If the NB-IoT UE 804 has an NPUSCH transmission scheduled by NPDCCH with DCI format N0 with upper layer configuration as HARQModeA terminating in subframe nor an NTN service cell, the UE 804 does not need to monitor NPDCCH in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+Kmac+3.

[084] If the NB-IoT UE 804 has an NPUSCH transmission scheduled by NPDCCH with DCI N0 format with top-layer configuration as HARQModeB ending in subframe nor an NTN service cell, the UE 804 is not expected to receive transmissions in Type B half-duplex guard periods.

[085] In a second configuration, the NPDCCH monitoring restriction is relaxed for different DCI formats. Specifically, for HARQ B mode, the UE 804 is not expected to receive transmissions in any downlink subframe that overlaps with the uplink subframe n+1 to n+3. This means that after sending an uplink transmission, the UE 804 will only start monitoring the NPDCCH 3 ms later.

[086] If the NB-IoT UE 804 is configured with the top-layer parameter 'twoHARQ-ProcessesConfig' and has an NPUSCH transmission terminating in subframe n, the following may apply:

[087] UE 804 does not need to receive transmissions during Type B half-duplex guard periods for FDD.

[088] If in an NTN service cell the corresponding NPUSCH transmission is scheduled by NPDCCH with DCI N1 format, UE 804 is not expected to receive an NPDCCH with DCI N1 format for the same HARQ process ID in any downlink subframe that overlaps the downlink subframe Petition 870250095215, dated 10 / 17 / 2025, p. 35 / 59 28 / 39 ascending n+1 to subframe n+Kmac+3. Furthermore, UE 804 does not need to monitor the NPDCCH DCI N0 format for the same HARQ process ID in any descending link subframe that overlaps with the ascending link subframe n+1 to subframe n+3.

[089] If in an NTN service cell the corresponding NPUSCH transmission is scheduled by NPDCCH with DCI N0 format with upper layer configuration as HARQModeA, the UE 804 is not expected to receive an NPDCCH with DCI N0 format for the same HARQ process ID in any downlink subframe that overlaps with uplink subframe n+1 to subframe n+Kmac+3. Furthermore, the UE 804 does not need to monitor the NPDCCH DCI N1 format for the same HARQ process ID in any downlink subframe that overlaps with uplink subframe n+1 to subframe n+3.

[090] If in an NTN service cell and the NB-IoT UE 804 has a scheduled NPUSCH transmission by NPDCCH with DCI format N0 with upper layer configuration as HARQModeB ending in subframe n, the UE 804 does not need to monitor the NPDCCH for the same HARQ process ID in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+3.

[091] If in a non-NTN service cell, UE 804 is not expected to receive an NPDCCH with DCI format N0 / N1 for the same HARQ process ID as the NPUSCH transmission in any subframe starting from subframe n+1 to subframe n+3.

[092] If the NB-IoT UE 804 is not configured with the top-tier parameter 'twoHARQ-ProcessesConfig', the following may apply:

[093] If the NB-IoT UE 804 has an NPUSCH transmission ending in subframe n, the UE 804 does not need to monitor NPDCCH in any subframe, starting from subframe n+1 to subframe n+3.

[094] If in an NTN service cell and the NB-IoT UE 804 Petition 870250095215, dated 10 / 17 / 2025, page 36 / 59 If NPDCCH transmission 29 / 39 is scheduled by NPDCCH with DCI N1 format ending in subframe n, UE804 does not need to monitor the NPDCCH DCI N1 format in any downlink subframe that overlaps with the uplink subframe n+1 to subframe n+Kmac+3. Furthermore, UE804 does not need to monitor the NPDCCH DCI N0 format in any downlink subframe that overlaps with the uplink subframe n+1 to subframe n+3.

[095] If in an NTN service cell and the NB-IoT UE 804 has a scheduled NPDCCH transmission with DCI N0 format with upper layer configuration as HARQModeA ending in subframe n, the UE 804 is not expected to receive an NPDCCH with DCI N0 format in any downlink subframe that overlaps with the uplink subframe n+1 to subframe n+Kmac+3. Furthermore, the UE 804 does not need to monitor the DCI N1 NPDCCH format in any downlink subframe that overlaps with the uplink subframe n+1 to subframe n+3.

[096] If in an NTN service cell and the NB-IoT UE 804 has an NPUSCH transmission scheduled by NPDCCH with DCI format N0 with upper layer configuration as HARQModeB terminating in subframe n, the UE 804 does not need to monitor NPDCCH in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+3. Furthermore, the UE 804 is not expected to receive transmissions in Type B half-duplex guard periods.

[097] In a third configuration, the NPDCCH monitoring restriction is relaxed for different DCI formats. Specifically, for HARQ B mode, the UE 804 is not expected to receive transmissions in the Type B halfduplex guard period, which is a 1 ms interval. However, the wait time for the UE 804 differs depending on the received DCI format (N0 or N1). Petition 870250095215, dated 10 / 17 / 2025, p. 37 / 59 30 / 39

[098] If the NB-IoT UE 804 is configured with the top-layer parameter 'twoHARQ-ProcessesConfig' and has an NPUSCH transmission terminating in subframe n, the following may apply:

[099] UE 804 does not need to receive transmissions during Type B half-duplex guard periods for FDD.

[100] If in an NTN service cell the corresponding NPUSCH transmission is scheduled by NPDCCH with DCI N1 format, UE 804 is not expected to receive an NPDCCH with DCI N1 format for the same HARQ process ID in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+Kmac+3.

[101] If in an NTN service cell the corresponding NPUSCH transmission is scheduled by NPDCCH with DCI format N0 with upper layer configuration as HARQModeA, UE 804 is not expected to receive an NPDCCH with DCI format N0 for the same HARQ process ID in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+Kmac+3.

[102] If in a non-NTN service cell, UE 804 is not expected to receive an NPDCCH with DCI format N0 / N1 for the same HARQ process ID as the NPUSCH transmission in any subframe starting from subframe n+1 to subframe n+3.

[103] If the NB-IoT UE 804 is not configured with the top-layer parameter 'twoHARQ-ProcessesConfig', the following may apply:

[104] If the NB-IoT UE 804 has an NPUSCH transmission terminating in subframe n, the UE 804 does not need to monitor NPDCCH in any subframe from subframe n+1 to subframe n+3.

[105] If in an NTN service cell and the NB-IoT UE 804 has an NPUSCH transmission scheduled by NPDCCH with DCI N1 format ending in subframe n, the UE 804 does not need to monitor the NPDCCH DCI N1 format in any subframe of Petition 870250095215, dated 10 / 17 / 2025, pp. 38 / 59 31 / 39 downlink that overlaps the uplink subframe n+1 to subframe n+Kmac+3, and UE 804 does not need to monitor the NPDCCH DCI N0 format during Type B halfduplex guard periods for FDD.

[106] If in an NTN service cell and the NB-IoT UE 804 has a scheduled NPUSCH transmission by NPDCCH with DCI N0 format with top-layer configuration as HARQModeA ending in subframe n, the UE 804 is not expected to receive an NPDCCH with DCI N0 format in any downlink subframe that overlaps the uplink subframe n+1 to subframe n+Kmac+3, and the UE 804 does not need to monitor the DCI N1 NPDCCH format in Type B half-duplex guard periods for FDD.

[107] If in an NTN service cell and the NB-IoT UE 804 has an NPUSCH transmission scheduled by NPDCCH with DCI N0 format with top layer configuration as HARQModeB ending in subframe n, the UE 804 is not expected to receive transmissions in the Type B half-duplex guard periods.

[108] This configuration allows different wait times based on the received DCI format, providing flexibility in restricting NPDCCH monitoring for HARQ B mode in NTN scenarios involving UE 804, base station 802, satellite 730 and gateway 740.

[109] Figure 9 is a diagram 900 illustrating a UE monitoring PDCCH after receiving a PDSCH. In this example, UE 804 receives a PDSCH 935 from base station 802. The last symbol of PDSCH 935 ends at time point t0. Subsequently, an interval period 910 starts at time point t0 and ends at time point t1. At time point t1, a DRX idle timer 930 is started. Subsequently, UE 804 can detect a PDCCH 945.

[110] When DL HARQ feedback is disabled on the UE 804 and it is in connected mode, the UE 804 does not start the Petition 870250095215, dated 10 / 17 / 2025, pp. 39 / 59 32 / 39 DL HARQ RTT timer after receiving a PDSCH. In the legacy system with DL HARQ feedback enabled, the UE initiated a DL HARQ RTT timer. However, if DL HARQ feedback is disabled, the DL HARQ RTT timer is not initiated at the point where it would have originally been initiated. Instead, the UE 804 initiates an XRD idle timer after an interval period.

[111] The DL HARQ RTT timer is not needed when DL HARQ feedback is disabled because the network (base station 802) can directly schedule the next transmission without waiting for UE 804 HARQ feedback. This eliminates the need for the DL HARQ RTT timer, which is used to track the round-trip time for HARQ feedback.

[112] The specific start time of the DRX idle timer is (the subframe containing the last repetition of the corresponding PDSCH reception + 12 subframes + PDCCH offset). The 12 subframes, which are equivalent to 12 ms, are a predefined value that allows sufficient time for the UE 804 to process the received PDSCH before starting the DRX idle timer. The UE 804 may not need to monitor the PDCCH before the start time.

[113] The PDCCH offset, also known as ΔpDccH, is used to align the start of the DRX idle timer with the next PDCCH occasion. PDCCH occasions occur periodically and their duration is configurable. By adding the PDCCH offset, the DRX idle timer starts on the first subframe of the next available PDCCH occasion. In this way, the UE 804 can efficiently monitor the PDCCH for any new downlink assignments.

[114] In the example illustrated in Figure 9, UE 804 receives PDSCH 935 from base station 802, with the last symbol of PDSCH 935 ending at time point t0. The interval period Petition 870250095215, dated 10 / 17 / 2025, pp. 40 / 59 33 / 39 The DRX 930 idle timer, which lasts 12 subframes and includes PDCCH offset, starts at time point tc and ends at time point t1. The DRX 930 idle timer then starts at time point ti, which is aligned with the next PDCCH occurrence. The UE 804 can begin monitoring PDCCH from time point t1. Subsequently, the UE 804 can detect PDCCH 945 during the DRX 930 idle timer.

[115] This enhancement of the DRX idle timer for disabled HARQ DL feedback improves the efficiency of the UE 804 in monitoring PDCCH and reduces unnecessary wait times. This can lead to longer battery life and improved overall system performance.

[116] Figure 10 is a diagram 1000 illustrating a UE monitoring the PDCCH after transmitting a PUSCH. In this example, UE 804 transmits a PUSCH 1035 to base station 802. The last symbol of PUSCH 1035 ends at time point t10. Subsequently, a 1010 interval period begins at time point t10 and ends at time point t11. At time point t11, a DRX 1030 idle timer is initiated. Subsequently, UE 804 can detect a PDCCH 1045.

[117] When UL HARQ B mode is configured on the UE 804 and the UE 804 is in connected mode, the network can schedule the next uplink transmission without waiting for confirmation of previous uplink data from the UE 804. Consequently, the UE 804 does not start the UL HARQ RTT timer after transmitting an uplink transmission. In the legacy system, after transmitting an uplink transmission, the UE 804 waited for an RTT timer before starting the DRX idle timer. The RTT timer and the DRX idle timer were linked, with the DRX idle timer starting upon expiration of the RTT timer.

[118] However, in UL HARQ B mode, the RTT timer Petition 870250095215, dated 10 / 17 / 2025, pp. 41 / 59 34 / 39 is no longer used. Instead, UE 804 starts the DRX idle timer directly after the uplink transmission, with its start time significantly advanced compared to the legacy system. This change aims to reduce wait time and improve PDCCH monitoring efficiency.

[119] The specific start time of the DRX idle timer for UL HARQ B mode is (the subframe containing the last repetition of the corresponding PUSCH transmission + 1 subframe + PDCCH offset). The 1 subframe, which is equivalent to 1 ms and corresponds to the Type B half-duplex guard period, is used to account for the minimum interval between the end of the PUSCH transmission and the start of PDCCH monitoring. This interval is necessary for the UE 804 to switch from the uplink to the downlink and prepare for PDCCH monitoring.

[120] The PDCCH offset, also known as ΔpDccH, is used to align the start of the DRX idle timer with the next PDCCH occasion. PDCCH occasions occur periodically and their duration is configurable. By adding the PDCCH offset, the DRX idle timer starts on the next available PDCCH occasion. In this way, the UE 804 can efficiently monitor the PDCCH for any new downlink assignments or uplink grants.

[121] During the DRX idle timer, the UE 804 monitors the PDCCH. If the timer expires without receiving new transmissions, the UE 804 enters an idle state and stops monitoring the PDCCH, conserving battery life.

[122] In the example illustrated in Figure 10, UE 804 transmits PUSCH 1035 to base station 802, with the last symbol of PUSCH 1035 ending at time point t10. The interval period 1010, which lasts 1 subframe and the offset of PDCCH, Petition 870250095215, dated 10 / 17 / 2025, pp. 42 / 59 35 / 39 starts at time point tio and ends at time point tii. The DRX 1030 idle timer then starts at time point tii, which is aligned with the next PDCCH occasion. The UE 804 can start monitoring PDCCH from time point tii. Subsequently, the UE 804 can detect PDCCH i045 during the DRX i030 idle timer. [i23] This enhancement of the DRX idle timer for UL HARQ B mode improves the efficiency of the UE 804 in monitoring PDCCH and reduces unnecessary wait times, resulting in longer battery life and overall system performance. [i24] Alternatively, the UE 804 can start the DRX i030 idle timer at a different start time when UL HARQ B mode is configured. Instead of starting the timer at (the subframe containing the last repetition of the corresponding PUSCH transmission + i subframe + PDCCH offset), the UE 804 can start the DRX i030 idle timer at (the subframe containing the last repetition of the corresponding PUSCH transmission + 3 subframes + PDCCH offset). [i25] In addition, when UE 804 is configured with HARQ B mode, message 3 of the random access procedure may also include Advance Data Transmission (EDT), UL transmission may be configured by Semi-Persistent Scheduling (SPS) and / or UL transmission may use Pre-configured UL Resource (PUR). [i26] In particular, uplink transmission using SPS can be configured for UE 804 with HARQ B mode. That is, the network can directly schedule the next uplink transmission using SPS without waiting for the decoding result of the previous transmission, thus reducing overall latency and improving system efficiency. [i27] Figure ii is a flowchart ii00 of a method for Petition 870250095215, dated 10 / 17 / 2025, pp. 43 / 59 36 / 39 Uplink signal transmission. The method can be performed by an UE (e.g., UE 804). In operation 1102, the UE transmits a first uplink signal to a network. In operation 1104, the UE starts monitoring downlink control information (DCI) from the network at a point in time that is at least one half-duplex guard period after the first uplink signal transmission is complete. In certain configurations, the half-duplex guard period is 1 millisecond. In certain configurations, the UE does not need to receive transmissions from the network during the half-duplex guard period.

[128] In operation 1106, the UE transmits a second uplink signal to the network without receiving Hybrid Automatic Repeat Request (HARQ) feedback regarding the first uplink signal from the network. In certain configurations, the UE is configured with HARQ mode B for uplink transmissions. In certain configurations, the second uplink signal is transmitted according to a semi-persistent scheduling (SPS) configuration.

[129] In operation 1108, the UE refrains from initiating an uplink (UL) HARQ round-trip time (RTT) timer with the UE configured with discontinuous receive (DRX) in a connected mode.

[130] In operation 1110, the UE starts or restarts a DRX idle timer based on a subframe that completes the transmission of the first uplink signal, plus a predetermined number of subframes and a physical downlink control channel offset (PDCCH). In certain configurations, the predetermined number of subframes is one subframe and the PDCCH offset is an interval that starts at the subframe that completes the transmission of the first uplink signal until the first subframe of a subsequent occasion of Petition 870250095215, dated 10 / 17 / 2025, pp. 44 / 59 37 / 39 PDCCH.

[131] Figure 12 is a 1200 flowchart of a method for monitoring downlink control information (DCI). The method can be performed by a UE (e.g., UE 804). In operation 1202, the UE receives a downlink signal from a network. In operation 1204, the UE refrains from transmitting Hybrid Automatic Repeat Request (HARQ) feedback regarding the downlink signal to the network. In operation 1206, the UE monitors the DCI from the network at a predetermined time point after the downlink signal reception is complete. In certain configurations, the predetermined time is 12 subframes plus a physical downlink control channel (PDCCH) offset.

[132] In operation 1208, the UE refrains from initiating a downlink (DL) HARQ RTT timer when the UE is configured with DRX in connected mode. In operation 1210, the UE initiates or restarts a DRX idle timer based on a subframe that completes downlink signal reception, plus a predetermined number of subframes and a PDCCH offset. In certain configurations, the predetermined number of subframes is 12 subframes and the PDCCH offset is an interval between the subframe that completes downlink signal reception and the first subframe of a subsequent PDCCH occasion.

[133] It is understood that the specific order or hierarchy of the blocks in the disclosed processes / flowcharts is an illustration of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of the blocks in the processes / flowcharts may be rearranged. In addition, some blocks may be combined or omitted. The method claims in the appendix present elements of the various blocks in a sample order and are not limited to the specific order or hierarchy presented. Petition 870250095215, dated 10 / 17 / 2025, pp. 45 / 59 38 / 39

[134] The preceding description is provided to enable anyone skilled in the art to practice the various aspects described in this document. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined in this document may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this document, but are to be granted in their full scope, consistent with language claims, wherein reference to an element in the singular is not intended to mean one and only one, unless specifically indicated, but rather one or more. The word exemplar is used in this document to mean serving as an example, instance, or illustration. Any aspect described in this document as exemplary should not necessarily be interpreted as preferential or advantageous in relation to other aspects.Unless specifically indicated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any of these combinations may contain one or more members of A, B, or C.All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or may become known to those commonly known in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Beyond this, nothing is disclosed. Petition 870250095215, dated 10 / 17 / 2025, pp. 46 / 59 Section 39 / 39 in this document is intended to be dedicated to the public, regardless of whether such disclosure is explicitly mentioned in the claims. The words module, mechanism, element, device, and the like cannot replace the word means. Thus, no element of the claim should be interpreted as a means plus function unless the element is expressly mentioned using the phrase means for. Petition 870250095215, dated 10 / 17 / 2025, pp. 47 / 59

Claims

1 / 4 CLAIMS 1. A wireless communication method by a user equipment (UE), characterized in that it comprises: transmitting a first uplink signal to a network; initiating monitoring of downlink control information (DCI) from the network at a point in time that is at least one half-duplex guard period after completion of the transmission of the first uplink signal; and transmitting a second uplink signal to the network without receiving Hybrid Automatic Repeat Request (HARQ) feedback relating to the first uplink signal from the network.

2. Method according to claim 1, characterized in that the half-duplex guard period is 1 millisecond.

3. Method according to claim 1, characterized in that the UE is configured with HARQ B mode for uplink transmissions.

4. Method according to claim 3, characterized in that the second uplink signal is transmitted according to a semi-persistent scheduling (SPS) configuration.

5. Method, according to claim 1, characterized in that the UE is not required to receive transmissions from the network during the half-duplex guard period.

6. Method according to claim 1, characterized in that it further comprises: refraining from initiating an uplink (UL) HARQ round-trip timer (RTT) with the UE configured with discontinuous receive (DRX) in a connected mode.

7. Method according to claim 6, characterized in that it further comprises: Petition 870250090129, dated 10 / 03 / 2025, page 18 / 22 2 / 4 initiating or restarting an XDR idle timer based on a subframe completing the transmission of the first uplink signal plus a predetermined number of subframes and a physical downlink control channel offset (PDCCH).

8. Method, according to claim 7, characterized in that the predetermined number of subframes is a subframe and the PDCCH offset is an interval that begins at the subframe that concludes the transmission of the first uplink signal to a first subframe of a subsequent PDCCH occasion.

9. A wireless communication method by a user equipment (UE), characterized in that it comprises: receiving a downlink signal from a network; refraining from transmitting Hybrid Automatic Repeat Request (HARQ) feedback on the downlink signal to the network; and monitoring downlink control information (DCI) from the network at a predetermined time point after the downlink signal reception is complete.

10. Method according to claim 9, characterized in that the predetermined time is 12 subframes plus a physical downlink control channel shift (PDCCH).

11. Method according to claim 9, characterized in that it further comprises: refraining from initiating a downlink (DL) HARQ round-trip time (RTT) timer when the UE is configured with discontinuous receive (DRX) in a connected mode.

12. Method, according to claim 11, characterized in that it further comprises: initiating or restarting a DRX idle timer Petition 870250090129, dated 10 / 03 / 2025, page 19 / 22 3 / 4 based on a subframe completing the reception of the downlink signal plus a predetermined number of subframes and a PDCCH offset.

13. Method, according to claim 12, characterized in that the predetermined number of subframes is 12 subframes and the PDCCH offset is an interval from the subframe that concludes the reception of the downlink signal to a first subframe of a subsequent PDCCH occasion.

14. Wireless communication apparatus, the apparatus being a user equipment (UE), characterized in that it comprises: a memory; and at least one processor coupled to the memory and configured to: transmit a first uplink signal to a network; initiate monitoring of downlink control information (DCI) from the network at a point in time that is at least one half-duplex guard period after completion of the transmission of the first uplink signal; and transmit a second uplink signal to the network without receiving Hybrid Automatic Repeat Request (HARQ) feedback with respect to the first uplink signal from the network.

15. Device according to claim 14, characterized in that the half-duplex guard period is 1 millisecond.

16. Device according to claim 14, characterized in that the UE is configured with HARQ B mode for uplink transmissions.

17. Device according to claim 16, characterized in that the second uplink signal is transmitted according to a semi-persistent (SPS) scheduling configuration.

18. Device, according to claim 14, characterized in that the UE is not required to receive transmissions from the network during the half-duplex guard period.

19. Device according to claim 14, characterized in that at least one processor is further configured to: refrain from initiating an uplink (UL) HARQ round-trip time (RTT) timer with the UE configured with discontinuous receive (DRX) in a connected mode.

20. Device, according to claim 19, characterized in that at least one processor is further configured to: initiate or restart a DRX idle timer based on a subframe completing the transmission of the first uplink signal plus a predetermined number of subframes and a physical downlink control channel offset (PDCCH). Petition 870250090129, dated 10 / 03 / 2025, pp. 21 / 22

Images