Handling of isolated symbols in shared spectrum

Abstract

Various aspects of the present disclosure provide techniques for handling scenarios in which a physical uplink shared channel (PUSCH) repetition is scheduled as a single symbol. According to certain aspects, a user equipment (UE) is configured to detect that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition, and take one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

Description

Technical Field

[0001] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for handling scenarios where Physical Uplink Shared Channel (PUSCH) repetitions are scheduled as a single symbol.

[0002] background

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, 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, to name just a few.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL) to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

[0006] Overview

[0007] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide advantages including improved UE performance.

[0008] Certain aspects provide a method for wireless communications by a user equipment (UE). The method generally includes detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition, and taking one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

[0009] Certain aspects provide an apparatus for wireless communications by a user equipment (UE). The apparatus generally includes a processing system configured to detect that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition, and take one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

[0010] Certain aspects provide an apparatus for wireless communications by a user equipment (UE). The apparatus generally includes means for detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition, and means for taking one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

[0011] Certain aspects provide a user equipment (UE). The UE generally includes at least one antenna and a processing system configured to detect that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition, and take one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

[0012] Certain aspects provide a computer-readable medium for wireless communications by a user equipment (UE). The computer-readable medium generally includes code executable to detect that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition, and take one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

[0013] Aspects of the present disclosure provide apparatuses, devices, processors, and computer-readable media for performing the methods described herein.

[0014] To achieve the foregoing and related ends, the one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of the one or more aspects. However, these features are only indicative of several of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The details of one or more implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. However, the accompanying drawings illustrate only some typical aspects of the present disclosure and are therefore not to be considered to limit its scope. Other features, aspects and advantages will become apparent from the description, drawings and claims.

[0017] Figure 1 An example wireless communication network is shown in which some aspects of the present disclosure may be performed.

[0018] Figure 2 Shown is a block diagram illustrating an example base station (BS) and an example user equipment (UE) according to some aspects of the present disclosure.

[0019] Figure 3A An example of a frame format for a telecommunications system is illustrated.

[0020] Figure 3B It explains how different beams can be used to send different synchronization signal blocks (SSBs).

[0021] Figures 4A-4C An example of PUSCH repetition including a single symbol that may be handled in accordance with aspects of the present disclosure is illustrated.

[0022] Figure 5

[0013] Example operations for wireless communications by a user equipment (UE) are illustrated in accordance with some aspects of the present disclosure.

[0023] Figure 6 An example of how to handle PUSCH repetitions including a single symbol in accordance with some aspects of the present disclosure is illustrated.

[0024] Fig. 6A and 6B

[0013] An example of cyclic prefix (CP) extension in accordance with aspects of the present disclosure is illustrated.

[0025] Figure 7 An example of how to handle PUSCH repetitions including a single symbol in accordance with aspects of the present disclosure is illustrated.

[0026] Figure 8 Another example of how to handle PUSCH repetitions including a single symbol in accordance with aspects of the present disclosure is illustrated.

[0027] Fig. 9A and 9B Another example of how to handle PUSCH repetitions including a single symbol in accordance with aspects of the present disclosure is illustrated.

[0028] Fig.10 Another example of how to handle PUSCH repetitions including a single symbol in accordance with aspects of the present disclosure is illustrated.

[0029] Fig.11 Some aspects of the present disclosure may include a Figure 5 The communication device of the various components of the operation explained in the figure.

[0030] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation.

[0031] Detailed Description

[0032] Aspects of the present disclosure relate to wireless communications, and more particularly to techniques for handling scenarios in which a physical uplink shared channel (PUSCH) repetition is scheduled as a single symbol. The single symbol is referred to as an orphan symbol because conventional systems omit such single-symbol transmissions. The handling may involve taking one or more actions designed to avoid losing channel access due to a transmission gap caused by the single-symbol PUSCH repetition.

[0033] The following description provides an example of how the UE handles isolated symbols, without limiting the scope, applicability or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality as a supplement to the various aspects of the present disclosure set forth herein or in addition. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims.

