CN116326017A

CN116326017A - Treatment of isolated symbols in shared spectrum

Info

Publication number: CN116326017A
Application number: CN202080103991.XA
Authority: CN
Inventors: 郭少珍; J·孙; 许昌龙; 张晓霞; R·帕卡什; 徐皓
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2020-08-19
Filing date: 2020-08-19
Publication date: 2023-06-23
Also published as: US20230262689A1; EP4201129A4; WO2022036579A1; EP4201129A1

Abstract

Aspects of the present disclosure provide techniques for handling scenarios in which Physical Uplink Shared Channel (PUSCH) repetition is scheduled as a single symbol. According to certain aspects, a User Equipment (UE) is configured to: detecting 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 symbol length gaps in the transmission due to the single symbol actual PUSCH repetition.

Description

Treatment of isolated symbols in shared spectrum

Technical Field

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for handling scenarios in which Physical Uplink Shared Channel (PUSCH) repetition is scheduled as a single symbol.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, and so on. These wireless communication systems may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include third generation partnership project (3 GPP) Long Term Evolution (LTE) systems, LTE-A advanced 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 a few.

These multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. New radios (e.g., 5G NR) are examples of emerging telecommunication standards. NR is an enhanced set of LTE mobile standards promulgated by 3 GPP. 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 spectral efficiency, reduce cost, improve service, utilize new spectrum, and integrate better with other open standards. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

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

SUMMARY

The systems, methods, and devices of the present disclosure each have several aspects, not only any single aspect of which is responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "detailed description" one will understand how the features of this disclosure provide advantages that include improved UE performance.

Certain aspects provide a method for wireless communication by a User Equipment (UE). The method generally includes: detecting 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 symbol length gaps in the transmission due to the single symbol actual PUSCH repetition.

Certain aspects provide an apparatus for wireless communication by a User Equipment (UE). The apparatus generally includes a processing system configured to: detecting 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 symbol length gaps in the transmission due to the single symbol actual PUSCH repetition.

Certain aspects provide an apparatus for wireless communication 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 a transmission due to the single symbol actual PUSCH repetition.

Certain aspects provide a User Equipment (UE). The UE generally includes at least one antenna and a processing system configured to: detecting 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 symbol length gaps in the transmission due to the single symbol actual PUSCH repetition.

Certain aspects provide a computer-readable medium for wireless communication by a User Equipment (UE). The computer-readable medium generally includes code executable to: detecting 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 symbol length gaps in the transmission due to the single symbol actual PUSCH repetition.

Aspects of the present disclosure provide apparatus, devices, processors, and computer readable media for performing the methods described herein.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

Brief Description of Drawings

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

Fig. 1 illustrates an example wireless communication network in which some aspects of the present disclosure may be implemented.

Fig. 2 illustrates a block diagram that is known to an example Base Station (BS) and an example User Equipment (UE) in accordance with some aspects of the present disclosure.

Fig. 3A illustrates an example of a frame format for a telecommunications system.

Fig. 3B illustrates how different Synchronization Signal Blocks (SSBs) may be transmitted using different beams.

Fig. 4A-4C illustrate examples of PUSCH repetition including a single symbol that may be handled in accordance with aspects of the present disclosure.

Fig. 5 illustrates example operations for wireless communication by a User Equipment (UE) in accordance with some aspects of the present disclosure.

Fig. 6 illustrates an example of how PUSCH repetition including a single symbol is handled in accordance with some aspects of the present disclosure.

Fig. 6A and 6B illustrate examples of Cyclic Prefix (CP) extension in accordance with aspects of the present disclosure.

Fig. 7 illustrates an example of how PUSCH repetition including a single symbol is handled in accordance with aspects of the present disclosure.

Fig. 8A and 8B illustrate another example of how PUSCH repetition including a single symbol is handled in accordance with aspects of the present disclosure.

Fig. 9A and 9B illustrate another example of how PUSCH repetition including a single symbol is handled in accordance with aspects of the present disclosure.

Fig. 10 illustrates another example of how PUSCH repetition including a single symbol is handled in accordance with aspects of the present disclosure.

