Resumption of discontinuous reception cycle synchronization

Abstract

A UE can be configured to receive, from a base station, consecutive DCI messages that include respective indicator values that are equal, each of which indicates an association with one of a new transmission or a retransmission. The UE can be further configured to remain in a wake state for at least a portion of a scheduled sleep state of a DRX cycle scheduled by the base station based on the respective indicator values being equal across the consecutive DCI messages. A base station can be configured to transmit, to a UE, a DCI message indicating a set of resources allocated to the UE for a transmission, and transmit, to the UE, data to synchronize the DRX cycle with the UE based on an absence of the transmission in the set of resources allocated to the UE.

Description

[0001] Cross-reference of related applications

[0002] This application claims the benefit of U.S. Provisional Application S / N.63 / 201,450, filed April 29, 2021, entitled “RECOVERY OF DISCONTINUOUSRECEPTION CYCLE SYNCHRONIZATION,” and U.S. Patent Application No. 17 / 456,869, filed November 29, 2021, entitled “RECOVERY OF DISCONTINUOUSRECEPTION CYCLE SYNCHRONIZATION,” the disclosures of which are expressly incorporated herein by reference in their entirety. background Technical Field

[0004] This disclosure generally relates to communication systems, and more particularly to discontinuous reception cycles that can be configured by a base station for a user equipment (UE).

[0005] introduction

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0007] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband, promulgated by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them.

[0008] Overview

[0009] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify the key or decisive elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as an introduction to the more detailed description that follows.

[0010] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be user equipment (UE) or a component thereof, configured to: receive from a base station a coherent downlink control information (DCI) message comprising equal corresponding indicator values, each of which indicates association with a new transmission or retransmission. The apparatus may be further configured to: maintain at least a portion of a scheduled sleep state for a discontinuous reception (DRX) cycle scheduled by the base station in an awake state based on the equality of corresponding indicator values ​​across coherent DCI messages.

[0011] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a base station or a component thereof, configured to: transmit to a UE a DCI message indicating a resource set allocated to the UE for transmission; and transmit to the UE data for cyclically synchronizing the DRX with the UE based on the absence of the transmission in the resource set allocated to the UE.

[0012] To achieve the foregoing and related objectives, these one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of these one or more aspects are set forth in detail in the following description and drawings. However, these features merely indicate a few of the various ways in which the principles of these various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. Brief description of the attached diagram

[0014] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0015] Figure 2A This is an example illustration of the first frame explaining various aspects of this disclosure.

[0016] Figure 2B This is a diagram illustrating an example of a downlink channel within a subframe according to various aspects of this disclosure.

[0017] Figure 2C This is an example illustration of the second frame explaining various aspects of this disclosure.

[0018] Figure 2DThis is a diagram illustrating an example of an uplink channel within a subframe according to various aspects of this disclosure.

[0019] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0020] Figure 4 This is a diagram illustrating an example of a UE operating with discontinuous reception (DRX) based on configurations made by the base station.

[0021] Figure 5 This is an example call flow diagram of a base station and a UE that explains how to reduce or prevent the frequency of UE loss of control information when operating in DRX mode.

[0022] Figure 6 This is a flowchart of a method for wireless communication at the UE.

[0023] Figure 7 This is a flowchart of a method for conducting wireless communication at a base station.

[0024] Figure 8 This is a diagram illustrating an example of the hardware implementation of the example device.

[0025] Figure 9 This is a diagram illustrating another example of the hardware implementation of another example device.

[0026] Detailed description

[0027] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent only the configurations in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, those skilled in the art will recognize that these concepts and related aspects can be implemented without some or all of these specific details. In some instances, well-known structures, components, etc., are shown in block diagram form to avoid obscuring such concepts.

[0028] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and explained in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" including 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, computer-executable code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0030] Accordingly, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or computer-executable code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of being used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0031] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0032] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation Radio Access Network (RAN) (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio channel cryptography and cryptography decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages.

[0033] In some respects, base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) on third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184, and third backhaul link 134 can be wired, wireless, or a combination thereof. At least some base stations 102 can be configured for Integrated Access and Backhaul (IAB). Accordingly, such base stations can wirelessly communicate with other base stations (which can also be configured for IAB).

[0034] At least some of the base stations 102 configured for IAB may have a split architecture, including at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a remote radio headend (RRH), and / or a remote unit, some or all of which may be co-located or distributed, and / or able to communicate with each other. In some configurations of such a split architecture, the CU may implement some or all of the functionality of the Radio Resource Control (RRC) layer, while the DU may implement some or all of the functionality of the Radio Link Control (RLC) layer.

[0035] Explained, some base stations 102 configured for IAB can communicate with the DU of an IAB donor node or other parent IAB node (e.g., a base station) via a corresponding CU, and further, can communicate with child IAB nodes (e.g., other base stations) and / or one or more UEs 104 via a corresponding DU. One or more base stations 102 configured for IAB can be IAB donors connected via a CU to at least one of EPC 160 and / or core network 190. Through such connections to EPC 160 and / or core network 190, a base station 102 operating as an IAB donor can provide links to EPC 160 and / or core network 190 to one or more UEs and / or other IAB nodes, which can be directly or indirectly connected to the IAB donor (e.g., more than one hop away from the IAB donor). In the context of communicating with EPC 160 or core network 190, both the UE and the IAB node can communicate with the DU of the IAB donor. In some additional aspects, one or more base stations 102 may be configured with connectivity in an Open RAN (ORAN) and / or a Virtualized RAN (VRAN), which can be achieved through at least one corresponding CU, DU, RU, RRH and / or remote unit.

[0036] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110 (which may also be referred to as a "cell"). Potentially, two or more geographic coverage areas 110 may at least partially overlap, or one geographic coverage area 110 may contain another geographic coverage area. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved B Node (eNB) (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0037] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The radio link may be on one or more carriers or component carriers (CCs). For each carrier allocated in a total of up to Y x MHz (e.g., x CCs) of carriers used for transmission in each direction, base station 102 and / or UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., Y may be equal to or approximately equal to 5, 10, 15, 20, 100, 400, etc.). These CCs may or may not be adjacent to each other. The allocation of CCs may be asymmetric with respect to the downlink and uplink (e.g., more or fewer CCs may be allocated to the downlink compared to the uplink).

[0038] A carrier cluster (CC) may include a primary CC and one or more secondary CCs. The primary CC may be referred to as the primary cell (PCell), and each secondary CC may be referred to as a secondary cell (SCell). A PCell may also be referred to as the "serving cell" when the UE is known to both a base station at the access network level and at least one core network entity (e.g., AMF and / or MME) at the core network level, and the UE can be configured to receive downlink control information in that access network (e.g., the UE may be in an RRC connected state). In some instances where carrier aggregation is configured for the UE, each of the PCell and one or more SCells may be the serving cell.

[0039] Some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use downlink / uplink WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0040] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum of 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0041] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can enhance access network coverage and / or increase access network capacity.

[0042] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz band.” Similar naming issues sometimes arise regarding FR2. Although different from the Extremely High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” (mmW) band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as “millimeter wave” (or “mmWave” or simply “mmW”) in various documents and articles.

[0043] In light of the foregoing, unless otherwise stated, for the purposes of this document, the terms "sub-6GHz," "sub-7GHz," etc., may broadly refer to frequencies less than 6GHz, frequencies less than 7GHz, frequencies within FR1, and / or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise stated, for the purposes of this document, the term "millimeter wave" and other similar references may broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, and / or frequencies within the EHF band.

[0044] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave frequencies or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0045] Base station 180 may transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more reception directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 may receive beamformed signals from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission and reception directions of base station 180 may be the same or different. The transmission and reception directions of UE 104 may be the same or different.

[0046] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, MBMS Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0047] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are delivered via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0048] Base stations may include and / or be referred to as gNB, B-node, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, oil pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0049] Refer again Figure 1 In some respects, UE 104 may particularly include a receiving component 198a and a DRX cyclic component 198b, and base station 102 / 180 may particularly include a transmission component 199a and a DRX synchronization component 199b. The receiving component 198a of UE 104 may be configured to receive from base station 102 / 180 a coherent DCI message comprising equal corresponding indicator values, each of which indicates an association with either a new transmission or a retransmission. The DRX cyclic component 198b of UE 104 may be configured to maintain at least a portion of the scheduled sleep state for a DRX cycle scheduled by the base station in an awake state based on the equality of corresponding indicator values ​​across coherent DCI messages.

[0050] The transmission component 199a of base station 102 / 180 can be configured to transmit a DCI message to UE 104 indicating a resource set allocated to the UE for transmission. The DRX synchronization component 199b of base station 102 / 180 can be configured to transmit data to UE 104 to synchronize the DRX cycle with UE 104 based on the absence of the transmission in the resource set allocated to UE 104.

[0051] While this disclosure may focus on 5G NR, the concepts and aspects described herein are applicable to other similar fields, such as LTE, LTE-A Advanced, Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other wireless / radio access technologies.

[0052] Figure 2A This is a diagram 200 illustrating an example of the first subframe within the 5G NR frame structure. Figure 2B Figure 230 is an example illustrating the downlink channel within a 5G NR subframe. Figure 2C This is a diagram 250 illustrating an example of the second subframe within the 5G NR frame structure. Figure 2D Figure 280 illustrates an example of an uplink channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either downlink or uplink; or it can be Time Division Duplex (TDD), where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both downlink and uplink. Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly downlink) and subframe 3 is configured with slot format 34 (mostly uplink), where D is downlink, U is uplink, and F is for flexible use between downlink and uplink. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all downlink and all uplink, respectively. Other slot formats 2-61 include downlink, uplink, and a mixture of flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via Downlink Control Information (DCI) or semi-statically / statically configured via RRC signaling). Note that the following description also applies to 5G NR frame structures for TDD.

[0053] Other wireless communication technologies may have different frame structures and / or different channels. A frame (e.g., a 10-millisecond (ms) frame) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the downlink may be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the uplink may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 symbols per subframe. μ Each time slot. The subcarrier spacing and symbol length / duration vary depending on the design parameters. The subcarrier spacing can be equal to 2. μ *15 kHz, where μ is the parameter design from 0 to 4. Thus, parameter design μ = 0 has a subcarrier spacing of 15 kHz, while parameter design μ = 4 has a subcarrier spacing of 240 kHz. Symbol length / duration is inversely correlated with subcarrier spacing. Figures 2A to 2D Examples are provided for a slot configuration of 0 with 14 symbols per slot and a parameter design of μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs). Within the frame set, there may be one or more different bandwidth portions (BWPs) that are frequency-division multiplexed (see [link to relevant documentation]). Figure 2B Each BWP can have specific parameter designs.

