Coordination of multiple configured grant uplinks with or without retransmission timers

Abstract

Dynamic grant (DG) for retransmission by user equipment (UE) uses communication resources more efficiently, while configured grant (CG) for retransmission by UE reduces overhead and latency. The base station (BS) uses radio resource control signaling to configure the UE with or without a retransmission timer. The BS sends a CG configuration set to the UE to configure a configured grant uplink (CG‑UL) process. The CG configuration set includes information indicating whether the cg‑RetransmissionTimer is associated with the CG‑UL process. The BS is also configured to receive communications from the UE on the UL. Communications from the UE are received based on the CG‑UL process set and an indication of whether the cg‑RetransmissionTimer is associated with the CG‑UL process. For multiple CG‑UL processes of the UE, the UE may have different channel conditions, and therefore using a combination of CG-based retransmission and DG-based retransmission will reduce latency and overhead, and use resources more efficiently.

Description

Technical Field

[0001] Generally, the present disclosure relates to communication systems, and more particularly, to dynamic switching between data retransmissions based on retransmission timers or uplink grants. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting 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.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., together 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 may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5GNR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an extensive overview of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0005] Dynamically scheduled data retransmissions (dynamic grants or DG) are based on indications of uplink (UL) grants from the base station (BS). Non-dynamically scheduled data retransmissions (configured grants or CG) are based on the configured parameter cg-RetransmissionTimer. Dynamic grants for retransmissions use communication resources more efficiently, while configured grants for retransmissions reduce overhead and latency.

[0006] In wireless communication, a BS configures a User Equipment (UE) using Radio Resource Control (RRC) signaling. The UE may be configured with a retransmission timer or without a retransmission timer.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. A BS apparatus is configured to send a CG configuration set that configures a configured granted uplink (CG-UL) process set to a UE. The CG configuration set includes information indicating whether a cg-RetransmissionTimer is associated with the CG-UL process. The BS apparatus is also configured to receive communications from the UE on the UL. The communications from the UE are received based on the CG-UL process set and the indication of whether the cg-RetransmissionTimer is associated with the CG-UL process.

[0008] To achieve the foregoing and related purposes, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 3 is a schematic diagram showing an example of a base station and a user equipment (UE) in an access network.

[0015] Figure 4 is a diagram showing an example communication between a UE and a BS using a cg-retransmission timer.

[0016] Figure 5 is a diagram illustrating example communications between a UE and a BS using UL Grant.

[0017] Figure 6 is a diagram illustrating example communications between a UE and a BS for switching from UL Grant to cg-Retransmission Timer.

[0018] Figure 7 is a flow chart of a method of wireless communication.

[0019] Figure 8 is a flow chart of a method of wireless communication.

[0020] Fig. 9 is a schematic diagram illustrating an example of a hardware implementation for an example UE device.

[0021] Fig.10 is a schematic diagram illustrating an example of a hardware implementation for an example BS apparatus. DETAILED DESCRIPTION

[0022] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. For the purpose of providing a comprehensive understanding of each concept, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams in order to avoid obscuring such concepts.

[0023] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the detailed description below by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements") and illustrated in the accompanying drawings. 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.

[0024] For example, an element or any part of an element or any combination of elements can 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, systems on 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 various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

[0025] Accordingly, in one or more example embodiments, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by 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 disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that may be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0026] Figure 1 1 is a schematic diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a 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 a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0027] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: transmission of user data, wireless channel encryption and decryption, 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, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) via a third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0028] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There can be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0029] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

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

[0032] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). The frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is typically (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0033] In view of the above, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can broadly represent a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can broadly represent a frequency that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

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

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

[0036] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides IP address allocation to the UE as well as other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provision and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0037] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) stream (PSS) service, and / or other IP services.

[0038] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver, a radio base station, a radio transceiver, a transceiver functional unit, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio unit, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, an oven, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a user agent, a mobile client, a client, or some other suitable terminology.

[0039] Reference again Figure 1 In some aspects, the UE 104 may be configured with a dynamic / configured grant component (198) that allows the UE 104 to retransmit based on a UL grant or a cg-RetransmissionTimer. In some aspects, the base station 180 may be configured with a dynamic / configured grant component (199) that allows the BS 180 to configure or reconfigure the UE 104 to retransmit based on a UL grant or a cg-RetransmissionTimer. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0040] Figure 2A is a diagram 200 showing an example of a first subframe within a 5G NR frame structure. Figure 2B is a schematic diagram 230 showing an example of DL channels within a 5G NR subframe. Figure 2C is a diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D280 is a diagram showing an example of UL channels within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within a subcarrier set is dedicated to either DL or UL), or can be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within a subcarrier set is dedicated to both DL and UL). Figure 2A , 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured to have a slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured to have a slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured to have any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured to have a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). It should be noted that the description below also applies to the 5G NR frame structure as TDD.

[0041] Other wireless communication technologies may have different frame structures or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, 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, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe may be based on the time slot configuration and numerology. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2 μtime slots / subframe. The subcarrier spacing and symbol length / duration are functions of the digital scheme. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is digital scheme 0 to 4. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for slot configuration 0 (with 14 symbols per slot) and digital scheme μ=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 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific numbering scheme.

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

[0043] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0044] Figure 2BExamples of various DL channels within a subframe of a frame are shown. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including four consecutive REs in one OFDM symbol. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at larger and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the above-mentioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to 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 that is not sent through the PBCH (such as a system information block (SIB)), and paging messages.

[0045] like Figure 2C As shown, some of the 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 may send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of the subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0046] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) information (ACK / negative ACK (NACK)) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0047] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting of 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 for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and switching support functions; RLC layer functions associated with: transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0048] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 including the physical (PHY) layer may include error detection of the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The 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-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes and for spatial processing. The channel estimates may be derived based on a reference signal and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0049] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

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

