Joint activation of multiple semi-persistent schedule configurations in a single message

Abstract

The present disclosure provides systems, methods, and apparatus for jointly activating or releasing multiple semi-persistent scheduling (SPS) configurations using a single downlink control information (DCI) message. In some implementations, a user equipment (UE) receiving a DCI message can determine the number of time slots between the end of the DCI message and the beginning of one or more downlink (DL) data frames for each SPS configuration based on a first value contained in the received DCI message. The UE can also determine, for each SPS configuration, the number of time slots between the end of the one or more DL data frames and the time instance at which the UE is to transmit a hybrid automatic repeat request acknowledgment (HARQ‑ACK) based on a second value contained in the DCI message. In some instances, a single DCI message can also jointly activate or release multiple configured grant (CG) configurations.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly to joint activation and / or release of multiple configured grant configurations and / or multiple semi-persistent scheduling configurations.

[0002] Related technical description

[0003] Wireless communication systems are widely deployed to provide various 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.

[0004] 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). There is a need for further improvements in 5G NR technology.

[0005] Overview

[0006] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0007] An innovative aspect of the subject matter described in the present disclosure may be implemented as a method for wireless communication. In some implementations, the method may be performed by a user equipment (UE) and may include: receiving a single downlink control information (DCI) message identifying multiple semi-persistent scheduling (SPS) configurations to be jointly activated or released; for each of the multiple SPS configurations, determining the number of time slots between the end of the DCI message and the beginning of one or more downlink (DL) data frames based on a first value carried in the received DCI message; and for each of the multiple SPS configurations, determining the number of time slots between the end of the one or more DL data frames and the time instance at which the UE is to transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on a second value carried in the DCI message. In some instances, the DCI message may also indicate at least one of the following common to each of the multiple SPS configurations: frequency domain resource assignment (FDRA), time domain resource assignment (TDRA), or modulation and coding scheme (MCS).

[0008] The first value and the second value may be configured by a radio resource controller (RRC). In some instances, the end of the received DCI message corresponds to the end of a physical downlink control channel (PDCCH) reception opportunity, and the start of the one or more DL data frames corresponds to the start of a physical downlink shared channel (PDSCH) reception opportunity. In other instances, the end of the one or more DL data frames corresponds to the end of a PDSCH reception opportunity, and the determined time instance corresponds to the start of a physical uplink control channel (PUCCH) resource. Additionally or alternatively, the DCI message may also indicate activation or release of multiple configured grant configurations, and may include at least one of the following common to each of the multiple configured grant configurations: frequency domain resource assignment (FDRA), time domain resource assignment (TDRA), or modulation and coding scheme (MCS).

[0009] In some implementations, the method may further include: determining a time difference between the end of the PDSCH reception opportunity and the beginning of the PUCCH resource; based on the time difference being less than a value, multiplexing the HARQ-ACK corresponding to the multiple SPS configurations with one or more codebooks; and concurrently transmitting the multiplexed HARQ-ACK and codebook on the PUCCH resource. The method may also include: based on the time difference being greater than or equal to the value, transmitting the HARQ-ACK corresponding to the multiple SPS configurations on the PUCCH at the determined time instance.

[0010] In other implementations, the method may further include: determining a time difference between the end of the PDSCH reception opportunity and the start of the PUCCH resource; and suppressing the transmission of HARQ-ACK on the PUCCH resource based on the time difference being less than the value. The second value may be based on the PDSCH to HARQ feedback timer, and may be associated with the end of the PDSCH reception opportunity of the corresponding SPS configuration. In some instances, the second value may indicate different PUCCH transmission opportunities for at least two of the multiple SPS configurations. In other instances, the second value may indicate the same PUCCH transmission opportunity for each of the multiple SPS configurations. In some other instances, the second value may identify a time slot or subframe in the PUCCH resource for transmitting HARQ-ACK according to each of the multiple SPS configurations.

[0011] In some implementations, the method may also include: receiving one or more DL data frames associated with at least one SPS configuration among the multiple SPS configurations; and transmitting a HARQ-ACK for the at least one SPS configuration among the multiple SPS configurations on a physical uplink control channel (PUCCH) at a determined time instance.

[0012] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a wireless communication device. In some implementations, the wireless communication device includes: at least one modem, at least one processor communicatively coupled to the at least one modem, and at least one memory communicatively coupled to the at least one processor. The at least one memory can store instructions that, when executed by the at least one processor in conjunction with the at least one modem, cause the wireless communication device to perform operations including: receiving a single downlink control information (DCI) message identifying multiple semi-persistent scheduling (SPS) configurations to be jointly activated or released; for each of the multiple SPS configurations, determining the number of time slots between the end of the DCI message and the beginning of one or more downlink (DL) data frames based on a first value carried in the received DCI message; and for each of the multiple SPS configurations, determining the number of time slots between the end of the one or more DL data frames and the time instance at which the UE is to transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on a second value carried in the DCI message. In some instances, the DCI message may also indicate at least one of the following common to each of the multiple SPS configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), or a modulation and coding scheme (MCS).

[0013] The first value and the second value may be configured by a radio resource controller (RRC). In some instances, the end of the received DCI message corresponds to the end of a physical downlink control channel (PDCCH) reception opportunity, and the start of the one or more DL data frames corresponds to the start of a physical downlink shared channel (PDSCH) reception opportunity. In other instances, the end of the one or more DL data frames corresponds to the end of a PDSCH reception opportunity, and the determined time instance corresponds to the start of a physical uplink control channel (PUCCH) resource. Additionally or alternatively, the DCI message may also indicate activation or release of multiple configured grant configurations, and may include at least one of the following common to each of the multiple configured grant configurations: frequency domain resource assignment (FDRA), time domain resource assignment (TDRA), or modulation and coding scheme (MCS).

[0014] In some implementations, the operations may also include: determining a time difference between an end of a PDSCH reception opportunity and a start of a PUCCH resource; based on the time difference being less than a value, multiplexing the HARQ-ACK corresponding to the multiple SPS configurations with one or more codebooks; and concurrently transmitting the multiplexed HARQ-ACK and codebook on the PUCCH resource. The operations may also include: based on the time difference being greater than or equal to the value, transmitting the HARQ-ACK corresponding to the multiple SPS configurations on the PUCCH at the determined time instance.

[0015] In other implementations, the operations may also include: determining the time difference between the end of the PDSCH reception opportunity and the start of the PUCCH resource; and suppressing the transmission of HARQ-ACK on the PUCCH resource based on the time difference being less than the value. The second value may be based on the PDSCH to HARQ feedback timer and may be associated with the end of the PDSCH reception opportunity of the corresponding SPS configuration. In some instances, the second value may indicate different PUCCH transmission opportunities for at least two of the multiple SPS configurations. In other instances, the second value may indicate the same PUCCH transmission opportunity for each of the multiple SPS configurations. In some other instances, the second value may identify a time slot or subframe in the PUCCH resource for transmitting HARQ-ACK according to each of the multiple SPS configurations.

[0016] In some implementations, the operations may also include: receiving one or more DL data frames associated with at least one SPS configuration among the multiple SPS configurations; and transmitting a HARQ-ACK for the at least one SPS configuration among the multiple SPS configurations on a physical uplink control channel (PUCCH) at a determined time instance. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A diagram illustrating an example of a wireless communication system and access network is shown.

[0019] Figure 2A , 2B , 2C, and 2D show diagrams illustrating examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

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

[0021] Figure 4 A sequence diagram depicting an example message exchange between a base station and a UE in an access network is shown.

[0022] Figure 5 Shown is a timing diagram depicting an example message exchange between a base station and a UE according to some implementations.

[0023] Figure 6 A timing diagram depicting another example message exchange between a base station and a UE according to other implementations is shown.

[0024] Figure 7 A timing diagram depicting an example message exchange between a base station and a UE in an access network is shown.

[0025] Figure 8 A flow chart of an example wireless communication method is shown.

[0026] Fig. 9 A flow chart of another example wireless communication method is shown.

[0027] Fig.10 A flow chart of another example wireless communication method is shown.

[0028] Fig.11 A flow chart of another example wireless communication method is shown.

[0029] Fig.12 A conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus is shown.

[0030] Fig.13 A diagram illustrating an example of a hardware implementation for a device employing a processing system is shown.

[0031] Detailed Description

[0032] 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 configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

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

[0034] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. 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, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0035] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, these 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. As an 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.

[0036] Figure 1 A diagram illustrating an example of a wireless communication system and access network 100 is shown. 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. Small cells include femto cells, pico cells, and micro cells.

[0037] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 via a backhaul link 184. Base stations 102 may perform one or more of the following functions, among other functions: delivery of user data, radio 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), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 may communicate with each other over a backhaul link 134 (eg, an X2 interface) directly or indirectly (eg, through EPC 160 or core network 190). Backhaul link 134 may be wired or wireless.

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

[0039] 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, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0040] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. 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.

[0041] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0042] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

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

[0044] 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 be in communication 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. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and 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), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning 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 traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0045] 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. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0046] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable 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, 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 health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, 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 handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0047] Reference again Figure 1 In some implementations, the base station 102 / 180 may be configured to jointly activate (and / or jointly release) multiple semi-persistent scheduling (SPS) configurations and / or multiple uplink configured grant configurations in a single DCI message, and the UE 104 may be configured to decode the DCI message to identify the activated SPS configurations and / or the activated uplink configured grant configurations (198). The UE 104 may also be configured to determine timing information for each activated SPS configuration based at least in part on the information carried by the single DCI message (198).

[0048] Figure 2A Diagram 200 is shown illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B A diagram 230 is shown illustrating an example of DL channels within a 5G / NR subframe. Figure 2C Diagram 250 is shown illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D A diagram 280 is shown illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are 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 with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with 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 mixture of DL, UL, and flexible symbols. The UE is configured with 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). Note that the following description also applies to the 5G / NR frame structure for TDD.

[0049] Other wireless communication technologies may have different frame structures and / 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 mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) 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 is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kKz, where μ is parameter design 0 to 5. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2DAn example of slot configuration 0 with 14 symbols per slot and parameter design μ=0 is provided, with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

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

[0051] like Figure 2A As illustrated in FIG. 1 , some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for one particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0052] Figure 2B An example of various DL channels within a subframe of an explanation frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. The 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 identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth, as well as the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0053] like Figure 2CAs illustrated in , some REs carry DM-RSs for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. Although not shown, the UE may transmit a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0054] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a location as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0055] Figure 3A block diagram of a base station 310 in communication with a UE 350 in an access network is shown. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. 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 media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality 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 of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery 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 functionality 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.

[0056] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted 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.

[0057] 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 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams 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 transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0058] 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 between transport channels and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0059] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery 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 functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0060] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a 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.

[0061] 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.

[0062] 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, cipher decoding, 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.

[0063] Semi-persistent scheduling (SPS) enables radio resources to be semi-statically configured and allocated to UEs for a period longer than one subframe, which avoids the need for specific downlink assignment messages and / or uplink grant messages on the physical downlink control channel (PDCCH) for each subframe. In order to configure SPS resources, radio resource control (RRC) signaling can indicate the interval to which radio resources are periodically assigned, and PDCCH signaling can indicate specific transmission resource allocations in the time domain / frequency domain and various transmission attributes of SPS resources (such as periodicity, modulation and control scheme (MCS), time offset, transmit power, etc.). A hybrid automatic repeat request (HARQ) process can be used to confirm the reception of UL data and DL data transmitted on SPS resources. More specifically, a non-adaptive synchronous HARQ process can be used for UL data transmission, allowing the UE to retransmit data using the same resources and the same MCS used for the original or previous UL data transmission. For DL ​​transmission, an adaptive asynchronous HARQ process can be used, where the MCS is indicated on the PDCCH.

[0064] In order to support different service types (such as URLLC, eMBB, MMTC, etc.) that may have different requirements regarding reliability, latency, data rate, and communication range, NR UL defines two types of UL data transmission that may be performed without a grant from a base station, generally referred to as a configured grant (CG). For example, a type 1 CG configuration allows a UE to perform UL data transmission without a grant without any PDCCH signaling based at least in part on an RRC configuration, and a type 2 CG configuration allows a UE to perform UL data transmission without a grant based at least in part on a combination of an RRC configuration and PDCCH signaling that activates and / or releases the type 2 CG configuration.

[0065] Downlink SPS resources and type 2 uplink configured grant resources are configured by RRC and can be activated and released using a downlink control information (DCI) message transmitted on the PDCCH. For example, RRC may periodically transmit a DCI message to activate a downlink SPS configuration and / or a type 2 uplink configured grant configuration, which remain active for a duration. When the UE receives a DCI that activates a downlink SPS configuration, the UE may receive DL data from the base station on the PDSCH according to the activated downlink SPS configuration. Similarly, when the UE receives a DCI that activates an uplink configured grant configuration, the UE may transmit UL data on the PUSCH according to the activated uplink configured grant configuration.

[0066] The DCI message activating a single SPS configuration typically indicates resource assignment and timing information for the SPS configuration, and the CS-RNTI, periodicity, number of HARQ processes, PUCCH resources, and MCS for the SPS configuration are typically indicated to the UE via RRC configuration. More specifically, the DCI message typically includes a frequency domain resource assignment (FDRA), a time domain resource assignment (FDRA), and a PDSCH-to-HARQ feedback timer for a single SPS configuration. The DCI message may also include an RRC configured table containing up to 16 entries, each of which includes a SLIV value and a K0 value. The SLIV value may indicate the starting symbol and length of the PDSCH, and the K0 value may indicate the number of time slots between the end of PDCCH reception and the start of PDSCH reception (e.g., the time period between the instance at which the UE receives the last symbol of the DCI message on the PDCCH and the instance at which the UE is to start receiving DL data on the PDSCH). The PDSCH to HARQ feedback timer can be used to determine a K1 value that indicates the number of time slots between the end of the PDSCH and the start of the PUCCH (at which time the HARQ-ACK is transmitted) (e.g., the time period between the instance at which the UE receives the last symbol of DL data on the PDSCH and the instance at which the UE is about to start transmitting HARQ feedback information on the PUCCH).

[0067] In some implementations, a UE may be provided with multiple downlink SPS configurations and / or multiple type 2 uplink configurations for a given bandwidth portion (BWP) of a serving cell. For example, a given UE may be associated with up to sixteen (16) different downlink SPS configurations and up to twelve (12) different type 2 uplink CG configurations. In the current approach, different downlink SPS configurations and different type 2 uplink CG configurations are individually activated and released, which requires the base station to send a separate DCI message for each SPS configuration and type 2 uplink CG configuration to be activated. In other words, in order to activate a number N of SPS configurations, the base station needs to send the same number N of DCI messages to the UE, and in order to release a number N of SPS configurations, the base station needs to send the same number N of DCI messages to the UE. Similarly, in order to activate a number N of type 2 uplink CG configurations, the base station needs to send the same number N of DCI messages to the UE, and in order to release a number N of type 2 uplink CG configurations, the base station needs to send the same number N of DCI messages to the UE. Thus, the current approach of having separate activation and separate release for different SPS configurations and different type 2 uplink CG configurations increases network overhead and consumes significant resources at the base station and the UE, because the base station has to prepare and transmit multiple DCI messages, the network has to transmit the multiple DCI messages, and the UE has to receive and decode the multiple DCI messages.