[0054] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) extending 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0055] like Figure 2AAs explained, some REs carry at least one pilot signal for the UE, such as a reference signal (RS). Broadly speaking, RS can be used for beam training and management, tracking and localization, channel estimation, and / or other such purposes. In some configurations, RS may include at least one demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x (where 100x is the port number, but other DM-RS configurations are possible) and / or at least one Channel State Information (CSI) RS (CSI-RS). In some other configurations, the RS may additionally or alternatively include at least one Beam Measurement (or Management) RS (BRS), at least one Beam Refinement RS (BRRS), and / or at least one Phase Tracking RS (PT-RS).

[0056] Figure 2B Examples of various downlink channels within a frame's subframes are explained. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in OFDM symbols. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). Additional BWPs can be located at higher and / or lower frequencies spanning the channel bandwidth. The Primary Synchronization Signal (PSS) is located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and radio frame timing. Based on the Physical Layer Identity and Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can logically group with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as the System Information Block (SIB)), and paging messages.

[0057] like Figure 2CAs explained, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and on the specific PUCCH format used. The UE can transmit a probe reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the uplink.

[0058] Figure 2D Examples of various uplink channels within a frame's subframes are explained. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), which may include a scheduling request (SR), channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) / negative acknowledgment (NACK) feedback. The PUCCH carries data and may additionally be used to carry buffer status report (BSR), power clearance report (PHR), and / or UCI.

[0059] Figure 3This is a block diagram showing the communication between base station 310 and UE 350 in the access network. In the downlink, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 2 (L2) and Layer 3 (L3) functionality. L3 includes the RRC layer, and L2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, RLC layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, 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 MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0060] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 (L1) functionality associated with various signal processing functions. L1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation 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 decoded 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., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from reference signals and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0061] At UE 350, each receiver 354RX receives signals via at least one corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement L1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by base station 310 on the physical channel. This data and control signals are then provided to controller / processor 359, which implements L3 and L2 functionality.

[0062] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the uplink, the controller / processor 359 provides demultiplexing, packet reassembly, cipher decoding, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0063] Similar to the functionality described in conjunction with downlink transmissions performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (cryptography, cryptographic decoding, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, 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 MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0064] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0065] Uplink transmissions are handled at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via at least one corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0066] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the uplink, the controller / processor 375 provides demultiplexing, packet reassembly, cipher decoding, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0067] In some respects, at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to... Figure 1 The receiving component 198a and / or the DRX loop component 198b are combined in various aspects.

[0068] In some other respects, at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to... Figure 1 The various aspects of the combination of the transmission component 199a and / or the DRX synchronization component 199b.

[0069] Figure 4 Figure 400 illustrates an example of DRX operation for a link between base station 402 and UE 404. This link can be a Uu link, such as with an LTE and / or 5G NR access network. In addition to reducing signaling overhead and network interference (e.g., improved signal-to-noise ratio), DRX operation can also save power at UE 404 by reducing the amount of signaling involved.

[0070] In some aspects, base station 402 can configure at least one DRX cycle for UE 404. Accordingly, base station 402 can transmit DRX configuration 406, which can indicate the at least one DRX cycle to UE 404. For example, base station 402 can transmit information configuring various parameters or other values ​​that can be applied to UE 404 to synchronize the DRX cycle with the expected DRX cycle of UE 404 tracked by base station 402. Specifically, DRX configuration 406 can indicate at least one of the following: start duration 412, 422, inactive timer 444, round-trip time (RTT) timer 440, retransmission (ReTx) timer 442, long DRX cycle 410, short DRX cycle 420, and / or other such information. Some of the aforementioned timers can trigger a transition by UE 404 between an active wake-up state (e.g., where UE 404 monitors and receives downlink transmissions) and an inactive sleep state (e.g., where UE 404 suppresses decoding downlink resources).

[0071] UE 404 may be configured with at least one of a long DRX cycle 410 and a short DRX cycle 420. For example, the long DRX cycle 410 may be 10ms-40240ms. The long DRX cycle 410 may include an on duration 412 and a off portion 414, during which UE 404 is permitted to monitor the control channel (e.g., PDCCH), and during the off portion 414, UE 404 may not monitor the control channel. For example, during the off portion 414, UE 404 may reduce or disable a circuit system and / or other components—specifically, the receiver circuit system or other circuit systems used for monitoring, amplifying, converting, etc., of received signaling.

[0072] When UE 404 is configured to operate in at least one of DRX cycles 410 and 420, and UE 404 is connected to base station 402, the operating mode of UE 404 can be connected mode DRX (C-DRX). For example, when UE 404 and base station 402 are in RRC connected state, UE 404 can operate in C-DRX if UE 404 can be assigned uplink permission indicated to UE 404 on the control channel.

[0073] If base station 402 intends to transmit data to UE 404 on a downlink data channel (e.g., PDSCH), base station 402 may first schedule the data on downlink data channel resources and transmit such scheduling information to UE 404 in control information 430 (which may be a DCI message). UE 404 may be configured to monitor the downlink control channel (e.g., PDCCH) to detect downlink control information 430 and identify resources of the downlink data channel scheduled to carry data intended for UE 404. For example, UE 404 may periodically monitor the downlink control channel, for example, at PDCCH timings.

[0074] To elicit uplink grant and request base station 402 to allocate resources for uplink transmission, UE 404 can transmit SR 428. Specifically, data may arrive at a lower layer of UE 404 (e.g., L2, such as MAC), where the data can be buffered, and an SR procedure is triggered for UE 404. In this SR procedure, UE 404 can transmit SR 428 and wait for uplink grant, which can be included in control information 430. If the arrival of uplink data from a higher layer coincides with the closing portion of long DRX cycle 410 or the closing portion 424 of short DRX cycle 420, UE 404 can transition from an inactive state to an active state to find grant in response to the SR transmission.

[0075] In response to SR 428, base station 402 may transmit control information 430 (e.g., DCI), which may indicate permission to include resources allocated to UE 404 on the uplink (data) channel for transmitting uplink data pending and buffered at UE 404. Potentially, base station 402 may also transmit certain control information to UE 404 regarding downlink data, as base station 402 may assume that UE 404 will wake up for a sufficient period of time to receive downlink data during inactive timers.

[0076] UE 404 can locate control information 430 (and grant) by decoding information about the resources of the control channel; however, such decoding may be blind decoding. For this blind decoding, UE 404 (continuously) attempts to decode any information about the control channel that might constitute a grant for UE 404 using UE 404's Radio Network Temporary Identifier (RNTI) to evaluate Cyclic Redundancy Check (CRC) or other similar data integrity / security checks. If the check using UE RNTI passes, the information about the control channel is intended for use by UE 404. If this check using UE RNTI fails, the UE stops decoding information about the control channel.

[0077] Potentially, UE 404 may fail to receive control information 430, for example, because UE 404 misses control information 430, or because, in cases where UE 404 expects control information 430 to include permission in response to SR 428, base station 402 misses SR 428 or is unable to allocate resources to UE 404 in response to SR 428. Where control information 430 provides aspects of uplink permission to UE 404, if UE 404 misses control information 430, UE 404 may not be able to transmit pending data on the permitted resources, because UE 404 will not know which resources have been allocated to UE 404. Where control information 430 schedules aspects of downlink data transmission, if UE 404 misses control information 430, UE 404 may not be able to decode information about the scheduled downlink data channel resources, because UE 404 may not know which downlink data channel resources are carrying data intended for UE 404.

[0078] In some instances, such as when some uplink data remains pending for a period of time after an SR transmission, UE 404 can be configured to retransmit the SR. For example, SR retransmission may depend on whether the data is a pending uplink transmission (and whether the SR disable timer is running), but SR transmission may be independent of whether any permission has been received.

[0079] In some respects, UE 404 can be configured with an SR disable timer to define the duration after the transmission of SR 428 before retransmitting the SR if the earlier SR was not acknowledged. If UE 404 does not receive permission for uplink transmission in response to SR 428, UE 404 may retransmit the SR when the SR disable timer expires—although UE 404 may not necessarily need to retransmit the SR (e.g., when pending uplink data has a relatively low priority). SR retransmission assumes that UE 404 has not yet met (e.g., met or exceeded) the maximum number of SR retransmission attempts.

[0080] In some respects, UE 404 can initiate an RTT timer 440 for the HARQ procedure of a transmission. If the transmission is an uplink transmission (such as SR), the RTT timer 440 can be started at the end of the uplink transmission. If the transmission is a downlink transmission, the RTT timer 440 can be started at the end of the ACK / NACK procedure for the downlink transmission. The RTT timer 440 can measure the amount of time until UE 404 wants to monitor permission or scheduling information for retransmission. UE 404 can start a ReTX timer 442 to monitor the window during which permission or scheduling for retransmission can be received.

[0081] If UE 404 receives control information for retransmission, UE 404 can restart RTT timer 440 and monitor control information again while ReTx timer 442 is running. Because control information for retransmission (e.g., scheduling information and / or permission) does not restart inactive timer 444, RTT timer 440 and / or retransmission timer 442 can run while UE 404 is in a short DRX cycle. UE 404 can monitor control information retransmission during short DRX cycle 420, even if UE 404 is not in the on-duration 422.

[0082] Figure 5 This describes the call flow diagram 500 of base station 502 and UE 504, configured to restore DRX loop synchronization to avoid missing control information. While UE 504 is operating in a DRX loop, a shutdown portion can be interrupted whenever uplink data arrives at UE 504's lower layers (e.g., L2). The arrival of such uplink data can trigger an SR transmission procedure, which in turn can trigger UE 504 to exit the DRX loop and transmit data upon receiving control information with uplink permission for UE transmission.

[0083] When in an active state, triggered as part of an SR procedure or scheduled as part of a UE DRX cycle, base station 502 may transmit downlink data to UE 504 before the inactive timer expires, such as remaining data that base station 502 could not schedule during the previous open period. Upon the expiration of the inactive timer, and with any further scheduling of downlink data or permission granted for uplink data prohibited, UE 504 may transition to the closed portion of the DRX cycle, where a circuitry of UE 504 (e.g., the receiver circuitry) may be in a sleep / inactive state.

[0084] As described above, for the SR procedure, base station 502 can transmit control information indicating uplink grant to UE 504, which may be associated with a specific carrier and HARQ procedure. The control information may further include a parameter labeled "New Data Indicator" (NDI), which may carry a bit value indicating whether the current grant is for an associated HARQ procedure as part of a retransmission or for a new transmission. In an ideal communication environment, the NDI bit value will switch between each control information transmission (e.g., for a downlink data channel or for an uplink data channel) to indicate successful communication that does not require retransmission.