[0034] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, subcarrier, frequency channel, frequency modulation, subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, a 5G NR RAT network may be deployed.

[0035] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. Figure 1 As shown in FIG. 1 , UE 120a may include an isolated symbol handling module 122, which may be configured to perform (or cause UE 120a to perform) Figure 5 Operation 500.

[0036] NR access (e.g., 5G NR) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmWave) targeting high carrier frequency (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technology, or mission-critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services may coexist in the same time domain resources (e.g., time slots or subframes) or frequency domain resources (e.g., component carriers).

[0037] like Figure 1 As illustrated in , the wireless communication network 100 may include several base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively referred to as BS 110) and other network entities. BS 110 may provide communication coverage for a specific geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may be interconnected to each other or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 using any suitable transport network via various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.). Figure 1In the example shown in , BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for a pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. The BS may support one or more cells. BS 110 communicates with user equipment (UE) 120a-y (each also individually referred to herein as UE 120 or collectively referred to as UE 120) in the wireless communication network 100. UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.

[0038] The wireless communication network 100 may also include a relay station (e.g., relay station 110r) (also referred to as a relay, etc.), which receives transmissions of data or other information from an upstream station (e.g., BS110a or UE 120r) and sends transmissions of data or other information to a downstream station (e.g., UE 120 or BS110), or which relays transmissions between UEs 120 to facilitate communication between the devices.

[0039] A network controller 130 may couple to a set of BSs 110 and provide coordination and control for the BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly), for example, via a wireless or wired backhaul.

[0040] Figure 2 Shown is a block diagram illustrating an example base station (BS) and an example user equipment (UE) according to some aspects of the present disclosure.

[0041] At BS 110, a transmit processor 220 may receive data from a data source 212 and control information from a controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 220 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, or reference symbols, where applicable, and may provide output symbol streams to modulators (MODs) 232a-232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0042] At the UE 120, antennas 252a-252r may receive downlink signals from the BS 110 and may provide received signals to demodulators (DEMODs) 254a-254r in the transceiver, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0043] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by a demodulator 254a-254r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the BS 110. At the BS 110, the uplink signal from the UE 120 may be received by the antenna 234, processed by the modulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240 .

[0044] Memories 242 and 282 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0045] The controller / processor 280 or other processors and modules at the UE 120 may perform or direct the execution of processes for the techniques described herein. Figure 2 As shown, the controller / processor 280 of the UE 120 has the above-mentioned functions and can be configured to execute (or cause the UE 120 to execute) Figure 5 The isolated codeword handling module 122 of operation 500 is implemented.

[0046] Figure 3A 300 is a diagram showing an example of a frame format 300 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. An index may be assigned to the symbol period in each slot. A mini slot (which may be referred to as a subslot structure) refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

[0047] Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission, and the link direction for each subframe may be switched dynamically. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information.

[0048] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and two-symbol PBCH. The SS block can be in a fixed time slot position (such as Figure 3A ) is transmitted in the codewords 0-3 shown in . PSS and SSS can be used by UE for cell search and acquisition. PSS can provide half-frame timing, and SS can provide CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within a radio frame, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam sweeping. Further system information (such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI)) can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes. SS blocks can be transmitted up to 64 times, for example, for mmW, up to 64 different beam directions are used to transmit. Up to 64 transmissions of SS blocks are called SS burst sets. SS blocks in SS burst sets are transmitted in the same frequency region, while SS blocks in different SS burst sets can be transmitted at different frequency positions.

[0049] like Figure 3B As shown in , SS blocks can be organized into SS burst sets to support beam sweeping. As shown, each SSB in a burst set can be transmitted using a different beam, which can help the UE quickly acquire both transmit (Tx) and receive (Rx) beams (especially for mmW applications). The physical cell identity (PCI) can still be decoded from the PSS and SSS of the SSB.