Fig. 11 illustrates a communication device that may include various components configured to perform the operations illustrated in fig. 5, in accordance with certain aspects of the present disclosure.

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 on other aspects without specific recitation.

Detailed Description

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for handling scenarios in which Physical Uplink Shared Channel (PUSCH) repetition is scheduled as a single symbol. This single symbol is referred to as an isolated 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 transmission gaps caused by the single symbol PUSCH repetition.

The following description provides examples of how a UE handles orphan symbols, but does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Moreover, features described with reference to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using such structure, functionality, or both as a complement to, or in addition to, the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular Radio Access Technology (RAT) and may operate on one or more frequencies. RATs may also be referred to as radio technologies, air interfaces, etc. Frequencies may also be referred to as carriers, subcarriers, frequency channels, tones, subbands, and so on. Each frequency may support a single RAT in a given geographical area in order to avoid interference between wireless networks of different RATs. In some cases, a 5G NR RAT network may be deployed.

Fig. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be implemented. For example, as shown in fig. 1, UE 120a may include an orphan symbol handling module 122 that may be configured to perform (or cause UE 120a to perform) operation 500 of fig. 5.

NR access (e.g., 5G NR) may support various wireless communication services, such as enhanced mobile broadband (emmbb) targeting a wide bandwidth (e.g., 80MHz or higher), millimeter wave (mmWave) targeting a high carrier frequency (e.g., 25GHz or higher), large-scale machine type communication MTC (mctc) 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. Further, these services may coexist in the same time domain resource (e.g., time slot or subframe) or frequency domain resource (e.g., component carrier).

As illustrated in fig. 1, the wireless communication network 100 may include several Base Stations (BSs) 110a-z (each also individually referred to herein as a BS110 or collectively referred to as a BS 110) and other network entities. BS110 may provide communication coverage for a particular geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of mobile BS 110. In some examples, BS110 may interconnect with each other or to one or more other BSs or network nodes (not shown) in wireless communication network 100 through various types of backhaul interfaces (e.g., direct physical connection, wireless connection, virtual network, etc.) using any suitable transport network. In the example shown in fig. 1,

BSs

110a, 110b, and 110c may be macro BSs for

macro cells

102a, 102b, and 102c, respectively. BS110 x may be a pico BS for pico cell 102 x.

BSs

110y and 110z may be femto BSs for

femtocells

102y and 102z, respectively. The BS may support one or more cells. BS110 communicates with User Equipments (UEs) 120a-y (each also individually referred to herein as UE 120 or collectively referred to as UE 120) in wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communication network 100, and each UE 120 may be stationary or mobile.

The wireless communication network 100 may also include relay stations (e.g., relay station 110 r) (also referred to as relays, etc.) that receive transmissions of data or other information from upstream stations (e.g., BS 110a or UE 120 r) and send transmissions of data or other information to downstream stations (e.g., UE 120 or BS 110), or which relay transmissions between UEs 120 to facilitate communications between devices.

Network controller 130 may be coupled to a set of BSs 110 and provide coordination and control of these BSs 110. Network controller 130 may communicate with BS 110 via a backhaul. BS 110 may also communicate with each other (e.g., directly or indirectly) via a wireless or wired backhaul, for example.

At BS 110, transmit processor 220 may receive data from data source 212 and control information from controller/processor 240. The control information may be used 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), and the like. The data may be used for a Physical Downlink Shared Channel (PDSCH) or the like. Processor 220 may process (e.g., encode and symbol map) the data and 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 the data symbols, the control symbols, or the reference symbols, if 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.

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

On the uplink, at UE 120, a 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 a reference signal, e.g., a Sounding Reference Signal (SRS). The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by demodulators 254a-254r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to BS 110. At BS 110, uplink signals from UE 120 may be received by antennas 234, processed by modulators 232, detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240.

Memories

242 and 282 may store data and program codes for BS 110 and UE 120, respectively. The scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

Controller/processor 280 or other processors and modules at UE 120 may perform or direct the execution of processes for the techniques described herein. As shown in fig. 2, controller/processor 280 of UE 120 has an orphan symbol handling module 122 as mentioned above that may be configured to perform (or cause UE 120 to perform) operation 500 of fig. 5.