[0085] In other words, the NDI value in each control message will be switched for each new HARQ MAC TB that base station 502 is about to transmit (on the downlink) or is expected to transmit (on the uplink). However, in a non-ideal situation, some retransmissions may occur, in which case the NDI value will not be switched. Instead, base station 502 can keep the NDI value the same across consecutive control message messages, where subsequent control message messages have the same NDI value as the original control message indicating the retransmission. In some aspects, base station 502 may additionally configure zero (0), two (2), three (3), or one (1) redundant versions (RV) for retransmission, which can be indicated in the control message(s) for retransmission, enabling base station 502 to perform soft combination.

[0086] Each control information message may further indicate a value corresponding to the modulation and coding scheme (MCS) to be used in the transmission or retransmission. Some MCS values ​​may be reserved for retransmission. For example, a reserved MCS value may indicate that the same MCS as that previously indicated in an earlier control information message for this transmission (retransmission) will be used or is intended to be used. Thus, the UE 504 can be informed how to transmit or receive through the various fields of the control information message.

[0087] However, UE 504 may lack a mechanism for efficient recovery from instances where control channel messages are missed. Instead, if UE 504 misses a control message, the UE may experience one or more poor decodings of subsequent control information messages. Such poor decoding and other related errors can significantly increase the latency of the SR procedure.

[0088] In some networks, for example, control information messages can be simply assumed to be (almost) completely reliable because they can be transmitted with fewer bits, higher spectral efficiency, and / or more protection compared to other messages, such as data messages. This assumption ignores the scenario where UE 504 actually misses a control information message, in which case the NDI value would be switched across the control information message transmitted by UE 545, but would be treated as unswitched by UE 504 (because UE 504 missed the message with the switched value).

[0089] Explained, base station 502 may transmit DCI0 524 to UE 504. DCI0 524 may include an NDI value of 0 and an RV value of 0 for a new transmission on HARQ procedure 0. The NDI value may match the NDI value expected by UE 504, and therefore the UE may continue to use DCI0 524, for example, it may indicate to UE 504 that it can grant permission for transmission or schedule downlink data that UE 504 can receive. UE 504 may then expect a DCI with an NDI value of 1 on HARQ procedure 1.

[0090] Base station 502 may subsequently transmit DCI1 528 with a switched NDI value for a new MAC transmission (e.g., a new HARQ MAC TB). However, UE 504 may not be able to receive the next DCI1 528. For example, UE 504's DRX cycle may be out of sync with the UE DRX cycle tracked by base station 502, and base station 502 may have already transmitted the next DCI1 528 while UE 504 is in an inactive / sleep state (such as during which UE 504 may not be able to monitor the closed portion of the downlink control channel's DRX cycle for DCI messages).

[0091] Base station 502 can attempt a retransmission by transmitting DCI2 530. In DCI2 530, the NDI value can be switched from DCI0 525 instead of DCI1528. Therefore, if DCI2 carries uplink permission and does not include the MCS value reserved for retransmission, UE 504 can use DCI2 530 for uplink transmission. In such a case, UE 504 can simply treat DCI2 530 as permission for the new HARQ MAC TB, even if base station 502 intended to use DCI2 530 for retransmission.

[0092] However, as explained, UE 504 may fail to receive DCI2 530. For example, UE 504's DRX cycle may be out of sync with the UE DRX cycle tracked by base station 502, and this may be delayed on each DCI transmission where base station 502 transmits a DCI with an NDI value switched from DCI0 524. Depending on various implementations and / or other factors, base station 502 may attempt zero or more (e.g., three) retransmissions of the DCI message, and if all UEs 504 miss all initial transmissions and those zero or more retransmissions, base station 502 may proceed to other operations.

[0093] For example, base station 502 may proceed to the next MAC HARQ TB, for example, to prevent latency accumulation. Since the next MAC HARQ TB may be associated with a new transmission, base station 502 may switch the NDI value from 1 to 0. Base station 502 may then transmit DCI3 534, which includes an NDI value of 0 and an RV value of 0 for the new MAC HARQ TB used for HARQ procedure 0. While base station 502 is switching the NDI value across the DCI associated with the new transmission, UE 504 may have last received DCI0 524 with an NDI value of 0. Therefore, UE 504 may expect a DCI with an NDI value of 1. Thus, UE 504 may treat DCI3 534 as an error or poor decoding upon receiving this message from base station 502.

[0094] Similarly, in another example, base station 502 may transmit DCI4 536 to UE 504 after UE 504 discards DCI3 534. DCI4 536 may include an NDI value that was not switched from DCI3 534 and may include an RV of 2, both of which can indicate to UE 504 that DCI4 536 is for retransmission. Furthermore, DCI4 536 may include an MCS value to be used for retransmission. Some MCS values ​​may correspond to reserved values, one or more of which may be functionally equivalent to indicating the same MCS as the new transmission. However, if UE 504 misses a DCI for a new transmission or interprets a DCI for a new transmission as a DCI for a retransmission, UE 504 may not be able to determine which MCS value to use. Therefore, UE 504 may discard DCI4 536. Alternatively, if the MCS value is not preserved, UE 504 can use DCI4 536—for example, UE 504 can treat DCI4 536 as an authorization for a new transmission.

[0095] In the existing system, the UE will treat consecutive messages with the same NDI value as an error condition that the UE is not prepared to resolve. Instead, UE 504 will discard the DCI message and continue operating as if the UE has not yet been provided with permission to transmit uplink data or scheduling information to receive downlink data.

[0096] Because of such operations, the UE can resume its DRX cycle (e.g., when an inactive timer expires), which may have become out of sync with the UE DRX cycle tracked at base station 502. Therefore, if base station 502 transmits DCI intended for UE 504 while UE 504 is operating in an inactive / sleep state, there is a possibility that UE 504 may miss control information again. Such situations can further exacerbate the latency and other error conditions experienced by UE 504.

[0097] In contrast, the UE of this disclosure can be configured to determine that consecutive DCI messages include equal corresponding NDI values, and furthermore, the UE can determine that such commonality indicates that UE 504 has missed at least one DCI message from base station 502. UE 504 can be configured to recover from a situation in which UE 504 has missed one or more DCI messages, resulting in poor decoding of some subsequent DCI messages. Specifically, UE 504 can be configured to remain awake for at least a portion of the scheduled sleep state of the DRX cycle scheduled by base station 502 based on the equal corresponding indicator values ​​across consecutive DCI messages DCI0 524 and DCI3 534.

[0098] In other words, UE 504 can autonomously extend the time it operates in an active or wake-up state in response to detecting an error condition that could be caused by poor decoding of the DCI. UE 504 can do this based on the assumption that the DCI is missed due to the loss of DRX cycle synchronization, which results in UE 504 being in an inactive / sleep state when base station 502 believes that UE 504 should be in a wake-up / active state (and therefore monitoring the downlink control channel at periodic intervals). By autonomously extending the DRX cycle, UE 504 can eliminate the risk of missing the DCI when UE 504 is in a sleep state.

[0099] By remaining in an awake state, UE 504 can attempt to synchronize its DRX cycle with base station 502. Potentially, UE 504 can synchronize its DRX cycle with base station 502 while remaining awake for at least a portion of a scheduled sleep state. UE 504 can cause base station 502 and UE 504 to begin measuring DRX inactivity timers and / or DRX start duration timers from a common starting point. For example, UE 504 can transmit messages mutually understood by both base station 502 and UE 504 to initiate a timer that causes UE 504 to enter an inactive state or otherwise initiate a DRX cycle upon its expiration, or UE 504 can withhold or delay any messages affecting another timer upon receiving a message from base station 502 that triggers UE 504 to enter an inactive state or otherwise initiate a DRX cycle upon its expiration.

[0100] Explained, UE 504 may communicate some active data to base station 502 during an autonomously extended wake-up state, which may include data that restarts the DRX inactive timer. While the DRX inactive timer is running, UE 504 may suppress any operations that affect the DRX inactive timer. The SR procedure can serve as a unified starting point that is understood by both UE 504 and base station 502 as initiating a DRX inactive timer for UE 504. When the DRX inactive timer expires, UE 504 may transition to a sleep or inactive state, or UE 504 may otherwise initiate a DRX cycle. By means that UE 504 and base station 502 have a shared trigger (e.g., the SR procedure) for calculating the timer duration and DRX cycle initiation for UE 504 from which it originates, the DRX cycle occurring at UE 504 will be synchronized with the tracking of such a DRX cycle for UE 504 at base station 502.

[0101] Ultimately, base station 502 can reach the upper limit threshold for retransmitted DCIs with the same NDI value, and base station 502 can advance to a new HARQ MAC TB. At this point, base station 502 can transmit DCI5 540, which can be a DCI for the new retransmission and therefore can include the handover NDI value. UE 504 can receive DCI5 540 from base station 502 with the handover NDI value indicating the association with the new transmission, and in response, UE 504 can initiate an inactive timer. The initiation of this inactive timer can be synchronized with the initiation of a corresponding timer at base station 502 (e.g., the UE DRX inactive timer tracked at base station 502).

[0102] Therefore, UE 504 can obtain DRX cycle synchronization because both UE 504 and base station 502 can track UE 504's DRX cycle from a shared or unified event or trigger, the occurrence of which can be observed synchronously at both UE 504 and base station 502. UE 504 can then resume adherence to the DRX cycle based on synchronization with the DRX cycle scheduled by base station 502. For example, UE 504 can stop autonomously extending its wake-up state upon receiving another DCI message with an indicator value indicating association with a new transmission, because UE 504 can assume that the DRX cycle at UE 504 is synchronized with the tracking of the DRX cycle at base station 502 after the active data exchange according to DCI 5 540.

[0103] In some other aspects, base station 502 can be configured to detect whether uplink data is absent from the resources allocated to UE 504 on the uplink data channel, for example, as indicated in DCI1 528 and DCI2 530. If base station 502 may fail to detect the uplink data, base station 502 can assume that UE 504 was in a sleep state of DRX loop when DCI1 528 and DCI2 530 were transmitted to UE 504, and therefore DCI1 528 and DCI2 530 were not received by UE 504. Based on this assumption, base station 502 can infer that the DRX loop tracked at base station 502 for UE 504 is out of sync with the DRX loop currently implemented at UE 504.

[0104] In other aspects, base station 502 can suppress the transmission of DCI3 534 and DCI4 536 to UE 504. Instead, base station 502 can determine that the UE DRX cycle should be resynchronized with UE 504 based on the absence of the transmission in the resource set allocated to UE 504. Base station 502 can transmit data to force the UE DRX cycle tracked at base station 502 to synchronize with the DRX cycle implemented at UE 504. For example, base station 502 can transmit DCI5 540 of scheduling data to UE 504 based on the absence of the transmission from UE 504.

[0105] DCI5 540 can serve as a common or unified point or trigger at which a corresponding DRX timer (e.g., a DRX inactive timer) is initiated at each of base station 502 and UE 504. In some aspects, the DCI message can have format 1_0, format 1_1, or format 1_2. DCI5 540 may include an indicator value indicating association with (e.g., on the downlink) a new transmission. For example, the indicator value could be the NDI value switched from the last DCI0 524, which could be a point at which UE 504 can be assumed to be running a DRX inactive timer.