[0050] A control resource set (CORESET) for a system (such as an NR and LTE system) may include one or more control resource (e.g., time and frequency resource) sets configured within the system bandwidth for communicating PDCCH. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. According to various aspects of the present disclosure, a CORESET is a time-frequency domain resource set defined in units of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) of frequency tones in a symbol period (e.g., a symbol period of a time slot), where one frequency tone in one symbol period is referred to as a resource element (RE). A fixed number of REGs may be included in a control channel element (CCE). A CCE set may be used to transmit a new radio PDCCH (NR-PDCCH), where different numbers of CCEs in the set are used to transmit NR-PDCCH using different aggregation levels. Multiple CCE sets may be defined as a search space for a UE, and thereby a Node B or other base station may transmit the NR-PDCCH to the UE by transmitting the NR-PDCCH in a CCE set that is a decoding candidate within the search space defined as the UE, and the UE may receive the NR-PDCCH by searching in the search space for the UE and decoding the NR-PDCCH transmitted by the Node B.

[0051] Example of orphan symbol handling in shared spectrum

[0052] Aspects of the present disclosure provide techniques for a UE to handle scenarios where Physical Uplink Shared Channel (PUSCH) repetitions are scheduled as single symbols (orphan symbols) on a shared spectrum.

[0053] Shared spectrum in this context may include unlicensed and licensed bands over which there is a medium access sharing mechanism, such as a listen-before-talk (LBT) mechanism. The handling may involve taking one or more actions designed to avoid losing channel access due to a transmission gap caused by the orphan symbol.

[0054] Various aspects of the present disclosure may be used to provide uplink enhancement in certain systems, such as New Radio Unlicensed (NR-U) utilizing such shared spectrum to provide uplink enhancement. For example, various aspects of the present disclosure may be used to help UE maintain access to the shared medium for certain types of traffic (such as URLLC), and may help support UE-initiated channel occupation time COT for frame-based equipment (FBE) operation mode.

[0055] Such applications can improve the reliability of the Physical Uplink Shared Channel (PUSCH) by using repetition. According to one type of repetition (referred to as Type B), the UE is configured to transmit K nominal repetitions of the PUSCH, each with a nominal length (number of symbols) L and each immediately following the start symbol S, where S and L are given by a parameter called the Start Length and Indicator Vector (SLIV). The SLIV is typically indicated by a row index in the Time Domain Resource Allocation (TDRA) signaled in the Downlink Control Information (DCI) for the scheduled PUSCH.

[0056] K repetitions may be referred to as nominal because the actual number of repetitions may be different depending on the available resource configuration. For example, based on parameters K, L, and S, the UE may determine that a certain number of symbols are not available for PUSCH repetitions. These invalid symbols may be determined based on predefined rules or RRC configurations.

[0057] After determining the invalid symbol(s) for PUSCH repetition type B transmission for each of the K nominal repetitions, the remaining symbols are considered as potentially valid symbols for PUSCH repetition type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is greater than zero for a nominal repetition, then the nominal repetition may be segmented into one or more actual repetitions, where each actual repetition may be a contiguous set of one or more potentially valid symbols that may be used for PUSCH repetition type B transmission in a slot. In conventional systems, such single-symbol PUSCH repetitions are not transmitted.

[0058] Figures 4A-4C An example scenario resulting in single-symbol PUSCH repetition is illustrated.

