Method and apparatus for facilitating layer 1 cross-carrier repetition

Abstract

Apparatus, methods, and computer-readable media for facilitating layer 1 cross-carrier repetition are disclosed herein. An example method for wireless communication includes determining a repetition configuration for a semi-persistent schedule (SPS) or a configured grant (CG) associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The example method also includes receiving the data transmission and at least one repetition of the data transmission. The example method also includes combining the data transmission and at least one repetition of the data transmission to decode the data transmission.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 62 / 868,743, filed on June 28, 2019, entitled “Methods and Apparatus to Facilitate Layer 1 Cross-Carrier Repetition,” and U.S. Patent Application No. 16 / 878,382, filed on May 19, 2020, entitled “METHODS AND APPARATUS TO FACILITATE LAYER 1 CROSS-CARRIER REPITITION,” which are expressly incorporated herein by reference in their entireties. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications utilizing retransmissions of data transmissions. Background Art

[0004] 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 that are capable of supporting communications 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at municipal, national, regional and even global levels. An example of a telecommunication standard is 5G New Radio (NR). 5GNR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC) and ultra-reliable low latency communication (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

[0006] A brief 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 key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that is presented later.

[0007] In some examples, a data transmission received by a first device from a second device may not be received correctly. For example, due to noise at, for example, the first device or the second device, the first device may not be able to correctly decode the received data transmission. In some such examples, when the first device cannot correctly decode the received data transmission, the first device may request the second device to retransmit the data transmission. In order to increase the possibility of correctly decoding the data transmission, the first device may combine the data transmission and the repetition of the data transmission. That is, combining the data transmission and the repetition (or retransmission) of the data transmission can provide the first device with sufficient information to correctly decode the data transmission. The exemplary techniques disclosed herein facilitate cross-carrier repetition (or retransmission).

[0008] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided. An example apparatus for wireless communication determines a repetition configuration for a semi-persistent schedule (SPS) or a configured grant (CG) associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The example apparatus also receives the data transmission and at least one repetition of the data transmission. In addition, the example apparatus combines the data transmission and at least one repetition of the data transmission to decode the data transmission.

[0009] In another aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided. An example apparatus for wireless communication determines a repetition configuration for an SPS or CG associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The example apparatus also sends the data transmission on the first entity. In addition, the example apparatus sends at least one repetition of the data transmission on the second entity.

[0010] To achieve the foregoing 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 merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0014] Figure 4 An example communication flow between a base station and a UE during a current period according to the teachings disclosed herein is illustrated.

[0015] Figure 5 Illustrated is example wireless communication between a base station and a UE according to the teachings disclosed herein.

[0016] Figure 6 An example timing diagram for an apparatus receiving downlink transmissions and sending uplink transmissions according to the teachings disclosed herein is illustrated.

[0017] Figure 7 An example timing diagram is illustrated for an apparatus receiving a downlink transmission and sending a common ACK / NACK signal for each received repetition in accordance with the teachings disclosed herein.

[0018] Figure 8 An example timing diagram is illustrated for an apparatus to receive downlink transmissions based on rules and send common ACK / NACK signals in accordance with the teachings disclosed herein.

[0019] Fig. 9 Illustrated is example wireless communication between a base station and a UE according to the teachings disclosed herein.

[0020] Fig.10 An example timing diagram for a device receiving downlink transmissions and sending uplink transmissions according to the teachings disclosed herein is illustrated.

[0021] Fig.11 is a flow chart of a method of wireless communication according to the teachings disclosed herein.

[0022] Fig.12 is a diagram illustrating an example of a hardware implementation for an example apparatus according to the teachings disclosed herein.

[0023] Fig.13 is a flow chart of a method of wireless communication according to the teachings disclosed herein.

[0024] Fig.14 is a diagram illustrating an example of a hardware implementation for an example apparatus according to the teachings disclosed herein. DETAILED DESCRIPTION

[0025] 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. The specific embodiments include specific details in order to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, in order to avoid obscuring these concepts, well-known structures and components are shown in block diagram form.

[0026] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (hereinafter collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0027] As an example, an element, any part of an element, or any combination of multiple 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 indicating instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads in execution, procedures, functions, etc., regardless of whether they are referred to as software, firmware, middleware, microcode, hardware description languages, or other.

[0028] Therefore, in one or more exemplary embodiments, the functions described can be implemented with hardware, software, firmware or any combination thereof. If implemented with software, the functions can be stored on a computer-readable medium or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media can 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 aforementioned types, or any other medium that can be used to store computer executable code that can be accessed by a computer in the form of instructions or data structures.

[0029] As used herein, the term computer-readable medium is expressly defined to include any type of computer-readable storage device and / or storage disk, and does not include propagating signals and does not include transmission media. As used herein, "computer-readable medium," "machine-readable medium," "computer-readable memory," and "machine-readable memory" are used interchangeably.

[0030] Figure 1 1 is a diagram illustrating 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.

[0031] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: transmission of user data, 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, allocation for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber 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.

[0032] 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 both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also called a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also called a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in carrier aggregation 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 with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for 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).

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

[0034] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates 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) to determine whether a channel is available before communicating.

[0035] The small cell 102' may operate in a licensed spectrum and / or an 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 improve coverage of the access network and / or increase capacity of the access network.

[0036] Base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Certain base stations, such as gNB 180, may operate in the traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates at mmW frequencies or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of the RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz with wavelengths between 1 mm and 10 mm. Radio waves in the frequency band may be referred to as millimeter waves. Near mmW may extend down to frequencies of 3 GHz with wavelengths of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. The frequency range bands include frequency range 1 (FR1), which includes frequency bands below 7.225 GHz, and frequency range 2 (FR2), which includes frequency bands above 24.250 GHz. Communications using mmW / near mmW radio frequency (RF) bands (e.g., 3 GHz-300 GHz) have extremely high path loss and short range. The base station / UE may operate in one or more frequency bands. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

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

[0038] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides 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 services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0039] 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 (UDP) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) stream (PSS) service, and / or other IP services.

[0040] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. 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 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.

[0041] Refer again Figure 1 In certain aspects, UE 104 may be configured to manage one or more aspects of wireless communication via cross-carrier retransmissions. As an example, in Figure 1In the example, the UE 104 can be configured to include a UE repetition component 198, which is configured to determine a repetition configuration for a semi-persistent scheduling or a configuration permission associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The example UE repetition component 198 can be configured to determine a repetition configuration for an SPS or a CG associated with a data transmission on the first entity and at least one repetition of the data transmission on the second entity. The example UE repetition component 198 can also be configured to receive the data transmission and the at least one repetition of the data transmission. In addition, the example UE repetition component 198 can be configured to combine the data transmission and the at least one repetition of the data transmission to decode the data transmission.

[0042] Still refer to Figure 1 In some aspects, the base station 102 / 180 may be configured to manage one or more aspects of wireless communication via cross-carrier retransmissions. As an example, in Figure 1 In the example, the base station 102 / 180 can be configured to include a base station repetition component 199, which is configured to determine a repetition configuration for an SPS or CG associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The example base station repetition component 199 can also be configured to send the data transmission on the first entity. In addition, the example base station repetition component 199 can be configured to send at least one repetition of the data transmission on the second entity.

[0043] Although the following description may provide examples based on SPS / CG transmissions, it will be appreciated that the concepts described herein may be applicable to other transmission types in which data transmissions may be retransmitted.

[0044] Furthermore, 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 / or other wireless technologies where transmissions may be retransmitted using cross-component carriers.

[0045] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G NR frame structure may be of frequency division duplex type (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL; or the 5G / NR frame structure may be of time division duplex type (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. Figure 2A , 2C In the example provided, the 5G / NR frame structure is assumed to be of TDD type, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, X is flexible for use between DL / UL, and subframe 3 is configured with slot format 34 (primarily 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 mix of DL symbols, UL symbols, and flexible symbols. The UE is configured with a slot format by a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). Note that the following description also applies to a TDD type 5G NR frame structure.

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

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

[0048] like Figure 2A As shown 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 (although indicated as Rs for one specific configuration). x , where 100x is the port number, but other DM-RS configurations are also 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).

[0049] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The UE 104 uses the PSS to determine subframe timing / symbol timing and physical layer identity. The 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 identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the position 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 an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0050] like Figure 2C As shown in , some REs carry DM-RS for channel estimation at the base station (although indicated as R for a specific configuration, 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 in the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0051] Figure 2DAn example of various UL channels within a subframe of a frame is illustrated. The PUCCH may be located 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) ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0052] 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 transmission 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 processing, and logical channel prioritization.

[0053] 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 / 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., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as 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.

[0054] At the UE 350, each receiver 354RX receives a signal through its respective 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.