Fig. 3A 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 partitioned 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 through 9, each subframe being 1ms. 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 for the symbol period in each slot. Mini-slots (which may be referred to as sub-slot structures) refer to transmission time intervals having a duration (e.g., 2, 3, or 4 symbols) that is less than a slot.

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 dynamically switched. The link direction may be based on slot format. Each slot may include DL/UL data and DL/UL control information.

In NR, a Synchronization Signal (SS) block is transmitted. The SS block includes PSS, SSs and two symbol PBCH. The SS blocks may be transmitted in fixed slot positions, such as symbols 0-3 shown in fig. 3A. PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half frame timing and the SS may provide CP length and frame timing. PSS and SSS may provide cell identity. The PBCH carries some basic system information such as downlink system bandwidth, timing information within the radio frame, SS burst set periodicity, system frame number, etc. SS blocks may be organized into SS bursts to support beam sweep. Further system information, such as Remaining Minimum System Information (RMSI), system Information Blocks (SIBs), other System Information (OSI), may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes. The SS blocks may be transmitted up to 64 times, e.g., up to 64 different beam directions for mmW. Up to 64 transmissions of an SS block are referred to as SS burst sets. SS blocks in SS burst sets are transmitted in the same frequency region, while SS blocks in different SS burst sets may be transmitted at different frequency locations.

As shown in fig. 3B, SS blocks may be organized into SS burst sets to support beam sweep. As shown, each SSB within a burst set may be transmitted using a different beam, which may 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.

A set of control resources (CORESET) for systems such as NR and LTE systems may include one or more sets of control resources (e.g., time and frequency resources) within a system bandwidth configured to convey PDCCH. Within each CORESET, one or more search spaces (e.g., a Common Search Space (CSS), a UE-specific search space (USS), etc.) may be defined for a given UE. In accordance with aspects of the present disclosure, CORESET is a set of time-frequency domain resources defined in units of Resource Element Groups (REGs). Each REG may include a fixed number (e.g., twelve) of tones in one symbol period (e.g., a symbol period of a slot), with one tone in one symbol period being referred to as a Resource Element (RE). A fixed number of REGs may be included in a Control Channel Element (CCE). A set of CCEs 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. The plurality of CCE sets may be defined as a search space for a UE, and thus a node B or other base station may transmit an NR-PDCCH to the UE by transmitting the NR-PDCCH in a set of CCEs defined as decoding candidates within the search space for 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.

Example orphan symbol handling in shared spectrum

Aspects of the present disclosure provide techniques for a UE to handle a scenario in which Physical Uplink Shared Channel (PUSCH) repetition is scheduled as a single symbol (an orphan symbol) on a shared spectrum.

Shared spectrum in this context may include unlicensed and licensed bands on 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 transmission gaps caused by the orphan symbols.

Aspects of the present disclosure may be used to provide uplink enhancements in certain systems, such as new radio unlicensed (NR-U) utilizing such shared spectrum to provide uplink enhancements. For example, aspects of the present disclosure may be used to help a UE maintain access to a shared medium for certain types of traffic, such as URLLC, and may help support UE-initiated channel occupancy time COT for frame-based equipment (FBE) modes of operation.

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

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

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 potential valid symbols for PUSCH repetition type B transmission is greater than zero for a nominal repetition, the nominal repetition may be segmented into one or more actual repetitions, where each actual repetition may be a coherent set of one or more potential valid symbols available for PUSCH repetition type B transmission within a slot. In conventional systems, such single symbol PUSCH repetition is not transmitted.

Fig. 4A-4C illustrate an example scenario resulting in single symbol PUSCH repetition.

In the example shown in fig. 4A, the repetition parameters (k=4, s=5, and l=4) and 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 slot boundary. As shown, in the conventional system, the actual repetition #2 will be omitted because it is a single symbol.