[0059] exist Figure 4A In the example shown in , the repetition parameters (K=4, S=5 and L=4) and the subframe configuration result in one nominal repetition (nominal repetition #2) being split into two actual repetitions (actual repetitions #2 and #3) because the nominal repetition spans the time slot boundary. As shown, in a conventional system, actual repetition #2 would be omitted because it is a single symbol.

[0060] exist Figure 4B In the example shown in , the repetition parameters (K=4, S=6 and L=4) and subframe configuration again result in one nominal repetition (nominal repetition #2) being segmented into a single-symbol actual repetition (actual repetition #2), in this case due to a collision with a semi-static downlink symbol. As shown, in a conventional system, actual repetition #2 would be omitted because it is a single symbol.

[0061] exist Figure 4CIn the example shown in , the repetition parameters (K=4, S=10 and L=4) and subframe configuration again result in one nominal repetition (nominal repetition #2) being segmented into a single-symbol actual repetition (actual repetition #1), in this case due to an invalid symbol configured by RRC. As shown, in a conventional system, actual repetition #1 would be omitted because it is a single symbol.

[0062] As shown by the above example, in some scenarios for type B PUSCH repetition, due to segmentation, the actual PUSCH repetition may include a single symbol. In typical systems and applications (e.g., Rel. 16 URLLC), the decision is not to transmit actual repetitions with a single symbol (isolated symbol) because there is usually no one-symbol PUSCH format to support a single symbol.

[0063] Unfortunately, in shared spectrum systems such as NR-U, leaving a one-symbol gap may result in channel loss for the UE. Aspects of the present disclosure provide techniques for the UE to handle this scenario where PUSCH repetitions are scheduled as a single symbol (isolated symbol).

[0064] Figure 5 Example operations 500 for wireless communication by a UE are illustrated. For example, operations 500 may be performed according to aspects of the present disclosure by Figure 1 or Figure 2 The UE 120 performs to handle isolated codewords.

[0065] Operations 500 begin at 502 by detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition. At 504, the UE takes one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition.

[0066] In some cases, if there is an actual repetition transmitted after an isolated symbol (e.g., a single symbol actual repetition), the UE may use the CP extension from the next actual repetition to fill the one-symbol gap (corresponding to the isolated symbol). This CP extension approach may be applicable, for example, to a situation where the UE is transmitting (e.g., PUSCH repetition) before a 1-symbol segment.

[0067] Figure 6 An example timeline 600 illustrating how CP extension 602 can be used to handle orphan symbols is illustrated. In the illustrated example, repetition parameters (K=4, S=5, L=4) and subframe configuration are similar to Figure 4AThe example of is the same. Thus, due to the split across the time slot boundary, the actual repetition #2 is a single codeword. As illustrated, the UE can apply the CP extension of the first OFDM codeword of the next actual repetition (actual repetition #3) to fill the one-codeword gap.

[0068] As illustrated, according to the first option (labeled as Option 1.1), the length of the CP extension may be the symbol length:

[0069]

[0070] Where μ is the subcarrier spacing (SCS) of the uplink (UL) bandwidth part (BWP), and l is the first OFDM symbol index of the next actual repetition after the orphan symbol. In some cases, an enhanced receiver can take advantage of this CP extension to obtain better LLRs or better channel estimates. According to the second option (labeled as option 1.2), the CP extension can be less than a full symbol period (small Δ value). In this case, the length of the CP extension can be:

[0071]

[0072] (to ensure that the gap is no larger than 16us), again, where μ is the subcarrier spacing (SCS) of the uplink (UL) bandwidth part (BWP), and l is the first OFDM symbol index of the next actual repetition after the isolated symbol.

[0073] and

[0074]

[0075] Fig. 6A and 6B Examples of CP extension lengths for different SCSs for a normal CP according to the first and second options are explained respectively.

[0076] In some cases, the UE may discard (not transmit) the single-symbol PUSCH repetition if there is no actual repetition transmitted after the orphan symbol.

[0077] Figure 7 An example timeline 700 of such a solution is illustrated. Figure 7In the example shown in , the repetition parameters (K=2, S=7 and L=4) and subframe configuration again result in one nominal repetition (nominal repetition #2) being segmented into a single symbol actual repetition 702. In this case, the orphan symbol can be discarded since it can not be considered a gap if there is no transmission after it. If the one symbol is at the end of the burst (as in this example), then since both the gNB and the UE know this, the gNB can schedule the next transmission accordingly taking into account the cancellation of the symbol. This approach can be used to solve the problem caused by Figures 4A-4C Single-symbol PUSCH repetition caused by any of the examples shown in .

[0078] In some cases, if there are orphan symbols, the UE may treat this configuration as an error situation (e.g., and not transmit any repetitions or one or more of these repetitions). Such situations can be addressed by scheduling, e.g., by the gNB avoiding parameter settings that lead to orphan symbols.

[0079] For example, resulting in Figure 8 The isolated code element 802 of the parameter setting (K=4, S=5, L=4) shown in the example timeline 800 of (A) can be avoided by setting different parameters. Figure 8 As shown in the example timeline 810 of (B) in FIG. 1 , the nominal repetition #2 is shifted using new parameters (K=4, S=6, and L=4) that shift the starting symbol by one symbol in time so that it is no longer split across a slot boundary, effectively removing orphan symbols. This approach can be used to address the problem caused by Figures 4A-4C Single-symbol PUSCH repetition caused by any of the examples shown in .

[0080] In some cases, if there is a DL or invalid symbol in the middle of a Type B PUSCH repetition, the UE may regard such a situation as an error situation so that in an unlicensed band, the UE does not expect to receive a Type B PUSCH repetition configuration including a DL or invalid symbol in the middle. Fig. 9A An example timeline 900 of such a scenario with repetition parameters (K=4, S=6, and L=4) and subframe configuration resulting in orphaned symbols 902 due to collisions with (invalid) downlink symbols is illustrated. Fig. 9B An example timeline 910 of another such scenario with repetition parameters (K=4, S=10, and L=4) and subframe configurations resulting in orphaned symbols 912 due to invalid symbols configured by RRC is illustrated. The UE may consider each of these scenarios as an error case. As such, the gNB should avoid scheduling with such parameters and subframe configurations. This approach may be used to address the issue caused by Figure 4B-4C Single-symbol PUSCH repetition caused by any of the examples shown in .

[0081] In some cases, if there are DL and / or invalid symbols in the middle of a Type B PUSCH repetition, the UE may take action to maintain channel access.

[0082] For example, Fig.10 As illustrated in the example timeline 1000 of FIG. 1000 , with repetition parameters (K=8, S=6, and L=4) and subframe configurations that result in orphaned symbols 1012 due to collisions with DL symbols, the UE may attempt to start transmission using a channel access procedure (such as type 1 uplink channel access known as Category 4 (Cat 4) Listen Before Talk (LBT)) at each repetition boundary. In some cases, the UE may discard orphaned symbols at the beginning (single symbol actual repetition #2). In some cases, after the transmission has been started, the UE may effectively propose a CP extension (see above for details). Figure 6 The method can be used to solve the problem of single code element actual repetition in the middle. Figure 4B-4C Single-symbol PUSCH repetition caused by any of the examples shown in .

[0083] Fig.11 The description may include operations configured to perform the techniques disclosed herein (such as, Figure 5 For example, the communication device 1100 may be a UE 120, such as Figure 1 or Figure 2 . The communication device 1100 includes a processing system 1102 coupled to a transceiver 1108. The transceiver 1108 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1100 via an antenna 1110. The processing system 1102 can be configured to perform processing functions for the communication device 1100, including processing signals received and / or to be transmitted by the communication device 1100.

[0084] The processing system 1102 includes a processor 1104 coupled to a computer readable medium / memory 1112 via a bus 1106. In some aspects, the computer readable medium / memory 1112 is configured to store a program that, when executed by the processor 1104, causes the processor 1104 to execute Figure 51104 includes: a circuit system 1120 for detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; and a circuit system 1122 for taking one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition. In some aspects, the processor 1104 has a circuit system configured to implement the code stored in the computer-readable medium / memory 1112. The processor 1104 includes: a circuit system 1120 for detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; and a circuit system 1122 for taking one or more actions to handle a symbol-length gap in transmission caused by the single-symbol actual PUSCH repetition. Circuitry 1120 and / or 1122 may be circuitry specifically designed to perform designated functions or may be general purpose circuitry that is configured or programmed to perform these functions.

[0085] Additional considerations

[0086] The techniques described herein may be used for various wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). NR is an emerging wireless communication technology under development.

[0087] The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms commonly associated with 3G, 4G or 5G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations.

[0088] In 3GPP, the term "cell" may refer to the coverage area of ​​a B node (NB) or a NB subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and BS, next-generation B node (gNB or g B node), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. The BS may provide communication coverage for macro cells, pico cells, femto cells, or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS.

[0089] UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), transportation component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0090] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 RBs), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0091] NR can utilize OFDM with CP on the uplink and downlink and includes support for half-duplex operation using TDD. In NR, a subframe is still 1ms, but the basic TTI is called a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16...time slots), depending on the subcarrier spacing. NR RB is 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and time slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. In some examples, the MIMO configuration in the DL can support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. In some examples, multi-layer transmission of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.