[0055] 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 an ACK and / or NACK protocol to support HARQ operations.

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

[0057] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback transmitted 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.

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

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

[0060] 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 Aspects related to UE repeating component 198.

[0061] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Aspects related to base station repeating component 199.

[0062] In some examples, a data transmission received by a first device from a second device may not be correctly received. For example, due to noise at, for example, the first device or the second device, the first device may not be able to correctly decode the received data transmission. In some such examples, when the first device is unable to correctly decode the received data transmission, the first device may request the second device to retransmit the data transmission. In order to increase the likelihood of correctly decoding the data transmission, the first device may combine the data transmission and the repetition of the data transmission. That is, combining the data transmission and the repetition (or retransmission) of the data transmission can provide the first device with sufficient information to correctly decode the data transmission.

[0063] In some examples, transmission and retransmission of the data transmission are performed within a cycle. In some such examples, if the first device cannot correctly decode the data transmission within the cycle, the data transmission is skipped and the next data transmission (if any) is processed.

[0064] However, if the duration of the period is relatively short (e.g., 0.5 ms), retransmissions of the data transmission may not be performed and / or the likelihood of decoding the data transmission based on the received data transmission and retransmissions may be reduced. In some examples, the first device and the second device may utilize an SPS or CG associated with the data transmission to improve the reliability (or likelihood) of decoding the data transmission.

[0065] In some examples, reliability with respect to decoding data transmissions may be further improved by utilizing higher layer PDCP replication on different component carriers (CCs) (sometimes referred to as "cells").

[0066] Figure 4 An example communication flow 400 between a base station 402 and a UE 404 during a current period 410 is illustrated. One or more aspects of the base station 402 may be provided by Figure 1 Base station 102, Figure 1 Base station 180 and / or Figure 3 One or more aspects of UE 404 may be implemented by Figure 1 UE 104 and / or Figure 3 UE 350 is implemented. Figure 4 In the illustrated example of , base station 402 sends a data transmission 420 (eg, a PDSCH) to UE 404 , and UE 404 sends a control transmission 430 (eg, a PUCCH) to base station 402 .

[0067] For example, base station 402 sends a data transmission 420 to UE 404 on a first component carrier (CC1) 440. UE 404 may, based on receiving the data transmission 420, send a control transmission 430 to base station 402 on first CC 440. Base station 402 may then send a copy (e.g., a data retransmission 422 or repetition) of data transmission 420 on a second component carrier (CC2) 442. UE 404 may then send a copy (e.g., a control retransmission 432 or repetition) of control transmission 430 on second CC 442. Figure 4 As shown, data transmissions 420, 422 can be associated with SPS and merged accordingly. In addition, control transmissions 430, 432 can be associated with CG and merged accordingly.

[0068] The examples disclosed herein utilize layer 1 (L1) cross-carrier repetition to further improve reliability with respect to decoding transmissions. For example, the examples disclosed herein enable repetitions of SPS transmissions or CG transmissions to be sent on different CCs in FR2 (e.g., a frequency range of 24.25 GHz to 52.6 GHz).

[0069] Example techniques disclosed herein facilitate signaling a repetition configuration from a first device (e.g., a base station) to a second device (e.g., a UE). A repetition configuration (sometimes referred to as an SPS / CG configuration) may indicate a CC for sending or receiving repetitions. It is understood that each cell may have multiple SPS / CG configurations. A device sending repetitions may send repetitions via corresponding CCs. A device receiving repetitions may combine transmissions received on corresponding CCs to facilitate decoding of the transmissions.

[0070] In some examples, the device receiving the repetition may be a UE. In some such examples, the UE may generate an ACK / NACK signal for the received transmission and send the ACK / NACK signal to the base station. The examples disclosed herein help the UE to generate a common ACK / NACK signal based on whether the UE can correctly decode the transmission (e.g., based on an erroneously received transmission and / or a repetition of the transmission). In some examples, the UE may send a common ACK / NACK signal for each received transmission or repetition. In some examples, the UE may send a common ACK / NACK signal for one of the repetitions.

[0071] Figure 5 An example wireless communication 500 between a base station 502 and a UE 504 as described herein is illustrated. Figure 5 In the illustrated wireless communication 500, a base station 502 sends a data transmission and a repetition of the data transmission to a UE 504. One or more aspects of the base station 502 may be implemented by Figure 1 Base station 102, Figure 1 Base station 180, Figure 3 Base station 310 and / or Figure 4 One or more aspects of UE504 may be implemented by Figure 1 UE 104, Figure 3 UE 350 and / or Figure 4 UE 404 is implemented.

[0072] Although wireless communication 500 includes one base station 502 communicating with one UE 504, in additional or alternative examples, base station 502 can communicate with any suitable number of UEs 504 and / or base stations 502, and / or UE 504 can communicate with any suitable number of base stations 502 and / or UE 504.

[0073] In the illustrated example, at 508, base station 502 may determine a repetition configuration 510. Repetition configuration 510 may be associated with an SPS configuration or a CG configuration. Repetition configuration 510 may be associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity.

[0074] The base station 502 may send a repetition configuration 510 that is received by the UE 504. The repetition configuration 510 may be associated with an SPS configuration or a CG configuration associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity.

[0075] At 512, the UE 504 may determine those entities on which any repetitions may be received based on the repetition configuration 510. For example, the UE 504 may determine that a first repetition occurrence may occur on a first entity and a second repetition occurrence may occur on a second entity based on the repetition configuration 510. In some examples, the first entity and the second entity may include frequency resources. In some examples, the first entity and the second entity may include a component carrier (CC) (or cell).

[0076] exist Figure 5 In the illustrated example of , base station 502 transmits data transmission 514 that is received by UE 504. For example, base station 502 may transmit data transmission 514 via PDSCH. Then, base station 502 may transmit repetition 516 of the data transmission. For example, base station 502 may transmit repetition 516 via an entity indicated via repetition configuration 510. Figure 5 The example of FIG. 5 illustrates an example repetition 516, but it is understood that in other examples, repetition 516 may be implemented by one or more repetitions of data transmission 514. Aspects of data transmission 514 may be implemented by Figure 4 The data transmission 420 is implemented. The aspect of repeating 516 can be achieved by Figure 4 The data retransmission 422 is implemented.

[0077] At 518, UE 504 may combine and decode received data transmission 514 and received repetition 516 of the data transmission. In some examples, UE 504 may combine one or more repetitions associated with and received in the same period.

[0078] At 520, UE 504 can generate a common ACK / NACK based on whether UE 504 was able to correctly decode the data transmission (e.g., based on data transmission 514 and / or repetition 516). UE 504 can then send a common ACK / NACK signal 522 that is received by base station 502. For example, UE 504 can send common ACK / NACK signal 522 via an uplink control channel associated with data transmission 514. In some examples, UE 504 can also retransmit the common ACK / NACK signal (e.g., a common ACK / NACK signal retransmission) 524. For example, UE 504 can retransmit common ACK / NACK signal retransmission 524 via an uplink control channel associated with each repetition 516.

[0079] At 526, base station 502 may determine whether transmission of the data transmission was successful based on received common ACK / NACK signals 522, 524. In some examples, base station 502 may determine that transmission of the data transmission was successful if at least one common ACK / NACK signal is ACK (e.g., common ACK / NACK signal 522 is ACK and / or at least one common ACK / NACK signal retransmission 425 is ACK).

[0080] In some examples, base station 502 may send repetition configuration 510 via RRC signaling, via DCI signaling, and / or via a MAC control element (MAC-CE). In some examples, repetition configuration 510 may include an identifier associated with the repetition configuration. In some examples, repetition configuration 510 may include a period identifier.

[0081] In some examples, repetition configuration 510 may correspond to an entity, such as a frequency resource or a component carrier (CC). For example, repetition configuration 510 may indicate on which CC repetitions may be received and / or on which CC repetitions may be sent.

[0082] In some examples, repetition configuration 510 may include a set of repetition configurations. In some examples, a set of repetition configurations may be associated with the same period (or period) having a common start boundary. In some examples, the common start boundary may be determined based on a common frame boundary (e.g., SFN=0). In some examples, the common start boundary may be configured via DCI signaling.

[0083] In some examples, the UE 504 may determine at 512 that a repetition event may occur on a subset of HARQ processes. For example, the repetition configuration 510 may indicate that repetitions occur for certain HARQ process identifiers. In some such examples, the UE 504 may perform combining and decoding of repetitions for corresponding HARQ process identifiers.

[0084] Although for the purpose of illustrating the principle of L1 cross-carrier repetition, Figure 5 The example of only describes a single repetition, but it will be appreciated that the principle can be extended to any number of repetitions.