In the example shown in fig. 4B, 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 single symbol actual repetitions (actual repetition # 2), in this case due to collisions with semi-static downlink symbols. As shown, in the conventional system, the actual repetition #2 will be omitted because it is a single symbol.

In the example shown in fig. 4C, 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 single symbol actual repetitions (actual repetition # 1), in this case due to the invalid symbols of the RRC configuration. As shown, in the conventional system, the actual repetition #1 will be omitted because it is a single symbol.

As demonstrated by the above examples, in some scenarios for type B PUSCH repetition, it is possible for an actual PUSCH repetition to include a single symbol due to segmentation. In typical systems and applications (e.g., rel.16urllc), the decision is that no actual repetition with a single symbol (an orphan symbol) will be transmitted, as there is typically no one symbol PUSCH format to support a single symbol.

Unfortunately, in shared spectrum systems such as NR-U, leaving a one symbol gap may result in a channel loss for the UE. Aspects of the present disclosure provide techniques for a UE to handle this scenario in which PUSCH repetition is scheduled as a single symbol (an orphan symbol).

Fig. 5 illustrates example operations 500 for wireless communication by a UE. For example, operation 500 may be performed by UE 120 of fig. 1 or 2 to handle orphan symbols in accordance with aspects of the disclosure.

Operation 500 begins at 502 with detecting one or more actual Physical Uplink Shared Channel (PUSCH) repetitions to be segmented into including single symbol actual PUSCH repetitions. At 504, the UE takes one or more actions to handle symbol length gaps in the transmission due to the single symbol actual PUSCH repetition.

In some cases, if there is an actual repetition transmitted after an isolated symbol (e.g., a single symbol actual repetition), the UE may fill the one symbol gap (corresponding to the isolated symbol) with a CP extension from the next actual repetition. The CP extension approach may be applicable, for example, to a situation in which the UE is transmitting (e.g., PUSCH repetition) before 1 symbol segmentation.

Fig. 6 illustrates an example timeline 600 illustrating how CP extension 602 may be used to handle isolated symbols. In the illustrated example, the repetition parameters (k=4, s= 5,L =4) and subframe configuration are the same as the example of fig. 4A. Thus, the actual repetition #2 is a single symbol due to the split across slot boundaries. As illustrated, the UE may apply the CP extension of the first OFDM symbol of the next actual repetition (actual repetition # 3) to fill the one symbol gap.

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

where μ is the subcarrier spacing (SCS) of the Uplink (UL) bandwidth portion (BWP), and l is the first OFDM symbol index of the next actual repetition after an orphan symbol. In some cases, the enhanced receiver may utilize this CP extension to obtain better LLRs or better channel estimates. According to a second option (labeled option 1.2), the CP extension may be less than a full symbol period (small delta value). In this case, the CP extended length may be:

(to ensure that the gap is no greater than 16 us), again where μ is the subcarrier spacing (SCS) of the Uplink (UL) bandwidth portion (BWP), and l is the first OFDM symbol index of the next actual repetition after an orphan symbol.

And is also provided with

Fig. 6A and 6B illustrate examples of CP extended lengths for different SCSs for a normal CP according to the first and second options, respectively.

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

Fig. 7 illustrates an example timeline 700 of such a solution. In the example shown in fig. 7, 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 single symbol actual repetitions 702. In this case, an orphan symbol may be discarded because it may not be considered a gap if it is not transmitted thereafter. If the one symbol is at the end of the burst (as in this example), then since both the gNB and the UE are aware of this, the gNB can schedule the next transmission accordingly taking into account the cancellation of the symbol. This approach may be used to address single symbol PUSCH repetition caused by any of the examples shown in fig. 4A-4C.

In some cases, if there are orphaned symbols, the UE may treat the configuration as an error condition (e.g., and not transmit any repetition or one or more of these repetitions). Such situations may be addressed by scheduling, e.g., by the gNB avoiding parameter settings that result in isolated symbols.

For example, an isolated symbol 802 that results in the parameter settings (k=4, s= 5,L =4) shown in the example timeline 800 of fig. 8A may be avoided by setting different parameters. As shown in the example timeline 810 of fig. 8B, the nominal repetition #2 is shifted using the 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 slot boundaries, effectively removing the isolated symbol. This approach may be used to address single symbol PUSCH repetition caused by any of the examples shown in fig. 4A-4C.

In some cases, if there is a DL or invalid symbol in the middle of a type B PUSCH repetition, the UE may consider such a case as an error case such that in an unlicensed band, the UE does not expect to receive a type B PUSCH repetition configuration including the DL or invalid symbol in the middle. Fig. 9A illustrates an example timeline 900 with such scenarios of repetition parameters (k=4, s=6, and l=4) and subframe configurations of isolated symbols 902 due to collisions with (invalid) downlink symbols. Fig. 9B illustrates an example timeline 910 with another such scenario of repetition parameters (k=4, s=10, and l=4) and subframe configuration of an isolated symbol 912 due to an invalid symbol configured by RRC. The UE may consider each of these scenarios as an error situation. As such, the gNB should avoid scheduling with such parameters and subframe configurations. This approach may be used to address single symbol PUSCH repetition caused by any of the examples shown in fig. 4B-4C.

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.

For example, as illustrated in the example timeline 1000 of fig. 10, in the case of repetition parameters (k=8, s=6, and l=4) and subframe configuration of the orphan symbol 1012 due to collision with DL symbols, the UE may attempt to initiate transmission using a channel access procedure, such as type 1 uplink channel access known as class 4 (Cat 4) Listen Before Talk (LBT), at each repetition boundary. In some cases, the UE may discard the orphan symbol at the beginning (single symbol actual repetition # 2). In some cases, the UE may effectively use the CP extension proposal (discussed above with reference to fig. 6) for intermediate single symbol actual repetition after the transmission has been initiated. This approach may be used to address single symbol PUSCH repetition caused by any of the examples shown in fig. 4B-4C.

Fig. 11 illustrates a communication device 1100 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations of the techniques disclosed herein, such as the operations illustrated in fig. 5. For example, communication device 1100 may be UE 120, such as shown in fig. 1 or fig. 2. Communication device 1100 includes a processing system 1102 coupled to a transceiver 1108. Transceiver 1108 is configured to transmit and receive signals (such as the various signals described herein) for communication device 1100 via antenna 1110. The processing system 1102 may 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.

The processing system 1102 includes a processor 1104 coupled to a computer-readable medium/memory 1112 via a bus 1106. In certain aspects, the computer-readable medium/memory 1112 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1104, cause the processor 1104 to perform the operations illustrated in fig. 5 or other operations for performing the various techniques discussed herein. In certain aspects, the computer-readable medium/memory 1112 stores code 1114 for detecting one or more actual Physical Uplink Shared Channel (PUSCH) repetitions to be segmented into including single-symbol actual PUSCH repetitions; and code 1116 for taking one or more actions to handle symbol length gaps in the transmission due to the single symbol actual PUSCH repetition. In certain aspects, the processor 1104 has circuitry configured to implement code stored in the computer-readable medium/memory 1112. The processor 1104 includes: circuitry 1120 for detecting a nominal Physical Uplink Shared Channel (PUSCH) repetition to be segmented into one or more actual PUSCH repetitions comprising a single symbol actual PUSCH repetition; and circuitry 1122 to take one or more actions to handle symbol length gaps in the transmission due to the single symbol actual PUSCH repetition. Circuitry 1120 and/or 1122 may be circuitry specifically designed to perform specified functions or may be general-purpose circuitry configured or programmed to perform these functions.

Additional considerations

The techniques described herein may be used for various wireless communication techniques such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE-advanced (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. TDMA networks may implement radio technologies such as global system for mobile communications (GSM). An OFDMA network may 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), IEEE802.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 the literature from an organization named "third generation partnership project" (3 GPP). cdma2000 and UMB are described in literature from an organization named "third generation partnership project 2" (3 GPP 2). NR is an emerging wireless communication technology under development.

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, while aspects may be described herein using terms commonly associated with 3G, 4G, or 5G wireless technologies, aspects of the disclosure may be applied in other generation-based communication systems.

In 3GPP, the term "cell" can refer to the coverage area of a Node B (NB) or an NB subsystem serving the coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and BS, next generation node BS (gNB or g B node), access Points (APs), distributed Units (DUs), carriers, or transmission-reception points (TRP) may be used interchangeably. The BS may provide communication coverage for a macrocell, picocell, femtocell, or other type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femtocell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a residence, etc.). The BS for a macro cell may be referred to as a macro BS. The BS for a pico cell may be referred to as a pico BS. The BS for a femto cell may be referred to as a femto BS or a home BS.

The UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer Premise Equipment (CPE), cellular telephone, smart phone, personal Digital Assistant (PDA), wireless modem, wireless communication device, handheld device, laptop, cordless telephone, wireless Local Loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, superbook, appliance, medical device or equipment, biometric sensor/device, wearable device (such as a smart watch, smart garment, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter/sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via a 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 may communicate with a BS, another device (e.g., a remote device), or some other entity. The wireless node may provide connectivity to 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.

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 a plurality of (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, the modulation symbols are transmitted in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers may be fixed and the total number of subcarriers (K) may depend on the system bandwidth. For example, the spacing of the subcarriers may be 15kHz, while the minimum resource allocation (referred to as a "resource block" (RB)) may be 12 subcarriers (or 180 kHz). Thus, the nominal Fast Fourier Transform (FFT) size may be equal to 128, 256, 512, 1024 or 2048 for a system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may also be divided into sub-bands. For example, the subbands may cover 1.08MHz (e.g., 6 RBs), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20MHz, respectively. In LTE, the basic Transmission Time Interval (TTI) or packet duration is a 1ms subframe.

NR may utilize OFDM with CP on uplink and downlink and include support for half duplex operation using TDD. In NR, one subframe is still 1ms, but the basic TTI is called a slot. A subframe includes a variable number of slots (e.g., 1, 2, 4, 8, 16 … … slots) depending on the subcarrier spacing. NR RBs are 12 consecutive frequency subcarriers. The NR may support a base subcarrier spacing of 15kHz and may define other subcarrier spacings with respect to the base subcarrier spacing, e.g., 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and slot lengths scale with subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming may be supported and beam directions may be dynamically configurable. MIMO transmission with precoding may also be supported. In some examples, MIMO configuration in DL may 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. Up to 8 serving cells may be used to support aggregation of multiple cells.

In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communication among some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. The 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 the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, the 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 the scheduling entity.

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, researching, looking up (e.g., looking up in a table, database, or another data structure), assuming, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and the like. Also, "determining" may include parsing, selecting, choosing, establishing, and the like.

As used herein, "or" is intended to be interpreted in an inclusive sense unless explicitly indicated otherwise. For example, "a or b" may include a alone, b alone, or a combination of a and b. As used herein, a phrase referring to a list of items "at least one of" or "one or more of" refers to any combination of these items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a. b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple identical elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" (unless specifically so stated) but rather "one or more". The term "some" means one or more unless specifically stated otherwise. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents that are presently or later to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No element of a claim should be construed under the specification of 35u.s.c. ≡112 (f) unless the element is explicitly recited using the phrase "means for … …" or in the case of method claims the element is recited using the phrase "step for … …".

The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These means may comprise 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 counterpart means-plus-function components with similar numbers. For example,

processors

258, 264, and 266 and/or controller/processor 280 of UE 120, and/or

processors

220, 230, 238 and/or controller/processor 240 of BS 110 shown in fig. 2 may be configured to perform operation 500 of fig. 5.

The means for receiving may comprise a transceiver, a receiver, or at least one antenna and at least one receive processor illustrated in fig. 2. The means for transmitting, means for sending, or means for outputting may comprise the transceiver, transmitter, or at least one antenna and at least one transmit processor illustrated in fig. 2. The means for detecting and the means for taking one or more actions may comprise a processing system that may include one or more processors, such as

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 shown in fig. 2.

In some cases, a device may not actually transmit a frame, but may have an interface (means for outputting) for outputting the frame for transmission. For example, the processor may output frames via a bus interface to a Radio Frequency (RF) front end for transmission. Similarly, a device may not actually receive a frame, but may have an interface (means for acquiring) for acquiring a frame received from another device. For example, the processor may obtain (or receive) frames from the RF front end via the bus interface for reception.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed 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. A processor may also be implemented as a combination of computing devices, e.g., 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.

If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including processors, machine-readable media, and bus interfaces. A bus interface may be used to connect network adapters and the like 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 case of UE 120 (see fig. 1), a user interface (e.g., 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 therefore, will not be described any further. A processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Those skilled in the art will recognize how best to implement the functionality described with respect to the processing system, depending on the particular application and the overall design constraints imposed on the overall network or system.

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on a machine-readable storage medium. A computer readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, machine-readable media may comprise a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium having instructions stored thereon, separate from the wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, the machine-readable medium, or any portion thereof, may be integrated into the processor, such as the cache and/or general purpose register file, as may be the case. By way of example, a machine-readable storage medium may comprise 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, a magnetic disk, an optical disk, a hard drive, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be implemented in a computer program product.

A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer readable medium may include a plurality of software modules. These software modules include instructions that, when executed by equipment (such as a processor), cause a processing system to perform various functions. These software modules may include a transmit module and a receive module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a trigger event occurs, the software module may be loaded into RAM from a hard drive. During execution of the software module, the processor may load some instructions into the cache to increase access speed. One or more cache lines may then be loaded into a general purpose register file for execution by the processor. Where functionality of a software module is described below, it will be understood that such functionality is implemented by a processor when executing instructions from the software module.

Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as Infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disc) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk, and blu-ray disc

A disc, in which the disc (disk) often magnetically reproduces data, and the disc (disk) optically reproduces data with a laser. Thus, in some aspects, a computer-readable medium may comprise a non-transitory computer-readable medium (e.g., a tangible medium). Additionally, for other aspects, the computer-readable medium may comprise a transitory computer-readable medium(e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such computer program products may include a computer-readable medium having instructions stored (and/or encoded) thereon that are executable by one or more processors to perform the operations described herein, such as instructions for performing the operations described herein and illustrated in fig. 5.

Further, it should be appreciated that modules and/or other suitable means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device can be coupled to a server to facilitate transfer of an apparatus 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 floppy disk, etc.), such that the apparatus can obtain the various methods once the storage device is coupled to or provided to a user terminal and/or base station. Further, any other suitable technique suitable for providing the methods and techniques described herein to a device may be utilized.

It is to be understood that the claims are not limited to the precise configurations and components illustrated above. Various modifications, substitutions and alterations can be made in the arrangement, 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 are to be accorded the widest scope consistent with the disclosure, principles and novel features disclosed herein.

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 that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination, or variation of a subcombination.

Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Furthermore, the figures may schematically depict one or more example processes in the form of a flowchart or flowsheet. However, other operations not depicted may be incorporated into the example process schematically illustrated. For example, one or more additional operations may be performed before, after, concurrently with, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations 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 comprising a single symbol actual PUSCH repetition; and

one or more actions are taken to handle symbol length gaps in transmissions due to the single symbol actual PUSCH repetition.

2. The method of claim 1, wherein the one or more actual PUSCH repetitions are scheduled for transmission on a shared spectrum.

3. The method of claim 2, wherein the one or more actions are taken to avoid losing access to the shared spectrum.

4. The method of claim 1, wherein the one or more actions comprise:

a Cyclic Prefix (CP) extension from the actual PUSCH repetition is used after the single symbol actual PUSCH repetition.

5. The method of claim 4, wherein the CP extended length is a single symbol duration.

6. The method of claim 4, wherein the CP-extended length occupies less than a symbol duration and is equal to or greater than the symbol duration minus a value of Δ.

7. The method of claim 1, wherein the one or more actions comprise:

And discarding the single-symbol actual PUSCH repetition in the case that the actual PUSCH repetition is not scheduled after the single-symbol actual PUSCH repetition.

8. The method of claim 1, wherein the one or more actions comprise:

the detection of the single symbol actual PUSCH repetition is considered as an error situation.

9. The method of claim 8, wherein the one or more actions further comprise:

any of the one or more actual PUSCH repetitions is refrained from being transmitted.

10. The method of claim 1, further comprising:

detecting semi-static downlink symbols or Radio Resource Control (RRC) configured invalid symbols in the middle of the one or more actual PUSCH repetitions, wherein:

the one or more actions include treating detection of invalid symbols of the semi-static downlink symbol or the Radio Resource Control (RRC) configuration in the middle of the one or more actual PUSCH repetitions as an error condition.

11. 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.

12. The method of claim 11, wherein a different action of the one or more actions is taken depending on whether the nominal PUSCH repetition is detected as a result of:

The nominal PUSCH repetition spans a slot boundary;

the nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to collision with semi-static downlink symbols; or alternatively

The nominal PUSCH repetition is segmented into the one or more actual PUSCH repetitions due to overlapping with invalid symbols of a Radio Resource Control (RRC) configuration.

13. The method of claim 1, wherein the one or more actions comprise:

the uplink channel procedure is used to resume the transmission at the boundary of each of the one or more actual PUSCH repetitions if the nominal PUSCH repetition is detected due to:

14. The method of claim 13, 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 inactive symbol.

15. An apparatus for wireless communication by a User Equipment (UE), comprising:

a processing system configured to:

16. The apparatus of claim 15, wherein the one or more actual PUSCH repetitions are scheduled for transmission on a shared spectrum.

17. The apparatus of claim 16, wherein the one or more actions are taken to avoid losing access to the shared spectrum.

18. The apparatus of claim 15, wherein the one or more actions comprise:

19. The apparatus of claim 18, wherein the CP extended length is a single symbol duration.

20. The device of claim 18, wherein the CP-extended length occupies less than a symbol duration and is equal to or greater than the symbol duration minus a value of Δ.

21. The apparatus of claim 15, wherein the one or more actions comprise:

22. The apparatus of claim 15, wherein the one or more actions comprise:

23. The apparatus of claim 22, wherein the one or more actions further comprise:

24. The apparatus of claim 15, further comprising:

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

26. The apparatus of claim 25, wherein a different action of the one or more actions is taken depending on whether the nominal PUSCH repetition is detected as a result of:

the nominal PUSCH repetition spans a slot boundary;

27. The apparatus of claim 15, wherein the one or more actions comprise using an uplink channel procedure to resume the transmission at a boundary of each of the one or more actual PUSCH repetitions if the nominal PUSCH repetition is detected due to:

28. The apparatus of claim 27, wherein the one or more actions further comprise:

29. An apparatus for wireless communication by a User Equipment (UE), comprising:

means for detecting that a nominal Physical Uplink Shared Channel (PUSCH) repetition is to be segmented into one or more actual PUSCH repetitions comprising a single symbol actual PUSCH repetition; and

means for taking one or more actions to handle symbol length gaps in transmissions due to the single symbol actual PUSCH repetition.

30. The apparatus of claim 29, wherein the one or more actual PUSCH repetitions are scheduled for transmission on a shared spectrum.

31. The apparatus of claim 30, wherein the one or more actions are taken to avoid losing access to the shared spectrum.

32. The apparatus of claim 29, wherein the one or more actions comprise:

33. The apparatus of claim 32, wherein the CP extended length is a single symbol duration.

34. The apparatus of claim 32, wherein the CP-extended length occupies less than a symbol duration and is equal to or greater than the symbol duration minus a value of Δ.

35. The apparatus of claim 29, wherein the one or more actions comprise:

36. The apparatus of claim 29, wherein the one or more actions comprise:

37. The apparatus of claim 36, wherein the one or more actions further comprise:

38. The apparatus of claim 29, further comprising:

means for detecting semi-static downlink symbols or Radio Resource Control (RRC) configured invalid symbols in the middle of the one or more actual PUSCH repetitions, wherein:

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

40. The apparatus of claim 39, wherein a different action of the one or more actions is taken depending on whether the nominal PUSCH repetition is detected as a result of:

the nominal PUSCH repetition spans a slot boundary;

41. The apparatus of claim 29, wherein the one or more actions comprise using an uplink channel procedure to resume the transmission at a boundary of each of the one or more actual PUSCH repetitions if the nominal PUSCH repetition is detected due to:

42. The apparatus of claim 41, wherein the one or more actions further comprise:

43. A User Equipment (UE), comprising:

at least one antenna; and

a processing system configured to:

one or more actions are taken via the at least one antenna to handle symbol length gaps in transmissions due to the single symbol actual PUSCH repetition.

44. A computer-readable medium for wireless communication by a User Equipment (UE), the computer-readable medium comprising code executable to: