Start bit determination for PUSCH repetition with transport block size scaling

Abstract

A configuration for determining a start bit for a PUSCH repetition with TBS scaling. The apparatus determines a TBS for a PUSCH transmission based at least in part on a PUSCH resource set corresponding to a PUSCH repetition set for transmission on a repetition unit comprising a plurality of time slots. The apparatus determines a start bit position for each code block for a PUSCH transmission for a first time slot of a plurality of time slots. The apparatus determines a different start bit position for each code block for a PUSCH transmission for each time slot after the first time slot of the plurality of time slots, wherein each of the different start bit positions for each time slot after the first time slot is based on a two-stage RV cycle. The apparatus sends a PUSCH repetition, each time slot including coded data based on a corresponding start bit position.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly, to a configuration for determining a start bit for a physical uplink shared channel (PUSCH) repetition with transport block size (TBS) scaling. Background Art

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

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An exemplary telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

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

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a UE. The apparatus may be a processor and / or a modem at a UE or the UE itself. The apparatus determines a transport block size (TBS) for a PUSCH transmission based at least in part on a set of PUSCH resources corresponding to a set of PUSCH repetitions for transmission on a repetition unit comprising a plurality of time slots. The apparatus determines a starting bit position for the PUSCH transmission for a first time slot in the plurality of time slots. The apparatus determines different starting bit positions for the PUSCH transmission for each time slot after the first time slot in the plurality of time slots, wherein each starting bit position in the different starting bit positions for each time slot after the first time slot is based on a two-level redundancy version (RV) cycle. The apparatus sends the PUSCH repetition, each time slot including coded data based on a corresponding starting bit position.

[0006] To achieve the above and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are only indicative of a few of the various ways in which the principles of the various aspects can be employed, and the present description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0013] Figure 4 An example of a multi-slot PUSCH is shown.

[0014] Figure 5An example of RV mapping is shown.

[0015] Figure 6A-6B An example of a time slot mapping is shown.

[0016] Figure 7 An example of an RV cycle is shown.

[0017] Figure 8 An example of a time slot mapping is shown.

[0018] Fig. 9 It is a call flow diagram of the signaling between the UE and the base station.

[0019] Fig.10 is a flow chart of a method of wireless communication.

[0020] Fig.11 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

[0021] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. This specific embodiment includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, various structures and components are shown in block diagram form to avoid making these concepts difficult to understand.

[0022] 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 with the aid of 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0023] 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 functions described throughout the present disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as representing instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other.

[0024] Therefore, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. The storage medium may be any available medium accessible by a computer. By way of example and not limitation, such a computer-readable medium may include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), an optical disk storage device, a magnetic disk storage device, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that may be used to store computer executable code in the form of instructions or data structures accessible by a computer.

[0025] Figure 1 1 is a schematic diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

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

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

[0028] 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 various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

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

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

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

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

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

[0035] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed 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 (PSS), 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 services 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 charging information related to eMBMS.

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

[0037] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for 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 computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a medical 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, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user 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.

[0038] Reference again Figure 1In certain aspects, the UE 104 may be configured to determine the starting bit position of a time slot for a PUSCH transmission using a two-stage RV cycle. For example, the UE 104 may include a determination component 198 configured to determine the starting bit position of a time slot for a PUSCH transmission using a two-stage RV cycle. The UE 104 may determine a transport block size (TBS) for a PUSCH transmission based at least in part on a PUSCH resource set corresponding to a physical uplink shared channel (PUSCH) repetition set for transmission on a repetition unit including a plurality of time slots. The UE 104 may determine a starting bit position for the PUSCH transmission for a first time slot in the plurality of time slots. The UE 104 may determine a different starting bit position for the PUSCH transmission for each time slot after the first time slot in the plurality of time slots, wherein each starting bit position in the different starting bit positions for each time slot after the first time slot is based on a two-stage redundancy version (RV) cycle. The UE 104 may send the PUSCH repetition, each time slot including coded data based on a corresponding starting bit position.

[0039] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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

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

[0042] A resource grid may be used to represent a 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.

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

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

[0045] like Figure 2C As shown, some REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are also possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of these combs. The base station can use the SRS for channel quality estimation to enable frequency-based scheduling on the UL.

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

[0047] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements the functions of layer 3 and layer 2. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0048] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation and demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain 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 state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

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

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

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

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

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

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

[0055] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 198 related aspects.

[0056] Figure 4 An example 400 of a multi-slot PUSCH is shown. In 5G NR, repeated transmission of a PUSCH on consecutive time slots (e.g., time slot repetition, aggregation, or multi-slot PUSCH) may be supported to increase the signal-to-noise ratio (SNR) and thereby obtain transmission reliability. For example, a modulation and coding scheme (MCS) and resource allocation may be indicated in the scheduling downlink control information (DCI) and may be common on consecutive time slots. For each time slot of a multi-slot PUSCH, the transport block (TB) may be the same, but the coded bits may be different, so that the redundancy version (RV) of each time slot may be different. For example, the RV of the first time slot may be indicated in the scheduling DCI, and the RV of another time slot (n) may be determined by "n mod 4". In some embodiments, an example RV on a time slot for a new transmission of a 4-slot PDSCH may include RV0, RV2, RV3, and RV1. Another example RV on a time slot for a retransmission of a 4-slot PDSCH may include RV3, RV1, RV0, and RV2. In addition, PUSCH repetition may be applied to cover restricted scenarios.

[0057] The TB size (TBS) may be determined using a single slot PUSCH resource, such as but not limited to a multi-slot PUSCH (eg, PUSCH repetition), and may be represented as TBS+L CRC ≈N RE ·R·Q m , where R and Q m are the code rate and modulation order indicated by MCS, and N RE is the total number of data REs for PUSCH in a single slot. This may result in a very low effective code rate R for multi-slot PUSCH eff,multi-slot =R / M, where M is the number of time slots.

[0058] However, for uplink coverage-limited scenarios where the UE's transmit power may be a bottleneck, further reducing the already low effective code rate R eff May be detrimental to transmission reliability and may cost more resources and / or bandwidth. For example, for an uplink with limited transmit power, eff / 2 can reduce the power spectral density (PSD) by 3dB. Therefore, the SNR can be reduced by 3dB. Although it can usually be assumed that R effThe combined gain of / 2 is 3dB, but the channel estimation loss due to the lower SNR makes this gain less than 3dB and may not compensate for the SNR loss.

[0059] Figure 5 An example 500 of RV mapping is shown. For RV mapping, the starting bit of each RV (e.g., RV0 502, RV1 504, RV2 506, RV3 508) can be defined at a corresponding position of a low-density parity check (LDPC) code. The four RVs (e.g., 502, 504, 506, 508) can have different starting bit positions and can be defined as follows:

[0060]

[0061] Table 1

[0062] Z c is the boost size, and N cb is the circular buffer length. For smaller TBS, for base graph (BG) 1, N cb =66Z c , and for BG2, N cb =50Z c The starting bit position of all RVs can be the boost size Z c An integer multiple of .

[0063] For a TBS determined by PUSCH resources over multiple time slots (e.g., M time slots (M>1), the TBS is scaled by an integer scaling factor M), at least one way of mapping coded bits to data REs may include continuous mapping, which may include: the start bit of each code block in time slot n+1 is determined by the end bit of the previous time slot n. However, in some examples, such as respectively Fig. 6A , 6B In examples 600, 610, DCI misdetection may result in misalignment between the base station and the UE.

[0064] refer to Fig. 6A In the example 600, a misdetection of a downlink schedule (e.g., PDCCH 602) with a HARQ feedback PUCCH 604 overlapping one of the time slots may result in a misalignment (e.g., 606) based on whether there is UCI (e.g., HARQ feedback and / or CSI) multiplexed on the overlapping time slot n (which may correspond to different rate matching on time slot n and may result in different end bits). In such an example, time slot n+1 may have different start bits for each code block, which is partially due to the different end bits of time slot n.

[0065] refer to Figure 6BIn example 610, in a TDD system, a misdetection of a dynamic slot format indicator (SFI) (e.g., PDCCH 602) indicating one (or more) downlink symbols in a slot may result in a misalignment (e.g., 606) based on whether a transmission in slot n (e.g., 608) is discarded (which may correspond to different start bits for each code block in slot n+1).

[0066] Various aspects presented herein provide a configuration for an improved way to determine the start bit of a PUSCH with TBS scaling. The configuration may allow a UE to utilize a two-stage RV cycle to determine the start bit position.

[0067] Figure 7 An example of a multi-slot PUSCH 700 and an example of an RV cycle 720 are shown. The RV cycle 720 may include a two-stage RV cycle, where the starting bit position of each code block of each M-time slot-unit is used as an outer stage, and the starting bit position of each code block of each time slot within the M-time slot-unit is used as an inner stage, where a different starting bit position can be determined for the inner stage RV than for the outer stage RV. The RV cycle 702 may set the starting bit position of each RV (e.g., RV0 722, RV1 724, RV2 726, RV3 728). In some aspects, a fixed (e.g., cyclic) offset may be between two consecutive time slots within the M-time slot-unit. In some aspects, the starting bit position may not be a boost size Z. c In some aspects, the offset between consecutive time slots can be determined by the circular buffer size N. cb For example, the cyclic offset for BG1 and BG2 can be defined as follows:

[0068]

[0069] Table 2

[0070] In some aspects, the offset can be larger than that used for BG1. or for BG2 As defined in Table 3, where the standard defined scaling factor β 1 >1 and β 2 > 1. The determination of the start bit position of the outer stage RV (eg, each M-slot-unit) and the inner stage RV (eg, each slot except the first slot in the M-slot-unit) may be different.

[0071]

[0072] Table 3

[0073] In some aspects, the offset may be determined by the TBS and may be indicated by the coding rate R, for example, the offset may be Where C is the number of code blocks. In another example, the offset can be Here, α is a scaling factor defined by the standard, and 0<α<1.

[0074] Figure 8 An example 800 of a timeslot mapping is shown. In some aspects, the timeslot mapping may include a pre-fixed continuous mapping. The pre-fixed continuous mapping may be similar to the continuous mapping, but with a pre-fixed starting bit position based on the scheduled resources of each timeslot. The starting bit position of each timeslot within the M-timeslot-unit for TBS determination is pre-fixed by the number of data REs within each timeslot. The pre-fixed starting bit position may not change for a different ending bit position of a previous timeslot due to undetected downlink scheduling or misdetection of a dynamic SFI, as described above in Fig. 6A and 6B discussed in .

[0075] In some aspects, for example, for a time slot m (0≤m≤M-1) within an M-time slot-unit, a starting bit position may be determined using a cyclic offset m·G to a starting bit position of the M-time slot-unit, where G is the number of bits that may be mapped in each time slot (e.g., G=N RE Q m v, where N RE is the number of data REs per time slot, and Q m is the modulation order, and v is the number of MIMO layers).

[0076] In some aspects, for example, for a time slot m in an M-time slot unit (0≤m≤M-1), a cumulative cyclic offset may be used. To determine the starting bit position, where G i is the number of bits that can be mapped in time slot i (e.g., G i =N RE,i Q m v, where N RE,i is the number of data REs in slot i). The cumulative cyclic offset can be used for non-uniform DMRS over the slots, where different N RE Associated with each time slot. In some aspects, the accumulated cyclic offset may not result in an integer increase in size Z at the starting bit position of each time slot. c .

[0077] In some aspects, such as for a single-slot PUCCH with HARQ-ACK overlapping with a multi-slot PUSCH with TBS scaling, for the case where the HARQ-ACK includes a HARQ-ACK greater than 2 bits, the coded HARQ-ACK bits may puncture the PUSCH when mapped to REs. The 2 bits may include information bits, which may be different from the coded HARQ-ACK bits. In some aspects, such as for a single-slot PUCCH overlapping with a multi-slot PUSCH with TBS scaling, UCI multiplexing may not be applied. In such aspects, in part because PUSCH has a lower priority than PUCCH, PUSCH may be discarded in the case of overlapping slots. The UE may not expect a slot within an M-slot-unit starting with RV0 that overlaps with a single-slot PUCCH. RV0 may include information bits, and if some portions are discarded, performance may be reduced.

[0078] In some aspects, RV mapping, pre-fixed starting bit position, or continuous mapping for multi-slot PUSCH with TBS scaling may be configured via RRC signaling. In some aspects, TBS scaling for multi-slot PUSCH may be limited to the single code block (CB) case, since there may be no benefit in sizing a TB over M slots with 2 CBs relative to sizing a TB over M / 2 slots with a single CB. The UE may not expect TBS scaling to be used for TBSs above a threshold, e.g., 3824 for BG2 or 8424 for BG1, above which a TB may need to be segmented into more than one CB.

[0079] Fig. 9 900 is a call flow diagram of signaling between UE 902 and base station 904. Base station 904 may be configured to provide at least one cell. UE 902 may be configured to communicate with base station 904. For example, Figure 1 In the context of , base station 904 may correspond to base station 102 / 180, and accordingly, a cell may include a geographic coverage area 110 in which communication coverage is provided and / or a small cell 102' having a coverage area 110'. In addition, UE 902 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 904 may correspond to base station 310, and UE 902 may correspond to UE 350. Optional aspects are shown with dashed lines.

[0080] In some aspects, for example, as shown at 906, the UE 902 may receive a configuration for applying an offset bit position. The UE 902 may receive a configuration for applying an offset bit position to an RV mapping for a PUSCH transmission. The UE 902 may receive a configuration for applying an offset bit position from a base station 904. In some aspects, the configuration may be received in a radio resource control (RRC) signaling indicating whether to use an offset bit position or a continuous mapping.

[0081] As shown at 908, the UE 902 may determine a TBS for the PUSCH. The UE 902 may determine the TBS for the PUSCH based at least in part on a PUSCH resource set corresponding to a PUSCH repetition set for transmission on a repetition unit comprising a plurality of time slots. In some aspects, the UE 902 may determine the TBS based on the TB comprising a single code block. In some aspects, the UE 902 does not determine the TBS based on the plurality of time slots for the TB comprising a plurality of code blocks.

[0082] UE 902 may determine a starting bit position for each code block of a PUSCH transmission, as shown at 910. UE 902 may determine a starting bit position for a PUSCH transmission for a first slot of a plurality of slots.

[0083] As shown at 912, UE 902 may determine different starting bit positions for each code block of PUSCH transmission for each time slot after the first time slot in multiple time slots. Each starting bit position in the different starting bit positions for each time slot after the first time slot may be based on a two-stage RV cycle. In some aspects, UE 902 may apply a cyclic offset between code block start bits of consecutive time slots within multiple time slots. The cyclic offset may be the same between any two consecutive time slots within multiple time slots. In some aspects, the cyclic offset may not be an integer multiple of the boost size (Zc) of a low-density parity check (LDPC) code. In some aspects, the cyclic offset may be determined by the boost size or the cyclic buffer size of the LDPC code. In some aspects, the cyclic offset may be based on one or more of a transport block size (TBS) or a code rate. In some aspects, the cyclic offset may be based at least on the number of resource elements (REs) within each time slot. The cyclic offset may be a fixed offset based on the number of REs within each time slot.

[0084] In some aspects, the UE 902 may avoid multiplexing uplink control information (UCI), for example, as shown at 914. The UE 902 may avoid multiplexing UCI that may be carried by a physical uplink control channel (PUCCH) that overlaps with the PUSCH transmissions over the plurality of time slots.

[0085] In some aspects, the UE 902 may drop a PUSCH transmission, for example, as shown at 916. The UE 902 may drop a PUSCH transmission in a time slot that may overlap with a PUCCH. In such aspects, the UE 902 may send a PUCCH in the time slot, as shown, for example, at 918.

[0086] In some aspects, the UE 902 may puncture the PUSCH REs with the coded HARQ-ACK, for example, as shown at 920. When mapped to the PUSCH, the UE 902 may puncture the PUSCH REs with the coded HARQ-ACK. The coded HARQ-ACK may include a HARQ-ACK greater than 2 bits.

[0087] UE 902 may transmit PUSCH repetitions, as indicated at 922. UE 902 may transmit PUSCH repetitions, where each slot may include coded data based on a corresponding starting bit position.

[0088] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104; apparatus 1102; cellular baseband processor 1104, which may include memory 360 and may be the entire UE 350 or a component of UE 350, such as TX processor 368, RX processor 356 and / or controller / processor 359). One or more of the operations shown may be omitted, swapped, or occur simultaneously. Optional aspects are shown with dashed lines. The method may allow the UE to use a two-stage RV cycle to determine the starting bit position of a time slot for a PUSCH transmission.

[0089] In some aspects, for example, at 1002, the UE may receive a configuration for applying an offset bit position. For example, 1002 may be performed by a configuration component 1140 of the apparatus 1102. The UE may receive a configuration for applying an offset bit position to an RV mapping for a PUSCH transmission. The UE may receive a configuration for applying an offset bit position from a base station. In some aspects, the configuration may be received in RRC signaling indicating whether to use an offset bit position or to use a continuous mapping.

[0090] At 1004, the UE may determine a TBS for the PUSCH. For example, 1004 may be performed by a determining component 1142 of the apparatus 1102. The UE may determine the TBS for the PUSCH based at least in part on a PUSCH resource set corresponding to a PUSCH repetition set for transmission on a repetition unit comprising a plurality of time slots. In some aspects, the UE may determine the TBS based on the TB comprising a single code block. In some aspects, the UE does not determine the TBS based on the plurality of time slots for the TB comprising a plurality of code blocks.

[0091] At 1006, the UE may determine a starting bit position for each code block of a PUSCH transmission. For example, 1006 may be performed by a determining component 1142 of the apparatus 1102. The UE may determine a starting bit position for each code block of a PUSCH transmission for a first time slot of a plurality of time slots.

[0092] At 1008, the UE may determine different starting bit positions for each code block of PUSCH transmission for each time slot after the first time slot in a plurality of time slots. For example, 1008 may be performed by the determining component 1142 of the device 1102. Each starting bit position in the different starting bit positions for each time slot after the first time slot may be based on a two-stage RV cycle. In some aspects, the UE may apply a cyclic offset between the code block start bits of consecutive time slots within a plurality of time slots. The cyclic offset may be the same between any two consecutive time slots within a plurality of time slots. In some aspects, the cyclic offset may not be an integer multiple of the boost size Zc of the LDPC code. In some aspects, the cyclic offset may be determined by the boost size or the cyclic buffer size of the LDPC code. In some aspects, the cyclic offset may be based on one or more of a transport block size (TBS) or a code rate. In some aspects, the cyclic offset may be based at least on the number of resource elements (REs) within each time slot. The cyclic offset may be a fixed offset based on the number of REs within each time slot.

[0093] In some aspects, the UE may avoid multiplexing UCI, for example at 1010. For example, 1010 may be performed by an avoiding component 1144 of the apparatus 1102. The UE may avoid multiplexing UCI that may be carried by a PUCCH that overlaps with the PUSCH transmission over the plurality of time slots.

[0094] In some aspects, the UE may drop the PUSCH transmission, for example, at 1012. For example, 1012 may be performed by a dropping component 1146 of the apparatus 1102. The UE may drop the PUSCH transmission in a time slot that may overlap with the PUCCH.

[0095] In some aspects, the UE may transmit a PUCCH, for example, at 1014. For example, 1014 may be performed by a PUCCH component 1148 of the apparatus 1102. The UE may transmit a PUCCH in the time slot.

[0096] In some aspects, for example, at 1016, the UE may puncture the PUSCH REs with the coded HARQ-ACK. For example, 1016 may be performed by the puncturing component 1150 of the apparatus 1102. When mapped to the PUSCH, the UE may puncture the PUSCH REs with the coded HARQ-ACK. The coded HARQ-ACK may include a HARQ-ACK greater than 2 bits.

[0097] At 1018, the UE may transmit a PUSCH repetition. For example, 1018 may be performed by a repetition component 1152 of the apparatus 1102. The UE may transmit a PUSCH repetition, wherein each time slot may include coded data based on a corresponding starting bit position.

[0098] Fig.11 1 is a schematic diagram 1100 showing an example of a hardware implementation of an apparatus 1102. The apparatus 1102 is a UE and includes a cellular baseband processor 1104 (also referred to as a modem) coupled to a cellular RF transceiver 1122 and one or more subscriber identity modules (SIM) cards 1120, an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110, a Bluetooth module 1112, a wireless local area network (WLAN) module 1114, a global positioning system (GPS) module 1111, and a power supply 1118. The cellular baseband processor 1104 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1122. The cellular baseband processor 1104 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1104 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1104, the software causes the cellular baseband processor 1104 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1104 when executing the software. The cellular baseband processor 1104 also includes a receiving component 1130, a communication manager 1132, and a transmission component 1134. The communication manager 1132 includes one or more of the components shown. The components within the communication manager 1132 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1104. The cellular baseband processor 1104 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1102 may be a modem chip and include only the cellular baseband processor 1104, and in another configuration, the device 1102 may be the entire UE (e.g., see Figure 3 350) and includes the aforementioned additional modules of device 1102.

[0099] The communication manager 1132 includes a configuration component 1140 that is configured to: receive a configuration for applying an offset bit position, for example, as combined with Fig.10 The communication manager 1132 also includes a determining component 1142, which is configured to determine the TBS for the PUSCH, for example, as described in conjunction with Fig.10 The determining component 1142 may be configured to determine the starting bit position of the PUSCH transmission, for example, as described in conjunction with Fig.10 The determining component 1142 may be configured to determine a different starting bit position for a PUSCH transmission for each time slot after the first time slot in the plurality of time slots, for example, as described in conjunction with Fig.10 The communication manager 1132 also includes an avoidance component 1144, which is configured to avoid multiplexing UCIs, for example, as described in conjunction with Fig.10 The communication manager 1132 also includes a discard component 1146, which is configured to discard the PUSCH transmission, for example, as described in conjunction with Fig.10 The communication manager 1132 also includes a PUCCH component 1148, which is configured to send a PUCCH, for example, as described in conjunction with Fig.10 The communication manager 1132 also includes a puncturing component 1150 configured to puncture the PUSCH REs using the encoded HARQ-ACK, for example, as described in conjunction with Fig.10 1016 as described. The communication manager 1132 also includes a repetition component 1152, which is configured to send PUSCH repetitions, for example, as combined Fig.10 1018 described.

[0100] The device may include executing the aforementioned Fig.10 The additional components of each box of the algorithm in the flowchart. Fig.10 Each block in the flowchart of can be performed by a component, and the apparatus may include one or more of these components. The component 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 to be implemented by a processor, or some combination thereof.

[0101] In one configuration, the apparatus 1102 and in particular the cellular baseband processor 1104 includes: a unit for determining a TBS for a PUSCH transmission based at least in part on a PUSCH resource set corresponding to a PUSCH repetition set for transmission on a repetition unit comprising a plurality of time slots. The apparatus includes: a unit for determining a starting bit position for each code block of the PUSCH transmission for a first time slot in the plurality of time slots. The apparatus includes: a unit for determining a different starting bit position for each code block of the PUSCH transmission for each time slot after the first time slot in the plurality of time slots. Each of the different starting bit positions for each time slot after the first time slot is based on a two-stage RV cycle. The apparatus includes: a unit for sending a PUSCH repetition, each time slot including coded data based on a corresponding starting bit position. The apparatus also includes: a unit for receiving a configuration for applying an offset bit position to an RV mapping for a PUSCH transmission. The apparatus also includes: a unit for avoiding multiplexing of UCI carried by a PUCCH that overlaps with the PUSCH transmission on the plurality of time slots. The apparatus also includes: a unit for discarding PUSCH transmissions in a time slot that overlaps with the PUCCH. The apparatus also includes: a unit for sending the PUCCH in the time slot. The apparatus also includes: a unit for puncturing the PUSCH RE using the encoded HARQ-ACK when mapped to the PUSCH. The encoded HARQ-ACK includes a HARQ-ACK greater than 2 bits. The aforementioned units may be one or more of the aforementioned components of the apparatus 1102 configured to perform the functions described by the aforementioned units. As described above, the apparatus 1102 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned units may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions described by the aforementioned units.

[0102] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary solution. Based on design preferences, it is understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. In addition, some blocks can be combined or omitted. The attached method claims present the elements of each block in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0103] The following aspects are merely illustrative and may be combined with aspects of other embodiments or teachings described herein without being limited thereto.

[0104] Aspect 1 is a method for wireless communication at a UE, comprising: determining a TBS for a PUSCH transmission based at least in part on a PUSCH resource set corresponding to a PUSCH repetition set for transmission on a repetition unit including multiple time slots; determining a starting bit position for each code block of the PUSCH transmission for a first time slot in the multiple time slots; determining a different starting bit position for each code block of the PUSCH transmission for each time slot after the first time slot in the multiple time slots, wherein each of the different starting bit positions for each time slot after the first time slot is based on a two-stage RV cycle; and sending the PUSCH repetition, each time slot including encoded data based on a corresponding starting bit position.

[0105] In aspect 2, the method according to aspect 1 further includes: the UE applying a cyclic offset between code block start bits of consecutive time slots within the plurality of time slots.

[0106] In aspect 3, the method according to aspect 1 or 2 further comprises: the cyclic offset is the same between any two consecutive time slots within the plurality of time slots.

[0107] In aspect 4, the method according to any one of aspects 1-3 further includes: the cyclic offset is not an integer multiple of a lifting size (Zc) of the LDPC code.

[0108] In aspect 5, the method according to any one of aspects 1-4 further comprises: the cyclic offset is determined by a boosting size or a cyclic buffer size of the LDPC code.

[0109] In aspect 6, the method according to any one of aspects 1-5 further includes: the cyclic offset is based on one or more of TBS or code rate.

[0110] In aspect 7, the method according to any one of aspects 1-6 further comprises: the cyclic offset is based on at least the number of resource elements (REs) within each time slot.

[0111] In aspect 8, the method according to any one of aspects 1-7 further includes: the cyclic offset is a fixed offset based on the number of REs in each time slot.

[0112] In aspect 9, the method of any one of aspects 1-8 further comprises: receiving a configuration for applying an offset bit position to an RV mapping of the PUSCH transmission.

[0113] In aspect 10, the method according to any one of aspects 1-9 further comprises: the configuration is received in RRC signaling indicating whether to use the offset bit position or to use continuous mapping.

[0114] In aspect 11, the method according to any one of aspects 1-10 further includes: the UE determining the TBS based on the TB comprising a single code block.

[0115] In aspect 12, the method according to any one of aspects 1-11 further includes: the UE not determining the TBS based on the plurality of time slots used for the TB including a plurality of code blocks.

[0116] In aspect 13, the method according to any one of aspects 1-12 further comprises: avoiding multiplexing UCI carried by PUCCH overlapping with the PUSCH transmission on the plurality of time slots.

[0117] In aspect 14, the method of any one of aspects 1-13 further includes: dropping the PUSCH transmission in a time slot overlapping with the PUCCH; and sending the PUCCH in the time slot.

[0118] In aspect 15, the method according to any one of aspects 1-14 further comprises: when mapped to PUSCH, puncturing PUSCH REs with coded HARQ-ACK, wherein the coded HARQ-ACK comprises HARQ-ACK greater than 2 bits.

[0119] Aspect 16 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors so that the system or device implements a method as described in any one of Aspects 1-15.

[0120] Aspect 17 is a system or device, comprising a unit for implementing the method as described in any one of Aspects 1-15 or realizing the device as described in any one of Aspects 1-15.

[0121] Aspect 18 is a non-transitory computer-readable medium storing instructions, wherein the instructions are executable by one or more processors to cause the one or more processors to implement the method as described in any one of aspects 1-15.

[0122] The above 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the textual claims, wherein the reference to the elements in the singular form does not mean "one and only one", unless specifically stated as such, but "one or more". Terms such as "if", "when ..." and "while ..." should be interpreted as meaning "under ..." conditions rather than implying an immediate time relationship or reaction. That is, these phrases, such as "when ...", are not implied to respond to the occurrence of an operation or to an immediate operation during the occurrence of an operation, but only to imply that if the condition is met, the operation will occur, but no specific or immediate time constraints are required for the occurrence of the operation. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as preferred or superior to other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later 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 recited in the claims. The words “module”, “mechanism”, “element”, “device” etc. may not replace the word “means”. Therefore, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated by the phrase “means for . . . ”

Claims

1. A method for wireless communication at a user equipment UE, comprising: determining a transport block size TBS for a PUSCH transmission based at least in part on a set of PUSCH resources corresponding to a physical uplink shared channel (PUSCH) repetition set for transmission on a repetition unit comprising a plurality of time slots; determining a starting bit position of each code block for the PUSCH transmission of a first time slot of the plurality of time slots; Determining a different starting bit position for each code block of the PUSCH transmission for each time slot after the first time slot in the plurality of time slots, wherein each of the different starting bit positions for each time slot after the first time slot is based on a two-level redundancy version (RV) cycle; and The PUSCH repetitions are sent, with each time slot including coded data based on a corresponding starting bit position.

2. The method according to claim 1, wherein: The UE applies a cyclic offset between code block start bits of consecutive time slots within the plurality of time slots.

3. The method according to claim 2, wherein: The cyclic offset is the same between any two consecutive time slots within the plurality of time slots.

4. The method according to claim 3, wherein: The cyclic offset is not an integer multiple of the lifting size Zc of the low-density parity-check LDPC code.

5. The method according to claim 3, wherein: The cyclic offset is determined by a boost size or a cyclic buffer size of a low-density parity check LDPC code.

6. The method according to claim 3, wherein: The cyclic offset is based on one or more of the transport block size TBS or the code rate.

7. The method according to claim 2, wherein: The cyclic shift is based at least on the number of resource elements RE in each time slot.

8. The method according to claim 7, wherein: The cyclic offset is a fixed offset based on the number of REs within each slot.

9. The method according to claim 1, further comprising: A configuration for applying an offset bit position to a redundancy version (RV) mapping of the PUSCH transmission is received.

10. The method according to claim 9, wherein: The configuration is received in a radio resource control, RRC, signaling indicating whether to use the offset bit positions or to use a continuous mapping.

11. The method according to claim 1, wherein: The UE determines the TBS based on the TB including a single code block.

12. The method according to claim 11, wherein: The UE does not determine the TBS based on that the plurality of time slots for the TB include a plurality of code blocks.

13. The method according to claim 1, further comprising: Multiplexing of uplink control information UCI carried by a physical uplink control channel PUCCH overlapping with the PUSCH transmission on the plurality of time slots is avoided.

14. The method according to claim 13, further comprising: discarding the PUSCH transmission in a time slot overlapping with the PUCCH; as well as The PUCCH is sent in the time slot.

15. The method according to claim 1, further comprising: When mapped to PUSCH, PUSCH REs are punctured using coded HARQ-ACK, wherein the coded HARQ-ACK includes HARQ-ACK greater than 2 bits.

16. An apparatus for wireless communication of a user equipment UE, comprising: means for determining a transport block size TBS for PUSCH transmission based at least in part on a set of PUSCH resources corresponding to a physical uplink shared channel, PUSCH, repetition set for transmission on a repetition unit comprising a plurality of time slots; means for determining a starting bit position of each code block for the PUSCH transmission of a first time slot of the plurality of time slots; means for determining a different starting bit position for each code block of the PUSCH transmission for each time slot after the first time slot in the plurality of time slots, wherein each of the different starting bit positions for each time slot after the first time slot is based on a two-level redundancy version (RV) cycle; as well as The unit for sending the PUSCH repetition, each time slot includes coded data based on a corresponding starting bit position.

17. The device according to claim 16, wherein: The UE applies a cyclic offset between code block start bits of consecutive time slots within the plurality of time slots.

18. The device according to claim 17, wherein: The cyclic offset is the same between any two consecutive time slots within the plurality of time slots.

19. The device according to claim 18, wherein: The cyclic offset is not an integer multiple of the lifting size Zc of the low-density parity-check LDPC code.

20. The device according to claim 18, wherein The cyclic offset is determined by a boost size or a cyclic buffer size of a low-density parity check LDPC code.

21. The device according to claim 18, wherein The cyclic offset is based on one or more of the transport block size TBS or the code rate.

22. The device according to claim 17, wherein: The cyclic shift is based at least on the number of resource elements RE in each time slot.

23. The device according to claim 22, wherein: The cyclic offset is a fixed offset based on the number of REs within each slot.

24. The apparatus of claim 16, further comprising: Means for receiving a configuration for applying an offset bit position to a redundancy version (RV) mapping for the PUSCH transmission.

25. The device according to claim 24, wherein: The configuration is received in a radio resource control, RRC, signaling indicating whether to use the offset bit positions or to use a continuous mapping.

26. The device according to claim 16, wherein: The UE determines the TBS based on the TB including a single code block.

27. The device according to claim 26, wherein: The UE does not determine the TBS based on that the plurality of time slots for the TB include a plurality of code blocks.

28. The apparatus of claim 16, further comprising: Means for avoiding multiplexing uplink control information UCI carried by a physical uplink control channel PUCCH overlapping with the PUSCH transmissions on the plurality of time slots.

29. The apparatus according to claim 28, further comprising: means for discarding the PUSCH transmission in a timeslot overlapping with the PUCCH; as well as means for sending the PUCCH in the time slot.

30. The apparatus of claim 16, further comprising: Unit for puncturing PUSCH REs with coded HARQ-ACK when mapped to PUSCH, wherein the coded HARQ-ACK comprises HARQ-ACK greater than 2 bits.

31. An apparatus for wireless communication of a user equipment UE, comprising: Memory; as well as at least one processor, the at least one processor being coupled to the memory and configured to cause the UE to: determining a transport block size TBS for a PUSCH transmission based at least in part on a set of PUSCH resources corresponding to a physical uplink shared channel (PUSCH) repetition set for transmission on a repetition unit comprising a plurality of time slots; determining a starting bit position of each code block for the PUSCH transmission of a first time slot of the plurality of time slots; Determining a different starting bit position for each code block of the PUSCH transmission for each time slot after the first time slot in the plurality of time slots, wherein each of the different starting bit positions for each time slot after the first time slot is based on a two-level redundancy version (RV) cycle; and The PUSCH repetitions are sent, with each time slot including coded data based on a corresponding starting bit position.

32. The device according to claim 31, wherein The at least one processor is configured to apply a cyclic offset between code block start bits of consecutive time slots within the plurality of time slots.

33. The device according to claim 32, wherein: The cyclic offset is the same between any two consecutive time slots within the plurality of time slots.

34. The device according to claim 33, wherein: The cyclic offset is not an integer multiple of the lifting size Zc of the low-density parity-check LDPC code.

35. The device according to claim 33, wherein The at least one processor is configured to determine the cyclic offset by a boosting size or a cyclic buffer size of a low density parity check (LDPC) code.

36. The device according to claim 33, wherein The cyclic offset is based on one or more of the transport block size TBS or the code rate.

37. The device according to claim 32, wherein: The cyclic shift is based at least on the number of resource elements RE in each time slot.

38. The device according to claim 37, wherein The cyclic offset is a fixed offset based on the number of REs within each slot.

39. The device according to claim 31, wherein The at least one processor is further configured to cause the UE to: A configuration for applying an offset bit position to a redundancy version (RV) mapping of the PUSCH transmission is received.

40. The device according to claim 39, wherein The at least one processor is configured to cause the UE to receive the configuration in radio resource control (RRC) signaling indicating whether to use the offset bit position or to use continuous mapping.

41. The apparatus of claim 31, wherein: The at least one processor is configured to determine the TBS based on the TB comprising a single code block.

42. The device according to claim 41, wherein The at least one processor is configured to not determine the TBS based on the plurality of time slots for the TB comprising a plurality of code blocks.

43. The apparatus of claim 31, wherein: The at least one processor is further configured to cause the UE to: Multiplexing of uplink control information UCI carried by a physical uplink control channel PUCCH overlapping with the PUSCH transmission on the plurality of time slots is avoided.

44. The device according to claim 43, wherein The at least one processor is further configured to cause the UE to: discarding the PUSCH transmission in a time slot overlapping with the PUCCH; and The PUCCH is sent in the time slot.

45. The apparatus of claim 31, wherein: The at least one processor is further configured to: When mapped to PUSCH, PUSCH REs are punctured using coded HARQ-ACK, wherein the coded HARQ-ACK includes HARQ-ACK greater than 2 bits.

46. ​​A computer readable medium storing computer executable code, which, when executed by a processor of a user equipment (UE), causes the UE to: determining a transport block size TBS for a PUSCH transmission based at least in part on a set of PUSCH resources corresponding to a physical uplink shared channel (PUSCH) repetition set for transmission on a repetition unit comprising a plurality of time slots; determining a starting bit position of each code block for the PUSCH transmission of a first time slot of the plurality of time slots; determining a different starting bit position for each code block of the PUSCH transmission for each time slot after the first time slot in the plurality of time slots, wherein: Each of the different starting bit positions for each time slot after the first time slot is based on a two-level redundancy version (RV) cycle; and The PUSCH repetitions are sent, with each time slot including coded data based on a corresponding starting bit position.

Images