[0085] Figure 6 An example timing diagram 600 is illustrated regarding an apparatus receiving a downlink transmission and sending an uplink transmission. The example apparatus may be a UE, such as the example UE 104, UE 350, UE 404, and / or UE 504. The example timing diagram 600 includes a first component carrier (CC7) and a second component carrier (CC0). However, other examples may include any suitable number of component carriers.

[0086] The example timing diagram 600 also includes a first period 602 and a second period 604. The start of the first period 602 can be defined by a first common start boundary 602a. The start of the second period 604 can be defined by a second common start boundary 604a. The common start boundaries 602a, 604a can be determined based on a common frame boundary (e.g., SFN=0) and / or via DCI signaling. Figure 6 In the illustrated example of , the duration of the cycles 602, 604 is 0.5 ms. However, other examples may utilize any suitable cycle duration.

[0087] In the illustrated timing diagram 600, the device receives a first downlink control transmission 610 (e.g., PDCCH) on a first component carrier (CC7). The device also receives a second downlink control transmission 612 (e.g., PDCCH) on a second component carrier (CC0). In the illustrated example, the downlink control transmissions 610, 612 provide duplicate configurations for the corresponding component carriers. For example, the first downlink control transmission 610 may indicate activation of an "X" SPS configuration (e.g., SPS configuration X) for the first component carrier (CC7), while the second downlink control transmission 612 may indicate activation of a "Y" SPS configuration (e.g., SPS configuration Y) for the second component carrier (CC0). Aspects of the downlink control transmissions 610, 612 may be provided by Figure 5 This is achieved by the repeated configuration 510.

[0088] In the illustrated example, SPS configuration X may indicate that a first repetition 620 of a first data transmission may be received on a first component carrier (CC7) during a first period 602 and a second repetition 622 of a second data transmission may be received on the first component carrier (CC7) during a second period 604.

[0089] In the illustrated example, SPS configuration Y may indicate that a third repetition 624 of the first data transmission may be received on the second component carrier (CC0) during the first period 602, and a fourth repetition 626 of the second data transmission may be received on the second component carrier (CC0) during the second period 604. Example SPS configuration Y may also indicate that the UE will send a first uplink control transmission 630 during the first period 602, and will send a second uplink control transmission 632 during the second period 604.

[0090] In the illustrated example, the device receives the first repetition 620 earlier during the first period 602 than the third repetition 624. Similarly, the device receives the second repetition 622 earlier during the second period 604 than the fourth repetition 626.

[0091] In the illustrated example, the device may combine transmissions and / or repetitions received during the same period. For example, for the first period 602, the device may combine the first repetition 620 received on the first component carrier (CC7) and the third repetition 624 received on the second component carrier (CC0). For the second period 604, the device may combine the second repetition 622 received on the first component carrier (CC7) and the fourth repetition 626 received on the second component carrier (CC0). The device may then attempt to decode the corresponding combined results and generate a common ACK / NACK signal for the corresponding periods 602, 604. For example, the device may use a first uplink control transmission 630 (e.g., PUCCH) to send a first common ACK / NACK signal associated with the first period 602. The device may also use a second uplink control transmission 632 (e.g., PUCCH) to send a second common ACK / NACK signal associated with the second period 604.

[0092] Therefore, if Figure 6 As shown, the apparatus is able to link repetitions of data transmissions across component carriers for configuration.

[0093] Figure 7 An example timing diagram 700 is illustrated for an apparatus receiving a downlink transmission and sending a common ACK / NACK signal for each received repetition. For example, the apparatus may combine repetitions of data transmissions received during a period to generate a common ACK / NACK signal and then send the common ACK / NACK signal via an uplink control channel associated with each data transmission repetition.

[0094] The example apparatus may be a UE, such as the example UE 104, UE 350, UE 404, and / or UE 504. The example timing diagram 700 includes a first component carrier (CC15), a second component carrier (CC8), a third component carrier (CC7), and a fourth component carrier (CC0). In the illustrated example, the second component carrier (CC8) may be used to send an uplink control transmission associated with a downlink data transmission received via the first component carrier (CC15). The fourth component carrier (CC0) may be used to send an uplink control transmission associated with a downlink data transmission received via the third component carrier (CC7).

[0095] The example timing diagram 700 also includes a first cycle 702 and a second cycle 704. The start of the first cycle 702 can be defined by a first common start boundary 702a. The start of the second cycle 704 can be defined by a second common start boundary 704a. The common start boundaries 702a, 704a can be determined based on common frame boundaries (e.g., SFN=0) and / or via DCI signaling. In the illustrated example, the cycles 702, 704 are associated with the transmission of corresponding data transmissions. For example, a repetition of the first data transmission can be received during the first cycle 702, and a repetition of the second data transmission can be received during the second cycle 704. In the illustrated example, the duration of the cycles 702, 704 is 0.5ms. However, other examples can utilize any suitable cycle duration.

[0096] In the illustrated timing diagram 700, the device receives a first downlink control transmission 710 (e.g., PDCCH) on a first component carrier (CC15). The device also receives a second downlink control transmission 712 (e.g., PDCCH) on a third component carrier (CC7). In the illustrated example, the downlink control transmissions 710, 712 provide duplicate configurations for the corresponding component carriers. For example, the first downlink control transmission 710 can activate SPS configuration X for the first component carrier (CC15), and the second downlink control transmission 712 can activate SPS configuration Y for the third component carrier (CC7). Aspects of the downlink control transmissions 710, 712 can be activated by Figure 5 This is achieved by the repeated configuration 510.

[0097] In the illustrated example, during the first period 702, the device receives a first repetition 720 (e.g., PDSCH) of a first data transmission on the first component carrier (CC15) and a second repetition 722 (e.g., PDSCH) of the first data transmission on the third component carrier (CC7). During the second period 704, the device receives a third repetition 724 (e.g., PDSCH) of a second data transmission on the first component carrier (CC15) and a fourth repetition 726 (e.g., PDSCH) of the second data transmission on the third component carrier (CC7).

[0098] In the illustrated example, the device receives the first repetition 720 earlier during the first period 702 than the second repetition 722. Similarly, the device receives the third repetition 724 earlier during the second period 704 than the fourth repetition 726.

[0099] In the illustrated example, the device combines the repetitions of data transmission received in the same period to generate a common ACK / NACK signal associated with the corresponding data transmission. For example, the device may combine the first repetition 720 and the second repetition 722 received during the first period 702, and attempt to decode the corresponding first data transmission. Then, the device may generate the same ACK / NACK signal (e.g., a common ACK / NACK signal) for repetitions 720 and 722 based on whether the device can correctly decode the first data transmission. In the illustrated example, the device sends a common ACK / NACK signal in the corresponding uplink control channel associated with each repetition. For example, the device may send a common ACK / NACK signal associated with the first period 702 via a first uplink control transmission 730 (e.g., PUCCH) on a second component carrier (CC8) corresponding to the first repetition 720. The device may also send a common ACK / NACK signal associated with the first period 702 via a second uplink control transmission 732 (e.g., PUCCH) on a fourth component carrier (CC0) corresponding to the second repetition 722. In the illustrated example, the device sends the first uplink control transmission 730 earlier than the second uplink control transmission 732 during the first period 702 .

[0100] Similarly, with respect to the second cycle 704, the device may combine the third repetition 724 and the fourth repetition 726 received during the second cycle 704 and attempt to decode the corresponding second data transmission. The device may then generate the same ACK / NACK signal (e.g., a common ACK / NACK signal) for the repetitions 724 and 726 based on whether the device is able to correctly decode the second data transmission. In the illustrated example, the device may send the common ACK / NACK signal associated with the second cycle 704 via a third uplink control transmission 734 (e.g., PUCCH) on a second component carrier (CC8) corresponding to the third repetition 724. The device may also send the common ACK / NACK signal associated with the second cycle 704 via a fourth uplink control transmission 736 (e.g., PUCCH) on a fourth component carrier (CC0) corresponding to the fourth repetition 726. In the illustrated example, the device sends the third uplink control transmission 734 earlier than the fourth uplink control transmission 736 during the second cycle 704.

[0101] In some examples, for each repetition, the common ACK / NACK signal has a bit position in a corresponding codebook determined by the repetition event. In some examples, the bit position of the common ACK / NACK signal depends on the time distance between the repetition and the uplink control channel. For example, the first uplink control transmission 730 may have a first bit position carried by an uplink control channel associated with the first repetition 720, the second uplink control transmission 732 may have a second bit position carried by an uplink control channel associated with the second repetition 722, the third uplink control transmission 734 may have a third bit position carried by an uplink control channel associated with the third repetition 724, and the fourth uplink control transmission 736 may have a fourth bit position carried by an uplink control channel associated with the fourth repetition 726.

[0102] In some examples, the distance threshold may provide a temporal distance between the earliest transmission of a common ACK / NACK signal and the receipt of a last repetition of a data transmission. In some examples, the distance threshold corresponds to a duration within a period before the earliest common ACK / NACK signal may be sent. In some such examples, the distance threshold may provide a sufficient temporal distance to enable the repetitions associated with the period to be received before the device performs merging and attempts decoding of the data transmission.

[0103] For example, in Figure 7 In the example shown, the first cycle 702 includes a first distance threshold 740 and the second cycle 704 includes a second distance threshold 742. The first distance threshold 740 can provide a sufficient time distance between receiving the second repetition 722 (e.g., the last repetition of the first cycle 702) and sending the first uplink control transmission 730 (e.g., the earliest transmission of the common ACK / NACK signal for the first cycle 702). Similarly, the second distance threshold 742 can provide a sufficient time distance between receiving the fourth repetition 726 (e.g., the last repetition of the second cycle 704) and sending the third uplink control transmission 734 (e.g., the earliest transmission of the common ACK / NACK signal for the second cycle 704). Therefore, it can be understood that the distance threshold can prevent the device from attempting to generate and send a common ACK / NACK signal before receiving each repetition associated with the corresponding cycle.

[0104] Figure 8 An example timing diagram 800 is illustrated for an apparatus receiving a downlink transmission and sending a common ACK / NACK signal based on a rule. For example, the apparatus may combine repetitions of data transmissions received during a period to generate a common ACK / NACK signal and then send the common ACK / NACK signal via an uplink control channel associated with the last received data transmission repetition.

[0105] The example apparatus may be a UE, such as the example UE 104, UE 350, UE 404, and / or UE 504. The example timing diagram 800 includes a first component carrier (CC15), a second component carrier (CC8), a third component carrier (CC7), and a fourth component carrier (CC0). In the illustrated example, the second component carrier (CC8) may be used to transmit uplink control transmissions 830, 834 (e.g., PUCCH) associated with downlink data transmissions (e.g., downlink data transmissions 820, 824 (e.g., PDSCH)) received via the first component carrier (CC15). The fourth component carrier (CC0) may be used to transmit uplink control transmissions 832, 836 (e.g., PUCCH) associated with downlink data transmissions (e.g., downlink data transmissions 822, 826 (e.g., PDSCH)) received via the third component carrier (CC7).

[0106] The example timing diagram 800 also includes a first cycle 802 and a second cycle 804. The start of the first cycle 802 can be defined by a first common start boundary 802a. The start of the second cycle 804 can be defined by a second common start boundary 804a. The common start boundaries 802a, 804a can be determined based on common frame boundaries (e.g., SFN=0) and / or via DCI signaling. In the example shown, the cycles 802, 804 are associated with the transmission of corresponding data transmissions. For example, a repetition of the first data transmission can be received during the first cycle 802, and a repetition of the second data transmission can be received during the second cycle 804. In the illustrated example, the cycles 802, 804 have a duration of 0.5ms. However, other examples can utilize any suitable cycle duration.

[0107] In the illustrated timing diagram 800, the device receives a first downlink control transmission 810 (e.g., PDCCH) on a first component carrier (CC15). The device also receives a second downlink control transmission 812 (e.g., PDCCH) on a third component carrier (CC7). In the illustrated example, the downlink control transmissions 810, 812 provide duplicate configurations for the corresponding component carriers. For example, the first downlink control transmission 810 can activate SPS configuration X for the first component carrier (CC15), and the second downlink control transmission 812 can activate SPS configuration Y for the third component carrier (CC7). Aspects of the downlink control transmissions 810, 812 can be activated by Figure 5 This is achieved by the repeated configuration 510.

[0108] exist Figure 8In the illustrated example of , during a first period 802, the device receives a first repetition 820 (e.g., PDSCH) of a first data transmission on a first component carrier (CC15) and a second repetition 822 (e.g., PDSCH) of the first data transmission on a third component carrier (CC7). During a second period 804, the device receives a third repetition 824 (e.g., PDSCH) of a second data transmission on the first component carrier (CC15) and a fourth repetition 826 (e.g., PDSCH) of the second data transmission on the third component carrier (CC7).

[0109] In the illustrated example, during the first cycle 802, the device receives the first repetition 820 earlier than the second repetition 82. Similarly, during the second cycle 804, the device receives the third repetition 824 earlier than the fourth repetition 826.

[0110] In the illustrated example, the device combines repetitions of data transmissions received within the same period to generate a common ACK / NACK signal associated with the corresponding data transmissions. For example, the device can combine the first repetition 820 and the second repetition 822 received during the first period 802 and attempt to decode the corresponding first data transmission. The device can then generate the same ACK / NACK signal (e.g., a common ACK / NACK signal) for the repetitions 820, 822 based on whether the device was able to correctly decode the first data transmission.

[0111] Similarly, with respect to the second period 804, the device may combine the third repetition 824 and the fourth repetition 826 received during the second period 804 and attempt to decode the corresponding second data transmission. The device may then generate the same ACK / NACK signal (e.g., a common ACK / NACK signal) for the repetitions 824, 826 based on whether the device was able to correctly decode the second data transmission.

[0112] In the illustrated example, the device may then send a common ACK / NACK signal based on a rule. In some examples, the rule may be provided via a downlink control transmission (e.g., downlink control transmissions 810, 812). In the illustrated example, the rule configures the device to send a common ACK / NACK signal using an uplink control transmission associated with the last repetition in a cycle.

[0113] For example, with respect to the first period 802, the device receives the first repetition 820 earlier than the second repetition 822, and therefore, the second repetition 822 is the last repetition received during the first period 802. Therefore, the device can use the uplink control transmission 832 (e.g., PUCCH) associated with the second repetition 822 to send a common ACK / NACK signal associated with the first data transmission.

[0114] Similarly, with respect to the second period 804, the device receives the third repetition 824 earlier than the fourth period 826, and thus, the fourth repetition 826 is the last repetition received during the second period 804. Therefore, the device can use the uplink control transmission 836 (e.g., PUCCH) associated with the fourth repetition 826 to send a common ACK / NACK signal associated with the second data transmission.

[0115] It will be appreciated that while the above examples include a rule that configures the apparatus to send a common ACK / NACK signal using an uplink control transmission associated with the last repetition in a cycle, in additional or alternative examples, other rules may be used to determine when and / or where to send a common ACK / NACK signal. For example, the rule may cause the apparatus to send a common ACK / NACK signal for each repetition (as described above in conjunction with Figure 7 700).

[0116] Fig. 9 An example wireless communication 900 between a base station 902 and a UE 904 as described herein is illustrated. Fig. 9 In the illustrated wireless communication 900, a UE 904 sends a data transmission and a repetition of the data transmission to a base station 902. One or more aspects of the base station 902 may be implemented by Figure 1 Base station 102, Figure 1 Base station 180, Figure 3 Base station 310, Figure 4 Base station 402 and / or Figure 5 One or more aspects of UE 904 may be implemented by Figure 1 UE 104, Figure 3 UE 350, Figure 4 UE 404 and / or Figure 5 UE 504 implements.

[0117] It will be appreciated that although the wireless communication 900 includes one base station 902 communicating with one UE 904, in additional or alternative examples, the base station 902 may communicate with any appropriate number of UEs 904 and / or base stations 902, and / or the UE 904 may communicate with any appropriate number of base stations 902 and / or UEs 904.

[0118] In the illustrated example, at 908, the base station 902 may determine a repetition configuration 910. The repetition configuration 910 may be associated with an SPS configuration or a CG configuration. The repetition configuration 910 may be associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity.

[0119] The base station 902 may send a repetition configuration 910 that is received by the UE 904. The repetition configuration 910 may be associated with an SPS configuration or a CG configuration associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity.

[0120] At 912, UE 904 may determine on which entities to send repetitions of data transmission based on repetition configuration 910. For example, UE 904 may determine to send a first repetition at a first entity and to send a second repetition at a second entity based on repetition configuration 910. In some examples, the first entity and the second entity may include frequency resources. In some examples, the first entity and the second entity may include component carriers (CCs) (or cells).

[0121] The UE 904 may then send a data transmission 914. For example, the UE 904 may send the data transmission 914 via the PUSCH. The UE 904 may then send a copy of the data transmission 914 (e.g., data repetition 916). For example, the UE 904 may send the repetition 916 using the entity indicated by the repetition configuration 910. Fig. 9 The example of FIG. 1 shows one example repetition 916, but it is understood that in other examples, repetition 916 may be implemented by one or more repetitions of data transmission 914. Aspects of data transmission 914 may be implemented by Figure 4 The control transfer 430 is implemented. The aspect of repeating 916 can be Figure 4 This is achieved by controlling the retransmission 432.

[0122] At 918, base station 902 may combine and decode the data transmission 914 and repetitions 916 of the data transmission. In some examples, base station 902 may combine one or more repetitions associated with and received during the same period.

[0123] In some examples, base station 902 may send repetition configuration 910 via RRC signaling, via DCI signaling, and / or via MAC-CE. In some examples, repetition configuration 910 may include an identifier associated with the repetition configuration. In some examples, repetition configuration 910 may include a period identifier.

[0124] In some examples, repetition configuration 910 may correspond to an entity, such as a frequency resource or a component carrier (CC). For example, repetition configuration 910 may indicate on which CC repetitions may be received and / or on which CC repetitions may be sent.

[0125] In some examples, the repetition configuration 910 may include a group of repetition configurations. In some examples, the group of repetition configurations may be associated with the same cycle (or cycle) with a common start boundary. In some examples, the common start boundary may be determined based on a common frame boundary (e.g., SFN=0). In some examples, the common start boundary may be configured via DCI signaling.

[0126] In some examples, the UE 904 may determine at 912 that the same transport block (TB) or control block group (CBG) occurs on uplink data transmissions using different entities. For example, based on the repetition configuration 910, the UE 904 may determine to send a first repetition using a first uplink data transmission on a first entity, and may determine to send a second repetition using a second uplink data transmission on a second entity.

[0127] Although in order to illustrate the principle of L1 cross-carrier repetition, combined Fig. 9 The example of only describes a single repetition, but it will be appreciated that the principle can be extended to any number of repetitions.

[0128] Fig.10 An example timing diagram 1000 is illustrated for an apparatus receiving downlink transmissions and sending uplink transmissions. The example apparatus may be a UE, such as example UE 104, UE 350, UE 404, UE 504, and / or UE 904. The example timing diagram 1000 includes a first component carrier (CC7) and a second component carrier (CC0).

[0129] The example timing diagram 1000 also includes a first cycle 1002 and a second cycle 1004. In the illustrated example, the first cycle 1002 can be associated with a first data transmission, and the second cycle 1004 can be associated with a second data transmission. The start of the first cycle 1002 can be defined by a first common start boundary 1002a. The start of the second cycle 1004 can be defined by a second common start boundary 1004a. The common start boundaries 1002a, 1004a can be determined based on a common frame boundary (e.g., SFN=0) and / or via DCI signaling. In the illustrated example, the duration of the cycles 1002, 1004 is 0.5ms. However, other examples can utilize any suitable cycle duration.

[0130] In the illustrated timing diagram 1000, the device receives a first downlink control transmission 1010 (e.g., PDCCH) on a first component carrier (CC7). The device also receives a second downlink control transmission 1012 (e.g., PDCCH) on a second component carrier (CC0). In the illustrated example, the downlink control transmissions 1010, 1012 provide duplicate configurations for the respective component carriers. For example, the first downlink control transmission 1010 may indicate activation of an "X" CG configuration (e.g., CG configuration X) for the first component carrier (CC7), while the second downlink control transmission 1012 may indicate activation of a "Y" CG configuration (e.g., CG configuration Y) for the second component carrier (CC0). Aspects of the downlink control transmissions 1010, 1012 may be provided by Figure 5 This is achieved by the repeated configuration 510.

[0131] In the illustrated example, CG configuration X may configure the device to send a repetition 1020 (e.g., PUSCH) of a first data transmission on a first component carrier (CC7) during a first period 1002, and to send a repetition 1022 (e.g., PUSCH) of a second data transmission on the first component carrier (CC7) during a second period 1004.

[0132] In the illustrated example, CG configuration Y may configure the device to send another repetition 1024 of the first data transmission on the second component carrier (CC0) during the first cycle 1002 and to send another repetition 1026 of the second data transmission on the second component carrier (CC0) during the second cycle 1004.

[0133] In the illustrated example, during the first period 1002, the device sends the first repetition 1020 earlier than the other repetitions 1024. Similarly, during the second period 1004, the device sends the second repetition 1022 earlier than the other repetitions 1026.

[0134] In the illustrated example, a receiving device (eg, a base station, such as a Figure 1 Base station 102, Figure 1 Base station 180, Figure 3 Base station 310, Figure 4 Base station 402 and / or Figure 5 The base station 502 of the receiving device may combine transmissions and / or repetitions received during the same period. For example, with respect to the first period 1002, the receiving device may combine repetitions 1020, 1024 sent by the device during the first period 1002 to determine the first data transmission. Similarly, with respect to the second period 1004, the receiving device may combine repetitions 1022, 1026 sent by the device during the second period 1004 to determine the second data transmission.

[0135] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 404, UE 504, and / or UE 904; apparatus 1202) or a component of a UE, which may include a memory 360 and may be the entire UE or a component of a UE (e.g., TX processor 368, RX processor 356, and / or controller / processor 359). The method may be performed by a base station (e.g., base station 102, base station 180, base station 310, base station 402, base station 502, and / or base station 902; apparatus 1402) or a component of a base station, which may include a memory 376 and may be the entire base station or a component of a base station (e.g., TX processor 316, RX processor 370, and / or controller / processor 375). Optional aspects are illustrated with dashed lines.

[0136] At 1102, the apparatus determines a repetition configuration for an SPS or CG associated with data transmission on a first entity and at least one repetition of data transmission on a second entity, as described above in conjunction with Figure 5 512 and / or Fig. 9 912. For example, it can be Fig.12 The configuration component 1240 of the apparatus 1202 performs 1102. The first entity and the second entity may each include frequency resources. In another example, the first entity and the second entity may each include a cell or a component carrier.

[0137] At 1106, the device receives a data transmission and at least one repetition of the data transmission, as described above in conjunction with Figure 5 Data transmission 514 and repetition 516 and / or Fig. 9 1106. For example, the receiving component 1230 of the device 1202 and / or the data component 1242 of the device 1202 may be performed. The data transmission may be received at a first entity and at least one repetition may be received at a second entity. In some examples, multiple repetitions of the data transmission may be sent at an entity different from the first entity. Although the receiving of the data transmission and the repetition of the data transmission are shown simultaneously, the receiving may also be performed separately. If Fig.11 If the method is performed by a UE, data transmission may be received on a downlink data channel (e.g., PDSCH) on a first entity, and a repetition of the data transmission may be received on a downlink data channel (e.g., PDSCH) on a second entity. Fig.11The method is performed by a base station, then data transmission may be received on an uplink data channel (eg, PUSCH) on a first entity, and a repetition of the data transmission may be received on an uplink data channel (eg, PUSCH) on a second entity.

[0138] At 1108, the apparatus combines the data transmission and at least one repetition of the data transmission to decode the data transmission, as described above in conjunction with, for example, Figure 5 518 and / or Fig. 9 918. For example, it can be Fig.12 The merging component 1244 of the device 1202 executes 1108.

[0139] In an example where the method is performed by a UE, the data transmission may include downlink data transmission, for example, on a downlink shared channel. In such an example, as described above in conjunction with, for example Figure 5 As described in 520, the UE may generate a common ACK / NACK signal based on decoding the data transmission at 1110. For example, 1110 may be composed of Fig.12 The ACK / NACK component 1246 of the apparatus 1202 of the embodiment of the present invention is performed. For example, if the UE is able to combine the repetitions of the data transmission to correctly receive the data transmission, the UE can send an ACK to the base station. If the UE cannot correctly receive the data transmission after combining the repetitions, the UE can send a NACK to the base station. The NACK can prompt the base station to retransmit the data transmission to the UE.

[0140] At 1112, the UE may send a common ACK / NACK signal as described above in conjunction with, for example, Figure 5The common ACK / NACK signal 522 of the device 1202 is described. For example, 1112 can be performed by the ACK / NACK component 1246 of the device 1202 and / or the sending component 1234 of the device 1202. In the first example, the ACK / NACK signal can be sent using a third entity configured to send a control channel associated with the first entity. In the second example, the ACK / NACK signal can be sent using a third entity configured to send a control channel associated with the second entity. The common ACK / NACK signal can be associated with a bit position in the ACK / NACK codebook carried by the uplink control channel on the third entity. The bit position can be based on the time distance between the repetition of the data transmission on the second entity and the uplink control channel on the third entity. In the second example, the ACK / NACK signal can be sent using a third entity configured to send a control channel associated with the second entity. The common ACK / NACK signal can be associated with a bit position in the ACK / NACK codebook carried by the uplink control channel on the third entity. The bit position may be based on the temporal distance between the repetition of the data transmission on the second entity and the uplink control channel on the third entity. In another example, a common ACK / NACK signal may be sent using multiple entities (e.g., as combined with Figure 7 described above).

[0141] The time distance between sending the earliest common ACK / NACK signal and receiving the last repetition of the data transmission may be greater than a distance threshold. The distance threshold corresponds to a duration for combining and decoding the data transmission and at least one repetition of the data transmission. The third entity may be associated with the last entity for the last repetition of the data transmission.

[0142] An identifier (ID) of a mergeable repeated SPS or CG configured to be carried on different entities may be indicated by a base station via at least one of RRC signaling, DCI signaling, or MAC-CE. At least one repetition of a data transmission may be limited to a subset of HARQ process identifiers associated with the identifier of the configured SPS or CG indicated by the base station.

[0143] The data transmission may be included in a downlink data channel configured based on the SPS. In another example, the method may be performed by a base station. Thus, the data transmission may be included in an uplink data channel (e.g., PUSCH) received from the UE. The uplink data channel may be configured based on the CG.

[0144] Each of the at least one repetition of the data transmission may be associated with the same period having a common starting boundary. As shown at 1104, an indication of the common starting boundary may be received via downlink control information (DCI) signaling, as described above in conjunction with, for example Figure 6 The common starting boundaries 602a, 604a, Figure 7 The common starting boundaries 702a, 704a, Figure 8 The common starting boundaries 802a, 804a, and / or Fig.10 The common starting boundaries 1002a, 1004a are described. For example, Fig.12 The boundary component 1248 of the device 1202 performs 1104. The data transmission and the at least one repetition of the data transmission can be received in the same cycle.

[0145] Fig.12 1200 is a diagram illustrating an example of a hardware implementation of an apparatus 1202. The apparatus 1202 is a UE and includes a cellular baseband processor 1204 (also referred to as a modem) coupled to a cellular RF transceiver 1222 and one or more subscriber identity modules (SIM) cards 1220, an application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210, a Bluetooth module 1212, a wireless local area network (WLAN) module 1214, a global positioning system (GPS) module 1216, and a power supply 1218. The cellular baseband processor 1204 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1222. The cellular baseband processor 1204 may include a computer-readable medium / memory. The cellular baseband processor 1204 is responsible for general processing, including executing software stored on a computer-readable medium / memory. When executed by the cellular baseband processor 1204, the software causes the cellular baseband processor 1204 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1204 when executing software. The cellular baseband processor 1204 also includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. The communication manager 1232 includes one or more of the components shown. The components within the communication manager 1232 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1204. The cellular baseband processor 1204 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 1202 may be a modem chip and include only the baseband processor 1204, and in another configuration, the device 1202 may be the entire UE (e.g., see Figure 3UE 350), and includes the above-mentioned additional modules of device 1202.

[0146] The communication manager 1232 includes a configuration component 1240, a data component 1242, a merge component 1244, an ACK / NACK component 1246, and a boundary component 1248, which can be configured to perform a combination Fig.11 Aspects of description.

[0147] The apparatus may include performing the above Fig.11 An additional component for each box of the algorithm in the flowchart. Therefore, Fig.11 Each block in the above flowchart may be performed by a component, and the apparatus may include one or more of these 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 processor implementation, or a combination of the above.

[0148] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes means for performing any aspects of determining a repetition configuration for an SPS or CG associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The apparatus 1202 may also include means for receiving the data transmission and at least one repetition of the data transmission. The apparatus 1202 may also include means for combining the data transmission and at least one repetition of the data transmission to decode the data transmission. The apparatus 1202 may also include means for generating a common ACK / NACK signal based on decoding the data transmission when the data transmission includes a downlink data transmission. The apparatus 1202 may also include means for sending a common ACK / NACK signal using a third entity configured to send a control channel associated with the first entity when the data transmission includes a downlink data transmission. The apparatus 1202 may also include means for generating a common ACK / NACK signal based on decoding the data transmission when the data transmission includes a downlink data transmission. The apparatus 1202 may also include means for sending a common ACK / NACK signal to the base station using a third entity configured to send an uplink control channel when the data transmission includes a downlink data transmission, the third entity being associated with the second entity. The apparatus 1202 may also include means for receiving an indication of a common starting boundary via DCI signaling.

[0149] If the apparatus 1202 includes a UE, the aforementioned means may be one or more of the aforementioned components of the apparatus 1202 configured to perform the functions described by the aforementioned means. As described above, the apparatus 1202 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned means may be a TX processor 368, an RX processor 356, and a controller / processor 359, which are configured to perform the functions described by the aforementioned means.

[0150] If the apparatus 1202 includes a base station, the aforementioned means may be one or more of the aforementioned components of the apparatus 1202 configured to perform the functions described by the aforementioned means. As described above, the apparatus 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned means may be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions described by the aforementioned means.

[0151] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 404, UE 504, and / or UE 904; apparatus 1202) or a component of a UE, which may include a memory 360 and may be the entire UE or a component of a UE (e.g., TX processor 368, RX processor 356, and / or controller / processor 359). The method may be performed by a base station (e.g., base station 102, base station 180, base station 310, base station 402, base station 502, and / or base station 902; apparatus 1402) or a component of a base station, which may include a memory 376 and may be the entire base station or a component of a base station (e.g., TX processor 316, RX processor 370, and / or controller / processor 375). Optional aspects are illustrated with dashed lines.

[0152] At 1302, the device determines a repetition configuration for an SPS or CG associated with at least one repetition of data transmission on a first entity and data transmission on a second entity, as described above in conjunction with Figure 5 512 and / or Fig. 9 912. For example, it can be Fig.14 The configuration component 1440 of the apparatus 1402 performs 1302. The first entity and the second entity may each include frequency resources. In another example, the first entity and the second entity may each include a cell or a component carrier.

[0153] At 1306, the device sends a data transmission, as described above in conjunction with Figure 5 Data transmission 514 and / or Fig. 9The data transmission 914 is described. For example, 1306 can be performed by the sending component 1434 of the device 1402 and / or the data component 1442 of the device 1402. The data transmission can be sent on the first entity.

[0154] At 1308, the device sends at least one repetition of the data transmission, as described above in conjunction with Figure 5 Repeated 516 and / or Fig. 9 The method may be performed as described in 916 of the repetition of the transmission of the data. For example, 1308 may be performed by the repetition component 1444 of the device 1402. At least one repetition may be sent on the second entity. In some examples, multiple repetitions of the data transmission may be sent on an entity different from the first entity. If the method is performed by a UE, the data transmission may be sent on an uplink data channel on the first entity, and the repetition of the data transmission may be sent on an uplink data channel on the second entity. If the method is performed by a base station, the data transmission may be sent on a downlink data channel on the first entity, and the repetition of the data transmission may be sent on a downlink data channel on the second entity.

[0155] At 1310, the device may receive a common ACK / NACK signal, as described above in conjunction with Figure 5 1310. For example, 1310 may be performed by a receiving component 1430 and / or an ACK / NACK component 1446 of the device 1402. For example, if the UE is able to combine repetitions of data transmission to correctly receive the data transmission, the base station may receive an ACK. If the UE cannot correctly receive the data transmission after combining the repetitions, the base station may receive a NACK. The NACK may prompt the base station to retransmit the data transmission to the UE. In a first example, the ACK / NACK signal may be received using a third entity configured for a control channel associated with the first entity. In a second example, the ACK / NACK signal may be received using a third entity configured for a control channel associated with the second entity. The common ACK / NACK signal may be associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity. The bit position may be based on a time distance between a repetition of data transmission on the second entity and an uplink control channel on the third entity. In a second example, the ACK / NACK signal may be received using a third entity configured for a control channel associated with the second entity. The common ACK / NACK signal may be associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity. The bit position may be based on a temporal distance between a repetition of the data transmission on the second entity and the uplink control channel on the third entity. In another example, the common ACK / NACK signal may be received using multiple entities (e.g., as in combination with Figure 7 described above).

[0156] The time distance between receiving the earliest common ACK / NACK signal and sending the last repetition of the data transmission may be greater than a distance threshold. The distance threshold corresponds to a duration for combining and decoding the data transmission and at least one repetition of the data transmission. The third entity may be associated with the last entity for the last repetition of the data transmission.

[0157] An identifier (ID) of a mergeable repeated SPS or CG configured to be carried on different entities may be indicated by a base station, for example, via at least one of RRC signaling, DCI signaling, or MAC-CE. At least one repetition of a data transmission may be limited to a subset of HARQ process identifiers associated with the identifier of the configured SPS or CG indicated by the base station.

[0158] The data transmission may be included in a downlink data channel configured based on the SPS. In another example, the method may be performed by a UE. Thus, the data transmission may be included in an uplink data channel sent from the UE. The uplink data channel may be configured based on the CG.

[0159] Each of the at least one repetition of the data transmission may be associated with the same period having a common starting boundary. As shown at 1304, an indication of the common starting boundary may be received / sent via downlink control information (DCI) signaling, as described above in conjunction with, for example Figure 6 The common starting boundaries 602a, 604a of Figure 7 The common starting boundaries 702a, 704a of Figure 8 The common starting boundaries 802a, 804a of Fig.10 The common starting boundaries 1002a, 1004a are described. For example, Fig.14 The boundary component 1448 of the device 1402 performs 1304. The data transmission and at least one repetition of the data transmission can be sent in the same cycle.

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

[0161] The communication manager 1432 includes a configuration component 1440, a data component 1442, a repeat component 1444, an ACK / NACK component 1446, and a boundary component 1448, which can be configured to perform a combined Fig.13 Aspects of description.

[0162] The apparatus may include performing the above Fig.13 An additional component for each box of the algorithm in the flowchart. Therefore, Fig.13 Each block in the above flowchart may be performed by a component, and the apparatus may include one or more of these 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 processor implementation, or a combination of the above.

[0163] In one configuration, the apparatus 1402, in particular the baseband unit 1404, includes a unit for determining a repetition configuration for an SPS or CG associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity. The apparatus 1402 may also include a unit for sending the data transmission on the first entity. The apparatus 1402 may also include a unit for sending at least one repetition of the data transmission on the second entity. The apparatus 1402 may also include a unit for receiving a common ACK / NACK signal for the data transmission from the UE, wherein when the data transmission includes a downlink data transmission, the common ACK / NACK is received using a third entity configured to send a control channel associated with the first entity. The apparatus 1402 may also include a unit for receiving a common ACK / NACK signal for the data transmission from the UE, wherein when the data transmission includes a downlink data transmission, the common ACK / NACK is received using a third entity configured to send an uplink control channel, the third entity being associated with the second entity. The apparatus 1402 may also include a unit for receiving an indication of a common starting boundary via DCI signaling.

[0164] If the apparatus 1402 includes a UE, the aforementioned means may be one or more of the aforementioned components configured to perform the functions described by the aforementioned means of the apparatus 1402. As described above, the apparatus 1402 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned means may be a TX processor 368, an RX processor 356, and a controller / processor 359, which are configured to perform the functions described by the aforementioned means.

[0165] If the apparatus 1402 includes a base station, the aforementioned means may be one or more of the aforementioned components of the apparatus 1402, configured to perform the functions described by the aforementioned means. As described above, the apparatus 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned means may be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions described by the aforementioned means.

[0166] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary manner. Based on design preferences, it should be 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 an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0167] 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 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 to conform to the full scope consistent with the language claims, wherein the reference element in the singular form is not intended to represent "one and only one" (unless specifically stated), but "one or more". "If", "when..." and "when..." terms such as "under..." should be interpreted as "under..." conditions, rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., "when...") do not mean to respond to the occurrence of the action or to take action immediately during the occurrence of the action, but only mean that if a certain condition is met, the action will occur, but does not require a specific or immediate time limit for the occurrence of the action. The word "exemplary" is used herein to represent "used as an example, instance or illustration". Any aspect described herein as "exemplary" is not necessarily interpreted as being preferred to or conducive to other aspects. Unless otherwise specified, 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 or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, 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 “unit.” Therefore, no claim element should be interpreted as a functional module unless the element is explicitly recited using the phrase “unit for . . . .”

[0168] The following examples are merely illustrative examples and may be combined with other embodiments or aspects of the teachings described herein, but are not limited thereto.

[0169] Example 1 is a method of wireless communication, comprising: determining a repetition configuration for an SPS or CG associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity; receiving the data transmission and at least one repetition of the data transmission; and combining the data transmission and the at least one repetition of the data transmission to decode the data transmission.

[0170] In Example 2, the method according to Example 1 also includes the first entity and the second entity each including frequency resources.

[0171] In Example 3, the method according to any of Examples 1 or 2 further includes the first entity and the second entity each comprising a cell or a component carrier.

[0172] In Example 4, the method according to any of Examples 1 to 3 also includes: data transmission includes downlink data transmission, and the method also includes: generating a common ACK / NACK signal based on decoding the data transmission; and sending the common ACK / NACK signal using a third entity configured to send a control channel associated with the first entity.

[0173] In Example 5, the method according to any of Examples 1 to 4 further includes: the common ACK / NACK signal is associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity.

[0174] In Example 6, the method of any of Examples 1 to 5 further includes: the bit position is based on a time distance between a repetition of data transmission on the second entity and an uplink control channel on the third entity.

[0175] In Example 7, the method according to any of Examples 1 to 6 also includes: data transmission includes downlink data transmission, the method also includes: generating a common ACK / NACK signal based on decoding the data transmission; and sending the common ACK / NACK signal to the base station using a third entity configured to send an uplink control channel, the third entity being associated with the second entity.

[0176] In Example 8, the method according to any of Examples 1 to 7 further includes: the common ACK / NACK signal is associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity.

[0177] In Example 9, the method according to any of Examples 1 to 8 further includes: the bit position is based on a time distance between a repetition of data transmission on the second entity and an uplink control channel on the third entity.

[0178] In Example 10, the method described in any of Examples 1 to 9 also includes: the time distance between sending the earliest common ACK / NACK signal and receiving the last repetition of the data transmission is greater than a distance threshold, wherein the distance threshold corresponds to the duration for combining and decoding the data transmission and at least one repetition of the data transmission.

[0179] In Example 11, the method according to any of Examples 1 to 10 further includes the third entity being associated with a last entity for a last repetition of the data transmission.

[0180] In Example 12, the method described in any of Examples 1 to 11 also includes: wherein an identifier for the repetition configuration for SPS or CG is indicated by the base station via at least one of RRC signaling, DCI signaling or MAC-CE, and the identifier is configured to carry mergeable repetitions on different entities.

[0181] In Example 13, the method according to any of Examples 1 to 12 also includes: at least one repetition of data transmission is limited to a subset of HARQ process identifiers associated with an identifier of a configured SPS or CG indicated by the base station.

[0182] In Example 14, the method according to any of Examples 1 to 13 further includes: data transmission is included in a downlink data channel configured based on the SPS.

[0183] In Example 15, the method according to any of Examples 1 to 14 also includes: the method is performed by a base station, wherein the data transmission is included in an uplink data channel configured based on the CG.

[0184] In Example 16, the method of any of Examples 1 to 15 further includes: each repetition of at least one repetition of the data transmission is associated with a same period having a common start boundary.

[0185] In Example 17, the method of any of Examples 1 to 16 further includes receiving an indication of the common starting boundary via DCI signaling.

[0186] In Example 18, the method of any of Examples 1 to 17 further includes receiving the data transmission and at least one repetition of the data transmission within a same period.

[0187] Example 19 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 to cause the system or device to implement the method described in any of Examples 1 to 18.

[0188] Example 20 is a system or apparatus comprising means for implementing the method according to any of Examples 1 to 18 or achieving the apparatus according to any of Examples 1 to 18.

[0189] Example 21 is a non-transitory computer-readable medium storing instructions executable by one or more processors to cause the one or more processors to implement the method according to any of Examples 1 to 18.

[0190] Example 22 is a method of wireless communication, comprising: determining a repetition configuration for an SPS or CG associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity; sending the data transmission on the first entity; and sending at least one repetition of the data transmission on the second entity.

[0191] In Example 23, the method according to Example 22 further includes: the first entity and the second entity each include frequency resources.

[0192] In Example 24, the method according to any of Examples 22 or 23 further includes: the first entity and the second entity each include a cell or a component carrier.

[0193] In Example 25, the method according to any of Examples 22 to 24 also includes: data transmission includes downlink data transmission, and the method also includes: receiving a common ACK / NACK signal for the data transmission from the UE, wherein the common ACK / NACK is received using a third entity configured to send a control channel associated with the first entity.

[0194] In Example 26, the method according to any of Examples 22 to 25 further includes: the common ACK / NACK signal is associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity.

[0195] In Example 27, the method according to any of Examples 22 to 26 further includes: the bit position is based on a time distance between a repetition of the data transmission on the second entity and an uplink control channel on the third entity.

[0196] In Example 28, the method according to any of Examples 22 to 27 also includes: data transmission includes downlink data transmission, and the method also includes: receiving a common ACK / NACK signal for data transmission from the UE, wherein the common ACK / NACK is received using a third entity configured to send an uplink control channel, and the third entity is associated with the second entity.

[0197] In Example 29, the method according to any of Examples 22 to 28 further includes: the common ACK / NACK signal is associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity.

[0198] In Example 30, the method according to any of Examples 22 to 29 further includes: the bit position is based on a time distance between a repetition of the data transmission on the second entity and an uplink control channel on the third entity.