[0068] Various aspects of the present disclosure may allow a single DCI message to jointly activate and / or jointly release multiple downlink SPS configurations and multiple type 2 uplink CG configurations. In some implementations, different SPS and / or CG configurations associated with a UE may be divided or otherwise grouped into different sets, and a bit sequence in a single DCI message may be used to indicate multiple SPS configurations and / or multiple CG configurations to be jointly activated and / or released. In some aspects, the bit sequence may include a code point indicating an index associated with a specific SPS configuration and / or CG configuration to be activated or released, and all SPS configurations and / or CG configurations that are members of a set including the specific SPS configuration and / or CG configuration may be jointly activated and / or released by a single DCI message. Additionally or alternatively, the bit sequence may include a bitmap, each individual bit in the bitmap corresponding to a specific set, and the bitmap may be used to indicate multiple sets to be jointly activated and / or released. Different configurations may be associated with different sets, and the individual configuration may be activated and / or released based at least in part on whether the bitmap indicates that all sets including the individual configuration are to be activated or released.

[0069] By using a single DCI message to jointly activate and / or jointly release multiple downlink SPS configurations and multiple uplink CG configurations, various aspects of the present disclosure can save network resources, base station resources, and UE resources compared to the current approach of using multiple DCIs to separately activate and / or release multiple downlink SPS configurations and multiple uplink CG configurations. In some implementations, the length of the bit sequence in a single DCI message can be constrained to be less than or equal to the length of the DCI field used for separate activation and / or release, for example, to avoid incurring additional overhead by ensuring that the joint activation and / or joint release of multiple SPS configurations or multiple uplink CG configurations does not increase the size of the DCI message. In some aspects, existing DCI fields (e.g., HARQ process numbers) can be used to indicate which configurations are to be activated and / or released, thereby avoiding the need to introduce new DCI fields to indicate which configurations are to be activated and / or released.

[0070] In some implementations, the CS-RNTI may be associated with multiple downlink SPS configurations and / or multiple uplink CG configurations. The CS-RNTI generally corresponds to a unique identifier of the UE and is used to manage resources associated with the downlink SPS configuration and the uplink CG configuration. In some aspects, the RRC may define the periodicity of the downlink SPS configuration, and the PDCCH addressing the CS-RNTI may activate and / or release the downlink SPS configuration. Similarly, the RRC may define the periodicity of the uplink CG configuration, and the PDCCH addressing the CS-RNTI may be used as a signal to activate or release the uplink CG configuration.

[0071] In other implementations, different configuration sets may be associated with different CS-RNTIs, and the SPS configurations and / or uplink CG configurations that are jointly activated or released may be constrained to those configurations associated with the same CS-RNTI. For example, in some aspects, a UE may be associated with multiple CS-RNTIs, and each CS-RNTI may correspond to a specific configuration set that includes one or more (multiple) configurations that may be jointly activated or released. In this way, through multiple different CS-RNTIs, the bit sequence in the DCI used to jointly activate or release uplink CG configurations, downlink SPS configurations, etc. can be reduced, thereby achieving higher reliability.

[0072] Implementations of the subject matter disclosed herein may also allow the same DCI message for jointly activating multiple downlink SPS configurations and / or multiple type 2 uplink CG configurations to indicate at least some of the transmission parameters for the activated downlink SPS configurations and / or uplink CG configurations without increasing the size or length of the DCI message. According to some aspects of the present disclosure, when a single DCI message activates multiple different SPS configurations, the K0 and K1 values ​​for the SPS configurations may be RRC configured and provided to the UE via the DCI message. In some implementations, the UE may apply the K1 value to all SPS configurations activated by the DCI message, for example, so that the time instance at which the UE is to transmit HARQ feedback information for each SPS configuration is based on the time at which the UE receives the last codeword of DL data associated with the corresponding SPS configuration. For such implementations, the UE may transmit HARQ feedback information for each activated SPS configuration at different times using different PUCCH resources, for example, as described in reference to Figure 5 discussed.

[0073] In other implementations, the UE may apply the K1 value to a selected SPS configuration among the activated SPS configurations to determine a time instance at which the UE is to transmit HARQ feedback information for the selected SPS configuration, and may transmit HARQ feedback information for another (non-selected) SPS configuration at the same determined time instance. For such implementations, the UE may transmit HARQ feedback information for each activated SPS configuration at the same time using the same PUCCH resource, for example, as described in reference Figure 6 discussed.

[0074] By providing at least some transmission parameters for a downlink SPS configuration and / or an uplink CG configuration in the same DCI message for jointly activating and / or jointly releasing a downlink SPS configuration and / or an uplink CG configuration, various aspects of the present disclosure can save network resources, base station resources, and UE resources, for example, compared to an alternative solution in which a set of transmission parameters for each of the jointly activated downlink SPS configuration and / or uplink CG configuration can be transmitted separately. In some implementations, the K0 and K1 values ​​can be carried in an existing field of the DCI message (e.g., a HARQ process number), thereby avoiding the need to introduce a new DCI field that would increase the size or length of the DCI message.

[0075] Figure 4 A sequence diagram depicting an example message exchange 400 between a base station 402 and a UE 404 in an access network is shown. The base station 402 (which may be Figure 1An implementation of the base station 102 in FIG. 4 may include defining and configuring the RRC for multiple downlink SPS configurations and multiple type 2 uplink CG configurations. Figure 1 104 in an example) can be associated with multiple downlink SPS configurations and / or with multiple Type 2 uplink CG configurations, for example, so that the UE 404 can support different services or traffic types. In some instances, different SPS configurations can be used for different service types (e.g., URLLC, eMMB, MMTC, etc.). In other instances, different SPS configurations can be used for different traffic types (e.g., VoIP data, V2X data, etc.).

[0076] As shown, the base station 402 may provide an RRC configuration that identifies multiple SPS configurations and / or multiple uplink CG configurations that may be associated with the UE 404. In some implementations, the RRC configuration may also indicate an MCS for each of the multiple SPS configurations and / or each of the multiple uplink CG configurations. Additionally or alternatively, the RRC configuration may indicate FDRA and TDRA information for each of the multiple SPS configurations and / or each of the multiple uplink CG configurations. In other implementations, the RRC configuration may define two types of SPS configurations: a type 1 SPS configuration that is not activated using PDCCH signaling, and a type 2 SPS configuration that is activated using PDCCH signaling. The type 1 SPS configuration may be similar to a type 1 uplink CG configuration, because the UE 404 does not have to use SPS resources through activation of a DCI message, and the type 2 SPS configuration may be similar to a type 2 uplink CG configuration, because the UE 404 needs to use SPS resources through activation of a DCI message.

[0077] Thereafter, the base station 402 may periodically transmit a DCI message that jointly activates multiple SPS configurations and / or multiple uplink CG configurations. In some implementations, the DCI message may include at least the K0 and K1 values ​​for the activated SPS configuration. In some other implementations, the DCI message may include the FDRA and TDRA for the activated SPS configuration. In some aspects, the DCI message may include FDRA information, TDRA information, and K0 and K1 values ​​common to all activated SPS configurations. In other implementations, the DCI message may not include FDRA or TDRA information, for example, when such information is provided to the UE 404 via an RRC configuration. Additionally or alternatively, the RRC configuration may indicate different K0 and / or K1 values ​​for each of the different SPS configurations, in which case the DCI message may not include any K0 value.

[0078] Although not shown for simplicity, UE 404 may transmit (to base station 402) a message jointly confirming all SPS configurations and / or uplink CG configurations activated and / or released by DCI message 501. For example, in the case of an activated or released SPS configuration, UE 404 may confirm the activation or release by transmitting an acknowledgement in a codebook via PUCCH resources, and in the case of an activated or released CG configuration, the UE may confirm the activation or release by transmitting an acknowledgement via a media access control (MAC) control element (MAC-CE).