[0092] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communication between some or all devices and equipment within its service area or cell. A scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may act as a scheduling entity, and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs may utilize resources scheduled by the UE for wireless communication. In some examples, a UE may act as a scheduling entity in a peer-to-peer (P2P) network or in a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.

[0093] As used herein, the term "determining" may encompass one or more of a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), assuming, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0094] As used herein, "or" is intended to be interpreted in an inclusive sense unless otherwise expressly indicated. For example, "a or b" may include only a, only b, or a combination of a and b. As used herein, a phrase citing "at least one of" or "one or more of" a list of items refers to any combination of these items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0095] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to ordinary technicians in the art and are explicitly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Any element of the claim should not be interpreted under the provisions of 35 U.S.C. § 112 (f), unless the element is explicitly stated using the phrase "device for..." or in the case of a method claim, the element is stated using the phrase "step for...".

[0096] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the figures, these operations may have corresponding paired device-plus-function components with similar numbers. For example, Figure 2 The processors 258, 264, and 266 of the UE 120 and / or the controller / processor 280, and / or the processors 220, 230, 238, and / or the controller / processor 240 of the BS 110 shown in FIG. 1 may be configured to perform Figure 5 Operation 500.

[0097] The means for receiving may include Figure 2 The transceiver, receiver or at least one antenna and at least one receiving processor described in the embodiment. The device for transmitting, the device for sending or the device for outputting may include Figure 2 The transceiver, transmitter or at least one antenna and at least one transmit processor as described in the foregoing. The means for detecting and the means for taking one or more actions may include a processing system, which may include one or more processors, such as Figure 2 1 and 2. Processors 258, 264, and 266 of UE 120 and / or controller / processor 280 and / or processors 220, 230, 238 and / or controller / processor 240 of BS 110 are shown in FIG.