[0051] Similar to the functions described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0052] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0053] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0054] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The 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 operations.

[0055] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The 198 came to execute all aspects.

[0056] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The 198 came to execute all aspects.

[0057] In wireless communication, a BS may configure UL data transmission without utilizing UL grants, for example using semi-static configuration or optional DCI activation. The configured grant UL may be configured using a CG configuration. Some parameters associated with a HARQ process configured for type 1 (RRC-based) where the configuration is handled by RRC include: a configured scheduling (CS)-radio network temporary identifier (RNTI) (cs-RNTI) for retransmissions; a periodicity for identifying the periodicity of the configured grant; a timeDomainOffset for the offset of resources in the time domain relative to SFN=0; a timeDomainAllocation in the time domain for a configured uplink grant containing a startSymbolAndLength (SLIV); and nrofHARQ-Processes for identifying the number of HARQ processes for the configured grant.

[0058] Some parameters related to HARQ processes configured for type 2 (DCI activation / deactivation) configured via RRC processing include: a configured scheduling (CS)-radio network temporary identifier (RNTI) (CS-RNTI) for activation, deactivation and retransmission; a periodicity for identifying the periodicity of the CG; nrofHARQ-Processes for identifying the number of HARQ processes allowed for the configuration; wherein L1 signaling indicates additional parameters for resources, which include an offset associated with the periodicity; and wherein MAC CE is used as an ACK for the L1 signaling for activation / deactivation.

[0059] In one aspect for time domain resource allocation (TDRA), multiple allocated time slots are added starting from a time slot offset and using a time slot period. In addition, multiple consecutive PUSCHs are added in the time slot, where the length of each PUSCH is the same. The time domain resource assignment in the configured grant is repeated over multiple added time slots within the time slot allocated by the CG. The same symbol allocation and mapping type are used for the first PUSCH in each time slot in the allocated CG time slot. In addition, the SLIV indicates information about the first PUSCH in the time slot and then repeats with the same length.

[0060] In one aspect for CG-uplink control information (CG-UCI), the CG-UCI is included in each CG-PUSCH transmission. For example, the CG-UCI may include at least the following information: HARQ ID, network device interface (NDI), redundancy version (RV), and channel occupancy time (COT) sharing information.

[0061] In one aspect, two types of PUSCH repetitions are defined, both of which apply to dynamically granted retransmissions and configured granted retransmissions. PUSCH repetition type A is not optimized unless the number of repetitions can be dynamically indicated. For example, if the number of repetitions K>1, the same SLIV applies across K consecutive time slots. PUSCH repetition type B provides repetitions within / across time slots, repetitions across time slot boundaries, dynamic indication of the number of repetitions, nominal inter-PUSCH frequency hopping, new U / D symbol interaction, and new SLIV, to name a few examples. For example, K nominal repetitions (each with a nominal length L) are sent back-to-back starting from symbol S, where S and L are given by the SLIV.

[0062] On the other hand, when the retransmission of the CG-UL is based on an indication of a UL grant, the retransmission is considered to be dynamically granted. When the retransmission CG-UL process is based on the CG (e.g., based on the parameter cg-RetransmissionTimer), the retransmission is considered to be configured to be granted. CG-based retransmission can reduce PDCCH overhead, thereby reducing transmission delay, while DG-based retransmission provides a more efficient use of resources. For multiple CG-UL processes of a UE, the UE may have different channel conditions, and therefore using a combination of CG-based retransmission and DG-based retransmission will reduce latency as well as reduce overhead, and use resources more efficiently.

[0063] Figure 44 is a schematic diagram illustrating an example communication 400 using a cg-RetransmissionTimer between a UE 402 and a BS 404. In an unlicensed band, retransmissions are typically implemented using configured grants. At 406, the BS 404 configures the UE 402 using an RRC configuration. For example, the RRC configuration configures retransmissions to be based on a cg-RetransmissionTimer and a CG-Downlink Feedback Information (DFI) (CG-DFI). The cg-RetransmissionTimer parameter provides a duration after a configured grant transmission (or subsequent retransmission) of a HARQ process when the UE involuntarily retransmits the HARQ process.

[0064] In one aspect, if DCI format 0_1 ​​is used to indicate CG-DFI, the HARQ-ACK bitmap field is set to 16 bits, where the order of the bitmap to HARQ process index mapping is such that the HARQ process index is mapped in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the bitmap. For example, for each bit in the bitmap, a value of 1 indicates ACK, while a value of 0 indicates NACK. In addition, the TPC command for the scheduled PUSCH is allocated 2 bits, and all remaining bits in format 0_1 ​​are set to zero. If the DFI indicates that the transmission is NACK, or if the UE does not receive the DFI during the time defined by the cg-RetransmissionTimer, a retransmission will occur. Otherwise, if a DFI is received and it indicates ACK, no retransmission will occur.

[0065] At 408, UE 402 sends new data to BS 404. The transmission is for the start time of cg-RetransmissionTimer. At 410, BS 404 responds to the transmission of UE 402 by sending a DFI with NACK or by not sending a DFI. At 412, when an amount of time equal to the value of the cg-RetransmissionTimer parameter has passed, UE 402 retransmits the data to BS 404. The retransmission at 412 starts a new retransmission time period. At 414, BS 404 responds to UE 402 by sending a DFI with ACK, and at 416, UE 402 sends new data to BS 404.

[0066] Figure 55 is a schematic diagram illustrating an example communication 500 using UL grants between a UE 502 and a BS 504. In a licensed band, dynamic grants are typically used to implement retransmissions. For example, if the BS 504 decodes a data transmission from the UE 502 as a NACK, the BS 504 will send an uplink grant to the UE 502 and indicate that a retransmission is required. Additionally, if the BS 504 misses a data transmission from the UE 502, the BS 504 will not send an uplink grant to the UE 502, and the UE 502 will not perform a retransmission.

[0067] In one aspect, at 506, BS 504 configures UE 502 with RRC configuration. At 508, UE 502 sends new data to BS 504. At 510, BS 504 responds to the transmission of UE 502 by NACK with uplink grant. At 512, UE 502 retransmits data to BS 504 as scheduled in the uplink grant. At 514, UE determines whether it has received a retransmission request from BS. If UE has not received a retransmission request (e.g., DCI 0_0 / 0_1 with NDI that is not switched) after a period of time, UE 502 determines that BS 504 successfully received and decoded retransmission 512. After determining that BS 504 successfully received and decoded retransmission 512, at 516, UE 502 sends new data to BS 504.

[0068] Figure 6 is a schematic diagram of an example communication 600 showing switching from UL grant to cg-Retransmission timer between a UE 602 and a BS 604. In one aspect, for URLLC, retransmission to the CG-UL is based on an indication of an uplink grant and is dynamically granted thereby. In one aspect, retransmission to the CG-UL is based on a DFI and a configured grant with a retransmission timer parameter cg-RetransmissionTimer. Advantageously, in wireless communications, it is allowed that the cg-RetransmissionTimer is not configured for the CG-UL.

[0069] Therefore, in one aspect, when multiple CG-UL processes are configured, all cg-RetransmissionTimer configurations are configured identically. In other words, all configured CG-UL processes are configured to have cg-RetransmissionTimer, or all configured CG-UL processes are configured to not have cg-RetransmissionTimer.

[0070] In another aspect, each CG-UL process may be independently configured with or without a cg-RetransmissionTimer. Furthermore, for those CG-UL processes configured with a cg-RetransmissionTimer, the value of the cg-RetransmissionTimer period parameter may vary.

[0071] For example, in the frequency domain, if there are multiple listen-before-talk (LBT) bandwidths, some CG-UL processes in some LBT bandwidths with low interference can be configured without cg-RetransmissionTimer. In addition, other CG-UL processes in other LBT bandwidths with high interference can be configured with cg-RetransmissionTimer.

[0072] In one aspect, different logical channels may have different service modes. For example, some logical channels may be used for URLLC, while other logical channels may be used for eMBB. Therefore, the CG-UL process corresponding to the URLCC channel may be configured without a cg-RetransmissionTimer, and the CG-UL process corresponding to the eMBB channel may be configured with a cg-RetransmissionTimer.

[0073] In one aspect, in the time domain, channel conditions may change during a time period. Therefore, BS 604 is configured to dynamically switch the retransmission mode of the CG-UL process on UE 602 to reduce PDCCH overhead and reduce transmission delay, and optimize efficient use of resources.

[0074] In one aspect, for a CG-UL process configured without a cg-RetransmissionTimer, different CG-UL processes are configured with different sets of HARQ process IDs to avoid overlap. In addition, for a CG-UL process configured with a cg-RetransmissionTimer, the UE 602 is configured to select a HARQ process ID from the HARQ process IDs that can be used for the configured permitted configuration.

[0075] In a hybrid configuration, a first subset of CG-UL processes is configured with a cg-RetransmissionTimer and a second subset of CG-UL processes is configured with a cg-RetransmissionTimer. In this aspect, the HARQ process ID for each CG-UL process must be determined.

[0076] In one aspect, the available HARQ process IDs may be arranged into a first set (Set 1) for CG-UL processes configured without a cg-RetransmissionTimer, a second set (Set 2) for CG-UL processes configured with a cg-RetransmissionTimer, and a third set for other scheduled grants. The first set of HARQ process IDs may be further arranged into subsets, where the number of subsets is equal to the number of CG-UL processes. For the HARQ process IDs in the second set, the UE 602 is configured to select a HARQ process ID from the second set for each CG-UL process configured with a cg-RetransmissionTimer.

[0077] In one aspect, the DFI for the CG-PUSCH includes: HARQ information including HARQ-ACK information. Thus, in one aspect, the HARQ-ACK information is included in the DFI and indicates the number of bits used for the HARQ-ACK bitmap. For example, the number of bits used for the HARQ-ACK bitmap may be equal to the number of CG-UL processes with cg-RetransmissionTimer.

[0078] Return to Figure 6 , in one aspect, at 606, BS 604 configures UE 602 with an RRC configuration indicating no cg-RetransmissionTimer. At 608, UE 602 sends new data to BS 604. At 610, BS 604 responds to the transmission of UE 602 with a NACK with an uplink grant. At 612, UE 602 retransmits the data to BS 604 as scheduled in the uplink grant.

[0079] At 614, BS 604 monitors communications during a monitoring time window with a predefined periodicity. Monitoring may include monitoring the number of UL grants sent for CG-UL retransmissions during the monitoring time window. For example, BS 604 may count the number of UL grants sent to UE 602. BS 604 may also monitor and / or count the number of DFIs with ACKs sent to UE 602.

[0080] Monitoring may also include evaluating communication channel characteristics such as reference signal received quality (RSRQ), reference signal received power (RSRP), signal to noise ratio (SNR), signal to interference plus noise ratio (SINR), or bandwidth energy associated with reception from the UE on the UL.

[0081] At 616, for example, when the number of UL grants exceeds a threshold, the BS 604 sends a switching indication to the UE 602, which is used to indicate that one or more CG-UL processes in the CG-UL process should be switched to a configuration with a cg-RetransmissionTimer.

[0082] At 618, UE 602 sends new data to BS 604. This transmission is for the start time of the newly configured cg-RetransmissionTimer. At 620, BS 604 responds to the transmission of UE 602 by sending a DFI with a NACK or by not sending a DFI. At 622, when an amount of time equal to the value of the cg-RetransmissionTimer parameter has passed, UE 602 retransmits the data to BS 604. As wireless communication between UE 602 and BS 604 continues, additional retransmissions may or may not be required.

[0083] Figure 7 700 is a flowchart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102 / 180; apparatus 1002). At 702, the base station is configured to send a configured grant configuration set to a UE. The CG configuration set is used to configure a CG-UL process set and includes information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set. For example, 702 may be performed by a user from Fig.10 The configured permission component 1040 is executed.

[0084] At 704, the BS receives a transmission on the UL from the UE. The transmission on the UL from the UE may be based on the CG-UL process set and an indication of whether at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set. For example, 704 may be received from Fig.10 The retransmission component 1042 is used to perform.

[0085] In one aspect, at least one cg-RetransmissionTimer includes one cg-RetransmissionTimer, and the CG configuration set includes information indicating whether the same cg-RetransmissionTimer is associated with the entire CG-UL process set.

[0086] In one aspect, each CG configuration in the CG configuration set includes information indicating whether the cg-RetransmissionTimer is associated with the corresponding CG-UL process. In addition, each CG configuration in the CG configuration set may also include information indicating that the same cg-RetransmissionTimer is associated with the corresponding CG-UL process. Alternatively, each CG configuration in the CG configuration set may include information indicating that no retransmission timer is associated with the corresponding CG-UL process. Alternatively, each CG configuration in the CG configuration set may include information indicating that an independent cg-RetransmissionTimer is associated with each corresponding CG-UL process or that no cg-RetransmissionTimer is associated with the corresponding CG-UL process. For example, each CG configuration in the first subset of CG configurations may include information indicating that a first cg-RetransmissionTimer is associated with the corresponding CG-UL process and also indicating that each CG configuration in the second subset of CG configurations includes information indicating that no cg-RetransmissionTimer is associated with the corresponding CG-UL process.

[0087] In one aspect, when the transmission received from the UL is associated with eMBB communication, the transmission received from the UL is associated with a first subset of CG configurations. In an alternative aspect, when the transmission received from the UL is associated with URLLC, the transmission received from the UL is associated with a second subset of CG configurations.

[0088] At 706, the BS may optionally send the DFI to the UE. In one aspect, 706 may be provided by Fig.10 The BS may optionally send a DFI including HARQ-ACK information for the first CG-UL process subset based on the first HARQ process ID set.

[0089] In one aspect, a CG-UL process in the second CG-UL process subset is associated with a HARQ process identifier in the second HARQ process identifier set. In addition, the HARQ-ACK information for the first CG-UL process subset may include a HARQ-ACK bitmap that includes one bit for each CG-UL process in the first CG-UL process subset.

[0090] In one aspect, when the CG configuration set includes a first CG configuration indicating that a first cg-RetransmissionTimer is associated with a first CG-UL process, the BS sends a DFI including an ACK or a NACK based on a UL received from the UE.

[0091] At 708, the BS may optionally send an UL grant to the UE. In one aspect, 708 may be performed by a Fig.10 The BS may send a UL grant to the UE when an expected transmission is not received from the UE or when a received transmission cannot be decoded. For example, when a first subset of CG configurations is associated with a first CG-UL process subset and is also associated with a first HARQ process identifier set, and a second subset of CG configurations is associated with a second CG-UL process subset and is also associated with a second HARQ process identifier set, the BS may send a UL grant for the second CG-UL process subset based on the second HARQ process ID set and based on reception from the UE in the UL. The UE may also send a UL grant for a CG-UL retransmission for the first CG-UL process to the UE when the reception from the UE on the UL is undecodable.

[0092] At 710, the BS may optionally monitor the communication characteristics during the time window. The time window may be periodic. In one aspect, 710 may be provided by Fig.10 The BS may be configured to monitor the number of ACKs sent during the time window when the UE is configured with cg-RetransmissionTimer. In another aspect, when the UE is configured without cg-RetransmissionTimer, the BS may monitor the number of UL grants sent for CG-UL retransmissions during the time window.

[0093] At 712, the BS may optionally determine communication channel characteristics. In one aspect, 712 may be determined by Fig.10The BS may be configured to perform the channel component 1046 of the UE. For example, when the UE is configured with a cg-RetransmissionTimer, the BS may determine at least one of the following: a reference signal received quality (RSRQ), a reference signal received power (RSRP), a signal to noise ratio (SNR), a signal to interference plus noise ratio (SINR), or a bandwidth energy associated with reception from the UE on the UL. In addition, when the UE is configured without a cg-RetransmissionTimer, the BS may also determine at least one of the following: a reference signal received quality (RSRQ), a reference signal received power (RSRP), a signal to noise ratio (SNR), a signal to interference plus noise ratio (SINR), or a bandwidth energy associated with reception from the UE on the UL.

[0094] At 714, the BS may optionally send a handover indication to the UE. In one aspect, 714 may be provided by a Fig.10 The retransmission component 1042 is used to perform.

[0095] For example, when the UE is configured with cg-RetransmissionTimer, when the number of ACKs sent is greater than a threshold, the BS may send a switching indication to the UE, which is used to indicate that the first CG-UL process should not be associated with the cg-RetransmissionTimer. When at least one of RSRQ, RSRP, SNR, or SINR is greater than a first threshold, or the determined bandwidth energy is less than a second threshold, the BS may also send a switching indication to the UE, which is used to indicate that the first CG-UL process should not be associated with the cg-RetransmissionTimer.

[0096] In addition, when the UE is configured without cg-RetransmissionTimer, when the number of UL grants sent for CG-UL retransmissions is greater than a threshold, the BS may send a switching indication to the UE, indicating that the first CG-UL process should be associated with the first cg-RetransmissionTimer. When at least one of RSRQ, RSRP, SNR, or SINR is less than a first threshold, or the determined bandwidth energy is greater than a second threshold, the BS may also send a switching indication to the UE, indicating that the first CG-UL process should be associated with the first cg-RetransmissionTimer.

[0097] In one aspect, when some CG-UL processes are configured to have cg-RetransmissionTimer and some CG-UL processes are configured not to have cg-RetransmissionTimer, the BS may send a switching indication to the UE to switch the first CG-UL process configured to have cg-RetransmissionTimer to one configured not to have cg-RetransmissionTimer, and may also send a switching indication to the UE to switch the second CG-UL process configured not to have cg-RetransmissionTimer to one configured to have cg-RetransmissionTimer.

[0098] In one aspect, the handover indication may be sent via at least one bit in a physical downlink control channel (PDCCH). In another aspect, the handover indication may be sent via at least one bit in a group common (GC) physical downlink control channel (PDCCH), which provides the handover indication to a set of UEs.

[0099] In one aspect, the GC-PDCCH may be sent in downlink control information (DCI). For example, the GC-PDCCH may be sent in a DCI format 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, or 2_6 message. Alternatively, the GC-PDCCH may be sent in a DCI format 2_x message, where x>6.

[0100] In one aspect, the switching indication may be sent via at least one bit in a medium access control (MAC) control element (CE) (MAC-CE). In addition, the switching indication may be sent via at least two bits in the MAC-CE to indicate multiple CG-UL configurations. In one aspect, the total amount of the at least two bits is equal to the number of CG configurations in the CG configuration set.

[0101] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; device 902). At 802, the UE receives a CG configuration set from a BS. In one aspect, 802 may be performed by Fig. 9 The configured permission component 940 is executed. For example, the UE may receive a CG configuration set for configuring a CG-UL process set from the BS. The CG configuration set may include information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set.

[0102] At 804, the UE transmits to the BS on the UL. For example, 804 may be performed by Fig. 9 The UE may transmit to the BS on the UL based on the CG-UL process set and an indication of whether at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set. For example, the at least one cg-RetransmissionTimer may include one cg-RetransmissionTimer, and the CG configuration set may include information indicating whether the same one cg-RetransmissionTimer is associated with the CG-UL process set.

[0103] In one aspect, each CG configuration in the CG configuration set includes information indicating whether a cg-RetransmissionTimer is associated with the corresponding CG-UL process. For example, all CG-UL processes may be associated with the same cg-RetransmissionTimer, or all CG-UL processes may be associated with no cg-RetransmissionTimer, or there may be a mixture of some CG-UL processes associated with the same cg-RetransmissionTimer and some CG-UL processes associated with no cg-RetransmissionTimer. In one aspect, of those CG-UL processes associated with a cg-RetransmissionTimer, some may be associated with a first cg-RetransmissionTimer and some may be associated with a second cg-RetransmissionTimer.

[0104] In one aspect, each CG configuration in the CG configuration set includes information indicating that an independent cg-RetransmissionTimer is associated with the corresponding CG-UL process or that no cg-RetransmissionTimer is associated with the corresponding CG-UL process. In a further aspect, each CG configuration in a first subset of CG configurations may include information indicating that a first cg-RetransmissionTimer is associated with the corresponding CG-UL process, and each CG configuration in a second subset of CG configurations may include information indicating that no cg-RetransmissionTimer is associated with the corresponding CG-UL process.

[0105] For example, each CG configuration in the first subset of CG configurations may include information indicating that an enhanced mobile broadband (eMBB) channel is associated with the corresponding CG-UL process. Alternatively, each CG configuration in the second subset of CG configurations may include information indicating that an ultra-reliable low-latency communication (URLLC) channel is associated with the corresponding CG-UL process.

[0106] At 806, the UE optionally receives a DFI from the BS. For example, 806 may be performed by Fig. 9 The UE may further receive a DFI including HARQ-ACK information for the first CG-UL process subset based on the first HARQ process ID set.

[0107] For example, a CG-UL process in the second CG-UL process subset can be associated with a HARQ process identifier in the second HARQ process identifier set. In addition, the HARQ-ACK information for the first CG-UL process subset may include a HARQ-ACK bitmap that includes one bit for each CG-UL process in the first CG-UL process subset.

[0108] At 808, the UE may optionally receive a UL grant from the BS. For example, 808 may be performed by Fig. 9 The UE may further receive a UL grant for a second CG-UL process subset based on the second HARQ process ID set and based on a transmission in the UL to the BS.

[0109] For example, the CG configuration set may include a first CG configuration indicating that the cg-RetransmissionTimer is not associated with a first CG-UL process, and the UE may receive from the BS an UL grant for CG-UL retransmission for the first CG-UL process when the transmission to the BS on the UL is undecodable.

[0110] At 810, the UE may optionally receive a handover indication from the BS. For example, 810 may be performed by Fig. 9The retransmission component 942 is executed. For example, when the UE is configured with a cg-RetransmissionTimer, when the number of ACKs sent by the BS is greater than a threshold, the UE can receive a switching indication indicating that the first CG-UL process should not be associated with the cg-RetransmissionTimer. When at least one of RSRQ, RSRP, SNR, or SINR is greater than a first threshold, or the determined bandwidth energy is less than a second threshold, the UE can also receive a switching indication indicating that the first CG-UL process should not be associated with the cg-RetransmissionTimer.

[0111] In addition, when the UE is configured without a cg-RetransmissionTimer, when the number of UL grants sent by the BS for CG-UL retransmissions is greater than a threshold, the UE may receive a switching indication indicating that the first CG-UL process should be associated with the first cg-RetransmissionTimer. The UE may also receive a switching indication indicating that the first CG-UL process should be associated with the first cg-RetransmissionTimer when at least one of RSRQ, RSRP, SNR, or SINR is less than a first threshold, or the determined bandwidth energy is greater than a second threshold.

[0112] In one aspect, when some CG-UL processes of the UE are configured to have a cg-RetransmissionTimer and some CG-UL processes of the UE are configured to have a cg-RetransmissionTimer, the UE may receive a switching indication to switch a first CG-UL process configured to have a cg-RetransmissionTimer to one configured not to have a cg-RetransmissionTimer, and may also receive a switching indication to switch a second CG-UL process configured not to have a cg-RetransmissionTimer to one configured to have a cg-RetransmissionTimer.