[0079] UE 404 may receive the DCI message and decode the information carried in the DCI message to identify an activated SPS configuration and / or an activated UL CG configuration. In some implementations, UE 404 may use the values ​​carried in the DCI message (such as K0 and K1 values) for each of the activated SPS configurations to determine timing information for receiving DL data on the PDSCH and for transmitting HARQ feedback information (e.g., ACK and NACK) on the PUCCH.

[0080] Once the SPS configuration is activated, the UE 404 may receive DL data on the PDSCH for one or more of the activated SPS configurations during the first SPS reception. For each of the one or more SPS configurations, the UE 404 may determine whether all transmitted DL data are received and correctly decoded, and then transmit HARQ feedback information on the PUCCH to the base station 402. The HARQ feedback information may include an ACK for acknowledging partial DL data that is received and correctly decoded, and / or may include a NACK for indicating partial DL data that is not received or not correctly decoded.

[0081] Thereafter, the base station 402 may transmit additional DL data on the PDSCH for each of the SPS configurations during one or more subsequent SPS receptions, and the UE 404 may transmit HARQ feedback information on the PUCCH to the base station 402 for each of the one or more subsequent SPS receptions. Figure 4 The example is shown as including three SPS receptions, but in other implementations, the DCI message may jointly activate the multiple SPS configurations (and multiple uplink CG configurations) for any suitable number of receptions or occurrences.

[0082] Figure 5A timing diagram depicting an example message exchange 500 between a base station 402 and a UE 404 according to some implementations is shown. Prior to time t0, the base station 402 may provide an RRC configuration that identifies multiple SPS configurations and / or multiple uplink CG configurations and indicates the MCS for each of these SPS configurations and / or uplink CG configurations. In some implementations, the RRC configuration may include separate FDRA and TDRA information for each of the different SPS configurations. Additionally or alternatively, the RRC configuration may include unique K0 and K1 values ​​for each of the different SPS configurations. In some other implementations, the RRC configuration may define a type 1 SPS configuration that is not activated using PDCCH signaling, and may define a type 2 SPS configuration that is activated using PDCCH signaling.

[0083] At time t0, base station 402 transmits a DCI message 501 that jointly activates the first SPS configuration (SPS1) and the second SPS configuration (SPS2). In other implementations, DCI message 501 may jointly activate other suitable number of SPS configurations and / or uplink CG configurations. In some implementations, DCI message 501 may include at least K0 and K1 values ​​for the activated SPS configuration. In some other implementations, DCI message 501 may include FDRA and TDRA for the activated SPS configuration. In some aspects, DCI message 501 may include FDRA information, TDRA information, and K0 and K1 values ​​common to all activated SPS configurations. In other implementations, DCI message 501 may not include FDRA or TDRA information, for example, when such information is provided to UE404 via RRC configuration. Additionally or alternatively, RRC configuration may indicate different K0 and / or K1 values ​​for each of different SPS configurations, in which case DCI message 501 may not include any K0 value.

[0084] In some other implementations, for example, if the activated uplink CG configurations do not overlap in time, the DCI message 501 may indicate a cg-DMRS-Configuration that is common to multiple activated uplink CG configurations; otherwise, if the activated uplink CG configurations overlap in time or are not common to all activated uplink CG configurations, the cg-DMRS-Configuration for each of the different uplink CG configurations may be indicated by the RRC configuration.

[0085] UE 404 may receive DCI message 501 at time t1 and may decode information carried by DCI message 501 to identify the activated first and second SPS configurations (and the activated UL CG configuration, if any). UE 404 may use the indicated K0 and K1 values ​​to determine timing information for receiving DL data on the PDSCH and for transmitting HARQ information on the PUCCH for each of the first and second SPS configurations.

[0086] More specifically, for the first SPS configuration, the UE 404 may use the K0 value to determine the number of time slots between the end of the received DCI message 501 (at time t1) and the start of one or more DL data frames 511 to be received on the PDSCH (at time t4). The end of the received DCI message 501 corresponds to the end of the PDCCH reception opportunity, and the start of the one or more DL data frames 511 corresponds to the start of the PDSCH reception opportunity for the first SPS configuration. The UE 404 may use the K1 value to determine the number of time slots between the end of the one or more DL data frames 511 (at time t7) and the time instance (at time t8) at which the UE 404 is to transmit HARQ feedback information for the first SPS configuration. The end of the one or more DL data frames 511 corresponds to the end of the PDSCH reception opportunity for the first SPS configuration, and the determined time instance corresponds to the start of the PUCCH resource (the HARQ feedback information for the first SPS configuration is to be transmitted at the start of the PUCCH). In this way, the K1 value may identify a time slot or subframe in the PUCCH resources for transmitting HARQ feedback information for the first SPS configuration.

[0087] For the second SPS configuration, the UE 404 may use the K0 value to determine the number of time slots between the end of the received DCI message 501 (at time t1) and the start of one or more DL data frames 521 to be received on the PDSCH (at time t2). The end of the received DCI message 501 corresponds to the end of the PDCCH reception opportunity, and the start of the one or more DL data frames 521 corresponds to the start of the PDSCH reception opportunity for the second SPS configuration. The UE 404 may use the K1 value to determine the number of time slots between the end of the one or more DL data frames 521 (at time t3) and the time instance (at time t5) at which the UE 404 is to transmit HARQ feedback information for the second SPS configuration. The end of the one or more DL data frames 521 corresponds to the end of the PDSCH reception opportunity for the second SPS configuration, and the determined time instance corresponds to the start of the PUCCH resources (the HARQ feedback information for the second SPS configuration is to be transmitted at the start of the PUCCH resources). In this way, the K1 value may identify a time slot or subframe in the PUCCH resources for transmitting HARQ feedback information for the second SPS configuration.

[0088] At time t2, UE 404 begins receiving DL data 521 associated with the second SPS configuration on the PDSCH, and receives the last symbol of DL data 521 at time t3. UE 404 may determine whether all transmitted DL data 521 are received and correctly decoded, and may transmit corresponding HARQ feedback information 522 on the PUCCH at time t5.

[0089] At time t4, UE 404 begins receiving DL data 511 associated with the first SPS configuration on the PDSCH, and at time t7 receives the last symbol of DL data 511. UE 404 may determine whether all transmitted DL data 511 are received and correctly decoded, and may transmit corresponding HARQ feedback information 512 on the PUCCH at time t8.

[0090] At time t 10 , UE 404 (eg, during the second SPS reception) begins receiving additional DL data 523 associated with the second SPS configuration on the PDSCH, and at time t 11 Receive the last symbol of DL data 523. UE 404 can determine whether all transmitted DL data 523 are received and decoded correctly, and can 13 The corresponding HARQ feedback information 524 is transmitted on the PUCCH.

[0091] At time t 12, UE 404 (eg, during the second SPS reception) begins receiving additional DL data 513 associated with the first SPS configuration on the PDSCH, and at time t 15 Receive the last symbol of DL data 513. UE 404 can determine whether all transmitted DL data 513 are received and decoded correctly, and can 16 The corresponding HARQ feedback information 514 is transmitted on the PUCCH.

[0092] Note that because the UE 404 uses the same K1 value to determine when to transmit HARQ feedback information for each of the first and second SPS configurations, the time period between receiving the last symbol of each DL data transmission and transmitting the corresponding HARQ feedback information is the same for both the first and second SPS configurations. Figure 5 In the example of , the first SPS configuration has a first periodicity of P1, and the second SPS configuration has a second periodicity of P2, where the first periodicity P1 is shorter than the second periodicity P2. Because the first and second SPS configurations have different periodicities, the timing offset between DL data reception for the first and second SPS configurations may change (e.g., drift) for each SPS reception occurrence. In addition, because the UE 404 uses the same K1 value to determine when to transmit HARQ feedback information for each of the first and second SPS configurations on the PUCCH, the timing offset between DL data reception for the first SPS configuration and transmission of HARQ feedback information for the second SPS configuration may also change (e.g., drift) for each SPS reception occurrence.

[0093] although Figure 5 The example includes two SPS receptions, but in other implementations, the DCI message can be for any suitable number of receptions or occurrences to jointly activate the first and second SPS configurations. In addition, although the DCI message 501 is in Figure 5 5 is shown as jointly activating two SPS configurations, but in other implementations, DCI message 501 may jointly activate any suitable number of SPS configurations and / or uplink CG configurations.

[0094] Figure 6 A timing diagram depicting an example message exchange 600 between a base station 402 and a UE 404 according to other implementations is shown. Figure 6 The message exchange 600 is similar to Figure 5500, except that the UE 404 uses the K1 value indicated in the DCI message 501 to determine the time instance at which the UE 404 is to transmit HARQ feedback information for the first SPS configuration, and aligns the transmission of HARQ feedback information for the second SPS configuration (and for all other activated SPS configurations, not shown for simplicity) with the determined time instance at which the UE is to transmit HARQ feedback information for the first SPS configuration. In this way, the K1 value indicated in the DCI message 501 can identify a time slot or subframe in the PUCCH resource for concurrently transmitting HARQ feedback information for the first and second SPS configurations.

[0095] Since the transmission of HARQ feedback information for each of the first and second SPS configurations is based on the end of each PDSCH reception opportunity for the first SPS configuration, the UE 404 transmits the HARQ feedback information at times t8 and t 16 The HARQ feedback information for the first SPS configuration is transmitted, and also at time t8 and t 16 More specifically, UE 404 transmits HARQ feedback information 512 for the first SPS configuration concurrently with the transmission of HARQ feedback information 522 for the second SPS configuration at the determined time instance corresponding to time t8, and transmits HARQ feedback information 522 for the second SPS configuration at the determined time instance corresponding to time t9. 16 The UE 404 may transmit HARQ feedback information 514 for the first SPS configuration concurrently with the transmission of HARQ feedback information 524 for the second SPS configuration at a time instance of . The UE 404 may transmit HARQ feedback information 512 and 522 using the same PUCCH resources, and may transmit HARQ feedback information 514 and 524 using the same PUCCH resources.

[0096] In some implementations, the UE 404 may multiplex the ACK-NACK corresponding to the HARQ feedback information 512 and 522 into a codebook carried by the PUCCH resource configured by the first SPS, and then transmit the HARQ-ACK multiplexed codebook on the PUCCH resource at time t8. Similarly, the UE 404 may multiplex the ACK-NACK corresponding to the HARQ feedback information 514 and 524 into a codebook carried by the PUCCH resource configured by the first SPS, and then transmit the HARQ-ACK multiplexed codebook on the PUCCH resource at time t8. 16The HARQ-ACK multiplexed codebook is transmitted on the PUCCH resource. In some aspects, the UE 404 may multiplex the ACK-NACK corresponding to the HARQ feedback information into the codebook carried by the PUCCH resources of the first SPS configuration only when the PUCCH resource occurs at least N1 codewords later than the DL data corresponding to the second SPS configuration is received. For example, the UE 404 may multiplex the ACK-NACK for HARQ 512 and 522 into the codebook carried by the PUCCH resources of SPS 1 only when time t8 occurs at least N1 codewords later than time t3, and only when time t 16 Compared to time t 11 When it occurs at least N1 symbols later, the UE 404 may multiplex the ACK-NACK for the HARQ 514 and 524 into the codebook carried by the PUCCH resources of SPS1.

[0097] for Figure 6 In the example of , selecting the first SPS configuration as a reference for determining the transmission time of HARQ feedback information for all activated SPS configurations is based on the fact that the first SPS configuration has the shortest periodicity. In other implementations, the SPS configuration with the longest periodicity may be selected as a reference for determining the transmission time of HARQ feedback information for all activated SPS configurations. In some other implementations, the first or last SPS configuration in the SPS configuration group may be selected as a reference for determining the transmission time of HARQ feedback information for all activated SPS configurations.

[0098] Figure 7 A timing diagram depicting another example message exchange 700 between base station 402 and UE 404 according to some other implementations is shown. Figure 7 The message exchange 700 is similar to Figure 6 Message exchange 600, except Figure 7 The first SPS configuration has less than Figure 6 The periodicity P1 of the first SPS configuration is therefore much smaller than the periodicity P1' of the second SPS configuration P2. Figure 6 The message exchange 600, the time when UE 404 is to transmit the HARQ feedback information for the second SPS configuration is referenced to the end of the DL data reception for the first SPS configuration. Due to the relative periodicity P1' and P2 of the first and second SPS configurations, UE 404 transmits the HARQ feedback information for the second SPS configuration at time t 10 Start receiving additional DL data 513 for the first SPS configuration, and at time t 12The UE 404 starts receiving the additional DL data 523 for the second SPS configuration. However, the time when the UE 404 is to transmit the HARQ feedback information for receiving the DL data 513 and 523 occurs at time t 13 , which is received by UE 404 for the last symbol of DL data 523 configured for the second SPS (at time t 15 ). As a result, UE 404 cannot 13 HARQ feedback information for receiving the DL data 523 is transmitted (eg, because not all of the DL data 523 has been received).

[0099] According to some aspects of the present disclosure, UE 404 may determine a time difference between the end of PDSCH reception and the beginning of PUCCH resources at which HARQ feedback information is to be transmitted, and may compare the determined time difference with a value to determine whether UE 404 has sufficient time to decode DL data, and then construct HARQ ACK / NACK before the time instance at which UE is to transmit HARQ feedback information to base station 402. In some implementations, UE 404 may refrain from transmitting HARQ feedback information based on the determined time difference being less than the value. In other implementations, UE 404 may multiplex HARQ feedback information for the first and second SPS configurations with one or more codebooks, and then transmit the multiplexed HARQ feedback information and codebooks on PUCCH resources.

[0100] for Figure 7 For example, the end of PDSCH reception (which corresponds to the time when UE 404 receives the last symbol of additional DL data 523) occurs at time t 15 , and the start of the PUCCH resource (the corresponding HARQ feedback information is to be transmitted at the beginning of the PUCCH resource) occurs at time t 13 , resulting in a negative time difference. In this case, the UE 404 may refrain from transmitting HARQ feedback information for receiving the additional DL data 523.

[0101] Figure 8 800. The method 800 may be performed by a UE (e.g., Figure 1 UE104, Figure 5-7 UE 404 or Fig.12 Although the device 1202 / 1202') is executed. Figure 5 Although the method 800 is described with reference to the UE 404, the method 800 may be performed by any suitable UE.

[0102] In block 802, UE 404 receives a single DCI message identifying multiple SPS configurations to be jointly activated or released. For example, UE 404 may receive a DCI message 501 that jointly activates the first and second SPS configurations (SPS1 and SPS2). In some implementations, DCI message 501 may include at least K0 and K1 values ​​for the activated SPS configuration. In some other implementations, DCI message 501 may include FDRA and TDRA for the activated SPS configuration. In some aspects, DCI message 501 may include FDRA information, TDRA information, and K0 and K1 values ​​common to all activated SPS configurations. In other implementations, DCI message 501 may not include FDRA or TDRA information, for example, when such information is provided to UE 404 via RRC configuration. Additionally or alternatively, the RRC configuration may indicate different K0 and / or K1 values ​​for each of the different SPS configurations, in which case DCI message 501 may not include any K0 value.

[0103] In some other implementations, for example, if the activated uplink CG configurations do not overlap in time, the DCI message 501 may indicate a cg-DMRS-Configuration that is common to multiple activated uplink CG configurations; otherwise, if the activated uplink CG configurations overlap in time or are not common to all activated uplink CG configurations, the cg-DMRS-Configuration for each of the different uplink CG configurations may be indicated by the RRC configuration.

[0104] At block 804, for each SPS configuration, the UE determines the number of time slots between the end of the received DCI message and the beginning of one or more DL data frames based on a first value carried in the received DCI message. As an example, for a first SPS configuration, the UE 404 may use the K0 value to determine the number of time slots between the end of the received DCI message 501 (at time t1) and the beginning of one or more DL data frames 511 to be received on the PDSCH (at time t4). As another example, for a second SPS configuration, the UE 404 may use the K0 value to determine the number of time slots between the end of the received DCI message 501 (at time t1) and the beginning of one or more DL data frames 521 to be received on the PDSCH (at time t2).

[0105] At block 806, for each SPS configuration, the UE 404 determines, based on the second value carried in the DCI message, the number of time slots between the end of the one or more DL data frames and the time instance at which the UE 404 is to transmit the HARQ-ACK. As an example, the UE 404 may use the K1 value to determine the number of time slots between the end of the one or more DL data frames 511 (at time t7) and the time instance at which the UE 404 is to transmit the HARQ feedback information for the first SPS configuration (at time t8). As another example, the UE 404 may use the K1 value to determine the number of time slots between the end of the one or more DL data frames 521 (at time t3) and the time instance at which the UE 404 is to transmit the HARQ feedback information for the second SPS configuration (at time t5).

[0106] Fig. 9 900 is a flow chart of an example wireless communication method. The method 900 may be performed by a UE (e.g., Figure 1 UE104, Figure 5-7 UE 404 or Fig.12 Although the device 1202 / 1202') is executed. Figure 5 Although the method 900 is described with reference to the UE 404, the method 900 may be performed by any suitable UE.

[0107] In block 902, the UE may optionally receive from a radio resource controller (RRC) at least one of the following for each of a plurality of SPS configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), a modulation and coding scheme (MCS), or a periodicity. For example, before time t0, the base station 402 may provide an RRC configuration identifying a plurality of SPS configurations and / or a plurality of uplink CG configurations, indicating an MCS for each of the SPS configurations and / or uplink CG configurations, and / or including FDRA and TDRA information for each of the different SPS configurations.

[0108] In block 904, the UE receives a single DCI message identifying multiple SPS configurations to be jointly activated or released. For example, UE 404 may receive a DCI message 501 that jointly activates the first and second SPS configurations (SPS1 and SPS2). In some implementations, the DCI message 501 may include at least K0 and K1 values ​​for the activated SPS configuration. In some other implementations, the DCI message 501 may include FDRA and TDRA for the activated SPS configuration. In some aspects, the DCI message 501 may include FDRA information, TDRA information, and K0 and K1 values ​​common to all activated SPS configurations. In other implementations, the DCI message 501 may not include FDRA or TDRA information, for example, when such information is provided to UE 404 via RRC configuration. Additionally or alternatively, the RRC configuration may indicate different K0 and / or K1 values ​​for each of the different SPS configurations, in which case the DCI message 501 may not include any K0 value.

[0109] At block 906, for each SPS configuration, the UE determines the number of time slots between the end of the received DCI message and the beginning of one or more DL data frames based on a first value carried in the received DCI message. As an example, for a first SPS configuration, the UE 404 may use the K0 value to determine the number of time slots between the end of the received DCI message 501 (at time t1) and the beginning of one or more DL data frames 511 to be received on the PDSCH (at time t4). As another example, for a second SPS configuration, the UE 404 may use the K0 value to determine the number of time slots between the end of the received DCI message 501 (at time t1) and the beginning of one or more DL data frames 521 to be received on the PDSCH (at time t2).

[0110] At block 908, for each of the plurality of SPS configurations, the UE determines, based on the second value carried in the DCI message, a number of time slots between the end of the one or more DL data frames and the time instance at which the UE 404 is to transmit the HARQ-ACK. As an example, for the first SPS configuration, the UE 404 may use the K1 value to determine the number of time slots between the end of the one or more DL data frames 511 (at time t7) and the time instance at which the UE 404 is to transmit the HARQ feedback information (at time t8). As another example, for the second SPS configuration, the UE 404 may use the K1 value to determine the number of time slots between the end of the one or more DL data frames 521 (at time t3) and the time instance at which the UE 404 is to transmit the HARQ feedback information (at time t5).

[0111] At block 910, the UE receives DL data frames associated with one or more SPS configurations on corresponding DL channel resources. As an example, at time t2, the UE 404 begins receiving DL data 521 associated with the second SPS configuration on the PDSCH, and at time t4, the UE 404 begins receiving DL data 511 associated with the first SPS configuration on the PDSCH. As another example, at time t 10 , UE 404 starts receiving DL data 523 associated with the second SPS configuration on the PDSCH, and at time t 12 , UE 404 starts receiving DL data 513 associated with the first SPS configuration on the PDSCH.

[0112] At block 912, the UE transmits a HARQ-ACK to acknowledge receipt of the DL data associated with each of the one or more SPS configurations. As an example, the UE 404 may transmit the HARQ feedback information 522 on the PUCCH at time t5 to acknowledge receipt of the DL data 521, and may transmit the HARQ feedback information 512 on the PUCCH at time t8 to acknowledge receipt of the DL data 511. As another example, the UE 404 may transmit the HARQ feedback information 522 on the PUCCH at time t5 to acknowledge receipt of the DL data 521. 13 HARQ feedback information 524 is transmitted on the PUCCH to acknowledge the reception of the DL data 523 and may be received at time t 16 HARQ feedback information 514 is transmitted on the PUCCH to acknowledge receipt of the DL data 513 .

[0113] Fig.10 1 is a flow chart of an example wireless communication method 1000. The method 1000 may be performed by a UE (e.g., Figure 1 UE104, Figure 5-7 UE 404 or Fig.12 Although the device 1202 / 1202') is executed. Figure 7 404, but the method 1000 can be performed by any suitable UE. In some implementations, the method 1000 can be performed by the UE 404 in Figure 8 The method starts at 806 after determining the number of time slots between the end of the one or more DL data frames and the time instance at which the UE 404 is to transmit the HARQ-ACK.

[0114] At block 1002, the UE determines a time difference between an end of a PDSCH reception opportunity and a start of a PUCCH resource. For example, the UE 404 may determine a time difference between an end of a PDSCH reception and a start of a PUCCH resource at which HARQ feedback information is to be transmitted, and may compare the determined time difference with a value to determine whether the UE 404 has sufficient time to decode the DL data, and then construct a HARQ ACK / NACK before a time instance at which the UE is to transmit HARQ feedback information to the base station 402.

[0115] If the time difference is greater than (or equal to) a value, as determined at block 1004, then at block 1006, the UE transmits a HARQ-ACK corresponding to the multiple SPS configurations on the PUCCH at the determined time instance. Conversely, if the time difference is less than the value, as determined at block 1004, then at block 1008, the UE 404 multiplexes the HARQ-ACK corresponding to the multiple SPS configurations with one or more codebooks. Figure 7 For example, the end of PDSCH reception (which corresponds to the time when UE 404 receives the last symbol of additional DL data 523) occurs at time t 15 , and the start of the PUCCH resource (the corresponding HARQ feedback information is to be transmitted at the beginning of the PUCCH resource) occurs at time t 13 , resulting in a negative time difference. At block 1010, the UE concurrently transmits the multiplexed HARQ-ACK and codebook on the PUCCH resources.

[0116] Fig.11 1 shows a flow chart of an example wireless communication method 1100. The method 1100 may be performed by a UE (e.g., Figure 1 UE104, Figure 5-7 UE 404 or Fig.12 Although the device 1202 / 1202') is executed. Figure 7 404, but the method 1100 may be performed by any suitable UE. In some implementations, the method 1100 may be performed by the UE 404 in Figure 8 The method starts at 806 after determining the number of time slots between the end of the one or more DL data frames and the time instance at which the UE 404 is to transmit the HARQ-ACK.

[0117] At block 1102, the UE determines a time difference between an end of a PDSCH reception opportunity and a start of a PUCCH resource. For example, the UE 404 may determine a time difference between an end of a PDSCH reception and a start of a PUCCH resource at which HARQ feedback information is to be transmitted, and may compare the determined time difference with a value to determine whether the UE 404 has sufficient time to decode the DL data, and then construct a HARQ ACK / NACK before a time instance at which the UE is to transmit HARQ feedback information to the base station 402.

[0118] If the time difference is greater than (or equal to) a value, as determined at block 1104, then at block 1106, the UE transmits a HARQ-ACK corresponding to the multiple SPS configurations on the PUCCH at the determined time instance. Conversely, if the time difference is less than the value, as determined at block 1104, then at block 1108, the UE refrains from transmitting HARQ-ACK on the PUCCH resources. Figure 7 For example, the end of PDSCH reception (which corresponds to the time when UE 404 receives the last symbol of additional DL data 523) occurs at time t 15 , and the start of the PUCCH resource (the corresponding HARQ feedback information is to be transmitted at the beginning of the PUCCH resource) occurs at time t 13 , resulting in a negative time difference. In this case, the UE 404 may refrain from transmitting HARQ feedback information for receiving the additional DL data 523.

[0119] Fig.12 1 is a conceptual data flow diagram 1200 illustrating data flow between different devices / components in an example device 1202. The device 1202 can be a UE. The device includes: a receiving component 1204 that receives a single DCI message identifying multiple SPS configurations to be jointly activated or released; a DL data timing determination component 1206 that determines a number of time slots between an end of the DCI message and a start of one or more DL data frames for each SPS configuration based on a first value carried in the received DCI message; and a HARQ timing determination component 1208 that determines a number of time slots between an end of the one or more DL data frames and a time instance at which the UE is to transmit a HARQ-ACK based on a second value carried in the DCI message.

[0120] The apparatus may include executing Figure 8-Figure 11 The additional components of each box of the algorithm in the preceding flowchart. Thus, Figure 8-Figure 11Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of those components. These components may 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 for implementation by a processor, or some combination thereof.

[0121] Fig.13 1300 is a diagram illustrating an example of a hardware implementation of a device 1102' employing a processing system 1314. The processing system 1314 may be implemented with a bus architecture generally represented by a bus 1324. Depending on the specific application of the processing system 1314 and the overall design constraints, the bus 1324 may include any number of interconnecting buses and bridges. The bus 1324 links various circuits together, including one or more processors and / or hardware components (represented by the processor 1304, components 1204, 1206, and 1208, and computer readable medium / memory 1306). The bus 1324 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0122] The processing system 1314 may be coupled to the transceiver 1310. The transceiver 1310 is coupled to one or more antennas 1320. The transceiver 1310 provides a means for communicating with various other devices over a transmission medium. The transceiver 1310 receives signals from the one or more antennas 1320, extracts information from the received signals, and provides the extracted information to the processing system 1314 (specifically, the receiving component 1204). In addition, the transceiver 1310 receives information from the processing system 1314 (specifically, the transmitting component 1210) and generates signals to be applied to the one or more antennas 1320 based on the received information. The processing system 1314 includes a processor 1304 coupled to a computer-readable medium / memory 1306. The processor 1304 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described above for any particular device. The computer-readable medium / memory 1306 may also be used to store data manipulated by the processor 1304 when executing software. The processing system 1314 further includes at least one of the components 1204, 1206, and 1208. These components may be software components running in the processor 1304, software components resident / stored in the computer-readable medium / memory 1306, one or more hardware components coupled to the processor 1304, or some combination thereof. The processing system 1314 may be a component of the UE 350 and may include the memory 360 and / or at least one of the following: the TX processor 368, the RX processor 356, and the controller / processor 359.

[0123] In one configuration, a device 1202 / 1202' for wireless communication includes: a device for receiving a single downlink control information (DCI) message identifying multiple semi-persistent scheduling (SPS) configurations to be jointly activated or released; a device for determining the number of time slots between the end of the DCI message and the beginning of one or more downlink (DL) data frames for each SPS configuration based on a first value carried in the received DCI message; and a device for determining the number of time slots between the end of the one or more DL data frames and the time instance at which the UE is to transmit a HARQ-ACK for each SPS configuration based on a second value carried in the DCI message. The aforementioned means may be one or more of the aforementioned components of the device 1202 and / or the processing system 1314 of the device 1202' configured to perform the functions recited by the aforementioned means. As described above, the processing system 1314 may include a TX processor 368, an RX processor 356, and a controller / processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0124] As described herein, aspects of the present disclosure may allow a single DCI message to jointly activate and / or jointly release multiple downlink SPS configurations and multiple type 2 uplink CG configurations. In some implementations, different SPS and / or CG configurations associated with a UE may be divided or otherwise grouped into different sets, and a bit sequence in a single DCI message may be used to indicate multiple SPS configurations and / or multiple CG configurations to be jointly activated and / or released. Additionally or alternatively, the bit sequence may include a bitmap, each individual bit in the bitmap corresponding to a specific set, and the bitmap may be used to indicate multiple sets to be jointly activated and / or released. By using a single DCI message to jointly activate and / or jointly release multiple downlink SPS configurations and multiple uplink CG configurations, various aspects of the present disclosure can save network resources, base station resources, and UE resources compared to the current approach of using multiple DCIs to respectively activate and / or release multiple downlink SPS configurations and multiple uplink CG configurations.

[0125] Implementations of the subject matter disclosed herein may also allow the same DCI message for jointly activating multiple downlink SPS configurations and / or multiple type 2 uplink CG configurations to indicate at least some of the transmission parameters for each of the activated downlink SPS configurations and / or uplink CG configurations without increasing the size or length of the DCI message. According to some aspects of the present disclosure, when a single DCI message activates multiple different SPS configurations, the K0 and K1 values ​​for the SPS configurations may be RRC configured and provided to the UE via the DCI message.

[0126] In some implementations, the UE may apply the K1 value to all SPS configurations activated by the DCI message, e.g., such that the instance of the time at which the UE is to transmit HARQ feedback information for each SPS configuration is based on the time at which the UE receives the last symbol of DL data associated with the corresponding SPS configuration. For such implementations, the UE may transmit HARQ feedback information for each activated SPS configuration at different times using different PUCCH resources, e.g., as described with reference to Figure 5 In other implementations, the UE may apply the K1 value to a selected SPS configuration among the activated SPS configurations to determine a time instance at which the UE is to transmit HARQ feedback information for the selected SPS configuration, and may transmit HARQ feedback information for another (non-selected) SPS configuration at the same determined time instance. For such implementations, the UE may transmit HARQ feedback information for each activated SPS configuration at the same time using the same PUCCH resource, for example, as described with reference to Figure 6 discussed.

[0127] By providing at least some transmission parameters for downlink SPS configurations and / or uplink CG configurations in the same DCI message for joint activation and / or joint release of downlink SPS configurations and / or uplink CG configurations, various aspects of the present disclosure can save network resources, base station resources, and UE resources, for example, compared to an alternative solution in which a set of transmission parameters can be transmitted separately for each of the jointly activated downlink SPS configurations and / or uplink CG configurations. In some implementations, the K0 and K1 values ​​can be carried in existing fields of the DCI message (e.g., HARQ process number), thereby avoiding the need to introduce new DCI fields that would increase the size or length of the DCI message.

[0128] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0129] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. The wording "exemplary" is used herein to mean "used as an example, instance or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / 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 multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, 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 this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recorded in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated using the phrase "means for..."

Claims

1. A wireless communication method performed by a user equipment (UE), comprising: receiving a single downlink control information (DCI) message identifying a plurality of semi-persistent scheduling (SPS) configurations to be jointly activated or released; For each SPS configuration of the plurality of SPS configurations, determining a number of time slots between an end of the DCI message and a start of one or more downlink (DL) data frames based on a first value carried in the received DCI message; as well as For each of the plurality of SPS configurations, a number of time slots between an end of the one or more DL data frames and a time instance at which the UE is to transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK) is determined based on a second value carried in the DCI message.