[0106] In some aspects, base station 502 may transmit data to UE 504 on another set of resources allocated according to DCI 5 540. In some aspects, base station 502 may transmit "dummy" or analog data to UE 504, such as data comprising a set of zero or empty values. This dummy or analog data may be intended to have no effect at UE 504 except to prevent UE 504 from determining that downlink data scheduled by another DCI message was missed by UE 504, which could lead UE 504 to request a retransmission, transmit a NACK feedback, or otherwise throw an error. In some other aspects, base station 502 may transmit real data intended for UE 504, such as data that should be transmitted to UE 504 regardless of circumstances.

[0107] After transmitting data to UE 504 for DRX cycle synchronization with base station 502, synchronization with UE 504's DRX cycle can be assumed. That is, base station 502 can assume that the UE 504 DRX cycle tracked at base station 502 is synchronized with the implementation of the DRX cycle at UE 504. Subsequently, base station 502 can operate under the assumption that the tracking of the UE DRX cycle at base station 502 is consistent with the implementation at UE 504. For example, base station 502 can subsequently receive an SR from UE 504, and base station 502 can transmit a DCI message to UE 504 on the downlink control channel to provide UE 504 with permission in response to the SR. Base station 502 can transmit such a DCI message during the wake-up time of UE 504 because the UE 504 DRX cycle can be synchronized at base station 502 and UE 504. If base station 502 fails to receive uplink transmission from UE 504 based on the DCI message, base station 502 may assume that the problem causing the lack of uplink transmission is somewhere other than DRX cyclic synchronization.

[0108] Figure 6 This is a flowchart 600 of a wireless communication method. The method can be performed by a UE (e.g., one or more of UE 104, UE 350, UE 404, UE 504, and UE 604 described above), a device (e.g., device 902), or its components. In various ways, one or more of the described operations may be interchanged, omitted, or performed concurrently.

[0109] At 602, the UE receives from the base station consecutive DCI messages comprising equal corresponding indicator values. Each of the indicator values ​​can indicate the association between the corresponding DCI message and a new transmission or retransmission. For example, each of the indicator values ​​can be a bit value equal to zero (0) or one (1) in the NDI field of the corresponding DCI message. In other words, the UE receives at least two consecutive DCI messages from the base station, and the NDI value is not switched across the at least two DCI messages.

[0110] In 604, the UE can determine whether the value indicated in the MCS field is reserved for DCI messages associated with retransmission. For example, the value in the MCS field corresponds to a cell or element in a table (e.g., a lookup table or database table) that is used as a key for its MCS attributes or headers (e.g., column headers or row headers).

[0111] In some respects, the UE can compare a value received in the MCS field with one or more cell or element values ​​of an MCS attribute or header in a table, and the UE can identify a cell or element value of an MCS attribute that is equal to the received MCS field value. The UE can also identify whether that cell or element value is associated with an attribute or header indicating that the cell or element value is reserved for control information related to retransmission. For example, the received value may correspond to a cell or element value that forms part of a record associated with an attribute indicating that the record is reserved for retransmission. The received value may correspond to a cell or element value that is functionally equivalent to an MCS indicating the same MCS as the control information previously transmitted by the base station for initial transmission.

[0112] Because the UE receives consecutive DCI messages with the same indicator value, it may be unable to identify which DCI includes the handover value for the initial transmission in the corresponding NDI field. Therefore, the UE may be unable to take any action based on the received DCI messages with reserved MCS values, because the UE may not be able to identify which MCS should be used from multiple DCI messages with the same NDI value—specifically, the UE may have missed the DCI message indicating the allocation for the initial transmission, and thus such MCS information may be completely unavailable to the UE.

[0113] Therefore, if the DCI message includes an MCS value corresponding to a reserved MCS value (and potentially, the UE fails to receive the DCI message for the initial transmission), the UE may lack sufficient information to perform data communication based on the DCI. In cases where such a DCI message indicates scheduling of downlink data on the downlink data channel (e.g., as with DCI messages having formats 1_0, 1_1, and 1_2), then:

[0114] In 606, the UE can suppress decoding of data identified by the most recent DCI message on the downlink data channel based on the MCS value indicated in the set of reserved MCS values ​​within the coherent DCI messages. In other words, the UE can ignore information carried on the downlink data channel resources scheduled by the most recent DCI message, for example, because the UE assumes that the information on the downlink data channel is a retransmission that the UE has already received or that the UE cannot identify the applicable MCS. For example, the UE can suppress decoding of the identified downlink data by suppressing the tuning of the receiver circuitry away from its current configuration on which it receives the control channel, and / or the UE can refuse to descramble at least a portion of the downlink data transmission on the downlink data channel. The UE can resume monitoring the control channel to receive other DCI messages at an appropriate time, or the UE can resume the DRX cycle if there are no further control channel opportunities remaining during the control channel period.

[0115] In cases where such a DCI message indicates permission for uplink data on the uplink data channel (e.g., as with DCI messages having formats 0_0, 0_1, and 0_2), then:

[0116] At 608, the UE can suppress data transmission to the base station based on the most recent DCI message indicating an MCS value within the set of reserved MCS values ​​in a coherent DCI message. In other words, the UE can ignore the uplink grant indicated by the most recent received DCI message, for example because if the UE fails to successfully receive a DCI message with the original grant for the initial transmission (e.g., where the MCS value does not correspond to a value reserved for retransmission), the UE cannot identify the MCS to be used for uplink data transmission from such a DCI message. For example, the UE can suppress data transmission to the base station by suppressing resources that tune the transmitter circuitry to the uplink data channel indicated by the DCI message, and / or the UE can maintain the current uplink buffer state because the UE does not transmit any pending uplink data. The UE can resume monitoring and control channels to receive other DCI messages at an appropriate time, or the UE can resume the DRX cycle if the DRX inactive timer expires or the upper limit threshold for the number of SR retransmissions is reached.

[0117] However, even when receiving consecutive DCI messages with the same NDI value, the UE can utilize the information included therein, because whether a transmission is considered an “initial” transmission or a “retransmission” may have a small (if any) practical impact on UE operation if the relevant parameters are provided—although RV in a DCI message intended for retransmission may be two (2), three (3), or one (1). Thus, if the set of MCS values ​​reserved for retransmission does not include the MCS value from the most recent DCI message, the UE can identify the applicable parameters to be used for the transmission (even if the base station considers the transmission a retransmission). For example, if the DCI message has a format for downlink data, the UE can identify the resources on the downlink data channel on which it will receive the transmission, and the MCS to be used to receive the transmission. Accordingly, the UE can receive the transmission on the downlink data channel, for example, even if the base station is retransmitting the transmission (e.g., with RV two, RV three, or RV one). The UE may not be able to identify which MCS should be used from multiple DCI messages with the same NDI value—specifically, the UE may have missed the DCI message indicating the allocation for the initial transmission, and therefore such MCS information may be completely unavailable to the UE.

[0118] Similarly, if the DCI message does not include the MCS value reserved for retransmission, the UE can obtain sufficient information from the DCI message intended for retransmission to perform uplink transmission. In cases where such a DCI message indicates permission for uplink data on the uplink data channel (e.g., as with DCI messages having formats 0_0, 0_1, and 0_2), then:

[0119] In 610, the UE can transmit data to the base station based on the most recent DCI message, which indicates an MCS value outside the set of MCS values ​​reserved for retransmission within the coherent DCI message. Specifically, the UE can simply use the parameters of the DCI intended for retransmission (e.g., even if RV is two, three, or one or others). For example, the UE can transmit uplink transmissions on uplink data channel resources indicated by retransmission permission, and the UE can do so using the MCS corresponding to the MCS value of the most recently received DCI message.

[0120] Receiving a coherent DCI message without an NDI value that is switched across DCI messages can indicate a loss of synchronization between the base station and the UE regarding the UE's DRX cycle. One or more mechanisms designed to enhance DCI reliability can be used (frequently or always) to transmit DCI messages—for example, fewer bits, higher spectral efficiency, and / or more protection can be used compared to other messages (such as data messages). Therefore, the UE can assume that the most likely cause of missed or lost DCI messages (where the NDI value is switched) is a lack of synchronization between the base station's DRX cycle tracking for the UE and the actual implementation of the DRX cycle at the UE. This unsynchronized DRX cycle can cause the base station to transmit DCI messages(s) to the UE while the UE is in sleep mode, and therefore not to monitor the control channel for DCI messages from the base station.

[0121] Once the UE has identified the likely root cause of the apparent erroneous DCI message, it can perform various operations to recover from the synchronization loss, allowing normal operation with DRX cycles to resume without interrupting DCI message communication. DRX cycles are measured relative to timing units, which can be based on frames (e.g., system frame numbers), time slots, PDCCH timing, or other timing unit scales or combinations thereof. Therefore, synchronization can be reacquired through a shared or unified event or trigger (such as the expiration of a DRX inactive timer) understood by both the UE and the base station to initiate a DRX cycle.

[0122] However, the expiration of the DRX inactivity timer assumes that such a timer is initiated simultaneously at both the base station (used to track UE active and inactive states) and the UE (used to transition between an active wake-up state and an inactive sleep state). The initiation of the DRX inactivity timer can be determined based on the receipt of a DCI message from the base station, the timing of which may be unpredictable (at least on the downlink). Therefore, the UE can take actions to avoid missing DCI messages, enabling it to reacquire DRX cyclic synchronization as quickly as possible and avoiding further message loss or increased latency.

[0123] In 612, the UE remains awake for at least a portion of the scheduled sleep state of a DRX cycle scheduled by the base station based on the equality of the corresponding indicator value across consecutive DCI messages. For example, the UE can measure a timing unit (e.g., a system frame number) until the expiration of a DRX inactive timer or an on-duration timer managed at the UE. The UE can detect the expiration of the timer (e.g., when a certain number of system frames have elapsed), at which point the UE should transition to an inactive or sleep state according to the DRX protocol. However, the UE can suppress the transition to such an inactive or sleep state upon detecting the timer expiration. Instead, the UE can remain awake for at least a portion of the time period for which the UE is configured to be in a sleep state. That is, the UE can autonomously extend the on-duration or active period. During this period, the UE can monitor the control channel (e.g., PDCCH) for DCI messages intended for the UE, and potentially, the UE can transmit (or retransmit) one or more SRs.

[0124] In section 614, the UE can synchronize its DRX cycle with the base station while in a wake-up state. Potentially, the UE can synchronize its DRX cycle with the base station while remaining in a wake-up state for at least a portion of a scheduled sleep state. The UE can cause the base station and the UE to begin measuring DRX inactivity timers and / or DRX start duration timers from a common starting point. For example, the UE can transmit messages mutually understood by both the base station and the UE to initiate a timer that causes the UE to enter an inactive state or otherwise initiate a DRX cycle upon its expiration, or the UE can withhold or delay any messages affecting another timer upon receiving a message from the base station that triggers the UE to enter an inactive state or otherwise initiate a DRX cycle upon its expiration.