[0113] In one aspect, the handover indication may be received via at least one bit in a physical downlink control channel (PDCCH). In another aspect, the handover indication may be received via at least one bit in a group common (GC) physical downlink control channel (PDCCH), wherein the GC-PDCCH provides the handover indication to the set of UEs.

[0114] In one aspect, the GC-PDCCH may be received in downlink control information (DCI). For example, the GC-PDCCH may be received in a DCI format 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, or 2_6 message. Alternatively, the GC-PDCCH may be received in a DCI format 2_x message, where x>6.

[0115] In one aspect, the switching indication may be received via at least one bit in the MAC-CE. In addition, the switching indication may be received via at least two bits in the MAC-CE to indicate multiple CG-UL configurations. In one aspect, the total amount of the at least two bits is equal to the number of CG configurations in the CG configuration set.

[0116] Fig. 9 900 is a schematic diagram showing an example of a hardware implementation for an apparatus 902. The apparatus 902 is a UE and includes a cellular baseband processor 904 (also referred to as a modem) coupled to a cellular RF transceiver 922 and one or more subscriber identity modules (SIM) cards 920, an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910, a Bluetooth module 912, a wireless local area network (WLAN) module 914, a global positioning system (GPS) module 916, and a power supply 918. The cellular baseband processor 904 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 922. The cellular baseband processor 904 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 904 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 904, the software causes the cellular baseband processor 904 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 904 when executing software. The cellular baseband processor 904 also includes a receiving component 930, a communication manager 932, and a transmitting component 934. The communication manager 932 includes one or more of the components shown. The components within the communication manager 932 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 904. The cellular baseband processor 904 may be a component of the UE 350 and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360. In one configuration, the device 902 may be a modem chip and include only the baseband processor 904, and in another configuration, the device 902 may be the entire UE (e.g., see Figure 3 350) and includes the above-mentioned additional modules of device 902.

[0117] The communication manager 932 includes a configured grant component 940 configured to receive a configured grant configuration from the BS, for example, as described in conjunction with Figure 8 The communication manager 932 also includes a retransmission component 942, which is configured to communicate with the BS based on the retransmission timer and the uplink grant, and switch between the retransmission timer and the uplink grant based on an indication from the BS, for example, as combined with Figure 8 As described in 804, 806, 808 and 810.

[0118] The device may include performing the above Figure 8 Each box in the flowchart of the algorithm has an additional component. Therefore, the above Figure 8 Each block in the flowchart of can be performed by a component, and the device may include one or more of these components. These components can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by a processor, or some combination thereof.

[0119] In one configuration, the device 902 (and specifically, the cellular baseband processor 904) includes: a unit for receiving a configured granted (CG) configuration set configuring a configured granted uplink (CG-UL) process set from a base station (BS), the CG configuration set including information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set; and a unit for transmitting to the BS on the UL based on the CG-UL process set and an indication that at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set. The above-mentioned units can be one or more of the above-mentioned components of the device 902 configured to perform the functions recorded by the above-mentioned units. As described above, the device 902 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the above-mentioned units can be a TX processor 368, an RX processor 356, and a controller / processor 359, which are configured to perform the functions recorded by the above-mentioned units.

[0120] Fig.101 is a schematic diagram 1000 showing an example of a hardware implementation for an apparatus 1002. The apparatus 1002 is a BS and includes a baseband unit 1004. The baseband unit 1004 can communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1004 may include a computer-readable medium / memory. The baseband unit 1004 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the baseband unit 1004, the software causes the baseband unit 1004 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1004 when executing the software. The baseband unit 1004 also includes a receiving component 1030, a communication manager 1032, and a sending component 1034. The communication manager 1032 includes one or more of the components shown. The components within the communication manager 1032 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1004. The baseband unit 1004 may be a component of the BS 310 and may include at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 , and / or the memory 376 .

[0121] The communication manager 1032 includes a configured grant component 1040 configured to configure the UE for retransmission based on a retransmission timer or based on an uplink grant, for example, as described in conjunction with Figure 7 The communication manager 1032 also includes a retransmission component 1042, which is configured to communicate with the UE based on the retransmission timer and the uplink grant, and indicate to the UE when to switch between the retransmission timer and the uplink grant, for example, as combined with Figure 7 The communication manager 1032 also includes a monitor component 1044, which is configured to monitor channel conditions and other communication characteristics to determine whether to switch between the retransmission timer and the uplink grant, for example, as described in conjunction with Figure 7 As described in 710 and 712.

[0122] The device may include performing the above Figure 8 Each box in the flowchart of the algorithm has an additional component. Therefore, the above Figure 8 Each block in the flowchart of can be performed by a component, and the device may include one or more of these components. These components can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by a processor, or some combination thereof.

[0123] In one configuration, the apparatus 1002 (and specifically, the baseband unit 1004) includes: a unit for sending a configured granted (CG) configuration set to a user equipment (UE) configuring a configured granted uplink (CG-UL) process set, the CG configuration set including information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set; and a unit for receiving from the UE on the UL based on the CG-UL process set and an indication of whether at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set. The above-mentioned units may be one or more of the above-mentioned components of the apparatus 1002 configured to perform the functions recorded by the above-mentioned units. As described above, the apparatus 1002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the above-mentioned units may be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions recorded by the above-mentioned units.

[0124] It is to be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. It is to be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in an exemplary order and are not intended to be limited to the specific order or hierarchy provided.