[0098] In some cases, a device may not actually transmit a frame, but may have an interface (means for outputting) for outputting a frame for transmission. For example, a processor may output a frame to a radio frequency (RF) front end via a bus interface for transmission. Similarly, a device may not actually receive a frame, but may have an interface (means for obtaining) for obtaining a frame received from another device. For example, a processor may obtain (or receive) a frame from an RF front end via a bus interface for reception.

[0099] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0100] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application of the processing system and the overall design constraints, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the UE 120 (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall network or system.

[0101] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be implemented in a computer program product.

[0102] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, between different programs, and across multiple storage media. A computer-readable medium may include multiple software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a reception module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0103] Likewise, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0104] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein, such as for performing the operations described herein and in Figure 5 Instructions for the operations explained in .

[0105] In addition, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0106] It will be understood that the claims are not limited to the precise configurations and components illustrated above. Various changes, substitutions, and variations may be made in the layout, operation, and details of the methods and apparatus described above without departing from the scope of the claims. Thus, the claims are not intended to be limited to the implementations shown herein, but rather should be granted the widest scope consistent with the present disclosure, the principles disclosed herein, and the novel features.

[0107] In addition, various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable subcombination. Thus, while features may be described above as functioning in a particular combination and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to a subcombination, or a variation of a subcombination.

[0108] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or to perform all the illustrated operations to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart or a flow diagram. However, other operations that are not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, simultaneously or between any illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the implementation described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; as well as taking one or more actions to handle a symbol length gap in transmission caused by the single symbol actual PUSCH repetition, The one or more actions include: The symbol length gap is filled after the single-symbol actual PUSCH repetition using a cyclic prefix (CP) extension of a first symbol from a next actual PUSCH repetition.

2. The method of claim 1, wherein the length of the CP extension is a single symbol duration.

3. The method of claim 1, wherein the length of the CP extension occupies less than one symbol duration and is equal to or greater than the symbol duration minus a Δ value, wherein the Δ value is the maximum value of the remaining gap after the CP extension is used to fill the symbol length gap.

4. The method of claim 1, wherein the one or more actions include: In case no actual PUSCH repetition is scheduled after the single-symbol actual PUSCH repetition, the single-symbol actual PUSCH repetition is discarded.

5. The method of claim 1, wherein the one or more actions include: The detection of the single-symbol actual PUSCH repetition is considered as an error case.

6. The method of claim 1, further comprising: detecting a semi-static downlink symbol or an invalid symbol configured by a radio resource control (RRC) in the middle of the one or more actual PUSCH repetitions, wherein: The one or more actions include treating as an error condition the detection of the semi-static downlink symbol or the radio resource control (RRC) configured invalid symbol in the middle of the one or more actual PUSCH repetitions.

7. The method of claim 1, wherein the one or more actions are taken based at least in part on how the single-symbol actual PUSCH repetition is detected.

8. The method of claim 7, wherein a different one of the one or more actions is taken depending on whether the nominal PUSCH repetition is detected due to: The nominal PUSCH repetition spans across time slot boundaries; The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlap with invalid symbols configured by Radio Resource Control (RRC).

9. The method of claim 1, wherein the one or more actions include: Resuming the transmission using uplink channel procedures at a boundary of each actual PUSCH repetition of the one or more actual PUSCH repetitions in a case where the nominal PUSCH repetition is detected due to: The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlap with invalid symbols configured by Radio Resource Control (RRC).

10. The method of claim 9, wherein the one or more actions further comprise: The single-symbol actual PUSCH repetition is discarded immediately after the semi-static downlink symbol or the radio resource control (RRC) configured invalid symbol.

11. An apparatus for wireless communication, comprising: A processing system, the processing system being configured to: detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; as well as taking one or more actions to handle a symbol length gap in transmission caused by the single symbol actual PUSCH repetition, The one or more actions include: The symbol length gap is filled after the single-symbol actual PUSCH repetition using a cyclic prefix (CP) extension of a first symbol from a next actual PUSCH repetition.

12. The apparatus of claim 11, wherein the length of the CP extension is a single symbol duration.

13. The apparatus of claim 11, wherein the length of the CP extension occupies less than a symbol duration and is equal to or greater than the symbol duration minus a Δ value, wherein the Δ value is a maximum value of a remaining gap after the CP extension is used to fill the symbol length gap.

14. The apparatus of claim 11, wherein the one or more actions include: In case no actual PUSCH repetition is scheduled after the single-symbol actual PUSCH repetition, the single-symbol actual PUSCH repetition is discarded.

15. The apparatus of claim 11, wherein the one or more actions include: The detection of the single-symbol actual PUSCH repetition is considered as an error case.

16. The apparatus of claim 11, further comprising: detecting a semi-static downlink symbol or an invalid symbol configured by a radio resource control (RRC) in the middle of the one or more actual PUSCH repetitions, wherein: The one or more actions include treating as an error condition the detection of the semi-static downlink symbol or the radio resource control (RRC) configured invalid symbol in the middle of the one or more actual PUSCH repetitions.

17. The apparatus of claim 11, wherein the one or more actions are taken based at least in part on how the single-symbol actual PUSCH repetition is detected.