[0199] In Example 31, the method described in any of Examples 22 to 30 also includes: the time distance between sending the earliest common ACK / NACK signal and receiving the last repetition of the data transmission is greater than a distance threshold, wherein the distance threshold corresponds to the duration for combining and decoding the data transmission and at least one repetition of the data transmission.

[0200] In Example 32, the method according to any of Examples 22 to 31 further includes: the third entity is associated with a last entity of a last repetition for data transmission.

[0201] In Example 33, the method described in any of Examples 22 to 32 also includes: an identifier of a mergeable repeated SPS or CG configured to be carried on different entities is indicated by the base station via at least one of RRC signaling, DCI signaling, or MAC-CE.

[0202] In Example 34, the method according to any of Examples 22 to 33 also includes: at least one repetition of data transmission is limited to a subset of HARQ process identifiers associated with an identifier of a configured SPS or CG indicated by the base station.

[0203] In Example 35, the method according to any of Examples 22 to 34 further includes: data transmission is included in a downlink data channel configured based on the SPS.

[0204] In Example 36, the method according to any of Examples 22 to 35 also includes: the method is performed by a UE, wherein the data transmission is included in an uplink data channel configured based on the CG.

[0205] In Example 37, the method according to any of Examples 22 to 36 further includes: each repetition of at least one repetition of the data transmission is associated with the same period having a common starting boundary.

[0206] In Example 38, the method according to any of Examples 22 to 37 further includes receiving an indication of a common starting boundary via DCI signaling.

[0207] In Example 39, the method of any of Examples 22 to 38 further includes receiving the data transmission and at least one repetition of the data transmission within the same period.

[0208] Example 40 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 to enable a system or device to implement a method described in any of Examples 22 to 39.

[0209] Example 41 is a system or apparatus comprising means for implementing the method described in any of Examples 22 to 39 or achieving the apparatus described in any of Examples 22 to 39.

[0210] Example 42 is a non-transitory computer-readable medium storing instructions executable by one or more processors to cause the one or more processors to implement the method according to any of Examples 22 to 39.

Claims

1. A wireless communication method, the method comprising: determining a repetition configuration for a semi-persistent schedule (SPS) or a configured grant (CG) associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity; receiving the data transmission and the at least one repetition of the data transmission within a first period; combining the data transmission and the at least one repetition of the data transmission into a combined data transmission based on determining that a difference between a time at which a last repetition of the data transmission was received and a time at which an uplink control transmission was sent is greater than a distance threshold associated with the first period; as well as The data transmission is decoded based on the combined data transmission.

2. The method according to claim 1, wherein: The first entity and the second entity each include frequency resources.

3. The method according to claim 1, wherein: The first entity and the second entity each include a cell or a component carrier.

4. The method according to claim 1, wherein: The data transmission includes downlink data transmission, and the method further includes: generating a common acknowledgement / negative acknowledgement (ACK / NACK) signal based on decoding the data transmission; and The common ACK / NACK signal is transmitted using a third entity configured to transmit a control channel associated with the first entity.

5. The method according to claim 4, wherein: The common ACK / NACK signal is associated with a bit position in an ACK / NACK codebook carried by an uplink control channel on the third entity.

6. The method according to claim 5, wherein: The bit position is based on the difference in time between the at least one repetition of the data transmission on the second entity and the uplink control channel on the third entity.

7. The method according to claim 1, wherein: The data transmission includes downlink data transmission, and the method further includes: generating a common acknowledgement / negative acknowledgement (ACK / NACK) signal based on decoding the data transmission; and The common ACK / NACK signal is sent to a base station in an uplink control transmission using a third entity configured to send an uplink control channel, the third entity being associated with the second entity.

8. The method according to claim 7, wherein: The common ACK / NACK signal is associated with a bit position in an ACK / NACK codebook carried by the uplink control channel on the third entity.

9. The method according to claim 7, further comprising: Determining that a temporal distance between sending an earliest common ACK / NACK signal and receiving a last repetition of the data transmission is greater than the distance threshold, wherein the distance threshold corresponds to a duration for combining and decoding the data transmission and the at least one repetition of the data transmission.

10. The method according to claim 7, wherein: The third entity is associated with a last entity for a last repetition of the data transmission.

11. The method according to claim 1, wherein: An identifier for the repetition configuration of the SPS or the CG is indicated by the base station via at least one of radio resource control (RRC) signaling, downlink control information (DCI) signaling, or medium access control-control element (MAC-CE), wherein the identifier for the repetition configuration of the SPS or the CG is configured as a mergeable repetition carried on different entities.

12. The method according to claim 11, wherein: The at least one repetition of the data transmission is limited to a subset of hybrid automatic repeat request (HARQ) process identifiers associated with the identifier of the configured SPS or the CG indicated by the base station.

13. The method according to claim 11, wherein: The data transmission is included in a downlink data channel based on the SPS configuration.

14. The method according to claim 11, wherein: The method is performed by the base station, and wherein the data transmission is included in an uplink data channel configured based on the CG.

15. The method according to claim 11, wherein: Each of the at least one repetition of the data transmission is associated with the first period having a common starting boundary.

16. The method according to claim 15, further comprising: An indication of the common starting boundary is received via the DCI signaling.

17. An apparatus for wireless communication, comprising: Memory; as well as at least one processor coupled to the memory and configured to: determining a repetition configuration for a semi-persistent schedule (SPS) or a configured grant (CG) associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity; receiving the data transmission and the at least one repetition of the data transmission within a first period; as well as combining the data transmission and the at least one repetition of the data transmission into a combined data transmission based on determining that a difference between a time at which a last repetition of the data transmission was received and a time at which an uplink control transmission was sent is greater than a distance threshold associated with the first period; as well as The data transmission is decoded based on the combined data transmission.

18. A method of wireless communication, the method comprising: determining a repetition configuration for a semi-persistent schedule (SPS) or a configured grant (CG) associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity; sending the data transmission on the first entity within a first period; sending at least one repetition of the data transmission on a second entity within the first period; as well as The uplink control transmission is received based on a difference between a time at which a last repetition of the data transmission was sent and a time at which the uplink control transmission was received, the difference being greater than a distance threshold associated with the first period.

19. The method according to claim 18, wherein: The first entity and the second entity each include frequency resources.

20. The method according to claim 18, wherein: The first entity and the second entity each include a cell or a component carrier.

21. The method according to claim 18, wherein: The data transmission includes downlink data transmission, and the method further includes: A common acknowledgement / negative acknowledgement (ACK / NACK) signal is received from a user equipment (UE) for the data transmission, wherein the common ACK / NACK signal is received in the uplink control transmission using a third entity configured to transmit a control channel associated with the first entity.

22. The method according to claim 18, wherein: The data transmission includes downlink data transmission, and the method further includes: A common acknowledgement / negative acknowledgement (ACK / NACK) signal is received from a user equipment (UE) for the data transmission, wherein the common ACK / NACK signal is received in the uplink control transmission using a third entity configured to send an uplink control channel, the third entity being associated with the second entity.

23. The method according to claim 22, wherein: The receiving of the uplink control transmission comprises receiving an earliest common ACK / NACK signal, and the sending of the at least one repetition comprises sending a last repetition of the data transmission, wherein the earliest common ACK / NACK signal is received after the last repetition of the data transmission is sent a time distance greater than the distance threshold, wherein the distance threshold corresponds to a duration for combining and decoding the data transmission and the at least one repetition of the data transmission.

24. The method according to claim 22, wherein: The third entity is associated with a last entity for a last repetition of the data transmission.

25. The method of claim 18, wherein: The identifier of the SPS or the CG is indicated by the base station via at least one of radio resource control (RRC) signaling, downlink control information (DCI) signaling, or medium access control-control element (MAC-CE), wherein the identifier of the SPS or the CG is configured as a mergeable repetition carried on different entities.

26. The method according to claim 25, wherein: The at least one repetition of the data transmission is limited to a subset of hybrid automatic repeat request (HARQ) process identifiers associated with the identifier of the configured SPS or the CG indicated by the base station.

27. The method according to claim 25, wherein: The data transmission is included in a downlink data channel based on the SPS configuration.

28. The method according to claim 25, wherein: The method is performed by a user equipment (UE), and wherein the data transmission is included in an uplink data channel configured based on the CG.

29. An apparatus for wireless communication at a base station, comprising: Memory; as well as at least one processor coupled to the memory and configured to: determining a repetition configuration for a semi-persistent schedule (SPS) or a configured grant (CG) associated with a data transmission on a first entity and at least one repetition of the data transmission on a second entity; sending the data transmission on the first entity within a first period; sending at least one repetition of the data transmission on a second entity within the first period; as well as The uplink control transmission is received based on a difference between a time at which a last repetition of the data transmission was sent and a time at which the uplink control transmission was received, the difference being greater than a distance threshold associated with the first period.

Images