[0125] The foregoing description is provided so that any person skilled in the art can implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to be given the full scope consistent with the language claims, wherein, unless explicitly stated as such, reference to singular elements is not intended to mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while ..." should be interpreted as "under the condition of ...", rather than meaning an immediate time relationship or reaction. That is, these phrases (e.g., "when ...") do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but only mean that the action will occur if the condition is met, but do not require a specific or immediate time constraint for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred to or having advantages over other aspects. Unless otherwise expressly stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is expressly recited in the claims. The words “module,” “mechanism,” “element,” “device,” etc. may not be substitutes for the word “unit.” Thus, no claim element should be interpreted as a functional unit unless the element is explicitly recited using the phrase “a means for….”

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving a configured grant (CG) configuration set configuring a configured grant uplink (CG-UL) process set from a base station (BS), the CG configuration set including information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set; and sending on the UL to the BS based on the CG-UL process set and an indication of whether the at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set, Among them, for the CG-UL process configured without cg-RetransmissionTimer, different CG-UL processes are configured to have different HARQ process IDs.

2. The device according to claim 1, wherein: Each CG configuration in the CG configuration set includes information indicating whether the cg-RetransmissionTimer is associated with the corresponding CG-UL process.

3. The device according to claim 1, wherein: Each CG configuration in the CG configuration set includes information indicating that the same cg-RetransmissionTimer is associated with the corresponding CG-UL process.

4. The device according to claim 1, wherein: Each CG configuration in the CG configuration set includes information indicating that no retransmission timer is associated with the corresponding CG-UL process.

5. The device according to claim 1, wherein: Each CG configuration in the CG configuration set includes information indicating that an independent cg-RetransmissionTimer is associated with the corresponding CG-UL process or no cg-RetransmissionTimer is associated with the corresponding CG-UL process.

6. The device according to claim 5, wherein: Each CG configuration in the first subset of the CG configurations includes information indicating that a first cg-RetransmissionTimer is associated with the corresponding CG-UL process, and wherein each CG configuration in the second subset of the CG configurations includes information indicating that no cg-RetransmissionTimer is associated with the corresponding CG-UL process.

7. The device according to claim 6, wherein: The first subset of CG configurations is associated with a first CG-UL process subset of the CG-UL process set and with a first hybrid automatic repeat request (HARQ) process identifier (ID) set, and the second subset of CG configurations is associated with a second CG-UL process subset of the CG-UL process set and with a second HARQ process identifier set, and the at least one processor is further configured to: receiving downlink feedback information (DFI) including HARQ acknowledgement (ACK) (HARQ-ACK) information for the first subset of CG-UL processes based on the first set of HARQ process IDs; and A UL grant for the second CG-UL process subset is received based on the second HARQ process ID set and based on the transmission on the UL to the BS.

8. The device according to claim 7, wherein: A CG-UL process in the second CG-UL process subset is associated with a HARQ process identifier in the second HARQ process identifier set.

9. The device according to claim 7, wherein: The HARQ-ACK information for the first CG-UL process subset includes a HARQ-ACK bitmap, and the HARQ-ACK bitmap includes one bit for each CG-UL process in the first CG-UL process subset.

10. The device according to claim 1, wherein: The CG configuration set includes a first CG configuration, the first CG configuration indicating that a first cg-RetransmissionTimer is associated with a first CG-UL process, and the at least one processor is further configured to: receiving downlink feedback information (DFI), the DFI comprising one of an acknowledgement (ACK) or a negative ACK (NACK) based on a UL sent to the BS; and When the number of received ACKs is greater than a threshold, a switching indication is received from the BS, where the switching indication is used to indicate that the first CG-UL process should not be associated with cg-RetransmissionTimer.

11. The device according to claim 10, wherein: The handover indication is received via at least one bit in a physical downlink control channel (PDCCH).

12. The device according to claim 10, wherein: The handover indication is received via at least one bit in a group common (GC) physical downlink control channel (PDCCH), the GC-PDCCH providing the handover indication to a set of UEs including the UE.

13. The device according to claim 10, wherein: The handover indication is received via at least one bit in a Medium Access Control (MAC) Control Element (CE) (MAC-CE).

14. An apparatus for wireless communication at a base station (BS), comprising: Memory; as well as at least one processor coupled to the memory and configured to: sending a configured grant (CG) configuration set configuring a configured grant uplink (CG-UL) process set to a user equipment (UE), the CG configuration set including information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set; and receiving on the UL from the UE based on the CG-UL process set and an indication of whether the at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set, Among them, for the CG-UL process configured without cg-RetransmissionTimer, different CG-UL processes are configured to have different HARQ process IDs.

15. The device according to claim 14, wherein: Each CG configuration in the CG configuration set includes information indicating whether the cg-RetransmissionTimer is associated with the corresponding CG-UL process.

16. The device according to claim 15, wherein: Each CG configuration in the CG configuration set includes information indicating that the same cg-RetransmissionTimer is associated with the corresponding CG-UL process.

17. The device according to claim 15, wherein: Each CG configuration in the CG configuration set includes information indicating that no retransmission timer is associated with the corresponding CG-UL process.

18. The device according to claim 15, wherein: Each CG configuration in the CG configuration set includes information indicating that an independent cg-RetransmissionTimer is associated with the corresponding CG-UL process or that no cg-RetransmissionTimer is associated with the corresponding CG-UL process.

19. The device according to claim 18, wherein: Each CG configuration in the first subset of the CG configurations includes information indicating that a first cg-RetransmissionTimer is associated with the corresponding CG-UL process, and wherein each CG configuration in the second subset of the CG configurations includes information indicating that no cg-RetransmissionTimer is associated with the corresponding CG-UL process.

20. The device according to claim 19, wherein When the UL reception is associated with enhanced mobile broadband (eMBB) communication, the UL reception is associated with the first subset of the CG configuration.

21. The device according to claim 19, wherein When UL reception is associated with ultra-reliable low-latency communication (URLLC), the UL reception is associated with the second subset of the CG configuration.