18. The apparatus of claim 17, wherein a different one of the one or more actions is taken depending on whether the nominal PUSCH repetition is detected due to: The nominal PUSCH repetition spans across time slot boundaries; The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlap with invalid symbols configured by Radio Resource Control (RRC).

19. The apparatus of claim 11, wherein the one or more actions comprise resuming the transmission using an uplink channel procedure at a boundary of each of the one or more actual PUSCH repetitions if the nominal PUSCH repetition is detected due to: The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlap with invalid symbols configured by Radio Resource Control (RRC).

20. The apparatus of claim 19, wherein the one or more actions further comprise: The single-symbol actual PUSCH repetition is discarded immediately after the semi-static downlink symbol or the radio resource control (RRC) configured invalid symbol.

21. A device for wireless communication, comprising: means for detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; as well as means for taking one or more actions to handle a symbol length gap in transmission caused by said single symbol actual PUSCH repetition, The one or more actions include: The symbol length gap is filled after the single-symbol actual PUSCH repetition using a cyclic prefix (CP) extension of a first symbol from a next actual PUSCH repetition.

22. The apparatus of claim 21, wherein the length of the CP extension is a single symbol duration.

23. The apparatus of claim 21, wherein the length of the CP extension occupies less than a symbol duration and is equal to or greater than the symbol duration minus a Δ value, wherein the Δ value is a maximum value of a remaining gap after the CP extension is used to fill the symbol length gap.

24. The apparatus of claim 21, wherein the one or more actions include: In case no actual PUSCH repetition is scheduled after the single-symbol actual PUSCH repetition, the single-symbol actual PUSCH repetition is discarded.

25. The apparatus of claim 21, wherein the one or more actions include: The detection of the single-symbol actual PUSCH repetition is considered as an error case.

26. The apparatus of claim 21, further comprising: means for detecting a semi-static downlink symbol or an invalid symbol configured by a radio resource control (RRC) in the middle of the one or more actual PUSCH repetitions, wherein: The one or more actions include treating as an error condition the detection of the semi-static downlink symbol or the radio resource control (RRC) configured invalid symbol in the middle of the one or more actual PUSCH repetitions.

27. The apparatus of claim 21, wherein the one or more actions are taken based at least in part on how the single-symbol actual PUSCH repetition is detected.

28. The apparatus of claim 27, wherein a different one of the one or more actions is taken depending on whether the nominal PUSCH repetition is detected due to: The nominal PUSCH repetition spans across time slot boundaries; The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlap with invalid symbols configured by Radio Resource Control (RRC).

29. The apparatus of claim 21, wherein the one or more actions comprise resuming the transmission using an uplink channel procedure at a boundary of each of the one or more actual PUSCH repetitions if the nominal PUSCH repetition is detected due to: The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlap with invalid symbols configured by Radio Resource Control (RRC).

30. The apparatus of claim 29, wherein the one or more actions further comprise: The single-symbol actual PUSCH repetition is discarded immediately after the semi-static downlink symbol or the radio resource control (RRC) configured invalid symbol.

31. A user equipment (UE), comprising: at least one antenna; as well as A processing system, the processing system being configured to: detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; and taking one or more actions to handle a symbol length gap in transmission caused by the single symbol actual PUSCH repetition via the at least one antenna, The one or more actions include: The symbol length gap is filled after the single-symbol actual PUSCH repetition using a cyclic prefix (CP) extension of a first symbol from a next actual PUSCH repetition.

32. A computer-readable storage medium for wireless communications by a user equipment (UE), the computer-readable storage medium comprising code executable to: detecting that a nominal physical uplink shared channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions including a single-symbol actual PUSCH repetition; and taking one or more actions to handle a symbol length gap in transmission caused by the single symbol actual PUSCH repetition, The one or more actions include: The symbol length gap is filled after the single-symbol actual PUSCH repetition using a cyclic prefix (CP) extension of a first symbol from a next actual PUSCH repetition.

Images