[0125] Explained, the UE may communicate some active data to the base station during an autonomously extended wake-up state, which may include data that restarts the DRX inactive timer. While the DRX inactive timer is running, the UE may suppress any operations that affect the DRX inactive timer. The SR procedure can serve as a unified starting point that is understood by both the UE and the base station as initiating a DRX inactive timer for the UE. When the DRX inactive timer expires, the UE may transition to a sleep or inactive state, or the UE may otherwise initiate a DRX cycle. By means of a shared trigger (e.g., the SR procedure) for synchronizing the timer duration and DRX cycle initiation for the UE from which the UE and the base station begin calculating, the DRX cycle occurring at the UE will be synchronized with the tracking of such a DRX cycle for the UE at the base station.

[0126] In some aspects, synchronizing the DRX cycle with the base station at 614 while keeping at least a portion of the scheduled sleep state awake may include one or more operations, such as one or more of 622, 624 and 626 or 628 below.

[0127] In step 622, the UE can receive from the base station another DCI message with an indicator value indicating association with a new transmission. This other DCI message can be received after a coherent DCI message with the same (unswitched) indicator value. For example, the UE can receive this other DCI message while autonomously extending its wake-up state—for example, the UE can receive this other DCI message while remaining in a wake-up state for at least a portion of a scheduled sleep state scheduled for the UE according to the DRX configuration from the base station. The indicator value indicating association with the new transmission can be an NDI value equal to the NDI value expected by the UE—for example, the received NDI value can be switched from a coherent DCI message with the same NDI value. Accordingly, the UE can determine that this other DCI message indicates a new transmission.

[0128] At 624, the UE can initiate an inactive timer at its location based on the other DCI message having an indicator value indicating association with a new transmission. The initiation of this inactive timer can be synchronized with the initiation of a corresponding timer at the base station (e.g., a UE DRX inactive timer tracked at the base station). Therefore, the UE can achieve DRX cycle synchronization because both the UE and the base station can track the UE's DRX cycle from a shared or unified event or trigger, the occurrence of which can be observed simultaneously at both the UE and the base station. In some aspects, initiating an inactive timer at the UE based on the other DCI message having an indicator value indicating association with a new transmission can include: identifying the DCI message as a trigger for the inactive timer; selecting timing units (e.g., system frame number, timeslot, PDCCH timing, etc.) from which to begin counting to measure the elapsed duration of the inactive timer; and counting each timing unit toward the expiration of the inactive timer.

[0129] In step 626, the UE can transmit data to the base station based on an indicator value in the other DCI message that indicates an association with the new transmission. For example, the UE can identify resource grants indicated in the other DCI message for uplink data that the UE can decide to transmit uplink. The UE can further identify the MCS indicated in the other DCI message. Accordingly, the UE can use the identified MCS to transmit at least a portion of the data buffered by the UE for uplink transmission.

[0130] If the other DCI message has a format used for scheduling downlink transmissions, then:

[0131] At 628, the UE can receive data from the base station based on the other DCI message having an indicator value that indicates an association with the new transmission. For example, the UE can identify the resource scheduling for downlink data on the downlink data channel indicated in the other DCI message, and the UE can monitor the resources on the downlink data channel indicated by the other DCI message in order to receive downlink data scheduled thereon.

[0132] In 616, the UE can resume adherence to a DRX cycle based on synchronization with the DRX cycle scheduled by the base station. For example, the UE can stop autonomously extending the wake-up state upon receiving another DCI message with an indicator value indicating association with a new transmission, because the UE can assume that the DRX cycle at the UE and the tracking of the DRX cycle at the base station are synchronized after active data exchange according to the other DCI message (e.g., see 622, 624 and 626 or 628 above). The UE can initiate an on-duration timer for the DRX cycle and can remain in the wake-up state while the on-duration timer is running, during which time the UE can supply sufficient power to the receiver circuitry to receive transmissions from the base station. Furthermore, the UE can count timing units (e.g., system frames, time slots, etc.) while in the wake-up state to track the elapsed duration of the on-duration timer.

[0133] In some respects, restoring compliance with a DRX cycle at 616 based on synchronization of the DRX cycle scheduled by the base station may include one or more operations, such as at 630.

[0134] At 630, the UE can transition from a wake-up state to a sleep state within a DRX cycle scheduled by the base station after the inactive timer expires. For example, the UE can measure the elapsed time of an inactive timer that was initiated when another DCI message is received on the downlink control channel (e.g., PDCCH). To this end, the UE can count the number of timing units (e.g., system frames, time slots, PDCCH timings, etc.) until a timing threshold is met (e.g., it meets, exceeds, or otherwise reaches the timing threshold). The UE can detect that the timing threshold has been met when the count of timing units equals the timing threshold, or when the count of timing units reaches a lower limit threshold (such as zero (0)) while the UE is counting down. Upon detecting that the inactive timer has expired, the UE can resume operation according to the DRX cycle configured by the base station. For example, if the expiration of the inactive timer coincides with the shutdown portion of the DRX cycle, the UE can transition from a wake-up state to a sleep state when the inactive timer expires, or the UE can remain in a wake-up state while the enabled duration timer is running, and then transition to a sleep state when the enabled duration timer expires.

[0135] Figure 7 This is a flowchart 700 of a wireless communication method. The method can be performed by a base station (e.g., base station 102 / 180, base station 310, base station 402, base station 502), a device (e.g., device 902), or its components. In various ways, one or more of the described operations may be interchanged, omitted, or performed concurrently.

[0136] In 702, the base station may transmit a DCI message to the UE indicating a set of resources allocated to the UE for transmission. These resources may be allocated on an uplink data channel (e.g., PUSCH) for uplink data transmission by the UE. In some aspects, the DCI message may have format 0_0, format 0_1, or format 0_2. The DCI message may include an indicator value indicating association with retransmission. For example, the indicator value may be an NDI value that has not been switched from a previous DCI message immediately preceding it, which may have indicated prior permission for the UE that was not used by the UE. Furthermore, the DCI message may indicate an MCS to be associated with the transmission, which may be an MCS value reserved for retransmission and / or an RV greater than zero (and usable for retransmission).

[0137] In 704, the base station can monitor the allocated resources on the uplink data channel to locate uplink data from the UE. The base station can determine whether uplink data from the UE is detected on the allocated resources or whether uplink data from the UE is not present in the allocated resources.

[0138] If uplink data is not available in the resources allocated to the UE on the uplink data channel, the base station may fail to detect uplink data. Based on the absence of uplink data on the allocated resources, the base station can assume that the UE was in a sleep state of the DRX cycle when the DCI message was transmitted to the UE, and therefore the DCI message was not received by the UE. Based on this assumption, the base station can infer that the DRX cycle tracked for the UE at the base station is out of sync with the DRX cycle currently implemented at the UE.

[0139] In 706, the base station can transmit data to the UE to synchronize the DRX cycle with the UE if the transmission is not present in the resource set allocated to the UE. The base station can transmit this data to force the UE DRX cycle tracked at the base station to synchronize with the DRX cycle implemented at the UE. For example, the base station can transmit another DCI message indicating scheduled resources on the downlink data channel that will carry downlink data. The base station can then transmit downlink data on the scheduled resources of that downlink data channel.

[0140] In some respects, transmitting data to the UE at 706 to synchronize the DRX cycle with the UE based on the absence of the transmission in the resource set allocated to the UE may include one or more operations, such as at 722 and 724.

[0141] In 722, the base station may transmit another DCI message to the UE, based on the absence of the transmission in the resource set allocated to the UE, to schedule the data on a different resource set on the downlink data channel. This other DCI message may serve as a common or unified point or trigger at which a corresponding DRX timer (e.g., a DRX inactive timer) is initiated at each of the base station and the UE. In some aspects, the DCI message may have format 1_0, format 1_1, or format 1_2. The DCI message may include an indicator value indicating the association with (e.g., on the downlink) a new transmission. For example, the indicator value may be an NDI value switched from a previous DCI message indicating a previously scheduled resource set on the downlink data channel used for the previous downlink transmission. Furthermore, the DCI message may indicate an MCS to be used in conjunction with the downlink transmission and / or the HARQ procedure of the downlink transmission.

[0142] In 724, the base station can transmit the data to the UE on this other resource set of the downlink data channel. In some aspects, the base station can transmit "dummy" data or simulated data to the UE, such as data including a set of zero or empty values. Such dummy or simulated data may be intended to have no effect at the UE except to prevent the UE from determining that the downlink data scheduled by this other DCI message was missed, which could lead the UE to request a retransmission, transmit a NACK feedback, or otherwise throw an error. In some other aspects, the base station can transmit real data intended for the UE, such as data that should be transmitted to the UE regardless of the circumstances.

[0143] After uplink data is detected at point 704 on the resources allocated to the UE on the uplink data channel, or after data for cyclically synchronizing the DRX with the UE is transmitted to the UE at point 706 based on the absence of such transmission in the resource set allocated to the UE:

[0144] In 708, the base station can assume synchronization with the UE's DRX cycle. That is, the base station can assume that the UE DRX cycle tracked at the base station is synchronized with the implementation of the DRX cycle at the UE. Subsequently, the base station can operate under the assumption that the tracking of the UE DRX cycle at the base station is consistent with the implementation at the UE. For example, the base station can subsequently receive an SR from the UE, and the base station can transmit a DCI message to the UE on the downlink control channel to provide the UE with permission in response to the SR. The base station can transmit such a DCI message during the UE's wake-up time, because the UE DRX cycle can be synchronized at both the base station and the UE. If the base station fails to receive uplink transmission from the UE based on the DCI message, the base station can consider that the problem causing the lack of uplink transmission lies somewhere other than DRX cycle synchronization.

[0145] Figure 8 Figure 800 illustrates an example of the hardware implementation of device 802. Device 802 may be a UE or similar device, or device 802 may be a component of a UE or similar device. Device 802 may include a cellular baseband processor 804 (also known as a modem) and / or a cellular RF transceiver 822, which may be coupled together and / or integrated into the same package or module.

[0146] In some aspects, device 802 may accept or may accept one or more Subscriber Identity Module (SIM) cards 820, which may be one or more integrated circuits, chips, or similar circuit systems, and may be removable or embedded. The one or more SIM cards 820 may carry identification and / or authentication information, such as International Mobile Subscriber Identity (IMSI) and / or IMSI-related keys. Furthermore, device 802 may include one or more of the following coupled to a Secure Digital (SD) card 808 and a screen 810: an application processor 806, a Bluetooth module 812, a Wireless Local Area Network (WLAN) module 814, a Global Positioning System (GPS) module 816, and / or a power supply 818.

[0147] Cellular baseband processor 804 communicates with UE 104 and / or base station 102 / 180 via cellular RF transceiver 822. Cellular baseband processor 804 may include computer-readable medium / memory. The computer-readable medium / memory may be non-transient. Cellular baseband processor 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. This software, when executed by cellular baseband processor 804, causes cellular baseband processor 804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by cellular baseband processor 804 during software execution. Cellular baseband processor 804 further includes receiving component 830, communication manager 832, and transmission component 834. Communication manager 832 includes one or more of the described components. Components within communication manager 832 may be stored in computer-readable medium / memory and / or configured as hardware within cellular baseband processor 804.

[0148] exist Figure 3 In the context of this, the cellular baseband processor 804 may be a component of the UE 350 and may include memory 360 and / or at least one of the following: TX processor 368, RX processor 356, and / or controller / processor 359. In one configuration, device 802 may be a modem chip and / or may be implemented as baseband processor 804, while in another configuration, device 802 may be the entire UE (e.g., Figure 3 The UE 350 may include some or all of the modules, components and / or circuitry described in the context of device 802. In one configuration, the cellular RF transceiver 822 may be implemented as at least one of transmitter 354TX and / or receiver 354RX.

[0149] The receiving component 830 can be configured to receive signaling on a wireless channel, such as signaling from base station 82 / 180 or UE 104. The transmitting component 834 can be configured to transmit signaling on a wireless channel, such as signaling to base station 102 / 180 or UE 104. The communication manager 832 can coordinate or manage some or all wireless communications performed by device 802, including wireless communications across the receiving component 830 and the transmitting component 834.

[0150] The receiving component 830 may provide the communication manager 832 with some or all of the data and / or control information included in the received signaling, and the communication manager 832 may generate some or all of the data and / or control information to be included in the transmitted signaling and provide this data and / or control information to the transmission component 834. The communication manager 832 may include various explained components, including one or more components configured to process the received data and / or control information, and / or one or more components configured to generate data and / or control information for transmission.

[0151] The receiving component 830 can receive coherent DCI messages from the base station 102 / 180, including corresponding indicator values ​​of equal value, for example, as combined with Figure 6 As described in 602. Each of the indicator values ​​can indicate the association between the corresponding DCI message and a new transmission or a retransmission. For example, each of the indicator values ​​can be a bit value equal to zero (0) or one (1) in the NDI field of the corresponding DCI message.

[0152] Communication manager 832 includes MCS identification component 840, bypass component 842, DRX modification component 844, DRX synchronization component 846, timer component 848, and / or DRX compliance component 850. MCS identification component 840 can be configured to determine whether the value indicated in the MCS field is retained for DCI messages associated with retransmission, for example, as in conjunction with... Figure 6 As described in section 604. For example, MCS identification component 840 can compare a value in a received MCS field with one or more cell or element values ​​of an MCS attribute or header in a table, and MCS identification component 840 can identify a cell or element value of an MCS attribute that is equal to the received MCS field value. MCS identification component 840 can also identify whether that cell or element value is also associated with an attribute or header that indicates that the cell or element value is reserved for control information related to retransmission.

[0153] When the most recent DCI message is for downlink data, the bypass component 842 can be configured to suppress decoding of data identified by the most recent DCI message on the downlink data channel based on the MCS values ​​indicated in the set of reserved MCS values ​​in the coherent DCI messages. For example, as in combination with Figure 6 As described in 606. In other words, the bypass component 842 can ignore the information carried on the downlink data channel resources scheduled by the most recent DCI message.

[0154] In cases where such a DCI message indicates permission for uplink data on the uplink data channel, the bypass component 842 can suppress data transmission to the base station based on the most recent DCI message indicating the MCS value within the set of retained MCS values ​​in the coherent DCI messages. For example, as in combination with Figure 6 As described in 608. In other words, the bypass component 842 can ignore uplink permission indicated by the most recently received DCI message.

[0155] However, if the most recent DCI message includes an uplink-granted set of MCS values ​​reserved for retransmission that does not include the MCS value in the most recent DCI message, then the transmission component 834 may transmit data to the base station 102 / 180 based on the most recent DCI message in the coherent DCI messages that indicates an MCS value outside the set of MCS values ​​reserved for retransmission, for example, as combined with Figure 6 As described in 610.

[0156] DRX modification component 844 can be configured to keep at least a portion of the scheduled sleep state of the DRX cycle scheduled by base station 102 / 1808 in an awake state based on the equality of the corresponding indicator value across coherent DCI messages, for example, as in combination with Figure 6 As described in section 612. For example, the DRX modification component 844 can measure timing units (e.g., system frame numbers) until the expiration of a DRX inactive timer or an on-duration timer managed at device 802. The DRX modification component 844 can detect the expiration of a timer, such as when a certain number of system frames have elapsed, at which point device 802 should transition to an inactive or sleep state according to the DRX protocol. However, the DRX modification component 844 can suppress the transition to such an inactive or sleep state upon detecting the timer expiration. Instead, the DRX modification component 844 can autonomously extend the on-duration or active period. During this period, the receiving component 830 can monitor the control channel (e.g., PDCCH) for DCI messages intended for device 802, and potentially, the transmitting component 834 can transmit (or retransmit) one or more SRs.

[0157] The DRX synchronization component 846 can be configured to synchronize the DRX cycle with the base station 102 / 180 while in a wake-up state, for example, as combined with Figure 6 As described in 614. Potentially, the DRX synchronization component 846 can synchronize the DRX cycle with base station 102 / 180 while at least a portion of the scheduled sleep state remains in the awake state. Device 802 can cause base station 102 / 180 and device 802 to measure the DRX inactive timer and / or DRX start duration timer from a common starting point.

[0158] In some respects, receiving component 830 can receive from base station 102 / 180 another DCI message having an indicator value indicating association with a new transmission, for example, as combined with Figure 6 As described in section 622. This additional DCI message can be received following a series of DCI messages with the same (unswitched) indicator value. For example, receiving component 830 can receive this additional DCI message while autonomously extending the wake-up state of device 802—for example, receiving component 830 can receive this additional DCI message while remaining in the wake-up state during or after at least a portion of a scheduled sleep state scheduled for device 802 according to the DRX configuration from base station 102 / 180.

[0159] Timer component 848 can initiate an inactive timer at device 802 based on the other DCI message having an indicator value indicating association with a new transmission, for example, as in combination with Figure 6 As described in section 624. The initiation of this inactive timer can be synchronized with the initiation of a corresponding timer at base station 102 / 180 (e.g., the inactive DRX timer of device 802 tracked at base station 102 / 180). Therefore, DRX synchronization component 846 can achieve DRX cycle synchronization because both device 802 and base station 102 / 180 can track the DRX cycle of device 802 from a shared or unified event or trigger, the occurrence of which can be observed synchronously at both device 802 and base station 102 / 180.

[0160] In this additional DCI message, which has some aspects of the format for granting uplink transmission, the transmission component 834 can be configured to transmit data to the base station 102 / 180 based on an indicator value in the additional DCI message that indicates an association with a new transmission, for example, as in combination with Figure 6 As described in 626.

[0161] In this additional DCI message, which has some other aspects of the format for scheduling downlink transmissions, the receiving component 830 can be configured to receive data from the base station 102 / 180 based on an indicator value in the additional DCI message that indicates an association with a new transmission, for example, as combined with Figure 6 As described in 628.

[0162] DRX compliance component 850 can be configured to restore compliance with a DRX cycle based on synchronization with the DRX cycle scheduled by base station 102 / 180, for example, as in combination with Figure 6As described in 616. For example, DRX compliance component 850 can cause DRX modification component 844 to stop autonomously extending the wake-up state upon receiving another DCI message with an indicator value indicating association with the new transmission.

[0163] In some respects, the DRX compliance component 850 can be configured to restore compliance with a DRX cycle based on synchronization with the DRX cycle scheduled by base station 102 / 180 by transitioning from an awake state to a sleep state of the DRX cycle scheduled by base station 102 / 180 after an inactive timer expires, for example, as in combination with Figure 6 As described in 630. For example, timer component 848 can measure the elapsed time of an inactive timer that was initiated when the other DCI message is received on the downlink control channel (e.g., PDCCH). Upon detecting that the inactive timer has expired, DRX compliance component 850 can resume operation according to the DRX cycle configured by base station 102 / 180. For example, DRX compliance component 850 can cause device 802 to transition from a wake-up state to a sleep state when the inactive timer expires if the expiration of the inactive timer coincides with the shutdown portion of the DRX cycle, or DRX compliance component 850 can cause device 802 to remain in a wake-up state while the enabled duration timer is running, and then transition to a sleep state when the enabled duration timer expires.

[0164] Device 802 may include execution Figure 5 and Figure 6 Some or all of the additional components of the algorithms, operations, signaling, etc., in the aforementioned call flow diagrams and / or flowcharts. Thus, Figure 5 and Figure 6 Some or all of the boxes, operations, signaling, etc., in the aforementioned call flow diagram and / or flowchart may be executed by a component, and device 802 may include one or more of those components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0165] In one configuration, device 802, specifically cellular baseband processor 804, includes: means for receiving from a base station a series of coherent DCI messages comprising equal corresponding indicator values, each of which indicates an association with a new transmission or a retransmission; and means for maintaining at least a portion of a scheduled sleep state for a DRX cycle scheduled by the base station in an awake state based on the equality of the corresponding indicator values ​​across the coherent DCI messages.

[0166] In one configuration, device 802, specifically cellular baseband processor 804, may further include: means for synchronizing a DRX cycle with a base station while remaining in a wake-up state; and means for resuming adherence to the DRX cycle based on synchronization with the DRX cycle scheduled by the base station.

[0167] In one configuration, the means for synchronizing the DRX cycle with the base station is configured to: receive from the base station another DCI message having an indicator value indicating association with a new transmission; and initiate an inactive timer at the UE based on the indicator value in the other DCI message indicating association with a new transmission, the initiation of the inactive timer at the UE being synchronized with the initiation of a corresponding timer for the UE at the base station.

[0168] In one configuration, device 802, specifically cellular baseband processor 804, may further include: means for receiving data from a base station before the expiration of the inactive timer based on the other DCI message having an indicator value indicating association with a new transmission, or means for transmitting data to a base station based on the other DCI message having an indicator value indicating association with a new transmission.

[0169] In one configuration, means for restoring compliance with a DRX cycle based on synchronization with the DRX cycle scheduled by the base station is configured to transition from an awake state to a sleep state of the DRX cycle scheduled by the base station after the inactive timer expires.

[0170] In one configuration, device 802, specifically cellular baseband processor 804, may further include: means for suppressing data transmission to a base station based on the most recent DCI message in a coherent DCI message indicating the MCS value within a set of retained MCS values.

[0171] In one configuration, device 802, specifically cellular baseband processor 804, may further include: means for transmitting data to a base station based on the most recent DCI message in a coherent DCI message indicating an MCS value outside the set of retained MCS values.

[0172] In one configuration, device 802, specifically cellular baseband processor 804, may further include means for suppressing the decoding of data on a downlink data channel identified by the most recent DCI message indicating an MCS value within a set of reserved MCS values ​​in a coherent DCI message.

[0173] In a configuration, each of these indicator values ​​corresponds to the NDI field of one of the coherent DCI messages.

[0174] In a configuration, one of the consecutive DCI messages corresponds to a HARQ procedure.

[0175] The aforementioned apparatus may be one or more of the aforementioned components in device 802 configured to perform the functions described by the aforementioned apparatus. As described above, device 802 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned apparatus may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described by the aforementioned apparatus.

[0176] Figure 9 Figure 900 illustrates an example of the hardware implementation of device 902. Device 902 may be a base station or similar device or system, or device 902 may be a component of a base station or similar device or system. Device 902 may include a baseband unit 904. Baseband unit 904 may communicate via a cellular RF transceiver. For example, baseband unit 904 may communicate with UE 104 via a cellular RF transceiver (e.g., for downlink and / or uplink communication), and / or with base stations 102 / 180 (e.g., for IAB).

[0177] Baseband unit 904 may include computer-readable medium / memory, which may be non-transient. Baseband unit 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by baseband unit 904, the software causes baseband unit 904 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 904 during software execution. Baseband unit 904 further includes receiving component 930, communication manager 932, and transmission component 934. Communication manager 932 includes one or more of the described components. Components within communication manager 932 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 904. Baseband unit 904 may be a component of base station 310 and may include memory 376 and / or at least one of the following: TX processor 316, RX processor 370, and controller / processor 375.

[0178] The receiving component 930 can be configured to receive signaling on a wireless channel, such as signaling from UE 104 (or base station 102 / 180). The transmitting component 934 can be configured to transmit signaling on a wireless channel, such as signaling to UE 104 (or base station 102 / 180). The communication manager 932 can coordinate or manage some or all wireless communications performed by the device 902, including wireless communications across the receiving component 930 and the transmitting component 934.

[0179] The receiving component 930 may provide some or all of the data and / or control information included in the received signaling to the communication manager 932, and the communication manager 932 may generate some or all of the data and / or control information to be included in the transmitted signaling and provide this data and / or control information to the transmission component 934. The communication manager 932 may include various explained components, including one or more components configured to process the received data and / or control information, and / or one or more components configured to generate data and / or control information for transmission. In some aspects, the generation of data and / or control information may include packetizing or otherwise reformatting the data and / or control information received from the core network (such as core network 190 or EPC 160) for transmission.

[0180] The transmission component 934 can be configured to transmit to the UE 104 a DCI message indicating the resource set allocated to the UE for transmission, for example, as in combination with Figure 7 As described in section 702. These resources can be allocated on an uplink data channel (e.g., PUSCH) for the transmission of uplink data by the UE. In some aspects, the DCI message can have format 0_0, format 0_1, or format 0_2. The DCI message can include an indicator value indicating association with retransmission. For example, the indicator value can be an NDI value that has not been switched from a previous DCI message immediately preceding it, which may have indicated prior permission for the UE that was not used by the UE. In addition, the DCI message can indicate the MCS to be associated with the transmission, which can be an MCS value reserved for retransmission and / or an RV greater than zero (and available for retransmission).

[0181] The communication manager 932 may include one or more of a detection component 940, a DRX synchronization component 942, and / or a scheduling component 944. The detection component 940 may be configured to monitor allocated resources on the uplink data channel to locate uplink data from the UE 104, for example, in conjunction with... Figure 7 As described in 704, the detection component 940 can determine whether uplink data from UE 104 is detected on the allocated resources or whether uplink data from UE 104 is not present in the allocated resources.

[0182] If there is no uplink data in the resources allocated to UE 104 on the uplink data channel, the base station may fail to detect the uplink data. Based on the absence of uplink data on the allocated resources, DRX synchronization component 942 can assume that UE 104 is in a sleep state of the DRX cycle when the DCI message is transmitted, and therefore the DCI message was not received by UE 104. Based on this assumption, DRX synchronization component 942 can infer that the DRX cycle tracked for UE 104 at DRX synchronization component 942 is out of sync with the DRX cycle currently implemented at UE 104.

[0183] Therefore, the DRX synchronization component 942 can generate data to synchronize the DRX cycle with the UE 104 based on the absence of the transmission in the resource set allocated to the UE 104, and transmit this data to the UE 104 (via the transmission component 934), for example, as in combination with Figure 7 As described in 706, the DRX synchronization component 942 can generate and transmit data to force the UE DRX cycle tracked at the DRX synchronization component 942 to synchronize with the DRX cycle implemented at the UE 104.

[0184] In some aspects, scheduling component 944 can schedule another resource set on the downlink data channel to carry downlink data to UE 104, and scheduling component 944 can transmit another DCI message scheduling downlink data on the other resource set of the downlink data channel (through transmission component 934) based on the absence of the transmission in the resource set allocated to UE 104, for example, as in combination with Figure 7 As described in section 722. This additional DCI message can serve as a common or unified point or trigger at which a corresponding DRX timer (e.g., a DRX inactive timer) is initiated at each of the DRX synchronization components 942 and UE 104. In some aspects, the DCI message can have format 1_0, format 1_1, or format 1_2. The DCI message can include an indicator value indicating association with (e.g., on the downlink) a new transmission. For example, the indicator value could be an NDI value switched from a previous DCI message indicating a prior set of resources previously scheduled on the downlink data channel for the previous downlink transmission. Furthermore, the DCI message can indicate an MCS to be used in conjunction with the downlink transmission and / or the HARQ procedure of the downlink transmission.

[0185] The DRX synchronization component 942 can generate this data and transmit it to the UE 104 (via the transmission component 934) on the other resource set of the downlink data channel, for example, as in combination with Figure 7As described in section 724. In some aspects, the DRX synchronization component 942 can generate and transmit "dummy" or simulated data to the UE 104, such as data comprising a set of zero or empty values. This dummy or simulated data may be intended to have no effect at the UE 104 except to prevent the UE 104 from determining that downlink data scheduled by this other DCI message was missed by the UE 104, which could lead the UE 104 to request a retransmission, transmit a NACK feedback, or otherwise throw an error. In some other aspects, the DRX synchronization component 942 can cause the transmission of real data intended for the UE 104 (such as data that should be transmitted to the UE 104 regardless of circumstances).

[0186] After detecting uplink data on the resources allocated to the UE on the uplink data channel, or after transmitting data to the UE 104 to synchronize the DRX cycle with the UE 104 based on the absence of such transmission in the resource set allocated to the UE 104, the scheduling component 944 may assume synchronization with the UE 104's DRX cycle, for example, as in conjunction with Figure 7 As described in 708. That is, the scheduling component 944 can assume that the UE DRX cycle tracked at the DRX synchronization component 942 is synchronized with the implementation of the DRX cycle at the UE 104.

[0187] Device 902 may include execution Figure 5 and Figure 7 Some or all of the additional components of the algorithms, operations, signaling, etc., in the aforementioned call flow diagrams and / or flowcharts. Thus, Figure 5 and Figure 7 Some or all of the boxes, operations, signaling, etc., in the aforementioned call flow diagram and / or flowchart may be executed by a component, and device 902 may include one or more of those components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0188] In one configuration, device 902, specifically baseband processing unit 904, includes: means for transmitting to the UE a DCI message indicating a resource set allocated to the UE for transmission; and means for transmitting to the UE data for cyclically synchronizing DRX with the UE based on the absence of the transmission in the resource set allocated to the UE.

[0189] In one configuration, this data is transmitted to synchronize the DRX cycle with the UE by restarting an inactive timer at the UE.

[0190] In one configuration, means for transmitting data for synchronizing DRX cycles with the UE is configured to: transmit to the UE another DCI message scheduling the data on another resource set of the downlink data channel based on the absence of the transmission in the resource set allocated to the UE; and transmit the data to the UE on the other resource set of the downlink data channel.

[0191] In one configuration, this data includes dummy data.

[0192] In one configuration, the DCI message further indicates at least one of the MCS values ​​in the set of reserved MCS values ​​or redundant values ​​greater than 0.

[0193] The aforementioned apparatus may be one or more of the aforementioned components in device 902 configured to perform the functions described by the aforementioned apparatus. As described above, device 902 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the aforementioned apparatus may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described by the aforementioned apparatus.

[0194] The specific order or hierarchy of the various boxes or operations in each of the processes, flowcharts, and other illustrations disclosed herein is an explanation of exemplary methods. Based on design preferences, those skilled in the art will readily recognize that the specific order or hierarchy of the boxes or operations in each of the aforementioned processes, flowcharts, and other illustrations can be rearranged, omitted, and / or performed concurrently without departing from the scope of this disclosure. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order and are not intended to limit them to the specific order or hierarchy presented.

[0195] The following examples are merely illustrative and can be combined with other embodiments or aspects of the teachings described herein without limitation.

[0196] Example 1 is an apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to: receive from a base station a series of DCI messages comprising equal corresponding indicator values, each of the indicator values ​​indicating an association with either a new transmission or a retransmission; and maintain at least a portion of a scheduled sleep state for a DRX cycle scheduled by the base station in an awake state based on the equality of the corresponding indicator values ​​across the series of DCI messages.

[0197] Example 2 may be an apparatus of Example 1, and these instructions, when executed by the processor, can further operate to cause the apparatus to: synchronize the DRX cycle with the base station while in the wake-up state; and to resume compliance with the DRX cycle based on the synchronization of the DRX cycle scheduled by the base station.

[0198] Example 3 may be the same apparatus as Example 2, and synchronizing the DRX cycle with the base station includes: receiving from the base station another DCI message having an indicator value indicating association with a new transmission; and initiating an inactive timer at the UE based on the indicator value in the other DCI message indicating association with a new transmission, the initiation of the inactive timer at the UE being synchronized with the initiation of a corresponding timer for the UE at the base station.

[0199] Example 4 may be an apparatus of Example 3, and these instructions, when executed by the processor, are further operable to cause the apparatus to perform one of the following: receive data from the base station before the expiration of the inactive timer based on the other DCI message having an indicator value indicating association with a new transmission, or transmit data to the base station based on the other DCI message having an indicator value indicating association with a new transmission.

[0200] Example 5 can be an apparatus of either Example 3 or 4, and restoring compliance with the DRX cycle based on synchronization with the DRX cycle scheduled by the base station includes transitioning from the awake state to the sleep state of the DRX cycle scheduled by the base station after the inactive timer expires.

[0201] Example 6 can be an apparatus of any of Examples 1 to 5, and these instructions, when executed by the processor, can further operate to cause the apparatus to: suppress data transmission to the base station based on the most recent DCI message in the coherent DCI message indicating the retention of MCS values ​​within the set of MCS values.

[0202] Example 7 can be an apparatus of any of Examples 1 to 5, and these instructions, when executed by the processor, can further operate to cause the apparatus to transmit data to the base station based on the most recent DCI message in the coherent DCI message indicating that an MCS value outside the set of retained MCS values.

[0203] Example 8 may be an apparatus of any of Examples 1 to 4, and these instructions, when executed by the processor, may further operate to cause the apparatus to: suppress decoding of data on the downlink data channel identified by the most recent DCI message indicating the MCS value within the set of reserved MCS values ​​in the coherent DCI messages.

[0204] Example 9 can be a device of any of Examples 1 to 8, and each of these indicator values ​​corresponds to the NDI field of one of the coherent DCI messages.

[0205] Example 10 can be a device of any of Examples 1 to 9, and each of the coherent DCI messages corresponds to a HARQ procedure.

[0206] Example 11 may be an apparatus for wireless communication at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to: transmit to the UE a DCI message indicating a resource set allocated to the UE for transmission; and transmit to the UE data for synchronizing the DRX cycle with the UE based on the absence of the transmission in the resource set allocated to the UE.

[0207] Example 12 can be the same device as Example 11, and the data is transmitted to synchronize the DRX cycle with the UE by restarting an inactive timer at the UE.

[0208] Example 13 may be an apparatus of either Example 11 or 12, and transmitting data for synchronizing the DRX cycle with the UE includes: transmitting to the UE another DCI message scheduling the data on another resource set of the downlink data channel based on the absence of the transmission in the resource set allocated to the UE; and transmitting the data to the UE on the other resource set of the downlink data channel.

[0209] Example 14 can be a device of any of Examples 11 to 13, and the data includes dummy data.

[0210] Example 15 may be an apparatus of any of Examples 11 to 14, and the DCI message further indicates at least one of the MCS values ​​in the set of reserved MCS values ​​or redundant values ​​greater than 0.

[0211] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein can be applied to other aspects. Therefore, the claims are not intended to limit the scope to the aspects shown herein, but are to be granted the full scope consistent with the language used herein.

[0212] As an example, the language "determine" can encompass a wide variety of actions and therefore may not be limited to the concepts and aspects explicitly described or explained by this disclosure. In some contexts, "determine" can include calculus, computation, processing, measurement, derivation, research, lookup (e.g., looking in a table, database, or other data structure), ascertainment, parsing, selection, choosing, establishing, and the like. In some other contexts, "determine" can include communication and / or memory operations / procedures through which information or values ​​are obtained, such as "receiving" (e.g., receiving information), "accessing" (e.g., accessing data in memory), "detecting," etc.

[0213] As another example, references to singular elements are not intended to mean "one and only one" (unless specifically stated otherwise), but rather "one or more." Furthermore, terms such as "if," "when," and "at" should be interpreted as meaning "under this condition," rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or event or during the occurrence of an action or event, but rather imply that another action or event will occur under the condition that a condition is met, without requiring a specific or immediate temporal constraint or direct relation for the occurrence of that other action or event. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as superior to or overriding other aspects. Unless specifically stated otherwise, the term "some / a certain" 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 multiple A, multiple B, or multiple 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 such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is explicitly stated in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., are not necessarily substitutes for the term “apparatus.” Thus, no claim element should be interpreted as an apparatus plus a function unless the element is explicitly stated using the phrase “apparatus for…”.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: Receive from the base station a coherent downlink control information (DCI) message comprising equal corresponding indicator values, each of which indicates an association with a new transmission or a retransmission; Based on the equality of the corresponding indicator value across the consecutive DCI messages, at least a portion of the scheduled sleep state for the discontinuous reception (DRX) cycle scheduled by the base station remains in the awake state. When in the wake-up state, the DRX cycle is synchronized with the base station; as well as Consistency with the DRX cycle is restored by synchronizing the DRX cycle scheduled by the base station. Synchronizing the DRX cycle with the base station includes: Receive another DCI message from the base station having an indicator value indicating association with the new transmission; and An inactive timer is initiated at the UE based on the other DCI message having an indicator value that indicates the association with the new transmission, the initiation of the inactive timer at the UE being synchronized with the initiation of the corresponding timer for the UE at the base station; And includes one of the following: Data is received from the base station before the inactive timer expires based on the other DCI message having the indicator value indicating the association with the new transmission, or Data is transmitted to the base station based on the other DCI message having an indicator value that indicates the association with the new transmission.

2. The method as described in claim 1, wherein, Restoring adherence to the DRX cycle based on synchronizing the DRX cycle scheduled by the base station includes: After the inactive timer expires, the system transitions from the awake state to the sleep state of the DRX cycle scheduled by the base station.

3. The method of claim 1, further comprising: Data transmission to the base station is suppressed based on the most recent DCI message in the coherent DCI message that indicates the MCS value within the set of reserved modulation and coding scheme (MCS) values.

4. The method of claim 1, further comprising: Data is transmitted to the base station based on the most recent DCI message in the coherent DCI message that indicates an MCS value outside the set of reserved modulation and coding scheme (MCS) values.

5. The method of claim 1, further comprising: Decoding of data on the downlink data channel identified by the most recent DCI message, which indicates the MCS value within the set of reserved modulation and coding scheme (MCS) values ​​in the coherent DCI messages, is suppressed.

6. The method of claim 1, wherein, Each of the indicator values ​​corresponds to the New Data Indicator (NDI) field of one of the coherent DCI messages.

7. The method of claim 1, wherein, Each of the coherent DCI messages corresponds to a Hybrid Automatic Repeat Request (HARQ) process.

8. A method for conducting wireless communication at a base station, comprising: A downlink control information (DCI) message is transmitted to the user equipment (UE) indicating the set of resources allocated to the UE for transmission; Data is transmitted to the UE to synchronize a discontinuous reception (DRX) cycle with the UE based on the absence of the transmission in the resource set allocated to the UE, wherein the data is transmitted to synchronize the DRX cycle with the UE by restarting an inactive timer at the UE; Transmit another DCI message to the UE, having an indicator value that indicates the association with the new transmission; And one of the following: Data is transmitted to the UE before the inactive timer expires based on the other DCI message having the indicator value indicating the association with the new transmission, or Data is received from the UE based on the other DCI message having the indicator value that indicates the association with the new transmission.

9. The method of claim 8, wherein, The data transmitted to synchronize the DRX cycle with the UE includes: Based on the absence of the transmission in the resource set allocated to the UE, another DCI message is transmitted to the UE to schedule the data on another resource set of the downlink data channel; and The data is transmitted to the UE on the other resource set of the downlink data channel.

10. The method of claim 8, wherein, The data includes fictitious data.

11. The method of claim 8, wherein, The DCI message further indicates at least one of the following: a reserved MCS value within the set of modulation and coding scheme (MCS) values, or a redundant value greater than 0.

12. An apparatus for wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and, when executed by the processor, are operable to cause the device to: Receive from the base station a coherent downlink control information (DCI) message comprising equal corresponding indicator values, each of which indicates an association with a new transmission or a retransmission; Based on the equality of the corresponding indicator value across the consecutive DCI messages, at least a portion of the scheduled sleep state for the discontinuous reception (DRX) cycle scheduled by the base station remains in the awake state. When in the wake-up state, the DRX cycle is synchronized with the base station; as well as Consistency with the DRX cycle is restored by synchronizing the DRX cycle scheduled by the base station. Synchronizing the DRX cycle with the base station includes: Receive another DCI message from the base station having an indicator value indicating association with the new transmission; and An inactive timer is initiated at the UE based on the other DCI message having an indicator value that indicates the association with the new transmission, the initiation of the inactive timer at the UE being synchronized with the initiation of the corresponding timer for the UE at the base station; And includes one of the following: Data is received from the base station before the inactive timer expires based on the other DCI message having the indicator value indicating the association with the new transmission, or Data is transmitted to the base station based on the other DCI message having an indicator value that indicates the association with the new transmission.

13. The apparatus of claim 12, wherein, Restoring adherence to the DRX cycle based on synchronizing the DRX cycle scheduled by the base station includes: After the inactive timer expires, the system transitions from the awake state to the sleep state of the DRX cycle scheduled by the base station.

14. The apparatus of claim 12, wherein, When executed by the processor, the instructions are further operable to cause the device to: Data transmission to the base station is suppressed based on the most recent DCI message in the coherent DCI message that indicates the MCS value within the set of reserved modulation and coding scheme (MCS) values.

15. The apparatus of claim 12, wherein, When executed by the processor, the instructions are further operable to cause the device to: Data is transmitted to the base station based on the most recent DCI message in the coherent DCI message that indicates an MCS value outside the set of reserved modulation and coding scheme (MCS) values.

16. The apparatus of claim 12, wherein, When executed by the processor, the instructions are further operable to cause the device to: Decoding of data on the downlink data channel identified by the most recent DCI message, which indicates the MCS value within the set of reserved modulation and coding scheme (MCS) values ​​in the coherent DCI messages, is suppressed.

17. The apparatus of claim 12, wherein, Each of the indicator values ​​corresponds to the New Data Indicator (NDI) field of one of the coherent DCI messages.

18. The apparatus of claim 12, wherein, Each of the coherent DCI messages corresponds to a Hybrid Automatic Repeat Request (HARQ) process.

19. An apparatus for conducting wireless communication at a base station, comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and, when executed by the processor, are operable to cause the device to: A downlink control information (DCI) message is transmitted to the user equipment (UE) indicating the set of resources allocated to the UE for transmission; as well as Data is transmitted to the UE to synchronize a discontinuous reception (DRX) cycle with the UE based on the absence of the transmission in the resource set allocated to the UE, wherein the data is transmitted to synchronize the DRX cycle with the UE by restarting an inactive timer at the UE; Transmit another DCI message to the UE, having an indicator value that indicates the association with the new transmission; And one of the following: Data is transmitted to the UE before the inactive timer expires based on the other DCI message having the indicator value indicating the association with the new transmission, or Data is received from the UE based on the other DCI message having the indicator value that indicates the association with the new transmission.

20. The apparatus of claim 19, wherein, The data transmitted to synchronize the DRX cycle with the UE includes: Based on the absence of the transmission in the resource set allocated to the UE, another DCI message is transmitted to the UE to schedule the data on another resource set of the downlink data channel; and The data is transmitted to the UE on the other resource set of the downlink data channel.

21. The apparatus of claim 19, wherein, The data includes fictitious data.

22. The apparatus of claim 19, wherein, The DCI message further indicates at least one of the following: a reserved MCS value within the set of modulation and coding scheme (MCS) values, or a redundant value greater than 0.

Images