22. The device according to claim 19, wherein The first subset of CG configurations is associated with a first CG-UL process subset of the CG-UL process set and with a first hybrid automatic repeat request (HARQ) process identifier (ID) set, and the second subset of CG configurations is associated with a second CG-UL process subset of the CG-UL process set and with a second HARQ process identifier set, and the at least one processor is further configured to: sending downlink feedback information (DFI) including HARQ acknowledgement (ACK) (HARQ-ACK) information for the first subset of CG-UL processes based on the first set of HARQ process IDs; and Sending a UL grant for the second CG-UL process subset based on the second HARQ process ID set and based on the reception on the UL from the UE.

23. The device according to claim 22, wherein: A CG-UL process in the second CG-UL process subset is associated with a HARQ process identifier in the second HARQ process identifier set.

24. The device according to claim 22, wherein: The HARQ-ACK information for the first CG-UL process subset includes a HARQ-ACK bitmap, and the HARQ-ACK bitmap includes one bit for each CG-UL process in the first CG-UL process subset.

25. The device according to claim 14, wherein: The CG configuration set includes a first CG configuration, the first CG configuration indicating that a first cg-RetransmissionTimer is associated with a first CG-UL process, and the at least one processor is further configured to: transmitting downlink feedback information (DFI) including one of an acknowledgement (ACK) or a negative ACK (NACK) based on a UL received from the UE; monitoring a number of ACKs sent during a time window, the time window being periodic; and When the number of ACKs sent is greater than a threshold, a switching indication is sent to the UE, where the switching indication is used to indicate that the first CG-UL process should not be associated with cg-RetransmissionTimer.

26. The device according to claim 14, wherein: The CG configuration set includes a first CG configuration, the first CG configuration indicating that a cg-RetransmissionTimer is not associated with a first CG-UL process, and the at least one processor is further configured to: When the reception from the UE on the UL is undecodable, sending to the UE a UL grant for CG-UL retransmission for the first CG-UL process; monitoring a number of UL grants sent for CG-UL retransmissions during a time window, the time window being periodic; and When the number of UL grants sent for the CG-UL retransmission is greater than a threshold, a switching indication is sent to the UE, where the switching indication is used to indicate that the first CG-UL process should be associated with a first cg-RetransmissionTimer.

27. The device according to claim 14, wherein: The CG configuration set includes a first CG configuration, the first CG configuration indicating that a first cg-RetransmissionTimer is associated with a first CG-UL process, and the at least one processor is further configured to: determining at least one of: a reference signal received quality (RSRQ), a reference signal received power (RSRP), a signal to noise ratio (SNR), a signal to interference plus noise ratio (SINR), or a bandwidth energy associated with reception on a UL from the UE; as well as When at least one of the RSRQ, RSRP, SNR or SINR is greater than the first threshold, or the determined bandwidth energy is less than the second threshold, a switching indication is sent to the UE, and the switching indication is used to indicate that the first CG-UL process should not be associated with cg-RetransmissionTimer.

28. The device according to claim 14, wherein: The CG configuration set includes a first CG configuration, the first CG configuration indicating that a cg-RetransmissionTimer is not associated with a first CG-UL process, and the at least one processor is further configured to: determining at least one of: a reference signal received quality (RSRQ), a reference signal received power (RSRP), a signal to noise ratio (SNR), a signal to interference plus noise ratio (SINR), or a bandwidth energy associated with reception on a UL from the UE; as well as When at least one of the RSRQ, RSRP, SNR or SINR is less than the first threshold, or the determined bandwidth energy is greater than the second threshold, a switching indication is sent to the UE, and the switching indication is used to indicate that the first CG-UL process should be associated with the first cg-RetransmissionTimer.

29. The device according to claim 14, wherein: The CG configuration set includes a first CG configuration, the first CG configuration indicating whether a first cg-RetransmissionTimer is associated with a first CG-UL process or no cg-RetransmissionTimer is associated with the first CG-UL process, and the at least one processor is further configured to: A switching indication is sent to the UE to switch the association between the first CG-UL process and the first cg-RetransmissionTimer, wherein the switching indication is used to indicate one of the following items: the first CG-UL process should be associated with the first cg-RetransmissionTimer, or the first CG-UL process should be associated with no cg-RetransmissionTimer.

30. The device according to claim 29, wherein: The handover indication is sent via at least one bit in a group common (GC) physical downlink control channel (PDCCH), and the GC-PDCCH provides the handover indication to a set of UEs including the UE.

31. The device according to claim 30, wherein The GC-PDCCH is sent in downlink control information (DCI) format 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, 2_6 or 2_x message, where x>6.

32. The device according to claim 29, wherein: The handover indication is sent via at least one bit in a medium access control (MAC) control element (CE) (MAC-CE).

33. The device according to claim 29, wherein: The switching indication is sent via at least two bits in a medium access control (MAC) control element (CE) (MAC-CE) to indicate multiple CG-UL configurations.

34. A method of wireless communication at a user equipment (UE), comprising: receiving a configured grant (CG) configuration set configuring a configured grant uplink (CG-UL) process set from a base station (BS), the CG configuration set including information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set; and sending on the UL to the BS based on the CG-UL process set and an indication of whether the at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set, Among them, for the CG-UL process configured without cg-RetransmissionTimer, different CG-UL processes are configured to have different HARQ process IDs.

35. A method for wireless communication at a base station (BS), comprising: sending a configured grant (CG) configuration set configuring a configured grant uplink (CG-UL) process set to a user equipment (UE), the CG configuration set including information indicating whether at least one cg-RetransmissionTimer is associated with the CG-UL process set; and receiving on the UL from the UE based on the CG-UL process set and an indication of whether the at least one cg-RetransmissionTimer is associated with each CG-UL process in the CG-UL process set, Among them, for the CG-UL process configured without cg-RetransmissionTimer, different CG-UL processes are configured to have different HARQ process IDs.

Images