2. The method of claim 1, wherein the first value and the second value are configured by a radio resource controller (RRC).

3. The method of claim 1, wherein the end of the received DCI message corresponds to the end of a physical downlink control channel (PDCCH) reception opportunity, and the start of the one or more DL data frames corresponds to the start of a physical downlink shared channel (PDSCH) reception opportunity.

4. The method of claim 3, wherein an end of the one or more DL data frames corresponds to an end of the PDSCH reception opportunity, and the determined time instance corresponds to a start of a physical uplink control channel (PUCCH) resource.

5. The method of claim 4, further comprising: Determining a time difference between an end of the PDSCH reception opportunity and a start of the PUCCH resource; Based on the time difference being less than a value, multiplexing the HARQ-ACK corresponding to the multiple SPS configurations with one or more codebooks; as well as The multiplexed HARQ-ACK and codebook are transmitted concurrently on the PUCCH resources.

6. The method of claim 5, further comprising: Based on the time difference being greater than or equal to the value, the HARQ-ACK corresponding to the multiple SPS configurations is transmitted on the PUCCH at the determined time instance.

7. The method of claim 4, further comprising: Determining a time difference between an end of the PDSCH reception opportunity and a start of the PUCCH resource; as well as Transmitting the HARQ-ACK on the PUCCH resource is suppressed based on the time difference being less than a value.

8. The method of claim 1, wherein the second value is based on a physical downlink shared channel (PDSCH) to HARQ feedback timer.

9. The method of claim 1, wherein the second value indicates different physical uplink control channel (PUCCH) transmission opportunities for at least two SPS configurations of the plurality of SPS configurations.

10. The method of claim 1, wherein the second value identifies a time slot or a subframe in a physical uplink control channel (PUCCH) resource for transmitting a HARQ-ACK according to each of the multiple SPS configurations.

11. The method of claim 1, wherein the second value indicates a same physical uplink control channel (PUCCH) transmission opportunity for each of the plurality of SPS configurations.

12. The method of claim 1, wherein the DCI message further indicates at least one of the following common to each of the plurality of SPS configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), or a modulation and coding scheme (MCS).

13. The method of claim 1, further comprising: At least one of the following is received from a radio resource controller (RRC) for each of the plurality of SPS configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), a modulation and coding scheme (MCS), or a periodicity.

14. The method of claim 1, further comprising: receiving the one or more DL data frames associated with at least one SPS configuration of the plurality of SPS configurations; as well as The HARQ-ACK for the at least one SPS configuration of the plurality of SPS configurations is transmitted on a physical uplink control channel (PUCCH) at the determined time instance.

15. The method of claim 1, wherein the DCI message further indicates activation or release of a plurality of configured grant configurations, and includes at least one of the following common to each of the plurality of configured grant configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), or a modulation and coding scheme (MCS).

16. A wireless communication device at a user equipment (UE), comprising: at least one modem; at least one processor communicatively coupled to the at least one modem; as well as at least one memory communicatively coupled to the at least one processor and storing instructions that, when executed by the at least one processor in conjunction with the at least one modem, cause the wireless communication device to perform operations comprising: receiving a single downlink control information (DCI) message identifying a plurality of semi-persistent scheduling (SPS) configurations to be jointly activated or released; For each SPS configuration of the plurality of SPS configurations, determining a number of time slots between an end of the DCI message and a start of one or more downlink (DL) data frames based on a first value carried in the received DCI message; as well as For each of the plurality of SPS configurations, a number of time slots between an end of the one or more DL data frames and a time instance at which the UE is to transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK) is determined based on a second value carried in the DCI message.

17. The wireless communication device of claim 16, wherein the first value and the second value are configured by a radio resource controller (RRC).

18. The wireless communication device of claim 16, wherein the end of the received DCI message corresponds to the end of a physical downlink control channel (PDCCH) reception opportunity, and the beginning of the one or more DL data frames corresponds to the beginning of a physical downlink shared channel (PDSCH) reception opportunity.

19. The wireless communication device of claim 18, wherein an end of the one or more DL data frames corresponds to an end of the PDSCH reception opportunity, and the determined time instance corresponds to a start of a physical uplink control channel (PUCCH) resource.

20. The wireless communication device of claim 19, wherein execution of the instructions causes the wireless communication device to perform operations further comprising: Determining a time difference between an end of the PDSCH reception opportunity and a start of the PUCCH resource; Based on the time difference being less than a value, multiplexing the HARQ-ACK corresponding to the multiple SPS configurations with one or more codebooks; and The multiplexed HARQ-ACK and codebook are transmitted concurrently on the PUCCH resources.

21. The wireless communication device of claim 20, wherein execution of the instructions causes the wireless communication device to perform operations further comprising: Based on the time difference being greater than or equal to the value, the HARQ-ACK corresponding to the multiple SPS configurations is transmitted on the PUCCH at the determined time instance.

22. The wireless communication device of claim 19, wherein execution of the instructions causes the wireless communication device to perform operations further comprising: determining a time difference between an end of the PDSCH reception opportunity and a start of the PUCCH resource; and Transmitting the HARQ-ACK on the PUCCH resource is suppressed based on the time difference being less than a value.

23. The wireless communication device of claim 16, wherein the second value is based on a physical downlink shared channel (PDSCH) to HARQ feedback timer.

24. The wireless communication device of claim 16, wherein the second value indicates different physical uplink control channel (PUCCH) transmission opportunities for at least two SPS configurations of the plurality of SPS configurations.

25. The wireless communication device of claim 16, wherein the second value identifies a time slot or subframe in a physical uplink control channel (PUCCH) resource for transmitting a HARQ-ACK according to each of the multiple SPS configurations.

26. The wireless communication device of claim 16, wherein the second value indicates a same physical uplink control channel (PUCCH) transmission opportunity for each of the plurality of SPS configurations.

27. The wireless communication device of claim 16, wherein the DCI message further indicates at least one of the following common to each of the plurality of SPS configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), or a modulation and coding scheme (MCS).

28. The wireless communication device of claim 16, wherein execution of the instructions causes the wireless communication device to perform operations further comprising: At least one of the following is received from a radio resource controller (RRC) for each of the plurality of SPS configurations: a frequency domain resource assignment (FDRA), a time domain resource assignment (TDRA), a modulation and coding scheme (MCS), or a periodicity.

29. The wireless communication device of claim 16, wherein execution of the instructions causes the wireless communication device to perform operations further comprising: receiving the one or more DL data frames associated with at least one SPS configuration of the plurality of SPS configurations; and The HARQ-ACK for the at least one SPS configuration of the plurality of SPS configurations is transmitted on a physical uplink control channel (PUCCH) at the determined time instance.

30. A wireless communication device as described in claim 16, wherein the DCI message further indicates activation or release of multiple configured grant configurations, and includes at least one of the following common to each of the multiple configured grant configurations: frequency domain resource assignment (FDRA), time domain resource assignment (TDRA), or modulation and coding scheme (MCS).

Images